draft-ietf-capwap-protocol-binding-ieee80211-03.txt   draft-ietf-capwap-protocol-binding-ieee80211-04.txt 
Network Working Group P. Calhoun, Editor Network Working Group P. Calhoun, Editor
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: September 11, 2007 M. Montemurro, Editor Expires: December 13, 2007 M. Montemurro, Editor
Research In Motion Research In Motion
D. Stanley, Editor D. Stanley, Editor
Aruba Networks Aruba Networks
June 11, 2007
CAPWAP Protocol Binding for IEEE 802.11 CAPWAP Protocol Binding for IEEE 802.11
draft-ietf-capwap-protocol-binding-ieee80211-03 draft-ietf-capwap-protocol-binding-ieee80211-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 2, 2007. This Internet-Draft will expire on December 13, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
Wireless LAN product architectures have evolved from single Wireless LAN product architectures have evolved from single
autonomous access points to systems consisting of a centralized autonomous access points to systems consisting of a centralized
Access Controller (AC) and Wireless Termination Points (WTPs). The Access Controller (AC) and Wireless Termination Points (WTPs). The
general goal of centralized control architectures is to move access general goal of centralized control architectures is to move access
control, including user authentication and authorization, mobility control, including user authentication and authorization, mobility
management and radio management from the single access point to a management and radio management from the single access point to a
centralized controller. centralized controller.
This specification defines the Control And Provisioning of Wireless This specification defines the Control And Provisioning of Wireless
Access Points (CAPWAP) Protocol Binding Specification for use with Access Points (CAPWAP) Protocol Binding Specification for use with
the IEEE 802.11 Wireless Local Area Network protocol. The CAPWAP the IEEE 802.11 Wireless Local Area Network protocol. The CAPWAP
Protocol Specification is defined separately [1]. Protocol Specification is defined separately [3].
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Conventions used in this document . . . . . . . . . . . . 4
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. IEEE 802.11 Binding . . . . . . . . . . . . . . . . . . . . . 6
2.1. Split MAC and Local MAC Functionality . . . . . . . . . . 6
2.1.1. Split MAC . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2. Local MAC . . . . . . . . . . . . . . . . . . . . . . 10
2.2. Roaming Behavior . . . . . . . . . . . . . . . . . . . . . 12
2.3. Group Key Refresh . . . . . . . . . . . . . . . . . . . . 13
2.4. BSSID to WLAN ID Mapping . . . . . . . . . . . . . . . . . 14
2.5. Quality of Service for IEEE 802.11 MAC Management
Messages . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.6. Run State Operation . . . . . . . . . . . . . . . . . . . 14
3. IEEE 802.11 Specific CAPWAP Control Messages . . . . . . . . . 15
3.1. IEEE 802.11 WLAN Configuration Request . . . . . . . . . . 15
3.2. IEEE 802.11 WLAN Configuration Response . . . . . . . . . 16
4. CAPWAP Data Message Bindings . . . . . . . . . . . . . . . . . 17
5. CAPWAP Control Message bindings . . . . . . . . . . . . . . . 19
5.1. Discovery Request Message . . . . . . . . . . . . . . . . 19
5.2. Discovery Response Message . . . . . . . . . . . . . . . . 19
5.3. Primary Discovery Request Message . . . . . . . . . . . . 19
5.4. Primary Discovery Response Message . . . . . . . . . . . . 19
5.5. Join Request Message . . . . . . . . . . . . . . . . . . . 19
5.6. Join Response Message . . . . . . . . . . . . . . . . . . 20
5.7. Configuration Status Message . . . . . . . . . . . . . . . 20
5.8. Configuration Status Response Message . . . . . . . . . . 20
5.9. Configuration Update Request Message . . . . . . . . . . . 21
5.10. Station Configuration Request . . . . . . . . . . . . . . 22
5.11. Change State Event Request . . . . . . . . . . . . . . . . 22
5.12. WTP Event Request . . . . . . . . . . . . . . . . . . . . 22
6. IEEE 802.11 Message Element Definitions . . . . . . . . . . . 23
6.1. IEEE 802.11 Add WLAN . . . . . . . . . . . . . . . . . . . 23
6.2. IEEE 802.11 Antenna . . . . . . . . . . . . . . . . . . . 27
6.3. IEEE 802.11 Assigned WTP BSSID . . . . . . . . . . . . . . 28
6.4. IEEE 802.11 Delete WLAN . . . . . . . . . . . . . . . . . 29
6.5. IEEE 802.11 Direct Sequence Control . . . . . . . . . . . 29
6.6. IEEE 802.11 Information Element . . . . . . . . . . . . . 30
6.7. IEEE 802.11 MAC Operation . . . . . . . . . . . . . . . . 31
6.8. IEEE 802.11 MIC Countermeasures . . . . . . . . . . . . . 33
6.9. IEEE 802.11 Multi-Domain Capability . . . . . . . . . . . 33
6.10. IEEE 802.11 OFDM Control . . . . . . . . . . . . . . . . . 34
6.11. IEEE 802.11 Rate Set . . . . . . . . . . . . . . . . . . . 35
6.12. IEEE 802.11 RSNA Error Report From Station . . . . . . . . 36
6.13. IEEE 802.11 Station . . . . . . . . . . . . . . . . . . . 38
6.14. IEEE 802.11 Station QoS Profile . . . . . . . . . . . . . 39
6.15. IEEE 802.11 Station Session Key . . . . . . . . . . . . . 39
6.16. IEEE 802.11 Statistics . . . . . . . . . . . . . . . . . . 41
6.17. IEEE 802.11 Supported Rates . . . . . . . . . . . . . . . 45
6.18. IEEE 802.11 Tx Power . . . . . . . . . . . . . . . . . . . 45
6.19. IEEE 802.11 Tx Power Level . . . . . . . . . . . . . . . . 46
6.20. IEEE 802.11 Update Station QoS . . . . . . . . . . . . . . 46
6.21. IEEE 802.11 Update WLAN . . . . . . . . . . . . . . . . . 47
6.22. IEEE 802.11 WTP Quality of Service . . . . . . . . . . . . 49
6.23. IEEE 802.11 WTP Radio Configuration . . . . . . . . . . . 50
6.24. IEEE 802.11 WTP Radio Fail Alarm Indication . . . . . . . 52
6.25. IEEE 802.11 WTP Radio Information . . . . . . . . . . . . 52
7. IEEE 802.11 Binding WTP Saved Variables . . . . . . . . . . . 54
7.1. IEEE80211AntennaInfo . . . . . . . . . . . . . . . . . . . 54
7.2. IEEE80211DSControl . . . . . . . . . . . . . . . . . . . . 54
7.3. IEEE80211MACOperation . . . . . . . . . . . . . . . . . . 54
7.4. IEEE80211OFDMControl . . . . . . . . . . . . . . . . . . . 54
7.5. IEEE80211Rateset . . . . . . . . . . . . . . . . . . . . . 54
7.6. IEEE80211TxPower . . . . . . . . . . . . . . . . . . . . . 54
7.7. IEEE80211QoS . . . . . . . . . . . . . . . . . . . . . . . 54
7.8. IEEE80211RadioConfig . . . . . . . . . . . . . . . . . . . 54
8. Technology Specific Message Element Values . . . . . . . . . . 55
9. Security Considerations . . . . . . . . . . . . . . . . . . . 56
9.1. IEEE 802.11 Security . . . . . . . . . . . . . . . . . . . 56
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 59
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 60
12.1. Normative References . . . . . . . . . . . . . . . . . . . 60
12.2. Informational References . . . . . . . . . . . . . . . . . 61
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 62
Intellectual Property and Copyright Statements . . . . . . . . . . 63
1. Introduction 1. Introduction
This specification defines the Control And Provisioning of Wireless This specification defines the Control And Provisioning of Wireless
Access Points (CAPWAP) Protocol Binding Specification for use with Access Points (CAPWAP) Protocol Binding Specification for use with
the IEEE 802.11 Wireless Local Area Network protocol. Use of CAPWAP the IEEE 802.11 Wireless Local Area Network protocol. Use of CAPWAP
control message fields, new control messages and message elements are control message fields, new control messages and message elements are
defined. The minimum required definitions for a binding-specific defined. The minimum required definitions for a binding-specific
Statistics message element, Station message element, and WTP Radio Statistics message element, Station message element, and WTP Radio
Information message element are included. Information message element are included.
skipping to change at page 4, line 40 skipping to change at page 3, line 40
pressure. pressure.
The CAPWAP protocol binding extensions defined herein apply solely to The CAPWAP protocol binding extensions defined herein apply solely to
the interface between the WTP and the AC. Inter-AC and station-to-AC the interface between the WTP and the AC. Inter-AC and station-to-AC
communication are strictly outside the scope of this document. communication are strictly outside the scope of this document.
1.2. Conventions used in this document 1.2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [2]. document are to be interpreted as described in RFC 2119 [1].
1.3. Terminology 1.3. Terminology
Access Controller (AC): The network entity that provides WTP access Access Controller (AC): The network entity that provides WTP access
to the network infrastructure in the data plane, control plane, to the network infrastructure in the data plane, control plane,
management plane, or a combination therein. management plane, or a combination therein.
Basic Service Set (BSS): A set of stations controlled by a single Basic Service Set (BSS): A set of stations controlled by a single
coordination function. coordination function.
skipping to change at page 6, line 20 skipping to change at page 5, line 20
802.11 MAC management frame Quality of Service tagging and Run State 802.11 MAC management frame Quality of Service tagging and Run State
operation. operation.
2.1. Split MAC and Local MAC Functionality 2.1. Split MAC and Local MAC Functionality
The CAPWAP protocol, when used with IEEE 802.11 devices, requires The CAPWAP protocol, when used with IEEE 802.11 devices, requires
specific behavior from the WTP and the AC to support the required specific behavior from the WTP and the AC to support the required
IEEE 802.11 protocol functions. IEEE 802.11 protocol functions.
For both the Split and Local MAC approaches, the CAPWAP functions, as For both the Split and Local MAC approaches, the CAPWAP functions, as
defined in the taxonomy specification [7], reside in the AC. defined in the taxonomy specification [6], reside in the AC.
To provide system component interoperability, the WTP and AC must To provide system component interoperability, the WTP and AC MUST
support 802.11 encryption/decryption at the WTP. The WTP and AC MAY support 802.11 encryption/decryption at the WTP. The WTP and AC MAY
support 802.11 encryption/decryption at the AC. support 802.11 encryption/decryption at the AC.
2.1.1. Split MAC 2.1.1. Split MAC
This section shows the division of labor between the WTP and the AC This section shows the division of labor between the WTP and the AC
in a Split MAC architecture. Figure 1 shows the separation of in a Split MAC architecture. Figure 1 shows the separation of
functionality between CAPWAP components. functionality between CAPWAP components.
Function Location Function Location
skipping to change at page 7, line 7 skipping to change at page 6, line 7
IEEE 802.11 RSN IEEE 802.11 RSN
IEEE 802.1X/EAP AC IEEE 802.1X/EAP AC
RSNA Key Management AC RSNA Key Management AC
IEEE 802.11 Encryption/Decryption WTP/AC IEEE 802.11 Encryption/Decryption WTP/AC
Figure 1: Mapping of 802.11 Functions for Split MAC Architecture Figure 1: Mapping of 802.11 Functions for Split MAC Architecture
In a Split MAC Architecture,the Distribution and Integration services In a Split MAC Architecture,the Distribution and Integration services
reside on the AC, and therefore all user data is tunneled between the reside on the AC, and therefore all user data is tunneled between the
WTP and the AC. As noted above, all real-time IEEE 802.11 services, WTP and the AC. As noted above, all real-time IEEE 802.11 services,
including the beacon and probe response frames, are handled on the including the Beacon and Probe Response frames, are handled on the
WTP. WTP.
All remaining IEEE 802.11 MAC management frames are supported on the All remaining IEEE 802.11 MAC management frames are supported on the
AC, including the Association Request frame which allows the AC to be AC, including the Association Request frame which allows the AC to be
involved in the access policy enforcement portion of the IEEE 802.11 involved in the access policy enforcement portion of the IEEE 802.11
protocol. The IEEE 802.1X and IEEE 802.11 key management function protocol. The IEEE 802.1X and IEEE 802.11 key management function
are also located on the AC. This implies that the AAA client also are also located on the AC. This implies that the AAA client also
resides on the AC. resides on the AC.
While the admission control component of IEEE 802.11 resides on the While the admission control component of IEEE 802.11 resides on the
skipping to change at page 7, line 35 skipping to change at page 6, line 35
Client WTP AC Client WTP AC
Beacon Beacon
<----------------------------- <-----------------------------
Probe Request Probe Request
----------------------------( - )-------------------------> ----------------------------( - )------------------------->
Probe Response Probe Response
<----------------------------- <-----------------------------
802.11 AUTH/Association 802.11 AUTH/Association
<---------------------------------------------------------> <--------------------------------------------------------->
Station Configuration Request[Add Station (Station Message Elements)] Station Configuration Request
<-------------------------> [Add Station (Station Message
Elements)]
<-------------------------->
802.1X Authentication & 802.11 Key Exchange 802.1X Authentication & 802.11 Key Exchange
<---------------------------------------------------------> <--------------------------------------------------------->
Station Configuration Request[Add Station (AES-CCMP, PTK=x)] Station Configuration Request
<-------------------------> [Add Station (AES-CCMP,
PTK=x)]
<-------------------------->
802.11 Action Frames 802.11 Action Frames
<---------------------------------------------------------> <--------------------------------------------------------->
802.11 DATA (1) 802.11 DATA (1)
<---------------------------( - )-------------------------> <---------------------------( - )------------------------->
Figure 2: Split MAC Message Flow Figure 2: Split MAC Message Flow
Figure 2 provides an illustration of the division of labor in a Split Figure 2 provides an illustration of the division of labor in a Split
MAC architecture. In this example, a WLAN has been created that is MAC architecture. In this example, a WLAN has been created that is
configured for IEEE 802.11, using 802.1X based end user configured for IEEE 802.11, using 802.1X based end user
authentication and AES-CCMP link layer encryption. The following authentication and AES-CCMP link layer encryption. The following
process occurs: process occurs:
o The WTP generates the IEEE 802.11 beacon frames, using information o The WTP generates the IEEE 802.11 Beacon frames, using information
provided to it through the IEEE 802.11 Add WLAN (see Section 6.1) provided to it through the IEEE 802.11 Add WLAN (see Section 6.1)
message element, including the RSNIE, which indicates support of message element, including the RSNIE, which indicates support of
802.1X and AES-CCMP. 802.1X and AES-CCMP.
o The WTP processes the probe request frame and responds with a o The WTP processes the Probe Request frame and responds with a
corresponding probe response frame. The probe request frame is corresponding Probe Response frame. The Probe Request frame is
then forwarded to the AC for optional processing. then forwarded to the AC for optional processing.
o The WTP forwards the IEEEE 802.11 Authentication and Association o The WTP forwards the IEEEE 802.11 Authentication and Association
frames to the AC, which is responsible for responding to the frames to the AC, which is responsible for responding to the
client. client.
o Once the association is complete, the AC transmits a Station o Once the association is complete, the AC transmits a Station
Configuration Request message, which includes an Add Station Configuration Request message, which includes an Add Station
message element, to the WTP (see Section 4.5.8 in [1]). In the message element, to the WTP (see Section 4.5.8 in [3]). In the
above example, the WLAN was configured for IEEE 802.1X. above example, the WLAN was configured for IEEE 802.1X.
o If the WTP is providing encryption/decryption services, once the o If the WTP is providing encryption/decryption services, once the
client has completed the IEEE 802.11 key exchange, the AC client has completed the IEEE 802.11 key exchange, the AC
transmits another Station Configuration Request message which transmits another Station Configuration Request message which
includes an Add Station message element, an IEEE 802.11 Station includes an Add Station message element, an IEEE 802.11 Station
message element, an IEEE 802.11 Station Session Key message message element, an IEEE 802.11 Station Session Key message
element and an IEEE 802.11 Information Element message element element and an IEEE 802.11 Information Element message element
which includes the RSNIE to the WTP, delivering the security which includes the RSNIE to the WTP, delivering the security
policy to enforce for the station (in this case AES-CCMP), and the policy to enforce for the station (in this case AES-CCMP), and the
skipping to change at page 9, line 48 skipping to change at page 9, line 4
Figure 3: Population of the IEEE 802.11 MAC header Fields for Figure 3: Population of the IEEE 802.11 MAC header Fields for
Downlink Frames Downlink Frames
When 802.11 encryption/decryption is performed at the AC, the When 802.11 encryption/decryption is performed at the AC, the
MoreFrag bit is populated at the AC. The Pwr Mgmt bit is not MoreFrag bit is populated at the AC. The Pwr Mgmt bit is not
applicable to downlink frames, and is set to 0. Note that the FCS applicable to downlink frames, and is set to 0. Note that the FCS
field is not included in 802.11 frames exchanged between the WTP and field is not included in 802.11 frames exchanged between the WTP and
the AC. Upon sending data frames to the AC, the WTP is responsible the AC. Upon sending data frames to the AC, the WTP is responsible
for validating, and stripping the FCS field. Upon receiving data for validating, and stripping the FCS field. Upon receiving data
frames from the AC, the WTP is responsible for adding the FCS field, frames from the AC, the WTP is responsible for adding the FCS field,
and populating the field as described in [3]. and populating the field as described in [2].
2.1.2. Local MAC 2.1.2. Local MAC
This section shows the division of labor between the WTP and the AC This section shows the division of labor between the WTP and the AC
in a Local MAC architecture. Figure 4 shows the separation of in a Local MAC architecture. Figure 4 shows the separation of
functionality among CAPWAP components. functionality among CAPWAP components.
Function Location Function Location
Distribution Service WTP/AC Distribution Service WTP/AC
Integration Service WTP Integration Service WTP
skipping to change at page 10, line 32 skipping to change at page 9, line 33
Scheduling WTP Scheduling WTP
Queuing WTP Queuing WTP
IEEE 802.11 RSN IEEE 802.11 RSN
IEEE 802.1X/EAP AC IEEE 802.1X/EAP AC
RSNA Key Management AC RSNA Key Management AC
IEEE 802.11 Encryption/Decryption WTP IEEE 802.11 Encryption/Decryption WTP
Figure 4: Mapping of 802.11 Functions for Local AP Architecture Figure 4: Mapping of 802.11 Functions for Local AP Architecture
Since the Distribution and Integration Services exist on the WTP, In the Local MAC mode, the integration service exists on the WTP,
station generated frames are not forwarded to the AC, with the while the distribution service MAY reside on either the WTP or the
exception listed in the following paragraphs. AC. When it resides on the AC, station generated frames are not
forwarded to the AC in their native format, but encapsulated as 802.3
frames.
While the MAC is terminated on the WTP, it is necessary for the AC to While the MAC is terminated on the WTP, it is necessary for the AC to
be aware of mobility events within the WTPs. Thus the WTP MUST be aware of mobility events within the WTPs. Thus the WTP MUST
forward the IEEE 802.11 Association Request frames to the AC. The AC forward the IEEE 802.11 Association Request frames to the AC. The AC
MAY reply with a failed Association Response frame if it deems it MAY reply with a failed Association Response frame if it deems it
necessary, and upon receipt of a failed Association Response frame necessary, and upon receipt of a failed Association Response frame
from the AC, the WTP must send a Disassociation frame to the station. from the AC, the WTP MUST send a Disassociation frame to the station.
The IEEE 802.1X and RSNA Key Management functions reside in the AC. The IEEE 802.1X and RSNA Key Management functions reside in the AC.
Therefore, the WTP MUST forward all IEEE 802.1X/RSNA Key Management Therefore, the WTP MUST forward all IEEE 802.1X/RSNA Key Management
frames to the AC and forward the corresponding responses to the frames to the AC and forward the corresponding responses to the
station. This implies that the AAA client also resides on the AC. station. This implies that the AAA client also resides on the AC.
Note that in the following figure, the use of '( - )' indicates that Note that in the following figure, the use of '( - )' indicates that
processing of the frames is done on the WTP. processing of the frames is done on the WTP.
Client WTP AC Client WTP AC
Beacon Beacon
<----------------------------- <-----------------------------
Probe Probe
<----------------------------> <---------------------------->
802.11 AUTH 802.11 AUTH
<----------------------------- <-----------------------------
802.11 Association 802.11 Association
<---------------------------( - )-------------------------> <---------------------------( - )------------------------->
Station Configuration Request[Add Station (Station Message Elements)] Station Configuration Request[
<-------------------------> Add Station (Station Message
Elements)]
<-------------------------->
802.1X Authentication & 802.11 Key Exchange 802.1X Authentication & 802.11 Key Exchange
<---------------------------------------------------------> <--------------------------------------------------------->
802.11 Action Frames 802.11 Action Frames
<---------------------------------------------------------> <--------------------------------------------------------->
Station Configuration Request[Add Station (AES-CCMP, PTK=x)] Station Configuration Request[
<-------------------------> Add Station (AES-CCMP,
PTK=x)]
<-------------------------->
802.11 DATA 802.11 DATA
<-----------------------------> <----------------------------->
Figure 5: Local MAC Message Flow Figure 5: Local MAC Message Flow
Figure 5 provides an illustration of the division of labor in a Local Figure 5 provides an illustration of the division of labor in a Local
MAC architecture. In this example, a WLAN that is configured for MAC architecture. In this example, a WLAN that is configured for
IEEE 802.11 has been created using AES-CCMP for privacy. The IEEE 802.11 has been created using AES-CCMP for privacy. The
following process occurs: following process occurs:
o The WTP generates the IEEE 802.11 beacon frames, using information o The WTP generates the IEEE 802.11 Beacon frames, using information
provided to it through the Add WLAN (see Section 6.1) message provided to it through the Add WLAN (see Section 6.1) message
element. element.
o The WTP processes a probe request frame and responds with a o The WTP processes a Probe Request frame and responds with a
corresponding probe response frame. corresponding Probe Response frame.
o The WTP forwards the IEEE 802.11 Authentication and Association o The WTP forwards the IEEE 802.11 Authentication and Association
frames to the AC. frames to the AC.
o Once the association is complete, the AC transmits a Station o Once the association is complete, the AC transmits a Station
Configuration Request message, which includes the Add Station Configuration Request message, which includes the Add Station
message element, to the WTP (see Section 10.1 in [1]). In the message element, to the WTP (see Section 10.1 in [3]). In the
above example, the WLAN is configured for IEEE 802.1X, and above example, the WLAN is configured for IEEE 802.1X, and
therefore the '802.1X only' policy bit is enabled. therefore the '802.1X only' policy bit is enabled.
o The WTP forwards all IEEE 802.1X and IEEE 802.11 key exchange o The WTP forwards all IEEE 802.1X and IEEE 802.11 key exchange
messages to the AC for processing. messages to the AC for processing.
o The AC transmits another Station Configuration Request message o The AC transmits another Station Configuration Request message
including an Add Station message element, an IEEE 802.11 Station including an Add Station message element, an IEEE 802.11 Station
message element, an IEEE 802.11 Station Session Key message message element, an IEEE 802.11 Station Session Key message
element and an IEEE 802.11 Information Element message element element and an IEEE 802.11 Information Element message element
which includes the RSNIE to the WTP, stating the security policy which includes the RSNIE to the WTP, stating the security policy
to enforce for the client (in this case AES-CCMP), as well as the to enforce for the client (in this case AES-CCMP), as well as the
encryption key to use. The Add Station message element MAY encryption key to use. The Add Station message element MAY
include a VLAN name, which when present is used by the WTP to include a VLAN name, which when present is used by the WTP to
identify the VLAN on which the user's data frames are to be identify the VLAN on which the user's data frames are to be
bridged. bridged.
o The WTP forwards any IEEE 802.11 Management Action frames received o The WTP forwards any IEEE 802.11 Management Action frames received
to the AC. to the AC.
o The WTP may locally bridge client data frames (and provide the o The WTP MAY locally bridge client data frames (and provide the
necessary encryption and decryption services). The WTP may also necessary encryption and decryption services). The WTP MAY also
tunnel client data frames to the AC, using 802.3 frame tunnel mode tunnel client data frames to the AC, using 802.3 frame tunnel mode
or 802.11 frame tunnel mode. or 802.11 frame tunnel mode.
2.2. Roaming Behavior 2.2. Roaming Behavior
This section expands upon the examples provided in the previous This section expands upon the examples provided in the previous
section, and describes how the CAPWAP control protocol is used to section, and describes how the CAPWAP control protocol is used to
provide secure roaming. provide secure roaming.
Once a client has successfully associated with the network in a Once a client has successfully associated with the network in a
secure fashion, it is likely to attempt to roam to another WTP. secure fashion, it is likely to attempt to roam to another WTP.
Figure 6 shows an example of a currently associated station moving Figure 6 shows an example of a currently associated station moving
from its "Old WTP" to a "new WTP". The figure is valid for multiple from its "Old WTP" to a "New WTP". The figure is valid for multiple
different security policies, including IEEE 802.1X and WPA or WPA2, different security policies, including IEEE 802.1X and WPA or WPA2,
both with key caching (where the IEEE 802.1x exchange would be both with key caching (where the IEEE 802.1x exchange would be
bypassed) and without. bypassed) and without.
Client Old WTP WTP AC Client Old WTP New WTP AC
Association Request/Response Association Request/Response
<--------------------------------------( - )--------------> <--------------------------------------( - )-------------->
Station Configuration Request[Add Station (Station Message Elements)] Station Configuration Request[
Add Station (Station Message
Elements)]
<----------------> <---------------->
802.1X Authentication (if no key cache entry exists) 802.1X Authentication (if no key cache entry exists)
<--------------------------------------( - )--------------> <--------------------------------------( - )-------------->
802.11 4-way Key Exchange 802.11 4-way Key Exchange
<--------------------------------------( - )--------------> <--------------------------------------( - )-------------->
Station Configuration Request[Delete Station] Station Configuration Request
[Delete Station]
<----------------------------------> <---------------------------------->
Station Configuration Request[Add Station (AES-CCMP, PTK=x)] Station Configuration Request
[Add Station (AES-CCMP,
PTK=x)]
<----------------> <---------------->
Figure 6: Client Roaming Example Figure 6: Client Roaming Example
2.3. Group Key Refresh 2.3. Group Key Refresh
Periodically, the Group Key (GTK)for the BSS needs to be updated. Periodically, the Group Key (GTK)for the BSS needs to be updated.
The AC uses an EAPOL-Key frame to update the group key for each STA The AC uses an EAPOL-Key frame to update the group key for each STA
in the BSS. While the AC is updating the GTK, each L2 broadcast in the BSS. While the AC is updating the GTK, each L2 broadcast
frame transmitted to the BSS needs to be duplicated and transmitted frame transmitted to the BSS needs to be duplicated and transmitted
using both the current GTK and the new GTK. Once the GTK update using both the current GTK and the new GTK. Once the GTK update
process has completed, broadcast frames transmitted to the BSS will process has completed, broadcast frames transmitted to the BSS will
skipping to change at page 13, line 30 skipping to change at page 12, line 51
needs to duplicate and transmit broadcast frames using the needs to duplicate and transmit broadcast frames using the
appropriate index to ensure that all STA's in the BSS continue to appropriate index to ensure that all STA's in the BSS continue to
receive broadcast frames. receive broadcast frames.
The Group Key update procedure is shown in the following figure. The The Group Key update procedure is shown in the following figure. The
AC will signal the update to the GTK using an IEEE 802.11 AC will signal the update to the GTK using an IEEE 802.11
Configuration Request message, including an IEEE 802.11 Update WLAN Configuration Request message, including an IEEE 802.11 Update WLAN
message element with the new GTK, its index, the TSC for the Group message element with the new GTK, its index, the TSC for the Group
Key and the Key Status set to 3 (begin GTK update). The AC will then Key and the Key Status set to 3 (begin GTK update). The AC will then
begin updating the GTK for each STA. During this time, the AC (for begin updating the GTK for each STA. During this time, the AC (for
Split MAC) or WTP (for Local MAC) must duplicate broadcast packets Split MAC) or WTP (for Local MAC) MUST duplicate broadcast packets
and transmit them encrypted with both the current and new GTK. When and transmit them encrypted with both the current and new GTK. When
the AC has completed the GTK update to all STA's in the BSS, the AC the AC has completed the GTK update to all STA's in the BSS, the AC
must transmit an IEEE 802.11 Configuration Request message including MUST transmit an IEEE 802.11 Configuration Request message including
an IEEE 802.11 Update WLAN message element containing the new GTK, an IEEE 802.11 Update WLAN message element containing the new GTK,
its index, and the Key Status set to 4 (GTK update complete). its index, and the Key Status set to 4 (GTK update complete).
Client WTP AC Client WTP AC
IEEE 802.11 WLAN Configuration Request ( Update WLAN (GTK, GTK Index, GTK Start, Group TSC) ) IEEE 802.11 WLAN Configuration Request [Update
<---------------------------------------------- WLAN (GTK, GTK Index, GTK Start,
Group TSC) ]
<--------------------------------------------
802.1X EAPoL (GTK Message 1) 802.1X EAPoL (GTK Message 1)
<-------------( - )------------------------------------------- <-------------( - )-------------------------------------------
802.1X EAPoL (GTK Message 2) 802.1X EAPoL (GTK Message 2)
-------------( - )-------------------------------------------> -------------( - )------------------------------------------->
IEEE 802.11 WLAN Configuration Request ( Update WLAN (GTK Index, GTK Complete) ) IEEE 802.11 WLAN Configuration Request [ Update
<--------------------------------------------- WLAN (GTK Index, GTK Complete) ]
<--------------------------------------------
Figure 7: Group Key Update Procedure Figure 7: Group Key Update Procedure
2.4. BSSID to WLAN ID Mapping 2.4. BSSID to WLAN ID Mapping
The CAPWAP protocol binding enables the WTP to assign BSSIDs upon The CAPWAP protocol binding enables the WTP to assign BSSIDs upon
creation of a WLAN (see Section 6.1). While manufacturers are free creation of a WLAN (see Section 6.1). While manufacturers are free
to assign BSSIDs using any arbitrary mechanism, it is advised that to assign BSSIDs using any arbitrary mechanism, it is advised that
where possible the BSSIDs are assigned as a contiguous block. where possible the BSSIDs are assigned as a contiguous block.
skipping to change at page 15, line 10 skipping to change at page 15, line 10
When the AC sends a WLAN Configuration Request message (see When the AC sends a WLAN Configuration Request message (see
Section 3.1) or receives the corresponding WLAN Configuration Section 3.1) or receives the corresponding WLAN Configuration
Response message (see Section 3.2) from the WTP, it remains in the Response message (see Section 3.2) from the WTP, it remains in the
Run state. Run state.
3. IEEE 802.11 Specific CAPWAP Control Messages 3. IEEE 802.11 Specific CAPWAP Control Messages
This section defines CAPWAP Control Messages that are specific to the This section defines CAPWAP Control Messages that are specific to the
IEEE 802.11 binding. Two messages are defined, IEEE 802.11 WLAN IEEE 802.11 binding. Two messages are defined, IEEE 802.11 WLAN
Configuration Request and IEEE 802.11 WLAN Configuration Response. Configuration Request and IEEE 802.11 WLAN Configuration Response.
See Section 4.4 in [1] for CAPWAP Control message definitions and the See Section 4.4 in [3] for CAPWAP Control message definitions and the
derivation of the Message Type value from the IANA Enterprise number. derivation of the Message Type value from the IANA Enterprise number.
The valid message types for IEEE 802.11 specific control messages are The valid message types for IEEE 802.11 specific control messages are
listed below. The IANA Enterprise number used with these messages is listed below. The IANA Enterprise number used with these messages is
13277. 13277.
CAPWAP Control Message Message Type CAPWAP Control Message Message Type
Value Value
IEEE 802.11 WLAN Configuration Request 3398912 IEEE 802.11 WLAN Configuration Request 3398912
skipping to change at page 15, line 33 skipping to change at page 15, line 33
3.1. IEEE 802.11 WLAN Configuration Request 3.1. IEEE 802.11 WLAN Configuration Request
The IEEE 802.11 WLAN Configuration Request is sent by the AC to the The IEEE 802.11 WLAN Configuration Request is sent by the AC to the
WTP in order to change services provided by the WTP. This control WTP in order to change services provided by the WTP. This control
message is used to either create, update or delete a WLAN on the WTP. message is used to either create, update or delete a WLAN on the WTP.
The IEEE 802.11 WLAN Configuration Request is sent as a result of The IEEE 802.11 WLAN Configuration Request is sent as a result of
either some manual admistrative process (e.g., deleting a WLAN), or either some manual admistrative process (e.g., deleting a WLAN), or
automatically to create a WLAN on a WTP. When sent automatically to automatically to create a WLAN on a WTP. When sent automatically to
create a WLAN, this control message is sent after the CAPWAP create a WLAN, this control message is sent after the CAPWAP
Configuration Update Request message (see Section 8.5 in [1]) has Configuration Update Request message (see Section 8.5 in [3]) has
been received by the WTP. been received by the WTP.
Upon receiving this control message, the WTP will modify the Upon receiving this control message, the WTP will modify the
necessary services, and transmit an IEEE 802.11 WLAN Configuration necessary services, and transmit an IEEE 802.11 WLAN Configuration
Response. Response.
A WTP MAY provide service for more than one WLAN, therefore every A WTP MAY provide service for more than one WLAN, therefore every
WLAN is identified through a numerical index. For instance, a WTP WLAN is identified through a numerical index. For instance, a WTP
that is capable of supporting up to 16 SSIDs, could accept up to 16 that is capable of supporting up to 16 SSIDs, could accept up to 16
IEEE 802.11 WLAN Configuration Request messages that include the Add IEEE 802.11 WLAN Configuration Request messages that include the Add
WLAN message element. WLAN message element.
Since the index is the primary identifier for a WLAN, an AC MAY Since the index is the primary identifier for a WLAN, an AC MAY
attempt to ensure that the same WLAN is identified through the same attempt to ensure that the same WLAN is identified through the same
index number on all of its WTPs. An AC that does not follow this index number on all of its WTPs. An AC that does not follow this
approach MUST find some other means of maintaining a WLAN-Identifier- approach MUST find some other means of maintaining a WLAN-Identifier-
to-SSID mapping table. to-SSID mapping table.
The following message elements may be included in the IEEE 802.11 The following message elements MAY be included in the IEEE 802.11
WLAN Configuration Request message. Only one message element MUST be WLAN Configuration Request message. Only one message element MUST be
present. present.
o IEEE 802.11 Add WLAN, see Section 6.1 o IEEE 802.11 Add WLAN, see Section 6.1
o IEEE 802.11 Delete WLAN, see Section 6.4 o IEEE 802.11 Delete WLAN, see Section 6.4
o IEEE 802.11 Update WLAN, see Section 6.21 o IEEE 802.11 Update WLAN, see Section 6.21
The following message element MAY be present. The following message element MAY be present.
skipping to change at page 16, line 34 skipping to change at page 16, line 34
Request message occurred on the WTP. Request message occurred on the WTP.
The following message element MAY be included in the IEEE 802.11 WLAN The following message element MAY be included in the IEEE 802.11 WLAN
Configuration Response message. Configuration Response message.
o IEEE 802.11 Assigned WTP BSSID, see Section 6.3 o IEEE 802.11 Assigned WTP BSSID, see Section 6.3
The following message element MUST be included in the IEEE 802.11 The following message element MUST be included in the IEEE 802.11
WLAN Configuration Response message. WLAN Configuration Response message.
o Result Code, see Section 4.5.31 in [1] o Result Code, see Section 4.5.31 in [3]
4. CAPWAP Data Message Bindings 4. CAPWAP Data Message Bindings
This section describes the CAPWAP Data Message bindings to support This section describes the CAPWAP Data Message bindings to support
transport of IEEE 802.11 frames. transport of IEEE 802.11 frames.
Payload encapsulation: The CAPWAP protocol defines the CAPWAP data Payload encapsulation: The CAPWAP protocol defines the CAPWAP data
message, which is used to encapsulate a wireless payload. For message, which is used to encapsulate a wireless payload. For
IEEE 802.11, the IEEE 802.11 header and payload are encapsulated IEEE 802.11, the IEEE 802.11 header and payload are encapsulated
(excluding the IEEE 802.11 FCS checksum). The IEEE 802.11 FCS (excluding the IEEE 802.11 FCS checksum). The IEEE 802.11 FCS
checksum is handled by the WTP. This allows the WTP to validate checksum is handled by the WTP. This allows the WTP to validate
an IEEE 802.11 frame prior to sending it to the AC. Similarly, an IEEE 802.11 frame prior to sending it to the AC. Similarly,
when an AC wishes to transmit a frame to a station, the WTP when an AC wishes to transmit a frame to a station, the WTP
computes and adds the FCS checksum. computes and adds the FCS checksum.
Optional Wireless Specific Information: The optional CAPWAP header Optional Wireless Specific Information: The optional CAPWAP header
field (see Section 4.2 in [1]) is only used with CAPWAP data field (see Section 4.2 in [3]) is only used with CAPWAP data
messages, and it serves two purposes, depending upon the direction messages, and it serves two purposes, depending upon the direction
of the message. For messages from the WTP to the AC, the field of the message. For messages from the WTP to the AC, the field
uses the format described in the "IEEE 802.11 Frame Info" field uses the format described in the "IEEE 802.11 Frame Info" field
(see below). However, for messages sent by the AC to the WTP, the (see below). However, for messages sent by the AC to the WTP, the
format used is described in the "Destination WLANs" field (also format used is described in the "Destination WLANs" field (also
defined below). defined below).
IEEE 802.11 Frame Info: When an IEEE 802.11 frame is received from a IEEE 802.11 Frame Info: When an IEEE 802.11 frame is received from a
station over the air, it is encapsulated and this field is used to station over the air, it is encapsulated and this field is used to
include radio and PHY specific information associated with the include radio and PHY specific information associated with the
skipping to change at page 20, line 17 skipping to change at page 20, line 17
The following IEEE 802.11 specific message element MUST be included The following IEEE 802.11 specific message element MUST be included
in the CAPWAP Join Response Message. in the CAPWAP Join Response Message.
o IEEE 802.11 WTP Radio Information, see Section 6.25. An IEEE o IEEE 802.11 WTP Radio Information, see Section 6.25. An IEEE
802.11 WTP Radio Information message element MUST be present for 802.11 WTP Radio Information message element MUST be present for
every radio in the WTP. every radio in the WTP.
5.7. Configuration Status Message 5.7. Configuration Status Message
The following IEEE 802.11 specific message elements may be included The following IEEE 802.11 specific message elements MAY be included
in the CAPWAP Configuration Status Message. More than one of each in the CAPWAP Configuration Status Message. More than one of each
message element listed may be included. message element listed MAY be included.
o IEEE 802.11 Antenna, see Section 6.2 o IEEE 802.11 Antenna, see Section 6.2
o IEEE 802.11 Direct Sequence Control, see Section 6.5 o IEEE 802.11 Direct Sequence Control, see Section 6.5
o IEEE 802.11 MAC Operation, see Section 6.7 o IEEE 802.11 MAC Operation, see Section 6.7
o IEEE 802.11 Multi Domain Capability, see Section 6.9 o IEEE 802.11 Multi Domain Capability, see Section 6.9
o IEEE 802.11 OFDM Control, see Section 6.10 o IEEE 802.11 OFDM Control, see Section 6.10
skipping to change at page 20, line 45 skipping to change at page 20, line 45
o IEEE 802.11 TX Power Level, see Section 6.19 o IEEE 802.11 TX Power Level, see Section 6.19
o IEEE 802.11 WTP Radio Configuration, see Section 6.23 o IEEE 802.11 WTP Radio Configuration, see Section 6.23
o IEEE 802.11 WTP Radio Information, see Section 6.25. An IEEE o IEEE 802.11 WTP Radio Information, see Section 6.25. An IEEE
802.11 WTP Radio Information message element MUST be present for 802.11 WTP Radio Information message element MUST be present for
every radio in the WTP. every radio in the WTP.
5.8. Configuration Status Response Message 5.8. Configuration Status Response Message
The following IEEE 802.11 specific message elements may be included The following IEEE 802.11 specific message elements MAY be included
in the CAPWAP Configuration Status Response Message. More than one in the CAPWAP Configuration Status Response Message. More than one
of each message element listed may be included. of each message element listed MAY be included.
o IEEE 802.11 Antenna, see Section 6.2 o IEEE 802.11 Antenna, see Section 6.2
o IEEE 802.11 Direct Sequence Control, see Section 6.5 o IEEE 802.11 Direct Sequence Control, see Section 6.5
o IEEE 802.11 MAC Operation, see Section 6.7 o IEEE 802.11 MAC Operation, see Section 6.7
o IEEE 802.11 Multi Domain Capability, see Section 6.9 o IEEE 802.11 Multi Domain Capability, see Section 6.9
o IEEE 802.11 OFDM Control, see Section 6.10 o IEEE 802.11 OFDM Control, see Section 6.10
skipping to change at page 21, line 24 skipping to change at page 21, line 24
o IEEE 802.11 Supported Rates, see Section 6.17 o IEEE 802.11 Supported Rates, see Section 6.17
o IEEE 802.11 Tx Power, see Section 6.18 o IEEE 802.11 Tx Power, see Section 6.18
o IEEE 802.11 WTP Quality of Service, see Section 6.22 o IEEE 802.11 WTP Quality of Service, see Section 6.22
o IEEE 802.11 WTP Radio Configuration, see Section 6.23 o IEEE 802.11 WTP Radio Configuration, see Section 6.23
5.9. Configuration Update Request Message 5.9. Configuration Update Request Message
The following IEEE 802.11 specific message elements may be included The following IEEE 802.11 specific message elements MAY be included
in the CAPWAP Configuration Update Request Message. More than one of in the CAPWAP Configuration Update Request Message. More than one of
each message element listed may be included. each message element listed MAY be included.
o IEEE 802.11 Antenna, see Section 6.2 o IEEE 802.11 Antenna, see Section 6.2
o IEEE 802.11 Direct Sequence Control, see Section 6.5 o IEEE 802.11 Direct Sequence Control, see Section 6.5
o IEEE 802.11 MAC Operation, see Section 6.7 o IEEE 802.11 MAC Operation, see Section 6.7
o IEEE 802.11 Multi Domain Capability, see Section 6.9 o IEEE 802.11 Multi Domain Capability, see Section 6.9
o IEEE 802.11 OFDM Control, see Section 6.10 o IEEE 802.11 OFDM Control, see Section 6.10
skipping to change at page 22, line 9 skipping to change at page 22, line 9
o IEEE 802.11 Tx Power, see Section 6.18 o IEEE 802.11 Tx Power, see Section 6.18
o IEEE 802.11 WTP Quality of Service, see Section 6.22 o IEEE 802.11 WTP Quality of Service, see Section 6.22
o IEEE 802.11 WTP Radio Configuration, see Section 6.23 o IEEE 802.11 WTP Radio Configuration, see Section 6.23
5.10. Station Configuration Request 5.10. Station Configuration Request
The following IEEE 802.11 specific message elements MAY included in The following IEEE 802.11 specific message elements MAY included in
the CAPWAP Station Configuration Request message. More than one of the CAPWAP Station Configuration Request message. More than one of
each message element listed may be included. each message element listed MAY be included.
o IEEE 802.11 Station, see Section 6.13 o IEEE 802.11 Station, see Section 6.13
o IEEE 802.11 Station Session Key, see Section 6.15 o IEEE 802.11 Station Session Key, see Section 6.15
o Station QoS Profile, see Section 6.14 o Station QoS Profile, see Section 6.14
5.11. Change State Event Request 5.11. Change State Event Request
The following IEEE 802.11 specific message elements MAY included in The following IEEE 802.11 specific message elements MAY included in
the CAPWAP Station Configuration Request message. the CAPWAP Station Configuration Request message.
o IEEE 802.11 WTP Radio Fail Alarm Indication, see Section 6.24 o IEEE 802.11 WTP Radio Fail Alarm Indication, see Section 6.24
5.12. WTP Event Request 5.12. WTP Event Request
The following IEEE 802.11 specific message elements MAY be included The following IEEE 802.11 specific message elements MAY be included
in the CAPWAP WTP Event Request message.More than one of each message in the CAPWAP WTP Event Request message.More than one of each message
element listed may be included. element listed MAY be included.
o IEEE 802.11 MIC Countermeasures, see Section 6.8 o IEEE 802.11 MIC Countermeasures, see Section 6.8
o IEEE 802.11 RSNA Error Report From Station, see Section 6.12 o IEEE 802.11 RSNA Error Report From Station, see Section 6.12
o IEEE 802.11 Statistics, see Section 6.16 o IEEE 802.11 Statistics, see Section 6.16
6. IEEE 802.11 Message Element Definitions 6. IEEE 802.11 Message Element Definitions
The following IEEE 802.11 specific message elements are defined in The following IEEE 802.11 specific message elements are defined in
skipping to change at page 25, line 37 skipping to change at page 25, line 37
Key Length: A 16-bit value representing the length of the Key Key Length: A 16-bit value representing the length of the Key
field. field.
Key: A 32 byte Session Key to use to provide data privacy. For Key: A 32 byte Session Key to use to provide data privacy. For
encryption schemes that employ a separate encryption key for encryption schemes that employ a separate encryption key for
unicast and multicast traffic, the key included here only applies unicast and multicast traffic, the key included here only applies
to multicast frames, and the cipher suite is specified in an to multicast frames, and the cipher suite is specified in an
accompanied RSN Information Element. In these scenarios, the key accompanied RSN Information Element. In these scenarios, the key
and cipher information is communicated via the Add Station message and cipher information is communicated via the Add Station message
element, see Section 4.5.8 in [1] and the IEEE 802.11 Station element, see Section 4.5.8 in [3] and the IEEE 802.11 Station
Session Key message element, see Section 6.15. Session Key message element, see Section 6.15.
Group TSC A 48-bit value containing the Transmit Sequence Counter Group TSC A 48-bit value containing the Transmit Sequence Counter
for the updated group key. The WTP will set the TSC for for the updated group key. The WTP will set the TSC for
broadcast/multicast frames to this value for the updated group broadcast/multicast frames to this value for the updated group
key. key.
QOS: An 8-bit value specifying the default QOS policy for the WTP QOS: An 8-bit value specifying the default QOS policy for the WTP
to apply to network traffic received for a non-WMM enabled STA. to apply to network traffic received for a non-WMM enabled STA.
skipping to change at page 26, line 25 skipping to change at page 26, line 25
The following values are supported: The following values are supported:
0 - Open System 0 - Open System
1 - WEP Shared Key 1 - WEP Shared Key
MAC Mode: This field specifies whether the WTP should support the MAC Mode: This field specifies whether the WTP should support the
WLAN in Local or Split MAC modes. Note that the AC MUST NOT WLAN in Local or Split MAC modes. Note that the AC MUST NOT
request a mode of operation that was not advertised by the WTP request a mode of operation that was not advertised by the WTP
during the discovery process (see Section 4.4.42 in [1]). The during the discovery process (see Section 4.4.42 in [3]). The
following values are supported: following values are supported:
0 - Local-MAC: Service for the WLAN is to be provided in Local 0 - Local-MAC: Service for the WLAN is to be provided in Local
MAC mode. MAC mode.
1 - Split-MAC: Service for the WLAN is to be provided in Split 1 - Split-MAC: Service for the WLAN is to be provided in Split
MAC mode. MAC mode.
Tunnel Mode: This field specifies the frame tunneling type to be Tunnel Mode: This field specifies the frame tunneling type to be
used for 802.11 data frames from all stations associated with the used for 802.11 data frames from all stations associated with the
WLAN. The AC MUST NOT request a mode of operation that was not WLAN. The AC MUST NOT request a mode of operation that was not
advertised by the WTP during the discovery process (see Section advertised by the WTP during the discovery process (see Section
4.4.40 in [1]). IEEE 802.11 managment frames SHALL be tunneled 4.4.40 in [3]). IEEE 802.11 managment frames SHALL be tunneled
using 802.11 Tunnel mode. The following values are supported: using 802.11 Tunnel mode. The following values are supported:
0 - Local Bridging: All user traffic is to be locally bridged. 0 - Local Bridging: All user traffic is to be locally bridged.
1 - 802.3 Tunnel: All user traffic is to be tunneled to the AC 1 - 802.3 Tunnel: All user traffic is to be tunneled to the AC
in 802.3 format (see Section 4.2 in [1]). in 802.3 format (see Section 4.2 in [3]).
2 - 802.11 Tunnel: All user traffic is to be tunneled to the AC 2 - 802.11 Tunnel: All user traffic is to be tunneled to the AC
in 802.11 format. in 802.11 format.
Supress SSID: A boolean indicating whether the SSID is to be Supress SSID: A boolean indicating whether the SSID is to be
advertised by the WTP. A value of zero supresses the SSID in the advertised by the WTP. A value of zero supresses the SSID in the
802.11 Beacon and Probe Response frames, while a value of one will 802.11 Beacon and Probe Response frames, while a value of one will
cause the WTP to populate the field. cause the WTP to populate the field.
SSID: The SSID attribute is the service set identifier that will be SSID: The SSID attribute is the service set identifier that will be
skipping to change at page 27, line 36 skipping to change at page 27, line 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1025 for IEEE 802.11 Antenna Type: 1025 for IEEE 802.11 Antenna
Length: >= 5 Length: >= 5
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Diversity: An 8-bit value specifying whether the antenna is to Diversity: An 8-bit value specifying whether the antenna is to
provide receive diversity. The value of this field is the same as provide receive diversity. The value of this field is the same as
the IEEE 802.11 dot11DiversitySelectionRx MIB element, see [3]. the IEEE 802.11 dot11DiversitySelectionRx MIB element, see [2].
The following values are supported: The following values are supported:
0 - Disabled 0 - Disabled
1 - Enabled (may only be true if the antenna can be used as a 1 - Enabled (may only be true if the antenna can be used as a
receive antenna) receive antenna)
Combiner: An 8-bit value specifying the combiner selection. The Combiner: An 8-bit value specifying the combiner selection. The
following values are supported: following values are supported:
1 - Sectorized (Left) 1 - Sectorized (Left)
2 - Sectorized (Right) 2 - Sectorized (Right)
3 - Omni 3 - Omni
4 - MIMO 4 - MIMO
Antenna Count: An 8-bit value specifying the number of Antenna Antenna Count: An 8-bit value specifying the number of Antenna
Selection fields. This value should be the same as the one found Selection fields. This value SHOULD be the same as the one found
in the IEEE 802.11 dot11CurrentTxAntenna MIB element (see [3]). in the IEEE 802.11 dot11CurrentTxAntenna MIB element (see [2]).
Antenna Selection: One 8-bit antenna configuration value per Antenna Selection: One 8-bit antenna configuration value per
antenna in the WTP. The following values are supported: antenna in the WTP. The following values are supported:
1 - Internal Antenna 1 - Internal Antenna
2 - External Antenna 2 - External Antenna
6.3. IEEE 802.11 Assigned WTP BSSID 6.3. IEEE 802.11 Assigned WTP BSSID
skipping to change at page 30, line 7 skipping to change at page 30, line 7
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Reserved: All implementations complying with this protocol MUST set Reserved: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the protocol to zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
Current Channel: This attribute contains the current operating Current Channel: This attribute contains the current operating
frequency channel of the DSSS PHY. This value comes from the IEEE frequency channel of the DSSS PHY. This value comes from the IEEE
802.11 dot11CurrentChannel MIB element (see [3]). 802.11 dot11CurrentChannel MIB element (see [2]).
Current CCA: The current CCA method in operation, whose value can Current CCA: The current CCA method in operation, whose value can
be found in the IEEE 802.11 dot11CCAModeSupported MIB element (see be found in the IEEE 802.11 dot11CCAModeSupported MIB element (see
[3]). Valid values are: [2]). Valid values are:
1 - energy detect only (edonly) 1 - energy detect only (edonly)
2 - carrier sense only (csonly) 2 - carrier sense only (csonly)
4 - carrier sense and energy detect (edandcs) 4 - carrier sense and energy detect (edandcs)
8 - carrier sense with timer (cswithtimer) 8 - carrier sense with timer (cswithtimer)
16 - high rate carrier sense and energy detect (hrcsanded) 16 - high rate carrier sense and energy detect (hrcsanded)
Energy Detect Threshold: The current Energy Detect Threshold being Energy Detect Threshold: The current Energy Detect Threshold being
used by the DSSS PHY. The value can be found in the IEEE 802.11 used by the DSSS PHY. The value can be found in the IEEE 802.11
dot11EDThreshold MIB element (see [3]). dot11EDThreshold MIB element (see [2]).
6.6. IEEE 802.11 Information Element 6.6. IEEE 802.11 Information Element
The IEEE 802.11 Information Element is used to communicate any IE The IEEE 802.11 Information Element is used to communicate any IE
defined in the IEEE 802.11 protocol. The data field contains the raw defined in the IEEE 802.11 protocol. The data field contains the raw
IE as it would be included within an IEEE 802.11 MAC management IE as it would be included within an IEEE 802.11 MAC management
message. message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 30, line 48 skipping to change at page 30, line 48
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1029 for IEEE 802.11 Information Element Type: 1029 for IEEE 802.11 Information Element
Length: >= 2 Length: >= 2
Radio ID: An 8-bit value representing the radio. Radio ID: An 8-bit value representing the radio.
WLAN ID: An 8-bit value specifying the WLAN Identifier. WLAN ID: An 8-bit value specifying the WLAN Identifier.
B: When set, the WTP is to include the information element in B: When set, the WTP is to include the information element in IEEE
beacons associated with the WLAN. 802.11 Beacons associated with the WLAN.
P: When set, the WTP is to include the information element in probe P: When set, the WTP is to include the information element in Probe
responses associated with the WLAN. Responses associated with the WLAN.
Flags: All implementations complying with this protocol MUST set to Flags: All implementations complying with this protocol MUST set to
zero any bits that are reserved in the version of the protocol zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
Info Element: The IEEE 802.11 Information Element, which includes Info Element: The IEEE 802.11 Information Element, which includes
the type, length and value field. the type, length and value field.
6.7. IEEE 802.11 MAC Operation 6.7. IEEE 802.11 MAC Operation
skipping to change at page 32, line 9 skipping to change at page 32, line 9
exchange sequence where the MPDU is of type Data or Management, exchange sequence where the MPDU is of type Data or Management,
the MPDU has an individual address in the Address1 field, and the the MPDU has an individual address in the Address1 field, and the
length of the MPDU is greater than this threshold. Setting this length of the MPDU is greater than this threshold. Setting this
attribute to be larger than the maximum MSDU size MUST have the attribute to be larger than the maximum MSDU size MUST have the
effect of turning off the RTS/CTS handshake for frames of Data or effect of turning off the RTS/CTS handshake for frames of Data or
Management type transmitted by this STA. Setting this attribute Management type transmitted by this STA. Setting this attribute
to zero MUST have the effect of turning on the RTS/CTS handshake to zero MUST have the effect of turning on the RTS/CTS handshake
for all frames of Data or Management type transmitted by this STA. for all frames of Data or Management type transmitted by this STA.
The default value of this attribute MUST be 2347. The value of The default value of this attribute MUST be 2347. The value of
this field comes from the IEEE 802.11 dot11RTSThreshold MIB this field comes from the IEEE 802.11 dot11RTSThreshold MIB
element, (see [3]). element, (see [2]).
Short Retry: This attribute indicates the maximum number of Short Retry: This attribute indicates the maximum number of
transmission attempts of a frame, the length of which is less than transmission attempts of a frame, the length of which is less than
or equal to RTSThreshold, that MUST be made before a failure or equal to RTSThreshold, that MUST be made before a failure
condition is indicated. The default value of this attribute MUST condition is indicated. The default value of this attribute MUST
be 7. The value of this field comes from the IEEE 802.11 be 7. The value of this field comes from the IEEE 802.11
dot11ShortRetryLimit MIB element, (see [3]). dot11ShortRetryLimit MIB element, (see [2]).
Long Retry: This attribute indicates the maximum number of Long Retry: This attribute indicates the maximum number of
transmission attempts of a frame, the length of which is greater transmission attempts of a frame, the length of which is greater
than dot11RTSThreshold, that MUST be made before a failure than dot11RTSThreshold, that MUST be made before a failure
condition is indicated. The default value of this attribute MUST condition is indicated. The default value of this attribute MUST
be 4. The value of this field comes from the IEEE 802.11 be 4. The value of this field comes from the IEEE 802.11
dot11LongRetryLimit MIB element, (see [3]). dot11LongRetryLimit MIB element, (see [2]).
Fragmentation Threshold: This attribute specifies the current Fragmentation Threshold: This attribute specifies the current
maximum size, in octets, of the MPDU that MAY be delivered to the maximum size, in octets, of the MPDU that MAY be delivered to the
PHY. An MSDU MUST be broken into fragments if its size exceeds PHY. An MSDU MUST be broken into fragments if its size exceeds
the value of this attribute after adding MAC headers and trailers. the value of this attribute after adding MAC headers and trailers.
An MSDU or MMPDU MUST be fragmented when the resulting frame has An MSDU or MMPDU MUST be fragmented when the resulting frame has
an individual address in the Address1 field, and the length of the an individual address in the Address1 field, and the length of the
frame is larger than this threshold. The default value for this frame is larger than this threshold. The default value for this
attribute MUST be the lesser of 2346 or the aMPDUMaxLength of the attribute MUST be the lesser of 2346 or the aMPDUMaxLength of the
attached PHY and MUST never exceed the lesser of 2346 or the attached PHY and MUST never exceed the lesser of 2346 or the
aMPDUMaxLength of the attached PHY. The value of this attribute aMPDUMaxLength of the attached PHY. The value of this attribute
MUST never be less than 256. The value of this field comes from MUST never be less than 256. The value of this field comes from
the IEEE 802.11 dot11FragmentationThreshold MIB element, (see the IEEE 802.11 dot11FragmentationThreshold MIB element, (see
[3]). [2]).
Tx MSDU Lifetime: This attribute speficies the elapsed time in TU, Tx MSDU Lifetime: This attribute speficies the elapsed time in TU,
after the initial transmission of an MSDU, after which further after the initial transmission of an MSDU, after which further
attempts to transmit the MSDU MUST be terminated. The default attempts to transmit the MSDU MUST be terminated. The default
value of this attribute MUST be 512. The value of this field value of this attribute MUST be 512. The value of this field
comes from the IEEE 802.11 dot11MaxTransmitMSDULifetime MIB comes from the IEEE 802.11 dot11MaxTransmitMSDULifetime MIB
element, (see [3]). element, (see [2]).
Rx MSDU Lifetime: This attribute specifies the elapsed time in TU, Rx MSDU Lifetime: This attribute specifies the elapsed time in TU,
after the initial reception of a fragmented MMPDU or MSDU, after after the initial reception of a fragmented MMPDU or MSDU, after
which further attempts to reassemble the MMPDU or MSDU MUST be which further attempts to reassemble the MMPDU or MSDU MUST be
terminated. The default value MUST be 512. The value of this terminated. The default value MUST be 512. The value of this
field comes from the IEEE 802.11 dot11MaxReceiveLifetime MIB field comes from the IEEE 802.11 dot11MaxReceiveLifetime MIB
element, (see [3]). element, (see [2]).
6.8. IEEE 802.11 MIC Countermeasures 6.8. IEEE 802.11 MIC Countermeasures
The IEEE 802.11 MIC Countermeasures message element is sent by the The IEEE 802.11 MIC Countermeasures message element is sent by the
WTP to the AC to indicate the occurrence of a MIC failure. For more WTP to the AC to indicate the occurrence of a MIC failure. For more
information on MIC failure events, see the information on MIC failure events, see the
dot11RSNATKIPCounterMeasuresInvoked MIB element definition in [3]. dot11RSNATKIPCounterMeasuresInvoked MIB element definition in [2].
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | WLAN ID | MAC Address | | Radio ID | WLAN ID | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1031 for IEEE 802.11 MIC Countermeasures Type: 1031 for IEEE 802.11 MIC Countermeasures
skipping to change at page 34, line 18 skipping to change at page 34, line 18
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Reserved: All implementations complying with this protocol MUST set Reserved: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the protocol to zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
First Channnel #: This attribute indicates the value of the lowest First Channnel #: This attribute indicates the value of the lowest
channel number in the subband for the associated domain country channel number in the subband for the associated domain country
string. The value of this field comes from the IEEE 802.11 string. The value of this field comes from the IEEE 802.11
dot11FirstChannelNumber MIB element (see [3]). dot11FirstChannelNumber MIB element (see [2]).
Number of Channels: This attribute indicates the value of the total Number of Channels: This attribute indicates the value of the total
number of channels allowed in the subband for the associated number of channels allowed in the subband for the associated
domain country string. The value of this field comes from the domain country string. The value of this field comes from the
IEEE 802.11 dot11NumberofChannels MIB element (see [3]). IEEE 802.11 dot11NumberofChannels MIB element (see [2]).
Max Tx Power Level: This attribute indicates the maximum transmit Max Tx Power Level: This attribute indicates the maximum transmit
power, in dBm, allowed in the subband for the associated domain power, in dBm, allowed in the subband for the associated domain
country string. The value of this field comes from the IEEE country string. The value of this field comes from the IEEE
802.11 dot11MaximumTransmitPowerLevel MIB element (see [3]). 802.11 dot11MaximumTransmitPowerLevel MIB element (see [2]).
6.10. IEEE 802.11 OFDM Control 6.10. IEEE 802.11 OFDM Control
The IEEE 802.11 OFDM Control message element is a bi-directional The IEEE 802.11 OFDM Control message element is a bi-directional
element. When sent by the WTP, it contains the current state. When element. When sent by the WTP, it contains the current state. When
sent by the AC, the WTP MUST adhere to the received values. This sent by the AC, the WTP MUST adhere to the received values. This
message element is only used for 802.11a radios and contains the message element is only used for 802.11a radios and contains the
following fields: following fields:
0 1 2 3 0 1 2 3
skipping to change at page 35, line 13 skipping to change at page 35, line 13
Length: 8 Length: 8
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Reserved: All implementations complying with this protocol MUST set Reserved: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the protocol to zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
Current Channel: This attribute contains the current operating Current Channel: This attribute contains the current operating
frequency channel of the OFDM PHY. The value of this field comes frequency channel of the OFDM PHY. The value of this field comes
from the IEEE 802.11 dot11CurrentFrequency MIB element (see [3]). from the IEEE 802.11 dot11CurrentFrequency MIB element (see [2]).
Band Supported: The capability of the OFDM PHY implementation to Band Supported: The capability of the OFDM PHY implementation to
operate in the three U-NII bands. The value of this field comes operate in the three U-NII bands. The value of this field comes
from the IEEE 802.11 dot11FrequencyBandsSupported MIB element (see from the IEEE 802.11 dot11FrequencyBandsSupported MIB element (see
[3]), coded as an integer value of a three bit field as follows: [2]), coded as an integer value of a three bit field as follows:
Bit 0 - capable of operating in the lower (5.15-5.25 GHz) U-NII Bit 0 - capable of operating in the lower (5.15-5.25 GHz) U-NII
band band
Bit 1 - capable of operating in the middle (5.25-5.35 GHz) U-NII Bit 1 - capable of operating in the middle (5.25-5.35 GHz) U-NII
band band
Bit 2 - capable of operating in the upper (5.725-5.825 GHz) U-NII Bit 2 - capable of operating in the upper (5.725-5.825 GHz) U-NII
band band
For example, for an implementation capable of operating in the For example, for an implementation capable of operating in the
lower and mid bands this attribute would take the value 3. lower and mid bands this attribute would take the value 3.
TI Threshold: The Threshold being used to detect a busy medium TI Threshold: The Threshold being used to detect a busy medium
(frequency). CCA MUST report a busy medium upon detecting the (frequency). CCA MUST report a busy medium upon detecting the
RSSI above this threshold. The value of this field comes from the RSSI above this threshold. The value of this field comes from the
IEEE 802.11 dot11TIThreshold MIB element (see [3]). IEEE 802.11 dot11TIThreshold MIB element (see [2]).
6.11. IEEE 802.11 Rate Set 6.11. IEEE 802.11 Rate Set
The rate set message element value is sent by the AC and contains the The rate set message element value is sent by the AC and contains the
supported operational rates. It contains the following fields. supported operational rates. It contains the following fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Rate Set... | Radio ID | Rate Set...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1034 for IEEE 802.11 Rate Set Type: 1034 for IEEE 802.11 Rate Set
Length: >= 3 Length: >= 3
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Rate Set: The AC generates the Rate Set that the WTP is to include Rate Set: The AC generates the Rate Set that the WTP is to include
in it's Beacon and Probe messages. The length of this field is in its Beacon and Probe messages. The length of this field is
between 2 and 8 bytes. The value of this field comes from the between 2 and 8 bytes. The value of this field comes from the
IEEE 802.11 dot11OperationalRateSet MIB element (see [3]). IEEE 802.11 dot11OperationalRateSet MIB element (see [2]).
6.12. IEEE 802.11 RSNA Error Report From Station 6.12. IEEE 802.11 RSNA Error Report From Station
The IEEE 802.11 RSN Error Report From Station message element is used The IEEE 802.11 RSN Error Report From Station message element is used
by a WTP to send RSN error reports to the AC. The WTP does not need by a WTP to send RSN error reports to the AC. The WTP does not need
to transmit any reports that do not include any failures. The fields to transmit any reports that do not include any failures. The fields
from this message element come from the IEEE 802.11 from this message element come from the IEEE 802.11
Dot11RSNAStatsEntry table, see [3]. Dot11RSNAStatsEntry table, see [2].
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client MAC Address | | Client MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client MAC Address | BSSID | | Client MAC Address | BSSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BSSID | | BSSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 37, line 25 skipping to change at page 37, line 25
WLAN ID: The WLAN ID on which the RSNA failures are being reported. WLAN ID: The WLAN ID on which the RSNA failures are being reported.
Reserved: All implementations complying with this protocol MUST set Reserved: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the protocol to zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
TKIP ICV Errors: A 32-bit value representing the number of TKIP ICV TKIP ICV Errors: A 32-bit value representing the number of TKIP ICV
errors encountered when decrypting packets from the station. The errors encountered when decrypting packets from the station. The
value of this field comes from the IEEE 802.11 value of this field comes from the IEEE 802.11
dot11RSNAStatsTKIPICVErrors MIB element (see [3]). dot11RSNAStatsTKIPICVErrors MIB element (see [2]).
TKIP Local MIC Failures: A 32-bit value representing the number of TKIP Local MIC Failures: A 32-bit value representing the number of
MIC failures encountered when checking the integrity of packets MIC failures encountered when checking the integrity of packets
received from the station. The value of this field comes from the received from the station. The value of this field comes from the
IEEE 802.11 dot11RSNAStatsTKIPLocalMICFailures MIB element (see IEEE 802.11 dot11RSNAStatsTKIPLocalMICFailures MIB element (see
[3]). [2]).
TKIP Remote MIC Failures: A 32-bit value representing the number of TKIP Remote MIC Failures: A 32-bit value representing the number of
MIC failures reported by the station encountered (possibly via the MIC failures reported by the station encountered (possibly via the
EAPOL-Key frame). The value of this field comes from the IEEE EAPOL-Key frame). The value of this field comes from the IEEE
802.11 dot11RSNAStatsTKIPRemoteMICFailures MIB element (see [3]). 802.11 dot11RSNAStatsTKIPRemoteMICFailures MIB element (see [2]).
CCMP Replays: A 32-bit value representing the number of CCMP MPDUs CCMP Replays: A 32-bit value representing the number of CCMP MPDUs
discarded by the replay detection mechanism. The value of this discarded by the replay detection mechanism. The value of this
field comes from the IEEE 802.11 dot11RSNACCMPReplays MIB element field comes from the IEEE 802.11 dot11RSNACCMPReplays MIB element
(see [3]). (see [2]).
CCMP Decrypt Errors: A 32-bit value representing the number of CCMP CCMP Decrypt Errors: A 32-bit value representing the number of CCMP
MDPUs discarded by the decryption algorithm. The value of this MDPUs discarded by the decryption algorithm. The value of this
field comes from the IEEE 802.11 dot11RSNACCMPDecryptErrors MIB field comes from the IEEE 802.11 dot11RSNACCMPDecryptErrors MIB
element (see [3]). element (see [2]).
TKIP Replays: A 32-bit value representing the number of TKIP TKIP Replays: A 32-bit value representing the number of TKIP
Replays detected in frames received from the station. The value Replays detected in frames received from the station. The value
of this field comes from the IEEE 802.11 dot11RSNAStatsTKIPReplays of this field comes from the IEEE 802.11 dot11RSNAStatsTKIPReplays
MIB element (see [3]). MIB element (see [2]).
6.13. IEEE 802.11 Station 6.13. IEEE 802.11 Station
The IEEE 802.11 Station message element accompanies the Add Station The IEEE 802.11 Station message element accompanies the Add Station
message element, and is used to deliver IEEE 802.11 station policy message element, and is used to deliver IEEE 802.11 station policy
from the AC to the WTP. from the AC to the WTP.
The latest IEEE 802.11 Station message element overrides any The latest IEEE 802.11 Station message element overrides any
previously received message elements. previously received message elements.
skipping to change at page 39, line 6 skipping to change at page 39, line 6
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
MAC Address: The station's MAC Address MAC Address: The station's MAC Address
Capabilities: A 16-bit field containing the IEEE 802.11 Capabilities: A 16-bit field containing the IEEE 802.11
Capabilities Information Field to use with the station. Capabilities Information Field to use with the station.
WLAN ID: An 8-bit value specifying the WLAN Identifier WLAN ID: An 8-bit value specifying the WLAN Identifier
Supported Rates: The variable length field containing the supported Supported Rates: The variable length field containing the supported
rates to be used with the station, as found in the IEEE 802.11 rates to be used with the station, as found in the IEEE 802.11
dot11OperationalRateSet MIB element (see [3]). dot11OperationalRateSet MIB element (see [2]).
6.14. IEEE 802.11 Station QoS Profile 6.14. IEEE 802.11 Station QoS Profile
The IEEE 802.11 Station QoS Profile message element contains the The IEEE 802.11 Station QoS Profile message element contains the
maximum IEEE 802.11e priority tag that may be used by the station. maximum IEEE 802.11e priority tag that may be used by the station.
Any packet received that exceeds the value encoded in this message Any packet received that exceeds the value encoded in this message
element must either be dropped or tagged using the maximum value element MUST either be dropped or tagged using the maximum value
permitted by to the user. The priority tag must be between zero (0) permitted by to the user. The priority tag MUST be between zero (0)
and seven (7). This message element MUST NOT be present without the and seven (7). This message element MUST NOT be present without the
IEEE 802.11 Station (see Section 6.13) message element IEEE 802.11 Station (see Section 6.13) message element
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | 802.1P Precedence Tag | | MAC Address | 802.1P Precedence Tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 40, line 7 skipping to change at page 40, line 7
The RSN information element MUST sent along with the IEEE 802.11 The RSN information element MUST sent along with the IEEE 802.11
Station Session Key in order to instruct the WTP on the usage of the Station Session Key in order to instruct the WTP on the usage of the
Key field. The AKM field of the RSM information element is used by Key field. The AKM field of the RSM information element is used by
the WTP to identify the authentication protocol. the WTP to identify the authentication protocol.
If the IEEE 802.11 Station Session Key message element's AKM-Only bit If the IEEE 802.11 Station Session Key message element's AKM-Only bit
is set, the WTP MUST drop all IEEE 802.11 packets that are not part is set, the WTP MUST drop all IEEE 802.11 packets that are not part
of the AKM (e.g., EAP). Note that AKM-Only is MAY be set while an of the AKM (e.g., EAP). Note that AKM-Only is MAY be set while an
encryption key is in force, requiring that the AKM packets be encryption key is in force, requiring that the AKM packets be
encrypted. Once the station has successfully completed encrypted. Once the station has successfully completed
authentication via the AKM, the AC must send a new Add Station authentication via the AKM, the AC MUST send a new Add Station
message element to remove the AKM-Only restriction, and optionally message element to remove the AKM-Only restriction, and optionally
push the session key down to the WTP. push the session key down to the WTP.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |A|C| Flags | | MAC Address |A|C| Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 43, line 18 skipping to change at page 43, line 18
Radio ID: An 8-bit value representing the radio. Radio ID: An 8-bit value representing the radio.
Reserved: All implementations complying with this protocol MUST set Reserved: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the protocol to zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
Tx Fragment Count: A 32-bit value representing the number of Tx Fragment Count: A 32-bit value representing the number of
fragmented frames transmitted. The value of this field comes from fragmented frames transmitted. The value of this field comes from
the IEEE 802.11 dot11TransmittedFragmentCount MIB element (see the IEEE 802.11 dot11TransmittedFragmentCount MIB element (see
[3]). [2]).
Multicast Tx Count: A 32-bit value representing the number of Multicast Tx Count: A 32-bit value representing the number of
multicast frames transmitted. The value of this field comes from multicast frames transmitted. The value of this field comes from
the IEEE 802.11 dot11MulticastTransmittedFrameCount MIB element the IEEE 802.11 dot11MulticastTransmittedFrameCount MIB element
(see [3]). (see [2]).
Failed Count: A 32-bit value representing the transmit excessive Failed Count: A 32-bit value representing the transmit excessive
retries. The value of this field comes from the IEEE 802.11 retries. The value of this field comes from the IEEE 802.11
dot11FailedCount MIB element (see [3]). dot11FailedCount MIB element (see [2]).
Retry Count: A 32-bit value representing the number of transmit Retry Count: A 32-bit value representing the number of transmit
retries. The value of this field comes from the IEEE 802.11 retries. The value of this field comes from the IEEE 802.11
dot11RetryCount MIB element (see [3]). dot11RetryCount MIB element (see [2]).
Multiple Retry Count: A 32-bit value representing the number of Multiple Retry Count: A 32-bit value representing the number of
transmits that required more than one retry. The value of this transmits that required more than one retry. The value of this
field comes from the IEEE 802.11 dot11MultipleRetryCount MIB field comes from the IEEE 802.11 dot11MultipleRetryCount MIB
element (see [3]). element (see [2]).
Frame Duplicate Count: A 32-bit value representing the duplicate Frame Duplicate Count: A 32-bit value representing the duplicate
frames received. The value of this field comes from the IEEE frames received. The value of this field comes from the IEEE
802.11 dot11FrameDuplicateCount MIB element (see [3]). 802.11 dot11FrameDuplicateCount MIB element (see [2]).
RTS Success Count: A 32-bit value representing the number of RTS Success Count: A 32-bit value representing the number of
successfully transmitted Ready To Send (RTS). The value of this successfully transmitted Ready To Send (RTS). The value of this
field comes from the IEEE 802.11 dot11RTSSuccessCount MIB element field comes from the IEEE 802.11 dot11RTSSuccessCount MIB element
(see [3]). (see [2]).
RTS Failure Count: A 32-bit value representing the failed RTS Failure Count: A 32-bit value representing the failed
transmitted RTS. The value of this field comes from the IEEE transmitted RTS. The value of this field comes from the IEEE
802.11 dot11RTSFailureCount MIB element (see [3]). 802.11 dot11RTSFailureCount MIB element (see [2]).
ACK Failure Count: A 32-bit value representing the number of failed ACK Failure Count: A 32-bit value representing the number of failed
acknowledgements. The value of this field comes from the IEEE acknowledgements. The value of this field comes from the IEEE
802.11 dot11ACKFailureCount MIB element (see [3]). 802.11 dot11ACKFailureCount MIB element (see [2]).
Rx Fragment Count: A 32-bit value representing the number of Rx Fragment Count: A 32-bit value representing the number of
fragmented frames received. The value of this field comes from fragmented frames received. The value of this field comes from
the IEEE 802.11 dot11ReceivedFragmentCount MIB element (see [3]). the IEEE 802.11 dot11ReceivedFragmentCount MIB element (see [2]).
Multicast RX Count: A 32-bit value representing the number of Multicast RX Count: A 32-bit value representing the number of
multicast frames received. The value of this field comes from the multicast frames received. The value of this field comes from the
IEEE 802.11 dot11MulticastReceivedFrameCount MIB element (see IEEE 802.11 dot11MulticastReceivedFrameCount MIB element (see
[3]). [2]).
FCS Error Count: A 32-bit value representing the number of FCS FCS Error Count: A 32-bit value representing the number of FCS
failures. The value of this field comes from the IEEE 802.11 failures. The value of this field comes from the IEEE 802.11
dot11FCSErrorCount MIB element (see [3]). dot11FCSErrorCount MIB element (see [2]).
Decryption Errors: A 32-bit value representing the number of Decryption Errors: A 32-bit value representing the number of
Decryption errors that occurred on the WTP. Note that this field Decryption errors that occurred on the WTP. Note that this field
is only valid in cases where the WTP provides encryption/ is only valid in cases where the WTP provides encryption/
decryption services. The value of this field comes from the IEEE decryption services. The value of this field comes from the IEEE
802.11 dot11WEPUndecryptableCount MIB element (see [3]). 802.11 dot11WEPUndecryptableCount MIB element (see [2]).
Discarded QoS Fragment Count: A 32-bit value representing the Discarded QoS Fragment Count: A 32-bit value representing the
number of discarded QoS fragments received. The value of this number of discarded QoS fragments received. The value of this
field comes from the IEEE 802.11 dot11QoSDiscardedFragmentCount field comes from the IEEE 802.11 dot11QoSDiscardedFragmentCount
MIB element (see [3]). MIB element (see [2]).
Associated Station Count: A 32-bit value representing the number of Associated Station Count: A 32-bit value representing the number of
number of associated stations. The value of this field comes from number of associated stations. The value of this field comes from
the IEEE 802.11 dot11AssociatedStationCount MIB element (see [3]). the IEEE 802.11 dot11AssociatedStationCount MIB element (see [2]).
QoS CF Polls Received Count: A 32-bit value representing the number QoS CF Polls Received Count: A 32-bit value representing the number
of (+)CF-Polls received. The value of this field comes from the of (+)CF-Polls received. The value of this field comes from the
IEEE 802.11 dot11QosCFPollsReceivedCount MIB element (see [3]). IEEE 802.11 dot11QosCFPollsReceivedCount MIB element (see [2]).
QoS CF Polls Unused Count: A 32-bit value representing the number QoS CF Polls Unused Count: A 32-bit value representing the number
of (+)CF-Polls that have been received, but not used. The value of (+)CF-Polls that have been received, but not used. The value
of this field comes from the IEEE 802.11 of this field comes from the IEEE 802.11
dot11QosCFPollsUnusedCount MIB element (see [3]). dot11QosCFPollsUnusedCount MIB element (see [2]).
QoS CF Polls Unusable Count: A 32-bit value representing the number QoS CF Polls Unusable Count: A 32-bit value representing the number
of (+)CF-Polls that have been received, but could not be used due of (+)CF-Polls that have been received, but could not be used due
to the TXOP size being smaller than the timethat is required for to the TXOP size being smaller than the timethat is required for
one frame exchange sequence. The value of this field comes from one frame exchange sequence. The value of this field comes from
the IEEE 802.11 dot11QosCFPollsUnusableCount MIB element (see the IEEE 802.11 dot11QosCFPollsUnusableCount MIB element (see
[3]). [2]).
6.17. IEEE 802.11 Supported Rates 6.17. IEEE 802.11 Supported Rates
The IEEE 802.11 Supported Rates message element is sent by the WTP to The IEEE 802.11 Supported Rates message element is sent by the WTP to
indicate the rates that it supports, and contains the following indicate the rates that it supports, and contains the following
fields. fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 46, line 7 skipping to change at page 46, line 7
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Reserved: All implementations complying with this protocol MUST set Reserved: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the protocol to zero any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
Current Tx Power: This attribute contains the current transmit Current Tx Power: This attribute contains the current transmit
output power in mW, as described in the dot11CurrentTxPowerLevel output power in mW, as described in the dot11CurrentTxPowerLevel
MIB variable, see [3]. MIB variable, see [2].
6.19. IEEE 802.11 Tx Power Level 6.19. IEEE 802.11 Tx Power Level
The IEEE 802.11 Tx Power Level message element is sent by the WTP and The IEEE 802.11 Tx Power Level message element is sent by the WTP and
contains the different power levels supported. The values found in contains the different power levels supported. The values found in
this message element are found in the IEEE 802.11 this message element are found in the IEEE 802.11
Dot11PhyTxPowerEntry MIB table, see [3]. Dot11PhyTxPowerEntry MIB table, see [2].
The value field contains the following: The value field contains the following:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Num Levels | Power Level [n] | | Radio ID | Num Levels | Power Level [n] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1042 for IEEE 802.11 Tx Power Level Type: 1042 for IEEE 802.11 Tx Power Level
Length: >= 4 Length: >= 4
Radio ID: An 8-bit value representing the radio to configure. Radio ID: An 8-bit value representing the radio to configure.
Num Levels: The number of power level attributes. The value of Num Levels: The number of power level attributes. The value of
this field comes from the IEEE 802.11 this field comes from the IEEE 802.11
dot11NumberSupportedPowerLevels MIB element (see [3]). dot11NumberSupportedPowerLevels MIB element (see [2]).
Power Level: Each power level fields contains a supported power Power Level: Each power level fields contains a supported power
level, in mW. The value of this field comes from the level, in mW. The value of this field comes from the
corresponding IEEE 802.11 dot11TxPowerLevel[n] MIB element, see corresponding IEEE 802.11 dot11TxPowerLevel[n] MIB element, see
[3]. [2].
6.20. IEEE 802.11 Update Station QoS 6.20. IEEE 802.11 Update Station QoS
The IEEE 802.11 Update Station QoS message element is used to change The IEEE 802.11 Update Station QoS message element is used to change
the Quality of Service policy on the WTP for a given station. the Quality of Service policy on the WTP for a given station.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | MAC Address | | Radio ID | MAC Address |
skipping to change at page 48, line 50 skipping to change at page 48, line 50
field. field.
Key: A 32 byte Session Key to use to provide data privacy. For Key: A 32 byte Session Key to use to provide data privacy. For
static WEP keys, which is true when the 'Key Status' bit is set to static WEP keys, which is true when the 'Key Status' bit is set to
one, this key is used for both unicast and multicast traffic. For one, this key is used for both unicast and multicast traffic. For
encryption schemes that employ a separate encryption key for encryption schemes that employ a separate encryption key for
unicast and multicast traffic, the key included hereonly applies unicast and multicast traffic, the key included hereonly applies
to multicast data, and the cipher suite is specified in an to multicast data, and the cipher suite is specified in an
accompanied RSN Information Element. In these scenarios, the key, accompanied RSN Information Element. In these scenarios, the key,
and cipher information, is communicated via the Add Station and cipher information, is communicated via the Add Station
message element, see Section 4.5.8 in [1]. message element, see Section 4.5.8 in [3].
6.22. IEEE 802.11 WTP Quality of Service 6.22. IEEE 802.11 WTP Quality of Service
The IEEE 802.11 WTP Quality of Service message element value is sent The IEEE 802.11 WTP Quality of Service message element value is sent
by the AC to the WTP to communicate quality of service configuration by the AC to the WTP to communicate quality of service configuration
information. information.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Tag Packets | | Radio ID | Tag Packets |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1045 for IEEE 802.11 WTP Quality of Service Type: 1045 for IEEE 802.11 WTP Quality of Service
Length: >= 2 Length: >= 2
Radio ID: The Radio Identifier, typically refers to some interface Radio ID: The Radio Identifier, typically refers to some interface
index on the WTP index on the WTP
Tag Packets: An value indicating whether CAPWAP packets should be Tag Packets: A value indicating whether CAPWAP packets should be
tagged with for QoS purposes. The following values are currently tagged for QoS purposes. The following values are currently
supported: supported:
0 - Untagged 0 - Untagged
1 - 802.1P 1 - 802.1P
2 - DSCP 2 - DSCP
Immediately following the above header is the following data Immediately following the above header is the following data
structure. This data structure will be repeated five times; once structure. This data structure will be repeated five times; once
skipping to change at page 50, line 7 skipping to change at page 50, line 7
| Queue Depth | CWMin | CWMax | | Queue Depth | CWMin | CWMax |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CWMax | AIFS | Dot1P Tag | DSCP Tag | | CWMax | AIFS | Dot1P Tag | DSCP Tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Queue Depth: The number of packets that can be on the specific QoS Queue Depth: The number of packets that can be on the specific QoS
transmit queue at any given time. transmit queue at any given time.
CWMin: The Contention Window minimum value for the QoS transmit CWMin: The Contention Window minimum value for the QoS transmit
queue. The value of this field comes from the IEEE 802.11 queue. The value of this field comes from the IEEE 802.11
dot11EDCATableCWMin MIB element (see [3]). dot11EDCATableCWMin MIB element (see [2]).
CWMax: The Contention Window maximum value for the QoS transmit CWMax: The Contention Window maximum value for the QoS transmit
queue. The value of this field comes from the IEEE 802.11 queue. The value of this field comes from the IEEE 802.11
dot11EDCATableCWMax MIB element (see [3]). dot11EDCATableCWMax MIB element (see [2]).
AIFS: The Arbitration Inter Frame Spacing to use for the QoS AIFS: The Arbitration Inter Frame Spacing to use for the QoS
transmit queue. The value of this field comes from the IEEE transmit queue. The value of this field comes from the IEEE
802.11 dot11EDCATableAIFSN MIB element (see [3]). 802.11 dot11EDCATableAIFSN MIB element (see [2]).
Dot1P Tag: The 802.1P precedence value to use if packets are to be Dot1P Tag: The 802.1P precedence value to use if packets are to be
802.1P tagged. 802.1P tagged.
DSCP Tag: The DSCP label to use if packets are to be DSCP tagged. DSCP Tag: The DSCP label to use if packets are to be DSCP tagged.
6.23. IEEE 802.11 WTP Radio Configuration 6.23. IEEE 802.11 WTP Radio Configuration
The IEEE 802.11 WTP WLAN Radio Configuration message element is used The IEEE 802.11 WTP WLAN Radio Configuration message element is used
by the AC to configure a Radio on the WTP, and by the WTP to deliver by the AC to configure a Radio on the WTP, and by the WTP to deliver
skipping to change at page 51, line 20 skipping to change at page 51, line 20
Number of BSSIDs: This attribute contains the maximum number of Number of BSSIDs: This attribute contains the maximum number of
BSSIDs supported by the WTP. This value restricts the number of BSSIDs supported by the WTP. This value restricts the number of
logical networks supported by the WTP, and is between 1 and 16. logical networks supported by the WTP, and is between 1 and 16.
DTIM Period: This attribute specifies the number of beacon DTIM Period: This attribute specifies the number of beacon
intervals that elapse between transmission of Beacons frames intervals that elapse between transmission of Beacons frames
containing a TIM element whose DTIM Count field is 0. This value containing a TIM element whose DTIM Count field is 0. This value
is transmitted in the DTIM Period field of Beacon frames. The is transmitted in the DTIM Period field of Beacon frames. The
value of this field comes from the IEEE 802.11 dot11DTIMPeriod MIB value of this field comes from the IEEE 802.11 dot11DTIMPeriod MIB
element (see [3]). element (see [2]).
Beacon Period: This attribute specifies the number of TU that a Beacon Period: This attribute specifies the number of TU that a
station uses for scheduling Beacon transmissions. This value is station uses for scheduling Beacon transmissions. This value is
transmitted in Beacon and Probe Response frames. The value of transmitted in Beacon and Probe Response frames. The value of
this field comes from the IEEE 802.11 dot11BeaconPeriod MIB this field comes from the IEEE 802.11 dot11BeaconPeriod MIB
element (see [3]). element (see [2]).
Country Code: This attribute identifies the country in which the Country Code: This attribute identifies the country in which the
station is operating. The value of this field comes from the IEEE station is operating. The value of this field comes from the IEEE
802.11 dot11CountryString MIB element (see [3]). Special 802.11 dot11CountryString MIB element (see [2]). Special
attention is required with use of this field, as implementations attention is required with use of this field, as implementations
which take action based on this field could violate regulatory which take action based on this field could violate regulatory
requirements. Some regulatory bodies do permit configuration of requirements. Some regulatory bodies do permit configuration of
the country code under certain restrictions, such as the FCC, when the country code under certain restrictions, such as the FCC, when
WTPs are certified as Software Defined Radios. WTPs are certified as Software Defined Radios.
The WTP and AC may ignore the value of this field, depending upon The WTP and AC MAY ignore the value of this field, depending upon
regulatory requirements, for example to avoid classification as a regulatory requirements, for example to avoid classification as a
Software Defined Radio. When this field is used, the first two Software Defined Radio. When this field is used, the first two
octets of this string is the two character country code as octets of this string is the two character country code as
described in document ISO/IEC 3166- 1, and the third octet MUST described in document ISO/IEC 3166- 1, and the third octet MUST
have the value 1, 2 or 3 as defined below. When the value of the have the value 1, 2 or 3 as defined below. When the value of the
third octet is 255, the country code field is not used, and MUST third octet is 255, the country code field is not used, and MUST
be ignored. be ignored.
1 an ASCII space character, if the regulations under which the 1 an ASCII space character, if the regulations under which the
station is operating encompass all environments in the country, station is operating encompass all environments in the country,
skipping to change at page 55, line 16 skipping to change at page 55, line 16
This section lists IEEE 802.11 specific values for the generic CAPWAP This section lists IEEE 802.11 specific values for the generic CAPWAP
message elements which include fields whose values are technology message elements which include fields whose values are technology
specific. specific.
IEEE 802.11 uses the following values: IEEE 802.11 uses the following values:
4 - Encrypt AES-CCMP 128: WTP supports AES-CCMP, as defined in [4]. 4 - Encrypt AES-CCMP 128: WTP supports AES-CCMP, as defined in [4].
5 - Encrypt TKIP-MIC: WTP supports TKIP and Michael, as defined in 5 - Encrypt TKIP-MIC: WTP supports TKIP and Michael, as defined in
[11]. [7].
9. Security Considerations 9. Security Considerations
This section describes security considerations for using IEEE 802.11 This section describes security considerations for using IEEE 802.11
with the CAPWAP protocol. with the CAPWAP protocol.
9.1. IEEE 802.11 Security 9.1. IEEE 802.11 Security
When used with an IEEE 802.11 infrastructure with WEP encryption, the When used with an IEEE 802.11 infrastructure with WEP encryption, the
CAPWAP protocol does not add any new vulnerabilities. Derived CAPWAP protocol does not add any new vulnerabilities. Derived
session keys between the STA and WTP can be compromised, resulting in session keys between the STA and WTP can be compromised, resulting in
many well-documented attacks. Implementors SHOULD discourage the use many well-documented attacks. Implementors SHOULD discourage the use
of WEP and encourage use of technically sound cryptographic solutions of WEP and encourage use of technically sound cryptographic solutions
such as those in an IEEE 802.11 RSN. such as those in an IEEE 802.11 RSN.
STA authentication is performed using IEEE 802.lX, and consequently STA authentication is performed using IEEE 802.lX, and consequently
EAP. Implementors SHOULD use EAP methods meeting the requirements EAP. Implementors SHOULD use EAP methods meeting the requirements
specified [6]. specified [5].
When used with IEEE 802.11 RSN security, the CAPWAP protocol may When used with IEEE 802.11 RSN security, the CAPWAP protocol may
introduce new vulnerabilities, depending on whether the link security introduce new vulnerabilities, depending on whether the link security
(packet encryption and integrity verification) is provided by the WTP (packet encryption and integrity verification) is provided by the WTP
or the AC. When the link security function is provided by the AC, no or the AC. When the link security function is provided by the AC, no
new security concerns are introduced. new security concerns are introduced.
However, when the WTP provides link security, a new vulnerability However, when the WTP provides link security, a new vulnerability
will exist when the following conditions are true: will exist when the following conditions are true:
skipping to change at page 60, line 9 skipping to change at page 60, line 9
The following individuals are acknowledged for their contributions to The following individuals are acknowledged for their contributions to
this binding specification: Puneet Agarwal, Charles Clancy, Saravanan this binding specification: Puneet Agarwal, Charles Clancy, Saravanan
Govindan, Scott Kelly, Peter Nilsson, Bob O'Hara, David Perkins and Govindan, Scott Kelly, Peter Nilsson, Bob O'Hara, David Perkins and
Margaret Wasserman. Margaret Wasserman.
12. References 12. References
12.1. Normative References 12.1. Normative References
[1] "draft-ietf-capwap-protocol-specification-05". [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[3] "Information technology - Telecommunications and information [2] "Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area networks exchange between systems - Local and metropolitan area networks
- Specific requirements - Part 11: Wireless LAN Medium Access - Specific requirements - Part 11: Wireless LAN Medium Access
Control (MAC) and Physical Layer (PHY) specifications", Control (MAC) and Physical Layer (PHY) specifications",
IEEE Standard 802.11, 1999, IEEE Standard 802.11, 1999,
<http://standards.ieee.org/getieee802/download/ <http://standards.ieee.org/getieee802/download/802.11-1999.pdf>.
802.11-1999.pdf>.
[3] Calhoun, P., Montemurro, M., Stanley, D., "CAPWAP Protocol
Specification", draft-ietf-capwap-protocol-specification-07
(work in progress), June 2007.
[4] "Information technology - Telecommunications and information [4] "Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area networks exchange between systems - Local and metropolitan area networks
- Specific requirements - Part 11: Wireless LAN Medium Access - Specific requirements - Part 11: Wireless LAN Medium Access
Control (MAC) and Physical Layer (PHY) specifications Amendment Control (MAC) and Physical Layer (PHY) specifications Amendment
6: Medium Access Control (MAC) Security Enhancements", 6: Medium Access Control (MAC) Security Enhancements",
IEEE Standard 802.11i, July 2004, <http://standards.ieee.org/ IEEE Standard 802.11i, July 2004,
getieee802/download/802.11i-2004.pdf>. <http://standards.ieee.org/getieee802/download/
802.11i-2004.pdf>.
[5] Aboba, B. and J. Wood, "Authentication, Authorization and 12.2. Informational References
Accounting (AAA) Transport Profile", RFC 3539, June 2003.
[6] Stanley, D., Walker, J., and B. Aboba, "Extensible [5] Stanley, D., Walker, J., and B. Aboba, "Extensible
Authentication Protocol (EAP) Method Requirements for Wireless Authentication Protocol (EAP) Method Requirements for Wireless
LANs", RFC 4017, March 2005. LANs", RFC 4017, March 2005.
[7] Yang, L., Zerfos, P., and E. Sadot, "Architecture Taxonomy for [6] Yang, L., Zerfos, P., and E. Sadot, "Architecture Taxonomy for
Control and Provisioning of Wireless Access Points (CAPWAP)", Control and Provisioning of Wireless Access Points (CAPWAP)",
RFC 4118, June 2005. RFC 4118, June 2005.
[8] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) [7] "WiFi Protected Access (WPA), WPAfor802.11ver3_073004.pdf",
Protocol Version 1.1", RFC 4346, April 2006. August 2004.
[9] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004.
[10] Rescorla et al, E., "Datagram Transport Layer Security",
June 2004.
12.2. Informational References
[11] "WiFi Protected Access (WPA) rev 1.6", April 2003.
Editors' Addresses Editors' Addresses
Pat R. Calhoun Pat R. Calhoun
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Phone: +1 408-853-5269 Phone: +1 408-853-5269
Email: pcalhoun@cisco.com Email: pcalhoun@cisco.com
 End of changes. 124 change blocks. 
233 lines changed or deleted 165 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/