idnits 2.17.1 draft-ietf-capwap-802dot11-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1000. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1011. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1018. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1024. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == 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 (June 28, 2008) is 5780 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) ** Downref: Normative reference to an Informational draft: draft-ietf-capwap-base-mib (ref. 'I-D.ietf-capwap-base-mib') == Outdated reference: A later version (-15) exists of draft-ietf-capwap-protocol-specification-10 == Outdated reference: A later version (-12) exists of draft-ietf-capwap-protocol-binding-ieee80211-06 Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 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: December 30, 2008 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 P. Puneet, Ed. 9 Broadcom, Inc. 10 June 28, 2008 12 CAPWAP Protocol Binding MIB for IEEE 802.11 13 draft-ietf-capwap-802dot11-mib-00 15 Status of This Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on December 30, 2008. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols. In particular, it 44 describes managed objects for modeling the Control And Provisioning 45 of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless 46 binding. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. The Internet-Standard Management Framework . . . . . . . . . . 3 52 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 56 6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 57 6.2. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5 58 6.3. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5 59 6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 5 60 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 61 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 6 62 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6 63 7.3. Relationship to CAPWAP Base MIB . . . . . . . . . . . . . 8 64 7.4. Relationship to IEEE 802.11 MIB . . . . . . . . . . . . . 8 65 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 66 8. Example of CAPWAP-DOT11-MIB Usage . . . . . . . . . . . . . . 8 67 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 68 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 69 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 70 11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 19 71 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 19 72 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 73 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 74 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 75 14.1. Normative References . . . . . . . . . . . . . . . . . . . 19 76 14.2. Informative References . . . . . . . . . . . . . . . . . . 21 78 1. Introduction 80 Current work is under way in the IETF to specify the CAPWAP Protocol 81 [I-D.ietf-capwap-protocol-specification], which enables an Access 82 Controller (AC) to manage a collection of Wireless Termination Points 83 (WTPs). CAPWAP supports the use of various wireless technologies by 84 the WTPs, with one being specified in the 802.11 binding document 85 [I-D.ietf-capwap-protocol-binding-ieee80211]. 87 This document defines a MIB module that can be used to manage CAPWAP 88 implementations for IEEE 802.11 wireless binding. This MIB module 89 covers both configuration for WLAN and a way to reuse IEEE 802.11 MIB 90 standard in series defined by IEEE 802.11 WG. 92 2. The Internet-Standard Management Framework 94 For a detailed overview of the documents that describe the current 95 Internet-Standard Management Framework, please refer to section 7 of 96 RFC 3410 [RFC3410]. 98 Managed objects are accessed via a virtual information store, termed 99 the Management Information Base or MIB. MIB objects are generally 100 accessed through the Simple Network Management Protocol (SNMP). 101 Objects in the MIB are defined using the mechanisms defined in the 102 Structure of Management Information (SMI). This memo specifies a MIB 103 module that is compliant to the SMIv2, which is described in STD 58, 104 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 105 [RFC2580]. 107 3. Terminology 109 This document uses terminology from the document describing the 110 CAPWAP Protocol specification for 802.11 binding 111 [I-D.ietf-capwap-protocol-binding-ieee80211]. Besides terminology 112 defined in the IEEE 802.11 standard and CAPWAP specification, an 113 important conception is WLAN service. In the document, WLAN service 114 refers to a logical component instantiated on a WTP device. A single 115 physical WTP may operate a number of WLAN services, and the way is 116 called as virtual AP. Each Basic Service Set Identifier (BSSID) and 117 its constituent wireless terminal radios is denoted as a distinct 118 WLAN on a physical WTP. To support physical WTP with multiple WLANs 119 is an important feature for CAPWAP protocol's 802.11 binding, and it 120 is also for MIB design. 122 4. Conventions 124 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 125 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 126 document are to be interpreted as described in RFC 2119 [RFC2119]. 128 5. Overview 130 The [I-D.ietf-capwap-base-mib] provides a way to configure and manage 131 WTP and radio objects through SNMP. It's a basis for manage and 132 control a IEEE 802.11 binding. 134 The CAPWAP Protocol's IEEE 802.11 binding MIB module (CAPWAP-DOT11- 135 MIB) provides a way to configure WLAN service, also could easily 136 reuse current and future IEEE 802.11 MIB standards. 138 It is designed to satisfy the following requirements and constraints: 140 - The MIB module could easily reuse current and future IEEE 802.11 141 MIB standard in series defined by IEEE 802.11 WG, and not require to 142 redefine them. 144 - From AC to centrally manage and configure WLAN service; 146 - Operators could configure MAC type and tunnel mode for a specific 147 WLAN service by SNMP; 149 - The MIB module supports virtual AP; 151 Before coming to details of CAPWAP-MIB-DOT11 module, it will 152 introduce how it is able to reuse IEEE MIB standard. As centralized 153 Wireless architecture, the operator has to prepare configurations for 154 each wireless at AC side before WTPs connect to AC. Under 155 centralized Wireless architectures, according to [I-D.ietf-capwap- 156 protocol-specification], each WLAN service is identified by WLAN Id. 157 According to IEEE 802.11 MIB standards, the MIB tables such as 158 Dot11AuthenticationAlgorithmsTable are able to support wireless 159 configuration (such as authentication algorithm), and these tables 160 use ifIndex as index. A Wireless service could be abstracted as an 161 interface on the AC side, and which could be identified by ifIndex. 162 On the AC side, the MIB table CapwapDot11WirelessConfigTable will 163 indicate the mapping relation between a "WLAN Id" and ifIndex of a 164 "WLAN Service Interface". With ifIndex of a "WLAN Service 165 Interface", system is able to reuse IEEE MIBs. 167 6. Structure of the MIB Module 169 6.1. Textual Conventions 171 The following textual conventions are defined: 173 CapwapDot11WLANId ::= TEXTUAL-CONVENTION 174 STATUS current 175 DESCRIPTION 176 "Represents the TC for WLAN Id." 177 SYNTAX Unsigned32 179 6.2. The capwapDot11Objects Subtree 181 The subtree provides information for configuration parameters of WLAN 182 service and binding WLAN service to a specific radio. 184 6.3. The capwapDot11Conformance Subtree 186 The subtree provides conformance information of MIB objects. 188 6.4. Brief Description of MIB Objects 190 The MIB objects were derived from the CAPWAP protocol 802.11 binding 191 document [I-D.ietf-capwap-protocol-binding-ieee80211]. 193 1) capwapDot11WLANConfigTable 195 The table is used for providing configuration such as MAC type and so 196 on for WLANs. For a specific WLAN service which is identified by 197 capwapDot11WLANId, an interface of 'WLAN Service Interface' ifType 198 will be created. By the ifIndex of interface, it provides a way to 199 reuse IEEE 802.11 MIB. For example, according to 200 [I-D.ietf-capwap-protocol-binding-ieee80211], there is a TLV of 201 authentication Type for a WLAN. In IEEE 802.11 MIB, the MIB object 202 dot11AuthenticationAlgorithm in the 203 dot11AuthenticationAlgorithmsTable is corresponding to Auth Type TLV. 204 Considering both capwapDot11WLANConfigTable and 205 dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP- 206 DOT11-MIB are able to easily reuse dot11AuthenticationAlgorithm 207 object in IEEE 802.11 MIB. It is same for other IEEE 802.11 MIBs' 208 reuse. 210 2) capwapDot11WLANBindTable 212 The table provides a way to bind WLAN service to a radio, then 213 support virtual AP. The binding operation will dynamically create 214 "WLAN BSS Interface", and this logical interface is used for data 215 forwarding function. 217 7. Relationship to Other MIB Modules 218 7.1. Relationship to the SNMPv2-MIB 220 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 221 mandatory for all systems, and the objects apply to the entity as a 222 whole. The 'system' group provides identification of the management 223 entity and certain other system-wide data. The CAPWAP-DOT11-MIB does 224 not duplicate those objects. 226 7.2. Relationship to the IF-MIB 228 The Interfaces Group [RFC2863] defines generic managed objects for 229 managing interfaces. This memo contains the media-specific 230 extensions to the Interfaces Group for managing WLAN service that are 231 modeled as interfaces. 233 For each WLAN, it will have a logical interface of 'WLAN Service 234 Interface' responding to it at AC side. The interface SHOULD be 235 modeled as an ifEntry and provide appropriate interface information. 237 To provide data forwarding service, system will dynamically create 238 logical interface of 'WLAN BSS Interface'. The interface SHOULD be 239 modeled as an ifEntry and provide appropriate interface information. 241 Some specific interpretations of ifTable for CAPWAP-DOT11-MIB are as 242 follow. 244 1) WLAN Service Interface 246 Object Use for the CAPWAP-DOT11-MIB 248 ifIndex Each interface of 'WLAN Service Interface' type 249 maybe be represented by an ifEntry. 251 ifDescr Description of the interface of 'WLAN Service 252 Interface' type. 254 ifType IANAifType of "WLAN Service Interface". 256 ifName Textual name (unique on this system) of the interface 257 or an octet string of zero length. 259 ifAlias The nonvolatile 'alias' name for the interface, as 260 specified by a network manager. 262 ifPhysAddress Unused. 264 ifAdminStatus This variable indicates the administrator's intent as 265 to whether PHY should be enabled, disabled. Could be 266 always enabled. 268 ifOperStatus This value reflects the actual or operational status 269 of interface. Could be always enabled. 270 Also see [RFC2863]. 272 ifLastChange The value of sysUpTime at the time the interface 273 entered its current operational state. 274 Also see [RFC2863]. 276 The other objects such as ifInOctets, ifOutOctets, ifInErrors, 277 ifOutErrors are unused. 279 2) WLAN BSS Interface 281 Object Use for the CAPWAP-DOT11-MIB 283 ifIndex Each interface of 'WLAN BSS Interface' type maybe 284 be represented by an ifEntry. 286 ifDescr Description of the interface of 'WLAN BSS Interface' 287 type. 289 ifType IANAifType of "WLAN BSS Interface". 291 ifName Textual name (unique on this system) of the interface 292 or an octet string of zero length. 294 ifAlias The nonvolatile 'alias' name for the interface, as 295 specified by a network manager. 297 ifPhysAddress The physical address of interface. 298 One possible method is for the WTP to assign the 299 address for 'WLAN BSS Interface' using the following 300 algorithm: base BSSID address + WLAN ID. 302 ifAdminStatus This variable indicates the administrator's intent as 303 to whether PHY should be enabled, disabled, or 304 running in some diagnostic testing mode on this 305 interface. 306 Also see [RFC2863]. 308 ifOperStatus This value reflects the actual or operational status 309 of interface. 310 Also see [RFC2863]. 312 ifLastChange The value of sysUpTime at the time the interface 313 entered its current operational state. 315 Also see [RFC2863]. 317 ifInOctets The number of octets received as 802.11 frames. 319 ifOutOctets The number of octets transmitted as 802.11 320 frames. 322 ifInErrors The number of 802.11 frames dropped due to 323 uncorrectable errors. 325 ifInUnknownProtos 326 The number of received 802.11 frame discarded during 327 frame header validation, including frames with 328 unrecognized label values. 330 ifOutErrors See [RFC2863]. 332 7.3. Relationship to CAPWAP Base MIB 334 The CAPWAP Base MIB provides a way to manage and control WTP and 335 radio objects. Based on it, CAPWAP-DOT11-MIB provides more 336 information from WLAN service perspective. 338 7.4. Relationship to IEEE 802.11 MIB 340 Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface' 341 ifType, the MIB module is able to reuse MIB objects in the IEEE 342 802.11 MIB. 344 7.5. MIB modules required for IMPORTS 346 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 347 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and 348 CAPWAP-MIB [I-D.ietf-capwap-base-mib]. 350 8. Example of CAPWAP-DOT11-MIB Usage 352 Combining the example in the [I-D.ietf-capwap-base-mib], 353 here give a whole example for configuration and management of WTP, 354 radio and WLAN object. 356 1) Identify each PHY radio by "WTP Virtual Radio Interface" 357 According to [I-D.ietf-capwap-protocol-specification], each radio on 358 a WTP will be identified by a radio Id. Each WTP could be identified 359 by its serial number. 360 When configuration for a WTP is prepared before a WTP connects to AC, 361 the following information is available in the CapwapRadioBindTable. 362 In CapwapRadioBindTable 363 { 364 capwapWTPId = 12345678 365 capwapRadioId = 1 366 capwapWTPVirtualRadioifIndex = 10, 367 capwapWirelessBinding = dot11(2), 368 } 369 Suppose WTP's serial number is 12345678, and first PHY radio's id 370 is 1. At AC side, the ifIndex of "WTP Virtual Radio Interface" is 371 10 which represents the PHY radio 1. 372 By the mechanism of "WTP Virtual Radio Interface", it seemed that WTP 373 PHY radios are located at AC side. 374 The interface of "WTP Virtual Radio Interface" is modeled by ifTable. 375 In ifTable 376 { 377 ifIndex = 10, 378 ifDescr = "WTP Virtual Radio Interface", 379 ifType = IANAifType of "WTP Virtual Radio 380 Interface", 381 ifMtu = 0, 382 ifSpeed = 0, 383 ifPhysAddress = 0.0.0.0.0.0, 384 ifAdminStatus = true, 385 ifOperStatus = false, 386 ifLastChange = 0, 387 ifInOctets = 0, 388 ifInUcastPkts = 0, 389 ifInDiscards = 0, 390 ifInErrors = 0, 391 ifInUnknownProtos = 0, 392 ifOutOctets = 0, 393 ifOutUcastPkts = 0, 394 ifOutDiscards = 0, 395 ifOutErrors = 0, 396 } 398 2) Configure IEEE 802.11 wireless binding parameters for "WTP Virtual 399 Radio Interface" 400 It will be done at the AC side through IEEE 802.11 MIB. 401 For example, to configure parameter for "WTP Virtual Radio Interface" 402 by IEEE 802.11 Dot11OperationTable. 403 In Dot11OperationTable 404 { 405 ifIndex = 10, 406 dot11MACAddress = 0.0.0.0.0.0, 407 dot11RTSThreshold = 2347, 408 dot11ShortRetryLimit = 7, 409 dot11LongRetryLimit = 4, 410 dot11FragmentationThreshold = 256, 411 dot11MaxTransmitMSDULifetime = 512, 412 dot11MaxReceiveLifetime = 512, 413 dot11ManufacturerID = "capwap", 414 dot11ProductID = "capwap" 415 } 416 In the example, it supposes ifIndex of a "WTP Virtual Radio 417 Interface" is 10. 419 3) Configure WLAN service 420 WLAN service configuration will be done through CAPWAP-DOT11-MIB 421 and IEEE 802.11 MIB. 422 First step is to create a "WLAN Service Interface" through 423 CAPWAP-DOT11-MIB at AC side. 424 In CapwapDot11WLANConfigTable 425 { 426 capwapDot11WLANId = 1, 427 capwapDot11WLANServiceIfIndex = 20, 428 capwapWTPMACType = splitMAC(2), 429 capwapWTPTunnelMode = dot3Tunnel, 430 capwapDot11WLANConfigRowStatus = create 431 } 432 Here supposes to configure a WLAN service which is identified by 433 capwapDot11WLANId 1. A "WLAN Service Interface" is created for it 434 and identified by ifIndex 20. 435 Corresponding to "WLAN Service Interface", it SHOULD be modeled as an 436 ifEntry at AC side and provide appropriate interface information. 437 In ifTable 438 { 439 ifIndex = 20, 440 ifDescr = "WLAN Service Interface", 441 ifType = IANAifType of "WLAN Service Interface", 442 ifMtu = 0, 443 ifSpeed = 0, 444 ifPhysAddress = 0.0.0.0.0.0, 445 ifAdminStatus = true, 446 ifOperStatus = true, 447 ifLastChange = 0, 448 ifInOctets = 0, 449 ifInUcastPkts = 0, 450 ifInDiscards = 0, 451 ifInErrors = 0, 452 ifInUnknownProtos = 0, 453 ifOutOctets = 0, 454 ifOutUcastPkts = 0, 455 ifOutDiscards = 0, 456 ifOutErrors = 0 457 } 458 Second step is to configure WLAN parameters of "WLAN Service 459 Interface" through IEEE 802.11 MIB at AC side. 460 In Dot11AuthenticationAlgorithmsTable 461 { 463 ifIndex = 20, 464 dot11AuthenticationAlgorithmsIndex = 1, 465 dot11AuthenticationAlgorithm = Shared Key, 466 dot11AuthenticationAlgorithmsEnable = true 467 } 468 Here ifIndex 20 is for interface of "WLAN Service Interface" 469 ifType. Suppose the index of authentication algorithm is 1. 471 4) Bind WLAN service to WTP radio 472 At AC side, through CapwapDot11WLANBindTable, it configures which 473 WLAN service (identified by capwapDot11WLANId) will be provided on 474 which radio (identified by ifIndex). Suppose capwapWTPMACType of WLAN 475 service is splitMAC(2), the interface of 'WLAN BSS Interface' 476 will be created at AC side. 477 The AC will use it for split data forwarding. Here supposes ifIndex 478 of interface in 'WLAN BSS Interface' ifType is 30. 479 In CapwapDot11WLANBindTable 480 { 481 ifIndex = 10, 482 capwapDot11WLANId = 1, 483 capwapDot11WLANBSSIfIndex = 30, 484 capwapDot11WLANBSSRowStatus = create 485 } 487 5) WTP reports its current configuration status 488 After join phase and before WTP get configuration from AC, it will 489 report its current configuration status to AC through configuration 490 status message. The MIB data will be updated at AC side. 491 For example, for the 802.11 binding, WTP will update data in the 492 ifTable and IEEE 802.11 MIB so on according to message content. 493 As a example for ifIndex 10 (which identify an interface of 494 "WLAN Virtual Radio Interface" ifType), its ifOperStatus in ifTable 495 will be updated with current radio operational status in the message. 497 6) Query WTP and radio statistics data 498 After WTPs come to run status, administrator could query WTP and 499 radio statistics data through CAPWAP-MIB and CAPWAP-DOT11-MIB. 500 For example, through dot11CountersTable in the IEEE 802.11 MIB, 501 administrator could query counter data for radio which is identified 502 by ifIndex of a "WLAN Virtual Radio Interface". 504 7) Query other statistics data 505 For example, administrator could query the configuration of 506 WLAN service through Dot11AuthenticationAlgorithmsTable. 508 Query statistic data of 'WLAN BSS Interface' through ifTable; 510 9. Definitions 512 CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN 514 IMPORTS 515 RowStatus, TEXTUAL-CONVENTION 516 FROM SNMPv2-TC 517 OBJECT-GROUP, MODULE-COMPLIANCE 518 FROM SNMPv2-CONF 519 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 520 FROM SNMPv2-SMI 521 ifIndex, InterfaceIndex 522 FROM IF-MIB 523 CapwapWTPMACType, CapwapWTPTunnelMode 524 FROM CAPWAP-MIB; 526 capwapDot11MIB MODULE-IDENTITY 527 LAST-UPDATED "200806280000Z" -- June 28, 2008 528 ORGANIZATION "IETF Control And Provisioning of Wireless Access 529 Points (CAPWAP) Working Group 530 http://www.ietf.org/html.charters/capwap-charter.html" 531 CONTACT-INFO 532 "General Discussion: capwap@frascone.com 534 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 536 Yang Shi 537 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 538 District,Beijing,China(100085) 539 Email: young@h3c.com 541 David T. Perkins 542 228 Bayview Dr 543 San Carlos, CA 94070 544 USA 545 Phone: +1 408 394-8702 546 Email: dperkins@snmpinfo.com 548 Chris Elliott 549 Cisco Systems, Inc. 550 7025 Kit Creek Rd., P.O. Box 14987 551 Research Triangle Park 27709 552 USA 553 Phone: +1 919-392-2146 554 Email: chelliot@cisco.com 555 Puneet Agarwal 556 BroadCom, Inc. 557 USA 558 Email: pagarwal@broadcom.com" 560 DESCRIPTION 561 "Copyright (C) 2008 The Internet Society. This version of 562 the MIB module is part of RFC xxx; see the RFC itself 563 for full legal notices. 565 This MIB module contains managed object definitions for 566 the IEEE 802.11 bindings for the CAPWAP Protocol." 567 REVISION "200806280000Z" 568 DESCRIPTION 569 "Initial version, published as RFC xxx" 570 ::= { mib-2 xxx } 572 -- Textual conventions 574 CapwapDot11WLANId ::= TEXTUAL-CONVENTION 575 STATUS current 576 DESCRIPTION 577 "Represents the TC for WLAN Id." 578 SYNTAX Unsigned32 580 -- Top level components of this MIB 582 -- Tables, Scalars 583 capwapDot11Objects OBJECT IDENTIFIER 584 ::= { capwapDot11MIB 1 } 585 -- Conformance 586 capwapDot11Conformance OBJECT IDENTIFIER 587 ::= { capwapDot11MIB 2 } 589 -- capwapDot11WLANConfigTable Table 591 capwapDot11WLANConfigTable OBJECT-TYPE 592 SYNTAX SEQUENCE OF CapwapDot11WLANConfigEntry 593 MAX-ACCESS not-accessible 594 STATUS current 595 DESCRIPTION 596 "A table of objects that display and control the WLAN 597 service." 598 ::= { capwapDot11Objects 1 } 600 capwapDot11WLANConfigEntry OBJECT-TYPE 601 SYNTAX CapwapDot11WLANConfigEntry 602 MAX-ACCESS not-accessible 603 STATUS current 604 DESCRIPTION 605 "A set of objects that display and control the WLAN 606 service." 607 INDEX { capwapDot11WLANId } 608 ::= { capwapDot11WLANConfigTable 1 } 610 CapwapDot11WLANConfigEntry ::= 611 SEQUENCE { 612 capwapDot11WLANId CapwapDot11WLANId, 613 capwapDot11WLANServiceIfIndex InterfaceIndex, 614 capwapWTPMACType CapwapWTPMACType, 615 capwapWTPTunnelMode CapwapWTPTunnelMode, 616 capwapDot11WLANConfigRowStatus RowStatus 617 } 619 capwapDot11WLANId OBJECT-TYPE 620 SYNTAX CapwapDot11WLANId 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "Represents the WLAN id for a WLAN which has a 625 capwapDot11WLANServiceIfIndex interface corresponding to it." 626 REFERENCE 627 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 628 RFC xxx." 629 ::= { capwapDot11WLANConfigEntry 1 } 631 capwapDot11WLANServiceIfIndex OBJECT-TYPE 632 SYNTAX InterfaceIndex 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "Represents the ifIndex for an interface of 'WLAN Service 637 Interface' ifType. 638 Before WTPs connect to AC and get configuration, administrator 639 will prepare configuration for them. For a specific WLAN 640 service, a logical interface of 'WLAN Service Interface' ifType 641 will be created, and administrator could configure WLAN 642 parameter through it. For example, according to IEEE 802.11 643 '6.1. IEEE 802.11 Add WLAN' in the 644 [I-D.ietf-capwap-protocol-binding-ieee80211], administrator 645 could configure specify Auth Type for a WLAN. The 'WLAN Service 646 Interface' provides a way to uniquely identify each WLAN by 647 logical at AC side. As most MIBs use ifIndex to identify an 648 interface for configuration and statistic data, for example, 649 dot11AuthenticationAlgorithmsTable in 802.11 MIB use ifIndex 650 as index, and dot11AuthenticationAlgorithm object is for 651 Auth Type mentioned in the CAPWAP '6.1. IEEE 802.11 Add WLAN', 652 With the way of 'WLAN Service Interface', it will easily 653 reuse MIB table like dot11AuthenticationAlgorithmsTable, while 654 only care for other configurations like capwapWTPTunnelMode." 655 ::= { capwapDot11WLANConfigEntry 2 } 657 capwapWTPMACType OBJECT-TYPE 658 SYNTAX CapwapWTPMACType 659 MAX-ACCESS read-create 660 STATUS current 661 DESCRIPTION 662 "Represents whether the WTP should run the WLAN in 663 Local or Split MAC modes." 664 REFERENCE 665 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 666 RFC xxx." 667 ::= { capwapDot11WLANConfigEntry 3 } 669 capwapWTPTunnelMode OBJECT-TYPE 670 SYNTAX CapwapWTPTunnelMode 671 MAX-ACCESS read-create 672 STATUS current 673 DESCRIPTION 674 "Represents the frame tunneling type to be used for 802.11 data 675 frames from all stations associated with the WLAN." 676 REFERENCE 677 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 678 RFC xxx." 679 ::= { capwapDot11WLANConfigEntry 4 } 681 capwapDot11WLANConfigRowStatus OBJECT-TYPE 682 SYNTAX RowStatus 683 MAX-ACCESS read-create 684 STATUS current 685 DESCRIPTION 686 "This variable is used to create, modify, and/or delete a row in 687 this table." 688 ::= { capwapDot11WLANConfigEntry 5 } 690 -- End of capwapDot11WLANConfigTable Table 692 -- capwapDot11WLANBindTable Table 693 capwapDot11WLANBindTable OBJECT-TYPE 694 SYNTAX SEQUENCE OF CapwapDot11WLANBindEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "A table of objects that display the mapping relationship 699 between interface of 'WTP Virtual Radio Interface' and 700 interface of 'WLAN BSS Interface'. 701 The PHY address for interface of 'WTP Virtual Radio 702 Interface' ifType will be base BSSID address for PHY 703 radio." 704 REFERENCE 705 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 706 RFC xxx." 707 ::= { capwapDot11Objects 2 } 709 capwapDot11WLANBindEntry OBJECT-TYPE 710 SYNTAX CapwapDot11WLANBindEntry 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "A set of objects that display the mapping relationship 715 between interface of 'WTP Virtual Radio Interface' and 716 interface of 'WLAN BSS Interface'." 717 INDEX { ifIndex, capwapDot11WLANId } 718 ::= { capwapDot11WLANBindTable 1 } 720 CapwapDot11WLANBindEntry ::= 721 SEQUENCE { 722 capwapDot11WLANBSSIfIndex InterfaceIndex, 723 capwapDot11WLANBSSRowStatus RowStatus 724 } 726 capwapDot11WLANBSSIfIndex OBJECT-TYPE 727 SYNTAX InterfaceIndex 728 MAX-ACCESS read-only 729 STATUS current 730 DESCRIPTION 731 "Represents a ifIndex for an interface of 732 'WLAN BSS Interface' ifType. Each capwapDot11WLANBSSIfIndex will 733 corresponding to a WLAN service on the PHY radio which is 734 identified by ifIndex. 735 When CapwapWTPMACType is localMAC(1), the interface of 736 'WLAN BSS Interface' will be created at AP side. 737 The AP will use interface for local data forwarding. 738 When CapwapWTPMACType is splitMAC(2), the interface of 739 'WLAN BSS Interface' will be created at AC side. 740 The AC will use it for split data forwarding. 741 The PHY address for capwapDot11WLANBSSIfIndex is BSSID. 742 While manufacturers are free to assign BSSIDs using any 743 arbitrary mechanism, it is advised that where possible the 744 BSSIDs are assigned as a contiguous block. 745 When assigned as a block, implementations can still assign 746 any of the available BSSIDs to any WLAN. One possible method 747 is for the WTP to assign the address using the following 748 algorithm: base BSSID address + WLAN ID." 749 REFERENCE 750 "Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11, 751 RFC xxx." 752 ::= { capwapDot11WLANBindEntry 1 } 754 capwapDot11WLANBSSRowStatus OBJECT-TYPE 755 SYNTAX RowStatus 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "This variable is used to create, modify, and/or delete a row in 760 this table." 761 ::= { capwapDot11WLANBindEntry 2 } 763 -- Module compliance 765 capwapDot11Groups OBJECT IDENTIFIER 766 ::= { capwapDot11Conformance 1 } 768 capwapDot11Compliances OBJECT IDENTIFIER 769 ::= { capwapDot11Conformance 2 } 771 capwapDot11Compliance MODULE-COMPLIANCE 772 STATUS current 773 DESCRIPTION 774 "Describes the requirements for conformance to the 775 CAPWAP Dot11 MIB." 777 MODULE -- this module 778 MANDATORY-GROUPS { capwapDot11WLANConfigGroup, 779 capwapDot11WLANBindGroup } 780 ::= { capwapDot11Compliances 1 } 782 capwapDot11WLANConfigGroup OBJECT-GROUP 783 OBJECTS { 784 capwapDot11WLANId, 785 capwapDot11WLANServiceIfIndex, 786 capwapWTPMACType, 787 capwapWTPTunnelMode, 788 capwapDot11WLANConfigRowStatus 789 } 790 STATUS current 791 DESCRIPTION 792 "The collection of objects which are used to configure 793 property of WLAN." 794 ::= { capwapDot11Groups 1 } 796 capwapDot11WLANBindGroup OBJECT-GROUP 797 OBJECTS { 798 capwapDot11WLANBSSIfIndex, 799 capwapDot11WLANBSSRowStatus 800 } 801 STATUS current 802 DESCRIPTION 803 "The collection of objects which are used to configure 804 WLAN BSS." 805 ::= { capwapDot11Groups 2 } 807 END 809 10. Security Considerations 811 There are a number of management objects defined in this MIB module 812 with a MAX-ACCESS clause of read-write and/or read-create. Such 813 objects may be considered sensitive or vulnerable in some network 814 environments. The support for SET operations in a non-secure 815 environment without proper protection can have a negative effect on 816 network operations. These are the tables and objects and their 817 sensitivity/vulnerability: 819 o - Unauthorized changes to the capwapDot11WLANConfigTable and 820 capwapDot11WLANBindTable may disrupt allocation of resources in 821 the network, also change the behavior of WLAN system such as MAC 822 type. 824 SNMP versions prior to SNMPv3 did not include adequate security. 825 Even if the network itself is secure (for example by using IPSec), 826 even then, there is no control as to who on the secure network is 827 allowed to access and GET/SET (read/change/create/delete) the objects 828 in this MIB module. 830 It is RECOMMENDED that implementers consider the security features as 831 provided by the SNMPv3 framework (see [RFC3410], section 8), 832 including full support for the SNMPv3 cryptographic mechanisms (for 833 authentication and privacy). 835 Further, deployment of SNMP versions prior to SNMPv3 is NOT 836 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 837 enable cryptographic security. It is then a customer/operator 838 responsibility to ensure that the SNMP entity giving access to an 839 instance of this MIB module is properly configured to give access to 840 the objects only to those principals (users) that have legitimate 841 rights to indeed GET or SET (change/create/delete) them. 843 11. IANA Considerations 845 11.1. IANA Considerations for CAPWAP-DOT11-MIB 847 The MIB module in this document uses the following IANA-assigned 848 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 850 Descriptor OBJECT IDENTIFIER value 851 ---------- ----------------------- 853 capwapDot11MIB { mib-2 XXX } 855 11.2. IANA Considerations for ifType 857 Require IANA to assign a ifType for 'WLAN Service Interface' type. 859 Require IANA to assign a ifType for 'WLAN BSS Interface' type. 861 12. Contributors 863 This MIB is based on contributions from Long Gao. 865 13. Acknowledgements 867 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 868 Dutta, Yujin Zhao, Haitao Zhang. 870 14. References 872 14.1. Normative References 874 [RFC2119] Bradner, S., "Key words 875 for use in RFCs to 876 Indicate Requirement 877 Levels", BCP 14, 878 RFC 2119, March 1997. 880 [RFC2578] McCloghrie, K., Ed., 881 Perkins, D., Ed., and 882 J. Schoenwaelder, Ed., 883 "Structure of 884 Management Information 885 Version 2 (SMIv2)", 886 STD 58, RFC 2578, 887 April 1999. 889 [RFC2579] McCloghrie, K., Ed., 890 Perkins, D., Ed., and 891 J. Schoenwaelder, Ed., 892 "Textual Conventions 893 for SMIv2", STD 58, 894 RFC 2579, April 1999. 896 [RFC2580] McCloghrie, K., 897 Perkins, D., and J. 898 Schoenwaelder, 899 "Conformance Statements 900 for SMIv2", STD 58, 901 RFC 2580, April 1999. 903 [RFC2863] McCloghrie, K. and F. 904 Kastenholz, "The 905 Interfaces Group MIB", 906 RFC 2863, June 2000. 908 [RFC3418] Presuhn, R., 909 "Management Information 910 Base (MIB) for the 911 Simple Network 912 Management Protocol 913 (SNMP)", STD 62, 914 RFC 3418, 915 December 2002. 917 [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., 918 Elliott, C., and P. 919 Agarwal, "CAPWAP 920 Protocol Base MIB", dra 921 ft-ietf-capwap-base- 922 mib-00 (work in 923 progress), May 2008. 925 [I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP 926 Protocol 927 Specification", draft- 928 ietf-capwap-protocol- 929 specification-10 (work 930 in progress), 931 March 2008. 933 [I-D.ietf-capwap-protocol-binding-ieee80211] Calhoun, P., "CAPWAP 934 Protocol Binding for 935 IEEE 802.11", draft- 936 ietf-capwap-protocol- 937 binding-ieee80211-06 938 (work in progress), 939 February 2008. 941 14.2. Informative References 943 [RFC3410] Case, J., Mundy, R., 944 Partain, D., and B. 945 Stewart, "Introduction 946 and Applicability 947 Statements for 948 Internet-Standard 949 Management Framework", 950 RFC 3410, 951 December 2002. 953 Authors' Addresses 955 Yang Shi (editor) 956 H3C Tech. Co., Ltd 957 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 958 Beijing 959 China(100085) 961 Phone: +86 010 82775276 962 EMail: young@h3c.com 964 David Perkins (editor) 965 SNMPinfo 966 288 Quailbrook Ct San Carlos, 967 CA 94070 968 USA 970 Phone: +1 408 394-8702 971 EMail: dperkins@snmpinfo.com 972 Chris Elliott (editor) 973 Cisco Systems, Inc. 974 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 975 27709 976 USA 978 Phone: +1 919-392-2146 979 EMail: chelliot@cisco.com 981 Puneet Agarwal (editor) 982 Broadcom, Inc. 984 EMail: pagarwal@broadcom.com 986 Full Copyright Statement 988 Copyright (C) The IETF Trust (2008). 990 This document is subject to the rights, licenses and restrictions 991 contained in BCP 78, and except as set forth therein, the authors 992 retain all their rights. 994 This document and the information contained herein are provided on an 995 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 996 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 997 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 998 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 999 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1000 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1002 Intellectual Property 1004 The IETF takes no position regarding the validity or scope of any 1005 Intellectual Property Rights or other rights that might be claimed to 1006 pertain to the implementation or use of the technology described in 1007 this document or the extent to which any license under such rights 1008 might or might not be available; nor does it represent that it has 1009 made any independent effort to identify any such rights. Information 1010 on the procedures with respect to rights in RFC documents can be 1011 found in BCP 78 and BCP 79. 1013 Copies of IPR disclosures made to the IETF Secretariat and any 1014 assurances of licenses to be made available, or the result of an 1015 attempt made to obtain a general license or permission for the use of 1016 such proprietary rights by implementers or users of this 1017 specification can be obtained from the IETF on-line IPR repository at 1018 http://www.ietf.org/ipr. 1020 The IETF invites any interested party to bring to its attention any 1021 copyrights, patents or patent applications, or other proprietary 1022 rights that may cover technology that may be required to implement 1023 this standard. Please address the information to the IETF at 1024 ietf-ipr@ietf.org.