draft-ietf-opsawg-capwap-extension-02.txt   draft-ietf-opsawg-capwap-extension-03.txt 
OPSAWG Y. Chen OPSAWG Y. Chen
Internet-Draft D. Liu Internet-Draft D. Liu
Updates: 5416 (if approved) H. Deng Updates: 5416 (if approved) H. Deng
Intended status: Standards Track China Mobile Intended status: Standards Track China Mobile
Expires: August 18, 2014 Lei. Zhu Expires: September 5, 2014 Lei. Zhu
Huawei Huawei
February 14, 2014 March 4, 2014
CAPWAP Extension for 802.11n and Power/channel Autoconfiguration CAPWAP Extension for 802.11n and Power/channel Autoconfiguration
draft-ietf-opsawg-capwap-extension-02 draft-ietf-opsawg-capwap-extension-03
Abstract Abstract
CAPWAP binding for 802.11 is specified by RFC5416 and it was based on The CAPWAP binding for 802.11 is specified by RFC5416 and it was
IEEE 802-11.2007 standard. After RFC5416 was published in 2009, based on IEEE 802-11.2007 standard. Several new amendments of 802.11
there were several new amendments of 802.11 have been published. have been published since RFC5416 was published in 2009. 802.11n is
802.11n is one of those amendments and it has been widely used in one of those amendments and it has been widely used in real
real deployment. This document extends the CAPWAP binding for 802.11 deployment. This document extends the CAPWAP binding for 802.11 to
to support 802.11n and also defines a power and channel auto support 802.11n and also defines a power and channel auto
configuration extension. configuration extension.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 18, 2014. This Internet-Draft will expire on September 5, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . 3 3. CAPWAP 802.11n Support . . . . . . . . . . . . . . . . . . . 3
4. CAPWAP 802.11n Support . . . . . . . . . . . . . . . . . . . 3 3.1. CAPWAP Extension for 802.11n Support . . . . . . . . . . 4
4.1. CAPWAP Extension for 802.11n Support . . . . . . . . . . 4 3.1.1. 802.11n Radio Capability Information . . . . . . . . 4
4.1.1. 802.11n Radio Capability Information . . . . . . . . 4 3.1.2. 802.11n Radio Configuration Message Element . . . . . 4
4.1.2. 802.11n Radio Configuration Message Element . . . . . 4 3.1.3. 802.11n Station Information . . . . . . . . . . . . . 6
4.1.3. 802.11n Station Information . . . . . . . . . . . . . 6 4. Power and Channel Autoconfiguration . . . . . . . . . . . . . 7
5. Power and Channel Autoconfiguration . . . . . . . . . . . . . 7 4.1. Channel Autoconfiguration When WTP Power On . . . . . . . 7
5.1. Channel Autoconfiguration When WTP Power On . . . . . . . 7 4.2. Power Configuration When WTP Power On . . . . . . . . . . 8
5.2. Power Configuration When WTP Power On . . . . . . . . . . 8 4.3. Channel/Power Auto Adjusment . . . . . . . . . . . . . . 8
5.3. Channel/Power Auto Adjusment . . . . . . . . . . . . . . 8 4.3.1. IEEE 802.11 Scan Parameters Message Element . . . . . 9
5.3.1. Scan Parameter Message Element . . . . . . . . . . . 9 4.3.2. IEEE 802.11 Channel Bind Message Element . . . . . . 11
5.3.2. Channel Bind Message Element . . . . . . . . . . . . 10 4.3.3. IEEE 802.11 Channel Scan Report . . . . . . . . . . . 12
5.3.3. Channel Scan Report . . . . . . . . . . . . . . . . . 11 4.3.4. IEEE 802.11 Neighbor WTP Report . . . . . . . . . . . 14
5.3.4. Neighbor WTP Report . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Normative References . . . . . . . . . . . . . . . . . . . . 15
10. Normative References . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
IEEE 802.11n standard was published in 2009 and it is an amendment to The 802.11-2009 [IEEE 802.11n.2009] standard was published in 2009 as
the IEEE 802.11-2007 standard. The maximum data rate increases to an amendment to the IEEE 802.11-2007 standard to improve network
600Mbps. In the physical layer, 802.11n use OFDM and MIMO to achieve throughput. The maximum data rate increases to 600Mbps. In the
the high throughput. 802.11n also use multiple antennas to form physical layer, 802.11n uses Orthogonal Frequency Division
antenna array which can be dynamically adjusted to improve the signal Multiplexing (OFDM) and Multiple Input/Multiple Output (MIMO) to
strength and extend the coverage. achieve the high throughput. 802.11n uses multiple antennas to form
an antenna array which can be dynamically adjusted to improve the
signal strength and extend the coverage.
There are several capabilities of 802.11n need to be supported by Capabilities of 802.11n such as radio capability, radio configuration
CAPWAP control message, such as radio capability, radio configuration and station information need to be supported by CAPWAP control
and station information etc. This document specifies the 802.11n and messages. The necessary extensions for this purpose are introduced
power/channel auto-configuration extensions for CAPWAP. in Section 3 and specified in Section 4.
For the AC/WTP that does not support the extensions defined by this For IEEE 802.11 in general, it is desirable to be able to support
document, it can simply ignore the extensions and will not cause any power and channel auto reconfiguration. Extensions for this purpose
incompatible issue. are specified in Section 5.
2. Conventions used in this document 2. Terminology
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Abbreviations This document uses the following abbreviations:
AC: Access Controller
A-MSDU:Aggregate MAC Service Data Unit
A-MPDU:Aggregate MAC Protocol Data Unit
MIMO: Multi-input Multi-output
MSDU: MAC Service Data Unit
MPDU: MAC Protocol Data Unit
MCS: Maximum Modulation and Coding Scheme
OFDM: Orthogonal Frequency-Division Multiplexing
WTP: Wireless Termination Points.
4. CAPWAP 802.11n Support AC Access Controller
A-MSDU Aggregate MAC Service Data Unit
A-MPDU Aggregate MAC Protocol Data Unit
AC Access Controller
GI Guard Interval
MCS Maximum Modulation and Coding Scheme
MIMO Multiple Input/Multiple Output
MPDU MAC Protocol Data Unit
MSDU MAC Service Data Unit
OFDM Orthogonal Frequency Division Multiplexing
TSF timing synchronization function
WTP Wireless Termination Point
[IEEE-802.11.2009] standard was published in 2009 and it is an 3. CAPWAP 802.11n Support
amendment of the IEEE 802.11-2007 standard to improve throughput.
The maximum data rate increases to 600Mbps. In the physical layer,
802.11n use OFDM and MIMO to achieve high throughput. 802.11n use
multiple antennas to form antenna array which can be dynamically
adjusted to improve the signal strength and extend the coverage.
802.11n support three modes of channel usage: 20MHz mode, 40MHz mode 802.11n supports three modes of channel usage: 20MHz mode, 40MHz mode
and mixed mode. 802.11n has a new feature called channel binding. It and mixed mode. 802.11n has a new feature called channel binding. It
can bind two adjacent 20MHz channel to one 40MHz channel to improve can bind two adjacent 20MHz channel to one 40MHz channel to improve
the throughput.If using 40MHz channel configuration there will be the throughput.If using 40MHz channel configuration there will be
only one non-overlapping channel in 2.4GHz. In the large scale only one non-overlapping channel in the 2.4GHz band. In the large
deployment scenario, operator need to use 20MHz channel configuration scale deployment scenario, the operator needs to use 20MHz channel
in 2.4GHz to allow more non-overlapping channels. configuration in the 2.4GHz band to allow more non-overlapping
channels.
In MAC layer, a new feature of 802.11n is Short Guard Interval(GI). In the MAC layer, a new feature of 802.11n is Short Guard
802.11a/g uses 800ns guard interval between the adjacent information Interval(GI). 802.11a/g uses an 800ns guard interval between the
symbols. In 802.11n, the GI can be configured to 400nm under good adjacent information symbols. In 802.11n, the GI can be configured
wireless condition. to 400nm under good wireless conditions.
Another feature in 802.11 MAC layer is Block ACK. 802.11n can use one Another feature in the 802.11 MAC layer is Block ACK. 802.11n can use
ACK frame to acknowledge several MPDU receiving event. one ACK frame to acknowledge several MAC Protocol Data Unit (MPDU)
receiving events.
CAPWAP needs to be extended to support the above new 802.11n CAPWAP needs to be extended to support the above new 802.11n
features. For example, CAPWAP should allow the access controller to features. CAPWAP should allow the access controller to know the
know the supported 802.11n features of WTP and the access controller supported 802.11n features and the access controller should be able
should be able to configure the different channel binding modes for to configure the different channel binding modes. This document
WTP. defines extensions of the CAPWAP 802.11 binding to support 802.11n
features.
4.1. CAPWAP Extension for 802.11n Support 3.1. CAPWAP Extension for 802.11n Support
There are three 802.11n features need to be supported by CAPWAP Three 802.11n features need to be supported by CAPWAP 802.11 binding:
802.11 binding: 802.11n radio capability, 802.11n radio configuration 802.11n radio capability, 802.11n radio configuration and station
and station information. This section defines the extension of information. This section defines the extension of the current
current CAPWAP 802.11 binding to support 802.11n features. CAPWAP 802.11 binding to support the 802.11n features.
4.1.1. 802.11n Radio Capability Information 3.1.1. 802.11n Radio Capability Information
[RFC5416] defines IEEE 802.11 binding for CAPWAP protocol. It [RFC5416] defines the IEEE 802.11 binding for the CAPWAP protocol.
defines IEEE 802.11 Information Element (Type 1029) which is used to It defines the IEEE 802.11 Information Element, which is used to
communicate any IE defined in IEEE 802.11 protocol. The detail communicate any information element (IE) defined in the IEEE 802.11
definition of IEEE 802.11 Information Element is in section 6.6 of protocol. This document specifies that the IEEE 802.11 Information
[RFC5416]. The IEEE 802.11 HT information element is defined in Element defined in section 6.6 of [RFC5416] SHALL be used to
section 8.4.2.58 of [IEEE-802.11.2012]. It contains the 802.11n transport the IEEE 802.11 HT information element defined in section
radio capability information. This document specifies use of the 8.4.2.58 of [IEEE-802.11.2012]. The HT IE MAY in this way be
IEEE 802.11 Information Element (Type 1029) transporting the IEEE included in CAPWAP Configuration Status Request/Response messages.
802.11 HT information element to carry the 802.11n radio capability
information. 802.11n radio capability information MAY be included in
the CAPWAP Configuration Status Request/Response messages.
4.1.2. 802.11n Radio Configuration Message Element 3.1.2. 802.11n Radio Configuration Message Element
The 802.11n Radio Configuration Information Element message element The 802.11n Radio Configuration message element is used by the AC to
is used by the AC to configure a Radio on the WTP and by the WTP to provide IEEE 802.11n-specific configuration for a Radio on the WTP,
deliver its radio configuration to the AC. The 802.11n Radio and by the WTP to deliver its radio configuration to the AC. This
Configuration Information Element is defined in figure 1. 802.11n supplements the IEEE 802.11 WTP WLAN Radio Configuration message
Radio Configuration Message Element MAY be included in the CAPWAP element defined in [RFC5416]. The format of the 802.11n Radio
Configuration message element is shown in Figure 1. The 802.11n
Radio Configuration message element MAY be included in the CAPWAP
Configuration Update Request/Response message. Configuration Update Request/Response message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID |S|P|N|G|B| | MaxSup MCS | Max MandMCS | | Radio ID |S|P|N|G|B| | MaxSup MCS | Max MandMCS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TxAntenna | RxAntenna | Reserved | | TxAntenna | RxAntenna | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: 802.11n Radio Configuration Message Element Figure 1: 802.11n Radio Configuration Message Element
Type: TBD for 802.11n Radio Configuration Message Element. Type: TBD1 for 802.11n Radio Configuration Message Element.
Length: 16. Length: 16.
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.
S bit: A-MSDU Cfg: Enable/disable Aggregate MAC Service Data Unit S bit: A-MSDU configuration: Enable/disable Aggregate MAC Service
(A-MSDU). Set to 0 if disabled. Set to 1 if enabled. Data Unit (A-MSDU). Set to 0 if disabled. Set to 1 if enabled.
P bit: A-MPDU Cfg: Enable/disable Aggregate MAC Protocol Data Unit P bit: A-MPDU configuration: Enable/disable Aggregate MAC Protocol
(A-MPDU). Set to 0 if disabled. Set to 1 if enabled. Data Unit (A-MPDU). Set to 0 if disabled. Set to 1 if enabled.
N bit: 11n Only Cfg: Whether to allow only 11n user access. Set to 0 N bit: 11n Only configuration: Whether to allow only 11n user access.
if allow non-802.11n user access. Set to 1 if do not allow Set to 0 if non-802.11n user access is allowed. Set to 1 if
non-802.11n user access. non-802.11n user access is not allowed.
G bit: Short GI Cfg: Set to 0 if disabled. Set to 1 if enabled. G bit: Short GI configuration: Set to 0 if Short Guard Interval is
disabled. Set to 1 if enabled.
B bit: Bandwidth Cfg: Bandwidth binding mode. Set to 0 if 40MHz B bit: Bandwidth binding mode configuration: Set to 0 if 40MHz
binding mode. Set to 1 if 20MHz binding mode. binding mode. Set to 1 if 20MHz binding mode.
MaxSup MCS: Maximum Modulation and Coding Scheme (MCS) index. It Maximum supported MCS: Maximum Modulation and Coding Scheme (MCS)
indicates the maximum MCS index that the WTP or the STA can support. index. It indicates the maximum MCS index that the WTP or the STA
can support.
Max Mandatory MCS: Maximum Mandatory Modulation and Coding Scheme Max Mandatory MCS: Maximum Mandatory Modulation and Coding Scheme
(MCS) index. Mandatory rates must be supported by the WTP and the (MCS) index. Mandatory rates must be supported by the WTP and the
STA that want to associate with the WTP. STA that want to associate with the WTP.
TxAntenna: Transmitting antenna configuration. Each TxAntenna bit TxAntenna: Transmitting antenna configuration. Each TxAntenna bit
represent a certain number of antennas. Set to 1 if enabled, set to represents a certain number of antennas. Set to 1 if enabled, set to
0 if disabled. 0 if disabled.
RxAntenna: Receiving antenna configuration. Each RxAntenna bit RxAntenna: Receiving antenna configuration. Each RxAntenna bit
represent a certain number of antennas. Set to 1 if enabled, set to represents a certain number of antennas. Set to 1 if enabled, set to
0 if disabled. 0 if disabled.
The detail definition of TxAntenna/RxAntenna is as follows: The detail definition of TxAntenna/RxAntenna is as follows:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|8|7|6|5|4|3|2|1| |8|7|6|5|4|3|2|1|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 2: Definition of TxAntenna/RxAntenna Figure 2: Definition of TxAntenna/RxAntenna
skipping to change at page 5, line 43 skipping to change at page 6, line 4
0 if disabled. 0 if disabled.
The detail definition of TxAntenna/RxAntenna is as follows: The detail definition of TxAntenna/RxAntenna is as follows:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|8|7|6|5|4|3|2|1| |8|7|6|5|4|3|2|1|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 2: Definition of TxAntenna/RxAntenna Figure 2: Definition of TxAntenna/RxAntenna
Each bit when enabled will represent the number of antennas Each bit when enabled will represent the number of antennas
correspondent to that bit. For example, when the first bit is correspondent to that bit. Only one bit is allowed to be set to 1.
enabled,it represents 8 antennas. For example, when the first bit is enabled,it represents 8 antennas.
4.1.3. 802.11n Station Information 3.1.3. 802.11n Station Information
The 802.11n Station Information message element is used to deliver The 802.11n Station Information message element is used to deliver
IEEE 802.11n station policy from the AC to the WTP. The definition IEEE 802.11n station policy from the AC to the WTP. The definition
of the 802.11n Station Information message element is in figure 3. of the 802.11n Station Information message element is in figure 3.
802.11n Station Information MAY be included in the CAPWAP Station The format of 802.11n Station Information MAY be included in the
Configuration Request message. CAPWAP Station Configuration Request message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |S| P |T|F|H|M| | Max RxFactor | | MAC Address |S| P |T|F|H|M| | Max RxFactor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min StaSpacing| HiSuppDataRate | AMPDUBufSize | | Min StaSpacing| HiSuppDataRate | AMPDUBufSize |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AMPDUBufSize | HtcSupp | MCS Set | | AMPDUBufSize | HtcSupp | MCS Set |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MCS Set | | MCS Set |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MCS Set | | MCS Set |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: 802.11n Station Information Figure 3: 802.11n Station Information
Type: TBD for 802.11 Station Information. MAC Address: The station's MAC Address.
Type: TBD2 for 802.11 Station Information.
Length: 24. Length: 24.
S bit: SupChanl width: Supporting bandwidth mode. 0x00: 20MHz S bit: Supporting bandwidth mode. 0x00: 20MHz bandwidth mode. 0x01:
bandwidth mode. 0x01: 40MHz bandwidth binding mode. 40MHz bandwidth binding mode.
P flag: Power Save: 0x00: Static power saving mode. 0x01: Dynamic P flag: Power Saving mode: 0x00: Static. 0x01: Dynamic. 0x03: Do
power saving mode. 0x03: Do not support power saving mode. not support power saving mode.
T bit: ShortGi20: Whether support short GI in 20MHz bandwidth mode. T bit: Whether to support short GI in 20MHz bandwidth mode. 0x00: Do
0x00: Do not support short GI. ox01: Support short GI. not support short GI. 0x01: Support short GI.
F bit: ShortGi40: Whether support short GI in 40MHz bandwidth mode. F bit: ShortGi40: Whether to support short GI in 40MHz bandwidth
0x00: Do not support short GI. ox01: Support short GI. mode. 0x00: Do not support short GI. 0x01: Support short GI.
H bit: HtDelyBlkack: Whether block Ack support delay mode. 0x00: Do H bit: Whether Block Ack supports delay mode. 0x00: Do not support
not support delay mode. 0x01: Support delay mode. delay mode. 0x01: Support delay mode.
M bit: Max Amsdu: The maximal AMSDU length. 0x00: 3839 bytes. 0x01: M bit: The maximal A-MSDU length. 0x00: 3839 bytes. 0x01: 7935
7935 bytes. bytes.
Max RxFactor: The maximal receiving AMPDU factor. Max RxFactor: The maximal receiving A-MPDU factor.
Min StaSpacing: Minimum MPDU Start Spacing. Min StaSpacing: Minimum MPDU Start Spacing.
HiSuppDataRate: Maximal transmission speed (Mbps). HiSuppDataRate: Maximal transmission speed (Mbps).
AMPDUBufSize: AMPDU buffer size. AMPDUBufSize: A-MPDU buffer size (Byte).
HtcSupp: Whether the packet have HT header. HtcSupp: Whether to place HT headers on the packets forwarded from
this station.
MCS Set: The MCS bitmap that the station supports. MCS Set: The MCS bitmap that the station supports.
5. Power and Channel Autoconfiguration 4. Power and Channel Autoconfiguration
Power and channel autoconfiguration could avoid potential radio Power and channel autoconfiguration could avoid potential radio
interference and improve the WLAN performance. In general, the auto- interference and improve the WLAN performance. In general, the auto-
configuration of radio power and channel could occur at two stages: configuration of radio power and channel could occur at two stages:
when the WTP power on or during the WTP running time. when the WTP power on or during the WTP running time.
5.1. Channel Autoconfiguration When WTP Power On 4.1. Channel Autoconfiguration When WTP Power On
When the WTP is power-on, it is of necessity to configure a proper Power and channel auto reconfiguration avoids potential radio
channel to the WTP in order to achieve best status of radio links. interference and improves the WLAN performance. In general, the
auto- configuration of radio power and channel can occur at two
stages: when the WTP powers on or while the WTP is in running state.
When the WTP is powered-on, it needs to configure a proper channel.
IEEE 802.11 Direct Sequence Control elements or IEEE 802.11 OFDM IEEE 802.11 Direct Sequence Control elements or IEEE 802.11 OFDM
Control element defined in RFC5416 SHOULD be carried in the Configure Control element defined in RFC5416 SHOULD be carried in the Configure
Status Response message to offer WTP a channel at this stage. If Status Response message to offer WTP a channel at this stage. If the
those information element is zero, the WTP will need to determine its channel field of those information element is set to 0, the WTP will
channel by itself, otherwise the WTP SHOULD be configured according need to determine its channel by itself, otherwise the WTP SHOULD be
to the provided information element. configured according to the provided information element.
When the WTP determines its own channel configuration, it should When the WTP determines its own channel configuration, it should
first scan the channel information, then determine which channel it first scan the channel information, then determine which channel it
will work on and form a channel quality scan report. The channel will work on and form a channel quality scan report. As shown in
quality report will be sent to the AC using WTP Event Request message Figure 3, the AC can control the scanning process by sending the IEEE
by the WTP. 802.11 Scan Parameters message element defined in Section 5.1 to the
WTP in a Configure Status Response message or in a WTP Configure
Update Request message. The WTP will send the channel quality report
to the AC using the WTP Event Request message.
AC will determine whether to change the channel configuration based AC will determine whether to change the channel configuration based
on the received channel quality report. The AC can use IEEE 802.11 on the received channel quality report. The AC MAY use a IEEE 802.11
Direct Sequence Control or IEEE 802.11 OFDM Control information Direct Sequence Control or IEEE 802.11 OFDM Control message element
element carried by the configure Update Request message to configure carried by the configure Update Request message to configure a new
a new channel for the WTP. channel for the WTP.
5.2. Power Configuration When WTP Power On 4.2. Power Configuration When WTP Power On
IEEE 802.11 Tx Power information element is used by the AC to control The IEEE 802.11 Tx Power message element defined in section 6.18 of
the transmission power of the WTP. The 802.11 Tx Power information [RFC5416] is used by the AC to control the transmission power of the
element is carried in the Configure Status Response message or in the WTP. The 802.11 Tx Power information element is carried in the
Configure Update Request message. Configure Status Response message or in the Configure Update Request
message.
5.3. Channel/Power Auto Adjusment 4.3. Channel/Power Auto Adjusment
The Channel Scan Procedure is illustrated by the figure 4. The Channel Scan Procedure is illustrated by the figure 4.
WTP Configure Status Req AC WTP Configure Status Req AC
-------------------------------------------------------> ------------------------------------------------------->
Configure Status Res(Scan Parameter Message Element, Channel Bind Message Element) Configure Status Res(Scan Parameter Message Element, Channel Bind Message Element)
<------------------------------------------------------ <------------------------------------------------------
or or
WTP AC WTP AC
Configure Update Req(Scan Parameter Message Element, Channel Bind Message Element ) Configure Update Req(Scan Parameter Message Element, Channel Bind Message Element )
<----------------------------------------------------- <-----------------------------------------------------
Configure Update Res Configure Update Res
-----------------------------------------------------> ----------------------------------------------------->
Figure 4: Channel Scan Procedure Figure 4: Channel Scan Procedure
WTP has two working modes, the first one is normal working mode. In The WTP has two work modes: normal mode and scan only mode. In
this mode, the WTP can scan the channel while providing the service normal mode, the WTP can provide service for station access and scan
to STA. Whether WTP will provide scanning service is determined by channels at the same time. Whether the WTP will scan a given set of
the Max Cycles value of Channel Bind Message Element. If this value channels is determined by the Max Cycles field in the IEEE 802.11
equls to zero, the WTP will not perform scanning. If this value Channel Bind message element defined in Section 5.2. When this field
equls to 255, the WTP will scan the channel continuously until is set to 0, the WTP will not scan the channel. If this field is set
getting notification from AC. Otherwise, the WTP will perform to 255, the WTP will scan the channel continuously. The type of the
scanning with the number that specified the value of Max Cycles. The scan is determined by the Scan Type field. With the passive scan
second working mode is scan only mode. The WTP will not provide type, the WTP monitors the air interface, using the received beacon
service to STA in this case. In this mode, WTP will scan the channel frames to determine the nearby WTPs. With the active scan type, the
continuously. WTP will send a probe message and receive probe response messages.
When the WTP work in the scan only mode, there is no difference In the normal scan mode, the WTP behaviour is controlled by three
between the working channel and scan channel. Every channel's scan parameters: PrimeChlSrvTime, OnChannelScanTIme, and
duration will be OffChannelScnTime and the PrimeChlSrvTime and OffChannelScnTIme. These are provided by the IEEE 802.11 Scan
OnChannelScanTime is set to 0. Parameters message element defined in Section 5.1. The WTP will
provide access service for stations for the duration given by
PrimeChlSrvTime. It then scans the working channel for the duration
given by OnChannelScnTime. It returns to servicing station access
requests on the working channel for another period of length
PrimeChlSrvTime, then moves to a different channel and scans it for
duration OffChannelScnTIme. It repeats this cycle, scanning a new
non-working channel each time, until all the channels have been
scanned.
There are two scan types which is determined by the Scan Type value. When the WTP works in scan only mode, it does not distinguish between
The first type is passive scan. The WTP will listen the channel the working channel and scan channel. Every channel's scan duration
passively in this case. The other type is active scan. The WTP will will be OffChannelScnTime and PrimeChlSrvTime and OnChannelScanTime
send probe for the scan. There are three parameters that will MUST be set to 0.
determine the working mode of scan: PrimeChlSrvTime, On Channel
ScanTime, Off Channel ScanTime. The WTP will provide service for the
period of "PrimeChlSrvTime" time then start channel scan for the
period of "On Channel ScanTime" time; then continue to provide
service for the period of "PrimeChlSrvTime" time; then leave the
current working channel and scan next channel for the period of "Off
Channel ScanTime" time; then provide service on the next channel for
the period of "PrimeChlSrvTime"..until finishing the scan procedure.
5.3.1. Scan Parameter Message Element As shown in Figure 4, the AC can control the scan behaviour at the
WTP by including the IEEE 802.11 Scan Parameters and IEEE 802.11
Channel Bind message elements in a Configure Status Response or WTP
Configure Update Request message.
The definition of the Scan Para Message Element is as follows: Scan Report. After completing its scan, the WTP MAY send the scan
report to the AC using a WTP Event Request message. The scan report
information is carried in the IEEE 802.11 Channel Scan Report message
element (Section 5.3) and an instance of the IEEE 802.11 Information
Element message element carrying a copy of theIEEE 802.11 Neighbor
WTP Report information element (Section 5.4).
0 1 2 3 4.3.1. IEEE 802.11 Scan Parameters Message Element
The format of the IEEE 802.11 Scan Parameters Message Element is as
shown in Figure 5:
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 |M|S|L|D| | Report Time | | Radio ID |M|S|L|D| | Report Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PrimeChlSrvTime | On Channel ScanTime | | PrimeChlSrvTime | On Channel ScanTime |
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| Off Channel ScanTime | | Off Channel ScanTime |
+-------------------------------+ +-------------------------------+
Figure 5: Scan Parameter Message Element Figure 5: IEEE 802.11 Scan Parameters Message Element
Type: TBD for Scan Parameter Message Element. Type: TBD3 for IEEE 802.11 Scan Parameters Message Element.
Length: 10. Length: 10.
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.
M bit: AP oper mode: the work mode of the WTP. 0x01:normal mode. M bit: Work mode of the WTP. 0x00:normal mode. 0x01: monitor only
0x02: monitor only mode, no service is provided in this mode.ss mode, no service is provided in this mode.
S bit: Scan Type: 0x01: active scan; 0x02: passive scan. S bit: Scan Type: 0x00: active scan; 0x01: passive scan.
L bit: L=1: Open Load Balance Scan. D bit: D=1: Open Rogue WTP L bit: L=1: Open Load Balance Scan. L=0: Disable Load Balance Scan.
D bit: D=1: Open Rogue WTP detection scan. D=0: Disable Rouge WTP
detection scan. detection scan.
Report Time: Channel quality report time (unit: second). Report Time: Channel quality report time (unit: second).
PrimeChlSrvTime: Service time (unit: millisecond) on the working scan PrimeChlSrvTime: Service time (unit: millisecond) on the working scan
channel. This segment is invalid(set to 0) when WTP oper mode is set channel. This segment is invalid(set to 0) when WTP oper mode is set
to 2. The maximum value of this segment is 10000, the minimum value to 1. The maximum value of this segment is 10000, the minimum value
of this segment is 5000, the default value is 5000. of this segment is 5000, the default value is 5000.
On Channel ScanTime: The scan time (unit: millisecond) of the working On Channel ScanTime: The scan time (unit: millisecond) of the working
channel. When the WTP oper mode is set to 2, this segment is channel. When the WTP oper mode is set to 2, this segment is
invalid(set to 0). The maximum value of this segment is 120, the invalid(set to 0). The maximum value of this segment is 120, the
minimum value of this segment is 60, the default value is 60. minimum value of this segment is 60, the default value is 60.
5.3.2. Channel Bind Message Element Off Channel ScanTime: The scan time (unit: millisecond) of the
working channel. When the WTP operating mode is set to 2, this
segment MUST be set to 0. The maximum value of this segment is 120,
the minimum value of this segment is 60, the default value is 60.
The definition of the Channel Bind Message ELement is as follows: 4.3.2. IEEE 802.11 Channel Bind Message Element
0 1 2 3 The format of the IEEE 802.11 Channel Bind Message Element is as
follows:
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 | Max Cycles |Channel Count |ScanChannelSet.| | Flag | Max Cycles |Channel Count |ScanChannelSet.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Channel Bind Message Element Figure 6: IEEE 802.11 Channel Bind Message Element
Type: TBD for Channel Bind Message Element. Type: TBD4 for IEEE 802.11 Channel Bind Message 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.
Flag: bitmap, reserved. Flag: bitmap, reserved.
Max Cycles: Scan repeat times. 255 means continuous scan. Max Cycles: Number of times the scanning cycle is repeated for the
set of channels identified by this message element. 255 means
continuous scan.
Channel Count: The number of channel will be scanned. Channel Count: The number of channels will be scanned.
Scan Channel Set: The channel information. The format is as follows: Scan Channel Set: identifies the members of the set of channels to
which this message element instance applies. The format for each
channel is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Channel ID | Flag | | Channel ID | Flag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Channel Information Format Figure 7: Channel Information Format
Channel ID: the channel ID of the channel which will be scanned. Channel ID: the channel ID of the channel which will be scanned.
Flag: Bitmap, reserved for future use. Flag: Bitmap, reserved for future use.
5.3.3. Channel Scan Report 4.3.3. IEEE 802.11 Channel Scan Report
There are two types of scan report: Channel Scan Reprot and Neighbor There are two types of scan report: Channel Scan Reprot and Neighbor
STA Reprot. Channel Scan Report is used to channel autoconfiguration STA Reprot. Channel Scan Report is used to channel autoconfiguration
while Neighbor WTP Report is used to power autoconfiguration. The while Neighbor WTP Report is used to power autoconfiguration. The
WTP send the scan report to the AC through WTP Event Request message. WTP send the scan report to the AC through WTP Event Request message.
The information element that used to carry the scan report is Channel The information element that used to carry the scan report is Channel
Scan Report Message Element and Neighbor WTP Report Message Element. Scan Report Message Element and Neighbor WTP Report Message Element.
The definition of the Channel Scan Report Message Element is in The format of the IEEE 802.11 Channel Scan Report message element is
figure 8. in Figure 8.
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 | Report Count | Channel Scan Report | | Radio ID | Report Count | Channel Scan Report |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
Figure 8: Channel Scan Report Message Element Figure 8: IEEE 802.11 Channel Scan Report Message Element
Type: TBD for Channel Scan Report Message Element. Type: TBD5 for IEEE 802.11 Channel Scan Report message element.
Length: >=29. Length: >=29.
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.
Report Count: The channel number will be reported. Report Count: The number of channels for which a report is provided.
Channel Scan Report: The definition of the Channel Scan Report is in Channel Scan Report: The format of each Channel Scan Report is shown
figure 9. It complies with the IEEE 802.11 Beacon report that in Figure 9. It complies with the IEEE 802.11 Beacon report that
defined in section 8.4.2.24.7 of [IEEE-802.11.2012]. defined in section 8.4.2.24.7 of [IEEE-802.11.2012].
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Operating Class|Channel Number |Actual Measurement Start Time..| |Operating Class|Channel Number |Actual Measurement Start Time..|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Actual Measurement Start Time | | ...Actual Measurement Start Time |
|-------------------------------+-------------------------------+ |-------------------------------+-------------------------------+
|..Actual Measurement Start Time| Measurement Duration | |..Actual Measurement Start Time| Measurement Duration |
+---------------+---------------+-------------------------------+ +---------------+---------------+-------------------------------+
|Reported Frame | RCPI | BSSID... | |Reported Frame | RCPI | BSSID... |
+---------------+---------------+-------------------------------+ +---------------+---------------+-------------------------------+
| ...BSSID | | ...BSSID |
+---------------+-----------------------------------------------+ +---------------+-----------------------------------------------+
| Antena ID | Parent TSF... | | Antenna ID | Parent TSF... |
+---------------+-----------------------------------------------+ +---------------+-----------------------------------------------+
|...Parent TSF | Optional Subelements(variable) | |...Parent TSF | Optional Sub-elements(variable) |
+---------------+-----------------------------------------------+ +---------------+-----------------------------------------------+
Figure 9: Channel Scan Report Figure 9: Channel Scan Report
Operating Class: Indicates the channel set for which the measurement Operating Class: Indicates the channel set for which the measurement
request applies. The definition of this field complies with the request applies. The definition of this field complies with the
definition in section 8.4.2.24.7 of [IEEE-802.11.2012]. definition in section 8.4.2.24.7 of [IEEE-802.11.2012].
Channel Number: Indicates the channel number for which the Channel Number: Indicates the channel number for which the
measurement report applies. The definition of this field complies measurement report applies. The definition of this field complies
with the definition in section 8.4.2.24.7 of [IEEE-802.11.2012]. with the definition in section 8.4.2.24.7 of [IEEE-802.11.2012].
Actual Measurement Start Time: Is set to the value of the measuring Actual Measurement Start Time: Is set to the value of the measuring
STA's TSF timer at the time the measurement started. station's TSF timer at the time the measurement started.
Measurement Duration: Is set to the duration over which the Beacon Measurement Duration: Is set to the duration over which the Beacon
Report was measured. The definition of this field complies with the Report was measured. The definition of this field complies with the
definition in section 8.4.2.24.7 of [IEEE-802.11.2012]. definition in section 8.4.2.24.7 of [IEEE-802.11.2012].
Reported Frame Information: This field contains two subfields as Reported Frame Information: This field contains two subfields as
defined in [IEEE-802.11.2012]. defined in [IEEE-802.11.2012].
RCPI: Indicates the received channel power of the Beacon, Measurement RCPI: Indicates the received channel power of the Beacon, Measurement
Pilot, or Probe Response frame. Pilot, or Probe Response frame.
skipping to change at page 13, line 9 skipping to change at page 14, line 9
RSNI:Indicates the received signal to noise indication for the RSNI:Indicates the received signal to noise indication for the
Beacon, Measurement Pilot, or Probe Response frame. Beacon, Measurement Pilot, or Probe Response frame.
BSSID: This field contains the BSSID from the Beacon,Measurement BSSID: This field contains the BSSID from the Beacon,Measurement
Pilot, or Probe Response frame being reported. Pilot, or Probe Response frame being reported.
Antenna ID: This field contains the identifying number for the Antenna ID: This field contains the identifying number for the
antennas used for this measurement. antennas used for this measurement.
Parent TSF: This field contains the lower 4 octets of the measuring Parent TSF: This field contains the lower 4 octets of the measuring
STA's TSF timer value at the start of reception of the first octet of station's TSF timer value at the start of reception of the first
the timestamp field of the reported Beacon, Measurement Pilot, or octet of the timestamp field of the reported Beacon, Measurement
Probe Response frame at the time the Beacon frame being reported was Pilot, or Probe Response frame at the time the Beacon frame being
received. reported was received.
Optional Subelements: This field contains zero or more subelements. Optional Subelements: This field contains zero or more subelements.
5.3.4. Neighbor WTP Report 4.3.4. IEEE 802.11 Neighbor WTP Report
The neighbor WTP report message element is composed of the IEEE This document specifies that the WTP MAY include an instance of the
802.11 Information Element that defined in section 6.6 of [RFC5416] IEEE 802.11 Neighbor Report Element defined in section 8.4.2.39 of
and IEEE 802.11 Neighbor Report Element that defined in section [IEEE-802.11.2012] within IEEE 802.11 Information Element message
8.4.2.39 of [IEEE-802.11.2012]. The Neighbor Report Element is element defined in section 6.6 of [RFC5416] to report neighbouring
carried by the IEEE 802.11 Information Element to form the neighbor WTP information to the AC.
WTP report message element.
6. Security Considerations 5. Security Considerations
This document is based on RFC5415/RFC5416 and it doesn't increase any This document is based on RFC5415/RFC5416 and adds no new security
security risk. The security considerations of this document aligns considerations.
with RFC5415/5416.
7. IANA Considerations 6. IANA Considerations
The extension defined in this document need to extend CAPWAP IEEE The extension defined in this document need to extend CAPWAP IEEE
802.11 binding message element which is defined in section 6 of 802.11 binding message element which is defined in section 6 of
[RFC5416]. The following IEEE 802.11 specific message element type [RFC5416]. The following IEEE 802.11 specific message element type
need to be defined by IANA. need to be defined by IANA.
802.11n Radio Configuration Message Element type value described in TBD1: 802.11n Radio Configuration Message Element type value
section 4.1.2. described in section 4.1.2.
802.11n Station Message Element type value described in section TBD2: 802.11n Station Message Element type value described in section
4.1.3. 4.1.3.
Scan Parameter Message Element type value described in section 5.3.1. TBD3: 802.11 Scan Parameter Message Element type value described in
section 5.3.1.
Channel Bind Message Element type value described in section 5.3.2. TBD4: 802.11 Channel Bind Message Element type value described in
section 5.3.2.
Channel Scan Report Message Element type value described in section TBD5: Channel Scan Report Message Element type value described in
5.3.3. section 5.3.3.
8. Contributors 7. Contributors
This draft is a joint effort from the following contributors: This draft is a joint effort from the following contributors:
Gang Chen: China Mobile chengang@chinamobile.com Gang Chen: China Mobile chengang@chinamobile.com
Naibao Zhou: China Mobile zhounaibao@chinamobile.com Naibao Zhou: China Mobile zhounaibao@chinamobile.com
Chunju Shao: China Mobile shaochunju@chinamobile.com Chunju Shao: China Mobile shaochunju@chinamobile.com
Hao Wang: Huawei3Come hwang@h3c.com Hao Wang: Huawei3Come hwang@h3c.com
skipping to change at page 14, line 27 skipping to change at page 15, line 27
Yakun Liu: AUTELAN liuyk@autelan.com Yakun Liu: AUTELAN liuyk@autelan.com
Xiaobo Zhang: GBCOM Xiaobo Zhang: GBCOM
Xiaolong Yu: Ruijie Networks Xiaolong Yu: Ruijie Networks
Song zhao: ZhiDaKang Communications Song zhao: ZhiDaKang Communications
Yiwen Mo: ZhongTai Networks Yiwen Mo: ZhongTai Networks
9. Acknowledgements Dorothy Stanley: dstanley1389@gmail.com
Tom Taylor: tom.taylor.stds@gmail.com
8. Acknowledgements
The authors would like to thanks Ronald Bonica,Romascanu Dan, Benoit The authors would like to thanks Ronald Bonica,Romascanu Dan, Benoit
Claise, Melinda Shore and Margaret Wasserman for their useful Claise, Melinda Shore and Margaret Wasserman for their useful
suggestions. The authors also thanks Dorothy Stanley and Tom Taylor suggestions. The authors also thanks Dorothy Stanley and Tom Taylor
for their review and useful comments. for their review and useful comments.
10. Normative References 9. Normative References
[IEEE-802.11.2009] [IEEE-802.11.2009]
"IEEE Standard for Information technology - "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems Local and metropolitan area networks - Specific systems Local and metropolitan area networks - Specific
requirements Part 11: Wireless LAN Medium Access Control requirements Part 11: Wireless LAN Medium Access Control
(MAC) and Physical Layer (PHY) Specifications", 2009. (MAC) and Physical Layer (PHY) Specifications", 2009.
[IEEE-802.11.2012] [IEEE-802.11.2012]
"IEEE Standard for Information technology - "IEEE Standard for Information technology -
 End of changes. 104 change blocks. 
243 lines changed or deleted 283 lines changed or added

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