1. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IETF Liaison Report September 2003 Dorothy Stanley – Agere Systems IEEE 802.11 Liaison To/From IETF

2. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) New IETF Activities IETF RADIUS Working Group May be Formed –Wi-Fi WLAN Public Access Needs –Requests from 3GPP2 Proposed charter includes: –Specifying how RADIUS handles prepaid accounting for WLAN (& other) Pre-paid applications –Standardizing WLAN-related RADIUS attributes. –Standardizing a basic RADIUS attribute extension mechanism Contact Bernard Aboba aboba@internaut.com or David Nelson dnelson@enterasys.comaboba@internaut.comdnelson@enterasys.com

3. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) New IRTF Activities Wireless Fast Handoff Research Group May be Formed Charter: Design, implement, and empirically measure protocols that support fast and secure wireless hand-offs Expected areas of interest: Inter and Intra-domain AAA, e.g. RADIUS and DIAMETER, communications-AAA to NAS communications-Coordination of Layer 2 and Layer 3 roaming triggers-Security Association movement and key caching Contact Bill Arbaugh, waa@cs.umd.edu, Insun Lee, insun@samsung.comwaa@cs.umd.edu insun@samsung.com Also see http://www.ietf.org/internet-drafts/draft-irtf- aaaarch-handoff-01.txt http://www.ietf.org/internet-drafts/draft-irtf- aaaarch-handoff-01.txt

4. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) Update: CAPWAP BOF July 2003 – Control And Provisioning of Wireless Access Points (CAPWAP) BOF Held –Vendors interested in a standardized, secure protocol for lightweight access points, access routers. –Slides available: http://www.geocities.com/kempf42/capwap.zip http://www.geocities.com/kempf42/capwap.zip –Mailing List: lwapp@frascone.comlwapp@frascone.com –Current draft: http://www.airespace.com/ftp/draft-calhoun- seamoby-lwapp-03.txthttp://www.airespace.com/ftp/draft-calhoun- seamoby-lwapp-03.txt IETF CAPWAP WG May be formed; Charter finalized, awaiting approval

5. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) CAPWAP BOF -Charter Charter includes –Link layer independent protocol, with mappings for specific wireless L2s –Discovery of a CAPWAP manager –Acquisition of APs by CAPWAP manager. –Configuration and monitoring of wireless link by CAPWAP manager. –Partially and/or fully terminate the wireless MAC layer at the CAPWAP manager. –Security for CAPWAP signaling

6. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IEEE 802.11i Dependencies IETF AES-CCM Specification –Approved by IESG and now in RFC editor’s Queue –Request made to expedite RFC number assignment, should be available shortly –See http://www.ietf.org/internet-drafts/draft-housley-ccm- mode-02.txthttp://www.ietf.org/internet-drafts/draft-housley-ccm- mode-02.txt (Of Interest) NIST has recently developed draft –Special Publication 800-38C, "Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality" –Now available for review –See http://csrc.nist.gov/publications/drafts.html.http://csrc.nist.gov/publications/drafts.html

7. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IEEE 802.11i Dependencies (via 802.1aa) RFC 2284bis – In IETF EAP WG last call –http://www.ietf.org/internet-drafts/draft-ietf-eap- rfc2284bis-05.txthttp://www.ietf.org/internet-drafts/draft-ietf-eap- rfc2284bis-05.txt –Last call closes September 25 th, 2003. Send comments to eap@frascone.com in the format specified at http://www.drizzle.com/~aboba/EAP/eapissues.htmleap@frascone.com http://www.drizzle.com/~aboba/EAP/eapissues.html

8. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IEEE 802.11i Dependencies (via 802.1aa) RFC 3579 RADIUS support for EAP, published –RFC 3579 depends on RFC 3576 (Dynamic Authorization, published) –RFC 3576 depends on RFC 3575 (RADIUS IANA considerations, published) RFC 3580 802.1X RADIUS Usage Guidelines, published

9. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) Summary:TGi Requests January 2002 - Letter to IETF requesting work, see document 02/040 –EAP Method Definition to meet 802.11i requirements –Specification of EAP Keying Framework –RADIUS Extensions for Key Delivery March 2003 – Letter To IETF providing information, see document 03/243 –EAP Method Requirements – Key Strength Requirements

10. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IETF Responses - 1 EAP Method Definition –EAP working group was formed –The EAP Specification, RFC 2284bis-05, now in EAP WG last call, http://www.ietf.org/internet-drafts/draft-ietf-eap-rfc2284bis- 05.txthttp://www.ietf.org/internet-drafts/draft-ietf-eap-rfc2284bis- 05.txt –EAP methods are discussed in the WG relative to RFC2284bis EAP Method Requirements –Plan that the IEEE 802.11i EAP Method requirements will be published as an RFC, and will reference security properties defined in RFC 2284. –EAP method specifications will include security claims based on the RFC2284 security properties, and can include a statement about whether the IEEE 802.11i requirements are met.

11. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IETF Responses - 2 EAP Key Framework Document –See http://www.ietf.org/internet-drafts/draft-aboba-pppext- key-problem-07.txthttp://www.ietf.org/internet-drafts/draft-aboba-pppext- key-problem-07.txt –Will become an EAP WG work item –Key Naming – Coordinate PMK name definitions as much as possible between 802.11i and EAP WG EAP State Machine Document –Will become an EAP WG work item RADIUS and RADIUS attribute usage with EAP –RFCs 3575, 3576, 3579, 3580 Published

12. doc: 11-03-0763-00-0000 Submission September 2003 Dorothy Stanley (Agere Systems) IETF Meetings Recent/upcoming meetings: –November 9-14, 2003 Minneapolis, MN –February 29-March 5, 2004 Seoul, Korea http://www.ietf.org TBD: Website of IETF/IEEE 802.11 request/response status –As maintained for others, for example see http://www.3gpp.org/TB/Other/IETF.htm http://www.3gpp.org/TB/Other/IETF.htm