idnits 2.17.1 draft-yangshi-capwap-802dot11-mib-02.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 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1001. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1012. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1019. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1025. 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 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 (February 12, 2008) is 5918 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4181' is defined on line 952, but no explicit reference was found in the text == Outdated reference: A later version (-02) exists of draft-yangshi-capwap-base-mib-01 == Outdated reference: A later version (-15) exists of draft-ietf-capwap-protocol-specification-08 == Outdated reference: A later version (-12) exists of draft-ietf-capwap-protocol-binding-ieee80211-05 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Yang Shi, Ed. 3 Internet-Draft H3C Tech. Co., Ltd 4 Intended status: Standards Track Perkins, Ed. 5 Expires: August 15, 2008 SNMPinfo 6 Chris, Ed. 7 Cisco Systems, Inc. 8 February 12, 2008 10 CAPWAP Protocol Binding MIB for IEEE 802.11 11 draft-yangshi-capwap-802dot11-mib-02 13 Status of This Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of 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 August 15, 2008. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2008). 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols. In particular, it 46 describes managed objects for modeling the Control And Provisioning 47 of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless 48 binding. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. The Internet-Standard Management Framework . . . . . . . . . . 3 54 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 58 6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 59 6.2. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5 60 6.3. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5 61 6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 5 62 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 63 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 6 64 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6 65 7.3. Relationship to CAPWAP Base MIB . . . . . . . . . . . . . 8 66 7.4. Relationship to IEEE 802.11 MIB . . . . . . . . . . . . . 8 67 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 68 8. Example of CAPWAP-DOT11-MIB Usage . . . . . . . . . . . . . . 8 69 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 71 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 72 11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 19 73 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 19 74 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 75 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 76 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 77 14.1. Normative References . . . . . . . . . . . . . . . . . . . 19 78 14.2. Informative References . . . . . . . . . . . . . . . . . . 21 80 1. Introduction 82 Current work is under way in the IETF to specify the CAPWAP Protocol 83 [I-D.ietf-capwap-protocol-specification], which enables an Access 84 Controller (AC) to manage a collection of Wireless Termination Points 85 (WTPs). CAPWAP supports the use of various wireless technologies by 86 the WTPs, with one being specified in the 802.11 binding document 87 [I-D.ietf-capwap-protocol-binding-ieee80211]. 89 This document defines a MIB module that can be used to manage CAPWAP 90 implementations for IEEE 802.11 wireless binding. This MIB module 91 covers both configuration for WLAN and a way to reuse IEEE 802.11 MIB 92 standard in series defined by IEEE 802.11 WG. 94 2. The Internet-Standard Management Framework 96 For a detailed overview of the documents that describe the current 97 Internet-Standard Management Framework, please refer to section 7 of 98 RFC 3410 [RFC3410]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. MIB objects are generally 102 accessed through the Simple Network Management Protocol (SNMP). 103 Objects in the MIB are defined using the mechanisms defined in the 104 Structure of Management Information (SMI). This memo specifies a MIB 105 module that is compliant to the SMIv2, which is described in STD 58, 106 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 107 [RFC2580]. 109 3. Terminology 111 This document uses terminology from the document describing the 112 CAPWAP Protocol specification for 802.11 binding 113 [I-D.ietf-capwap-protocol-binding-ieee80211]. Besides terminology 114 defined in the IEEE 802.11 standard and CAPWAP specification, an 115 important conception is WLAN service. In the document, WLAN service 116 refers to a logical component instantiated on a WTP device. A single 117 physical WTP may operate a number of WLAN services, and the way is 118 called as virtual AP. Each Basic Service Set Identifier (BSSID) and 119 its constituent wireless terminal radios is denoted as a distinct 120 WLAN on a physical WTP. To support physical WTP with multiple WLANs 121 is an important feature for CAPWAP protocol's 802.11 binding, and it 122 is also for MIB design. 124 4. Conventions 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC 2119 [RFC2119]. 130 5. Overview 132 The [I-D.yangshi-capwap-base-mib] provides a way to configure and 133 manage WTP and radio objects through SNMP. It's a basis for manage 134 and control a IEEE 802.11 binding. 136 The CAPWAP Protocol's IEEE 802.11 binding MIB module (CAPWAP-DOT11- 137 MIB) provides a way to configure WLAN service, also could easily 138 reuse current and future IEEE 802.11 MIB standards. 140 It is designed to satisfy the following requirements and constraints: 142 - The MIB module could easily reuse current and future IEEE 802.11 143 MIB standard in series defined by IEEE 802.11 WG, and not require to 144 redefine them. 146 - From AC to centrally manage and configure WLAN service; 148 - Operators could configure MAC type and tunnel mode for a specific 149 WLAN service by SNMP; 151 - The MIB module supports virtual AP; 153 Before coming to details of CAPWAP-MIB-DOT11 module, it will 154 introduce how it is able to reuse IEEE MIB standard. As centralized 155 Wireless architecture, the operator has to prepare configurations for 156 each wireless at AC side before WTPs connect to AC. Under 157 centralized Wireless architectures, according to [I-D.ietf-capwap- 158 protocol-specification], each WLAN service is identifed by WLAN Id. 159 According to IEEE 802.11 MIB standards, the MIB tables such as 160 Dot11AuthenticationAlgorithmsTable are able to support wireless 161 configuration (such as authentication algorithm), and these tables 162 use ifIndex as index. A Wireless service could be abstracted as an 163 interface on the AC side, and which could be identified by ifIndex. 164 On the AC side, the MIB table CapwapDot11WirelessConfigTable will 165 indicate the mapping relation between a "WLAN Id" and ifIndex of a 166 "WLAN Service Interface". With ifIndex of a "WLAN Service 167 Interface", system is able to reuse IEEE MIBs. 169 6. Structure of the MIB Module 171 6.1. Textual Conventions 173 The following textual conventions are defined: 175 CapwapDot11WLANId ::= TEXTUAL-CONVENTION 176 STATUS current 177 DESCRIPTION 178 "Represents the TC for WLAN Id." 179 SYNTAX Unsigned32 181 6.2. The capwapDot11Objects Subtree 183 The subtree provides information for configuration parameters of WLAN 184 service and binding WLAN service to a specific radio. 186 6.3. The capwapDot11Conformance Subtree 188 The subtree provides conformance information of MIB objects. 190 6.4. Brief Description of MIB Objects 192 The MIB objects were derived from the CAPWAP protocol 802.11 binding 193 document [I-D.ietf-capwap-protocol-binding-ieee80211]. 195 1) capwapDot11WLANConfigTable 197 The table is used for providing configuration such as MAC type and so 198 on for WLANs. For a specific WLAN service which is identified by 199 capwapDot11WLANId, an interface of 'WLAN Service Interface' ifType 200 will be created. By the ifIndex of interface, it provides a way to 201 reuse IEEE 802.11 MIB. For example, according to 202 [I-D.ietf-capwap-protocol-binding-ieee80211], there is a TLV of 203 authentication Type for a WLAN. In IEEE 802.11 MIB, the MIB object 204 dot11AuthenticationAlgorithm in the 205 dot11AuthenticationAlgorithmsTable is corresponding to Auth Type TLV. 206 Considering both capwapDot11WLANConfigTable and 207 dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP- 208 DOT11-MIB are able to easily reuse dot11AuthenticationAlgorithm 209 object in IEEE 802.11 MIB. It is same for other IEEE 802.11 MIBs' 210 reuse. 212 2) capwapDot11WLANBindTable 214 The table provides a way to bind WLAN service to a radio, then 215 support virtual AP. The binding operation will dynamically create 216 "WLAN BSS Interface", and this logical interface is used for data 217 forwarding function. 219 7. Relationship to Other MIB Modules 220 7.1. Relationship to the SNMPv2-MIB 222 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 223 mandatory for all systems, and the objects apply to the entity as a 224 whole. The 'system' group provides identification of the management 225 entity and certain other system-wide data. The CAPWAP-DOT11-MIB does 226 not duplicate those objects. 228 7.2. Relationship to the IF-MIB 230 The Interfaces Group [RFC2863] defines generic managed objects for 231 managing interfaces. This memo contains the media-specific 232 extensions to the Interfaces Group for managing WLAN service that are 233 modeled as interfaces. 235 For each WLAN, it will have a logical interface of 'WLAN Service 236 Interface' responding to it at AC side. The interface SHOULD be 237 modeled as an ifEntry and provide appropriate interface information. 239 To provide data forwarding service, system will dynamically create 240 logical interface of 'WLAN BSS Interface'. The interface SHOULD be 241 modeled as an ifEntry and provide appropriate interface information. 243 Some specific interpretations of ifTable for CAPWAP-DOT11-MIB are as 244 follow. 246 1) WLAN Service Interface 248 Object Use for the CAPWAP-DOT11-MIB 250 ifIndex Each interface of 'WLAN Service Interface' type 251 maybe be represented by an ifEntry. 253 ifDescr Description of the interface of 'WLAN Service 254 Interface' type. 256 ifType IANAifType of "WLAN Service Interface". 258 ifName Textual name (unique on this system) of the interface 259 or an octet string of zero length. 261 ifAlias The nonvolatile 'alias' name for the interface, as 262 specified by a network manager. 264 ifPhysAddress Unused. 266 ifAdminStatus This variable indicates the administrator's intent as 267 to whether PHY should be enabled, disabled. Could be 268 always enabled. 270 ifOperStatus This value reflects the actual or operational status 271 of interface. Could be always enabled. 272 Also see [RFC2863]. 274 ifLastChange The value of sysUpTime at the time the interface 275 entered its current operational state. 276 Also see [RFC2863]. 278 The other objects such as ifInOctets, ifOutOctets, ifInErrors, 279 ifOutErrors are unused. 281 2) WLAN BSS Interface 283 Object Use for the CAPWAP-DOT11-MIB 285 ifIndex Each interface of 'WLAN BSS Interface' type maybe 286 be represented by an ifEntry. 288 ifDescr Description of the interface of 'WLAN BSS Interface' 289 type. 291 ifType IANAifType of "WLAN BSS Interface". 293 ifName Textual name (unique on this system) of the interface 294 or an octet string of zero length. 296 ifAlias The nonvolatile 'alias' name for the interface, as 297 specified by a network manager. 299 ifPhysAddress The physical address of interface. 300 One possible method is for the WTP to assign the 301 address for 'WLAN BSS Interface' using the following 302 algorithm: base BSSID address + WLAN ID. 304 ifAdminStatus This variable indicates the administrator's intent as 305 to whether PHY should be enabled, disabled, or 306 running in some diagnostic testing mode on this 307 interface. 308 Also see [RFC2863]. 310 ifOperStatus This value reflects the actual or operational status 311 of interface. 312 Also see [RFC2863]. 314 ifLastChange The value of sysUpTime at the time the interface 315 entered its current operational state. 317 Also see [RFC2863]. 319 ifInOctets The number of octets received as 802.11 frames. 321 ifOutOctets The number of octets transmitted as 802.11 322 frames. 324 ifInErrors The number of 802.11 frames dropped due to 325 uncorrectable errors. 327 ifInUnknownProtos 328 The number of received 802.11 frame discarded during 329 frame header validation, including frames with 330 unrecognized label values. 332 ifOutErrors See [RFC2863]. 334 7.3. Relationship to CAPWAP Base MIB 336 The CAPWAP Base MIB provides a way to manage and control WTP and 337 radio objects. Based on it, CAPWAP-DOT11-MIB provides more 338 information from WLAN service perspective. 340 7.4. Relationship to IEEE 802.11 MIB 342 Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface' 343 ifType, the MIB module is able to reuse MIB objects in the IEEE 344 802.11 MIB. 346 7.5. MIB modules required for IMPORTS 348 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 349 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and 350 CAPWAP-MIB [I-D.yangshi-capwap-base-mib]. 352 8. Example of CAPWAP-DOT11-MIB Usage 354 Combining the example in the [I-D.yangshi-capwap-base-mib], 355 here give a whole example for configuration and management of WTP, 356 radio and WLAN object. 358 1) Identify each 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. 362 When configuration for a WTP is prepared before a WTP connects to AC, 363 the following information is available in the CapwapRadioBindTable. 364 In CapwapRadioBindTable 365 { 366 capwapWTPId = 12345678 367 capwapRadioId = 1 368 capwapWTPVirtualRadioifIndex = 10, 369 capwapWirelessBinding = dot11(2), 370 } 371 Suppose WTP's serial number is 12345678, and first PHY radio's id 372 is 1. At AC side, the ifIndex of "WTP Virtual Radio Interface" is 373 10 which represents the PHY radio 1. 374 By the mechanism of "WTP Virtual Radio Interface", it seemed that WTP 375 PHY radios are located at AC side. 376 The interface of "WTP Virtual Radio Interface" is modeled by ifTable. 377 In ifTable 378 { 379 ifIndex = 10, 380 ifDescr = "WTP Virtual Radio Interface", 381 ifType = IANAifType of "WTP Virtual Radio 382 Interface", 383 ifMtu = 0, 384 ifSpeed = 0, 385 ifPhysAddress = 0.0.0.0.0.0, 386 ifAdminStatus = true, 387 ifOperStatus = false, 388 ifLastChange = 0, 389 ifInOctets = 0, 390 ifInUcastPkts = 0, 391 ifInDiscards = 0, 392 ifInErrors = 0, 393 ifInUnknownProtos = 0, 394 ifOutOctets = 0, 395 ifOutUcastPkts = 0, 396 ifOutDiscards = 0, 397 ifOutErrors = 0, 398 } 400 2) Configure IEEE 802.11 wireless binding parameters for "WTP Virtual 401 Radio Interface" 402 It will be done at the AC side through IEEE 802.11 MIB. 403 For example, to configure parameter for "WTP Virtual Radio Interface" 404 by IEEE 802.11 Dot11OperationTable. 405 In Dot11OperationTable 406 { 407 ifIndex = 10, 408 dot11MACAddress = 0.0.0.0.0.0, 409 dot11RTSThreshold = 2347, 410 dot11ShortRetryLimit = 7, 411 dot11LongRetryLimit = 4, 412 dot11FragmentationThreshold = 256, 413 dot11MaxTransmitMSDULifetime = 512, 414 dot11MaxReceiveLifetime = 512, 415 dot11ManufacturerID = "capwap", 416 dot11ProductID = "capwap" 417 } 418 In the example, it supposes ifIndex of a "WTP Virtual Radio 419 Interface" is 10. 421 3) Configure WLAN service 422 WLAN service configuration will be done through CAPWAP-DOT11-MIB 423 and IEEE 802.11 MIB. 424 First step is to create a "WLAN Service Interface" through 425 CAPWAP-DOT11-MIB at AC side. 426 In CapwapDot11WLANConfigTable 427 { 428 capwapDot11WLANId = 1, 429 capwapDot11WLANServiceIfIndex = 20, 430 capwapWTPMACType = splitMAC(2), 431 capwapWTPTunnelMode = dot3Tunnel, 432 capwapDot11WLANConfigRowStatus = create 433 } 434 Here supposes to configure a WLAN serivce which is identified by 435 capwapDot11WLANId 1. A "WLAN Service Interface" is created for it 436 and identified by ifIndex 20. 437 Corresponding to "WLAN Service Interface", it SHOULD be modeled as an 438 ifEntry at AC side and provide appropriate interface information. 439 In ifTable 440 { 441 ifIndex = 20, 442 ifDescr = "WLAN Service Interface", 443 ifType = IANAifType of "WLAN Service Interface", 444 ifMtu = 0, 445 ifSpeed = 0, 446 ifPhysAddress = 0.0.0.0.0.0, 447 ifAdminStatus = true, 448 ifOperStatus = true, 449 ifLastChange = 0, 450 ifInOctets = 0, 451 ifInUcastPkts = 0, 452 ifInDiscards = 0, 453 ifInErrors = 0, 454 ifInUnknownProtos = 0, 455 ifOutOctets = 0, 456 ifOutUcastPkts = 0, 457 ifOutDiscards = 0, 458 ifOutErrors = 0 459 } 460 Second step is to configure WLAN parameters of "WLAN Service 461 Interface" through IEEE 802.11 MIB at AC side. 462 In Dot11AuthenticationAlgorithmsTable 463 { 465 ifIndex = 20, 466 dot11AuthenticationAlgorithmsIndex = 1, 467 dot11AuthenticationAlgorithm = Shared Key, 468 dot11AuthenticationAlgorithmsEnable = true 469 } 470 Here ifIndex 20 is for interface of "WLAN Service Interface" 471 ifType. Suppose the index of authentication algorithm is 1. 473 4) Bind WLAN service to WTP radio 474 At AC side, through CapwapDot11WLANBindTable, it configures which 475 WLAN service (identified by capwapDot11WLANId) will be provided on 476 which radio (identifed by ifIndex). Suppose capwapWTPMACType of WLAN 477 service is splitMAC(2), the interface of 'WLAN BSS Interface' 478 will be created at AC side. 479 The AC will use it for split data forwarding. Here supposes ifIndex 480 of interface in 'WLAN BSS Interface' ifType is 30. 481 In CapwapDot11WLANBindTable 482 { 483 ifIndex = 10, 484 capwapDot11WLANId = 1, 485 capwapDot11WLANBSSIfIndex = 30, 486 capwapDot11WLANBSSRowStatus = create 487 } 489 5) WTP reports its current configuration status 490 After join phase and before WTP get configuration from AC, it will 491 report its current configuration status to AC through configuration 492 status message. The MIB data will be updated at AC side. 493 For example, for the 802.11 binding, WTP will update data in the 494 ifTable and IEEE 802.11 MIB so on according to message content. 495 As a example for ifIndex 10 (which identify an interface of 496 "WLAN Virtual Radio Interface" ifType), its ifOperStatus in ifTable 497 will be updated with current radio operational status in the message. 499 6) Query WTP and radio statistics data 500 After WTPs come to run status, administrator could query WTP and 501 radio statistics data through CAPWAP-MIB and CAPWAP-DOT11-MIB. 502 For example, through dot11CountersTable in the IEEE 802.11 MIB, 503 administrator could query counter data for radio which is identified 504 by ifIndex of a "WLAN Virtual Radio Interface". 506 7) Query other statistics data 507 For example, administrator could query the configuration of 508 WLAN service through Dot11AuthenticationAlgorithmsTable. 510 Query statistic data of 'WLAN BSS Interface' through ifTable; 512 9. Definitions 514 CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN 516 IMPORTS 517 RowStatus, TEXTUAL-CONVENTION 518 FROM SNMPv2-TC 519 OBJECT-GROUP, MODULE-COMPLIANCE 520 FROM SNMPv2-CONF 521 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 522 FROM SNMPv2-SMI 523 ifIndex, InterfaceIndex 524 FROM IF-MIB 525 CapwapWTPMACType, CapwapWTPTunnelMode 526 FROM CAPWAP-MIB; 528 capwapDot11MIB MODULE-IDENTITY 529 LAST-UPDATED "200802120000Z" -- Feb 12, 2008 530 ORGANIZATION "IETF Control And Provisioning of Wireless Access 531 Points (CAPWAP) Working Group 532 http://www.ietf.org/html.charters/capwap-charter.html" 533 CONTACT-INFO 534 "General Discussion: capwap@frascone.com 535 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 537 Yang Shi 538 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 539 District,Beijing,China 540 Email: young@h3c.com 542 David T. Perkins 543 228 Bayview Dr 544 San Carlos, CA 94070 545 USA 546 Phone: +1 408 394-8702 547 Email: dperkins@snmpinfo.com 549 Chris Elliott 550 Cisco Systems, Inc. 551 7025 Kit Creek Rd., P.O. Box 14987 552 Research Triangle Park 27709 553 USA 554 Phone: +1 919-392-2146 555 Email: chelliot@cisco.com" 557 DESCRIPTION 558 "Copyright (C) 2008 The Internet Society. This version of 559 the MIB module is part of RFC xxx; see the RFC itself 560 for full legal notices. 562 This MIB module contains managed object definitions for 563 the IEEE 802.11 bindings for the CAPWAP Protocol." 564 REVISION "200802120000Z" 565 DESCRIPTION 566 "Initial version, published as RFC xxx" 567 ::= { mib-2 xxx } 569 -- Textual conventions 571 CapwapDot11WLANId ::= TEXTUAL-CONVENTION 572 STATUS current 573 DESCRIPTION 574 "Represents the TC for WLAN Id." 575 SYNTAX Unsigned32 577 -- Top level components of this MIB 579 -- Tables, Scalars 580 capwapDot11Objects OBJECT IDENTIFIER 581 ::= { capwapDot11MIB 1 } 582 -- Conformance 583 capwapDot11Conformance OBJECT IDENTIFIER 584 ::= { capwapDot11MIB 2 } 586 -- capwapDot11WLANConfigTable Table 588 capwapDot11WLANConfigTable OBJECT-TYPE 589 SYNTAX SEQUENCE OF CapwapDot11WLANConfigEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "A table of objects that display and control the WLAN 594 service." 595 ::= { capwapDot11Objects 1 } 597 capwapDot11WLANConfigEntry OBJECT-TYPE 598 SYNTAX CapwapDot11WLANConfigEntry 599 MAX-ACCESS not-accessible 600 STATUS current 601 DESCRIPTION 602 "A set of objects that display and control the WLAN 603 service." 605 INDEX { capwapDot11WLANId } 606 ::= { capwapDot11WLANConfigTable 1 } 608 CapwapDot11WLANConfigEntry ::= 609 SEQUENCE { 610 capwapDot11WLANId CapwapDot11WLANId, 611 capwapDot11WLANServiceIfIndex InterfaceIndex, 612 capwapWTPMACType CapwapWTPMACType, 613 capwapWTPTunnelMode CapwapWTPTunnelMode, 614 capwapDot11WLANConfigRowStatus RowStatus 615 } 617 capwapDot11WLANId OBJECT-TYPE 618 SYNTAX CapwapDot11WLANId 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "Represents the WLAN id for a WLAN which has a 623 capwapDot11WLANServiceIfIndex interface corresponding to it." 624 REFERENCE 625 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 626 RFC xxx." 627 ::= { capwapDot11WLANConfigEntry 1 } 629 capwapDot11WLANServiceIfIndex OBJECT-TYPE 630 SYNTAX InterfaceIndex 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "Represents the ifIndex for an interface of 'WLAN Service 635 Interface' ifType. 636 Before WTPs connect to AC and get configuration, administrator 637 will prepare configuration for them. For a specific WLAN 638 service, a logical interface of 'WLAN Service Interface' ifType 639 will be created, and administrator could configure WLAN 640 parameter through it. For example, according to IEEE 802.11 641 '6.1. IEEE 802.11 Add WLAN' in the 642 [I-D.ietf-capwap-protocol-binding-ieee80211], administrator 643 could configure specify Auth Type for a WLAN. The 'WLAN Service 644 Interface' provides a way to uniquely identify each WLAN by 645 logical at AC side. As most MIBs use ifIndex to identify an 646 interface for configuration and statistic data, for example, 647 dot11AuthenticationAlgorithmsTable in 802.11 MIB use ifIndex 648 as index, and dot11AuthenticationAlgorithm object is for 649 Auth Type mentioned in the CAPWAP '6.1. IEEE 802.11 Add WLAN', 650 With the way of 'WLAN Service Interface', it will easily 651 reuse MIB table like dot11AuthenticationAlgorithmsTable, while 652 only care for other configurations like capwapWTPTunnelMode." 654 ::= { capwapDot11WLANConfigEntry 2 } 656 capwapWTPMACType OBJECT-TYPE 657 SYNTAX CapwapWTPMACType 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "Represents specifies whether the WTP should run the WLAN in 662 Local or Split MAC modes." 663 REFERENCE 664 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 665 RFC xxx." 666 ::= { capwapDot11WLANConfigEntry 3 } 668 capwapWTPTunnelMode OBJECT-TYPE 669 SYNTAX CapwapWTPTunnelMode 670 MAX-ACCESS read-create 671 STATUS current 672 DESCRIPTION 673 "Represents the frame tunneling type to be used for 802.11 data 674 frames from all stations associated with the WLAN." 675 REFERENCE 676 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 677 RFC xxx." 678 ::= { capwapDot11WLANConfigEntry 4 } 680 capwapDot11WLANConfigRowStatus OBJECT-TYPE 681 SYNTAX RowStatus 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "This variable is used to create, modify, and/or delete a row in 686 this table." 687 ::= { capwapDot11WLANConfigEntry 5 } 689 -- End of capwapDot11WLANConfigTable Table 691 -- 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'. 702 The PHY address for interface of 'WTP Virtual Radio Interface' 703 ifType will be base BSSID address for PHY 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.yangshi-capwap-base-mib] Shi, Y. and C. Elliott, 918 "CAPWAP Protocol Base 919 MIB", draft-yangshi- 920 capwap-base-mib-01 921 (work in progress), 922 December 2007. 924 [I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP 925 Protocol 926 Specification", draft- 927 ietf-capwap-protocol- 928 specification-08 (work 929 in progress), 930 November 2007. 932 [I-D.ietf-capwap-protocol-binding-ieee80211] Calhoun, P., "CAPWAP 933 Protocol Binding for 934 IEEE 802.11", draft- 935 ietf-capwap-protocol- 936 binding-ieee80211-05 937 (work in progress), 938 November 2007. 940 14.2. Informative References 942 [RFC3410] Case, J., Mundy, R., 943 Partain, D., and B. 944 Stewart, "Introduction 945 and Applicability 946 Statements for 947 Internet-Standard 948 Management Framework", 949 RFC 3410, 950 December 2002. 952 [RFC4181] Heard, C., "Guidelines 953 for Authors and 954 Reviewers of MIB 955 Documents", BCP 111, 956 RFC 4181, 957 September 2005. 959 Authors' Addresses 961 Yang Shi (editor) 962 H3C Tech. Co., Ltd 963 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 964 Beijing 965 China(100085) 967 Phone: +86 010 82775276 968 EMail: young@h3c.com 970 D. Perkins (editor) 971 SNMPinfo 972 288 Quailbrook Ct San Carlos, 973 CA 94070 974 USA 976 Phone: +1 408 394-8702 977 EMail: dperkins@snmpinfo.com 978 Chris Elliott (editor) 979 Cisco Systems, Inc. 980 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 981 27709 982 USA 984 Phone: +1 919-392-2146 985 EMail: chelliot@cisco.com 987 Full Copyright Statement 989 Copyright (C) The IETF Trust (2008). 991 This document is subject to the rights, licenses and restrictions 992 contained in BCP 78, and except as set forth therein, the authors 993 retain all their rights. 995 This document and the information contained herein are provided on an 996 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 997 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 998 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 999 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1000 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1001 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1003 Intellectual Property 1005 The IETF takes no position regarding the validity or scope of any 1006 Intellectual Property Rights or other rights that might be claimed to 1007 pertain to the implementation or use of the technology described in 1008 this document or the extent to which any license under such rights 1009 might or might not be available; nor does it represent that it has 1010 made any independent effort to identify any such rights. Information 1011 on the procedures with respect to rights in RFC documents can be 1012 found in BCP 78 and BCP 79. 1014 Copies of IPR disclosures made to the IETF Secretariat and any 1015 assurances of licenses to be made available, or the result of an 1016 attempt made to obtain a general license or permission for the use of 1017 such proprietary rights by implementers or users of this 1018 specification can be obtained from the IETF on-line IPR repository at 1019 http://www.ietf.org/ipr. 1021 The IETF invites any interested party to bring to its attention any 1022 copyrights, patents or patent applications, or other proprietary 1023 rights that may cover technology that may be required to implement 1024 this standard. Please address the information to the IETF at 1025 ietf-ipr@ietf.org. 1027 Acknowledgement 1029 Funding for the RFC Editor function is provided by the IETF 1030 Administrative Support Activity (IASA).