idnits 2.17.1 draft-ietf-capwap-802dot11-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (August 13, 2009) is 5363 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) == Outdated reference: A later version (-09) exists of draft-ietf-capwap-base-mib-05 ** Downref: Normative reference to an Informational draft: draft-ietf-capwap-base-mib (ref. 'I-D.ietf-capwap-base-mib') -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE.802-11.2007' -- Obsolete informational reference (is this intentional?): RFC 4347 (Obsoleted by RFC 6347) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Y. Shi, Ed. 3 Internet-Draft Hangzhou H3C Tech. Co., Ltd. 4 Intended status: Standards Track D. Perkins, Ed. 5 Expires: February 14, 2010 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 August 13, 2009 12 CAPWAP Protocol Binding MIB for IEEE 802.11 13 draft-ietf-capwap-802dot11-mib-05 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on February 14, 2010. 38 Copyright Notice 40 Copyright (c) 2009 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents in effect on the date of 45 publication of this document (http://trustee.ietf.org/license-info). 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. 49 Abstract 51 This memo defines a portion of the Management Information Base (MIB) 52 for use with network management protocols. In particular, it 53 describes managed objects for modeling the Control And Provisioning 54 of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless 55 binding. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. The Internet-Standard Management Framework . . . . . . . . . . 3 61 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 5.1. WLAN Profile . . . . . . . . . . . . . . . . . . . . . . . 5 65 5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5 66 5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6 67 6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6 68 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 69 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7 70 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7 71 7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7 72 7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 7 73 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8 74 8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8 75 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 76 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21 77 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 78 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 22 79 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 22 80 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22 81 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 82 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 83 14.1. Normative References . . . . . . . . . . . . . . . . . . . 22 84 14.2. Informative References . . . . . . . . . . . . . . . . . . 23 85 Appendix A. Appendix A. Changes between -05 and -04 . . . . . . . 24 87 1. Introduction 89 The CAPWAP Protocol [RFC5415] defines a standard, interoperable 90 protocol, which enables an Access Controller (AC) to manage a 91 collection of Wireless Termination Points(WTPs). CAPWAP supports the 92 use of various wireless technologies by the WTPs, with one specified 93 in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416]. 95 This document defines a MIB module that can be used to manage CAPWAP 96 implementations for IEEE 802.11 wireless binding. This MIB module 97 covers both configuration for WLAN and a way to reuse the IEEE 802.11 98 MIB module [IEEE.802-11.2007]. 100 2. The Internet-Standard Management Framework 102 For a detailed overview of the documents that describe the current 103 Internet-Standard Management Framework, please refer to section 7 of 104 RFC 3410 [RFC3410]. 106 Managed objects are accessed via a virtual information store, termed 107 the Management Information Base or MIB. MIB objects are generally 108 accessed through the Simple Network Management Protocol (SNMP). 109 Objects in the MIB are defined using the mechanisms defined in the 110 Structure of Management Information (SMI). This memo specifies a MIB 111 module that is compliant to the SMIv2, which is described in STD 58, 112 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 113 [RFC2580]. 115 3. Terminology 117 This document uses terminology from the CAPWAP Protocol specification 118 [RFC5415], the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] and 119 CAPWAP Protocol Base MIB [I-D.ietf-capwap-base-mib]. 121 Access Controller (AC): The network entity that provides WTP access 122 to the network infrastructure in the data plane, control plane, 123 management plane, or a combination therein. 125 Wireless Termination Point (WTP): The physical or network entity that 126 contains an RF antenna and wireless PHY to transmit and receive 127 station traffic for wireless access networks. 129 Control And Provisioning of Wireless Access Points (CAPWAP): It is a 130 generic protocol defining AC and WTP control and data plane 131 communication via a CAPWAP protocol transport mechanism. CAPWAP 132 control messages, and optionally CAPWAP data messages, are secured 133 using Datagram Transport Layer Security (DTLS) [RFC4347]. 135 CAPWAP Control Channel: A bi-directional flow defined by the AC IP 136 Address, WTP IP Address, AC control port, WTP control port and the 137 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control 138 packets are sent and received. 140 CAPWAP Data Channel: A bi-directional flow defined by the AC IP 141 Address, WTP IP Address, AC data port, WTP data port, and the 142 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data 143 packets are sent and received. 145 Station (STA): A device that contains an interface to a wireless 146 medium (WM). 148 Split and Local MAC: The CAPWAP protocol supports two modes of 149 operation: Split and Local MAC. In Split MAC mode all L2 wireless 150 data and management frames are encapsulated via the CAPWAP protocol 151 and exchanged between the AC and the WTPs. The Local MAC mode of 152 operation allows the data frames to be either locally bridged, or 153 tunneled as 802.3 frames. 155 Wireless Binding: The CAPWAP protocol is independent of a specific 156 WTP radio technology, as well its associated wireless link layer 157 protocol. Elements of the CAPWAP protocol are designed to 158 accommodate the specific needs of each wireless technology in a 159 standard way. Implementation of the CAPWAP protocol for a particular 160 wireless technology MUST define a binding protocol for it, e.g., the 161 binding for IEEE 802.11, provided in [RFC5416]. 163 WLAN: A WLAN refers to a logical component instantiated on a WTP 164 device. A single physical WTP MAY operate a number of WLANs. Each 165 Basic Service Set Identifier (BSSID) and its constituent wireless 166 terminal radios are denoted as a distinct WLAN on a physical WTP. To 167 support a physical WTP with multiple WLANs is an important feature 168 for CAPWAP protocol's 802.11 binding, and it is also for MIB module 169 design. 171 Wireless Binding MIB Module: Other Standards Developing Organizations 172 (SDOs), such as IEEE already defined MIB module for a specific 173 wireless technology, e.g., the IEEE 802.11 MIB module 174 [IEEE.802-11.2007]. Such MIB modules are called wireless binding MIB 175 modules. 177 CAPWAP Protocol Wireless Binding MIB Module: It is a MIB module 178 corresponding to the CAPWAP Protocol Binding for a Wireless binding. 179 Sometimes, not all the technology-specific message elements in a 180 CAPWAP binding protocol have MIB objects defined by other SDOs. For 181 example, the protocol of [RFC5416] defines WLAN conception. Also, 182 Local or Split MAC modes could be specified for a WLAN. The MAC mode 183 for a WLAN is not in the scope of IEEE 802.11 [IEEE.802-11.2007]. In 184 such cases, in addition to the existing wireless binding MIB modules 185 defined by other SDOs, a CAPWAP protocol wireless binding MIB module 186 is required to be defined for a wireless binding. 188 4. Conventions 190 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 191 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 192 document are to be interpreted as described in RFC 2119 [RFC2119]. 194 5. Overview 196 5.1. WLAN Profile 198 A WLAN profile stores configuration parameters such as MAC type and 199 tunnel mode for a WLAN. Each WLAN profile is identified by a profile 200 identifier. The operator needs to create WLAN profiles before WTPs 201 connect to the AC. To provide WLAN service, the operator SHOULD bind 202 WLAN profiles to a WTP Virtual Radio Interface which corresponding to 203 a PHY radio. During the binding operation, the AC MUST select an 204 unused WLAN ID between one(1) and 16 [RFC5416]. For example, to bind 205 one more WLAN profile to a radio that has been bound with a WLAN 206 profile, the AC SHOULD allocate WLAN ID 2 to the radio. Although the 207 maximum value of WLAN ID is 16, the operator could configure more 208 than 16 WLAN Profiles on the AC. 210 5.2. Requirements and Constraints 212 The IEEE 802.11 MIB module [IEEE.802-11.2007] already defines MIB 213 objects for most IEEE 802.11 Message Elements in the the CAPWAP 214 Protocol Binding for IEEE 802.11 [RFC5416]. As a CAPWAP Protocol 215 802.11 binding MIB module, the CAPWAP-DOT11-MIB module MUST be able 216 to reuse such MIB objects in the IEEE 802.11 MIB module and support 217 functions such as MAC mode for WLAN in the [RFC5416] which are not in 218 the scope of IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST 219 support such functions. 221 In summary, the CAPWAP-DOT11-MIB module needs to support: 223 - Reuse of wireless binding MIB modules in the IEEE 802.11 standard; 225 - Centralized manage and configuration of WLAN profiles on the AC; 227 - Configuration of a MAC type and tunnel mode for a specific WLAN 228 profile. 230 5.3. Mechanism of Reusing Wireless Binding MIB Module 232 In the IEEE 802.11 MIB module, the MIB tables such as 233 Dot11AuthenticationAlgorithmsTable are able to support WLAN 234 configuration (such as authentication algorithm), and these tables 235 use the ifIndex as the index which works well in the autonomous WLAN 236 architecture. 238 Reuse of such wireless binding MIB modules is very important to 239 centralized WLAN architectures. The key point is to abstract a WLAN 240 profile as a WLAN Profile Interface on the AC, which could be 241 identified by an ifIndex. The MIB objects in the IEEE 802.11 MIB 242 module which are associated with this interface can be used to 243 configure WLAN parameters for the WLAN, such as authentication 244 algorithm. With the ifIndex of a WLAN Profile Interface, the AC is 245 able to reuse the IEEE 802.11 MIB module. 247 In the CAPWAP-BASE-MIB module, each PHY radio is identified by a WTP 248 ID and a radio ID, and has a corresponding WTP Virtual Radio 249 Interface on the AC. The IEEE 802.11 MIB module associated with this 250 interface can be used to configure IEEE 802.11 wireless binding 251 parameters for the radio such as RTS Threshold. A WLAN BSS 252 Interface, created by binding WLAN to WTP Virtual Radio Interface, is 253 used for data forwarding. 255 6. Structure of MIB Module 257 The MIB objects are derived from the CAPWAP protocol binding for IEEE 258 802.11 document [RFC5416]. 260 1) capwapDot11WlanTable 262 The table allows the operator to display and configure WLAN profiles, 263 such as specifying the MAC type and tunnel mode for a WLAN. Also, it 264 helps the AC to configure a WLAN through the IEEE 802.11 MIB module. 266 2) capwapDot11WlanBindTable 268 The table provides a way to bind WLAN profiles to a WTP Virtual Radio 269 Interface which has a PHY radio corresponding to it. A binding 270 operation dynamically creates a WLAN BSS Interface, which is used for 271 data forwarding. 273 7. Relationship to Other MIB Modules 274 7.1. Relationship to SNMPv2-MIB Module 276 The CAPWAP-DOT11-MIB module does not duplicate the objects of the 277 'system' group in the SNMPv2-MIB [RFC3418] that is defined as being 278 mandatory for all systems, and the objects apply to the entity as a 279 whole. The 'system' group provides identification of the management 280 entity and certain other system-wide data. 282 7.2. Relationship to IF-MIB Module 284 The Interfaces Group [RFC2863] defines generic managed objects for 285 managing interfaces. This memo contains the media-specific 286 extensions to the Interfaces Group for managing WLAN that are modeled 287 as interfaces. 289 Each WLAN profile corresponds to a WLAN Profile Interface on the AC. 290 The interface MUST be modeled as an ifEntry, and ifEntry objects such 291 as ifIndex, ifDescr, ifName, ifAlias are to be used as per [RFC2863]. 292 The WLAN Profile Interface provides a way to configure IEEE 802.11 293 parameters for a specific WLAN, and reuse the IEEE 802.11 MIB module. 295 Also, the AC MUST have a mechanism that preserves the value of the 296 WLAN Profile Interfaces' ifIndexes in the ifTable at AC reboot. 298 To provide data forwarding service, the AC dynamically creates WLAN 299 BSS Interfaces. A WLAN BSS Interface MUST be modeled as an ifEntry, 300 and ifEntry objects such as ifIndex, ifDescr, ifName, ifAlias are to 301 be used as per [RFC2863]. The interface enables a single physical 302 WTP to support multiple WLANs. 304 Also, the AC MUST have a mechanism that preserves the value of the 305 WLAN BSS Interfaces' ifIndexes in the ifTable at AC reboot. 307 7.3. Relationship to CAPWAP-BASE-MIB Module 309 The CAPWAP-BASE-MIB module provides a way to manage and control WTP 310 and radio objects. Especially, it provides the WTP Virtual Radio 311 Interface mechanism to enable the AC to reuse the IEEE 802.11 MIB 312 module. With this mechanism, an operator could configure an IEEE 313 802.11 radio's parameters and view the radio's traffic statistics on 314 the AC. Based on the CAPWAP-BASE-MIB module, the CAPWAP-DOT11-MIB 315 module provides more WLAN information. 317 7.4. Relationship to MIB Module in IEEE 802.11 Standard 319 With the ifIndex of WLAN Profile Interface and WLAN BSS Interface, 320 the MIB module is able to reuse the IEEE 802.11 MIB module 321 [IEEE.802-11.2007]. The CAPWAP-DOT11-MIB module does not duplicate 322 those objects in the IEEE 802.11 MIB module. 324 The CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] involves some 325 of the MIB objects defined in IEEE 802.11 standard. Although CAPWAP- 326 DOT11-MIB module uses it [RFC5416] as a reference, it could reuse all 327 the MIB objects in the IEEE 802.11 standard , and is not limited by 328 the scope of CAPWAP Protocol Binding for IEEE 802.11. 330 7.5. MIB Modules Required for IMPORTS 332 The following MIB modules are required for IMPORTS: SNMPv2-SMI 333 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 334 [RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib]. 336 8. Example of CAPWAP-DOT11-MIB Module Usage 338 1) Create a WTP profile 340 Suppose the WTP's base MAC address is '00:01:01:01:01:00'. Creates a 341 WTP profile for it through the CapwapBaseWtpProfileTable 342 [I-D.ietf-capwap-base-mib] as follows: 344 In CapwapBaseWtpProfileTable 345 { 346 capwapBaseWtpProfileId = 1, 347 capwapBaseWtpProfileName = 'WTP Profile 123456', 348 capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00', 349 capwapBaseWtpProfileWTPModelNumber = 'WTP123', 350 capwapBaseWtpProfileWtpName = 'WTP 123456', 351 capwapBaseWtpProfileWtpLocation = 'office', 352 capwapBaseWtpProfileWtpStaticIpEnable = true(1), 353 capwapBaseWtpProfileWtpStaticIpType = ipv4(1), 354 capwapBaseWtpProfileWtpStaticIp = '192.168.0.100', 355 capwapBaseWtpProfileWtpNetmask = '255.255.255.0', 356 capwapBaseWtpProfileWtpGateway = '192.168.0.1', 357 capwapBaseWtpProfileWtpFallbackEnable = true(1), 358 capwapBaseWtpProfileWtpEchoInterval = 30, 359 capwapBaseWtpProfileWtpIdleTimeout = 300, 360 capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, 361 capwapBaseWtpProfileWtpReportInterval = 120, 362 capwapBaseWtpProfileWtpSilentInterval = 30, 363 capwapBaseWtpProfileWtpStatisticsTimer = 120, 364 capwapBaseWtpProfileWtpWaitDTLSTimer = 60, 365 capwapBaseWtpProfileWtpEcnSupport = limited(0) 366 } 368 Suppose the WTP with model number 'WTP123' has one PHY radio and this 369 PHY radio is identified by ID 1. The creation of this WTP profile 370 triggers the AC to automatically create a WTP Virtual Radio Interface 371 and add a new row object to the CapwapBaseWirelessBindingTable 372 without manual intervention. Suppose the ifIndex of the WTP Virtual 373 Radio Interface is 10. The following information is stored in the 374 CapwapBaseWirelessBindingTable. 376 In CapwapBaseWirelessBindingTable 377 { 378 capwapBaseWtpProfileId = 1, 379 capwapBaseWirelessBindingRadioId = 1, 380 capwapBaseWirelessBindingVirtualRadioIfIndex = 10, 381 capwapBaseWirelessBindingType = dot11(2) 382 } 384 The WTP Virtual Radio Interfaces on the AC correspond to the PHY 385 radios on the WTP. The WTP Virtual Radio Interface is modeled by 386 ifTable [RFC2863]. 388 In ifTable 389 { 390 ifIndex = 10, 391 ifDescr = 'WTP Virtual Radio Interface', 392 ifType = xxx, 393 RFC Editor - please replace xxx with the value 394 allocated by IANA for IANAifType of WTP Virtual Radio Interface 395 ifMtu = 0, 396 ifSpeed = 0, 397 ifPhysAddress = '00:00:00:00:00:00', 398 ifAdminStatus = true(1), 399 ifOperStatus = false(0), 400 ifLastChange = 0, 401 ifInOctets = 0, 402 ifInUcastPkts = 0, 403 ifInDiscards = 0, 404 ifInErrors = 0, 405 ifInUnknownProtos = 0, 406 ifOutOctets = 0, 407 ifOutUcastPkts = 0, 408 ifOutDiscards = 0, 409 ifOutErrors = 0 410 } 412 2) Query the ifIndexes of WTP Virtual Radio Interfaces 414 Before configuring PHY radios, the operator needs to get the 415 ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY 416 radios. 418 As the CapwapBaseWirelessBindingTable already stores the mappings 419 between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio 420 Interfaces, the operator can get the ifIndex information by querying 421 this table. Such a query operation SHOULD run from radio ID 1 to 422 radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex 423 value (0) is returned. 425 This example uses capwapBaseWtpProfileId = 1 and 426 capwapBaseWirelessBindingRadioId = 1 as inputs to query the 427 CapwapBaseWirelessBindingTable, and gets 428 capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses 429 capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, 430 and gets a invalid ifIndex value (0), so the the query operation 431 ends. This method gets not only the ifIndexes of WTP Virtual Radio 432 Interfaces, but also the numbers of PHY radios. Besides checking 433 whether the ifIndex value is valid, the operator SHOULD check whether 434 the capwapBaseWirelessBindingType is the desired binding type. 436 3) Configure IEEE 802.11 parameters for a WTP Virtual Radio Interface 438 This configuration is made on the AC through the IEEE 802.11 MIB 439 module. 441 The following shows an example of configuring parameters for a WTP 442 Virtual Radio Interface with ifIndex 10 through the 443 Dot11OperationTable [IEEE.802-11.2007]. 445 In Dot11OperationTable 446 { 447 ifIndex = 10, 448 dot11MACAddress = '00:00:00:00:00:00', 449 dot11RTSThreshold = 2347, 450 dot11ShortRetryLimit = 7, 451 dot11LongRetryLimit = 4, 452 dot11FragmentationThreshold = 256, 453 dot11MaxTransmitMSDULifetime = 512, 454 dot11MaxReceiveLifetime = 512, 455 dot11ManufacturerID = 'capwap', 456 dot11ProductID = 'capwap' 457 dot11CAPLimit = 2, 458 dot11HCCWmin = 0, 459 dot11HCCWmax = 0, 460 dot11HCCAIFSN = 1, 461 dot11ADDBAResponseTimeout = 1, 462 dot11ADDTSResponseTimeout = 1, 463 dot11ChannelUtilizationBeaconInterval = 50, 464 dot11ScheduleTimeout = 10, 465 dot11DLSResponseTimeout = 10, 466 dot11QAPMissingAckRetryLimit = 1, 467 dot11EDCAAveragingPeriod = 5 468 } 470 4) Configure a WLAN Profile 472 WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB 473 Module, and IEEE 802.11 MIB module. 475 The first step is to create a WLAN Profile Interface through the 476 CAPWAP-DOT11-MIB module on the AC. 478 For example, when you configure a WLAN profile which is identified by 479 capwapDot11WlanProfileId 1, the CapwapDot11WlanTable creates the 480 following row object for it. 482 In CapwapDot11WlanTable 483 { 484 capwapDot11WlanProfileId = 1, 485 capwapDot11WlanProfileIfIndex = 20, 486 capwapDot11WlanMacType = splitMAC(2), 487 capwapDot11WlanTunnelMode = dot3Tunnel(2), 488 capwapDot11WlanRowStatus = createAndGo(4) 489 } 491 The creation of a row object triggers the AC to automatically create 492 a WLAN Profile Interface and it is identified by ifIndex 20 without 493 manual intervention. 495 A WLAN Profile Interface MUST be modeled as an ifEntry on the AC 496 which provides appropriate interface information. The 497 CapwapDot11WlanTable stores the mappings between 498 capwapDot11WlanProfileIds and the ifIndexes of WLAN Profile 499 Interfaces. 501 In ifTable 502 { 503 ifIndex = 20, 504 ifDescr = 'WLAN Profile Interface', 505 ifType = xxx, 506 RFC Editor - please replace xxx with the value 507 allocated by IANA for IANAifType of 'WLAN Profile Interface' 508 ifMtu = 0, 509 ifSpeed = 0, 510 ifPhysAddress = '00:00:00:00:00:00', 511 ifAdminStatus = true(1), 512 ifOperStatus = true(1), 513 ifLastChange = 0, 514 ifInOctets = 0, 515 ifInUcastPkts = 0, 516 ifInDiscards = 0, 517 ifInErrors = 0, 518 ifInUnknownProtos = 0, 519 ifOutOctets = 0, 520 ifOutUcastPkts = 0, 521 ifOutDiscards = 0, 522 ifOutErrors = 0 523 } 525 The second step is to configure WLAN parameters for the WLAN Profile 526 Interface through the IEEE 802.11 MIB module on the AC. 528 The following example configures an authentication algorithm for a 529 WLAN. 531 In Dot11AuthenticationAlgorithmsTable 532 { 533 ifIndex = 20, 534 dot11AuthenticationAlgorithmsIndex = 1, 535 dot11AuthenticationAlgorithm = Shared Key(2), 536 dot11AuthenticationAlgorithmsEnable = true(1) 537 } 539 Here ifIndex 20 identifies the WLAN Profile Interface and the index 540 of the configured authentication algorithm is 1. 542 5) Bind WLAN Profiles to a WTP radio 544 On the AC, the CapwapDot11WlanBindTable in the CAPWAP-DOT11-MIB 545 stores the bindings between WLAN profiles(identified by 546 capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces 547 (identified by the ifIndex). 549 For example, after the operator binds a WLAN profile with 550 capwapDot11WlanProfileId 1 to WTP Virtual Radio Interface with 551 ifIndex 10, the CapwapDot11WlanBindTable creates the following row 552 object. 554 In CapwapDot11WlanBindTable 555 { 556 ifIndex = 10, 557 capwapDot11WlanProfileId = 1, 558 capwapDot11WlanBindBssIfIndex = 30, 559 capwapDot11WlanBindRowStatus = createAndGo(4) 560 } 562 If the capwapDot11WlanMacType of the WLAN is splitMAC(2), the 563 creation of the row object in the CapwapDot11WlanBindTable triggers 564 the AC to automatically create a WLAN BSS Interface identified by 565 ifIndex 30 without manual intervention. 567 The WLAN BSS Interface MUST be modeled as an ifEntry on the AC, which 568 provides appropriate interface information. The 569 CapwapDot11WlanBindTable stores the mappings among the ifIndex of a 570 WTP Virtual Radio Interface, WLAN profile ID, WLAN ID and the ifIndex 571 of a WLAN BSS Interface. 573 6) Current configuration status report from the WTP to the AC 575 Before a WTP that has joined the AC gets configuration from the AC, 576 it needs to report its current configuration status by sending a 577 configuration status request message to the AC, which uses the 578 message to update corresponding MIB objects on the AC. For example, 579 for ifIndex 10 (which identifies a WLAN Virtual Radio Interface), its 580 ifOperStatus in the ifTable is updated according to the current radio 581 operational status in the CAPWAP message [RFC5415]. 583 7) Query WTP and radio statistics data 585 After WTPs start to run, the operator could query WTP and radio 586 statistics data through the CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB 587 modules. For example, through the dot11CountersTable 588 [IEEE.802-11.2007], the operator could query counter data of a radio 589 which is identified by the ifIndex of the corresponding WLAN Virtual 590 Radio Interface. 592 8) Query other statistics data 594 The operator could query the configuration of a WLAN through the 595 Dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and the 596 statistic data of a WLAN BSS Interface through the ifTable [RFC2863]; 598 9. Definitions 600 CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN 602 IMPORTS 603 RowStatus, TEXTUAL-CONVENTION 604 FROM SNMPv2-TC 605 OBJECT-GROUP, MODULE-COMPLIANCE 606 FROM SNMPv2-CONF 607 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 608 FROM SNMPv2-SMI 609 ifIndex, InterfaceIndex 610 FROM IF-MIB 611 CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC 612 FROM CAPWAP-BASE-MIB; 614 capwapDot11MIB MODULE-IDENTITY 615 LAST-UPDATED "200908130000Z" -- August 13th, 2009 616 ORGANIZATION "IETF Control And Provisioning of Wireless Access 617 Points (CAPWAP) Working Group 618 http://www.ietf.org/html.charters/capwap-charter.html" 619 CONTACT-INFO 620 "General Discussion: capwap@frascone.com 621 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 623 Yang Shi (editor) 624 Hangzhou H3C Tech. Co., Ltd. 625 Beijing R&D Center of H3C, Digital Technology Plaza, 626 NO.9 Shangdi 9th Street,Haidian District, 627 Beijing 628 China(100085) 629 Phone: +86 010 82775276 630 EMail: young@h3c.com 632 David T. Perkins 633 228 Bayview Dr 634 San Carlos, CA 94070 635 USA 636 Phone: +1 408 394-8702 637 Email: dperkins@snmpinfo.com 638 Chris Elliott 639 Cisco Systems, Inc. 640 7025 Kit Creek Rd., P.O. Box 14987 641 Research Triangle Park 27709 642 USA 643 Phone: +1 919-392-2146 644 Email: chelliot@cisco.com 646 Yong Zhang 647 Fortinet, Inc. 648 1090 Kifer Road 649 Sunnyvale, CA 94086 650 USA 651 Email: yzhang@fortinet.com" 653 DESCRIPTION 654 "Copyright (C) 2009 The Internet Society. This version of 655 the MIB module is part of RFC xxx; see the RFC itself 656 for full legal notices. 658 This MIB module contains managed object definitions for 659 CAPWAP Protocol binding for IEEE 802.11." 660 REVISION "200908130000Z" 661 DESCRIPTION 662 "Initial version, published as RFC xxx" 663 ::= { mib-2 xxx } 665 -- Textual conventions 667 CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION 668 DISPLAY-HINT "d" 669 STATUS current 670 DESCRIPTION 671 "Represents the unique identifier of a WLAN." 672 SYNTAX Unsigned32 (1..16) 674 CapwapDot11WlanIdProfileTC ::= TEXTUAL-CONVENTION 675 DISPLAY-HINT "d" 676 STATUS current 677 DESCRIPTION 678 "Represents the unique identifier of a WLAN profile." 679 SYNTAX Unsigned32 (1..512) 681 -- Top level components of this MIB module 683 -- Tables, Scalars 684 capwapDot11Objects OBJECT IDENTIFIER 685 ::= { capwapDot11MIB 1 } 687 -- Conformance 688 capwapDot11Conformance OBJECT IDENTIFIER 689 ::= { capwapDot11MIB 2 } 691 -- capwapDot11WlanTable Table 693 capwapDot11WlanTable OBJECT-TYPE 694 SYNTAX SEQUENCE OF CapwapDot11WlanEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "A table that allows the operator to display and configure 699 WLAN profiles, such as specifying the MAC type and tunnel mode 700 for a WLAN. Also, it helps the AC to configure a WLAN through 701 the IEEE 802.11 MIB module. 702 Values of all objects in this table are persistent at 703 restart/reboot." 704 ::= { capwapDot11Objects 1 } 706 capwapDot11WlanEntry OBJECT-TYPE 707 SYNTAX CapwapDot11WlanEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "A set of objects that store the settings of a WLAN profile." 712 INDEX { capwapDot11WlanProfileId } 713 ::= { capwapDot11WlanTable 1 } 715 CapwapDot11WlanEntry ::= 716 SEQUENCE { 717 capwapDot11WlanProfileId CapwapDot11WlanIdProfileTC, 718 capwapDot11WlanProfileIfIndex InterfaceIndex, 719 capwapDot11WlanMacType CapwapBaseMacTypeTC, 720 capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC, 721 capwapDot11WlanRowStatus RowStatus 722 } 724 capwapDot11WlanProfileId OBJECT-TYPE 725 SYNTAX CapwapDot11WlanIdProfileTC 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "Represents the identifier of a WLAN profile which has a 730 corresponding capwapDot11WlanProfileIfIndex." 731 ::= { capwapDot11WlanEntry 1 } 733 capwapDot11WlanProfileIfIndex OBJECT-TYPE 734 SYNTAX InterfaceIndex 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "Represents the index value that uniquely identifies a 739 WLAN Profile Interface. The interface identified by a 740 particular value of this index is the same interface as 741 identified by the same value of the ifIndex. 742 The creation of a row object in the capwapDot11WlanTable 743 triggers the AC to automatically create an WLAN Profile 744 Interface identified by an ifIndex without manual 745 intervention. 746 Most MIB tables in the IEEE 802.11 MIB module 747 [IEEE.802-11.2007] use an ifIndex to identify an interface 748 to facilitate the configuration and maintenance, for example, 749 dot11AuthenticationAlgorithmsTable. 750 Using the ifIndex of a WLAN Profile Interface, the Operator 751 could configure a WLAN through the IEEE 802.11 MIB module." 752 ::= { capwapDot11WlanEntry 2 } 754 capwapDot11WlanMacType OBJECT-TYPE 755 SYNTAX CapwapBaseMacTypeTC 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "Represents whether the WTP SHOULD support the WLAN in 760 Local or Split MAC modes." 761 REFERENCE 762 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 763 RFC 5416." 764 ::= { capwapDot11WlanEntry 3 } 766 capwapDot11WlanTunnelMode OBJECT-TYPE 767 SYNTAX CapwapBaseTunnelModeTC 768 MAX-ACCESS read-create 769 STATUS current 770 DESCRIPTION 771 "Represents the frame tunneling mode to be used for IEEE 802.11 772 data frames from all stations associated with the WLAN. 773 Bits are exclusive with each other for a specific WLAN profile, 774 and only one tunnel mode could be configured. 775 If the operator set more than one bit, the value of the 776 Response-PDU's error-status field is set to `wrongValue', 777 and the value of its error-index field is set to the index of 778 the failed variable binding." 779 REFERENCE 780 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 781 RFC 5416." 783 ::= { capwapDot11WlanEntry 4 } 785 capwapDot11WlanRowStatus OBJECT-TYPE 786 SYNTAX RowStatus 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "This variable is used to create, modify, and/or delete a row 791 in this table. 792 When the operator deletes a WLAN profile, the AC SHOULD 793 check whether the WLAN profile is bound with a radio. 794 If yes, the value of the Response-PDU's error-status field 795 is set to `inconsistentValue', and the value of its 796 error-index field is set to the index of the failed variable 797 binding. If not, the row object could be deleted." 798 ::= { capwapDot11WlanEntry 5 } 800 -- End of capwapDot11WlanTable Table 802 -- capwapDot11WlanBindTable Table 804 capwapDot11WlanBindTable OBJECT-TYPE 805 SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "A table that stores bindings between WLAN profiles 810 (identified by capwapDot11WlanProfileId) and 811 WTP Virtual Radio Interfaces. The WTP Virtual Radio Interfaces 812 on the AC correspond to PHY radios on the WTPs. It also stores 813 the mappings between WLAN IDs and WLAN BSS Interfaces. 814 Values of all objects in this table are persistent at 815 restart/reboot." 816 REFERENCE 817 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 818 RFC 5416." 819 ::= { capwapDot11Objects 2 } 821 capwapDot11WlanBindEntry OBJECT-TYPE 822 SYNTAX CapwapDot11WlanBindEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "A set of objects that stores the binding of a WLAN profile 827 to a WTP Virtual Radio Interface. It also stores the mapping 828 between WLAN ID and WLAN BSS Interface. 829 The INDEX object ifIndex is the ifIndex of a WTP Virtual 830 Radio Interface." 831 INDEX { ifIndex, capwapDot11WlanProfileId } 832 ::= { capwapDot11WlanBindTable 1 } 834 CapwapDot11WlanBindEntry ::= 835 SEQUENCE { 836 capwapDot11WlanBindWlanId CapwapDot11WlanIdTC, 837 capwapDot11WlanBindBssIfIndex InterfaceIndex, 838 capwapDot11WlanBindRowStatus RowStatus 839 } 841 capwapDot11WlanBindWlanId OBJECT-TYPE 842 SYNTAX CapwapDot11WlanIdTC 843 MAX-ACCESS read-only 844 STATUS current 845 DESCRIPTION 846 "Represents the WLAN ID of a WLAN. 847 During a binding operation, the AC MUST select an unused 848 WLAN ID from (1) and 16 [RFC5416]. For example, to bind 849 another WLAN profile to a radio that has been bound with 850 a WLAN profile, WLAN ID 2 should be assigned." 851 REFERENCE 852 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 853 RFC 5416." 854 ::= { capwapDot11WlanBindEntry 1 } 856 capwapDot11WlanBindBssIfIndex OBJECT-TYPE 857 SYNTAX InterfaceIndex 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "Represents the index value that uniquely identifies a 862 WLAN BSS Interface. The interface identified by a 863 particular value of this index is the same interface as 864 identified by the same value of the ifIndex. 865 The ifIndex here is for a WLAN BSS Interface. 866 The creation of a row object in the capwapDot11WlanBindTable 867 triggers the AC to automatically create a WLAN BSS Interface 868 identified by an ifIndex without manual intervention. 869 The PHY address of the capwapDot11WlanBindBssIfIndex is the 870 BSSID. While manufacturers are free to assign BSSIDs by using 871 any arbitrary mechanism, it is advised that where possible the 872 BSSIDs are assigned as a contiguous block. 873 When assigned as a block, implementations can still assign 874 any of the available BSSIDs to any WLAN. One possible method 875 is for the WTP to assign the address using the following 876 algorithm: base BSSID address + WLAN ID." 877 REFERENCE 878 "Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11, 879 RFC 5416." 880 ::= { capwapDot11WlanBindEntry 2 } 882 capwapDot11WlanBindRowStatus OBJECT-TYPE 883 SYNTAX RowStatus 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "This variable is used to create, modify, and/or delete a row 888 in this table." 889 ::= { capwapDot11WlanBindEntry 3 } 891 -- End of capwapDot11WlanBindTable Table 893 -- Module compliance 895 capwapDot11Groups OBJECT IDENTIFIER 896 ::= { capwapDot11Conformance 1 } 898 capwapDot11Compliances OBJECT IDENTIFIER 899 ::= { capwapDot11Conformance 2 } 901 capwapDot11Compliance MODULE-COMPLIANCE 902 STATUS current 903 DESCRIPTION 904 "Describes the requirements for conformance to the 905 CAPWAP-DOT11-MIB module." 907 MODULE -- this module 908 MANDATORY-GROUPS { 909 capwapDot11WlanGroup, 910 capwapDot11WlanBindGroup 911 } 912 ::= { capwapDot11Compliances 1 } 914 capwapDot11WlanGroup OBJECT-GROUP 915 OBJECTS { 916 capwapDot11WlanProfileIfIndex, 917 capwapDot11WlanMacType, 918 capwapDot11WlanTunnelMode, 919 capwapDot11WlanRowStatus 920 } 921 STATUS current 922 DESCRIPTION 923 "A collection of objects which are used to configure 924 the properties of a WLAN profile." 926 ::= { capwapDot11Groups 1 } 928 capwapDot11WlanBindGroup OBJECT-GROUP 929 OBJECTS { 930 capwapDot11WlanBindWlanId, 931 capwapDot11WlanBindBssIfIndex, 932 capwapDot11WlanBindRowStatus 933 } 934 STATUS current 935 DESCRIPTION 936 "A collection of objects which are used to bind the 937 WLAN profiles with a radio." 938 ::= { capwapDot11Groups 2 } 940 END 942 10. Security Considerations 944 There are a number of management objects defined in this MIB module 945 with a MAX-ACCESS clause of read-write and/or read-create. Such 946 objects MAY be considered sensitive or vulnerable in some network 947 environments. The support for SET operations in a non-secure 948 environment without proper protection can have a negative effect on 949 network operations. The followings are the tables and objects and 950 their sensitivity/vulnerability: 952 o - Unauthorized changes to the capwapDot11WlanTable and 953 capwapDot11WlanBindTable MAY disrupt allocation of resources in 954 the network, also change the behavior of WLAN system such as MAC 955 type. 957 SNMP versions prior to SNMPv3 did not include adequate security. 958 Even if the network itself is secure (for example by using IPSec), 959 even then, there is no control as to who on the secure network is 960 allowed to access and GET/SET (read/change/create/delete) the objects 961 in this MIB module. 963 It is RECOMMENDED that implementers consider the security features as 964 provided by the SNMPv3 framework (see [RFC3410], section 8), 965 including full support for the SNMPv3 cryptographic mechanisms (for 966 authentication and privacy). 968 Further, deployment of SNMP versions prior to SNMPv3 is NOT 969 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 970 enable cryptographic security. It is then a customer/operator 971 responsibility to ensure that the SNMP entity giving access to an 972 instance of this MIB module is properly configured to give access to 973 the objects only to those principals (users) that have legitimate 974 rights to indeed GET or SET (change/create/delete) them. 976 11. IANA Considerations 978 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module 980 The MIB module in this document uses the following IANA-assigned 981 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 983 Descriptor OBJECT IDENTIFIER value 984 ---------- ----------------------- 986 capwapDot11MIB { mib-2 XXX } 988 11.2. IANA Considerations for ifType 990 Require IANA to assign a ifType for the WLAN Profile Interface. 992 Require IANA to assign a ifType for the WLAN BSS Interface. 994 12. Contributors 996 This MIB module is based on contributions from Long Gao. 998 13. Acknowledgements 1000 The authors wish to thank David Harrington, Abhijit Choudhury, Fei 1001 Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Yujin Zhao, Haitao 1002 Zhang, Hao Wang. 1004 14. References 1006 14.1. Normative References 1008 [RFC2119] Bradner, S., "Key words for use in RFCs 1009 to Indicate Requirement Levels", BCP 14, 1010 RFC 2119, March 1997. 1012 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1013 and J. Schoenwaelder, Ed., "Structure of 1014 Management Information Version 2 1015 (SMIv2)", STD 58, RFC 2578, April 1999. 1017 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1018 and J. Schoenwaelder, Ed., "Textual 1019 Conventions for SMIv2", STD 58, RFC 2579, 1020 April 1999. 1022 [RFC2580] McCloghrie, K., Perkins, D., and J. 1023 Schoenwaelder, "Conformance Statements 1024 for SMIv2", STD 58, RFC 2580, April 1999. 1026 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1027 Interfaces Group MIB", RFC 2863, 1028 June 2000. 1030 [RFC3418] Presuhn, R., "Management Information Base 1031 (MIB) for the Simple Network Management 1032 Protocol (SNMP)", STD 62, RFC 3418, 1033 December 2002. 1035 [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y. 1036 Zhang, "CAPWAP Protocol Base MIB", 1037 draft-ietf-capwap-base-mib-05 (work in 1038 progress), May 2009. 1040 [RFC5415] Calhoun, P., Montemurro, M., and D. 1041 Stanley, "Control And Provisioning of 1042 Wireless Access Points (CAPWAP) Protocol 1043 Specification", RFC 5415, March 2009. 1045 [RFC5416] Calhoun, P., Montemurro, M., and D. 1046 Stanley, "Control and Provisioning of 1047 Wireless Access Points (CAPWAP) Protocol 1048 Binding for IEEE 802.11", RFC 5416, 1049 March 2009. 1051 [IEEE.802-11.2007] "Information technology - 1052 Telecommunications and information 1053 exchange between systems - Local and 1054 metropolitan area networks - Specific 1055 requirements - Part 11: Wireless LAN 1056 Medium Access Control (MAC) and Physical 1057 Layer (PHY) specifications", 1058 IEEE Standard 802.11, 2007, . 1062 14.2. Informative References 1064 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1065 Stewart, "Introduction and Applicability 1066 Statements for Internet-Standard 1067 Management Framework", RFC 3410, 1068 December 2002. 1070 [RFC4347] Rescorla, E. and N. Modadugu, "Datagram 1071 Transport Layer Security", RFC 4347, 1072 April 2006. 1074 Appendix A. Appendix A. Changes between -05 and -04 1076 All the issues are tracked by 1077 http://www.capwap.org/cgi-bin/roundup.cgi/MIB/ 1079 1)Issue 71: For Dot11 MIB, some bugs detected post-WGLC but pre-IESG 1081 The editor's address is updated. Also, update the WTP id in the 1082 section 8. 1084 2)Issue 73: For the example section in the Base and Dot11 MIB, the 1085 Dot11OperationTable is incorrect 1087 In the draft version 04, the Dot11OperationTable follows the IEEE 1088 802.11-1999 instead of IEEE 802.11-2007. It is incorrect. The draft 1089 version 05 is updated according to IEEE 802.11-2007. 1091 Authors' Addresses 1093 Yang Shi (editor) 1094 Hangzhou H3C Tech. Co., Ltd. 1095 Beijing R&D Center of H3C, Digital Technology Plaza, 1096 NO.9 Shangdi 9th Street,Haidian District, 1097 Beijing 1098 China(100085) 1100 Phone: +86 010 82775276 1101 EMail: young@h3c.com 1103 David Perkins (editor) 1104 SNMPinfo 1105 288 Quailbrook Ct San Carlos, 1106 CA 94070 1107 USA 1109 Phone: +1 408 394-8702 1110 EMail: dperkins@snmpinfo.com 1111 Chris Elliott (editor) 1112 Cisco Systems, Inc. 1113 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 1114 27709 1115 USA 1117 Phone: +1 919-392-2146 1118 EMail: chelliot@cisco.com 1120 Yong Zhang (editor) 1121 Fortinet, Inc. 1122 1090 Kifer Road 1123 Sunnyvale, CA 94086 1124 USA 1126 EMail: yzhang@fortinet.com