Hi,
I've just posted another *Prototype* draft of HCD TNC Binding.
This version addresses all typos and edits from the IDS WG session
at PWG F2F in October 2013.
For review at IDS WG session in February F2F and/or telecons.
ftp://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20140125.pdf
- clean w/ line numbers
ftp://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20140125-rev.pdf
- redlines w/ line numbers
Comments?
Cheers,
- Ira
---------------------
Change History
25 January 2014
- Global - Updated copyright to 2014 (headers/boilerplate), per PWG F2F
10/23/13
- Global - Corrected typos in previous draft
- Revised section 2.3 TNC Terminology definition of CESP, per PWG F2F
10/23/13
- Revised section 3.1 Rationale to change "may" to "might", per PWG F2F
10/23/13
- Revised sections 3.3 and 3.4 to change to numbered lists, per PWG F2F
10/23/13
- Revised section 5 to discuss ordered correlated attributes (FirmwareXxx,
etc.), per PWG F2F 10/23/13
- Revised section 6.1 conformance to reference sections 5, section 7, and
section 8, per PWG F2F 10/23/13
- Revised sections 6.1 and 6.2.2 conformance to align with ordered
correlated attributes definition in section 5, per PWG F2F 10/23/13
- Revised section 8 Security Considerations to reference IETF NEA PA-TNC,
PB-TNC, and PT-TLS, per PWG F2F 10/23/13
- Revised section 10.1 Normative References to refer to PWG 5110.1-2014
(new version) and clarify that PT-EAP is in RFC Editor's Queue awaiting
IETF TEAP, per PWG F2F 10/23/13
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ids/attachments/20140125/ad28ee4b/attachment.html>