1 / 8

IETF Liaison Report

IETF Liaison Report. November 2003 Dorothy Stanley – Agere Systems IEEE 802.11 Liaison To/From IETF. IETF AES-CCM Specification Issued as RFC 3610, see http://www.ietf.org/rfc/rfc3610.txt Resolved 802.11i LB 61 comments. IEEE 802.11i Dependencies. RFC 2284bis – In IETF last call

rehan
Download Presentation

IETF Liaison Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF Liaison Report November 2003 Dorothy Stanley – Agere Systems IEEE 802.11 Liaison To/From IETF

  2. IETF AES-CCM Specification Issued as RFC 3610, see http://www.ietf.org/rfc/rfc3610.txt Resolved 802.11i LB 61 comments IEEE 802.11i Dependencies

  3. RFC 2284bis – In IETF last call http://www.levkowetz.com/pub/ietf/drafts/eap/rfc2284bis/draft-ietf-eap-rfc2284bis-07.d.html Last call (equivalent of Sponsor Ballot) closed November 6th , 2003. IEEE 802.11i Dependencies (via 802.1-REV)

  4. Control And Provisioning of Wireless Access Points (CAPWAP) BOF-2 will be held Nov 14th, 2003 BOF-2 Chairs Mahalingam Mani, mmani@avaya.com and Dorothy Gellert, Dorothy.Gellert@nokia.com Mailing List: lwapp@frascone.com Current draft: http://www.airespace.com/ftp/draft-calhoun-seamoby-lwapp-03.txt Charter, links, issues lise available at http://www.frascone.com/lwapp/ Request for IEEE Review of CAPWAP documents, after WG formed. Please see Stuart Kerry or Dorothy Stanley if you’re interested. Update: CAPWAP BOF

  5. Clear problem statement of CAPWAP work Description of the split AP (AP – Access Controller) architecture CAPWAP security requirements, defining the needs for security between the AP and the AC, both for host data transport and for AP-AC signaling and control Discovery of ACs by APs Auto-organization of APs and ACs into a managed wireless access network, including AC redundancy Secure Encapsulation of host data and AC-AP signaling, as necessary to address the requirements Secure Configuration of the AP by the AC CAPWAP BOF -Charter

  6. IETF RADIUS Working Group May be Formed RADEXT BOF to be held November 14th, 2003 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.com Update: RADIUS WG

  7. EAP Key Framework Document See http://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 Joint meeting held with 802.11i, Herndon Oct 15, topics: Document status, Key Scoping, EAP State Machines, Key Hierarchies. See 03/830. EAP State Machine Document Will become an EAP WG work item Update: EAP Keying

  8. Recent/upcoming meetings: November 9-14, 2003 Minneapolis, MN Feb 29-March 5 2004 Seoul, Korea August 1-6, 2004 November 7-12, 2004 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 IETF Meetings

More Related