Network Working Group P. Calhoun, Ed.
Request for Comments: 5416 Cisco Systems, Inc.
Category: Standards Track M. Montemurro, Ed.
Research In Motion
D. Stanley, Ed.
Aruba Networks
March 2009
Control and Provisioning of Wireless Access Points (CAPWAP) Protocol
Binding for IEEE 802.11
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Calhoun, et al. Standards Track [Page 1]RFC 5416 CAPWAP Protocol Binding for IEEE 802.11 March 2009Abstract
Wireless LAN product architectures have evolved from single
autonomous access points to systems consisting of a centralized
Access Controller (AC) and Wireless Termination Points (WTPs). The
general goal of centralized control architectures is to move access
control, including user authentication and authorization, mobility
management, and radio management from the single access point to a
centralized controller.
This specification defines the Control And Provisioning of Wireless
Access Points (CAPWAP) Protocol Binding Specification for use with
the IEEE 802.11 Wireless Local Area Network protocol.
Table of Contents
1. Introduction ....................................................4
1.1. Goals ......................................................5
1.2. Conventions Used in This Document ..........................5
1.3. Terminology ................................................5
2. IEEE 802.11 Binding .............................................7
2.1. CAPWAP Wireless Binding Identifier .........................7
2.2. Split MAC and Local MAC Functionality ......................7
2.2.1. Split MAC ...........................................7
2.2.2. Local MAC ..........................................12
2.3. Roaming Behavior ..........................................15
2.4. Group Key Refresh .........................................16
2.5. BSSID to WLAN ID Mapping ..................................17
2.6. CAPWAP Data Channel QoS Behavior ..........................18
2.6.1. IEEE 802.11 Data Frames ............................18
2.6.1.1. 802.1p Support ............................19
2.6.1.2. DSCP Support ..............................19
2.6.2. IEEE 802.11 MAC Management Messages ................21
2.7. Run State Operation .......................................21
3. IEEE 802.11 Specific CAPWAP Control Messages ...................21
3.1. IEEE 802.11 WLAN Configuration Request ....................22
3.2. IEEE 802.11 WLAN Configuration Response ...................23
4. CAPWAP Data Message Bindings ...................................23
5. CAPWAP Control Message Bindings ................................25
5.1. Discovery Request Message .................................25
5.2. Discovery Response Message ................................25
5.3. Primary Discovery Request Message .........................25