Network Working Group
Request for Comments: 5416
Category: Standards Track
P. Calhoun, Ed.
Cisco Systems, Inc.
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 2009
Abstract
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
5.4. Primary Discovery Response Message ........................26
5.5. Join Request Message ......................................26
5.6. Join Response Message .....................................26
5.7. Configuration Status Request Message ......................26
5.8. Configuration Status Response Message .....................27
5.9. Configuration Update Request Message ......................27
Calhoun, et al.
Standards Track
[Page 2]
RFC 5416
CAPWAP Protocol Binding for IEEE 802.11
March 2009
5.10. Station Configuration Request ............................28
5.11. Change State Event Request ...............................28
5.12. WTP Event Request ........................................28
6. IEEE 802.11 Message Element Definitions ........................29
6.1. IEEE 802.11 Add WLAN ......................................29
6.2. IEEE 802.11 Antenna .......................................35
6.3. IEEE 802.11 Assigned WTP BSSID ............................36
6.4. IEEE 802.11 Delete WLAN ...................................37
6.5. IEEE 802.11 Direct Sequence Control .......................37
6.6. IEEE 802.11 Information Element ...........................38
6.7. IEEE 802.11 MAC Operation .................................39
6.8. IEEE 802.11 MIC Countermeasures ...........................41
6.9. IEEE 802.11 Multi-Domain Capability .......................42
6.10. IEEE 802.11 OFDM Control .................................43
6.11. IEEE 802.11 Rate Set .....................................44
6.12. IEEE 802.11 RSNA Error Report From Station ...............44
6.13. IEEE 802.11 Station ......................................46
6.14. IEEE 802.11 Station QoS Profile ..........................47
6.15. IEEE 802.11 Station Session Key ..........................48
6.16. IEEE 802.11 Statistics ...................................50
6.17. IEEE 802.11 Supported Rates ..............................54
6.18. IEEE 802.11 Tx Power .....................................54
6.19. IEEE 802.11 Tx Power Level ...............................55
6.20. IEEE 802.11 Update Station QoS ...........................56
6.21. IEEE 802.11 Update WLAN ..................................57
6.22. IEEE 802.11 WTP Quality of Service .......................61
6.23. IEEE 802.11 WTP Radio Configuration ......................63
6.24. IEEE 802.11 WTP Radio Fail Alarm Indication ..............65
6.25. IEEE 802.11 WTP Radio Information ........................66
7. IEEE 802.11 Binding WTP Saved Variables ........................67
7.1. IEEE80211AntennaInfo ......................................67
7.2. IEEE80211DSControl ........................................67
7.3. IEEE80211MACOperation .....................................67
7.4. IEEE80211OFDMControl ......................................67
7.5. IEEE80211Rateset ..........................................67
7.6. IEEE80211TxPower ..........................................67
7.7. IEEE80211QoS ..............................................68
7.8. IEEE80211RadioConfig ......................................68
8. Technology Specific Message Element Values .....................68
8.1. WTP Descriptor Message Element, Encryption
Capabilities Field ........................................68
9. Security Considerations ........................................68
9.1. IEEE 802.11 Security ......................................68
10. IANA Considerations ...........................................70
10.1. CAPWAP Wireless Binding Identifier .......................70
10.2. CAPWAP IEEE 802.11 Message Types .........................70
10.3. CAPWAP Message Element Type ..............................70
10.4. IEEE 802.11 Key Status ...................................71
Calhoun, et al.
Standards Track
[Page 3]
RFC 5416
CAPWAP Protocol Binding for IEEE 802.11
March 2009
10.5. IEEE 802.11 QoS ..........................................71
10.6. IEEE 802.11 Auth Type ....................................71
10.7. IEEE 802.11 Antenna Combiner .............................71
10.8. IEEE 802.11 Antenna Selection ............................72
10.9. IEEE 802.11 Session Key Flags ............................72
10.10. IEEE 802.11 Tagging Policy ..............................72
10.11. IEEE 802.11 WTP Radio Fail ..............................72
10.12. IEEE 802.11 WTP Radio Type ..............................73
10.13. WTP Encryption Capabilities .............................73
11. Acknowledgments ...............................................73
12. References ....................................................73
12.1. Normative References .....................................73
12.2. Informative References ...................................75
1.
Introduction
The CAPWAP protocol [RFC5415] defines an extensible protocol to allow
an Access Controller to manage wireless agnostic Wireless Termination
Points. The CAPWAP protocol itself does not include any specific
wireless technologies; instead, it relies on a binding specification
to extend the technology to a particular wireless technology.
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. Use of CAPWAP
control message fields, new control messages, and message elements
are defined. The minimum required definitions for a binding-specific
Statistics message element, Station message element, and WTP Radio
Information message element are included.
Note that this binding only supports the IEEE 802.11-2007
specification. Of note, this binding does not support the ad hoc
network mode defined in the IEEE 802.11-2007 standard. This
specification also does not cover the use of data frames with the
four-address format, commonly referred to as Wireless Bridges, whose
use is not specified in the IEEE 802.11-2007 standard. This protocol
specification does not currently officially support IEEE 802.11n.
That said, the protocol does allow a WTP to advertise support for an
IEEE 802.11n radio; however, the protocol does not allow for any of
the protocol’s additional features to be configured and/or used. New
IEEE protocol specifications published outside of this document
(e.g., IEEE 802.11v, IEEE 802.11r) are also not supported through
this binding, and in addition to IEEE 802.11n, must be addressed
either through a separate CAPWAP binding, or an update to this
binding.
Calhoun, et al.
Standards Track
[Page 4]
RFC 5416
CAPWAP Protocol Binding for IEEE 802.11
March 2009
In order to address immediate market needs for standards still being
developed by the IEEE 802.11 standards body, the WiFi Alliance
created interim pseudo-standards specifications. Two such
specifications are widely used in the industry, namely the WiFi
Protect Access [WPA] and the WiFi MultiMedia [WMM] specifications.
Given their widespread adoption, this CAPWAP binding requires the use
of these two specifications.
1.1.
Goals
The goals of this CAPWAP protocol binding are to make the
capabilities of the CAPWAP protocol available for use in conjunction
with IEEE 802.11 wireless networks. The capabilities to be made
available can be summarized as:
1. To centralize the authentication and policy enforcement functions
for an IEEE 802.11 wireless network. The AC may also provide
centralized bridging, forwarding, and encryption of user traffic.
Centralization of these functions will enable reduced cost and
higher efficiency by applying the capabilities of network
processing silicon to the wireless network, as in wired LANs.
2. To enable shifting of the
the WTP. This leaves the
control and access in the
computing power available
pressure.
higher-level protocol processing from
time-critical applications of wireless
WTP, making efficient use of the
in WTPs that are subject to severe cost
The CAPWAP protocol binding extensions defined herein apply solely to
the interface between the WTP and the AC. Inter-AC and station-to-AC
communication are strictly outside the scope of this document.
1.2.
Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
1.3.
Terminology
This section contains definitions for terms used frequently
throughout this document. However, many additional definitions can
be found in [IEEE.802-11.2007].
Access Controller (AC): The network entity that provides WTP access
to the network infrastructure in the data plane, control plane,
management plane, or a combination therein.
Calhoun, et al.
Standards Track
[Page 5]
京公网安备 11010802033920号
Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved
评论