These are Brian's notes on HCD-TNC binding spec from the October F2F.
I'm doing these updates and will send a new version of the spec tomorrow.
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
mailto: blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
---------- Forwarded message ----------
From: Brian Smithson <bsmithson at ricohsv.com>
Date: Wed, Oct 23, 2013 at 1:47 PM
Subject: TNC binding spec notes
To: Ira McDonald <blueroofmusic at gmail.com>
Cc: "Murdock, Joe" <jmurdock at sharplabs.com>
(line numbers may be approximate) :-)
line 248 add "one or more" enforcement mechanisms)
340 change "may" to "might"
350-355 should be a numbered list
358-367 should be a numbered list
early in section 5 describe the behavior the sets of related attributes,
like firmware/resident/user application, etc.
firmware versions should be organized by 4-tuples
in security considerations, reference NEA
look at security considerations in the RFC
work with the SC to see how to make this more visible, maybe with Anne Price
1139-1142 fix the reference for IDS attributes (since we're updating IDS
CISSP, CISA, PMP, CSM
Senior Security Architect
Global Solutions Engineering
Business Development Center
bsmithson at ricohsv.com
-------------- next part --------------
An HTML attachment was scrubbed...