1. July 27, 2009IETF NEA Meeting1 NEA Working Group IETF 75 nea[-request]@ietf.org http://tools.ietf.org/wg/nea Co-chairs: Steve Hanna shanna@juniper.netshanna@juniper.net Susan Thomsonsethomso@cisco.comsethomso@cisco.com

2. July 27, 2009IETF NEA Meeting2 Agenda Review 1740 Administrivia Blue Sheets Jabber & Minute scribes Agenda bashing 1745 WG Status 1750 Addressing IETF LC and IESG comments for PB-TNC: http://www.ietf.org/internet-drafts/draft-ietf-nea-pb-tnc-04.txt 1820 Addressing IETF LC and IESG comments for PA-TNC: http://www.ietf.org/internet-drafts/draft-ietf-nea-pb-tnc-04.txt 1850 Discuss proposed charter updates 1915 Process for soliciting proposals for PT 1930 Next Steps 1940 Adjourn

3. July 27, 2009IETF NEA Meeting3 WG Status Internet Drafts –PA-TNC -04 I-D (Apr 2009) http://www.ietf.org/internet-drafts/draft-ietf-nea-pa-tnc-04.txt –PB-TNC -04 I-D (Apr 2009) http://www.ietf.org/internet-drafts/draft-ietf-nea-pb-tnc-04.txt IETF Last Call (Jun 9-23, 2009). Comments received from: –IANA –Gen-Art –Other PA-TNC and PB-TNC in IESG evaluation now –Several IESG members have made comments –Completes last milestone in current charter WG Charter Revision Being Discussed –Proposed charter updates sent to mailing list for review (Jun 12)

4. July 27, 2009IETF NEA Meeting4 NEA Protocol Overview

5. July 27, 2009IETF NEA Meeting5 NEA Reference Model from RFC 5209 Posture Collectors Posture Validators Posture Transport Server Posture Attribute (PA) protocol Posture Broker (PB) protocol NEA ClientNEA Server Posture Transport (PT) protocols Posture Transport Client Posture Broker Client Posture Broker Server

6. July 27, 2009IETF NEA Meeting6 PA-TNC Within PB-TNC PT PB-TNC Header (Batch-Type=CDATA) PB-TNC Message (Type=PB-PA, PA Vendor ID=0, PA Subtype= OS) PA-TNC Message PA-TNC Attribute (Type=Product Info, Product ID=Windows XP) PA-TNC Attribute (Type=Numeric Version, Major=5, Minor=3,...)

7. July 27, 2009IETF NEA Meeting7 Addressing IETF LC and IESG Comments for PB-TNC

8. July 27, 2009IETF NEA Meeting8 Summary of Changes in draft-ietf-nea-pb-tnc-04.txt Changes discussed at IETF 74 with WG consensus confirmed on NEA email list –PB-TNC version handling changed to match PA-TNC –PB-Assessment-Result and PB-Access- Recommendation MUST NOT appear in a batch of type other than RESULT –RESULT batches MAY include PB-Access- Recommendation (was SHOULD)

9. July 27, 2009IETF NEA Meeting9 IETF LC Comments on draft-ietf-nea-pb-tnc-04.txt Concern re TCG text –Propose: Remove section 1.1, add acknowledgement

10. July 27, 2009IETF NEA Meeting10 IANA Comments on draft-ietf-nea-pb-tnc-04.txt Several values listed in the specification differ from contents of IANA Considerations –PB-TNC Message Types 2-7 with PEN 0 –PB-TNC Message Type 0xFFFFFFFF (reserved for all PEN values) –Propose: Fix IANA Considerations Concern re archiving specs for registered vendor-specific values and making these publicly available if vendor stops doing so –Resolved: IANA has agreed to do this

11. July 27, 2009IETF NEA Meeting11 Susan Thomson’s Comments on draft-ietf-nea-pb-tnc-04.txt Remove Retry-Acknowledge –Not needed with new state machine –Propose: Accept Version should be 2 for Version Not Supported in section 4.1 –Already says 2 in section 4.9.2 –Propose: Accept

12. July 27, 2009IETF NEA Meeting12 Some IESG Comments on draft-ietf-nea-pb-tnc-04.txt Add language tag to Remediation-String –Propose: Add language tag No way to indicate reserved versions with Min/Max –Propose: Reserved versions always subtracted from range Description of Posture Collector Identifier and Posture Validator Identifier does not reflect decision to allow several IDs per PC/PV –Propose: Fix this text

13. July 27, 2009IETF NEA Meeting13 More IESG Comments on draft-ietf-nea-pb-tnc-04.txt Tighten up error handling, changing SHOULDs to MUSTs, etc. –Propose: Examine and change as needed Minor changes (typos, clarifications, inconsistencies, missing references) –Propose: Make these changes

14. July 27, 2009IETF NEA Meeting14 Addressing IETF LC and IESG Comments for PA-TNC

15. July 27, 2009IETF NEA Meeting15 Summary of Changes in draf-ietf-nea-pa-tnc-04 Changes discussed at IETF 74 with WG consensus confirmed on NEA email list –MUST use same version number in response –MUST use and parse version 1 for Version Not Supported errors –Dropped version 0 for version discovery –Minor wording changes

16. July 27, 2009IETF NEA Meeting16 IETF LC Comments on draft-ietf-nea-pa-tnc-04.txt Concern re TCG text –Propose: Remove section 1.1, add acknowledgement

17. July 27, 2009IETF NEA Meeting17 IANA Comments on draft-ietf-nea-pa-tnc-04.txt Several values listed in the specification are missing from IANA Considerations –PA-TNC Attribute Types 9-12 with PEN 0 –PA-TNC Attribute Type 0xFFFFFFFF (reserved for all PEN values) –PA-TNC Error Code 0 with PEN 0 –Propose: Add to IANA Considerations Concern re archiving specs for registered vendor-specific values and making these publicly available if vendor stops doing so –Resolved: IANA has agreed to do this

18. July 27, 2009IETF NEA Meeting18 Some IESG Comments on draft-ietf-nea-pa-tnc-04.txt Add language tag to Remediation-String –Propose: Add language tag Clarify Posture Collector behavior when receiving Attribute-Request –Propose: Say MUST respond with an attribute or an error Add Security Considerations text re dangers of automated remediation –Propose: Add such text Question re status of PA-TNC Security draft –Propose: Remove text relating to this since no longer active

19. July 27, 2009IETF NEA Meeting19 More IESG Comments on draft-ietf-nea-pa-tnc-04.txt Tighten up error handling, changing SHOULDs to MUSTs, etc. –Propose: Examine and change as needed Field Types defined in section 3.6 not used elsewhere –Propose: Editors will try using them throughout. Not sure whether complexity will exceed benefit. Please provide suggested list of Designated Experts –Propose: WG chairs will seek volunteers and select nominees. IESG will officially designate experts, as required by RFC 5226 Minor changes (typos, clarifications, inconsistencies) –Propose: Make these changes

20. July 27, 2009IETF NEA Meeting20 Discuss Proposed Charter Updates

21. July 27, 2009IETF NEA Meeting21 Proposed Charter Updates Goal: Allow WG to define PT –Allow specification of one or more PTs to encapsulate PB, preferably leveraging existing transport protocols –Require at least one mandatory to implement PT –Updated milestones Already reviewed on list with positive response Any concerns?

22. July 27, 2009IETF NEA Meeting22 Process for Developing PT

23. July 27, 2009IETF NEA Meeting23 Proposed Process for PT Same process as for PA and PB Solicit proposals as individual submissions WG reviews proposals WG determines contents of -00 NEA WG I-Ds Normal IETF development process from there

24. July 27, 2009IETF NEA Meeting24 Next Steps

25. July 27, 2009IETF NEA Meeting25 Next Steps for NEA-WG PA-TNC and PB-TNC I-Ds: –Resolve IESG comments with IESG –Post -05 versions –Perform another WGLC –Submit to AD for IESG evaluation Re-charter to work on PT –Revise proposed charter based on comments –Submit charter to AD for IESG Evaluation