OPSAWG Y. Chen Internet-Draft D. Liu Updates: 5416 (if approved) H. Deng Intended status: Standards Track China Mobile Expires:August 18,September 5, 2014 Lei. Zhu HuaweiFebruary 14,March 4, 2014 CAPWAP Extension for 802.11n and Power/channel Autoconfigurationdraft-ietf-opsawg-capwap-extension-02draft-ietf-opsawg-capwap-extension-03 Abstract The CAPWAP binding for 802.11 is specified by RFC5416 and it was based on IEEE 802-11.2007 standard.After RFC5416 was published in 2009, there were severalSeveral new amendments of 802.11 have beenpublished.published since RFC5416 was published in 2009. 802.11n is one of those amendments and it has been widely used in real deployment. This document extends the CAPWAP binding for 802.11 to support 802.11n and also defines a power and channel auto configuration extension. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months 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." This Internet-Draft will expire onAugust 18,September 5, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2.Conventions used in this document . . . . . . .Terminology . . . . . . .3 3. Abbreviations . . . . . .. . . . . . . . . . . . . . . . . . 34.3. CAPWAP 802.11n Support . . . . . . . . . . . . . . . . . . . 34.1.3.1. CAPWAP Extension for 802.11n Support . . . . . . . . . . 44.1.1.3.1.1. 802.11n Radio Capability Information . . . . . . . . 44.1.2.3.1.2. 802.11n Radio Configuration Message Element . . . . . 44.1.3.3.1.3. 802.11n Station Information . . . . . . . . . . . . . 65.4. Power and Channel Autoconfiguration . . . . . . . . . . . . . 75.1.4.1. Channel Autoconfiguration When WTP Power On . . . . . . . 75.2.4.2. Power Configuration When WTP Power On . . . . . . . . . . 85.3.4.3. Channel/Power Auto Adjusment . . . . . . . . . . . . . . 85.3.1.4.3.1. IEEE 802.11 ScanParameterParameters Message Element . . . . .. . . . . .95.3.2.4.3.2. IEEE 802.11 Channel Bind Message Element . . . . . .. . . . . . 10 5.3.3.11 4.3.3. IEEE 802.11 Channel Scan Report . . . . . . . . . . .. . . . . . 11 5.3.4.12 4.3.4. IEEE 802.11 Neighbor WTP Report . . . . . . . . . . .. . . . . . 13 6.14 5. Security Considerations . . . . . . . . . . . . . . . . . . .13 7.14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . .13 8.14 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . .14 9.15 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . .14 10.15 9. Normative References . . . . . . . . . . . . . . . . . . . .1415 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .1516 1. IntroductionIEEE 802.11nThe 802.11-2009 [IEEE 802.11n.2009] standard was published in 2009and it isas an amendment to the IEEE 802.11-2007standard.standard to improve network throughput. The maximum data rate increases to 600Mbps. In the physical layer, 802.11nuse OFDMuses Orthogonal Frequency Division Multiplexing (OFDM) andMIMOMultiple Input/Multiple Output (MIMO) to achieve the high throughput. 802.11nalso useuses multiple antennas to form an antenna array which can be dynamically adjusted to improve the signal strength and extend the coverage.There are several capabilitiesCapabilities of 802.11nneed to be supported by CAPWAP control message,such as radio capability, radio configuration and station informationetc. This document specifies the 802.11n and power/channel auto-configurationneed to be supported by CAPWAP control messages. The necessary extensions forCAPWAP. For the AC/WTP that does not support the extensions defined bythisdocument, it can simply ignore the extensionspurpose are introduced in Section 3 andwill not cause any incompatible issue. 2. Conventions usedspecified in Section 4. For IEEE 802.11 in general, it is desirable to be able to support power and channel auto reconfiguration. Extensions for thisdocumentpurpose are specified in Section 5. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].3. Abbreviations AC:This document uses the following abbreviations: AC Access ControllerA-MSDU:AggregateA-MSDU Aggregate MAC Service Data UnitA-MPDU:AggregateA-MPDU Aggregate MAC Protocol Data UnitMIMO: Multi-input Multi-output MSDU:AC Access Controller GI Guard Interval MCS Maximum Modulation and Coding Scheme MIMO Multiple Input/Multiple Output MPDU MACServiceProtocol Data UnitMPDU:MSDU MACProtocolService Data UnitMCS: Maximum Modulation and Coding Scheme OFDM:OFDM OrthogonalFrequency-DivisionFrequency Division MultiplexingWTP:TSF timing synchronization function WTP Wireless TerminationPoints. 4.Point 3. CAPWAP 802.11n Support[IEEE-802.11.2009] standard was published in 2009 and it is an 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 modes802.11n supports three modes of channel usage: 20MHz mode, 40MHz mode 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 the throughput.If using 40MHz channel configuration there will be only one non-overlapping channel in2.4GHz.the 2.4GHz band. In the large scale deployment scenario, the operatorneedneeds to use 20MHz channel configuration in the 2.4GHz band to allow more non-overlapping channels. In the MAC layer, a new feature of 802.11n is Short Guard Interval(GI). 802.11a/g uses an 800ns guard interval between the adjacent information symbols. In 802.11n, the GI can be configured to 400nm under good wirelesscondition.conditions. Another feature in the 802.11 MAC layer is Block ACK. 802.11n can use one ACK frame to acknowledge severalMPDUMAC Protocol Data Unit (MPDU) receivingevent.events. CAPWAP needs to be extended to support the above new 802.11n features.For example,CAPWAP should allow the access controller to know the supported 802.11n featuresof WTPand the access controller should be able to configure the different channel bindingmodes for WTP. 4.1.modes. This document defines extensions of the CAPWAP 802.11 binding to support 802.11n features. 3.1. CAPWAP Extension for 802.11n SupportThere are threeThree 802.11n features need to be supported by CAPWAP 802.11 binding: 802.11n radio capability, 802.11n radio configuration and station information. This section defines the extension of the current CAPWAP 802.11 binding to support the 802.11n features.4.1.1.3.1.1. 802.11n Radio Capability Information [RFC5416] defines the IEEE 802.11 binding for the CAPWAP protocol. It defines the IEEE 802.11 InformationElement (Type 1029)Element, which is used to communicate anyIEinformation element (IE) defined in the IEEE 802.11 protocol.The detail definition ofThis document specifies that the IEEE 802.11 Information Elementisdefined in section 6.6 of[RFC5416]. The[RFC5416] SHALL be used to transport the IEEE 802.11 HT information elementisdefined in section 8.4.2.58 of [IEEE-802.11.2012].It contains the 802.11n radio capability information. This document specifies use of the IEEE 802.11 Information Element (Type 1029) transporting the IEEE 802.11The HTinformation element to carry the 802.11n radio capability information. 802.11n radio capability informationIE MAY in this way be included intheCAPWAP Configuration Status Request/Response messages.4.1.2.3.1.2. 802.11n Radio Configuration Message Element The 802.11n Radio ConfigurationInformation Elementmessage element is used by the AC toconfigureprovide IEEE 802.11n-specific configuration for a Radio on theWTPWTP, and by the WTP to deliver its radio configuration to the AC. This supplements the IEEE 802.11 WTP WLAN Radio Configuration message element defined in [RFC5416]. The format of the 802.11n Radio ConfigurationInformation Elementmessage element isdefinedshown infigureFigure 1. The 802.11n Radio ConfigurationMessage Elementmessage element MAY be included in the CAPWAP Configuration Update Request/Response message. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Radio ID |S|P|N|G|B| | MaxSup MCS | Max MandMCS | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TxAntenna | RxAntenna | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: 802.11n Radio Configuration Message Element Type:TBDTBD1 for 802.11n Radio Configuration Message Element. Length: 16. Radio ID: An 8-bit value representing the radio, whose value is between one (1) and 31. S bit: A-MSDUCfg:configuration: Enable/disable Aggregate MAC Service Data Unit (A-MSDU). Set to 0 if disabled. Set to 1 if enabled. P bit: A-MPDUCfg:configuration: Enable/disable Aggregate MAC Protocol Data Unit (A-MPDU). Set to 0 if disabled. Set to 1 if enabled. N bit: 11n OnlyCfg:configuration: Whether to allow only 11n user access. Set to 0 ifallownon-802.11n useraccess.access is allowed. Set to 1 ifdo not allownon-802.11n useraccess.access is not allowed. G bit: Short GICfg:configuration: Set to 0 if Short Guard Interval is disabled. Set to 1 if enabled. B bit: BandwidthCfg: Bandwidthbindingmode.mode configuration: Set to 0 if 40MHz binding mode. Set to 1 if 20MHz binding mode.MaxSupMaximum supported MCS: Maximum Modulation and Coding Scheme (MCS) index. It indicates the maximum MCS index that the WTP or the STA can support. Max Mandatory MCS: Maximum Mandatory Modulation and Coding Scheme (MCS) index. Mandatory rates must be supported by the WTP and the STA that want to associate with the WTP. TxAntenna: Transmitting antenna configuration. Each TxAntenna bitrepresentrepresents a certain number of antennas. Set to 1 if enabled, set to 0 if disabled. RxAntenna: Receiving antenna configuration. Each RxAntenna bitrepresentrepresents a certain number of antennas. Set to 1 if enabled, set to 0 if disabled. The detail definition of TxAntenna/RxAntenna is as follows: 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |8|7|6|5|4|3|2|1| +-+-+-+-+-+-+-+-+ Figure 2: Definition of TxAntenna/RxAntenna Each bit when enabled will represent the number of antennas correspondent to that bit. Only one bit is allowed to be set to 1. For example, when the first bit is enabled,it represents 8 antennas.4.1.3.3.1.3. 802.11n Station Information The 802.11n Station Information message element is used to deliver 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. The format of 802.11n Station Information MAY be included in the CAPWAP Station Configuration Request message. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MAC Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MAC Address |S| P |T|F|H|M| | Max RxFactor | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Min StaSpacing| HiSuppDataRate | AMPDUBufSize | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AMPDUBufSize | HtcSupp | MCS Set | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MCS Set | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MCS Set | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: 802.11n Station Information MAC Address: The station's MAC Address. Type:TBDTBD2 for 802.11 Station Information. Length: 24. S bit:SupChanl width:Supporting bandwidth mode. 0x00: 20MHz bandwidth mode. 0x01: 40MHz bandwidth binding mode. P flag: PowerSave:Saving mode: 0x00:Static power saving mode.Static. 0x01:Dynamic power saving mode.Dynamic. 0x03: Do not support power saving mode. T bit:ShortGi20:Whether to support short GI in 20MHz bandwidth mode. 0x00: Do not support short GI.ox01:0x01: Support short GI. F bit: ShortGi40: Whether to support short GI in 40MHz bandwidth mode. 0x00: Do not support short GI.ox01:0x01: Support short GI. H bit:HtDelyBlkack:WhetherblockBlock Acksupportsupports delay mode. 0x00: Do not support delay mode. 0x01: Support delay mode. M bit:Max Amsdu:The maximalAMSDUA-MSDU length. 0x00: 3839 bytes. 0x01: 7935 bytes. Max RxFactor: The maximal receivingAMPDUA-MPDU factor. Min StaSpacing: Minimum MPDU Start Spacing. HiSuppDataRate: Maximal transmission speed (Mbps). AMPDUBufSize:AMPDUA-MPDU buffersize.size (Byte). HtcSupp: Whetherthe packet haveto place HTheader.headers on the packets forwarded from this station. MCS Set: The MCS bitmap that the station supports.5.4. Power and Channel Autoconfiguration Power and channel autoconfiguration could avoid potential radio interference and improve the WLAN performance. In general, the auto- configuration of radio power and channel could occur at two stages: when the WTP power on or during the WTP running time.5.1.4.1. Channel Autoconfiguration When WTP Power OnWhen thePower and channel auto reconfiguration avoids potential radio 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 ispower-on, itin running state. When the WTP isof necessitypowered-on, it needs to configure a properchannel to the WTP in order to achieve best status of radio links.channel. IEEE 802.11 Direct Sequence Control elements or IEEE 802.11 OFDM Control element defined in RFC5416 SHOULD be carried in the Configure Status Response message to offer WTP a channel at this stage. If the channel field of those information element iszero,set to 0, the WTP will need to determine its channel by itself, otherwise the WTP SHOULD be configured according to the provided information element. When the WTP determines its own channel configuration, it should first scan the channel information, then determine which channel it will work on and form a channel quality scan report. As shown in Figure 3, the AC can control the scanning process by sending the IEEE 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 reportwill be sentto the AC using the WTP Event Requestmessage by the WTP.message. AC will determine whether to change the channel configuration based on the received channel quality report. The ACcanMAY use a IEEE 802.11 Direct Sequence Control or IEEE 802.11 OFDM Controlinformationmessage element carried by the configure Update Request message to configure a new channel for the WTP.5.2.4.2. Power Configuration When WTP Power On The IEEE 802.11 Tx Powerinformationmessage element defined in section 6.18 of [RFC5416] is used by the AC to control the transmission power of the WTP. The 802.11 Tx Power information element is carried in the Configure Status Response message or in the Configure Update Request message.5.3.4.3. Channel/Power Auto Adjusment The Channel Scan Procedure is illustrated by the figure 4. WTP Configure Status Req AC -------------------------------------------------------> Configure Status Res(Scan Parameter Message Element, Channel Bind Message Element) <------------------------------------------------------ or WTP AC Configure Update Req(Scan Parameter Message Element, Channel Bind Message Element ) <----------------------------------------------------- Configure Update Res -----------------------------------------------------> Figure 4: Channel Scan Procedure The WTP has twoworking modes, the first one iswork modes: normalworkingmode and scan only mode. Inthisnormal mode, the WTP can provide service for station access and scan channels at thechannel while providing the service to STA.same time. Whether the WTP willprovide scanning servicescan a given set of channels is determined by the Max Cyclesvalue offield in the IEEE 802.11 Channel BindMessage Element. Ifmessage element defined in Section 5.2. When thisvalue equlsfield is set tozero,0, the WTP will notperform scanning.scan the channel. If thisvalue equlsfield is set to 255, the WTP will scan the channelcontinuously until getting notification from AC. Otherwise,continuously. The type of the scan is determined by the Scan Type field. With the passive scan type, the WTP monitors the air interface, using the received beacon frames to determine the nearby WTPs. With the active scan type, the WTP willperform scanning withsend a probe message and receive probe response messages. In thenumber that specifiednormal scan mode, thevalue of Max Cycles. The second working modeWTP behaviour isscan only mode.controlled by three parameters: PrimeChlSrvTime, OnChannelScanTIme, and OffChannelScnTIme. These are provided by the IEEE 802.11 Scan Parameters message element defined in Section 5.1. The WTP willnotprovide access service for stations for the duration given by PrimeChlSrvTime. It then scans the working channel for the duration given by OnChannelScnTime. It returns toSTA in this case. In this mode, WTP will scanservicing station access requests on the working channelcontinuously.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. When the WTPworkworks inthescan only mode,there is no differenceit does not distinguish between the working channel and scan channel. Every channel's scan duration will be OffChannelScnTime andthePrimeChlSrvTime and OnChannelScanTimeisMUST be set to 0.There are twoAs shown in Figure 4, the AC can control the scantypes which is determinedbehaviour at the WTP by including the IEEE 802.11 ScanType value. The first type is passive scan. TheParameters and IEEE 802.11 Channel Bind message elements in a Configure Status Response or WTPwill listenConfigure Update Request message. Scan Report. After completing its scan, thechannel passively in this case. The other type is active scan. TheWTPwillMAY sendprobe forthescan. There are three parameters that will determinescan report to theworking mode of scan: PrimeChlSrvTime, On Channel ScanTime, Off Channel ScanTime. TheAC using a WTPwill provide service for the period of "PrimeChlSrvTime" time then start channelEvent Request message. The scanforreport information is carried in theperiod of "OnIEEE 802.11 ChannelScanTime" time; then continue to provide service for the period of "PrimeChlSrvTime" time; then leave the current working channelScan Report message element (Section 5.3) andscan next channel for the periodan instance of"Off Channel ScanTime" time; then provide service on the next channel fortheperiodIEEE 802.11 Information Element message element carrying a copy of"PrimeChlSrvTime"..until finishing the scan procedure. 5.3.1.theIEEE 802.11 Neighbor WTP Report information element (Section 5.4). 4.3.1. IEEE 802.11 ScanParameterParameters Message Element Thedefinitionformat of the IEEE 802.11 ScanParaParameters Message Element is asfollows: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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Radio ID |M|S|L|D| | Report Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PrimeChlSrvTime | On Channel ScanTime | +-------------------------------+-------------------------------+ | Off Channel ScanTime | +-------------------------------+ Figure 5: IEEE 802.11 ScanParameterParameters Message Element Type:TBDTBD3 for IEEE 802.11 ScanParameterParameters Message Element. Length: 10. Radio ID: An 8-bit value representing the radio, whose value is between one (1) and 31. M bit:AP oper mode: the workWork mode of the WTP.0x01:normal0x00:normal mode.0x02:0x01: monitor only mode, no service is provided in thismode.ssmode. S bit: Scan Type:0x01:0x00: active scan;0x02:0x01: passive scan. 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. Report Time: Channel quality report time (unit: second). PrimeChlSrvTime: Service time (unit: millisecond) on the working scan channel. This segment is invalid(set to 0) when WTP oper mode is set to2.1. The maximum value of this segment is 10000, the minimum value of this segment is 5000, the default value is 5000. On Channel ScanTime: The scan time (unit: millisecond) of the working 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 minimum value of this segment is 60, the default value is 60.5.3.2.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. 4.3.2. IEEE 802.11 Channel Bind Message Element Thedefinitionformat of the IEEE 802.11 Channel Bind MessageELementElement 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Radio IDFlag | Max Cycles |Channel Count |ScanChannelSet.| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 6: IEEE 802.11 Channel Bind Message Element Type:TBDTBD4 for IEEE 802.11 Channel Bind Message Element. Length: 4. Radio ID: An 8-bit value representing the radio, whose value is between one (1) and 31. Flag: bitmap, reserved. Max Cycles:Scan repeat times.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 ofchannelchannels will be scanned. Scan Channel Set:The channel information.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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 7: Channel Information Format Channel ID: the channel ID of the channel which will be scanned. Flag: Bitmap, reserved for future use.5.3.3.4.3.3. IEEE 802.11 Channel Scan Report There are two types of scan report: Channel Scan Reprot and Neighbor STA Reprot. Channel Scan Report is used to channel autoconfiguration while Neighbor WTP Report is used to power autoconfiguration. The 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 Scan Report Message Element and Neighbor WTP Report Message Element. Thedefinitionformat of the IEEE 802.11 Channel Scan ReportMessage Elementmessage element is infigureFigure 8. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Radio ID | Report Count | Channel Scan Report | +---------------------------------------------------------------+ Figure 8: IEEE 802.11 Channel Scan Report Message Element Type:TBDTBD5 for IEEE 802.11 Channel Scan ReportMessage Element.message element. Length: >=29. Radio ID: An 8-bit value representing the radio, whose value is between one (1) and 31. Report Count: Thechannelnumberwill be reported.of channels for which a report is provided. Channel Scan Report: Thedefinitionformat oftheeach Channel Scan Report is shown infigureFigure 9. It complies with the IEEE 802.11 Beacon report that defined in section 8.4.2.24.7 of [IEEE-802.11.2012]. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Operating Class|Channel Number |Actual Measurement Start Time..| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ...Actual Measurement Start Time | |-------------------------------+-------------------------------+ |..Actual Measurement Start Time| Measurement Duration | +---------------+---------------+-------------------------------+ |Reported Frame | RCPI | BSSID... | +---------------+---------------+-------------------------------+ | ...BSSID | +---------------+-----------------------------------------------+ |AntenaAntenna ID | Parent TSF... | +---------------+-----------------------------------------------+ |...Parent TSF | OptionalSubelements(variable)Sub-elements(variable) | +---------------+-----------------------------------------------+ Figure 9: Channel Scan Report Operating Class: Indicates the channel set for which the measurement request applies. The definition of this field complies with the definition in section 8.4.2.24.7 of [IEEE-802.11.2012]. Channel Number: Indicates the channel number for which the measurement report applies. The definition of this field complies 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 measuringSTA'sstation's TSF timer at the time the measurement started. Measurement Duration: Is set to the duration over which the Beacon Report was measured. The definition of this field complies with the definition in section 8.4.2.24.7 of [IEEE-802.11.2012]. Reported Frame Information: This field contains two subfields as defined in [IEEE-802.11.2012]. RCPI: Indicates the received channel power of the Beacon, Measurement Pilot, or Probe Response frame. RSNI:Indicates the received signal to noise indication for the Beacon, Measurement Pilot, or Probe Response frame. BSSID: This field contains the BSSID from the Beacon,Measurement Pilot, or Probe Response frame being reported. Antenna ID: This field contains the identifying number for the antennas used for this measurement. Parent TSF: This field contains the lower 4 octets of the measuringSTA'sstation's TSF timer value at the start of reception of the first octet of the timestamp field of the reported Beacon, Measurement Pilot, or Probe Response frame at the time the Beacon frame being reported was received. Optional Subelements: This field contains zero or more subelements.5.3.4.4.3.4. IEEE 802.11 Neighbor WTP ReportThe neighborThis document specifies that the WTPreport message element is composedMAY include an instance of the IEEE 802.11Information Element that defined in section 6.6 of [RFC5416] and IEEE 802.11Neighbor Report Elementthatdefined in section 8.4.2.39 of[IEEE-802.11.2012]. The Neighbor Report Element is carried by the[IEEE-802.11.2012] within IEEE 802.11 Information Element message element defined in section 6.6 of [RFC5416] toform the neighbor WTPreportmessage element. 6.neighbouring WTP information to the AC. 5. Security Considerations This document is based on RFC5415/RFC5416 andit doesn't increase any security risk. Theadds no new securityconsiderations of this document aligns with RFC5415/5416. 7.considerations. 6. IANA Considerations The extension defined in this document need to extend CAPWAP IEEE 802.11 binding message element which is defined in section 6 of [RFC5416]. The following IEEE 802.11 specific message element type need to be defined by IANA. TBD1: 802.11n Radio Configuration Message Element type value described in section 4.1.2. TBD2: 802.11n Station Message Element type value described in section 4.1.3. TBD3: 802.11 Scan Parameter Message Element type value described in section 5.3.1. TBD4: 802.11 Channel Bind Message Element type value described in section 5.3.2. TBD5: Channel Scan Report Message Element type value described in section 5.3.3.8.7. Contributors This draft is a joint effort from the following contributors: Gang Chen: China Mobile chengang@chinamobile.com Naibao Zhou: China Mobile zhounaibao@chinamobile.com Chunju Shao: China Mobile shaochunju@chinamobile.com Hao Wang: Huawei3Come hwang@h3c.com Yakun Liu: AUTELAN liuyk@autelan.com Xiaobo Zhang: GBCOM Xiaolong Yu: Ruijie Networks Song zhao: ZhiDaKang Communications Yiwen Mo: ZhongTai Networks9.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 Claise, Melinda Shore and Margaret Wasserman for their useful suggestions. The authors also thanks Dorothy Stanley and Tom Taylor for their review and useful comments.10.9. Normative References [IEEE-802.11.2009] "IEEE Standard for Information technology - Telecommunications and information exchange between systems Local and metropolitan area networks - Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", 2009. [IEEE-802.11.2012] "IEEE Standard for Information technology - Telecommunications and information exchange between systems Local and metropolitan area networks - Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", March 2012. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4564] Govindan, S., Cheng, H., Yao, ZH., Zhou, WH., and L. Yang, "Objectives for Control and Provisioning of Wireless Access Points (CAPWAP)", RFC 4564, July 2006. [RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification", RFC 5415, March 2009. [RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11", RFC 5416, March 2009. Authors' Addresses Yifan Chen China Mobile No.32 Xuanwumen West Street Beijing 100053 China Email: chenyifan@chinamobile.com Dapeng Liu China Mobile No.32 Xuanwumen West Street Beijing 100053 China Email: liudapeng@chinamobile.com Hui Deng China Mobile No.32 Xuanwumen West Street Beijing 100053 China Email: denghui@chinamobile.com Lei Zhu Huawei No. 156, Shi-Chuang-Ke-Ji-Shi-Fan-Yuan Beiqing Road, Haidian District Beijing 100095 China Email: lei.zhu@huawei.com