1 / 8

IEEE 802.11-IETF March Summary

IEEE 802.11-IETF March Summary. Dorothy Stanley, Agere Systems. IETF/IEEE 802.11 January 15 th , 2004 Meeting Summary. CAPWAP Potential need for additional IEEE 802.11 AP functionality and interface requirement definition Continue planned liaison and review activities

jam
Download Presentation

IEEE 802.11-IETF March Summary

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. IEEE 802.11-IETF March Summary Dorothy Stanley, Agere Systems D. Stanley, Agere Systems

  2. IETF/IEEE 802.11 January 15th, 2004 Meeting Summary • CAPWAP • Potential need for additional IEEE 802.11 AP functionality and interface requirement definition • Continue planned liaison and review activities • RADIUS Extensions (RADEXT) Interaction • Process for RADIUS attribute definition: Same as IEEE 802.1 (Publish as Internet Draft for Review) • EAP Network Discovery • Q: Is This being Addressed in 802.11? • A: Network Discovery alternatives are in scope for proposed Wireless Interworking SG D. Stanley, Agere Systems

  3. Attendees • IETF: Bert Wijnen (AD Operations), Bernard Aboba (IAB), James Kempf (IESG), Dave Nelson (RADEXT, also .11) • IEEE 802.11: Stuart Kerry (Chair), Bob O’Hara, David Halasz (Chair 802.11i), Dorothy Stanley (IEEE 802.11 to IETF Liaison), Clint Chaplin (Chair Fast Roaming SG) D. Stanley, Agere Systems

  4. IETF/IEEE 802.11 Meeting CAPWAP Discussion - 1 • Several vendors have come to the IETF requesting definition of a CAPWAP protocol; Definition of any CAPWAP protocol(s) require assumptions on AP functionality partitioning between AP and AC. Together the AP and AC provide the traditional “AP” functionality • Current IEEE 802.11 AP functionality and interface requirements definition is sparse, and located across several documents. Need a cohesive, complete definition. • Consider the AP “functional” architecture and the “network” architecture • IEEE 802.11 owns the definition of AP functionality. • IETF successfully defines protocols for use between network elements, typically at layer 3 and above. • Once the AP functions are defined, they can be mapped to a network architecture, and the IETF can define/re-use existing protocols for communication between the network elements. D. Stanley, Agere Systems

  5. IETF/IEEE 802.11 Meeting CAPWAP Discussion- 2 • CAPWAP Working Group has been formed with a charter to perform a taxonomy of existing vendor implementations, to identify protocols in use. • CAPWAP Working Group should also identify elements of AP functionality definition that are needed – as input to IEEE 802.11 further AP functional architecture definition • IEEE 802.11 will initiate a call for interest for AP architecture definition • IEEE 802.11 Wireless LANs Next Generation (WNG) committee March 14-19 agenda includes: AP Functional Definition. The purpose is to codify the functional architecture including functional blocks, interfaces and information exchanges • Continue planned liaison and review activities D. Stanley, Agere Systems

  6. IETF/IEEE 802.11 Meeting – RADIUS Extensions • RADIUS Extensions (RADEXT) Working Group to be formed • What process should be used for RADIUS attribute definition? • Define attributes in IEEE 802.11? • Define attributes in IETF? • Had issues in the past with IEEE 802.11f incorrectly defining RADIUS commands • Some of the IEEE 802.11 attributes actually are more general in scope; useful to have these defined centrally, to identify general needs across applications (IEEE 802.11, 802.1, 3GPP, Wi-Fi, etc) • Agreement: Process for RADIUS attribute definition: Same as IEEE 802.1 (Publish IEEE 802.11 needs as an Internet Draft to obtain Review within IETF) • Agreement: RADIUS command definition in RADEXT D. Stanley, Agere Systems

  7. IETF/IEEE 802.11 Meeting – Discussion EAP Network Discovery • Is EAP network discovery being addressed in IEEE 802.11 working groups? • Network Discovery alternatives are in scope for proposed WLAN Inter-working with External IP networks SG • Determine impacts on IEEE 802.11, for example:network selection: is anything additional required in the MAC to support network selection, such as operator advertisement, discovery of network capabilities before authentication etc? • Work underway on an Internet draft summarizing the requests and current status of IETF work (B. Aboba, J. Arrko), see http://www.ietf.org/internet-drafts/draft-ietf-eap-netsel-problem-00.txt • Have received requests to use EAP as a mechanism for WLAN network discovery • Discussion of these requests should be in new IEEE 802.11 SG D. Stanley, Agere Systems

  8. IEEE 802.11 EAP Requirements • IEEE 802.11 has documented the requirements on EAP methods for WLAN applications, see IEEE document 11-04-0160-01-000i-ieee-802-11-eap-requirements.doc • Informational RFC drafted to document the requirements in the IETF, see http://www.ietf.org/internet-drafts/draft-walker-ieee802-req-00.txt • Stuart Kerry (IEEE 802.11 Chair) requested publication of this document as an informational RFC • IETF last call will complete March 28, 2004 D. Stanley, Agere Systems

More Related