I've just posted another *Prototype* draft of HCD TNC Binding.
Note: This version is technically complete (i.e., stable content
with no outstanding mapping or syntax issues). This version is
ready for prototyping.
The changes in this version were all based on IDS WG review
on 1 June 2015 of the previous version where most changes
were suggested during recent discussions with Andreas Steffen
of HSR University of Applied Sciences, Rapperswil, Switzerland
- project leader of strongSWAN that includes open source
implementations of most TCG and IETF TNC protocols:
For review at IDS WG telecons.
- clean w/ line numbers
- redlines w/ line numbers
8 June 2015
Editorial – Added new section 1.1 Rationale for HCD-Specific TNC PA
Subtypes to explain the need for these new PA subtypes to allow dispatch of
the appropriate HCD-specific Integrity Measurement Validator (IMV) and
forward reference sections 5 and 9 for details, per IDS WG
Editorial – Revised section 2.3 TCG TNC Terminology to delete Clientless
Endpoint (i.e., to remove definition that is not part of the IETF NEA TNC
architecture), per IDS WG
Editorial – Revised section 2.4 Acronyms to correct font/format of TNC
link, per IDS WG
Editorial – Revised section 5 HCD Statement of Health for TNC Protocol to
add reasoning for new HCD-specific PA subtypes, per IDS WG
Editorial – Revised section 5.2 Conditionally Mandatory Attributes to allow
PA subtype of “Any PWG-registered value (see section 9.1), per IDS WG
Editorial – Revised section 5.4 Correlated Attributes bullet 2 to change
“SHOULD be omitted” to “SHOULD NOT be included”, per IDS WG
Editorial – Revised section 9.1 PWG Standard PA Subtypes to added a new
note about the feeder element that may be present in a Media Path, per IDS
-------------- next part --------------
An HTML attachment was scrubbed...