Hi,
I've just posted the first *Prototype* draft of HCD TNC Binding.
For review at this week's IDS WG session during our PWG F2F meeting!
Mike - please add link to agenda page.
ftp://ftp.pwg.org/pub/pwg/ids/wd/wd-ids-tnc10-20121202.pdf / doc
- clean w/ line numbers
ftp://ftp.pwg.org/pub/pwg/ids/wd/wd-ids-tnc10-20121202-rev.pdf / doc
- redlines w/ line numbers
WARNING: During the updates to this HCD-TNC document based on
IDS WG review on 6 June 2012, I discovered several mandatory changes
to HCD-ATR (and therefore HCD-NAP) which were agreed but NOT
implemented in the current versions out for PWG Last Call. See:
ftp://ftp.pwg.org/pub/pwg/ids/minutes/ids-f2f-minutes-20120606.pdf
- see especially decisions to change mandatory attributes
Comments?
Cheers,
- Ira
---------------------
Change History
2 December 2012
Editorial – Changed status to Prototype Draft (only boilerplate sections
and PT-TLS/PT-EAP sections are still to be written).
Editorial – Global – Revised all sections that still have missing text and
added “ISSUE: xxx” (for clarity).
Editorial – Global – Revised all text that contains numbered or alphabetic
lists to put each element on a separate line, per IDS WG review.
Editorial – Revised Abstract and section 1 Introduction to expand scope to
include both trusted initial network endpoint attachment and continuous
health assessment of Imaging Devices, per IDS WG review.
Editorial – Revised section 3 Requirements to add text for rationale, use
cases, out-of-scope, and design requirements, per PWG process.
Editorial – Fixed broken formatting at beginning of sections 5.1 and 6 (an
artifact of accepting changes).
Editorial – Revised section 5 HCD Statement of Health for TNC Protocol to
add note that all health assessment attributes MUST be supplied in their
complete form (i.e., MUST not be truncated due to packets sizes or other
constraints), per IDS WG review.
Editorial – Revised section 5 HCD Statement of Health for TNC Protocol to
add note that multi-valued attributes are delimited by CR/LF pairs and
therefore individual values MUST NOT contain either CR or LF, per IDS WG
review.
Editorial – Revised section 5.1 Mandatory Attributes to change all PWG
NOSKIP attributes to SKIP (to allow interoperation w/ an IMV without
PWG-specific module), per IDS WG review.
Editorial – Revised section 5.2 Conditionally Mandatory Attributes to put
“CONDITIONALLY REQUIRED:” in front of all capability constraints and made
into separate paragraph (for clarity).
Editorial – Revised section 5.1.6 to correct spelling of “Attribute Value”,
per IDS WG review.
Editorial – Revised section 5.1.9 FirmwarePatches, section 5.2.2
UserApplicationPatches, and section 5.2.8 ResidentApplicationPatches to
change delimiter from semicolon to CR/LF pair, per IDS WG review.
Editorial – Moved sections 5.2.9 PSTNFaxEnabled and 5.2.10 Time Source to
section 5.1 Mandatory Attributes, per IDS WG review.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ids/attachments/20121202/99aa0ea5/attachment-0001.html>