1 / 11

CAPWAP Architectural Requirements on 802.11

This article discusses the architectural requirements of CAPWAP for interoperability between access controllers and access points in large WLAN deployments. It explores the need for manageability, security, mobility, and quality of service in wireless networks.

cleo
Download Presentation

CAPWAP Architectural Requirements on 802.11

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. CAPWAP Architectural Requirements on 802.11 Michael Montemurro Chantry Networks Michael Montemurro, Chantry Networks

  2. Introduction • CAPWAP goal is to provide interoperability between an “Access Controller” and an “Access Point” • The motivation is to provide: • Manageability • Security • Mobility • Quality of Service … across “large” WLAN deployments Michael Montemurro, Chantry Networks

  3. What is CAPWAP really? • It’s an interface between AP’s and an Access Controller. • It needs to be: • Robust • Secure • Provide functionality to make it easier to deploy and manage a wireless network Michael Montemurro, Chantry Networks

  4. CAPWAP Architecture Definition • Presents Four Alternative Architectures: • Traditional AP Architecture with centralized management • AP’s controlled centrally by Access Controller • AP’s sharing 802.11 services with Access Controller • Access Controller provides 802.11 MAC state – AP’s reduce to radios. Michael Montemurro, Chantry Networks

  5. 802.11 Architecture Definition • 802.11 architecture defined as MAC services between STA’s • Services for an AP can be: • Authentication, Association, Deauthentication, Disassociation, Reassociation, Integration, MSDU Delivery Michael Montemurro, Chantry Networks

  6. Architecture Requirements • The “service”-based architecture for 802.11 should NOT need to change to support CAPWAP • The question is? • Should the 802.11 standard be modified to recognize CAPWAP as a new service? • Or should there be a Recommended Practice to address the a new service for CAPWAP? Michael Montemurro, Chantry Networks

  7. What does CAPWAP need from 802.11? • A component to communicate with the AR. • It would be nice to have a standard interface into the 802.11 MAC Michael Montemurro, Chantry Networks

  8. MAC Sublayer PLCP Sublayer PMD Sublayer Modification to MAC for CAPWAP MAC Sublayer Management Entity SME CAPWAP Interface Data Link Layer Access Controller PHY Sublayer Management Entity Physical Layer New service should be defined as part of 802.11 Michael Montemurro, Chantry Networks

  9. IAPP and CAPWAP • 802.11f was defined to support interoperability between Access Points • IAPP defines primitives to use between Access Points: MOVE, ADD, etc. • If RADIUS interaction was removed or made optional, IAPP primitives could be extended to support CAPWAP Michael Montemurro, Chantry Networks

  10. Extend 802.11 Services Across AP’s • These primitives could be extended to address: • CAPWAP communications • Fast roaming • RF Metrics • Load-balancing information Michael Montemurro, Chantry Networks

  11. Conclusions • 802.11 Architecture does not need to change to accommodate CAPWAP • A new service could be defined using part of IAPP, to provide primitives to support CAPWAP, Fast Roaming, and potential future extensions Michael Montemurro, Chantry Networks

More Related