idnits 2.17.1 draft-ietf-opsawg-capwap-extension-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 58 instances of too long lines in the document, the longest one being 15 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The draft header indicates that this document updates RFC5416, but the abstract doesn't seem to directly say this. It does mention RFC5416 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). (Using the creation date from RFC5416, updated by this document, for RFC5378 checks: 2006-10-16) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 10, 2014) is 3637 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'IEEE-802.11.2009' is defined on line 689, but no explicit reference was found in the text == Unused Reference: 'RFC4564' is defined on line 707, but no explicit reference was found in the text == Unused Reference: 'RFC5415' is defined on line 711, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.11.2009' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.11.2012' ** Downref: Normative reference to an Informational RFC: RFC 4564 Summary: 2 errors (**), 0 flaws (~~), 6 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 OPSAWG Y. Chen 2 Internet-Draft D. Liu 3 Updates: 5416 (if approved) H. Deng 4 Intended status: Standards Track China Mobile 5 Expires: Nov 10, 2014 Lei. Zhu 6 Huawei 7 May 10, 2014 9 CAPWAP Extension for 802.11n and Power/channel Autoconfiguration 10 draft-ietf-opsawg-capwap-extension-04 12 Abstract 14 The CAPWAP binding for 802.11 is specified by RFC5416 and it was 15 based on IEEE 802-11.2007 standard. Several new amendments of 802.11 16 have been published since RFC5416 was published in 2009. 802.11n is 17 one of those amendments and it has been widely used in real 18 deployment. This document extends the CAPWAP binding for 802.11 to 19 support 802.11n and also defines a power and channel auto 20 configuration extension. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on September 20, 2014. 39 Copyright Notice 41 Copyright (c) 2014 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. CAPWAP 802.11n Support . . . . . . . . . . . . . . . . . . . 3 59 3.1. CAPWAP Extension for 802.11n Support . . . . . . . . . . 4 60 3.1.1. 802.11n Radio Capability Information . . . . . . . . 4 61 3.1.2. 802.11n Radio Configuration Message Element . . . . . 4 62 3.1.3. 802.11n Station Information . . . . . . . . . . . . . 6 63 4. Power and Channel Autoconfiguration . . . . . . . . . . . . . 7 64 4.1. Channel Autoconfiguration When WTP Power On . . . . . . . 7 65 4.2. Power Configuration When WTP Power On . . . . . . . . . . 8 66 4.3. Channel/Power Auto Adjusment . . . . . . . . . . . . . . 8 67 4.3.1. IEEE 802.11 Scan Parameters Message Element . . . . . 9 68 4.3.2. IEEE 802.11 Channel Bind Message Element . . . . . . 11 69 4.3.3. IEEE 802.11 Channel Scan Report . . . . . . . . . . . 12 70 4.3.4. IEEE 802.11 Neighbor WTP Report . . . . . . . . . . . 14 71 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 73 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 74 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 75 9. Normative References . . . . . . . . . . . . . . . . . . . . 16 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 78 1. Introduction 80 The 802.11-2009 [IEEE 802.11n.2009] standard was published in 2009 as 81 an amendment to the IEEE 802.11-2007 standard to improve network 82 throughput. The maximum data rate increases to 600Mbps. In the 83 physical layer, 802.11n uses Orthogonal Frequency Division 84 Multiplexing (OFDM) and Multiple Input/Multiple Output (MIMO) to 85 achieve the high throughput. 802.11n uses multiple antennas to form 86 an antenna array which can be dynamically adjusted to improve the 87 signal strength and extend the coverage. 89 Capabilities of 802.11n such as radio capability, radio configuration 90 and station information need to be supported by CAPWAP control 91 messages. The necessary extensions for this purpose are introduced 92 in Section 3 and specified in Section 4. 94 For IEEE 802.11 in general, it is desirable to be able to support 95 power and channel auto reconfiguration. Extensions for this purpose 96 are specified in Section 5. 98 2. Terminology 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 This document uses the following abbreviations: 106 AC Access Controller 107 A-MSDU Aggregate MAC Service Data Unit 108 A-MPDU Aggregate MAC Protocol Data Unit 109 AC Access Controller 110 GI Guard Interval 111 MCS Maximum Modulation and Coding Scheme 112 MIMO Multiple Input/Multiple Output 113 MPDU MAC Protocol Data Unit 114 MSDU MAC Service Data Unit 115 OFDM Orthogonal Frequency Division Multiplexing 116 TSF timing synchronization function 117 WTP Wireless Termination Point 119 3. CAPWAP 802.11n Support 121 802.11n supports three modes of channel usage: 20MHz mode, 40MHz mode 122 and mixed mode. 802.11n has a new feature called channel binding. It 123 can bind two adjacent 20MHz channel to one 40MHz channel to improve 124 the throughput.If using 40MHz channel configuration there will be 125 only one non-overlapping channel in the 2.4GHz band. In the large 126 scale deployment scenario, the operator needs to use 20MHz channel 127 configuration in the 2.4GHz band to allow more non-overlapping 128 channels. 130 In the MAC layer, a new feature of 802.11n is Short Guard 131 Interval(GI). 802.11a/g uses an 800ns guard interval between the 132 adjacent information symbols. In 802.11n, the GI can be configured 133 to 400nm under good wireless conditions. 135 Another feature in the 802.11 MAC layer is Block ACK. 802.11n can use 136 one ACK frame to acknowledge several MAC Protocol Data Unit (MPDU) 137 receiving events. 139 CAPWAP needs to be extended to support the above new 802.11n 140 features. CAPWAP should allow the access controller to know the 141 supported 802.11n features and the access controller should be able 142 to configure the different channel binding modes. This document 143 defines extensions of the CAPWAP 802.11 binding to support 802.11n 144 features. 146 3.1. CAPWAP Extension for 802.11n Support 148 Three 802.11n features need to be supported by CAPWAP 802.11 binding: 149 802.11n radio capability, 802.11n radio configuration and station 150 information. This section defines the extension of the current 151 CAPWAP 802.11 binding to support the 802.11n features. 153 3.1.1. 802.11n Radio Capability Information 155 [RFC5416] defines the IEEE 802.11 binding for the CAPWAP protocol. 156 It defines the IEEE 802.11 Information Element, which is used to 157 communicate any information element (IE) defined in the IEEE 802.11 158 protocol. This document specifies that the IEEE 802.11 Information 159 Element defined in section 6.6 of [RFC5416] SHALL be used to 160 transport the IEEE 802.11 HT information element defined in section 161 8.4.2.58 of [IEEE-802.11.2012]. The HT IE MAY in this way be 162 included in CAPWAP Configuration Status Request/Response messages. 164 3.1.2. 802.11n Radio Configuration Message Element 166 The 802.11n Radio Configuration message element is used by the AC to 167 provide IEEE 802.11n-specific configuration for a Radio on the WTP, 168 and by the WTP to deliver its radio configuration to the AC. This 169 supplements the IEEE 802.11 WTP WLAN Radio Configuration message 170 element defined in [RFC5416]. The format of the 802.11n Radio 171 Configuration message element is shown in Figure 1. The 802.11n 172 Radio Configuration message element MAY be included in the CAPWAP 173 Configuration Update Request/Response message. 175 0 1 2 3 176 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 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | Radio ID |S|P|N|G|B| | MaxSup MCS | Max MandMCS | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | TxAntenna | RxAntenna | Reserved | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 Figure 1: 802.11n Radio Configuration Message Element 185 Type: TBD1 for 802.11n Radio Configuration Message Element. 187 Length: 16. 189 Radio ID: An 8-bit value representing the radio, whose value is 190 between one (1) and 31. 192 S bit: A-MSDU configuration: Enable/disable Aggregate MAC Service 193 Data Unit (A-MSDU). Set to 0 if disabled. Set to 1 if enabled. 195 P bit: A-MPDU configuration: Enable/disable Aggregate MAC Protocol 196 Data Unit (A-MPDU). Set to 0 if disabled. Set to 1 if enabled. 198 N bit: 11n Only configuration: Whether to allow only 11n user access. 199 Set to 0 if non-802.11n user access is allowed. Set to 1 if 200 non-802.11n user access is not allowed. 202 G bit: Short GI configuration: Set to 0 if Short Guard Interval is 203 disabled. Set to 1 if enabled. 205 B bit: Bandwidth binding mode configuration: Set to 0 if 40MHz 206 binding mode. Set to 1 if 20MHz binding mode. 208 Maximum supported MCS: Maximum Modulation and Coding Scheme (MCS) 209 index. It indicates the maximum MCS index that the WTP or the STA 210 can support. 212 Max Mandatory MCS: Maximum Mandatory Modulation and Coding Scheme 213 (MCS) index. Mandatory rates must be supported by the WTP and the 214 STA that want to associate with the WTP. 216 TxAntenna: Transmitting antenna configuration. Each TxAntenna bit 217 represents a certain number of antennas. Set to 1 if enabled, set to 218 0 if disabled. 220 RxAntenna: Receiving antenna configuration. Each RxAntenna bit 221 represents a certain number of antennas. Set to 1 if enabled, set to 222 0 if disabled. 224 The detail definition of TxAntenna/RxAntenna is as follows: 226 0 1 2 3 4 5 6 7 227 +-+-+-+-+-+-+-+-+ 228 |8|7|6|5|4|3|2|1| 229 +-+-+-+-+-+-+-+-+ 231 Figure 2: Definition of TxAntenna/RxAntenna 232 Each bit when enabled will represent the number of antennas 233 correspondent to that bit. Only one bit is allowed to be set to 1. 234 For example, when the first bit is enabled,it represents 8 antennas. 236 3.1.3. 802.11n Station Information 238 The 802.11n Station Information message element is used to deliver 239 IEEE 802.11n station policy from the AC to the WTP. The definition 240 of the 802.11n Station Information message element is in figure 3. 241 The format of 802.11n Station Information MAY be included in the 242 CAPWAP Station Configuration Request message. 244 0 1 2 3 245 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 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | MAC Address | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | MAC Address |S| P |T|F|H|M| | Max RxFactor | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Min StaSpacing| HiSuppDataRate | AMPDUBufSize | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | AMPDUBufSize | HtcSupp | MCS Set | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | MCS Set | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | MCS Set | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 Figure 3: 802.11n Station Information 262 MAC Address: The station's MAC Address. 264 Type: TBD2 for 802.11 Station Information. 266 Length: 24. 268 S bit: Supporting bandwidth mode. 0x00: 20MHz bandwidth mode. 0x01: 269 40MHz bandwidth binding mode. 271 P flag: Power Saving mode: 0x00: Static. 0x01: Dynamic. 0x03: Do 272 not support power saving mode. 274 T bit: Whether to support short GI in 20MHz bandwidth mode. 0x00: Do 275 not support short GI. 0x01: Support short GI. 277 F bit: ShortGi40: Whether to support short GI in 40MHz bandwidth 278 mode. 0x00: Do not support short GI. 0x01: Support short GI. 280 H bit: Whether Block Ack supports delay mode. 0x00: Do not support 281 delay mode. 0x01: Support delay mode. 283 M bit: The maximal A-MSDU length. 0x00: 3839 bytes. 0x01: 7935 284 bytes. 286 Max RxFactor: The maximal receiving A-MPDU factor. 288 Min StaSpacing: Minimum MPDU Start Spacing. 290 HiSuppDataRate: Maximal transmission speed (Mbps). 292 AMPDUBufSize: A-MPDU buffer size (Byte). 294 HtcSupp: Whether to place HT headers on the packets forwarded from 295 this station. 297 MCS Set: The MCS bitmap that the station supports. 299 4. Power and Channel Autoconfiguration 301 Power and channel autoconfiguration could avoid potential radio 302 interference and improve the WLAN performance. In general, the auto- 303 configuration of radio power and channel could occur at two stages: 304 when the WTP power on or during the WTP running time. 306 4.1. Channel Autoconfiguration When WTP Power On 308 Power and channel auto reconfiguration avoids potential radio 309 interference and improves the WLAN performance. In general, the 310 auto- configuration of radio power and channel can occur at two 311 stages: when the WTP powers on or while the WTP is in running state. 312 When the WTP is powered-on, it needs to configure a proper channel. 313 IEEE 802.11 Direct Sequence Control elements or IEEE 802.11 OFDM 314 Control element defined in RFC5416 SHOULD be carried in the Configure 315 Status Response message to offer WTP a channel at this stage. If the 316 channel field of those information element is set to 0, the WTP will 317 need to determine its channel by itself, otherwise the WTP SHOULD be 318 configured according to the provided information element. 320 When the WTP determines its own channel configuration, it should 321 first scan the channel information, then determine which channel it 322 will work on and form a channel quality scan report. As shown in 323 Figure 3, the AC can control the scanning process by sending the IEEE 324 802.11 Scan Parameters message element defined in Section 5.1 to the 325 WTP in a Configure Status Response message or in a WTP Configure 326 Update Request message. The WTP will send the channel quality report 327 to the AC using the WTP Event Request message. 329 AC will determine whether to change the channel configuration based 330 on the received channel quality report. The AC MAY use a IEEE 802.11 331 Direct Sequence Control or IEEE 802.11 OFDM Control message element 332 carried by the configure Update Request message to configure a new 333 channel for the WTP. 335 4.2. Power Configuration When WTP Power On 337 The IEEE 802.11 Tx Power message element defined in section 6.18 of 338 [RFC5416] is used by the AC to control the transmission power of the 339 WTP. The 802.11 Tx Power information element is carried in the 340 Configure Status Response message or in the Configure Update Request 341 message. 343 4.3. Channel/Power Auto Adjustment 345 The Channel Scan Procedure is illustrated by the figure 4. 347 WTP Configure Status Req AC 348 -------------------------------------------------------> 349 Configure Status Res(Scan Parameter Message Element, Channel Bind Message Element) 350 <------------------------------------------------------ 351 or 353 WTP AC 354 Configure Update Req(Scan Parameter Message Element, Channel Bind Message Element ) 355 <----------------------------------------------------- 356 Configure Update Res 357 -----------------------------------------------------> 359 Figure 4: Channel Scan Procedure 361 The WTP has two work modes: normal mode and scan only mode. In 362 normal mode, the WTP can provide service for station access and scan 363 channels at the same time. Whether the WTP will scan a given set of 364 channels is determined by the Max Cycles field in the IEEE 802.11 365 Channel Bind message element defined in Section 5.2. When this field 366 is set to 0, the WTP will not scan the channel. If this field is set 367 to 255, the WTP will scan the channel continuously. The type of the 368 scan is determined by the Scan Type field. With the passive scan 369 type, the WTP monitors the air interface, using the received beacon 370 frames to determine the nearby WTPs. With the active scan type, the 371 WTP will send a probe message and receive probe response messages. 373 In the normal scan mode, the WTP behaviour is controlled by three 374 parameters: PrimeChlSrvTime, OnChannelScanTIme, and 375 OffChannelScnTIme. These are provided by the IEEE 802.11 Scan 376 Parameters message element defined in Section 5.1. The WTP will 377 provide access service for stations for the duration given by 378 PrimeChlSrvTime. It then scans the working channel for the duration 379 given by OnChannelScnTime. It returns to servicing station access 380 requests on the working channel for another period of length 381 PrimeChlSrvTime, then moves to a different channel and scans it for 382 duration OffChannelScnTIme. It repeats this cycle, scanning a new 383 non-working channel each time, until all the channels have been 384 scanned. 386 When the WTP works in scan only mode, it does not distinguish between 387 the working channel and scan channel. Every channel's scan duration 388 will be OffChannelScnTime and PrimeChlSrvTime and OnChannelScanTime 389 MUST be set to 0. 391 As shown in Figure 4, the AC can control the scan behaviour at the 392 WTP by including the IEEE 802.11 Scan Parameters and IEEE 802.11 393 Channel Bind message elements in a Configure Status Response or WTP 394 Configure Update Request message. 396 Scan Report. After completing its scan, the WTP MAY send the scan 397 report to the AC using a WTP Event Request message. The scan report 398 information is carried in the IEEE 802.11 Channel Scan Report message 399 element (Section 5.3) and an instance of the IEEE 802.11 Information 400 Element message element carrying a copy of theIEEE 802.11 Neighbor 401 WTP Report information element (Section 5.4). 403 4.3.1. IEEE 802.11 Scan Parameters Message Element 405 The format of the IEEE 802.11 Scan Parameters Message Element is as 406 shown in Figure 5: 408 0 1 2 3 409 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 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | Radio ID |M|S|L|D| | Report Time | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | PrimeChlSrvTime | On Channel ScanTime | 414 +-------------------------------+-------------------------------+ 415 | Off Channel ScanTime | 416 +-------------------------------+ 418 Figure 5: IEEE 802.11 Scan Parameters Message Element 420 Type: TBD3 for IEEE 802.11 Scan Parameters Message Element. 422 Length: 10. 424 Radio ID: An 8-bit value representing the radio, whose value is 425 between one (1) and 31. 427 M bit: Work mode of the WTP. 0:normal mode. 1: monitor only mode, no 428 service is provided in this mode. 430 S bit: Scan Type: 0: active scan; 1: passive scan. 432 L bit: L=1: Open Load Balance Scan. L=0: Disable Load Balance Scan. 434 D bit: D=1: Open Rogue WTP detection scan. D=0: Disable Rouge WTP 435 detection scan. 437 Report Time: Channel quality report time (unit: second). 439 PrimeChlSrvTime: Service time (unit: millisecond) on the working scan 440 channel. This segment is invalid(set to 0) when WTP oper mode is set 441 to 1. The maximum value of this segment is 10000, the minimum value 442 of this segment is 5000, the default value is 5000. 444 On Channel ScanTime: The scan time (unit: millisecond) of the working 445 channel. When the WTP oper mode is set to 2, this segment is 446 invalid(set to 0). The maximum value of this segment is 120, the 447 minimum value of this segment is 60, the default value is 60. 449 Off Channel ScanTime: The scan time (unit: millisecond) of the 450 working channel. When the WTP operating mode is set to 2, this 451 segment MUST be set to 0. The maximum value of this segment is 120, 452 the minimum value of this segment is 60, the default value is 60. 454 4.3.2. IEEE 802.11 Channel Bind Message Element 456 The format of the IEEE 802.11 Channel Bind Message Element is as 457 follows: 459 0 1 2 3 460 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 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | Flag | Max Cycles |Channel Count |ScanChannelSet.| 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 Figure 6: IEEE 802.11 Channel Bind Message Element 467 Type: TBD4 for IEEE 802.11 Channel Bind Message Element. 469 Length: 4. 471 Radio ID: An 8-bit value representing the radio, whose value is 472 between one (1) and 31. 474 Flag: bitmap, reserved. 476 Max Cycles: Number of times the scanning cycle is repeated for the 477 set of channels identified by this message element. 255 means 478 continuous scan. 480 Channel Count: The number of channels will be scanned. 482 Scan Channel Set: identifies the members of the set of channels to 483 which this message element instance applies. The format for each 484 channel is as follows: 486 0 1 2 3 487 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 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 | Channel ID | Flag | 490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 492 Figure 7: Channel Information Format 494 Channel ID: the channel ID of the channel which will be scanned. 496 Flag: Bitmap, reserved for future use. 498 4.3.3. IEEE 802.11 Channel Scan Report 500 There are two types of scan report: Channel Scan Report and Neighbor 501 STA Report. Channel Scan Report is used to channel autoconfiguration 502 while Neighbor WTP Report is used to power autoconfiguration. The 503 WTP send the scan report to the AC through WTP Event Request message. 504 The information element that used to carry the scan report is Channel 505 Scan Report Message Element and Neighbor WTP Report Message Element. 507 The format of the IEEE 802.11 Channel Scan Report message element is 508 in Figure 8. 510 0 1 2 3 511 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 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Radio ID | Report Count | Channel Scan Report | 514 +---------------------------------------------------------------+ 516 Figure 8: IEEE 802.11 Channel Scan Report Message Element 518 Type: TBD5 for IEEE 802.11 Channel Scan Report message element. 520 Length: >=29. 522 Radio ID: An 8-bit value representing the radio, whose value is 523 between one (1) and 31. 525 Report Count: The number of channels for which a report is provided. 527 Channel Scan Report: The format of each Channel Scan Report is shown 528 in Figure 9. 530 0 1 2 3 531 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 532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 533 | Channel Number | Radar Statistics | Mean | 534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 | Time | Mean RSSI | Screen Packet Count | 536 +---------------------------------------------------------------+ 537 | NeighborCount| Mean Noise | Interference | WTP Tx Occp | 538 +---------------------------------------------------------------+ 539 | WTP Rx Occp | Unknown Occp | CRC Err Cnt | Decrypt Err Cnt | 540 +---------------------------------------------------------------+ 541 |Phy Err Cnt | Retrans Cnt | 542 +-----------------------------+ 544 Figure 9: Channel Scan Report 546 Channel Number: The channel number. 548 Radar Statistics: Whether detect radar signal in this channel. 0x00: 549 detect radar signal. 0x01: no radar signal is detected. 551 Mean Time: Channel measurement duration (ms). 553 Mean RSSI: The average signal strength of the scanned channel (dbm). 555 Screen Packet Count: Received packet number. 557 Neighbor Count: The neighbor number of this channel. 559 Mean Noise: the average noise on this channel. 561 Interference: The interference of the channel, including STA 562 interference and WTP interference. 564 WTP Tx Occp: (The WTP sending duration time/Monitor time)*255. 565 The WTP sending duration time is the total sending time of 566 the WTP during the period of channel scan. 568 WTP Rx Occp: (The WTP receiving duration time/Monitor time)*255. 569 THe WTP receiving duration time is the total receiving time of 570 the WTP during the period of channel scan. 572 Unknown Occp: (All other packet transmission time duration/Monitor 573 time)*255. 575 CRC Err Cnt: CRC err packet number. 577 Decrypt Err Cnt: Decryption err packet number. 579 Phy Err Cnt: Physical err packet number. 581 Retrans Cnt: Retransmission packet number. 583 4.3.4. IEEE 802.11 WTP Neighbor Report 585 0 1 2 3 586 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 587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 588 | Element ID | Length | 589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 | Radio ID | Reserved | Number of Neighbor Report | 591 +---------------------------------------------------------------+ 592 | Neighbor Infor... | 593 +---------------------------------------------------------------+ 595 Figure 10: WTP Neighbor Report TLV 597 The definition of Neighbor info is as follows: 599 0 1 2 3 600 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 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 602 | BSSID | 603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 604 | BSSID | Channel Number | 605 +---------------------------------------------------------------+ 606 | 2nd Offset | Mean RSSI | Sta Intf | AP Intf | 607 +---------------------------------------------------------------+ 609 Figure 11: Neighbor info 611 BSSID: The BSSID of this neighbor WTP. 613 Channel Number: The channel number of this WTP neighbor. 615 2nd channel offset: The auxiliary channel offset of this WTP. 617 Mean RSSI: The average signal strength of this WTP (dbm). 619 Sta Intf: (The station air interface occupation time/Monitor 620 time)*255. The station air interface occupation time is the 621 air interface occupation time caused by the stations which are connected 622 to this WTP. 624 AP Intf: (The WTP air interface occupation time/Monitor time)*255. 625 The WTP air interface occupation time is the air interface occupation 626 time caused by the WTP. 628 5. Security Considerations 630 This document is based on RFC5415/RFC5416 and adds no new security 631 considerations. 633 6. IANA Considerations 635 The extension defined in this document need to extend CAPWAP IEEE 636 802.11 binding message element which is defined in section 6 of 637 [RFC5416]. The following IEEE 802.11 specific message element type 638 need to be defined by IANA. 640 TBD1: 802.11n Radio Configuration Message Element type value 641 described in section 4.1.2. 643 TBD2: 802.11n Station Message Element type value described in section 644 4.1.3. 646 TBD3: 802.11 Scan Parameter Message Element type value described in 647 section 5.3.1. 649 TBD4: 802.11 Channel Bind Message Element type value described in 650 section 5.3.2. 652 TBD5: Channel Scan Report Message Element type value described in 653 section 5.3.3. 655 7. Contributors 657 This draft is a joint effort from the following contributors: 659 Gang Chen: China Mobile chengang@chinamobile.com 661 Naibao Zhou: China Mobile zhounaibao@chinamobile.com 663 Chunju Shao: China Mobile shaochunju@chinamobile.com 665 Hao Wang: Huawei3Come hwang@h3c.com 667 Yakun Liu: AUTELAN liuyk@autelan.com 669 Xiaobo Zhang: GBCOM 670 Xiaolong Yu: Ruijie Networks 672 Song zhao: ZhiDaKang Communications 674 Yiwen Mo: ZhongTai Networks 676 Dorothy Stanley: dstanley1389@gmail.com 678 Tom Taylor: tom.taylor.stds@gmail.com 680 8. Acknowledgements 682 The authors would like to thanks Ronald Bonica,Romascanu Dan, Benoit 683 Claise, Melinda Shore and Margaret Wasserman for their useful 684 suggestions. The authors also thanks Dorothy Stanley and Tom Taylor 685 for their review and useful comments. 687 9. Normative References 689 [IEEE-802.11.2009] 690 "IEEE Standard for Information technology - 691 Telecommunications and information exchange between 692 systems Local and metropolitan area networks - Specific 693 requirements Part 11: Wireless LAN Medium Access Control 694 (MAC) and Physical Layer (PHY) Specifications", 2009. 696 [IEEE-802.11.2012] 697 "IEEE Standard for Information technology - 698 Telecommunications and information exchange between 699 systems Local and metropolitan area networks - Specific 700 requirements Part 11: Wireless LAN Medium Access Control 701 (MAC) and Physical Layer (PHY) Specifications", March 702 2012. 704 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 705 Requirement Levels", BCP 14, RFC 2119, March 1997. 707 [RFC4564] Govindan, S., Cheng, H., Yao, ZH., Zhou, WH., and L. Yang, 708 "Objectives for Control and Provisioning of Wireless 709 Access Points (CAPWAP)", RFC 4564, July 2006. 711 [RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And 712 Provisioning of Wireless Access Points (CAPWAP) Protocol 713 Specification", RFC 5415, March 2009. 715 [RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and 716 Provisioning of Wireless Access Points (CAPWAP) Protocol 717 Binding for IEEE 802.11", RFC 5416, March 2009. 719 Authors' Addresses 721 Yifan Chen 722 China Mobile 723 No.32 Xuanwumen West Street 724 Beijing 100053 725 China 727 Email: chenyifan@chinamobile.com 729 Dapeng Liu 730 China Mobile 731 No.32 Xuanwumen West Street 732 Beijing 100053 733 China 735 Email: liudapeng@chinamobile.com 737 Hui Deng 738 China Mobile 739 No.32 Xuanwumen West Street 740 Beijing 100053 741 China 743 Email: denghui@chinamobile.com 745 Lei Zhu 746 Huawei 747 No. 156, Shi-Chuang-Ke-Ji-Shi-Fan-Yuan Beiqing Road, Haidian District 748 Beijing 100095 749 China 751 Email: lei.zhu@huawei.com