idnits 2.17.1 draft-ietf-capwap-802dot11-mib-03.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 (March 3, 2009) is 5526 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) == Missing Reference: 'RFC3411' is mentioned on line 1174, but not defined == Outdated reference: A later version (-09) exists of draft-ietf-capwap-base-mib-03 ** 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 (~~), 4 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 H3C Tech. Co., Ltd 4 Intended status: Standards Track D. Perkins, Ed. 5 Expires: September 4, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 March 3, 2009 12 CAPWAP Protocol Binding MIB for IEEE 802.11 13 draft-ietf-capwap-802dot11-mib-03 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 September 4, 2009. 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. Requirements and Constraints . . . . . . . . . . . . . . . 5 65 5.2. Mechanism of Reusing Wireless Binding MIB Module . . . . . 5 66 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 67 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 68 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7 69 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7 70 7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7 71 7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 8 72 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 73 8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8 74 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 75 10. Security Considerations . . . . . . . . . . . . . . . . . . . 20 76 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 77 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 21 78 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 21 79 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 21 80 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 81 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 82 14.1. Normative References . . . . . . . . . . . . . . . . . . . 21 83 14.2. Informative References . . . . . . . . . . . . . . . . . . 23 84 Appendix A. Appendix A. Changes between -03 and -02 . . . . . . . 23 86 1. Introduction 88 The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines 89 a standard, interoperable protocol, which enables an Access 90 Controller (AC) to manage a collection of Wireless Termination 91 Points(WTPs). CAPWAP supports the use of various wireless 92 technologies by the WTPs, with one being specified in the CAPWAP 93 Protocol Binding for IEEE 802.11 94 [I-D.ietf-capwap-protocol-binding-ieee80211]. 96 This document defines a MIB module that can be used to manage CAPWAP 97 implementations for IEEE 802.11 wireless binding. This MIB module 98 covers both configuration for WLAN and a way to reuse the MIB module 99 defined in IEEE 802.11 standard. 101 2. The Internet-Standard Management Framework 103 For a detailed overview of the documents that describe the current 104 Internet-Standard Management Framework, please refer to section 7 of 105 RFC 3410 [RFC3410]. 107 Managed objects are accessed via a virtual information store, termed 108 the Management Information Base or MIB. MIB objects are generally 109 accessed through the Simple Network Management Protocol (SNMP). 110 Objects in the MIB are defined using the mechanisms defined in the 111 Structure of Management Information (SMI). This memo specifies a MIB 112 module that is compliant to the SMIv2, which is described in STD 58, 113 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 114 [RFC2580]. 116 3. Terminology 118 This document uses terminology from the CAPWAP Protocol specification 119 [I-D.ietf-capwap-protocol-specification], the CAPWAP Protocol Binding 120 for IEEE 802.11 [I-D.ietf-capwap-protocol-binding-ieee80211] and 121 CAPWAP Protocol Base MIB [I-D.ietf-capwap-base-mib]. 123 Access Controller (AC): The network entity that provides WTP access 124 to the network infrastructure in the data plane, control plane, 125 management plane, or a combination therein. 127 Wireless Termination Point (WTP): The physical or network entity that 128 contains an RF antenna and wireless PHY to transmit and receive 129 station traffic for wireless access networks. 131 Control And Provisioning of Wireless Access Points (CAPWAP): It is a 132 generic protocol defining AC and WTP control and data plane 133 communication via a CAPWAP protocol transport mechanism. CAPWAP 134 control messages, and optionally CAPWAP data messages, are secured 135 using Datagram Transport Layer Security (DTLS) [RFC4347]. 137 CAPWAP Control Channel: A bi-directional flow defined by the AC IP 138 Address, WTP IP Address, AC control port, WTP control port and the 139 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control 140 packets are sent and received. 142 CAPWAP Data Channel: A bi-directional flow defined by the AC IP 143 Address, WTP IP Address, AC data port, WTP data port, and the 144 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data 145 packets are sent and received. 147 Station (STA): A device that contains an interface to a wireless 148 medium (WM). 150 Split and Local MAC: The CAPWAP protocol supports two modes of 151 operation: Split and Local MAC. In Split MAC mode all L2 wireless 152 data and management frames are encapsulated via the CAPWAP protocol 153 and exchanged between the AC and the WTPs. The Local MAC mode of 154 operation allows for the data frames to be either locally bridged, or 155 tunneled as 802.3 frames. 157 Wireless Binding: The CAPWAP protocol is independent of a specific 158 WTP radio technology, as well its associated wireless link layer 159 protocol. Elements of the CAPWAP protocol are designed to 160 accommodate the specific needs of each wireless technology in a 161 standard way. Implementation of the CAPWAP protocol for a particular 162 wireless technology MUST define a binding protocol for it, e.g., the 163 binding for IEEE 802.11, provided in 164 [I-D.ietf-capwap-protocol-binding-ieee80211]. 166 WLAN: The WLAN refers to a logical component instantiated on a WTP 167 device. A single physical WTP may operate a number of WLANs. Each 168 Basic Service Set Identifier (BSSID) and its constituent wireless 169 terminal radios is denoted as a distinct WLAN on a physical WTP. To 170 support a physical WTP with multiple WLANs is an important feature 171 for CAPWAP protocol's 802.11 binding, and it is also for MIB module 172 design. 174 Wireless Binding MIB Module: Other Standards Developing Organizations 175 (SDOs), such as IEEE already defined MIB module for a specific 176 wireless technology, e.g., the MIB module in IEEE 802.11 standard 177 [IEEE.802-11.2007]. Such MIB modules are called as wireless binding 178 MIB module defined by other SDOs. 180 CAPWAP Protocol Wireless Binding MIB Module: It is a MIB module 181 corresponding to CAPWAP Protocol Binding for a Wireless binding. 183 Sometimes, not all the technology-specific message elements in a 184 CAPWAP binding protocol have MIB objects defined by other SDOs. For 185 example, the protocol of [I-D.ietf-capwap-protocol-binding-ieee80211] 186 defines WLAN conception. Also, Local or Split MAC modes could be 187 specified for a WLAN. The MAC mode for a WLAN is not in the scope of 188 IEEE 802.11 [IEEE.802-11.2007]. In such cases, in addition to the 189 existing wireless binding MIB modules defined by other SDOs, a CAPWAP 190 protocol wireless binding MIB module is required to be defined for a 191 wireless binding. 193 4. Conventions 195 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 196 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 197 document are to be interpreted as described in RFC 2119 [RFC2119]. 199 5. Overview 201 5.1. Requirements and Constraints 203 The MIB module in IEEE 802.11 standard [IEEE.802-11.2007] already has 204 MIB objects definition for most IEEE 802.11 Message Elements in the 205 the CAPWAP Protocol Binding for IEEE 802.11 206 [I-D.ietf-capwap-protocol-binding-ieee80211]. As a CAPWAP Protocol 207 802.11 binding MIB module, the CAPWAP-DOT11-MIB module MUST be able 208 to reuse such MIB objects in the IEEE 802.11 MIB module. Also, the 209 functions such as MAC mode for WLAN in the 210 [I-D.ietf-capwap-protocol-binding-ieee80211] are not in the scope of 211 IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST support such 212 functions. 214 In summary, the CAPWAP-DOT11-MIB module is designed to satisfy the 215 following requirements and constraints: 217 - Could easily reuse wireless binding MIB module in the IEEE 802.11 218 standard; 220 - From AC to centrally manage and configure WLAN; 222 - Operators could configure MAC type and tunnel mode for a specific 223 WLAN. 225 5.2. Mechanism of Reusing Wireless Binding MIB Module 227 Before coming to details of CAPWAP-DOT11-MIB module, it will 228 introduce how it is able to reuse the MIB module in IEEE 802.11 229 standard. According to [I-D.ietf-capwap-protocol-binding-ieee80211], 230 each WLAN is identified by WLAN Id. In the MIB module of IEEE 802.11 231 standard, the MIB tables such as Dot11AuthenticationAlgorithmsTable 232 are able to support wireless configuration (such as authentication 233 algorithm), and these tables use ifIndex as index. To support 802.11 234 parameters for a specific WLAN, and consider that the operator has to 235 prepare configurations for each WLAN on the AC before WTPs connect to 236 AC. A WLAN could be abstracted as a 'WLAN Service Interface' on the 237 AC, and which could be identified by ifIndex. The MIB objects in the 238 MIB module of IEEE 802.11 standard which are associated with this 239 interface can be used to configure WLAN parameters for a WLAN, such 240 as Authentication Algorithm. On the AC, the MIB table 241 CapwapDot11WlanTable in the CAPWAP-DOT11-MIB module will indicate the 242 mapping relation between a 'WLAN Id" and ifIndex of a 'WLAN Service 243 Interface'. With ifIndex of a 'WLAN Service Interface', system is 244 able to reuse the MIB module in the IEEE 802.11 standard. 246 In the CAPWAP-BASE-MIB module, each PHY radio is identified by WTP Id 247 and radio ID, and has a corresponding 'WTP Virtual Radio Interface' 248 on the AC. The IEEE 802.11 MIB module associated with this interface 249 can be used to configure IEEE 802.11 wireless binding parameters for 250 radio such as RTS Threshold. The 'WLAN BSS Interface', created by 251 binding 'WTP Virtual Radio Interface' and WLAN, is used for data 252 forwarding. 254 6. Structure of the MIB Module 256 The MIB objects were derived from the CAPWAP protocol binding for 257 802.11 document [I-D.ietf-capwap-protocol-binding-ieee80211]. 259 1) capwapDot11WlanTable 261 The table is used for providing configuration such as MAC type and so 262 on for WLANs. For a specific WLAN which is identified by 263 capwapDot11WlanId, an interface of 'WLAN Service Interface' ifType 264 will be created. By the ifIndex of interface, it provides a way to 265 reuse the MIB module in IEEE 802.11 standard. For example, according 266 to [I-D.ietf-capwap-protocol-binding-ieee80211], Auth Type needs to 267 be configured for a WLAN. In the IEEE 802.11 MIB module, the MIB 268 object dot11AuthenticationAlgorithm in the 269 dot11AuthenticationAlgorithmsTable is corresponding to Auth Type. 270 Considering both capwapDot11WlanTable and 271 dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP- 272 DOT11-MIB module are able to easily reuse 273 dot11AuthenticationAlgorithm object in IEEE 802.11 MIB module. It is 274 same for other objects in the MIB module of IEEE 802.11 standard. 276 2) capwapDot11WlanBindTable 278 The table provides a way to bind WLAN to a radio, then supports 279 multiple WLANs on a physical WTP. The binding operation will 280 dynamically create 'WLAN BSS Interface', and this logical interface 281 is used for data forwarding function. 283 7. Relationship to Other MIB Modules 285 7.1. Relationship to SNMPv2-MIB Module 287 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 288 mandatory for all systems, and the objects apply to the entity as a 289 whole. The 'system' group provides identification of the management 290 entity and certain other system-wide data. The CAPWAP-DOT11-MIB 291 module does not duplicate those objects. 293 7.2. Relationship to IF-MIB Module 295 The Interfaces Group [RFC2863] defines generic managed objects for 296 managing interfaces. This memo contains the media-specific 297 extensions to the Interfaces Group for managing WLAN that are modeled 298 as interfaces. 300 For each WLAN, it will have a logical interface of 'WLAN Service 301 Interface' responding to it on the AC. The interface MUST be modeled 302 as an ifEntry and provide appropriate interface information. 'WLAN 303 Service Interface' provides a way to configure IEEE 802.11 parameters 304 for a specific WLAN, and reuse the MIB module in IEEE 802.11 305 standard. 307 Also, the system (AC) MUST have a mechanism that preserves the values 308 of ifIndex of 'WLAN Service Interface' ifType in the ifTable at AC 309 reboot. 311 To provide data forwarding service, system will dynamically create 312 logical interface of 'WLAN BSS Interface'. The interface MUST be 313 modeled as an ifEntry and provide appropriate interface information. 314 The interface enables a single physical WTP to support multiple 315 WLANs. 317 Also, the system (AC) MUST have a mechanism that preserves the values 318 of ifIndex of 'WLAN BSS Interface' ifType in the ifTable at AC 319 reboot. 321 7.3. Relationship to CAPWAP-BASE-MIB Module 323 The CAPWAP-BASE-MIB module provides a way to manage and control WTP 324 and radio objects. Especially, CAPWAP-BASE-MIB module has a 325 mechanism of 'WTP Virtual Radio Interface' which enable system to 326 reuse the MIB module in IEEE 802.11 standard. With it, operator 327 could configure an IEEE 802.11 AP radio's parameter and query radio's 328 traffic statistics. Based on CAPWAP-BASE-MIB module, CAPWAP-DOT11- 329 MIB module provides more information from WLAN perspective. 331 7.4. Relationship to MIB Module in IEEE 802.11 Standard 333 Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface' 334 ifType, the MIB module is able to reuse MIB module in the IEEE 802.11 335 standard [IEEE.802-11.2007]. The CAPWAP-DOT11-MIB module does not 336 duplicate those objects in the MIB module of IEEE 802.11 standard. 338 In the CAPWAP Protocol Binding for IEEE 802.11 339 [I-D.ietf-capwap-protocol-binding-ieee80211], it involves a part of 340 MIB objects defined by IEEE 802.11 standard. Although CAPWAP-DOT11- 341 MIB module uses it [I-D.ietf-capwap-protocol-binding-ieee80211] as a 342 reference, it could reuse all the MIB objects in the IEEE 802.11 343 standard , and not limited by the scope of CAPWAP Protocol Binding 344 for IEEE 802.11. 346 7.5. MIB modules required for IMPORTS 348 The following MIB modules are required for IMPORTS: SNMPv2-SMI 349 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 350 [RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib]. 352 8. Example of CAPWAP-DOT11-MIB Module Usage 354 The following is a whole example for configuration and management of 355 WTP, radio and WLAN for IEEE 802.11 binding. 357 1) Identify the PHY radio by 'WTP Virtual Radio Interface' 359 According to [I-D.ietf-capwap-protocol-specification], each radio on 360 a WTP will be identified by a radio Id. Each WTP could be identified 361 by its serial number. 363 Suppose a WTP's serial number is '12345678', and first radio id is 1. 364 On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' 365 ifType is 10 which represents the PHY radio 1. The following 366 information is obtained in the CapwapBaseWirelessBindingTable. 368 In CapwapBaseWirelessBindingTable 369 { 370 capwapBaseWtpStateWtpId = '12345678', 371 capwapBaseWirelessBindingRadioId = 1, 372 capwapBaseWirelessBindingVirtualRadioIfIndex = 10, 373 capwapBaseWirelessBindingType = dot11(2) 374 } 376 By the mechanism of 'WTP Virtual Radio Interface', it seems WTP PHY 377 radios are located on the AC. The interface of 'WTP Virtual Radio 378 Interface' ifType is modeled by ifTable [RFC2863]. 380 In ifTable 381 { 382 ifIndex = 10, 383 ifDescr = 'WTP Virtual Radio Interface', 384 ifType = xxx, 385 RFC Editor - please replace xxx with the value 386 allocated by IANA for IANAifType of 'WTP Virtual Radio Interface' 387 ifMtu = 0, 388 ifSpeed = 0, 389 ifPhysAddress = '000000', 390 ifAdminStatus = true, 391 ifOperStatus = false, 392 ifLastChange = 0, 393 ifInOctets = 0, 394 ifInUcastPkts = 0, 395 ifInDiscards = 0, 396 ifInErrors = 0, 397 ifInUnknownProtos = 0, 398 ifOutOctets = 0, 399 ifOutUcastPkts = 0, 400 ifOutDiscards = 0, 401 ifOutErrors = 0 402 } 404 2) Configure specific wireless binding parameters for 'WTP Virtual 405 Radio Interface' 407 It will be done on the AC through the MIB module defined in IEEE 408 802.11 standard. 410 For example, to configure parameter for 'WTP Virtual Radio Interface' 411 by Dot11OperationTable [IEEE.802-11.2007]. 413 In Dot11OperationTable 414 { 415 ifIndex = 10, 416 dot11MACAddress = 0.0.0.0.0.0, 417 dot11RTSThreshold = 2347, 418 dot11ShortRetryLimit = 7, 419 dot11LongRetryLimit = 4, 420 dot11FragmentationThreshold = 256, 421 dot11MaxTransmitMSDULifetime = 512, 422 dot11MaxReceiveLifetime = 512, 423 dot11ManufacturerID = 'capwap', 424 dot11ProductID = 'capwap' 425 } 427 In the example, it supposes ifIndex of a 'WTP Virtual Radio 428 Interface' is 10. 430 3) Configure WLAN 432 WLAN configuration will be done through CAPWAP-DOT11-MIB Module, and 433 the MIB module defined in IEEE 802.11 standard 435 First step is to create a 'WLAN Service Interface' through CAPWAP- 436 DOT11-MIB Module on the AC. 438 Here supposes to configure a WLAN which is identified by 439 capwapDot11WlanId 1, and CapwapDot11WlanTable would create a row 440 object for it. 442 In CapwapDot11WlanTable 443 { 444 capwapDot11WlanId = 1, 445 capwapDot11WlanServiceIfIndex = 20, 446 capwapDot11WlanMacType = splitMAC(2), 447 capwapDot11WlanTunnelMode = dot3Tunnel(2), 448 capwapDot11WlanRowStatus = create 449 } 451 The creation operation of a row object would trigger AC system to 452 automatically create a 'WLAN Service Interface' and it is identified 453 by ifIndex 20. It does not require operator to manually create a 454 'WLAN Service Interface'. 456 Corresponding to 'WLAN Service Interface', it MUST be modeled as an 457 ifEntry on the AC and provide appropriate interface information. 458 CapwapDot11WlanTable would keep the mapping relationship between 459 capwapDot11WlanId and ifIndex of a 'WLAN Service Interface'. 461 In ifTable 462 { 463 ifIndex = 20, 464 ifDescr = 'WLAN Service Interface', 465 ifType = xxx, 466 RFC Editor - please replace xxx with the value 467 allocated by IANA for IANAifType of 'WLAN Service Interface' 468 ifMtu = 0, 469 ifSpeed = 0, 470 ifPhysAddress = 0.0.0.0.0.0, 471 ifAdminStatus = true, 472 ifOperStatus = true, 473 ifLastChange = 0, 474 ifInOctets = 0, 475 ifInUcastPkts = 0, 476 ifInDiscards = 0, 477 ifInErrors = 0, 478 ifInUnknownProtos = 0, 479 ifOutOctets = 0, 480 ifOutUcastPkts = 0, 481 ifOutDiscards = 0, 482 ifOutErrors = 0 483 } 485 Second step is to configure WLAN parameters of 'WLAN Service 486 Interface' through the MIB module defined in IEEE 802.11 standard on 487 the AC. 489 Suppose operator to configure authentication algorithm for a WLAN. 491 In Dot11AuthenticationAlgorithmsTable 492 { 493 ifIndex = 20, 494 dot11AuthenticationAlgorithmsIndex = 1, 495 dot11AuthenticationAlgorithm = Shared Key, 496 dot11AuthenticationAlgorithmsEnable = true 497 } 499 Here ifIndex 20 is for interface of 'WLAN Service Interface' ifType. 500 Suppose the index of authentication algorithm is 1. 502 4) Bind WLAN to WTP radio 504 On the AC, through CapwapDot11WlanBindTable in the CAPWAP-DOT11-MIB, 505 it configures which WLAN (identified by capwapDot11WlanId) will be 506 provided on which 'WTP Virtual Radio Interface' (identified by 507 ifIndex). 509 Here supposes to bind a WLAN (capwapDot11WlanId is 1) with a 510 interface of 'WTP Virtual Radio Interface'(ifIndex is 10). The 511 CapwapDot11WlanBindTable would create a row object for it. 513 In CapwapDot11WlanBindTable 514 { 515 ifIndex = 10, 516 capwapDot11WlanId = 1, 517 capwapDot11WlanBindBssIfIndex = 30, 518 capwapDot11WlanBindBssRowStatus = create 519 } 521 Suppose capwapDot11WlanMacType of WLAN is splitMAC(2), the creation 522 operation of a row object on the CapwapDot11WlanBindTable would 523 trigger AC system to automatically create a 'WLAN BSS Interface' and 524 it is identified by ifIndex 30. It does not require operator to 525 manually create a 'WLAN BSS Interface'. 527 Corresponding to 'WLAN BSS Interface', it MUST be modeled as an 528 ifEntry on the AC and provide appropriate interface information. 529 CapwapDot11WlanBindTable would keep the mapping relationship among 530 ifIndex of a 'WTP Virtual Radio Interface', WLAN and ifIndex of a 531 'WLAN BSS Interface'. 533 5) WTP reports its current configuration status 535 After join phase and before WTP get configuration from AC, it will 536 report its current configuration status to AC through configuration 537 status request message. The MIB data will be updated on the AC. As 538 an example, for ifIndex 10 (which identifies an interface of 'WLAN 539 Virtual Radio Interface' ifType), its ifOperStatus in ifTable will be 540 updated with current radio operational status. 542 6) Query WTP and radio statistics data 544 After WTPs come to run status, operator could query WTP and radio 545 statistics data through CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB module. 546 For example, through dot11CountersTable [IEEE.802-11.2007], operator 547 could query counter data for radio which is identified by ifIndex of 548 a 'WLAN Virtual Radio Interface'. 550 7) Query other statistics data 552 For example, operator could query the configuration of WLAN through 553 Dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and statistic 554 data of 'WLAN BSS Interface' through ifTable; 556 9. Definitions 557 CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN 559 IMPORTS 560 RowStatus, TEXTUAL-CONVENTION 561 FROM SNMPv2-TC 562 OBJECT-GROUP, MODULE-COMPLIANCE 563 FROM SNMPv2-CONF 564 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 565 FROM SNMPv2-SMI 566 ifIndex, InterfaceIndex 567 FROM IF-MIB 568 CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC 569 FROM CAPWAP-BASE-MIB; 571 capwapDot11MIB MODULE-IDENTITY 572 LAST-UPDATED "200903030000Z" -- March 3th, 2009 573 ORGANIZATION "IETF Control And Provisioning of Wireless Access 574 Points (CAPWAP) Working Group 575 http://www.ietf.org/html.charters/capwap-charter.html" 576 CONTACT-INFO 577 "General Discussion: capwap@frascone.com 578 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 580 Yang Shi 581 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 582 District,Beijing,China(100085) 583 Email: young@h3c.com 585 David T. Perkins 586 228 Bayview Dr 587 San Carlos, CA 94070 588 USA 589 Phone: +1 408 394-8702 590 Email: dperkins@snmpinfo.com 592 Chris Elliott 593 Cisco Systems, Inc. 594 7025 Kit Creek Rd., P.O. Box 14987 595 Research Triangle Park 27709 596 USA 597 Phone: +1 919-392-2146 598 Email: chelliot@cisco.com 600 Yong Zhang 601 Fortinet, Inc. 602 1090 Kifer Road 603 Sunnyvale, CA 94086 604 USA 605 Email: yzhang@fortinet.com" 607 DESCRIPTION 608 "Copyright (C) 2009 The Internet Society. This version of 609 the MIB module is part of RFC xxx; see the RFC itself 610 for full legal notices. 612 This MIB module contains managed object definitions for 613 CAPWAP Protocol binding for IEEE 802.11." 614 REVISION "200903030000Z" 615 DESCRIPTION 616 "Initial version, published as RFC xxx" 617 ::= { mib-2 xxx } 619 -- Textual conventions 621 CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION 622 DISPLAY-HINT "d" 623 STATUS current 624 DESCRIPTION 625 "Represents an unique identifier of a WLAN. 626 According to REFERENCE, the value of WLAN ID MUST be between 627 one (1) and 16, and it is specified for a radio of WTP. 628 The SYNTAX of capwapDot11WlanId is defined as 629 CapwapDot11WlanIdTC, and capwapDot11WlanId is WLAN configured 630 on the AC (NOT on the WTP). 631 As AC could have more WLANs configured than WTP, the value of 632 capwapDot11WlanId could be more than 16. 633 SYNTAX CapwapDot11WlanIdTC " 634 REFERENCE 635 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 636 RFC xxx." 637 SYNTAX Unsigned32 (1..512) 639 -- Top level components of this MIB module 641 -- Tables, Scalars 642 capwapDot11Objects OBJECT IDENTIFIER 643 ::= { capwapDot11MIB 1 } 644 -- Conformance 645 capwapDot11Conformance OBJECT IDENTIFIER 646 ::= { capwapDot11MIB 2 } 648 -- capwapDot11WlanTable Table 650 capwapDot11WlanTable OBJECT-TYPE 651 SYNTAX SEQUENCE OF CapwapDot11WlanEntry 652 MAX-ACCESS not-accessible 653 STATUS current 654 DESCRIPTION 655 "A table of objects that display and control WLANs. 656 Values of all objects in this table are persistent at 657 restart/reboot." 658 ::= { capwapDot11Objects 1 } 660 capwapDot11WlanEntry OBJECT-TYPE 661 SYNTAX CapwapDot11WlanEntry 662 MAX-ACCESS not-accessible 663 STATUS current 664 DESCRIPTION 665 "A set of objects that display and control WLANs." 666 INDEX { capwapDot11WlanId } 667 ::= { capwapDot11WlanTable 1 } 669 CapwapDot11WlanEntry ::= 670 SEQUENCE { 671 capwapDot11WlanId CapwapDot11WlanIdTC, 672 capwapDot11WlanServiceIfIndex InterfaceIndex, 673 capwapDot11WlanMacType CapwapBaseMacTypeTC, 674 capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC, 675 capwapDot11WlanRowStatus RowStatus 676 } 678 capwapDot11WlanId OBJECT-TYPE 679 SYNTAX CapwapDot11WlanIdTC 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "Represents the WLAN Id for a WLAN which has a 684 capwapDot11WlanServiceIfIndex interface corresponding to it." 685 REFERENCE 686 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 687 RFC xxx." 688 ::= { capwapDot11WlanEntry 1 } 690 capwapDot11WlanServiceIfIndex OBJECT-TYPE 691 SYNTAX InterfaceIndex 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "Represents the index value that uniquely identifies a 696 'WLAN Service Interface'. The interface identified by a 697 particular value of this index is the same interface as 698 identified by the same value of ifIndex. 699 The creation operation of a row object on the 700 capwapDot11WlanTable would trigger AC system to automatically 701 create a 'WLAN Service Interface' and it is identified by 702 ifIndex. It does not require operator to manually create a 703 'WLAN Service Interface'. 704 Before WTPs connect to AC and get configuration, operator 705 will prepare configuration for them. For a specific WLAN, 706 a logical interface of 'WLAN Service Interface' 707 ifType will be created by system, and operator could 708 configure WLAN parameter through it. 709 For example, according to IEEE 802.11 '6.1. IEEE 802.11 710 Add WLAN' in the [I-D.ietf-capwap-protocol-binding-ieee80211], 711 operator could configure Auth Type for a WLAN. The 'WLAN 712 Service Interface' provides a way to uniquely identify each 713 WLAN by logical on the AC. As most MIB modules use ifIndex to 714 identify an interface for configuration and statistic data, 715 for example, dot11AuthenticationAlgorithmsTable in IEEE 802.11 716 MIB module use ifIndex as index, and 717 dot11AuthenticationAlgorithm object is for Auth Type mentioned 718 in the CAPWAP '6.1. IEEE 802.11 Add WLAN' 719 [I-D.ietf-capwap-protocol-binding-ieee80211], With the way of 720 'WLAN Service Interface', it will easily reuse MIB table like 721 dot11AuthenticationAlgorithmsTable in the IEEE 802.11 standard, 722 while only care for other configurations like 723 capwapDot11WlanTunnelMode." 724 ::= { capwapDot11WlanEntry 2 } 726 capwapDot11WlanMacType OBJECT-TYPE 727 SYNTAX CapwapBaseMacTypeTC 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "Represents whether the WTP should support the WLAN in 732 Local or Split MAC modes." 733 REFERENCE 734 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 735 RFC xxx." 736 ::= { capwapDot11WlanEntry 3 } 738 capwapDot11WlanTunnelMode OBJECT-TYPE 739 SYNTAX CapwapBaseTunnelModeTC 740 MAX-ACCESS read-create 741 STATUS current 742 DESCRIPTION 743 "Represents the frame tunneling type to be used for 802.11 data 744 frames from all stations associated with the WLAN. 745 Bits are exclusive with each other for a specific WLAN Id, and 746 only one tunnel mode could be configured. 747 If operator set more than one bit, the value of the 748 Response-PDU's error-status field is set to `wrongValue', 749 and the value of its error-index field is set to the index of 750 the failed variable binding." 751 REFERENCE 752 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 753 RFC xxx." 754 ::= { capwapDot11WlanEntry 4 } 756 capwapDot11WlanRowStatus OBJECT-TYPE 757 SYNTAX RowStatus 758 MAX-ACCESS read-create 759 STATUS current 760 DESCRIPTION 761 "This variable is used to create, modify, and/or delete a row in 762 this table." 763 ::= { capwapDot11WlanEntry 5 } 765 -- End of capwapDot11WlanTable Table 767 -- capwapDot11WlanBindTable Table 769 capwapDot11WlanBindTable OBJECT-TYPE 770 SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry 771 MAX-ACCESS not-accessible 772 STATUS current 773 DESCRIPTION 774 "A table of objects that configure which WLAN 775 (identified by capwapDot11WlanId) will be provided on 776 which 'WTP Virtual Radio Interface' (identified by ifIndex) 777 Also, display and control the mapping 778 relationship between interface of 'WTP Virtual Radio Interface' 779 interface and interface of 'WLAN BSS Interface'. 780 The PHY address for interface of 'WTP Virtual Radio 781 Interface' ifType will be base BSSID address for PHY 782 radio." 783 REFERENCE 784 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 785 RFC xxx." 786 ::= { capwapDot11Objects 2 } 788 capwapDot11WlanBindEntry OBJECT-TYPE 789 SYNTAX CapwapDot11WlanBindEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "A set of objects that display the mapping relationship 794 between interface of 'WTP Virtual Radio Interface' and 795 interface of 'WLAN BSS Interface'. 796 The INDEX object ifIndex is the ifIndex of an interface 797 'WTP Virtual Radio Interface'." 798 INDEX { ifIndex, capwapDot11WlanId } 799 ::= { capwapDot11WlanBindTable 1 } 801 CapwapDot11WlanBindEntry ::= 802 SEQUENCE { 803 capwapDot11WlanBindBssIfIndex InterfaceIndex, 804 capwapDot11WlanBindBssRowStatus RowStatus 805 } 807 capwapDot11WlanBindBssIfIndex OBJECT-TYPE 808 SYNTAX InterfaceIndex 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "Represents the index value that uniquely identifies a 813 'WLAN BSS Interface'. The interface identified by a 814 particular value of this index is the same interface as 815 identified by the same value of ifIndex. The ifIndex here 816 is for an interface of 'WLAN BSS Interface'. 817 For a WLAN configuration on a radio, an interface of 'WLAN 818 BSS Interface' will correspond to it. 819 The creation operation of a row object on the 820 capwapDot11WlanBindTable would trigger AC system to 821 automatically create a 'WLAN BSS Interface' and it is 822 identified by ifIndex. It does not require operator to manually 823 create a 'WLAN BSS Interface'. 824 The PHY address for capwapDot11WlanBindBssIfIndex is BSSID. 825 While manufacturers are free to assign BSSIDs using any 826 arbitrary mechanism, it is advised that where possible the 827 BSSIDs are assigned as a contiguous block. 828 When assigned as a block, implementations can still assign 829 any of the available BSSIDs to any WLAN. One possible method 830 is for the WTP to assign the address using the following 831 algorithm: base BSSID address + WLAN ID." 832 REFERENCE 833 "Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11, 834 RFC xxx." 835 ::= { capwapDot11WlanBindEntry 1 } 837 capwapDot11WlanBindBssRowStatus OBJECT-TYPE 838 SYNTAX RowStatus 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "This variable is used to create, modify, and/or delete a row 843 in this table." 844 ::= { capwapDot11WlanBindEntry 2 } 846 -- End of capwapDot11WlanBindTable Table 848 -- Module compliance 850 capwapDot11Groups OBJECT IDENTIFIER 851 ::= { capwapDot11Conformance 1 } 853 capwapDot11Compliances OBJECT IDENTIFIER 854 ::= { capwapDot11Conformance 2 } 856 capwapDot11Compliance MODULE-COMPLIANCE 857 STATUS current 858 DESCRIPTION 859 "Describes the requirements for conformance to the 860 CAPWAP-DOT11-MIB module." 862 MODULE -- this module 863 MANDATORY-GROUPS { 864 capwapDot11WlanGroup, 865 capwapDot11WlanBindGroup 866 } 867 ::= { capwapDot11Compliances 1 } 869 capwapDot11WlanGroup OBJECT-GROUP 870 OBJECTS { 871 capwapDot11WlanServiceIfIndex, 872 capwapDot11WlanMacType, 873 capwapDot11WlanTunnelMode, 874 capwapDot11WlanRowStatus 875 } 876 STATUS current 877 DESCRIPTION 878 "The collection of objects which are used to configure 879 property of WLAN." 880 ::= { capwapDot11Groups 1 } 882 capwapDot11WlanBindGroup OBJECT-GROUP 883 OBJECTS { 884 capwapDot11WlanBindBssIfIndex, 885 capwapDot11WlanBindBssRowStatus 886 } 887 STATUS current 888 DESCRIPTION 889 "The collection of objects which are used to configure 890 WLAN BSS." 891 ::= { capwapDot11Groups 2 } 893 END 895 10. Security Considerations 897 There are a number of management objects defined in this MIB module 898 with a MAX-ACCESS clause of read-write and/or read-create. Such 899 objects may be considered sensitive or vulnerable in some network 900 environments. The support for SET operations in a non-secure 901 environment without proper protection can have a negative effect on 902 network operations. The followings are the tables and objects and 903 their sensitivity/vulnerability: 905 o - Unauthorized changes to the capwapDot11WlanTable and 906 capwapDot11WlanBindTable may disrupt allocation of resources in 907 the network, also change the behavior of WLAN system such as MAC 908 type. 910 SNMP versions prior to SNMPv3 did not include adequate security. 911 Even if the network itself is secure (for example by using IPSec), 912 even then, there is no control as to who on the secure network is 913 allowed to access and GET/SET (read/change/create/delete) the objects 914 in this MIB module. 916 It is RECOMMENDED that implementers consider the security features as 917 provided by the SNMPv3 framework (see [RFC3410], section 8), 918 including full support for the SNMPv3 cryptographic mechanisms (for 919 authentication and privacy). 921 Further, deployment of SNMP versions prior to SNMPv3 is NOT 922 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 923 enable cryptographic security. It is then a customer/operator 924 responsibility to ensure that the SNMP entity giving access to an 925 instance of this MIB module is properly configured to give access to 926 the objects only to those principals (users) that have legitimate 927 rights to indeed GET or SET (change/create/delete) them. 929 11. IANA Considerations 930 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module 932 The MIB module in this document uses the following IANA-assigned 933 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 935 Descriptor OBJECT IDENTIFIER value 936 ---------- ----------------------- 938 capwapDot11MIB { mib-2 XXX } 940 11.2. IANA Considerations for ifType 942 Require IANA to assign a ifType for 'WLAN Service Interface' type. 944 Require IANA to assign a ifType for 'WLAN BSS Interface' type. 946 12. Contributors 948 This MIB module is based on contributions from Long Gao. 950 13. Acknowledgements 952 The authors wish to thank David Harrington, Fei Fang, Yu Liu, Sachin 953 Dutta, Yujin Zhao, Haitao Zhang, Hao Song. 955 14. References 957 14.1. Normative References 959 [RFC2119] Bradner, S., "Key words 960 for use in RFCs to 961 Indicate Requirement 962 Levels", BCP 14, 963 RFC 2119, March 1997. 965 [RFC2578] McCloghrie, K., Ed., 966 Perkins, D., Ed., and 967 J. Schoenwaelder, Ed., 968 "Structure of 969 Management Information 970 Version 2 (SMIv2)", 971 STD 58, RFC 2578, 972 April 1999. 974 [RFC2579] McCloghrie, K., Ed., 975 Perkins, D., Ed., and 976 J. Schoenwaelder, Ed., 977 "Textual Conventions 978 for SMIv2", STD 58, 979 RFC 2579, April 1999. 981 [RFC2580] McCloghrie, K., 982 Perkins, D., and J. 983 Schoenwaelder, 984 "Conformance Statements 985 for SMIv2", STD 58, 986 RFC 2580, April 1999. 988 [RFC2863] McCloghrie, K. and F. 989 Kastenholz, "The 990 Interfaces Group MIB", 991 RFC 2863, June 2000. 993 [RFC3418] Presuhn, R., 994 "Management Information 995 Base (MIB) for the 996 Simple Network 997 Management Protocol 998 (SNMP)", STD 62, 999 RFC 3418, 1000 December 2002. 1002 [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., 1003 Elliott, C., and Y. 1004 Zhang, "CAPWAP Protocol 1005 Base MIB", draft-ietf- 1006 capwap-base-mib-03 1007 (work in progress), 1008 November 2008. 1010 [I-D.ietf-capwap-protocol-specification] Montemurro, M., 1011 Stanley, D., and P. 1012 Calhoun, "CAPWAP 1013 Protocol 1014 Specification", draft- 1015 ietf-capwap-protocol- 1016 specification-15 (work 1017 in progress), 1018 November 2008. 1020 [I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M., 1021 Stanley, D., and P. 1022 Calhoun, "CAPWAP 1023 Protocol Binding for 1024 IEEE 802.11", draft- 1025 ietf-capwap-protocol- 1026 binding-ieee80211-12 1027 (work in progress), 1028 November 2008. 1030 [IEEE.802-11.2007] "Information technology 1031 - Telecommunications 1032 and information 1033 exchange between 1034 systems - Local and 1035 metropolitan area 1036 networks - Specific 1037 requirements - Part 11: 1038 Wireless LAN Medium 1039 Access Control (MAC) 1040 and Physical Layer 1041 (PHY) specifications", 1042 IEEE Standard 802.11, 1043 2007, . 1048 14.2. Informative References 1050 [RFC3410] Case, J., Mundy, R., 1051 Partain, D., and B. 1052 Stewart, "Introduction 1053 and Applicability 1054 Statements for 1055 Internet-Standard 1056 Management Framework", 1057 RFC 3410, 1058 December 2002. 1060 [RFC4347] Rescorla, E. and N. 1061 Modadugu, "Datagram 1062 Transport Layer 1063 Security", RFC 4347, 1064 April 2006. 1066 Appendix A. Appendix A. Changes between -03 and -02 1068 T1. T4. In order for ifIndex to be used as a common handler for the 1069 CAPWAP MIB and for the interface specific MIB modules like a dot11 1070 MIB from IEEE one needs to ensure that the same numbering scheme and 1071 mapping is used by all MIB modules, and that it behaves identically 1072 for events like interface card swapping, reset or power loss. I do 1073 not see how this can happen, I am not sure that this is possible at 1074 all, and in any case there is no text in the document that explains 1075 this mechanism. 1077 -------------------------------------------------------------- 1079 In the Capwap Digest, Vol 39, Issue 4, we gave the text to explain a 1080 mechanism that preserves the values of ifIndex, Request mailing list 1081 to confirm it. 1083 In the section of "Relationship to the IF-MIB", add text: 1085 Also, the system (AC) MUST have a mechanism that preserves the values 1086 of ifIndex of 'WLAN Service Interface' ifType in the ifTable at AC 1087 reboot. 1089 Also, the system (AC) MUST have a mechanism that preserves the values 1090 of ifIndex of 'WLAN BSS Interface' ifType in the ifTable at AC 1091 reboot. 1093 T2. Is the WLAN Service interface described in Section 7.2 modeled 1094 by capwapDot11WlanConfigTable? If so please say it and make this 1095 clear by using a more explicit naming convention. The model here is 1096 not clear to me. On one hand you say 'the interface SHOULD be 1097 modeled as an ifEntry ...' Why only a SHOULD and not a MUST? What 1098 is the procedure for the manager? Is he looking for all 802.11 1099 interfaces on the AC and then creates manually a WLAN Service entry 1100 in the table for each? What if the ifNumber does not correspond to a 1101 802.11 interface? What if the 802.11 interface disappears? 1103 ----------------------------------------------------------------- 1105 1) The "WLAN Service interface" is modeled by 1106 capwapDot11WlanConfigTable, and capwapDot11WlanConfigTable is rename 1107 as capwapDot11WlanTable. 1109 2) Yes, the the interface MUST be modeled as an ifEntry, not SHOULD 1110 be 1112 3) What is the procedure for the manager? Is he looking for all 1113 802.11 interfaces on the AC and then creates manually a WLAN Service 1114 entry in the table for each? 1116 Please refer to the section of Example of CAPWAP-DOT11-MIB Module 1117 Usage (the section is updated in the new version). 1119 The creation operation of a row object on capwapDot11WlanTable would 1120 trigger system to create "WLAN service Interface", and it does not 1121 require operator to manually create a "WLAN service Interface". 1123 In the section of "Relationship to the IF-MIB", add text: 1125 Also, the system (AC) MUST have a mechanism that preserves the values 1126 of ifIndex of 'WLAN Service Interface' ifType in the ifTable at AC 1127 reboot. 1129 T3. What 'could be always enabled' means for ifAdminStatus and 1130 ifOperStatus in the WLAN Service Interface table? Either change this 1131 to MUST or explain in what cases these should be other than enabled. 1133 -------------------------------------------------------------- 1135 The section for interpration of specific MIB objects in the iftable 1136 was removed in the new version. Reader could refer to RFC2863 1138 T4. What does the statement that 'the other objects such as 1139 ifInOctets ... are unused' relative to the VLAN Service interface 1140 mean? Counters are always zero? 1142 -------------------------------------------------------------- 1144 The section for interpration of specific MIB objects in the iftable 1145 was removed in the new version. Reader could refer to RFC2863 1147 T5. In 7.4 - does the text mean that the manager can reuse objects 1148 from the IEEE 802.11 MIB modules, or that values of these objects are 1149 being duplicates in this MIB module? (why? Which ones?) In any case 1150 the IEEE 802.11 standard that defines these objects must be a 1151 Normative Reference for this document. 1153 ----------------------------------------------------------------- 1155 Yes 1157 1)the text mean that the manager can reuse objects from the IEEE 1158 802.11 MIB modules, and the section of "Mechanism of Reusing Wireless 1159 Binding MIB Module" give explain to it. 1161 2) also, add one text of "The CAPWAP-DOT11-MIB module does not 1162 duplicate those objects in the MIB module of IEEE 802.11 standard." 1163 in the section of "7.4. Relationship to MIB Module in IEEE 802.11 1164 Standard" 1166 3) yes, IEEE 802.11 standard was added as a Normative Reference. 1168 T6. The RFCs that define all MIB modules required for IMPORTSs must 1169 be Normative References to this document. 1171 ----------------------------------------------------------------- 1173 add reference to RFC3411 in the section of "MIB modules required for 1174 IMPORTS", add "SNMP-FRAMEWORK-MIB [RFC3411]," 1176 T7. The value of the object capwapBaseWTPId in the example is the 1177 string '12345678' not the integer 12345678 1179 ----------------------------------------------------------------- 1181 Yes, it is change into '12345678' 1183 T8. The names of the objects in the capwapDot11WlanConfigTable are 1184 not consistent (similar prefix) to capwapDot11WlanConfigEntry. 1186 --------------------------------------------------------- 1188 Yes, they are changed with: 1190 CapwapDot11WlanEntry ::= 1191 SEQUENCE { 1192 capwapDot11WlanId CapwapDot11WlanIdTC, 1193 capwapDot11WlanServiceIfIndex InterfaceIndex, 1194 capwapDot11WlanMacType CapwapBaseMacTypeTC, 1195 capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC, 1196 capwapDot11WlanRowStatus RowStatus 1197 } 1199 T9. The names of the objects in the capwapDot11WlanBindTable are not 1200 consistent (similar prefix) to capwapDot11WlanBindEntry. 1202 --------------------------------------------------------- 1204 Yes, they are changed with: 1206 CapwapDot11WlanBindEntry ::= 1207 SEQUENCE { 1208 capwapDot11WlanBindBssIfIndex InterfaceIndex, 1209 capwapDot11WlanBindBssRowStatus RowStatus 1210 } 1212 T10. What does 'Bits are exclusive for each other for a specific 1213 WLAN Id' mean for capwapDot11WlanTunnelMode? That only one tunnel 1214 mode can be configured (one bit set)? I assume this does not include 1215 the bit unused(0). What happens if the manager sets more than one 1216 bit, ore no bit, or unused(0) - how does the agent behave in this 1217 case? 1218 ----------------------------------------------------------------- 1220 1) Yes, unused(0) is removed. 1222 2) The description is updated with: 1224 Bits are exclusive with each other for a specific WLAN Id, and only 1225 one tunnel mode could be configured. If operator set more than one 1226 bit, the value of the Response-PDU's error-status field is set to 1227 `wrongValue', and the value of its error-index field is set to the 1228 index of the failed variable binding." 1230 T11. What is the persistency of the capwapDot11WlanTunnelMode at 1231 agent reboot? Is the whole table persistent at agent reboot? 1233 ----------------------------------------------------------------- 1235 Yes, it should be whole table persistent instead of previous 1236 statement "Values of all read-create objects in this table are 1237 persistent at restart/reboot." 1239 T12. I do not understand how does row creation in the 1240 capwapDot11WlanBindTable work. It is indexed by ifIndex and 1241 capwapDot11WlanId. The only visible object in this table except 1242 RowStatus is capwapDot11WlanBssIfIndex which is read-only and the 1243 description says that 'it is the same interface as identified by the 1244 same value of ifIndex. But the manager cannot read its value until 1245 the row exists. How does the manager know its value in order to 1246 create the row in the table? 1248 ---------------------------------------------------------------- 1250 The old description would lead to misunderstanding when it says "The 1251 interface identified by a particular value of this index is the same 1252 interface as identified by the same value of ifIndex". In fact, the 1253 ifIndex here is not a ifIndex in the INDEX { ifIndex (it is a 1254 "Wireless virtual radio interface), capwapDot11WlanId }, while it is 1255 a "WLAN "WLAN BSS Interface". 1257 To clarify it, the following text is added to the description of 1258 capwapDot11WlanBindBssIfIndex: 1260 The ifIndex here is for an interface of 'WLAN BSS Interface'. For a 1261 WLAN configuration on a radio, an interface of 'WLAN BSS Interface' 1262 will correspond to it. The creation operation of a row object on the 1263 capwapDot11WlanBindTable would trigger AC system to automatically 1264 create a 'WLAN BSS Interface' and it is identified by ifIndex. It 1265 does not require operator to manually create a 'WLAN BSS Interface'. 1267 For the table of capwapDot11WlanBindTable, the description is updated 1268 with the following text: 1270 A table of objects that configure which WLAN (identified by 1271 capwapDot11WlanId) will be provided on which 'WTP Virtual Radio 1272 Interface' (identified by ifIndex) Also, display and control the 1273 mapping relationship between interface of 'WTP Virtual Radio 1274 Interface' interface and interface of 'WLAN BSS Interface'. The PHY 1275 address for interface of 'WTP Virtual Radio Interface' ifType will be 1276 base BSSID address for PHY radio. 1278 Values of all bjects in this table are persistent at restart/reboot. 1280 For the table of capwapDot11WlanBindEntry, the description is updated 1281 with the following text: 1283 A set of objects that display the mapping relationship between 1284 interface of 'WTP Virtual Radio Interface' and interface of 'WLAN BSS 1285 Interface'. The Index object ifIndex is a ifIndex of a 'WTP Virtual 1286 Radio Interface'. 1288 T13. Is the capwapDot11WlanBindTable persistent at agent reboot? 1290 ----------------------------------------------------------------- 1292 Yes, The whole table is persistent at restart/reboot. 1294 E1. Not all acronyms are expanded at first occurrence - e.g. WTP 1296 ----------------------------------------------------------------- 1298 The Terminology section is updated with more Terminology such as 1299 CAPWAP,WTP,AC, Wireless Binding,Split and Local MAC and so on. 1301 E2. Please avoid using the construct 'the MIBs' (e.g. in Section 5). 1302 s/the MIBs/the MIB modules/ 1304 ----------------------------------------------------------------- 1306 use either "MIB module" or "MIB modules" in the document 1308 E3. There is no need to include sections 6.1 and 6.2, they provide 1309 no new or specific information for this MIB module. 1311 ---------------------------------------------------------------- 1313 Yes, they were removed 1314 E4. I suggest for this document to be verified by a native English 1315 speaker for English spelling and grammar. 1317 E5. ifIndex, ifDescr, ifName, ifAlias in the WLAN Service Interface 1318 and WLAN BSS Interface table contain no specific information, I 1319 suggest to just mention that they are used as per RFC 2863 1321 -------------------------------------------------------------- 1323 The section for interpration of specific MIB objects in the iftable 1324 was removed in the new version. Reader could refer to RFC2863 1326 Other changes made by authors: 1327 1) reorganized the section of overview, and divided it into the 1328 following sub sections: 1329 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1330 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5 1331 5.2. Mechanism of Reusing Wireless Binding MIB Module . . . . . 5 1333 2) Update some words in the section of" Example of CAPWAP-DOT11-MIB 1334 Module Usage, especially explain how interfaces of 1335 "WLAN service Interface" and "WLAN BSS Interface" are created. 1337 3) Modify the value scope of CapwapDot11WlanIdTC from (1, 16) to 1338 (1, 512), and description of it. 1340 Authors' Addresses 1342 Yang Shi (editor) 1343 H3C Tech. Co., Ltd 1344 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 1345 Beijing 1346 China(100085) 1348 Phone: +86 010 82775276 1349 EMail: young@h3c.com 1351 David Perkins (editor) 1352 SNMPinfo 1353 288 Quailbrook Ct San Carlos, 1354 CA 94070 1355 USA 1357 Phone: +1 408 394-8702 1358 EMail: dperkins@snmpinfo.com 1359 Chris Elliott (editor) 1360 Cisco Systems, Inc. 1361 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 1362 27709 1363 USA 1365 Phone: +1 919-392-2146 1366 EMail: chelliot@cisco.com 1368 Yong Zhang (editor) 1369 Fortinet, Inc. 1370 1090 Kifer Road 1371 Sunnyvale, CA 94086 1372 USA 1374 EMail: yzhang@fortinet.com