draft-ietf-capwap-protocol-binding-ieee80211-12.txt   rfc5416.txt 
Network Working Group P. Calhoun, Editor Network Working Group P. Calhoun, Ed.
Internet-Draft Cisco Systems, Inc. Request for Comments: 5416 Cisco Systems, Inc.
Intended status: Standards Track M. Montemurro, Editor Category: Standards Track M. Montemurro, Ed.
Expires: May 4, 2009 Research In Motion Research In Motion
D. Stanley, Editor D. Stanley, Ed.
Aruba Networks Aruba Networks
October 31, 2008 Control and Provisioning of Wireless Access Points (CAPWAP) Protocol
Binding for IEEE 802.11
CAPWAP Protocol Binding for IEEE 802.11
draft-ietf-capwap-protocol-binding-ieee80211-12
Status of this Memo
By submitting this Internet-Draft, each author represents that any Status of This Memo
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document specifies an Internet standards track protocol for the
Task Force (IETF), its areas, and its working groups. Note that Internet community, and requests discussion and suggestions for
other groups may also distribute working documents as Internet- improvements. Please refer to the current edition of the "Internet
Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months Copyright Notice
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright (c) 2009 IETF Trust and the persons identified as the
http://www.ietf.org/ietf/1id-abstracts.txt. document authors. All rights reserved.
The list of Internet-Draft Shadow Directories can be accessed at This document is subject to BCP 78 and the IETF Trust's Legal
http://www.ietf.org/shadow.html. Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This Internet-Draft will expire on May 4, 2009. This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
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 IEEE 802.11 Wireless Local Area Network protocol.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction ....................................................4
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Goals ......................................................5
1.2. Conventions used in this document . . . . . . . . . . . . 6 1.2. Conventions Used in This Document ..........................5
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 1.3. Terminology ................................................5
2. IEEE 802.11 Binding . . . . . . . . . . . . . . . . . . . . . 8 2. IEEE 802.11 Binding .............................................7
2.1. CAPWAP Wireless Binding Identifier . . . . . . . . . . . 8 2.1. CAPWAP Wireless Binding Identifier .........................7
2.2. Split MAC and Local MAC Functionality . . . . . . . . . . 8 2.2. Split MAC and Local MAC Functionality ......................7
2.2.1. Split MAC . . . . . . . . . . . . . . . . . . . . . . 8 2.2.1. Split MAC ...........................................7
2.2.2. Local MAC . . . . . . . . . . . . . . . . . . . . . . 13 2.2.2. Local MAC ..........................................12
2.3. Roaming Behavior . . . . . . . . . . . . . . . . . . . . 16 2.3. Roaming Behavior ..........................................15
2.4. Group Key Refresh . . . . . . . . . . . . . . . . . . . . 17 2.4. Group Key Refresh .........................................16
2.5. BSSID to WLAN ID Mapping . . . . . . . . . . . . . . . . 18 2.5. BSSID to WLAN ID Mapping ..................................17
2.6. CAPWAP Data Channel QoS Behavior . . . . . . . . . . . . 19 2.6. CAPWAP Data Channel QoS Behavior ..........................18
2.6.1. IEEE 802.11 Data Frames . . . . . . . . . . . . . . . 19 2.6.1. IEEE 802.11 Data Frames ............................18
2.6.2. IEEE 802.11 MAC Management Messages . . . . . . . . . 22 2.6.1.1. 802.1p Support ............................19
2.7. Run State Operation . . . . . . . . . . . . . . . . . . . 22 2.6.1.2. DSCP Support ..............................19
3. IEEE 802.11 Specific CAPWAP Control Messages . . . . . . . . . 23 2.6.2. IEEE 802.11 MAC Management Messages ................21
3.1. IEEE 802.11 WLAN Configuration Request . . . . . . . . . 23 2.7. Run State Operation .......................................21
3.2. IEEE 802.11 WLAN Configuration Response . . . . . . . . . 24 3. IEEE 802.11 Specific CAPWAP Control Messages ...................21
4. CAPWAP Data Message Bindings . . . . . . . . . . . . . . . . . 25 3.1. IEEE 802.11 WLAN Configuration Request ....................22
5. CAPWAP Control Message bindings . . . . . . . . . . . . . . . 27 3.2. IEEE 802.11 WLAN Configuration Response ...................23
5.1. Discovery Request Message . . . . . . . . . . . . . . . . 27 4. CAPWAP Data Message Bindings ...................................23
5.2. Discovery Response Message . . . . . . . . . . . . . . . 27 5. CAPWAP Control Message Bindings ................................25
5.3. Primary Discovery Request Message . . . . . . . . . . . . 27 5.1. Discovery Request Message .................................25
5.4. Primary Discovery Response Message . . . . . . . . . . . 27 5.2. Discovery Response Message ................................25
5.5. Join Request Message . . . . . . . . . . . . . . . . . . 27 5.3. Primary Discovery Request Message .........................25
5.6. Join Response Message . . . . . . . . . . . . . . . . . . 28 5.4. Primary Discovery Response Message ........................26
5.7. Configuration Status Request Message . . . . . . . . . . 28 5.5. Join Request Message ......................................26
5.8. Configuration Status Response Message . . . . . . . . . . 28 5.6. Join Response Message .....................................26
5.9. Configuration Update Request Message . . . . . . . . . . 29 5.7. Configuration Status Request Message ......................26
5.10. Station Configuration Request . . . . . . . . . . . . . . 30 5.8. Configuration Status Response Message .....................27
5.11. Change State Event Request . . . . . . . . . . . . . . . 30 5.9. Configuration Update Request Message ......................27
5.12. WTP Event Request . . . . . . . . . . . . . . . . . . . . 30 5.10. Station Configuration Request ............................28
6. IEEE 802.11 Message Element Definitions . . . . . . . . . . . 31 5.11. Change State Event Request ...............................28
6.1. IEEE 802.11 Add WLAN . . . . . . . . . . . . . . . . . . 31 5.12. WTP Event Request ........................................28
6.2. IEEE 802.11 Antenna . . . . . . . . . . . . . . . . . . . 37 6. IEEE 802.11 Message Element Definitions ........................29
6.3. IEEE 802.11 Assigned WTP BSSID . . . . . . . . . . . . . 38 6.1. IEEE 802.11 Add WLAN ......................................29
6.4. IEEE 802.11 Delete WLAN . . . . . . . . . . . . . . . . . 39 6.2. IEEE 802.11 Antenna .......................................35
6.5. IEEE 802.11 Direct Sequence Control . . . . . . . . . . . 39 6.3. IEEE 802.11 Assigned WTP BSSID ............................36
6.6. IEEE 802.11 Information Element . . . . . . . . . . . . . 41 6.4. IEEE 802.11 Delete WLAN ...................................37
6.7. IEEE 802.11 MAC Operation . . . . . . . . . . . . . . . . 41 6.5. IEEE 802.11 Direct Sequence Control .......................37
6.8. IEEE 802.11 MIC Countermeasures . . . . . . . . . . . . . 43 6.6. IEEE 802.11 Information Element ...........................38
6.9. IEEE 802.11 Multi-Domain Capability . . . . . . . . . . . 44 6.7. IEEE 802.11 MAC Operation .................................39
6.10. IEEE 802.11 OFDM Control . . . . . . . . . . . . . . . . 45 6.8. IEEE 802.11 MIC Countermeasures ...........................41
6.11. IEEE 802.11 Rate Set . . . . . . . . . . . . . . . . . . 46 6.9. IEEE 802.11 Multi-Domain Capability .......................42
6.12. IEEE 802.11 RSNA Error Report From Station . . . . . . . 47 6.10. IEEE 802.11 OFDM Control .................................43
6.13. IEEE 802.11 Station . . . . . . . . . . . . . . . . . . . 49 6.11. IEEE 802.11 Rate Set .....................................44
6.14. IEEE 802.11 Station QoS Profile . . . . . . . . . . . . . 50 6.12. IEEE 802.11 RSNA Error Report From Station ...............44
6.15. IEEE 802.11 Station Session Key . . . . . . . . . . . . . 51 6.13. IEEE 802.11 Station ......................................46
6.16. IEEE 802.11 Statistics . . . . . . . . . . . . . . . . . 53 6.14. IEEE 802.11 Station QoS Profile ..........................47
6.17. IEEE 802.11 Supported Rates . . . . . . . . . . . . . . . 57 6.15. IEEE 802.11 Station Session Key ..........................48
6.18. IEEE 802.11 Tx Power . . . . . . . . . . . . . . . . . . 57 6.16. IEEE 802.11 Statistics ...................................50
6.19. IEEE 802.11 Tx Power Level . . . . . . . . . . . . . . . 58 6.17. IEEE 802.11 Supported Rates ..............................54
6.20. IEEE 802.11 Update Station QoS . . . . . . . . . . . . . 59 6.18. IEEE 802.11 Tx Power .....................................54
6.21. IEEE 802.11 Update WLAN . . . . . . . . . . . . . . . . . 60 6.19. IEEE 802.11 Tx Power Level ...............................55
6.22. IEEE 802.11 WTP Quality of Service . . . . . . . . . . . 64 6.20. IEEE 802.11 Update Station QoS ...........................56
6.23. IEEE 802.11 WTP Radio Configuration . . . . . . . . . . . 66 6.21. IEEE 802.11 Update WLAN ..................................57
6.24. IEEE 802.11 WTP Radio Fail Alarm Indication . . . . . . . 68 6.22. IEEE 802.11 WTP Quality of Service .......................61
6.25. IEEE 802.11 WTP Radio Information . . . . . . . . . . . . 69 6.23. IEEE 802.11 WTP Radio Configuration ......................63
7. IEEE 802.11 Binding WTP Saved Variables . . . . . . . . . . . 71 6.24. IEEE 802.11 WTP Radio Fail Alarm Indication ..............65
7.1. IEEE80211AntennaInfo . . . . . . . . . . . . . . . . . . 71 6.25. IEEE 802.11 WTP Radio Information ........................66
7.2. IEEE80211DSControl . . . . . . . . . . . . . . . . . . . 71 7. IEEE 802.11 Binding WTP Saved Variables ........................67
7.3. IEEE80211MACOperation . . . . . . . . . . . . . . . . . . 71 7.1. IEEE80211AntennaInfo ......................................67
7.4. IEEE80211OFDMControl . . . . . . . . . . . . . . . . . . 71 7.2. IEEE80211DSControl ........................................67
7.5. IEEE80211Rateset . . . . . . . . . . . . . . . . . . . . 71 7.3. IEEE80211MACOperation .....................................67
7.6. IEEE80211TxPower . . . . . . . . . . . . . . . . . . . . 71 7.4. IEEE80211OFDMControl ......................................67
7.7. IEEE80211QoS . . . . . . . . . . . . . . . . . . . . . . 71 7.5. IEEE80211Rateset ..........................................67
7.8. IEEE80211RadioConfig . . . . . . . . . . . . . . . . . . 71 7.6. IEEE80211TxPower ..........................................67
8. Technology Specific Message Element Values . . . . . . . . . . 72 7.7. IEEE80211QoS ..............................................68
7.8. IEEE80211RadioConfig ......................................68
8. Technology Specific Message Element Values .....................68
8.1. WTP Descriptor Message Element, Encryption 8.1. WTP Descriptor Message Element, Encryption
Capabilities Field: . . . . . . . . . . . . . . . . . . . 72 Capabilities Field ........................................68
9. Security Considerations . . . . . . . . . . . . . . . . . . . 73 9. Security Considerations ........................................68
9.1. IEEE 802.11 Security . . . . . . . . . . . . . . . . . . 73 9.1. IEEE 802.11 Security ......................................68
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 75 10. IANA Considerations ...........................................70
10.1. CAPWAP Wireless Binding Identifier . . . . . . . . . . . 75 10.1. CAPWAP Wireless Binding Identifier .......................70
10.2. CAPWAP IEEE 802.11 Message Types . . . . . . . . . . . . 75 10.2. CAPWAP IEEE 802.11 Message Types .........................70
10.3. CAPWAP Message Element Type . . . . . . . . . . . . . . . 75 10.3. CAPWAP Message Element Type ..............................70
10.4. IEEE 802.11 Key Status . . . . . . . . . . . . . . . . . 75 10.4. IEEE 802.11 Key Status ...................................71
10.5. IEEE 802.11 QoS . . . . . . . . . . . . . . . . . . . . . 76 10.5. IEEE 802.11 QoS ..........................................71
10.6. IEEE 802.11 Auth Type . . . . . . . . . . . . . . . . . . 76 10.6. IEEE 802.11 Auth Type ....................................71
10.7. IEEE 802.11 Antenna Combiner . . . . . . . . . . . . . . 76 10.7. IEEE 802.11 Antenna Combiner .............................71
10.8. IEEE 802.11 Antenna Selection . . . . . . . . . . . . . . 76 10.8. IEEE 802.11 Antenna Selection ............................72
10.9. IEEE 802.11 Session Key Flags . . . . . . . . . . . . . . 77 10.9. IEEE 802.11 Session Key Flags ............................72
10.10. IEEE 802.11 Tagging Policy . . . . . . . . . . . . . . . 77 10.10. IEEE 802.11 Tagging Policy ..............................72
10.11. IEEE 802.11 WTP Radio Fail . . . . . . . . . . . . . . . 77 10.11. IEEE 802.11 WTP Radio Fail ..............................72
10.12. IEEE 802.11 WTP Radio Type . . . . . . . . . . . . . . . 77 10.12. IEEE 802.11 WTP Radio Type ..............................73
10.13. WTP Encryption Capabilities . . . . . . . . . . . . . . . 78 10.13. WTP Encryption Capabilities .............................73
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79 11. Acknowledgments ...............................................73
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 80 12. References ....................................................73
12.1. Normative References . . . . . . . . . . . . . . . . . . 80 12.1. Normative References .....................................73
12.2. Informational References . . . . . . . . . . . . . . . . 81 12.2. Informative References ...................................75
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 82
Intellectual Property and Copyright Statements . . . . . . . . . . 83
1. Introduction 1. Introduction
The CAPWAP protocol [I-D.ietf-capwap-protocol-specification] defines The CAPWAP protocol [RFC5415] defines an extensible protocol to allow
an extensible protocol to allow an Access Controller to manage an Access Controller to manage wireless agnostic Wireless Termination
wireless agnostic Wireless Termination Points. The CAPWAP protocol Points. The CAPWAP protocol itself does not include any specific
itself does not include any specific wireless technologies, but wireless technologies; instead, it relies on a binding specification
instead relies on binding specification to extend the technology to a to extend the technology to a particular wireless technology.
particular wireless technology.
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
defined. The minimum required definitions for a binding-specific are 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.
Note that this binding only supports the IEEE 802.11-2007 Note that this binding only supports the IEEE 802.11-2007
specification. Of note, this binding does not support the ad-hoc specification. Of note, this binding does not support the ad hoc
network mode defined in the IEEE 802.11-2007 standard. This network mode defined in the IEEE 802.11-2007 standard. This
specification also does not cover the use of data frames with the specification also does not cover the use of data frames with the
four-address format, commonly referred to as Wireless Bridges, whose four-address format, commonly referred to as Wireless Bridges, whose
use is not specified in the IEEE 802.11-2007 standard. New protocol use is not specified in the IEEE 802.11-2007 standard. This protocol
specifications published outside of this document (e.g., IEEE specification does not currently officially support IEEE 802.11n.
802.11n, IEEE 802.11r) are therefore not supported through this That said, the protocol does allow a WTP to advertise support for an
binding, and must be addressed either through a separate CAPWAP IEEE 802.11n radio; however, the protocol does not allow for any of
binding, or an update to this binding. the protocol's additional features to be configured and/or used. New
IEEE protocol specifications published outside of this document
(e.g., IEEE 802.11v, IEEE 802.11r) are also not supported through
this binding, and in addition to IEEE 802.11n, must be addressed
either through a separate CAPWAP binding, or an update to this
binding.
In order to address immediate market needs for standards still being In order to address immediate market needs for standards still being
developed by the IEEE 802.11 standards body, the WiFi Alliance developed by the IEEE 802.11 standards body, the WiFi Alliance
created interim pseudo-standards specifications. Two such created interim pseudo-standards specifications. Two such
specifications are widely used in the industry, namely the WiFi specifications are widely used in the industry, namely the WiFi
Protect Access [WPA] and the WiFi MultiMedia [WMM] specifications. Protect Access [WPA] and the WiFi MultiMedia [WMM] specifications.
Given their widespread adoption, this CAPWAP binding requires the use Given their widespread adoption, this CAPWAP binding requires the use
of these two specifications. of these two specifications.
1.1. Goals 1.1. Goals
skipping to change at page 6, line 6 skipping to change at page 5, line 27
with IEEE 802.11 wireless networks. The capabilities to be made with IEEE 802.11 wireless networks. The capabilities to be made
available can be summarized as: available can be summarized as:
1. To centralize the authentication and policy enforcement functions 1. To centralize the authentication and policy enforcement functions
for an IEEE 802.11 wireless network. The AC may also provide for an IEEE 802.11 wireless network. The AC may also provide
centralized bridging, forwarding, and encryption of user traffic. centralized bridging, forwarding, and encryption of user traffic.
Centralization of these functions will enable reduced cost and Centralization of these functions will enable reduced cost and
higher efficiency by applying the capabilities of network higher efficiency by applying the capabilities of network
processing silicon to the wireless network, as in wired LANs. processing silicon to the wireless network, as in wired LANs.
2. To enable shifting of the higher level protocol processing from 2. To enable shifting of the higher-level protocol processing from
the WTP. This leaves the time-critical applications of wireless the WTP. This leaves the time-critical applications of wireless
control and access in the WTP, making efficient use of the control and access in the WTP, making efficient use of the
computing power available in WTPs which are subject to severe cost computing power available in WTPs that are subject to severe cost
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 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.3. Terminology 1.3. Terminology
This section contains definitions for terms used frequently This section contains definitions for terms used frequently
throughout this document. However, many additional definitions can throughout this document. However, many additional definitions can
be found in [IEEE.802-11.2007]. be found in [IEEE.802-11.2007].
skipping to change at page 6, line 49 skipping to change at page 6, line 22
Distribution System Service (DSS): The set of services provided by Distribution System Service (DSS): The set of services provided by
the distribution system (DS) that enable the medium access control the distribution system (DS) that enable the medium access control
(MAC) layer to transport MAC service data units (MSDUs) between (MAC) layer to transport MAC service data units (MSDUs) between
stations that are not in direct communication with each other over a stations that are not in direct communication with each other over a
single instance of the wireless medium (WM). These services include single instance of the wireless medium (WM). These services include
the transport of MSDUs between the access points (APs) of basic the transport of MSDUs between the access points (APs) of basic
service sets (BSSs) within an extended service set (ESS), transport service sets (BSSs) within an extended service set (ESS), transport
of MSDUs between portals and BSSs within an ESS, and transport of of MSDUs between portals and BSSs within an ESS, and transport of
MSDUs between stations in the same BSS in cases where the MSDU has a MSDUs between stations in the same BSS in cases where the MSDU has a
multicast or broadcast destination address, or where the destination multicast or broadcast destination address, or where the destination
is an individual address, but the station sending the MSDU chooses to is an individual address but the station sending the MSDU chooses to
involve the DSS. DSSs are provided between pairs of IEEE 802.11 involve the DSS. DSSs are provided between pairs of IEEE 802.11
MACs. MACs.
Integration: The service that enables delivery of medium access Integration: The service that enables delivery of medium access
control (MAC) service data units (MSDUs) between the distribution control (MAC) service data units (MSDUs) between the distribution
system (DS) and an existing, non-IEEE 802.11 local area network (via system (DS) and an existing, non-IEEE 802.11 local area network (via
a portal). a portal).
Station (STA): A device that contains an IEEE 802.11 conformant Station (STA): A device that contains an IEEE 802.11 conformant
medium access control (MAC) and physical layer (PHY) interface to the medium access control (MAC) and physical layer (PHY) interface to the
skipping to change at page 8, line 11 skipping to change at page 7, line 11
Wireless Termination Point (WTP): The physical or network entity that Wireless Termination Point (WTP): The physical or network entity that
contains an IEEE 802.11 RF antenna and wireless PHY to transmit and contains an IEEE 802.11 RF antenna and wireless PHY to transmit and
receive station traffic for wireless access networks. receive station traffic for wireless access networks.
2. IEEE 802.11 Binding 2. IEEE 802.11 Binding
This section describes use of the CAPWAP protocol with the IEEE This section describes use of the CAPWAP protocol with the IEEE
802.11 Wireless Local Area Network protocol, including Local and 802.11 Wireless Local Area Network protocol, including Local and
Split MAC operation, Group Key Refresh, Basic Service Set Split MAC operation, Group Key Refresh, Basic Service Set
Identification (BSSID) to WLAN Mapping, IEEE 802.11 MAC management Identification (BSSID) to WLAN Mapping, IEEE 802.11 MAC management
frame Quality of Service tagging and Run State operation. frame Quality of Service (Qos) tagging and Run State operation.
2.1. CAPWAP Wireless Binding Identifier 2.1. CAPWAP Wireless Binding Identifier
The CAPWAP Header, defined in section 4.3 of The CAPWAP Header, defined in Section 4.3 of [RFC5415] requires that
[I-D.ietf-capwap-protocol-specification] requires that all CAPWAP all CAPWAP binding specifications have a Wireless Binding Identifier
binding specifications have a Wireless Binding Identifier (WBID) (WBID) assigned. This document, which defines the IEEE 802.11
assigned. This document, which defines the IEEE 802.11 binding, uses binding, uses the value one (1).
the the value one (1).
2.2. Split MAC and Local MAC Functionality 2.2. 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 [RFC4118], reside in the AC. defined in the taxonomy specification [RFC4118], reside in the AC.
skipping to change at page 9, line 14 skipping to change at page 8, line 14
Function Location Function Location
Distribution Service AC Distribution Service AC
Integration Service AC Integration Service AC
Beacon Generation WTP Beacon Generation WTP
Probe Response Generation WTP Probe Response Generation WTP
Power Mgmt/Packet Buffering WTP Power Mgmt/Packet Buffering WTP
Fragmentation/Defragmentation WTP/AC Fragmentation/Defragmentation WTP/AC
Assoc/Disassoc/Reassoc AC Assoc/Disassoc/Reassoc AC
IEEE 802.11 QOS IEEE 802.11 QoS
Classifying AC Classifying AC
Scheduling WTP/AC Scheduling WTP/AC
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/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 In a Split MAC Architecture, the Distribution and Integration
services reside on the AC, and therefore all user data is tunneled services reside on the AC, and therefore all user data is tunneled
between the WTP and the AC. As noted above, all real-time IEEE between the WTP and the AC. As noted above, all real-time IEEE
802.11 services, including the Beacon and Probe Response frames, are 802.11 services, including the Beacon and Probe Response frames, are
handled on the WTP. handled on the 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 that 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 [IEEE.802-1X.2004], Extensible protocol. The IEEE 802.1X [IEEE.802-1X.2004], Extensible
Authentication Protocol (EAP) [RFC3748] and IEEE Robust Security Authentication Protocol (EAP) [RFC3748] and IEEE Robust Security
Network Association (RSNA) Key Management [IEEE.802-11.2007] Network Association (RSNA) Key Management [IEEE.802-11.2007]
functions are also located on the AC. This implies that the AAA functions are also located on the AC. This implies that the
client also resides on the AC. Authentication, Authorization, and Accounting (AAA) client also
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
AC, the real time scheduling and queuing functions are on the WTP. AC, the real-time scheduling and queuing functions are on the WTP.
Note that this does not prevent the AC from providing additional Note that this does not prevent the AC from providing additional
policy and scheduling functionality. policy and scheduling functionality.
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. This figure represents processing of the frames is done on the WTP. This figure represents
a case where encryption services are provided by the AC. a case where encryption services are provided by the AC.
Client WTP AC Client WTP AC
Beacon Beacon
skipping to change at page 10, line 38 skipping to change at page 9, line 38
<--------------------------> <-------------------------->
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 (Counter mode with authentication and Advanced Encryption Standard-Counter Mode with
Cipher-block chaining Message authentication code Protocol, see CBC-MAC Protocol (AES-CCMP) link layer encryption (CCMP, see
[FIPS.197.2001]). The following process occurs: [FIPS.197.2001]). The 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 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 Robust Security Network Information
802.1X and AES-CCMP. Element (RSNIE), which indicates support of 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.6.8 in message element, to the WTP (see Section 4.6.8 in [RFC5415]). In
[I-D.ietf-capwap-protocol-specification]). In the above example, the above example, the WLAN was configured for IEEE 802.1X, and
the WLAN was configured for IEEE 802.1X, and therefore the IEEE therefore the IEEE 802.11 Station Session Key is included with the
802.11 Station Session Key is included with the flag field's 'A' flag field's 'A' bit set.
bit set.
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: includes:
- An Add Station message element. - An Add Station message element.
- An IEEE 802.11 Add Station message element, which includes the - An IEEE 802.11 Add Station message element, which includes the
WLAN Identifier the station has associated with. WLAN Identifier with which the station has associated.
- An IEEE 802.11 Station Session Key message element, which - An IEEE 802.11 Station Session Key message element, which
includes the pairwise encryption key. includes the pairwise encryption key.
- An IEEE 802.11 Information Element message element which - An IEEE 802.11 Information Element message element, which
includes the obust Security Network Information Element (RSNIE) includes the Robust Security Network Information Element
to the WTP, stating the security policy to enforce for the (RSNIE) to the WTP, stating the security policy to enforce for
client (in this case AES-CCMP). the client (in this case AES-CCMP).
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: includes:
- An Add Station message element. - An Add Station message element.
- An IEEE 802.11 Add Station message element, which includes the - An IEEE 802.11 Add Station message element, which includes the
WLAN Identifier the station has associated with. WLAN Identifier with which the station has associated.
- An IEEE 802.11 Station Session Key message element, which - An IEEE 802.11 Station Session Key message element, which
includes the pairwise encryption key. includes the pairwise encryption key.
- An IEEE 802.11 Information Element message element which - An IEEE 802.11 Information Element message element, which
includes the Robust Security Network Information Element includes the Robust Security Network Information Element
(RSNIE) to the WTP, stating the security policy to enforce for (RSNIE) to the WTP, stating the security policy to enforce for
the client (in this case AES-CCMP). the client (in this case AES-CCMP).
o If the AC is providing encryption/decryption services, once the o If the AC 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: includes:
- An Add Station message element. - An Add Station message element.
- An IEEE 802.11 Add Station message element, which includes the - An IEEE 802.11 Add Station message element, which includes the
WLAN Identifier the station has associated with. WLAN Identifier with which the station has associated.
- An IEEE 802.11 Station Session Key message element with the - An IEEE 802.11 Station Session Key message element with the
flag fields' 'C' bit enabled (indicating that the AC will flag field's 'C' bit enabled (indicating that the AC will
provide crypto services). provide crypto services).
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 All IEEE 802.11 station data frames are tunneled between the WTP o All IEEE 802.11 station data frames are tunneled between the WTP
and the AC. and the AC.
Note that during the EAPOL-Key exchange between the Station and the Note that during the EAP over LAN (EAPOL)-Key exchange between the
AC, the Receive Sequence Counter (RSC) field for the GTK needs to be Station and the AC, the Receive Sequence Counter (RSC) field for the
included in the frame. The value of zero (0) is used by the AC Group Key (GTK) needs to be included in the frame. The value of zero
during this exchange. Additional details are available in (0) is used by the AC during this exchange. Additional details are
Section 9.1. available in Section 9.1.
The WTP SHALL include the IEEE 802.11 MAC header contents in all The WTP SHALL include the IEEE 802.11 MAC header contents in all
frames transmitted to the AC. frames transmitted to the AC.
When 802.11 encryption/decryption is performed at the WTP, the WTP When 802.11 encryption/decryption is performed at the WTP, the WTP
MUST decrypt the uplink frames, MUST set the Protected Frame field to MUST decrypt the uplink frames, MUST set the Protected Frame field to
0, and MUST make the frame format consistent with that of an 0, and MUST make the frame format consistent with that of an
unprotected 802.11 frame prior to transmitting the frames to the AC. unprotected 802.11 frame prior to transmitting the frames to the AC.
The fields added to an 802.11 protected frame (i.e., Initialization The fields added to an 802.11 protected frame (i.e., Initialization
Vector/Extended Initialization Vector (IV/EIV), Message Integrity Vector/Extended Initialization Vector (IV/EIV), Message Integrity
skipping to change at page 13, line 28 skipping to change at page 12, line 28
Duration: WTP Duration: WTP
Address 1: AC Address 1: AC
Address 2: AC Address 2: AC
Address 3: AC Address 3: AC
Sequence Ctrl: WTP Sequence Ctrl: WTP
Address 4: AC Address 4: AC
QoS Control: AC QoS Control: AC
Frame Body: AC Frame Body: AC
FCS: WTP FCS: WTP
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 Frame applicable to downlink frames, and is set to 0. Note that the Frame
Check Sequence (FCS) field is not included in 802.11 frames exchanged Check Sequence (FCS) field is not included in 802.11 frames exchanged
between the WTP and the AC. Upon sending data frames to the AC, the between the WTP and the AC. Upon sending data frames to the AC, the
WTP is responsible for validating, and stripping the FCS field. Upon WTP is responsible for validating and stripping the FCS field. Upon
receiving data frames from the AC, the WTP is responsible for adding receiving data frames from the AC, the WTP is responsible for adding
the FCS field, and populating the field as described in the FCS field, and populating the field as described in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
Note that when the WTP tunnels data packets to the AC (and vice Note that when the WTP tunnels data packets to the AC (and vice
versa), the CAPWAP protocol does not guarantee in-order delivery. versa), the CAPWAP protocol does not guarantee in-order delivery.
When the protocol being transported over IEEE 802.11 is IP, out of When the protocol being transported over IEEE 802.11 is IP, out-of-
order delivery is not an issue as IP has no such requirements. order delivery is not an issue as IP has no such requirements.
However, implementors need to be aware of this protocol However, implementers need to be aware of this protocol
characteristic before deciding to use CAPWAP. characteristic before deciding to use CAPWAP.
2.2.2. Local MAC 2.2.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
Beacon Generation WTP Beacon Generation WTP
Probe Response Generation WTP Probe Response Generation WTP
Power Mgmt/Packet Buffering WTP Power Mgmt/Packet Buffering WTP
Fragmentation/Defragmentation WTP Fragmentation/Defragmentation WTP
Assoc/Disassoc/Reassoc WTP/AC Assoc/Disassoc/Reassoc WTP/AC
IEEE 802.11 QOS IEEE 802.11 QoS
Classifying WTP Classifying WTP
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
In the Local MAC mode, the integration service exists on the WTP, In the Local MAC mode, the integration service exists on the WTP,
while the distribution service MAY reside on either the WTP or the while the distribution service MAY reside on either the WTP or the
AC. When it resides on the AC, station generated frames are not 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 forwarded to the AC in their native format, but encapsulated as 802.3
frames. 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 [IEEE.802-1X.2004], EAP and IEEE RSNA Key Management The IEEE 802.1X [IEEE.802-1X.2004], EAP, and IEEE RSNA Key Management
[IEEE.802-11.2007] functions reside in the AC. Therefore, the WTP [IEEE.802-11.2007] functions reside in the AC. Therefore, the WTP
MUST forward all IEEE 802.1X, EAP and RSNA Key Management frames to MUST forward all IEEE 802.1X, EAP, and RSNA Key Management frames to
the AC and forward the corresponding responses to the station. This the AC and forward the corresponding responses to the station. This
implies that the AAA client also resides on the AC. 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
<----------------------------- <-----------------------------
skipping to change at page 16, line 10 skipping to change at page 15, line 7
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 4.6.8 in message element, to the WTP (see Section 4.6.8 in [RFC5415]). In
[I-D.ietf-capwap-protocol-specification]). In the above example, the above example, the WLAN was configured for IEEE 802.1X, and
the WLAN was configured for IEEE 802.1X, and therefore the IEEE therefore the IEEE 802.11 Station Session Key is included with the
802.11 Station Session Key is included with the flag field's 'A' flag field's 'A' bit set.
bit set.
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,
which includes: which includes:
- An Add Station message element, which MAY include a Virtual LAN - An Add Station message element, which MAY include a Virtual LAN
(VLAN) [IEEE.802-1Q.2005] name, which when present is used by (VLAN) [IEEE.802-1Q.2005] name, which when present is used by
the WTP to identify the VLAN on which the user's data frames the WTP to identify the VLAN on which the user's data frames
are to be bridged. are to be bridged.
- An IEEE 802.11 Add Station message element, which includes the - An IEEE 802.11 Add Station message element, which includes the
WLAN Identifier the station has associated with WLAN Identifier with which the station has associated.
- An IEEE 802.11 Station Session Key message element, which - An IEEE 802.11 Station Session Key message element, which
includes the pairwise encryption key. includes the pairwise encryption key.
- An IEEE 802.11 Information Element message element which - An IEEE 802.11 Information Element message element, which
includes the RSNIE to the WTP, stating the security policy to includes the RSNIE to the WTP, stating the security policy to
enforce for the client (in this case AES-CCMP). enforce for the client (in this case AES-CCMP).
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.
skipping to change at page 17, line 48 skipping to change at page 16, line 44
Element(RSNIE(Pairwise Element(RSNIE(Pairwise
Cipher=CCMP))] Cipher=CCMP))]
<----------------> <---------------->
Figure 6: Client Roaming Example Figure 6: Client Roaming Example
2.4. Group Key Refresh 2.4. 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 Layer 2 (L2)
frame transmitted to the BSS needs to be duplicated and transmitted broadcast frame transmitted to the BSS needs to be duplicated and
using both the current GTK and the new GTK. Once the GTK update transmitted using both the current GTK and the new GTK. Once the GTK
process has completed, broadcast frames transmitted to the BSS will update process has completed, broadcast frames transmitted to the BSS
be encrypted using the new GTK. will be encrypted using the new GTK.
In the case of Split MAC, the AC needs to duplicate all broadcast In the case of Split MAC, the AC needs to duplicate all broadcast
packets and update the key index so that the packet is transmitted packets and update the key index so that the packet is transmitted
using both the current and new GTK to ensure that all STA's in the using both the current and new GTK to ensure that all STAs in the BSS
BSS receive the broadcast frames. In the case of local MAC, the WTP receive the broadcast frames. In the case of Local MAC, the WTP
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 STAs 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 Transmit Sequence
Key and the Key Status set to 3 (begin GTK update). The AC will then Counter (TSC) for the Group Key and the Key Status set to 3 (begin
begin updating the GTK for each STA. During this time, the AC (for GTK update). The AC will then begin updating the GTK for each STA.
Split MAC) or WTP (for Local MAC) MUST duplicate broadcast packets During this time, the AC (for Split MAC) or WTP (for Local MAC) MUST
and transmit them encrypted with both the current and new GTK. When duplicate broadcast packets and transmit them encrypted with both the
the AC has completed the GTK update to all STA's in the BSS, the AC current and new GTK. When the AC has completed the GTK update to all
MUST transmit an IEEE 802.11 Configuration Request message including STAs in the BSS, the AC MUST transmit an IEEE 802.11 Configuration
an IEEE 802.11 Update WLAN message element containing the new GTK, Request message including an IEEE 802.11 Update WLAN message element
its index, and the Key Status set to 4 (GTK update complete). containing the new GTK, 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 IEEE 802.11 WLAN Configuration Request [Update
WLAN (GTK, GTK Index, GTK Start, WLAN (GTK, GTK Index, GTK Start,
Group TSC) ] 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)
skipping to change at page 19, line 22 skipping to change at page 18, line 22
allow for the WTP to enforce Quality of Service on IEEE 802.11 Data allow for the WTP to enforce Quality of Service on IEEE 802.11 Data
Frames and MAC Management messages. Frames and MAC Management messages.
2.6.1. IEEE 802.11 Data Frames 2.6.1. IEEE 802.11 Data Frames
When the WLAN is created on the WTP, a default Quality of Service When the WLAN is created on the WTP, a default Quality of Service
policy is established through the IEEE 802.11 WTP Quality of Service policy is established through the IEEE 802.11 WTP Quality of Service
message element (see Section 6.22). This default policy will cause message element (see Section 6.22). This default policy will cause
the WTP to use the default QoS values for any station associated with the WTP to use the default QoS values for any station associated with
the WLAN in question. The AC MAY also override the policy for a the WLAN in question. The AC MAY also override the policy for a
given station, by sending the IEEE 802.11 Update Station QoS message given station by sending the IEEE 802.11 Update Station QoS message
element (see Section 6.20), known as a station specific QoS policy. element (see Section 6.20), known as a station-specific QoS policy.
Beyond the default, and per station QoS policy, the IEEE 802.11 Beyond the default, and per station QoS policy, the IEEE 802.11
protocol also allows a station to request special QoS treatment for a protocol also allows a station to request special QoS treatment for a
specific flow through the TSPEC information elements found in the specific flow through the Traffic Specification (TSPEC) Information
IEEE 802.11-2007's QoS Action Frame. Alternatively, stations MAY Elements found in the IEEE 802.11-2007's QoS Action Frame.
also use the WiFi Alliance's WMM specification instead to request QoS Alternatively, stations MAY also use the WiFi Alliance's WMM
treatment for a flow (see [WMM]). This requires the WTP to observe specification instead to request QoS treatment for a flow (see
the Status Code in the IEEE 802.11-2007 and WMM QoS Action ADDTS [WMM]). This requires the WTP to observe the Status Code in the IEEE
responses from the AC, and provide the services requested in the 802.11-2007 and WMM QoS Action Add Traffic System (ADDTS) responses
TSPEC information element. Similarly, the WTP MUST observe the from the AC, and provide the services requested in the TSPEC
Reason Code information element in the IEEE 802.11-2007 and WMM QoS Information Element. Similarly, the WTP MUST observe the Reason Code
Action DELTS responses from the AC by removing the policy associated Information Element in the IEEE 802.11-2007 and WMM QoS Action DELTS
with the TSPEC. responses from the AC by removing the policy associated with the
TSPEC.
The IEEE 802.11 WTP Quality of Service message element's Tagging The IEEE 802.11 WTP Quality of Service message element's Tagging
Policy field indicates how the packets are to be tagged, known as the Policy field indicates how the packets are to be tagged, known as the
Tagging Policy. There are five bits defined, two of which are used Tagging Policy. There are five bits defined, two of which are used
to indicate the type of QoS to be used by the WTP. The first is the to indicate the type of QoS to be used by the WTP. The first is the
'P' bit which is set to inform the WTP it is to use the 802.1p QoS 'P' bit, which is set to inform the WTP it is to use the 802.1p QoS
mechanism. When set, the 'Q' bit is used to inform the WTP which mechanism. When set, the 'Q' bit is used to inform the WTP which
802.1p priority values it is to use. 802.1p priority values it is to use.
The 'D' bit is set to inform the WTP it is to use the DSCP QoS The 'D' bit is set to inform the WTP it is to use the Differentiated
mechanism. When set, the 'I' and 'O' bits are used to inform the WTP Services Code Point (DSCP) QoS mechanism. When set, the 'I' and 'O'
which values it is to use in the inner header, in the station's bits are used to inform the WTP which values it is to use in the
original packet, or the outer header, the latter of which is only inner header, in the station's original packet, or the outer header,
valid when tunneling is enabled. the latter of which is only valid when tunneling is enabled.
When an IEEE 802.11 Update Station QoS message element is received, When an IEEE 802.11 Update Station QoS message element is received,
while the specific 802.1p priority or DSCP values may change for a while the specific 802.1p priority or DSCP values may change for a
given station, known as the station specific policy, the original given station, known as the station specific policy, the original
Tagging Policy (the use of the five bits) remains the same. Tagging Policy (the use of the five bits) remains the same.
The use of the DSCP and 802.1p QoS mechanisms are not mutually The use of the DSCP and 802.1p QoS mechanisms are not mutually
exclusive. An AC MAY request that a WTP use none, one or both types exclusive. An AC MAY request that a WTP use none, one, or both types
of QoS mechanisms at the same time. of QoS mechanisms at the same time.
2.6.1.1. 802.1p Support 2.6.1.1. 802.1p Support
The IEEE 802.11 WTP Quality of Service and IEEE 802.11 Update Station The IEEE 802.11 WTP Quality of Service and IEEE 802.11 Update Station
QoS message elements include the "802.1p Tag" field, which is the QoS message elements include the "802.1p Tag" field, which is the
802.1p priority value. This value is used by the WTP by adding an 802.1p priority value. This value is used by the WTP by adding an
802.1Q header (see [IEEE.802-1Q.2005]) with the priority field set 802.1Q header (see [IEEE.802-1Q.2005]) with the priority field set
according to the policy provided. Note this tagging is only valid according to the policy provided. Note that this tagging is only
for interfaces that support 802.1p. The actual treatment does not valid for interfaces that support 802.1p. The actual treatment does
change for either Split or Local MAC modes, or when tunneling is not change for either Split or Local MAC modes, or when tunneling is
used. The only exception is when tunneling is used, the 802.1Q used. The only exception is when tunneling is used, the 802.1Q
header is added to the outer packet (tunneled) header. The IEEE header is added to the outer packet (tunneled) header. The IEEE
802.11 standard does not permit the station's packet to include an 802.11 standard does not permit the station's packet to include an
802.1Q header. Instead, the QoS mechanisms defined in the IEEE 802.1Q header. Instead, the QoS mechanisms defined in the IEEE
802.11 standard are used by stations to mark a packet's priority. 802.11 standard are used by stations to mark a packet's priority.
When the 'P' bit is set in the Tagging Policy, the 'Q' bit has the When the 'P' bit is set in the Tagging Policy, the 'Q' bit has the
following behavior: following behavior:
Q=1: The WTP marks the priority field in the 802.1Q header to Q=1: The WTP marks the priority field in the 802.1Q header to
either the default, or the station specific 802.1p policy. either the default or the station-specific 802.1p policy.
Q=0: The WTP marks the priority field in the 802.1Q header to the Q=0: The WTP marks the priority field in the 802.1Q header to the
value found in User Priority field of the QoS Control field of the value found in the User Priority field of the QoS Control
IEEE 802.11 header. If the QoS Control field is not present in field of the IEEE 802.11 header. If the QoS Control field is
the IEEE 802.11 header, then the behavior described under 'Q=1' is not present in the IEEE 802.11 header, then the behavior
used. described under 'Q=1' is used.
2.6.1.2. DSCP Support 2.6.1.2. DSCP Support
The IEEE 802.11 WTP Quality of Service and IEEE 802.11 Update Station The IEEE 802.11 WTP Quality of Service and IEEE 802.11 Update Station
QoS message elements also provide a "DSCP Tag", which is used by the QoS message elements also provide a "DSCP Tag", which is used by the
WTP when the 'D' bit is set to mark the DSCP field of both the IPv4 WTP when the 'D' bit is set to mark the DSCP field of both the IPv4
and IPv6 headers (see [RFC2474]). When DSCP is used, the WTP marks and IPv6 headers (see [RFC2474]). When DSCP is used, the WTP marks
the inner packet (the original packet received by the station) when the inner packet (the original packet received by the station) when
the 'I' bit is set. Similarly, the WTP marks the outer packet the 'I' bit is set. Similarly, the WTP marks the outer packet
(tunnel header's DSCP field) when the 'O' bit is set. (tunnel header's DSCP field) when the 'O' bit is set.
When the 'D' bit is set, the treatment of the packet differs based When the 'D' bit is set, the treatment of the packet differs based on
whether the WTP is tunneling the station's packets to the AC. whether the WTP is tunneling the station's packets to the AC.
Tunneling does not occur in a Local MAC mode when the AC has Tunneling does not occur in a Local MAC mode when the AC has
communicated that tunneling is not required, as part of the IEEE communicated that tunneling is not required, as part of the IEEE
802.11 Add WLAN message element Section 6.1. In the case where 802.11 Add WLAN message element, see Section 6.1. In the case where
tunneling is not used, the 'I' and 'O' bits have the following tunneling is not used, the 'I' and 'O' bits have the following
behavior: behaviors:
O=1: This option is invalid when tunneling is not enabled for O=1: This option is invalid when tunneling is not enabled for
station data frames. station data frames.
O=0: This option is invalid when tunneling is not enabled for O=0: This option is invalid when tunneling is not enabled for
station data frames. station data frames.
I=1: The WTP sets the DSCP field in the station's packet to either I=1: The WTP sets the DSCP field in the station's packet to either
the default policy, or the station specific policy if one exists. the default policy or the station-specific policy if one
exists.
I=0: The WTP MUST NOT modify the DSCP field in the station's I=0: The WTP MUST NOT modify the DSCP field in the station's
packet. packet.
For Split MAC mode, or Local MAC with tunneling enabled, the WTP For Split MAC mode, or Local MAC with tunneling enabled, the WTP
needs to contend with both the inner packet (the station's original needs to contend with both the inner packet (the station's original
packet), as well as the tunnel header (added by the WTP). In this packet) as well as the tunnel header (added by the WTP). In this
mode of operation, the bits are treated as follows: mode of operation, the bits are treated as follows:
O=1: The WTP sets the DSCP field in the tunnel header to either the O=1: The WTP sets the DSCP field in the tunnel header to either the
default policy, or the station specific policy if one exists. default policy or the station specific policy if one exists.
O=0: The WTP sets the DSCP field in the tunnel header to the value O=0: The WTP sets the DSCP field in the tunnel header to the value
found in the inner packet's DSCP field. If encryption services found in the inner packet's DSCP field. If encryption
are provided by the AC (see Section 6.15), the packet is services are provided by the AC (see Section 6.15), the packet
encrypted, therefore the WTP cannot access the inner DSCP field, is encrypted; therefore, the WTP cannot access the inner DSCP
in which case it uses the behavior described when the 'O' bit is field, in which case it uses the behavior described when the
set. This occurs also if the inner packet is not IPv4 or IPv6, 'O' bit is set. This occurs also if the inner packet is not
and thus does not have a DSCP field. IPv4 or IPv6, and thus does not have a DSCP field.
I=1: The WTP sets the DSCP field in the station's packet to either I=1: The WTP sets the DSCP field in the station's packet to either
the default policy, or the station specific policy if one exists. the default policy or the station-specific policy if one
If encryption services are provided by the AC (see Section 6.15), exists. If encryption services are provided by the AC (see
the packet is encrypted, therefore the WTP cannot access the inner Section 6.15), the packet is encrypted; therefore, the WTP
DSCP field, in which case it uses the behavior described when the cannot access the inner DSCP field, in which case it uses the
'I' bit is not set. This occurs also if the inner packet is not behavior described when the 'I' bit is not set. This occurs
IPv4 or IPv6, and thus does not have a DSCP field. also if the inner packet is not IPv4 or IPv6, and thus does
not have a DSCP field.
I=0: The WTP MUST NOT modify the DSCP field in the station's I=0: The WTP MUST NOT modify the DSCP field in the station's
packet. packet.
The CAPWAP protocol supports the Explicit Congestion Notification The CAPWAP protocol supports the Explicit Congestion Notification
(ECN) bits [RFC3168]. Additional details on ECN support can be found (ECN) bits [RFC3168]. Additional details on ECN support can be found
[I-D.ietf-capwap-protocol-specification]. in [RFC5415].
2.6.2. IEEE 802.11 MAC Management Messages 2.6.2. IEEE 802.11 MAC Management Messages
It is recommended that IEEE 802.11 MAC Management frames be sent by It is recommended that IEEE 802.11 MAC Management frames be sent by
both the AC and the WTP with appropriate Quality of Service values, both the AC and the WTP with appropriate Quality of Service values,
listed below, to ensure that congestion in the network minimizes listed below, to ensure that congestion in the network minimizes
occurrences of packet loss. Note that the QoS Mechanism specified in occurrences of packet loss. Note that the QoS Mechanism specified in
Tagging Policy is used as specified by the AC in the IEEE 802.11 WTP the Tagging Policy is used as specified by the AC in the IEEE 802.11
Quality of Service message element (see Section 6.22). However, the WTP Quality of Service message element (see Section 6.22). However,
station specific policy is not used for IEEE 802.11 MAC Management the station-specific policy is not used for IEEE 802.11 MAC
frames. Management frames.
802.1p: The precedence value of 7 (decimal) SHOULD be used for all 802.1p: The precedence value of 7 (decimal) SHOULD be used for all
IEEE 802.11 MAC management frames, except for Probe Requests which IEEE 802.11 MAC management frames, except for Probe
SHOULD use 4. Requests, which SHOULD use 4.
DSCP: All IEEE 802.11 MAC management frames SHOULD use the CS6 per- DSCP: All IEEE 802.11 MAC management frames SHOULD use the CS6
hop behavior (see [RFC2474]), while IEEE 802.11 Probe Requests per- hop behavior (see [RFC2474]), while IEEE 802.11 Probe
should use the Low Drop Assured Forwarding per-hop behavior (see Requests should use the Low Drop Assured Forwarding per-hop
[RFC2598]). behavior (see [RFC3246]).
2.7. Run State Operation 2.7. Run State Operation
The Run state is the normal state of operation for the CAPWAP The Run state is the normal state of operation for the CAPWAP
protocol in both the WTP and the AC. protocol in both the WTP and the AC.
When the WTP receives a WLAN Configuration Request message (see When the WTP receives a WLAN Configuration Request message (see
Section 3.1), it MUST respond with a WLAN Configuration Response Section 3.1), it MUST respond with a WLAN Configuration Response
message (see Section 3.2) and it remains in the Run state. message (see Section 3.2), and it remains in the Run state.
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.5 in [I-D.ietf-capwap-protocol-specification] for See Section 4.5 in [RFC5415] for CAPWAP Control message definitions
CAPWAP Control message definitions and the derivation of the Message and the derivation of the Message Type value from the IANA Enterprise
Type value from the IANA Enterprise number. 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 3398913 IEEE 802.11 WLAN Configuration Request 3398913
IEEE 802.11 WLAN Configuration Response 3398914 IEEE 802.11 WLAN Configuration Response 3398914
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 administrative process (e.g., deleting a WLAN), or either some manual administrative 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 Response message (see Section 8.5 in Configuration Update Response message (see Section 8.5 in [RFC5415])
[I-D.ietf-capwap-protocol-specification]) has been received by the has been received by the AC.
AC.
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 Service Set Identifiers that is capable of supporting up to 16 Service Set Identifiers
(SSIDs), could accept up to 16 IEEE 802.11 WLAN Configuration Request (SSIDs), could accept up to 16 IEEE 802.11 WLAN Configuration Request
messages that include the Add WLAN message element. messages that include the Add 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.
skipping to change at page 24, line 12 skipping to change at page 23, line 4
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.
o IEEE 802.11 Information Element, see Section 6.6 o IEEE 802.11 Information Element, see Section 6.6
o Vendor Specific Payload, see o Vendor-Specific Payload, see [RFC5415]
[I-D.ietf-capwap-protocol-specification]
3.2. IEEE 802.11 WLAN Configuration Response 3.2. IEEE 802.11 WLAN Configuration Response
The IEEE 802.11 WLAN Configuration Response message is sent by the The IEEE 802.11 WLAN Configuration Response message is sent by the
WTP to the AC. It is used to acknowledge receipt of an IEEE 802.11 WTP to the AC. It is used to acknowledge receipt of an IEEE 802.11
WLAN Configuration Request message, and to indicate that the WLAN Configuration Request message, and to indicate that the
requested configuration was successfully applied, or that an error requested configuration was successfully applied or that an error
related to the processing of the IEEE 802.11 WLAN Configuration related to the processing of the IEEE 802.11 WLAN Configuration
Request message occurred on the WTP. Request message occurred on the WTP.
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.6.34 in o Result Code, see Section 4.6.34 in [RFC5415]
[I-D.ietf-capwap-protocol-specification]
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
o Vendor Specific Payload, see o Vendor-Specific Payload, see [RFC5415]
[I-D.ietf-capwap-protocol-specification]
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: This optional CAPWAP header Optional Wireless Specific Information: This optional CAPWAP header
field (see Section 4.3 in field (see Section 4.3 in [RFC5415]) is only used with CAPWAP data
[I-D.ietf-capwap-protocol-specification]) is only used with CAPWAP messages, and it serves two purposes, depending upon the direction
data messages, and it serves two purposes, depending upon the of the message. For messages from the WTP to the AC, the field
direction of the message. For messages from the WTP to the AC, uses the format described in the "IEEE 802.11 Frame Info" field
the field uses the format described in the "IEEE 802.11 Frame (see below). However, for messages sent by the AC to the WTP, the
Info" field (see below). However, for messages sent by the AC to format used is described in the "Destination WLANs" field (also
the WTP, the format used is described in the "Destination WLANs" defined below).
field (also defined below).
Note that in both cases, the two optional headers fit in the Note that in both cases, the two optional headers fit in the
"Data" field of the Wireless Specific Information header. "Data" field of the Wireless Specific Information header.
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
frame. frame.
The IEEE 802.11 Frame Info field has the following format: The IEEE 802.11 Frame Info field has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RSSI | SNR | Data Rate | | RSSI | SNR | Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RSSI: RSSI is a signed, 8-bit value. It is the received signal RSSI: Received Signal Strength Indication (RSSI) is a signed,
strength indication, in dBm. 8-bit value. It is the received signal strength indication, in
dBm.
SNR: SNR is a signed, 8-bit value. It is the signal to noise SNR: SNR is a signed, 8-bit value. It is the signal-to-noise
ratio of the received IEEE 802.11 frame, in dB. ratio of the received IEEE 802.11 frame, in dB.
Data Rate: The data rate field is a 16 bit unsigned value. The Data Rate: The data rate field is a 16-bit unsigned value. The
data rate field is a 16 bit unsigned value expressing the data data rate field is a 16-bit unsigned value expressing the data
rate of the packets received by the WTP in units of 0.1 Mbps. rate of the packets received by the WTP in units of 0.1 Mbps.
For instance, a packet received at 5.5Mbps would be set to 55, For instance, a packet received at 5.5Mbps would be set to 55,
while 11Mbps would be set to 110. while 11Mbps would be set to 110.
Destination WLANs The Destination WLANs field is used to specify the Destination WLANs: The Destination WLANs field is used to specify
target WLANs for a given frame, and is only used with broadcast the target WLANs for a given frame, and is only used with
and multicast frames. This field allows the AC to transmit a broadcast and multicast frames. This field allows the AC to
single broadcast or multicast frame to the WTP, and allows the WTP transmit a single broadcast or multicast frame to the WTP and
to perform the necessary frame replication. The field uses the allows the WTP to perform the necessary frame replication. The
following format: field uses the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WLAN ID bitmap | Reserved | | WLAN ID bitmap | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
WLAN ID bitmap: This bit field indicates the WLAN ID (see WLAN ID bitmap: This bit field indicates the WLAN ID (see
Section 6.1) on which the WTP will transmit the included frame. Section 6.1) on which the WTP will transmit the included frame.
For instance, if a multicast packet is to be transmitted on For instance, if a multicast packet is to be transmitted on
WLANs 1 and 3, the bits for WLAN 1 and 3 of this field would be WLANs 1 and 3, the bits for WLAN 1 and 3 of this field would be
enabled. WLAN 1 is represented by bit 15 in the figure above, enabled. WLAN 1 is represented by bit 15 in the figure above,
or the least significant bit, while WLAN 16 would be or the least significant bit, while WLAN 16 would be
represented by bit zero (0), or the most significant bit, in represented by bit zero (0), or the most significant bit, in
the figure. This field is to be set to all zeroes for unicast the figure. This field is to be set to all zeroes for unicast
packets and is unused if the WTP is not providing IEEE 802.11 packets and is unused if the WTP is not providing IEEE 802.11
encryption. encryption.
skipping to change at page 27, line 5 skipping to change at page 25, line 21
the figure. This field is to be set to all zeroes for unicast the figure. This field is to be set to all zeroes for unicast
packets and is unused if the WTP is not providing IEEE 802.11 packets and is unused if the WTP is not providing IEEE 802.11
encryption. encryption.
Reserved: All implementations complying with this protocol MUST Reserved: All implementations complying with this protocol MUST
set to zero any bits that are reserved in the version of the set to zero any bits that are reserved in the version of the
protocol supported by that implementation. Receivers MUST protocol supported by that implementation. Receivers MUST
ignore all bits not defined for the version of the protocol ignore all bits not defined for the version of the protocol
they support. they support.
5. CAPWAP Control Message bindings 5. CAPWAP Control Message Bindings
This section describes the IEEE 802.11 specific message elements This section describes the IEEE 802.11-specific message elements
included in CAPWAP Control Messages. included in CAPWAP Control Messages.
5.1. Discovery Request Message 5.1. Discovery Request Message
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 Discovery Request Message. in the CAPWAP Discovery Request 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.2. Discovery Response Message 5.2. Discovery Response Message
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 Discovery Response Message. in the CAPWAP Discovery 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.3. Primary Discovery Request Message 5.3. Primary Discovery Request Message
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 Primary Discovery Request Message. in the CAPWAP Primary Discovery Request 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.4. Primary Discovery Response Message 5.4. Primary Discovery Response Message
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 Primary Discovery Response Message. in the CAPWAP Primary Discovery 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.5. Join Request Message 5.5. Join Request Message
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 Request Message. in the CAPWAP Join Request 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.6. Join Response Message 5.6. Join Response Message
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 Request Message 5.7. Configuration Status 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 Status Request Message. More than one of in the CAPWAP Configuration Status 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 Orthogonal Frequency Division Multiplexing (OFDM)
Control, see Section 6.10
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 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
skipping to change at page 29, line 4 skipping to change at page 27, line 19
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
o IEEE 802.11 Rate Set, see Section 6.11 o IEEE 802.11 Rate Set, see Section 6.11
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
o IEEE 802.11 Rate Set, see Section 6.11 o IEEE 802.11 Rate Set, see Section 6.11
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 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 be included
the CAPWAP Station Configuration Request message. More than one of in the CAPWAP Station Configuration Request message. More than one
each message element listed MAY be included. of 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 IEEE 802.11 Station QoS Profile, see Section 6.14 o IEEE 802.11 Station QoS Profile, see Section 6.14
o IEEE 802.11 Update Station Qos, see Section 6.20 o IEEE 802.11 Update Station Qos, see Section 6.20
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 element MAY be 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 in the CAPWAP WTP Event Request message. More than one of each
message element listed MAY be included. message 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
this section. this section.
IEEE 802.11 Message Element Type Value IEEE 802.11 Message Element Type Value
IEEE 802.11 Add WLAN 1024 IEEE 802.11 Add WLAN 1024
IEEE 802.11 Antenna 1025 IEEE 802.11 Antenna 1025
IEEE 802.11 Assigned WTP BSSID 1026 IEEE 802.11 Assigned WTP BSSID 1026
IEEE 802.11 Delete WLAN 1027 IEEE 802.11 Delete WLAN 1027
IEEE 802.11 Direct Sequence Control 1028 IEEE 802.11 Direct Sequence Control 1028
IEEE 802.11 Information Element 1029 IEEE 802.11 Information Element 1029
skipping to change at page 32, line 4 skipping to change at page 29, line 48
Figure 8: IEEE 802.11 Binding Message Elements Figure 8: IEEE 802.11 Binding Message Elements
6.1. IEEE 802.11 Add WLAN 6.1. IEEE 802.11 Add WLAN
The IEEE 802.11 Add WLAN message element is used by the AC to define The IEEE 802.11 Add WLAN message element is used by the AC to define
a WLAN on the WTP. The inclusion of this message element MUST also a WLAN on the WTP. The inclusion of this message element MUST also
include IEEE 802.11 Information Element message elements, containing include IEEE 802.11 Information Element message elements, containing
the following IEEE 802.11 IEs: the following IEEE 802.11 IEs:
Power Constraint information element Power Constraint information element
EDCA Parameter Set information element EDCA Parameter Set information element
QoS Capability information element QoS Capability information element
WPA information element [WPA] WPA information element [WPA]
RSN information element RSN information element
WMM information element [WMM] WMM information element [WMM]
These IEEE 802.11 information elements are stored by the WTP and These IEEE 802.11 Information Elements are stored by the WTP and
included in any Probe Responses and Beacons generated, as specified included in any Probe Responses and Beacons generated, as specified
in the IEEE 802.11 standard [IEEE.802-11.2007]. If present, the RSN in the IEEE 802.11 standard [IEEE.802-11.2007]. If present, the RSN
information element is sent with the IEEE 802.11 Add WLAN message Information Element is sent with the IEEE 802.11 Add WLAN message
element to instruct the WTP on the usage of the Key field. element to instruct the WTP on the usage of the Key field.
If cryptographic services are provided at the WTP, the WTP MUST If cryptographic services are provided at the WTP, the WTP MUST
observe the algorithm dictated in the Group Cipher Suite field of the observe the algorithm dictated in the Group Cipher Suite field of the
RSN information element sent by the AC. The RSN Information Element RSN Information Element sent by the AC. The RSN Information Element
is used to communicate any supported algorithm, including WEP, TKIP is used to communicate any supported algorithm, including WEP,
and AES-CCMP. In the case of static WEP keys, the RSN Information Temporal Key Integrity Protocol (TKIP) and AES-CCMP. In the case of
Element is still used to indicate the cryptographic algorithm even static WEP keys, the RSN Information Element is still used to
though no key exchange occurred. indicate the cryptographic algorithm even though no key exchange
occurred.
An AC MAY include additional information elements as desired. The An AC MAY include additional Information Elements as desired. The
message element uses the following format: message element uses the following format:
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 | Capability | | Radio ID | WLAN ID | Capability |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Index | Key Status | Key Length | | Key Index | Key Status | Key Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key... | | Key... |
skipping to change at page 33, line 4 skipping to change at page 30, line 45
| Key... | | Key... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group TSC | | Group TSC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group TSC | QoS | Auth Type | | Group TSC | QoS | Auth Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Mode | Tunnel Mode | Suppress SSID | SSID ... | MAC Mode | Tunnel Mode | Suppress SSID | SSID ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1024 for IEEE 802.11 Add WLAN Type: 1024 for IEEE 802.11 Add WLAN
Length: >= 20 Length: >= 20
Radio ID: An 8-bit value representing the radio, whose value is Radio ID: An 8-bit value representing the radio, whose value is
between one (1) and 31. between one (1) and 31.
WLAN ID: An 8-bit value specifying the WLAN Identifier. The value WLAN ID: An 8-bit value specifying the WLAN Identifier. The value
MUST be between one (1) and 16. MUST be between one (1) and 16.
Capability: A 16-bit value containing the capability information Capability: A 16-bit value containing the Capability information
field to be advertised by the WTP in the Probe Request and Beacon field to be advertised by the WTP in the Probe Request and Beacon
frames. Each bit of the Capability field represents a different frames. Each bit of the Capability field represents a different
WTP capability, which are described in detail in WTP capability, which are described in detail in
[IEEE.802-11.2007]. The format of the field is: [IEEE.802-11.2007]. The format of the field is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E|I|C|F|P|S|B|A|M|Q|T|D|V|O|K|L| |E|I|C|F|P|S|B|A|M|Q|T|D|V|O|K|L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 33, line 42 skipping to change at page 31, line 38
[IEEE.802-11.2007]. [IEEE.802-11.2007].
F (CF-Poll Request): The AC sets the CF-Poll Request subfield F (CF-Poll Request): The AC sets the CF-Poll Request subfield
based on the table found in [IEEE.802-11.2007]. based on the table found in [IEEE.802-11.2007].
P (Privacy): The AC sets the Privacy subfield based on the P (Privacy): The AC sets the Privacy subfield based on the
confidentiality requirements of the WLAN, as defined in confidentiality requirements of the WLAN, as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
S (Short Preamble): The AC sets the Short Preamble subfield S (Short Preamble): The AC sets the Short Preamble subfield
based on whether the use of short preambles are permitted on based on whether the use of short preambles is permitted on the
the WLAN, as defined in [IEEE.802-11.2007]. WLAN, as defined in [IEEE.802-11.2007].
B (PBCC): The AC sets the Packet Binary Convolutional Code B (PBCC): The AC sets the Packet Binary Convolutional Code
(PBCC) modulation option subfield based on whether the use of (PBCC) modulation option subfield based on whether the use of
PBCC is permitted on the WLAN, as defined in PBCC is permitted on the WLAN, as defined in [IEEE.802-11.2007].
[IEEE.802-11.2007].
A (Channel Agility): The AC sets the Channel Agility subfield A (Channel Agility): The AC sets the Channel Agility subfield
based on whether the WTP is capable of supporting the High Rate based on whether the WTP is capable of supporting the High Rate
Direct Sequence Spread Spectrum (HR/DSSS), as defined in Direct Sequence Spread Spectrum (HR/DSSS), as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
M (Spectrum Management): The AC sets the Spectrum Management M (Spectrum Management): The AC sets the Spectrum Management
subfield according to the value of the subfield according to the value of the
dot11SpectrumManagementRequired MIB variable, as defined in dot11SpectrumManagementRequired MIB variable, as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
Q (QOS): The AC sets the Quality of Service (QOS) subfield based Q (QoS): The AC sets the Quality of Service (QoS) subfield based
on the table found in [IEEE.802-11.2007]. on the table found in [IEEE.802-11.2007].
T (Short Slot Time): The AC sets the Short Slot Timesubfield T (Short Slot Time): The AC sets the Short Slot Timesubfield
according to the value of the WTP's currently used slot time according to the value of the WTP's currently used slot time
value, as defined in [IEEE.802-11.2007]. value, as defined in [IEEE.802-11.2007].
D (APSD): The AC sets the APSD subfield according to the value D (APSD): The AC sets the Automatic Power Save Delivery (APSD)
of the dot11APSDOptionImplemented Management Information Base subfield according to the value of the
(MIB) variable, as defined in [IEEE.802-11.2007]. dot11APSDOptionImplemented Management Information Base (MIB)
variable, as defined in [IEEE.802-11.2007].
V (Reserved): The AC sets the Reserved subfield to zero, as V (Reserved): The AC sets the Reserved subfield to zero, as
defined in [IEEE.802-11.2007]. defined in [IEEE.802-11.2007].
O (DSSS-OFDM): The AC sets the DSSS-OFDM subfield to indicate O (DSSS-OFDM): The AC sets the DSSS-OFDM subfield to indicate
the use of Direct Sequence Spread Spectrum with Orthogonal the use of Direct Sequence Spread Spectrum with Orthogonal
Frequency Division Multiplexing (DSSS-OFDM), as defined in Frequency Division Multiplexing (DSSS-OFDM), as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
K (Delayed Block ACK): The AC sets the Delayed Block ACK K (Delayed Block ACK): The AC sets the Delayed Block ACK
subfield according to the value of the subfield according to the value of the
dot11DelayedBlockAckOptionImplemented MIB variable, as defined dot11DelayedBlockAckOptionImplemented MIB variable, as defined
in [IEEE.802-11.2007]. in [IEEE.802-11.2007].
L (Immediate Block ACK): The AC sets the Delayed Block ACK L (Immediate Block ACK): The AC sets the Delayed Block ACK
subfield according to the value of the subfield according to the value of the
dot11ImmediateBlockAckOptionImplemented MIB variable, as dot11ImmediateBlockAckOptionImplemented MIB variable, as defined
defined in [IEEE.802-11.2007]. in [IEEE.802-11.2007].
Key-Index: The Key Index associated with the key. Key-Index: The Key Index associated with the key.
Key Status: A 1 byte value that specifies the state and usage of Key Status: A 1-byte value that specifies the state and usage of
the key that has been included. Note this field is ignored if the the key that has been included. Note this field is ignored if the
Key Length field is set to zero (0). The following values Key Length field is set to zero (0). The following values
describe the key usage and its status: describe the key usage and its status:
0 - A value of zero, with the inclusion of the RSN Information 0 - A value of zero, with the inclusion of the RSN Information
Element means that the WLAN uses per-station encryption keys, Element means that the WLAN uses per-station encryption keys,
and therefore the key in the 'Key' field is only used for and therefore the key in the 'Key' field is only used for
multicast traffic. multicast traffic.
1 - When set to one, the WLAN employs a shared Wired Equivalent 1 - When set to one, the WLAN employs a shared Wired Equivalent
Privacy (WEP) key, also known as a static WEP key, and uses the Privacy (WEP) key, also known as a static WEP key, and uses
encryption key for both unicast and multicast traffic for all the encryption key for both unicast and multicast traffic for
stations. all stations.
2 - The value of 2 indicates that the AC will begin rekeying the 2 - The value of 2 indicates that the AC will begin rekeying the
GTK with the STA's in the BSS. It is only valid when IEEE GTK with the STA's in the BSS. It is only valid when IEEE
802.11 is enabled as the security policy for the BSS. 802.11 is enabled as the security policy for the BSS.
3 - The value of 3 indicates that the AC has completed rekeying 3 - The value of 3 indicates that the AC has completed rekeying
the GTK and broadcast packets no longer need to be duplicated the GTK and broadcast packets no longer need to be duplicated
and transmitted with both GTK's. and transmitted with both GTK's.
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 Session Key, whose length is known via the key length field, Key: A Session Key, whose length is known via the Key Length field,
used to provide data privacy. For encryption schemes that employ used to provide data privacy. For encryption schemes that employ
a separate encryption key for unicast and multicast traffic, the a separate encryption key for unicast and multicast traffic, the
key included here only applies to multicast frames, and the cipher key included here only applies to multicast frames, and the cipher
suite is specified in an accompanied RSN Information Element. In suite is specified in an accompanied RSN Information Element. In
these scenarios, the key and cipher information is communicated these scenarios, the key and cipher information is communicated
via the Add Station message element, see Section 4.6.8 in via the Add Station message element, see Section 4.6.8 in
[I-D.ietf-capwap-protocol-specification] and the IEEE 802.11 [RFC5415] and the IEEE 802.11 Station Session Key message element,
Station Session Key message element, see Section 6.15. When used see Section 6.15. When used with WEP, the key field includes the
with WEP, the key field includes the broadcast key. When used broadcast key. When used with CCMP, the Key field includes the
with CCMP, the Key field includes the 128-bit Group Temporal Key. 128-bit Group Temporal Key. When used with TKIP, the Key field
When used with TKIP, the Key field includes the 256-bit Group includes the 256-bit Group Temporal Key (which consists of a 128-
Temporal Key (which consists of a 128-bit key used as input for bit key used as input for TKIP key mixing, and two 64-bit keys
TKIP key mixing, and two 64-bit keys used for Michael). used for Michael).
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 (TSC) 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.
The following enumerated values are supported: The following enumerated values are supported:
0 - Best Effort 0 - Best Effort
1 - Video 1 - Video
2 - Voice 2 - Voice
3 - Background 3 - Background
Auth Type: An 8-bit value specifying the supported authentication Auth Type: An 8-bit value specifying the supported authentication
type. type.
The following enumerated values are supported: The following enumerated values are supported:
0 - Open System 0 - Open System
skipping to change at page 36, line 23 skipping to change at page 34, line 18
Auth Type: An 8-bit value specifying the supported authentication Auth Type: An 8-bit value specifying the supported authentication
type. type.
The following enumerated values are supported: The following enumerated 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 mode. 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.6.43 in during the discovery process (see Section 4.6.43 in [RFC5415]).
[I-D.ietf-capwap-protocol-specification]). The following The following enumerated values are supported:
enumerated 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.6.42 in [I-D.ietf-capwap-protocol-specification]). All IEEE 4.6.42 in [RFC5415]). All IEEE 802.11 management frames MUST be
802.11 management frames MUST be tunneled using 802.11 Tunnel tunneled using 802.11 Tunnel mode. The following enumerated
mode. The following enumerated values are supported: 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.4.2 in in 802.3 format (see Section 4.4.2 in [RFC5415]). Note that
[I-D.ietf-capwap-protocol-specification]). Note that this this option MUST NOT be selected with Split MAC mode.
option MUST NOT be selected with Split-MAC mode.
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 Suppress SSID: A boolean indicating whether the SSID is to be
advertised by the WTP. A value of zero suppresses the SSID in the advertised by the WTP. A value of zero suppresses 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
advertised by the WTP for this WLAN. The SSID field contains any advertised by the WTP for this WLAN. The SSID field contains any
ASCII character and MUST NOT exceed 32 octets in length, as ASCII character and MUST NOT exceed 32 octets in length, as
defined in [IEEE.802-11.2007]. defined in [IEEE.802-11.2007].
6.2. IEEE 802.11 Antenna 6.2. IEEE 802.11 Antenna
skipping to change at page 37, line 41 skipping to change at page 35, line 33
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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, whose Radio ID: An 8-bit value representing the radio to configure, whose
value is between one (1) and 31. value is between one (1) and 31.
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 receiver diversity. The value of this field is the same
the IEEE 802.11 dot11DiversitySelectionRx MIB element, see as the IEEE 802.11 dot11DiversitySelectionRx MIB element, see
[IEEE.802-11.2007]. The following enumerated values are [IEEE.802-11.2007]. The following enumerated values are
supported: 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) receiving antenna)
Combiner: An 8-bit value specifying the combiner selection. The Combiner: An 8-bit value specifying the combiner selection. The
following enumerated values are supported: following enumerated values are supported:
1 - Sectorized (Left) 1 - Sectorized (Left)
2 - Sectorized (Right) 2 - Sectorized (Right)
3 - Omni 3 - Omni
4 - Multiple Input/Multiple Output (MIMO) 4 - Multiple Input/Multiple Output (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 in the IEEE 802.11 dot11CurrentTxAntenna MIB element (see
[IEEE.802-11.2007]). [IEEE.802-11.2007]).
Antenna Selection: One 8-bit antenna configuration value per Antenna Selection: One 8-bit antenna configuration value per
skipping to change at page 41, line 28 skipping to change at page 39, line 14
Type: 1029 for IEEE 802.11 Information Element Type: 1029 for IEEE 802.11 Information Element
Length: >= 4 Length: >= 4
Radio ID: An 8-bit value representing the radio, whose value is Radio ID: An 8-bit value representing the radio, whose value is
between one (1) and 31. between one (1) and 31.
WLAN ID: An 8-bit value specifying the WLAN Identifier. The value WLAN ID: An 8-bit value specifying the WLAN Identifier. The value
MUST be between one (1) and 16. MUST be between one (1) and 16.
B: When set, the WTP is to include the information element in IEEE B: When set, the WTP is to include the Information Element in IEEE
802.11 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.
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.
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
The IEEE 802.11 MAC Operation message element is sent by the AC to The IEEE 802.11 MAC Operation message element is sent by the AC to
set the IEEE 802.11 MAC parameters on the WTP, and contains the set the IEEE 802.11 MAC parameters on the WTP, and contains the
following fields. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 42, line 20 skipping to change at page 40, line 4
| Short Retry | Long Retry | Fragmentation Threshold | | Short Retry | Long Retry | Fragmentation Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tx MSDU Lifetime | | Tx MSDU Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rx MSDU Lifetime | | Rx MSDU Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1030 for IEEE 802.11 MAC Operation Type: 1030 for IEEE 802.11 MAC Operation
Length: 16 Length: 16
Radio ID: An 8-bit value representing the radio to configure, whose Radio ID: An 8-bit value representing the radio to configure, whose
value is between one (1) and 31. value is between one (1) and 31.
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.
RTS Threshold: This attribute indicates the number of octets in an RTS Threshold: This attribute indicates the number of octets in an
MAC Protocol Data Unit (MPDU), below which an Request To Send/ MAC Protocol Data Unit (MPDU), below which a Request To Send/Clear
Clear To Send (RTS/CTS) handshake MUST NOT be performed. An RTS/ To Send (RTS/CTS) handshake MUST NOT be performed. An RTS/CTS
CTS handshake MUST be performed at the beginning of any frame handshake MUST be performed at the beginning of any frame exchange
exchange sequence where the MPDU is of type Data or Management, sequence where the MPDU is of type Data or Management, the MPDU
the MPDU has an individual address in the Address1 field, and the has an individual address in the Address1 field, and the length of
length of the MPDU is greater than this threshold. Setting this the MPDU is greater than this threshold. Setting this attribute
attribute to be larger than the maximum MSDU size MUST have the to be larger than the maximum MSDU size MUST have the effect of
effect of turning off the RTS/CTS handshake for frames of Data or turning off the RTS/CTS handshake for frames of Data or Management
Management type transmitted by this STA. Setting this attribute type transmitted by this STA. Setting this attribute to zero MUST
to zero MUST have the effect of turning on the RTS/CTS handshake have the effect of turning on the RTS/CTS handshake for all frames
for all frames of Data or Management type transmitted by this STA. of Data or Management type transmitted by this STA. The default
The default value of this attribute MUST be 2347. The value of value of this attribute MUST be 2347. The value of this field
this field comes from the IEEE 802.11 dot11RTSThreshold MIB comes from the IEEE 802.11 dot11RTSThreshold MIB element, (see
element, (see [IEEE.802-11.2007]). [IEEE.802-11.2007]).
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 [IEEE.802-11.2007]). dot11ShortRetryLimit MIB element, (see [IEEE.802-11.2007]).
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
skipping to change at page 43, line 27 skipping to change at page 41, line 9
Unit (MMPDU) MUST be fragmented when the resulting frame has an Unit (MMPDU) MUST be fragmented when the resulting frame has an
individual address in the Address1 field, and the length of the 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
[IEEE.802-11.2007]). [IEEE.802-11.2007]).
Tx MSDU Lifetime: This attribute specifies the elapsed time in TU, Tx MSDU Lifetime: This attribute specifies the elapsed time in Time
after the initial transmission of an MSDU, after which further Units (TUs), after the initial transmission of an MSDU, after
attempts to transmit the MSDU MUST be terminated. The default which further attempts to transmit the MSDU MUST be terminated.
value of this attribute MUST be 512. The value of this field The default value of this attribute MUST be 512. The value of
comes from the IEEE 802.11 dot11MaxTransmitMSDULifetime MIB this field comes from the IEEE 802.11 dot11MaxTransmitMSDULifetime
element, (see [IEEE.802-11.2007]). MIB element, (see [IEEE.802-11.2007]).
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 [IEEE.802-11.2007]). element, (see [IEEE.802-11.2007]).
6.8. IEEE 802.11 MIC Countermeasures 6.8. IEEE 802.11 MIC Countermeasures
skipping to change at page 45, line 10 skipping to change at page 42, line 36
Length: 8 Length: 8
Radio ID: An 8-bit value representing the radio to configure, whose Radio ID: An 8-bit value representing the radio to configure, whose
value is between one (1) and 31. value is between one (1) and 31.
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 Channel #: This attribute indicates the value of the lowest
channel number in the sub-band for the associated domain country channel number in the sub-band 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 [IEEE.802-11.2007]). dot11FirstChannelNumber MIB element (see [IEEE.802-11.2007]).
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 sub-band for the associated number of channels allowed in the sub-band for the associated
domain country string (see Section 6.23). The value of this field domain country string (see Section 6.23). The value of this field
comes from the IEEE 802.11 dot11NumberofChannels MIB element (see comes from the IEEE 802.11 dot11NumberofChannels MIB element (see
[IEEE.802-11.2007]). [IEEE.802-11.2007]).
skipping to change at page 46, line 16 skipping to change at page 43, line 39
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 from the IEEE 802.11 dot11CurrentFrequency MIB element (see
[IEEE.802-11.2007]). [IEEE.802-11.2007]).
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 Unlicensed National Information
from the IEEE 802.11 dot11FrequencyBandsSupported MIB element (see Infrastructure (U-NII) bands. The value of this field comes from
the IEEE 802.11 dot11FrequencyBandsSupported MIB element (see
[IEEE.802-11.2007]), coded as a bit field, whose values are: [IEEE.802-11.2007]), coded as a bit field, whose values are:
Bit 0 - capable of operating in the 5.15-5.25 GHz band Bit 0 - capable of operating in the 5.15-5.25 GHz band
Bit 1 - capable of operating in the 5.25-5.35 GHz band Bit 1 - capable of operating in the 5.25-5.35 GHz band
Bit 2 - capable of operating in the 5.725-5.825 GHz band Bit 2 - capable of operating in the 5.725-5.825 GHz band
Bit 3 - capable of operating in the 5.47-5.725 GHz band Bit 3 - capable of operating in the 5.47-5.725 GHz band
Bit 4 - capable of operating in the lower Japanese 5.25 GHz band Bit 4 - capable of operating in the lower Japanese 5.25 GHz band
Bit 5 - capable of operating in the 5.03-5.091 GHz band Bit 5 - capable of operating in the 5.03-5.091 GHz band
Bit 6 - capable of operating in the 4.94-4.99 GHz band Bit 6 - capable of operating in the 4.94-4.99 GHz band
For example, for an implementation capable of operating in the For example, for an implementation capable of operating in the
5.15-5.35 GHz bands this attribute would take the value 3. 5.15-5.35 GHz 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 [IEEE.802-11.2007]). IEEE 802.11 dot11TIThreshold MIB element (see [IEEE.802-11.2007]).
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
skipping to change at page 48, line 4 skipping to change at page 45, line 28
| TKIP Local MIC Failures | | TKIP Local MIC Failures |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TKIP Remote MIC Failures | | TKIP Remote MIC Failures |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CCMP Replays | | CCMP Replays |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CCMP Decrypt Errors | | CCMP Decrypt Errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TKIP Replays | | TKIP Replays |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1035 for IEEE 802.11 RSNA Error Report From Station Type: 1035 for IEEE 802.11 RSNA Error Report From Station
Length: 40 Length: 40
Client MAC Address: The Client MAC Address of the station. Client MAC Address: The Client MAC Address of the station.
BSSID: The BSSID on which the failures are being reported on. BSSID: The BSSID on which the failures are being reported.
Radio ID: The Radio Identifier, whose value is between one (1) and Radio ID: The Radio Identifier, whose value is between one (1) and
31, typically refers to some interface index on the WTP 31, typically refers to some interface index on the WTP.
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.
The value MUST be between one (1) and 16. The value MUST be between one (1) and 16.
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 Temporal TKIP ICV Errors: A 32-bit value representing the number of Temporal
skipping to change at page 49, line 43 skipping to change at page 47, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1036 for IEEE 802.11 Station Type: 1036 for IEEE 802.11 Station
Length: >= 14 Length: >= 14
Radio ID: An 8-bit value representing the radio, whose value is Radio ID: An 8-bit value representing the radio, whose value is
between one (1) and 31. between one (1) and 31.
Association ID: A 16-bit value specifying the IEEE 802.11 Association ID: A 16-bit value specifying the IEEE 802.11
Association Identifier Association Identifier.
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.
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. The value WLAN ID: An 8-bit value specifying the WLAN Identifier. The value
MUST be between one (1) and 16. MUST be between one (1) and 16.
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 [IEEE.802-11.2007]). dot11OperationalRateSet MIB element (see [IEEE.802-11.2007]).
This field MUST NOT exceed 126 octets and specifies the set of This field MUST NOT exceed 126 octets and specifies the set of
data rates at which the station may transmit data, where each data rates at which the station may transmit data, where each
octet represents a data rate. octet represents a data rate.
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.
skipping to change at page 50, line 38 skipping to change at page 48, line 16
(see Section 6.13) message element. (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 | Reserved |8021p| | MAC Address | Reserved |8021p|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1037 for IEEE 802.11 Station QOS Profile Type: 1037 for IEEE 802.11 Station QoS Profile
Length: 8 Length: 8
MAC Address: The station's MAC Address MAC Address: The station's MAC Address
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.
8021p: The maximum 802.1p priority value that the WTP will allow in 8021p: The maximum 802.1p priority value that the WTP will allow in
the Traffic Identifier (TID) field in the extended 802.11e QOS the Traffic Identifier (TID) field in the extended 802.11e QoS
Data header. Data header.
6.15. IEEE 802.11 Station Session Key 6.15. IEEE 802.11 Station Session Key
The IEEE 802.11 Station Session Key message element is sent when the The IEEE 802.11 Station Session Key message element is sent by the AC
AC by the AC to provision encryption keys, or to configure an access to provision encryption keys, or to configure an access policy, on
policy, on the WTP. This message element MUST NOT be present without the WTP. This message element MUST NOT be present without the IEEE
the IEEE 802.11 Station (see Section 6.13) message element, and MUST 802.11 Station (see Section 6.13) message element, and MUST NOT be
NOT be sent if the WTP had not specifically advertised support for sent if the WTP had not specifically advertised support for the
the requested encryption scheme, through the WTP Descriptor Message requested encryption scheme, through the WTP Descriptor Message
Element's Encryption Capabilities Field (see Section 8.1). Element's Encryption Capabilities field (see Section 8.1).
When the Key field is non-zero in length, the RSN information element When the Key field is non-zero in length, the RSN Information Element
MUST be sent along with the IEEE 802.11 Station Session Key in order MUST be sent along with the IEEE 802.11 Station Session Key in order
to instruct the WTP on the usage of the Key field. The WTP MUST to instruct the WTP on the usage of the Key field. The WTP MUST
observe the AKM field of the RSN information element in order to observe the Authentication and Key Management (AKM) field of the RSN
identify the authentication protocol to be enforced with the station. Information Element in order to identify the authentication protocol
to be enforced with the station.
If cryptographic services are provided at the WTP, the WTP MUST If cryptographic services are provided at the WTP, the WTP MUST
observe the algorithm dictated in the Pairwise Cipher Suite field of observe the algorithm dictated in the Pairwise Cipher Suite field of
the RSN information element sent by the AC. The RSN Information the RSN Information Element sent by the AC. The RSN Information
Element included here is the one sent by the AC in the third message Element included here is the one sent by the AC in the third message
of the 4-Way Key Handshake, which specifies which cipher is to be of the 4-Way Key Handshake, which specifies which cipher is to be
applied to provide encryption and decryption services with the applied to provide encryption and decryption services with the
station. The RSN Information Element is used to communicate any station. The RSN Information Element is used to communicate any
supported algorithm, including WEP, TKIP and AES-CCMP. In the case supported algorithm, including WEP, TKIP, and AES-CCMP. In the case
of static WEP keys, the RSN Information Element is still used to of static WEP keys, the RSN Information Element is still used to
indicate the cryptographic algorithm even though no key exchange indicate the cryptographic algorithm even though no key exchange
occurred. occurred.
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'
is set, the WTP MUST drop all IEEE 802.11 packets that are not part bit is set, the WTP MUST drop all IEEE 802.11 packets that are not
of the Authentication and Key Management (AKM), such as EAP. Note part of the Authentication and Key Management (AKM), such as EAP.
that AKM-Only is MAY be set while an encryption key is in force, Note that AKM-Only MAY be set while an encryption key is in force,
requiring that the AKM packets be encrypted. Once the station has requiring that the AKM packets be encrypted. Once the station has
successfully completed authentication via the AKM, the AC MUST send a successfully completed authentication via the AKM, the AC MUST send a
new Add Station message element to remove the AKM-Only restriction, new Add Station message element to remove the AKM-Only restriction,
and optionally push the session key down to the WTP. and optionally 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 52, line 33 skipping to change at page 50, line 5
Length: >= 25 Length: >= 25
MAC Address: The station's MAC Address MAC Address: The station's MAC Address
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. The not defined for the version of the protocol they support. The
following bits are defined: following bits are defined:
A: The one bit AKM-Only field is set by the AC to inform the WTP A: The 1-bit AKM-Only field is set by the AC to inform the WTP
that is MUST NOT accept any 802.11 data frames, other than AKM that is MUST NOT accept any 802.11 Data Frames other than AKM
frames. This is the equivalent of the WTP's IEEE 802.1X port frames. This is the equivalent of the WTP's IEEE 802.1X port
for the station to be in the closed state. When set, the WTP for the station to be in the closed state. When set, the WTP
MUST drop any non-IEEE 802.1X packets it receives from the MUST drop any non-IEEE 802.1X packets it receives from the
station. station.
C: The one bit field is set by the AC to inform the WTP that C: The 1-bit field is set by the AC to inform the WTP that
encryption services will be provided by the AC. When set, the encryption services will be provided by the AC. When set,
WTP SHOULD police frames received from stations to ensure that the WTP SHOULD police frames received from stations to ensure
are properly encrypted as specified in the RSN Information that they are properly encrypted as specified in the RSN
Element, but does not need to take specific cryptographic Information Element, but does not need to take specific
action on the frame. Similarly, for transmitted frames, the cryptographic action on the frame. Similarly, for
WTP only needs to forward already encrypted frames. Since transmitted frames, the WTP only needs to forward already
packets received by the WTP will be encrypted, the WTP cannot encrypted frames. Since packets received by the WTP will be
modify the contents of the packets, including modifying the encrypted, the WTP cannot modify the contents of the packets,
DSCP markings of the encapsulated packet. In this case, this including modifying the DSCP markings of the encapsulated
function would be the responsibility of the AC. packet. In this case, this function would be the
responsibility of the AC.
Pairwise TSC: The 6 byte Transmit Sequence Counter (TSC) field to Pairwise TSC: The 6-byte Transmit Sequence Counter (TSC) field to
use for unicast packets transmitted to the station. use for unicast packets transmitted to the station.
Pairwise RSC: The 6 byte Receive Sequence Counter (RSC) to use for Pairwise RSC: The 6-byte Receive Sequence Counter (RSC) to use for
unicast packets received from the station. unicast packets received from the station.
Key: The pairwise key the WTP is to use when encrypting traffic to/ Key: The pairwise key the WTP is to use when encrypting traffic to/
from the station. The format of the keys differ based on the from the station. The format of the keys differs based on the
crypto algorithm used. For unicast WEP keys, the Key field crypto algorithm used. For unicast WEP keys, the Key field
consists of the actual unicast encryption key (note, this is used consists of the actual unicast encryption key (note, this is used
when WEP is used in conjunction with 802.1X, and therefore a when WEP is used in conjunction with 802.1X, and therefore a
unicast encryption key exists). When used with CCMP, the Key unicast encryption key exists). When used with CCMP, the Key
field includes the 128-bit Temporal Key. When used with TKIP, the field includes the 128-bit Temporal Key. When used with TKIP, the
Key field includes the 256-bit Temporal Key (which consists of a Key field includes the 256-bit Temporal Key (which consists of a
128-bit key used as input for TKIP key mixing, and two 64-bit keys 128-bit key used as input for TKIP key mixing, and two 64-bit keys
used for Michael). used for Michael).
6.16. IEEE 802.11 Statistics 6.16. IEEE 802.11 Statistics
The IEEE 802.11 Statistics message element is sent by the WTP to The IEEE 802.11 Statistics message element is sent by the WTP to
transmit its current statistics, and contains the following fields. transmit its current statistics, and it contains the following
All of the fields in this message element are set to zero upon WTP fields. All of the fields in this message element are set to zero
initialization. The fields will roll over when they reach their upon WTP initialization. The fields will roll over when they reach
maximum value of 4294967295. Due to the nature of each counter their maximum value of 4294967295. Due to the nature of each counter
representing different data points, the roll over event will vary representing different data points, the roll over event will vary
greatly across each field. Applications or human operators using greatly across each field. Applications or human operators using
these counters need to be aware about the minimal possible times these counters need to be aware of the minimal possible times between
between rollover events in order to make sure that no consecutive rollover events in order to make sure that no consecutive rollover
rollover events are missed. events are missed.
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 | Reserved | | Radio ID | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tx Fragment Count | | Tx Fragment Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Tx Count | | Multicast Tx Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 57, line 40 skipping to change at page 54, line 40
Supported Rates: The WTP includes the Supported Rates that its Supported Rates: The WTP includes the Supported Rates that its
hardware supports. The format is identical to the Rate Set hardware supports. The format is identical to the Rate Set
message element and is between 2 and 8 bytes in length. message element and is between 2 and 8 bytes in length.
6.18. IEEE 802.11 Tx Power 6.18. IEEE 802.11 Tx Power
The IEEE 802.11 Tx Power message element value is bi-directional. The IEEE 802.11 Tx Power message element value is bi-directional.
When sent by the WTP, it contains the current power level of the When sent by the WTP, it contains the current power level of the
radio in question. When sent by the AC, it contains the power level radio in question. When sent by the AC, it contains the power level
the WTP MUST adhere to. to which the WTP MUST adhere.
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 | Reserved | Current Tx Power | | Radio ID | Reserved | Current Tx Power |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1041 for IEEE 802.11 Tx Power Type: 1041 for IEEE 802.11 Tx Power
Length: 4 Length: 4
skipping to change at page 58, line 45 skipping to change at page 55, line 45
Length: >= 4 Length: >= 4
Radio ID: An 8-bit value representing the radio to configure, whose Radio ID: An 8-bit value representing the radio to configure, whose
value is between one (1) and 31. value is between one (1) and 31.
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 dot11NumberSupportedPowerLevels MIB element (see
[IEEE.802-11.2007]). [IEEE.802-11.2007]).
Power Level: Each power level fields contains a supported power Power Level: Each power level field 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
[IEEE.802-11.2007]. [IEEE.802-11.2007].
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 the Quality of Service policy on the WTP for a given station. The
QoS tags included in this message element are to be applied to QoS tags included in this message element are to be applied to
packets received at the WTP from the station indicated through the packets received at the WTP from the station indicated through the
MAC Address field. This message element overrides the default values MAC Address field. This message element overrides the default values
provided through the IEEE 802.11 WTP Quality of Service message provided through the IEEE 802.11 WTP Quality of Service message
element (see Section 6.22). Any tagging performed by the WTP MUST be element (see Section 6.22). Any tagging performed by the WTP MUST be
directly applied to the packets receive from the station, as well as directly applied to the packets received from the station, as well as
the CAPWAP tunnel, if the packets are tunneled to the AC. See the CAPWAP tunnel, if the packets are tunneled to the AC. See
Section 2.6 for more information. Section 2.6 for more information.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | QoS Sub-Element... | | MAC Address | QoS Sub-Element... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1043 for IEEE 802.11 Update Station QoS Type: 1043 for IEEE 802.11 Update Station QoS
Length: 8 Length: 8
Radio ID: The Radio Identifier, whose value is between one (1) and Radio ID: The Radio Identifier, whose value is between one (1) and
31, typically refers to some interface index on the WTP 31, typically refers to some interface index on the WTP.
MAC Address: The station's MAC Address. MAC Address: The station's MAC Address.
QoS Sub-Element: The IEEE 802.11 WTP Quality of Service message QoS Sub-Element: The IEEE 802.11 WTP Quality of Service message
element contains four QoS sub-elements, one for every QoS profile. element contains four QoS sub-elements, one for every QoS profile.
The order of the QoS profiles are Voice, Video, Best Effort and The order of the QoS profiles are Voice, Video, Best Effort, and
Background. Background.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved|8021p|RSV| DSCP Tag | | Reserved|8021p|RSV| DSCP Tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reserved: All implementations complying with this protocol MUST Reserved: All implementations complying with this protocol MUST
set to zero any bits that are reserved in the version of the set to zero any bits that are reserved in the version of the
protocol supported by that implementation. Receivers MUST protocol supported by that implementation. Receivers MUST
ignore all bits not defined for the version of the protocol ignore all bits not defined for the version of the protocol
they support. they support.
8021p: The three bit 802.1p priority value to use if packets are 8021p: The 3-bit 802.1p priority value to use if packets are to
to be IEEE 802.1p tagged. This field is used only if the 'P' be IEEE 802.1p tagged. This field is used only if the 'P' bit
bit in the WTP Quality of Service message element was set; in the WTP Quality of Service message element was set;
otherwise, its contents MUST be ignored. otherwise, its contents MUST be ignored.
RSV: All implementations complying with this protocol MUST set RSV: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the to zero any bits that are reserved in the version of the
protocol supported by that implementation. Receivers MUST protocol supported by that implementation. Receivers MUST
ignore all bits not defined for the version of the protocol ignore all bits not defined for the version of the protocol
they support. they support.
DSCP Tag: The 6 bit DSCP label to use if packets are eligible to DSCP Tag: The 6-bit DSCP label to use if packets are eligible to
be DSCP tagged, specifically an IPv4 or IPv6 packet (see be DSCP tagged, specifically an IPv4 or IPv6 packet (see
[RFC2474]). This field is used only if the 'D' bit in the WTP [RFC2474]). This field is used only if the 'D' bit in the WTP
Quality of Service message element was set; otherwise, its Quality of Service message element was set; otherwise, its
contents MUST be ignored. contents MUST be ignored.
6.21. IEEE 802.11 Update WLAN 6.21. IEEE 802.11 Update WLAN
The IEEE 802.11 Update WLAN message element is used by the AC to The IEEE 802.11 Update WLAN message element is used by the AC to
define a wireless LAN on the WTP. The inclusion of this message define a wireless LAN on the WTP. The inclusion of this message
element MUST also include the IEEE 802.11 Information Element message element MUST also include the IEEE 802.11 Information Element message
element, containing the following 802.11 IEs: element, containing the following 802.11 IEs:
Power Constraint information element Power Constraint information element
WPA information element [WPA] WPA information element [WPA]
RSN information element RSN information element
EDCA Parameter Set information element Enhanced Distributed Channel Access (EDCA) Parameter Set information
element
QoS Capability information element QoS Capability information element
WMM information element [WMM] WMM information element [WMM]
These IEEE 802.11 information elements are stored by the WTP and These IEEE 802.11 Information Elements are stored by the WTP and
included in any Probe Responses and Beacons generated, as specified included in any Probe Responses and Beacons generated, as specified
in the IEEE 802.11 standard [IEEE.802-11.2007]. in the IEEE 802.11 standard [IEEE.802-11.2007].
If cryptographic services are provided at the WTP, the WTP MUST If cryptographic services are provided at the WTP, the WTP MUST
observe the algorithm dictated in the Group Cipher Suite field of the observe the algorithm dictated in the Group Cipher Suite field of the
RSN information element sent by the AC. The RSN Information Element RSN Information Element sent by the AC. The RSN Information Element
is used to communicate any supported algorithm, including WEP, TKIP is used to communicate any supported algorithm, including WEP, TKIP,
and AES-CCMP. In the case of static WEP keys, the RSN Information and AES-CCMP. In the case of static WEP keys, the RSN Information
Element is still used to indicate the cryptographic algorithm even Element is still used to indicate the cryptographic algorithm even
though no key exchange occurred. though no key exchange occurred.
The message element uses the following format: The message element uses the following format:
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 | Capability | | Radio ID | WLAN ID | Capability |
skipping to change at page 61, line 27 skipping to change at page 58, line 27
Type: 1044 for IEEE 802.11 Update WLAN Type: 1044 for IEEE 802.11 Update WLAN
Length: >= 8 Length: >= 8
Radio ID: An 8-bit value representing the radio, whose value is Radio ID: An 8-bit value representing the radio, whose value is
between one (1) and 31. between one (1) and 31.
WLAN ID: An 8-bit value specifying the WLAN Identifier. The value WLAN ID: An 8-bit value specifying the WLAN Identifier. The value
MUST be between one (1) and 16. MUST be between one (1) and 16.
Capability: A 16-bit value containing the capability information Capability: A 16-bit value containing the Capability information
field to be advertised by the WTP in the Probe Request and Beacon field to be advertised by the WTP in the Probe Request and Beacon
frames. Each bit of the Capability field represents a different frames. Each bit of the Capability field represents a different
WTP capability, which are described in detail in WTP capability, which are described in detail in
[IEEE.802-11.2007]. The format of the field is: [IEEE.802-11.2007]. The format of the field is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E|I|C|F|P|S|B|A|M|Q|T|D|V|O|K|L| |E|I|C|F|P|S|B|A|M|Q|T|D|V|O|K|L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 62, line 10 skipping to change at page 59, line 10
[IEEE.802-11.2007]. [IEEE.802-11.2007].
F (CF-Poll Request): The AC sets the CF-Poll Request subfield F (CF-Poll Request): The AC sets the CF-Poll Request subfield
based on the table found in [IEEE.802-11.2007]. based on the table found in [IEEE.802-11.2007].
P (Privacy): The AC sets the Privacy subfield based on the P (Privacy): The AC sets the Privacy subfield based on the
confidentiality requirements of the WLAN, as defined in confidentiality requirements of the WLAN, as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
S (Short Preamble): The AC sets the Short Preamble subfield S (Short Preamble): The AC sets the Short Preamble subfield
based on whether the use of short preambles are permitted on based on whether the use of short preambles are permitted on the
the WLAN, as defined in [IEEE.802-11.2007]. WLAN, as defined in [IEEE.802-11.2007].
B (PBCC): The AC sets the Packet Binary Convolutional Code B (PBCC): The AC sets the Packet Binary Convolutional Code
(PBCC) modulation option subfield based on whether the use of (PBCC) modulation option subfield based on whether the use of
PBCC is permitted on the WLAN, as defined in PBCC is permitted on the WLAN, as defined in [IEEE.802-11.2007].
[IEEE.802-11.2007].
A (Channel Agility): The AC sets the Channel Agility subfield A (Channel Agility): The AC sets the Channel Agility subfield
based on whether the WTP is capable of supporting the High Rate based on whether the WTP is capable of supporting the High Rate
Direct Sequence Spread Spectrum (HR/DSSS), as defined in Direct Sequence Spread Spectrum (HR/DSSS), as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
M (Spectrum Management): The AC sets the Spectrum Management M (Spectrum Management): The AC sets the Spectrum Management
subfield according to the value of the subfield according to the value of the
dot11SpectrumManagementRequired MIB variable, as defined in dot11SpectrumManagementRequired MIB variable, as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
Q (QOS): The AC sets the Quality of Service (QOS) subfield based Q (QoS): The AC sets the Quality of Service (QoS) subfield based
on the table found in [IEEE.802-11.2007]. on the table found in [IEEE.802-11.2007].
T (Short Slot Time): The AC sets the Short Slot Timesubfield T (Short Slot Time): The AC sets the Short Slot Timesubfield
according to the value of the WTP's currently used slot time according to the value of the WTP's currently used slot time
value, as defined in [IEEE.802-11.2007]. value, as defined in [IEEE.802-11.2007].
D (APSD): The AC sets the APSD subfield according to the value D (APSD): The AC sets the APSD subfield according to the value
of the dot11APSDOptionImplemented Management Information Base of the dot11APSDOptionImplemented Management Information Base
(MIB) variable, as defined in [IEEE.802-11.2007]. (MIB) variable, as defined in [IEEE.802-11.2007].
skipping to change at page 63, line 7 skipping to change at page 60, line 7
Frequency Division Multiplexing (DSSS-OFDM), as defined in Frequency Division Multiplexing (DSSS-OFDM), as defined in
[IEEE.802-11.2007]. [IEEE.802-11.2007].
K (Delayed Block ACK): The AC sets the Delayed Block ACK K (Delayed Block ACK): The AC sets the Delayed Block ACK
subfield according to the value of the subfield according to the value of the
dot11DelayedBlockAckOptionImplemented MIB variable, as defined dot11DelayedBlockAckOptionImplemented MIB variable, as defined
in [IEEE.802-11.2007]. in [IEEE.802-11.2007].
L (Immediate Block ACK): The AC sets the Delayed Block ACK L (Immediate Block ACK): The AC sets the Delayed Block ACK
subfield according to the value of the subfield according to the value of the
dot11ImmediateBlockAckOptionImplemented MIB variable, as dot11ImmediateBlockAckOptionImplemented MIB variable, as defined
defined in [IEEE.802-11.2007]. in [IEEE.802-11.2007].
Key-Index: The Key Index associated with the key. Key-Index: The Key-Index associated with the key.
Key Status: A 1 byte value that specifies the state and usage of Key Status: A 1-byte value that specifies the state and usage of
the key that has been included. The following values describe the the key that has been included. The following values describe the
key usage and its status: key usage and its status:
0 - A value of zero, with the inclusion of the RSN Information 0 - A value of zero, with the inclusion of the RSN Information
Element means that the WLAN uses per-station encryption keys, Element means that the WLAN uses per-station encryption keys,
and therefore the key in the 'Key' field is only used for and therefore the key in the 'Key' field is only used for
multicast traffic. multicast traffic.
1 - When set to one, the WLAN employs a shared WEP key, also 1 - When set to one, the WLAN employs a shared WEP key, also
known as a static WEP key, and uses the encryption key for both known as a static WEP key, and uses the encryption key for
unicast and multicast traffic for all stations. both unicast and multicast traffic for all stations.
2 - The value of 2 indicates that the AC will begin rekeying the 2 - The value of 2 indicates that the AC will begin rekeying the
GTK with the STA's in the BSS. It is only valid when IEEE GTK with the STA's in the BSS. It is only valid when IEEE
802.11 is enabled as the security policy for the BSS. 802.11 is enabled as the security policy for the BSS.
3 - The value of 3 indicates that the AC has completed rekeying 3 - The value of 3 indicates that the AC has completed rekeying
the GTK and broadcast packets no longer need to be duplicated the GTK and broadcast packets no longer need to be duplicated
and transmitted with both GTK's. and transmitted with both GTK's.
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 Session Key, whose length is known via the key length field, Key: A Session Key, whose length is known via the Key Length field,
used to provide data privacy. For static WEP keys, which is true used to provide data privacy. For static WEP keys, which is true
when the 'Key Status' bit is set to one, this key is used for both when the 'Key Status' bit is set to one, this key is used for both
unicast and multicast traffic. For encryption schemes that employ unicast and multicast traffic. For encryption schemes that employ
a separate encryption key for unicast and multicast traffic, the a separate encryption key for unicast and multicast traffic, the
key included here only applies to multicast data, and the cipher key included here only applies to multicast data, and the cipher
suite is specified in an accompanied RSN Information Element. In suite is specified in an accompanied RSN Information Element. In
these scenarios, the key, and cipher information, is communicated these scenarios, the key, and cipher information, is communicated
via the Add Station message element, see Section 4.6.8 in via the Add Station message element, see Section 4.6.8 in
[I-D.ietf-capwap-protocol-specification]. When used with WEP, the [RFC5415]. When used with WEP, the Key field includes the
key field includes the broadcast key. When used with CCMP, the broadcast key. When used with CCMP, the Key field includes the
Key field includes the 128-bit Group Temporal Key. When used with 128-bit Group Temporal Key. When used with TKIP, the Key field
TKIP, the Key field includes the 256-bit Group Temporal Key (which includes the 256-bit Group Temporal Key (which consists of a 128-
consists of a 128-bit key used as input for TKIP key mixing, and bit key used as input for TKIP key mixing, and two 64-bit keys
two 64-bit keys used for Michael). used for Michael).
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. The QoS tag included in this message element are the information. The QoS tags included in this message element are the
default QoS values to be applied to packets received by the WTP from default QoS values to be applied to packets received by the WTP from
stations on a particular radio. Any tagging performed by the WTP stations on a particular radio. Any tagging performed by the WTP
MUST be directly applied to the packets receive from the station, as MUST be directly applied to the packets received from the station, as
well as the CAPWAP tunnel, if the packets are tunneled to the AC. well as the CAPWAP tunnel, if the packets are tunneled to the AC.
See Section 2.6 for more information. See Section 2.6 for more information.
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 |Tagging Policy | QoS Sub-Element ... | Radio ID |Tagging Policy | QoS Sub-Element ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1045 for IEEE 802.11 WTP Quality of Service Type: 1045 for IEEE 802.11 WTP Quality of Service
Length: 34 Length: 34
Radio ID: The Radio Identifier, whose value is between one (1) and Radio ID: The Radio Identifier, whose value is between one (1) and
31, typically refers to some interface index on the WTP 31, typically refers to some interface index on the WTP.
Tagging Policy: A bit field indicating how the WTP is to mark Tagging Policy: A bit field indicating how the WTP is to mark
packets for QoS purposes. The required WTP behavior is defined in packets for QoS purposes. The required WTP behavior is defined in
Section 2.6.1. The field has the following format: Section 2.6.1. The field has the following format:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Rsvd |P|Q|D|O|I| |Rsvd |P|Q|D|O|I|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 64, line 49 skipping to change at page 61, line 49
complying with this protocol MUST set to zero any bits that are complying with this protocol MUST set to zero any bits that are
reserved in the version of the protocol supported by that reserved in the version of the protocol supported by that
implementation. Receivers MUST ignore all bits not defined for implementation. Receivers MUST ignore all bits not defined for
the version of the protocol they support. the version of the protocol they support.
P: When set, the WTP is to employ the 802.1p QoS mechanism (see P: When set, the WTP is to employ the 802.1p QoS mechanism (see
Section 2.6.1.1), and the WTP is to use the 'Q' bit. Section 2.6.1.1), and the WTP is to use the 'Q' bit.
Q: When the 'P' bit is set, the 'Q' bit is used by the AC to Q: When the 'P' bit is set, the 'Q' bit is used by the AC to
communicate to the WTP how 802.1p QoS is to be enforced. communicate to the WTP how 802.1p QoS is to be enforced.
Details on the behavior of the 'Q' bit is specified in Details on the behavior of the 'Q' bit are specified in
Section 2.6.1.1. Section 2.6.1.1.
D: When set, the WTP is to employ the DSCP QoS mechanism (see D: When set, the WTP is to employ the DSCP QoS mechanism (see
Section 2.6.1.2), and the WTP is to use the 'O' and 'I' bits. Section 2.6.1.2), and the WTP is to use the 'O' and 'I' bits.
O: When the 'D' bit is set, the 'O' bit is used by the AC to O: When the 'D' bit is set, the 'O' bit is used by the AC to
communicate to the WTP how DSCP QoS is to be enforced on the communicate to the WTP how DSCP QoS is to be enforced on the
outer (tunneled) header. Details on the behavior of the 'O' outer (tunneled) header. Details on the behavior of the 'O'
bit is specified in Section 2.6.1.2. bit are specified in Section 2.6.1.2.
I: When the 'D' bit is set, the 'I' bit is used by the AC to I: When the 'D' bit is set, the 'I' bit is used by the AC to
communicate to the WTP how DSCP QoS is to be enforced on the communicate to the WTP how DSCP QoS is to be enforced on the
station's packet (inner) header. Details on the behavior of station's packet (inner) header. Details on the behavior of
the 'I' bit is specified in Section 2.6.1.2. the 'I' bit are specified in Section 2.6.1.2.
QoS Sub-Element: The IEEE 802.11 WTP Quality of Service message QoS Sub-Element: The IEEE 802.11 WTP Quality of Service message
element contains four QoS sub-elements, one for every QoS profile. element contains four QoS sub-elements, one for every QoS profile.
The order of the QoS profiles are Voice, Video, Best Effort and The order of the QoS profiles are Voice, Video, Best Effort, and
Background. Background.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Depth | CWMin | CWMax | | Queue Depth | CWMin | CWMax |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CWMax | AIFS | Reserved|8021p|RSV| DSCP Tag | | CWMax | AIFS | Reserved|8021p|RSV| DSCP Tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 66, line 11 skipping to change at page 63, line 11
QoS transmit queue. The value of this field comes from the QoS transmit queue. The value of this field comes from the
IEEE 802.11 dot11EDCATableAIFSN MIB element (see IEEE 802.11 dot11EDCATableAIFSN MIB element (see
[IEEE.802-11.2007]). [IEEE.802-11.2007]).
Reserved: All implementations complying with this protocol MUST Reserved: All implementations complying with this protocol MUST
set to zero any bits that are reserved in the version of the set to zero any bits that are reserved in the version of the
protocol supported by that implementation. Receivers MUST protocol supported by that implementation. Receivers MUST
ignore all bits not defined for the version of the protocol ignore all bits not defined for the version of the protocol
they support. they support.
8021p: The three bit 802.1p priority value to use if packets are 8021p: The 3-bit 802.1p priority value to use if packets are to
to be IEEE 802.1p tagged. This field is used only if the 'P' be IEEE 802.1p tagged. This field is used only if the 'P' bit
bit is set; otherwise, its contents MUST be ignored. is set; otherwise, its contents MUST be ignored.
RSV: All implementations complying with this protocol MUST set RSV: All implementations complying with this protocol MUST set
to zero any bits that are reserved in the version of the to zero any bits that are reserved in the version of the
protocol supported by that implementation. Receivers MUST protocol supported by that implementation. Receivers MUST
ignore all bits not defined for the version of the protocol ignore all bits not defined for the version of the protocol
they support. they support.
DSCP Tag: The 6 bit DSCP label to use if packets are eligible to DSCP Tag: The 6-bit DSCP label to use if packets are eligible to
be DSCP tagged, specifically an IPv4 or IPv6 packet (see be DSCP tagged, specifically an IPv4 or IPv6 packet (see
[RFC2474]). This field is used only if the 'D' bit is set; [RFC2474]). This field is used only if the 'D' bit is set;
otherwise, its contents MUST be ignored. otherwise, its contents MUST be ignored.
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
its radio configuration to the AC. The message element value its radio configuration to the AC. The message element value
contains the following fields: contains the following fields:
skipping to change at page 67, line 21 skipping to change at page 64, line 19
0 - Short preamble not supported. 0 - Short preamble not supported.
1 - Short preamble is supported. 1 - Short preamble is supported.
BSSID: The WLAN Radio's base MAC Address. BSSID: The WLAN Radio's base MAC Address.
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 Traffic Indication Map (TIM) element whose Delivery containing a Traffic Indication Map (TIM) element whose Delivery
Traffic Indication Message (DTIM) Count field is 0. This value is Traffic Indication Message (DTIM) Count field is 0. This value is
transmitted in the DTIM Period field of Beacon frames. The value transmitted in the DTIM Period field of Beacon frames. The value
of this field comes from the IEEE 802.11 dot11DTIMPeriod MIB of this field comes from the IEEE 802.11 dot11DTIMPeriod MIB
element (see [IEEE.802-11.2007]). element (see [IEEE.802-11.2007]).
Beacon Period: This attribute specifies the number of Time Unit Beacon Period: This attribute specifies the number of Time Unit
(TU) that a station uses for scheduling Beacon transmissions. (TU) that a station uses for scheduling Beacon transmissions.
This value is transmitted in Beacon and Probe Response frames. This value is transmitted in Beacon and Probe Response frames.
skipping to change at page 67, line 49 skipping to change at page 64, line 47
configurable country string, and require that it be a fixed value configurable country string, and require that it be a fixed value
during the manufacturing process. Therefore, WTP vendors that during the manufacturing process. Therefore, WTP vendors that
wish to allow for the configuration of this field will need to wish to allow for the configuration of this field will need to
validate this behavior during its radio certification process. validate this behavior during its radio certification process.
Other WTP vendors may simply wish to treat this WTP configuration Other WTP vendors may simply wish to treat this WTP configuration
parameter as read-only. The country strings can be found in parameter as read-only. The country strings can be found in
[ISO.3166-1]. [ISO.3166-1].
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 string as octets of this string is the two-character country string as
described in document [ISO.3166-1], and the third octet MUST described in [ISO.3166-1], and the third octet MUST either be a
either be a space, 'O', 'I' or X' as defined below. When the space, 'O', 'I', or X' as defined below. When the value of the
value of the third octet is 255 (HEX 0xff), the country string third octet is 255 (HEX 0xff), the country string field is not
field is not used, and MUST be ignored. The following are the used, and MUST be ignored. The following are the possible values
possible values for the third octet: for the third octet:
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,
2. an ASCII 'O' character, if the regulations under which the 2. an ASCII 'O' character, if the regulations under which the
station is operating are for an outdoor environment only, or station is operating are for an outdoor environment only, or
3. an ASCII 'I' character, if the regulations under which the 3. an ASCII 'I' character, if the regulations under which the
station is operating are for an indoor environment only. station is operating are for an indoor environment only,
4. an ASCII 'X' character, if the station is operating under a 4. an ASCII 'X' character, if the station is operating under a
non-country entity. The first two octets of the non-country non-country entity. The first two octets of the non-country
entity shall be two ASCII 'XX' characters. entity shall be two ASCII 'XX' characters,
3. a HEX 0xff character means that the country string field is 5. a HEX 0xff character means that the country string field is
not used and MUST be ignored. not used and MUST be ignored.
Note that the last byte of the Country String MUST be set to NULL. Note that the last byte of the Country String MUST be set to NULL.
6.24. IEEE 802.11 WTP Radio Fail Alarm Indication 6.24. IEEE 802.11 WTP Radio Fail Alarm Indication
The IEEE 802.11 WTP Radio Fail Alarm Indication message element is The IEEE 802.11 WTP Radio Fail Alarm Indication message element is
sent by the WTP to the AC when it detects a radio failure. sent by the WTP to the AC when it detects a radio failure.
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 | Type | Status | Pad | | Radio ID | Type | Status | Pad |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1047 for IEEE 802.11 WTP Radio Fail Alarm Indication Type: 1047 for IEEE 802.11 WTP Radio Fail Alarm Indication
Length: 4 Length: 4
Radio ID: The Radio Identifier, whose value is between one (1) and Radio ID: The Radio Identifier, whose value is between one (1) and
31, typically refers to some interface index on the WTP 31, typically refers to some interface index on the WTP.
Type: The type of radio failure detected. The following enumerated Type: The type of radio failure detected. The following enumerated
values are supported: values are supported:
1 - Receiver 1 - Receiver
2 - Transmitter
2 - Transmitter
Status: An 8-bit boolean indicating whether the radio failure is Status: An 8-bit boolean indicating whether the radio failure is
being reported or cleared. A value of zero is used to clear the being reported or cleared. A value of zero is used to clear the
event, while a value of one is used to report the event. event, while a value of one is used to report the event.
Pad: All implementations complying with version zero of this Pad: All implementations complying with version zero of this
protocol MUST set these bits to zero. Receivers MUST ignore all protocol MUST set these bits to zero. Receivers MUST ignore all
bits not defined for the version of the protocol they support. bits not defined for the version of the protocol they support.
6.25. IEEE 802.11 WTP Radio Information 6.25. IEEE 802.11 WTP Radio Information
The IEEE 802.11 WTP Radio Information message element is used to The IEEE 802.11 WTP Radio Information message element is used to
communicate the radio information for each IEEE 802.11 radio in the communicate the radio information for each IEEE 802.11 radio in the
WTP. The Discovery Request message, Primary Discovery Request WTP. The Discovery Request message, Primary Discovery Request
message and Join Request message MUST include one such message message, and Join Request message MUST include one such message
element per radio in the WTP. The Radio-Type field is used by the AC element per radio in the WTP. The Radio-Type field is used by the AC
in order to determine which IEEE 802.11 technology specific binding in order to determine which IEEE 802.11 technology specific binding
is to be used with the WTP. is to be used with the WTP.
The message element contains two fields, as shown below. The message element contains two fields, as shown below.
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 | Radio Type | | Radio ID | Radio Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio Type | | Radio Type |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 1048 for IEEE 802.11 WTP Radio Information Type: 1048 for IEEE 802.11 WTP Radio Information
Length: 5 Length: 5
Radio ID: The Radio Identifier, whose value is between one (1) and Radio ID: The Radio Identifier, whose value is between one (1) and
31, which typically refers to an interface index on the WTP 31, which typically refers to an interface index on the WTP.
Radio Type: The type of radio present. Note this is a bit field Radio Type: The type of radio present. Note this is a bit field
which is used to specify support for more than a single type of that is used to specify support for more than a single type of
PHY/MAC. The field has the following format: PHY/MAC. The field has the following format:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Reservd|N|G|A|B| |Reservd|N|G|A|B|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Reservd: A set of reserved bits for future use. All Reservd: A set of reserved bits for future use. All
implementations complying with this protocol MUST set to zero implementations complying with this protocol MUST set to zero
any bits that are reserved in the version of the protocol any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all supported by that implementation. Receivers MUST ignore all
skipping to change at page 71, line 12 skipping to change at page 67, line 25
B: An IEEE 802.11b radio. B: An IEEE 802.11b radio.
7. IEEE 802.11 Binding WTP Saved Variables 7. IEEE 802.11 Binding WTP Saved Variables
This section contains the IEEE 802.11 binding specific variables that This section contains the IEEE 802.11 binding specific variables that
SHOULD be saved in non-volatile memory on the WTP. SHOULD be saved in non-volatile memory on the WTP.
7.1. IEEE80211AntennaInfo 7.1. IEEE80211AntennaInfo
The WTP per radio antenna configuration, defined in Section 6.2. The WTP-per-radio antenna configuration, defined in Section 6.2.
7.2. IEEE80211DSControl 7.2. IEEE80211DSControl
The WTP per radio Direct Sequence Control configuration, defined in The WTP-per-radio Direct Sequence Control configuration, defined in
Section 6.5. Section 6.5.
7.3. IEEE80211MACOperation 7.3. IEEE80211MACOperation
The WTP per radio MAC Operation configuration, defined in The WTP-per-radio MAC Operation configuration, defined in
Section 6.7. Section 6.7.
7.4. IEEE80211OFDMControl 7.4. IEEE80211OFDMControl
The WTP per radio OFDM MAC Operation configuration, defined in The WTP-per-radio OFDM MAC Operation configuration, defined in
Section 6.10. Section 6.10.
7.5. IEEE80211Rateset 7.5. IEEE80211Rateset
The WTP per radio Basic Rate Set configuration, defined in The WTP-per-radio Basic Rate Set configuration, defined in
Section 6.11. Section 6.11.
7.6. IEEE80211TxPower 7.6. IEEE80211TxPower
The WTP per radio Transmit Power configuration, defined in The WTP-per-radio Transmit Power configuration, defined in
Section 6.18. Section 6.18.
7.7. IEEE80211QoS 7.7. IEEE80211QoS
The WTP per radio Quality of Service configuration, defined in The WTP-per-radio Quality of Service configuration, defined in
Section 6.22. Section 6.22.
7.8. IEEE80211RadioConfig 7.8. IEEE80211RadioConfig
The WTP per radio Radio Configuration, defined in Section 6.23. The WTP-per-radio Radio Configuration, defined in Section 6.23.
8. Technology Specific Message Element Values 8. Technology Specific Message Element Values
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 that include fields whose values are technology
specific. specific.
8.1. WTP Descriptor Message Element, Encryption Capabilities Field: 8.1. WTP Descriptor Message Element, Encryption Capabilities Field
This specification defines two new bits for the WTP Descriptor's This specification defines two new bits for the WTP Descriptor's
Encryption Capabilities field, as defined in Encryption Capabilities field, as defined in [RFC5415]. Note that
[I-D.ietf-capwap-protocol-specification]. Note that only the bits only the bits defined in this specification are described below. WEP
defined in this specification are described below. WEP is not is not explicitly advertised as a WTP capability since all WTPs are
explicitely advertised as a WTP capability since all WTPs are
expected to support the encryption cipher. The format of the expected to support the encryption cipher. The format of the
Encryption Capabilities Field is: Encryption Capabilities field is:
1 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |A|T| | | |A|T| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A: WTP supports AES-CCMP, as defined in [IEEE.802-11.2007]. A: WTP supports AES-CCMP, as defined in [IEEE.802-11.2007].
T: WTP supports TKIP and Michael, as defined in [IEEE.802-11.2007] T: WTP supports TKIP and Michael, as defined in [IEEE.802-11.2007]
and [WPA], respectively. and [WPA], respectively.
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. A complete threat analysis of the CAPWAP with the CAPWAP protocol. A complete threat analysis of the CAPWAP
protocol can also be found in [I-D.ietf-capwap-threat-analysis] protocol can also be found in [RFC5418].
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. Implementers SHOULD discourage the use many well-documented attacks. Implementers SHOULD discourage the use
of WEP and encourage use of technically sound cryptographic solutions of WEP and encourage the use of technically-sound cryptographic
such as those in an IEEE 802.11 RSN. solutions 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. Implementers SHOULD use EAP methods meeting the requirements EAP. Implementers SHOULD use EAP methods meeting the requirements
specified [RFC4017]. specified [RFC4017].
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:
o The client is not the first to associate to the WTP/ESSID (i.e. o The client is not the first to associate to the WTP/ESSID (i.e.,
other clients are associated), and a GTK already exists other clients are associated), a GTK already exists, and
o traffic has been broadcast under the existing GTK o traffic has been broadcast under the existing GTK.
Under these circumstances, the receive sequence counter (KeyRSC) Under these circumstances, the receive sequence counter (KeyRSC)
associated with the GTK is non-zero, but because the AC anchors the associated with the GTK is non-zero, but because the AC anchors the
4-way handshake with the client, the exact value of the KeyRSC is not 4-way handshake with the client, the exact value of the KeyRSC is not
known when the AC constructs the message containing the GTK. The known when the AC constructs the message containing the GTK. The
client will update its Key RSC value to the current valid KeyRSC upon client will update its Key RSC value to the current valid KeyRSC upon
receipt of a valid multicast/broadcast message, but prior to this, receipt of a valid multicast/broadcast message, but prior to this,
previous multicast/broadcast traffic which was secured with the previous multicast/broadcast traffic that was secured with the
existing GTK may be replayed, and the client will accept this traffic existing GTK may be replayed, and the client will accept this traffic
as valid. as valid.
Typically, busy networks will produce numerous multicast or broadcast Typically, busy networks will produce numerous multicast or broadcast
frames per second, so the window of opportunity with respect to such frames per second, so the window of opportunity with respect to such
replay is expected to be very small. In most conditions, it is replay is expected to be very small. In most conditions, it is
expected that replayed frames could be detected (and logged) by the expected that replayed frames could be detected (and logged) by the
WTP. WTP.
The only way to completely close this window is to provide the exact The only way to completely close this window is to provide the exact
skipping to change at page 75, line 7 skipping to change at page 70, line 12
providing the exact KeyRSC value is not warranted. That is, this providing the exact KeyRSC value is not warranted. That is, this
specification provides for a calculated risk in this regard. specification provides for a calculated risk in this regard.
The AC SHOULD use an RSC of 0 when computing message-3 of the 4-way The AC SHOULD use an RSC of 0 when computing message-3 of the 4-way
802.11i handshake, unless the AC has knowledge of a more optimal RSC 802.11i handshake, unless the AC has knowledge of a more optimal RSC
value to use. Mechanisms for determining a more optimal RSC value value to use. Mechanisms for determining a more optimal RSC value
are outside the scope of this specification. are outside the scope of this specification.
10. IANA Considerations 10. IANA Considerations
This section details the actions to be taken by IANA during the This section details the actions IANA has taken per this
publication of the specification. There are numerous registries that specification. There are numerous registries that have been be
need to be created, and the contents, document action (see [RFC5226], created, and the contents, document action (see [RFC5226], and
and registry format are all included below. Note that in cases where registry format are all included below. Note that in cases where bit
bit fields are referred to, the bit numbering is left to right, where fields are referred to, the bit numbering is left to right, where the
the leftmost bit is labelled as bit zero (0). leftmost bit is labeled as bit zero (0).
10.1. CAPWAP Wireless Binding Identifier 10.1. CAPWAP Wireless Binding Identifier
This specification requires a value assigned from the Wireless This specification requires a value assigned from the Wireless
Binding Identifier namespace, defined in Binding Identifier namespace, defined in [RFC5415]. (1) has been
[I-D.ietf-capwap-protocol-specification]. The value assigned is to assigned (see Section 2.1, as it is used in implementations.
be added to Section 2.1. The value of one (1)is highly recommended,
as it is used in implementations.
10.2. CAPWAP IEEE 802.11 Message Types 10.2. CAPWAP IEEE 802.11 Message Types
This document creates a new sub-registry to the existing CAPWAP IANA created a new sub-registry in the existing CAPWAP Message Type
Message Type registry, which is defined in registry, which is defined in [RFC5415].
[I-D.ietf-capwap-protocol-specification].
IANA will create and maintain the CAPWAP IEEE 802.11 Message Types IANA will create and maintain the CAPWAP IEEE 802.11 Message Types
sub-registry for all message types whose Enterprise Number is set to sub-registry for all message types whose Enterprise Number is set to
13277. The namespace is 8 bits (3398912-3399167), where the value 13277. The namespace is 8 bits (3398912-3399167), where the value
3398912 is reserved and must not be assigned. The values 3398913 and 3398912 is reserved and must not be assigned. The values 3398913 and
3398914 are allocated in this specification, and can be found in 3398914 are allocated in this specification, and can be found in
Section 3. Any new assignments of a CAPWAP IEEE 802.11 Message Type, Section 3. Any new assignments of a CAPWAP IEEE 802.11 Message Type
whose Enterprise Number is set to 13277) requires a Expert Review. (whose Enterprise Number is set to 13277) require an Expert Review.
The format of the registry to be maintained by IANA has the following The format of the registry to be maintained by IANA is as follows:
format:
CAPWAP IEEE 802.11 Message Type Reference CAPWAP IEEE 802.11 Message Type Reference
Control Message Value Control Message Value
10.3. CAPWAP Message Element Type 10.3. CAPWAP Message Element Type
This specification defines new values to be registered to the This specification defines new values to be registered to the
existing CAPWAP Message Element Type registry, defined in existing CAPWAP Message Element Type registry, defined in [RFC5415].
[I-D.ietf-capwap-protocol-specification]. The values used in this The values used in this document, 1024 through 1048, as listed in
document, 1024 through 1048, as listed in Figure 8 are recommended as Figure 8 are recommended as implementations already exist that make
implementations already exist that make use of these values. use of these values.
10.4. IEEE 802.11 Key Status 10.4. IEEE 802.11 Key Status
The Key Status field in the IEEE 802.11 Add WLAN message element (see The Key Status field in the IEEE 802.11 Add WLAN message element (see
Section 6.1) and IEEE 802.11 Update WLAN message element (see Section 6.1) and IEEE 802.11 Update WLAN message element (see
Section 6.21) is used to provide information about the status of the Section 6.21) is used to provide information about the status of the
keying exchange. This document defines four values, and the keying exchange. This document defines four values, zero (0) through
remaining values are controlled and maintained by IANA and requires a three (3), and the remaining values (4-255) are controlled and
Expert Review. maintained by IANA and requires an Expert Review.
10.5. IEEE 802.11 QoS 10.5. IEEE 802.11 QoS
The QoS field in the IEEE 802.11 Add WLAN message element (see The QoS field in the IEEE 802.11 Add WLAN message element (see
Section 6.1) is used to configure a QoS policy for the WLAN. The Section 6.1) is used to configure a QoS policy for the WLAN. The
namespace is 8 bits (0-255), where the values zero (0) through three namespace is 8 bits (0-255), where the values zero (0) through three
(3) are allocated in this specification, and can be found in (3) are allocated in this specification, and can be found in
Section 6.1. This namespace is managed by IANA and assignments Section 6.1. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the IEEE 802.11 QoS require an Expert Review. IANA will create the IEEE 802.11 QoS
registry, whose format is: registry, whose format is:
IEEE 802.11 QoS Type Value Reference IEEE 802.11 QoS Type Value Reference
10.6. IEEE 802.11 Auth Type 10.6. IEEE 802.11 Auth Type
The Auth Type field in the IEEE 802.11 Add WLAN message element (see The Auth Type field in the IEEE 802.11 Add WLAN message element (see
Section 6.1) is 8 bits and is used to configure the IEEE 802.11 Section 6.1) is 8 bits and is used to configure the IEEE 802.11
authentication policy for the WLAN. The namespace is 8 bits (0-255), authentication policy for the WLAN. The namespace is 8 bits (0-255),
where the values zero (0) and one (1) are allocated in this where the values zero (0) and one (1) are allocated in this
specification, and can be found in Section 6.1. This namespace is specification, and can be found in Section 6.1. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require an Expert Review. IANA will
create the IEEE 802.11 Auth Type registry, whose format is: create the IEEE 802.11 Auth Type registry, whose format is:
IEEE 802.11 Auth Type Type Value Reference IEEE 802.11 Auth Type Type Value Reference
10.7. IEEE 802.11 Antenna Combiner 10.7. IEEE 802.11 Antenna Combiner
The Combiner field in the IEEE 802.11 Antenna message element (see The Combiner field in the IEEE 802.11 Antenna message element (see
Section 6.2) is used to provide information about the WTP's antennas. Section 6.2) is used to provide information about the WTP's antennas.
The namespace is 8 bits (0-255), where the values zero (0) and four The namespace is 8 bits (0-255), where the values one (1) through
(4) are allocated in this specification, and can be found in four (4) are allocated in this specification, and can be found in
Section 6.2. This namespace is managed by IANA and assignments Section 6.2. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the IEEE 802.11 Antenna require an Expert Review. IANA will create the IEEE 802.11 Antenna
Combiner registry, whose format is: Combiner registry, whose format is:
IEEE 802.11 Antenna Combiner Type Value Reference IEEE 802.11 Antenna Combiner Type Value Reference
10.8. IEEE 802.11 Antenna Selection 10.8. IEEE 802.11 Antenna Selection
The Antenna Selection field in the IEEE 802.11 Antenna message The Antenna Selection field in the IEEE 802.11 Antenna message
element (see Section 6.2) is used to provide information about the element (see Section 6.2) is used to provide information about the
WTP's antennas. The namespace is 8 bits (0-255), where the values WTP's antennas. The namespace is 8 bits (0-255), where the values
zero (0) is reserved and used and the values one (1) through two (2) zero (0) is reserved and used and the values one (1) through two (2)
are allocated in this specification, and can be found in Section 6.2. are allocated in this specification, and can be found in Section 6.2.
This namespace is managed by IANA and assignments require an Expert
This namespace is managed by IANA and assignments require a Expert
Review. IANA will create the IEEE 802.11 Antenna Selection registry, Review. IANA will create the IEEE 802.11 Antenna Selection registry,
whose format is: whose format is:
IEEE 802.11 Antenna Selection Type Value Reference IEEE 802.11 Antenna Selection Type Value Reference
10.9. IEEE 802.11 Session Key Flags 10.9. IEEE 802.11 Session Key Flags
The Flags field in the IEEE 802.11 Station Session Key message The flags field in the IEEE 802.11 Station Session Key message
element (see Section 6.15) is 16 bits and is used to configure the element (see Section 6.15) is 16 bits and is used to configure the
session key association with the mobile device. This specification session key association with the mobile device. This specification
defines bits zero (0) and one (1), while bits two (2) through fifteen defines bits zero (0) and one (1), while bits two (2) through fifteen
are reserved. The reserved bits are managed by IANA and whose are reserved. The reserved bits are managed by IANA and assignment
assignment requires a Expert Review. IANA will create the IEEE requires an Expert Review. IANA will create the IEEE 802.11 Session
802.11 Session Key Flags registry, whose format is: Key Flags registry, whose format is:
IEEE 802.11 Station Session Key Bit Position Reference IEEE 802.11 Station Session Key Bit Position Reference
10.10. IEEE 802.11 Tagging Policy 10.10. IEEE 802.11 Tagging Policy
The Tagging Policy field in the IEEE 802.11 WTP Quality of Service The Tagging Policy field in the IEEE 802.11 WTP Quality of Service
message element (see Section 6.22) is 8 bits and is used to specify message element (see Section 6.22) is 8 bits and is used to specify
how the CAPWAP Data Channel packets are to be tagged. This how the CAPWAP Data Channel packets are to be tagged. This
specification defines bits three (3) through seven (7). The specification defines bits three (3) through seven (7). The
remaining bits are managed by IANA and whose assignment requires a remaining bits are managed by IANA and assignment requires an Expert
Expert Review. IANA will create the IEEE 802.11 Tagging Policy Review. IANA will create the IEEE 802.11 Tagging Policy registry,
registry, whose format is: whose format is:
IEEE 802.11 Tagging Policy Bit Position Reference IEEE 802.11 Tagging Policy Bit Position Reference
10.11. IEEE 802.11 WTP Radio Fail 10.11. IEEE 802.11 WTP Radio Fail
The Type field in the IEEE 802.11 WTP Radio Fail Alarm Indication The Type field in the IEEE 802.11 WTP Radio Fail Alarm Indication
message element (see Section 6.24) is used to provide information on message element (see Section 6.24) is used to provide information on
why a WTP's radio has failed. The namespace is 8 bits (0-255), where why a WTP's radio has failed. The namespace is 8 bits (0-255), where
the values zero (0) is reserved and unused, while the values one (1) the value zero (0) is reserved and unused, while the values one (1)
and two (2) are allocated in this specification, and can be found in and two (2) are allocated in this specification, and can be found in
Section 6.24. This namespace is managed by IANA and assignments Section 6.24. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the IEEE 802.11 WTP Radio require an Expert Review. IANA will create the IEEE 802.11 WTP Radio
Fail registry, whose format is: Fail registry, whose format is:
IEEE 802.11 WTP Radio Fail Type Value Reference IEEE 802.11 WTP Radio Fail Type Value Reference
10.12. IEEE 802.11 WTP Radio Type 10.12. IEEE 802.11 WTP Radio Type
The Radio Type field in the IEEE 802.11 WTP Radio Information message The Radio Type field in the IEEE 802.11 WTP Radio Information message
element (see Section 6.25) is 8 bits and is used to provide element (see Section 6.25) is 8 bits and is used to provide
information about the WTP's radio type. This specification defines information about the WTP's radio type. This specification defines
bits four (4) through seven (7). The remaining bits are managed by bits four (4) through seven (7). The remaining bits are managed by
IANA and whose assignment requires a Expert Review. IANA will create IANA and assignment requires an Expert Review. IANA will create the
the IEEE 802.11 WTP Radio Type registry, whose format is: IEEE 802.11 WTP Radio Type registry, whose format is:
IEEE 802.11 WTP Radio Type Bit Position Reference IEEE 802.11 WTP Radio Type Bit Position Reference
10.13. WTP Encryption Capabilities 10.13. WTP Encryption Capabilities
The WTP Encryption Capabilities field in the WTP Descriptor message The WTP Encryption Capabilities field in the WTP Descriptor message
element (see Section 8.1) is 16 bits and is used by the WTP to element (see Section 8.1) is 16 bits and is used by the WTP to
indicate its IEEE 802.11 encryption capabilities. This specification indicate its IEEE 802.11 encryption capabilities. This specification
defines bits 12 and 13. The reserved bits are managed by IANA and defines bits 12 and 13. The reserved bits are managed by IANA and
whose assignment requires a Expert Review. IANA will create the IEEE assignment requires an Expert Review. IANA will create the IEEE
802.11 Encryption Capabilities registry, whose format is: 802.11 Encryption Capabilities registry, whose format is:
IEEE 802.11 Encryption Capabilities Bit Position Reference IEEE 802.11 Encryption Capabilities Bit Position Reference
11. Acknowledgments 11. Acknowledgments
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, Pasi this binding specification: Puneet Agarwal, Charles Clancy, Pasi
Eronen, Saravanan Govindan, Scott Kelly, Peter Nilsson, Bob O'Hara, Eronen, Saravanan Govindan, Scott Kelly, Peter Nilsson, Bob O'Hara,
David Perkins, Margaret Wasserman and Yong Zhang. David Perkins, Margaret Wasserman, and Yong Zhang.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to
Requirement Levels", BCP 14, RFC 2119, March 1997. Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field
Field) in the IPv4 and IPv6 Headers", RFC 2474, (DS Field) in the IPv4 and IPv6 Headers",
December 1998. RFC 2474, December 1998.
[RFC2597] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski,
"Assured Forwarding PHB Group", RFC 2597, June 1999.
[RFC2598] Jacobson, V., Nichols, K., and K. Poduri, "An Expedited [RFC3246] Davie, B., Charny, A., Bennet, J., Benson, K., Le
Forwarding PHB", RFC 2598, June 1999. Boudec, J., Courtney, W., Davari, S., Firoiu, V.,
and D. Stiliadis, "An Expedited Forwarding PHB
(Per-Hop Behavior)", RFC 3246, March 2002.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The
of Explicit Congestion Notification (ECN) to IP", Addition of Explicit Congestion Notification
RFC 3168, September 2001. (ECN) to IP", RFC 3168, September 2001.
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson,
Levkowetz, "Extensible Authentication Protocol (EAP)", J., and H. Levkowetz, "Extensible Authentication
RFC 3748, June 2004. Protocol (EAP)", RFC 3748, June 2004.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for
IANA Considerations Section in RFCs", BCP 26, RFC 5226, Writing an IANA Considerations Section in RFCs",
May 2008. BCP 26, RFC 5226, May 2008.
[FIPS.197.2001] [FIPS.197.2001] National Institute of Standards and Technology,
National Institute of Standards and Technology, "Advanced "Advanced Encryption Standard (AES)", FIPS PUB
Encryption Standard (AES)", FIPS PUB 197, November 2001, < 197, November 2001, <http://csrc.nist.gov/
http://csrc.nist.gov/publications/fips/fips197/ publications/fips/fips197/fips-197.pdf>.
fips-197.pdf>.
[ISO.3166-1] [ISO.3166-1] ISO Standard, "International Organization for
ISO Standard, "International Organization for Standardization, Codes for the representation of
Standardization, Codes for the representation of names of names of countries and their subdivisions - Part
countries and their subdivisions - Part 1: Country codes", 1: Country codes", ISO Standard 3166-1:1997,
ISO Standard 3166-1:1997, 1997. 1997.
[IEEE.802-11.2007] [IEEE.802-11.2007] "Information technology - Telecommunications and
"Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - Part metropolitan area networks - Specific
11: Wireless LAN Medium Access Control (MAC) and Physical requirements - Part 11: Wireless LAN Medium
Layer (PHY) specifications", IEEE Standard 802.11, 2007, < Access Control (MAC) and Physical Layer (PHY)
http://standards.ieee.org/getieee802/download/ specifications", IEEE Standard 802.11, 2007,
<http://standards.ieee.org/getieee802/download/
802.11-2007.pdf>. 802.11-2007.pdf>.
[I-D.ietf-capwap-protocol-specification] [RFC5415] Montemurro, M., Stanley, D., and P. Calhoun,
Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP "CAPWAP Protocol Specification", RFC 5415, March
Protocol Specification", 2009.
draft-ietf-capwap-protocol-specification-14 (work in
progress), October 2008.
[IEEE.802-1X.2004] [IEEE.802-1X.2004] "Information technology - Telecommunications and
"Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - Port- metropolitan area networks - Specific
Based Network Access Control", IEEE Standard 802.1X, 2004, requirements - Port-Based Network Access
<http://standards.ieee.org/getieee802/download/ Control", IEEE Standard 802.1X, 2004, <http://
standards.ieee.org/getieee802/download/
802.1X-2004.pdf>. 802.1X-2004.pdf>.
[IEEE.802-1Q.2005] [IEEE.802-1Q.2005] "Information technology - Telecommunications and
"Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - metropolitan area networks - Specific
Virtual Bridged Local Area Networks", IEEE Standard requirements - Virtual Bridged Local Area
802.1Q, 2005, <http://standards.ieee.org/getieee802/ Networks", IEEE Standard 802.1Q, 2005, <http://
download/802.1Q-2005.pdf>. standards.ieee.org/getieee802/download/
802.1Q-2005.pdf>.
12.2. Informational References 12.2. Informative References
[RFC4017] Stanley, D., Walker, J., and B. Aboba, "Extensible [RFC4017] Stanley, D., Walker, J., and B. Aboba,
Authentication Protocol (EAP) Method Requirements for "Extensible Authentication Protocol (EAP) Method
Wireless LANs", RFC 4017, March 2005. Requirements for Wireless LANs", RFC 4017,
March 2005.
[RFC4118] Yang, L., Zerfos, P., and E. Sadot, "Architecture Taxonomy [RFC4118] Yang, L., Zerfos, P., and E. Sadot, "Architecture
for Control and Provisioning of Wireless Access Points Taxonomy for Control and Provisioning of Wireless
(CAPWAP)", RFC 4118, June 2005. Access Points (CAPWAP)", RFC 4118, June 2005.
[I-D.ietf-capwap-threat-analysis] [RFC5418] Kelly, S. and C. Clancy, "Control And
Kelly, S. and C. Clancy, "CAPWAP Threat Analysis for IEEE Provisioning for Wireless Access Points (CAPWAP)
802.11 Deployments", draft-ietf-capwap-threat-analysis-04 Threat Analysis for IEEE 802.11 Deployments",
(work in progress), September 2008. RFC 5418, March 2009.
[WPA] "Deploying Wi-Fi Protected Access (WPA) and WPA2 in the [WPA] "Deploying Wi-Fi Protected Access (WPA) and WPA2
Enterprise", March 2005, <www.wi-fi.org>. in the Enterprise", March 2005, <www.wi-fi.org>.
[WMM] "Support for Multimedia Applications with Quality of [WMM] "Support for Multimedia Applications with Quality
Service in WiFi Networks)", September 2004, <www.wi- of Service in WiFi Networks)", September 2004,
fi.org>. <www.wi-fi.org>.
Editors' Addresses Editors' Addresses
Pat R. Calhoun Pat R. Calhoun (editor)
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-902-3240 Phone: +1 408-902-3240
Email: pcalhoun@cisco.com EMail: pcalhoun@cisco.com
Michael P. Montemurro Michael P. Montemurro (editor)
Research In Motion Research In Motion
5090 Commerce Blvd 5090 Commerce Blvd
Mississauga, ON L4W 5M4 Mississauga, ON L4W 5M4
Canada Canada
Phone: +1 905-629-4746 x4999 Phone: +1 905-629-4746 x4999
Email: mmontemurro@rim.com EMail: mmontemurro@rim.com
Dorothy Stanley Dorothy Stanley (editor)
Aruba Networks Aruba Networks
1322 Crossman Ave 1322 Crossman Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Phone: +1 630-363-1389 Phone: +1 630-363-1389
Email: dstanley@arubanetworks.com EMail: dstanley@arubanetworks.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 280 change blocks. 
664 lines changed or deleted 663 lines changed or added

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