idnits 2.17.1 draft-ietf-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 20. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1058. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1069. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1076. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1082. ** 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 : ---------------------------------------------------------------------------- No issues found here. 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 (October 27, 2008) is 5650 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-09) exists of draft-ietf-capwap-base-mib-01 ** Downref: Normative reference to an Informational draft: draft-ietf-capwap-base-mib (ref. 'I-D.ietf-capwap-base-mib') -- No information found for draft-ietf-capwap-protocol-specification - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-capwap-protocol-specification' -- No information found for draft-ietf-capwap-protocol-binding-ieee80211 - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-capwap-protocol-binding-ieee80211' Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 11 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: April 30, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 October 27, 2008 12 CAPWAP Protocol Binding MIB for IEEE 802.11 13 draft-ietf-capwap-802dot11-mib-02 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 April 30, 2009. 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. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5 57 6.2. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5 58 6.3. Brief Description of MIB Objects . . . . . . . . . . . . . 5 59 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 60 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 5 61 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6 62 7.3. Relationship to CAPWAP-BASE-MIB . . . . . . . . . . . . . 8 63 7.4. Relationship to the MIBs defined in IEEE 802.11 64 standard and its amendments . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . 19 69 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 70 11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 20 71 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 20 72 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20 73 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 74 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 75 14.1. Normative References . . . . . . . . . . . . . . . . . . . 20 76 14.2. Informative References . . . . . . . . . . . . . . . . . . 22 78 1. Introduction 80 The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines 81 a standard, interoperable protocol, which enables an Access 82 Controller (AC) to manage a collection of Wireless Termination 83 Points(WTPs). CAPWAP supports the use of various wireless 84 technologies by the WTPs, with one being specified in the 802.11 85 binding document [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 the MIBs 90 defined in IEEE 802.11 standard and its amendments. 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 are 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, and it also allows to 136 easily reuse current and future MIBs defined in IEEE 802.11 standard 137 and its amendments. 139 It is designed to satisfy the following requirements and constraints: 141 - The MIB module could easily reuse current and future MIBs defined 142 in IEEE 802.11 standard and its amendments, and not require to 143 redefine them. 145 - From AC to centrally manage and configure WLAN service; 147 - Operators could configure MAC type and tunnel mode for a specific 148 WLAN service by SNMP; 150 - The MIB module supports virtual AP; 152 Before coming to details of CAPWAP-DOT11-MIB module, it will 153 introduce how it is able to reuse IEEE MIB standard. According to 154 [I-D.ietf-capwap-protocol-binding-ieee80211], each WLAN service is 155 identified by WLAN Id. In the MIBs defined in IEEE 802.11 standard 156 and its amendments, the MIB tables such as 157 Dot11AuthenticationAlgorithmsTable are able to support wireless 158 configuration (such as authentication algorithm), and these tables 159 use ifIndex as index. To support 802.11 parameters for a specific 160 WLAN service, and consider that the operator has to prepare 161 configurations for each WLAN service on the AC before WTPs connect to 162 AC, a wireless service could be abstracted as a 'WLAN Service 163 Interface' on the AC, and which could be identified by ifIndex. On 164 the AC, the MIB table CapwapDot11WlanConfigTable will indicate the 165 mapping relation between a 'WLAN Id" and ifIndex of a 'WLAN Service 166 Interface'. With ifIndex of a 'WLAN Service Interface', system is 167 able to reuse the MIBs defined in IEEE 802.11 standard and its 168 amendments. 170 6. Structure of the MIB Module 171 6.1. The capwapDot11Objects Subtree 173 The subtree provides information for configuration parameters of WLAN 174 service and binding WLAN service to a specific radio. 176 6.2. The capwapDot11Conformance Subtree 178 The subtree provides conformance information of MIB objects. 180 6.3. Brief Description of MIB Objects 182 The MIB objects were derived from the CAPWAP protocol binding for 183 802.11 document [I-D.ietf-capwap-protocol-binding-ieee80211]. 185 1) capwapDot11WlanConfigTable 187 The table is used for providing configuration such as MAC type and so 188 on for WLANs. For a specific WLAN service which is identified by 189 capwapDot11WlanId, an interface of 'WLAN Service Interface' ifType 190 will be created. By the ifIndex of interface, it provides a way to 191 reuse the MIBs defined in IEEE 802.11 standard and its amendments. 192 For example, according to 193 [I-D.ietf-capwap-protocol-binding-ieee80211], Auth Type needs to be 194 configured for a WLAN. In IEEE 802.11 MIB, the MIB object 195 dot11AuthenticationAlgorithm in the 196 dot11AuthenticationAlgorithmsTable is corresponding to Auth Type. 197 Considering both capwapDot11WlanConfigTable and 198 dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP- 199 DOT11-MIB are able to easily reuse dot11AuthenticationAlgorithm 200 object in IEEE 802.11 MIB. It is same for other objects in the MIBs 201 defined in IEEE 802.11 standard and its amendments. 203 2) capwapDot11WlanBindTable 205 The table provides a way to bind WLAN service to a radio, then 206 supports virtual AP. The binding operation will dynamically create 207 'WLAN BSS Interface', and this logical interface is used for data 208 forwarding function. 210 7. Relationship to Other MIB Modules 212 7.1. Relationship to the SNMPv2-MIB 214 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 215 mandatory for all systems, and the objects apply to the entity as a 216 whole. The 'system' group provides identification of the management 217 entity and certain other system-wide data. The CAPWAP-DOT11-MIB does 218 not duplicate those objects. 220 7.2. Relationship to the IF-MIB 222 The Interfaces Group [RFC2863] defines generic managed objects for 223 managing interfaces. This memo contains the media-specific 224 extensions to the Interfaces Group for managing WLAN service that are 225 modeled as interfaces. 227 For each WLAN, it will have a logical interface of 'WLAN Service 228 Interface' responding to it on the AC. The interface SHOULD be 229 modeled as an ifEntry and provide appropriate interface information. 230 'WLAN Service Interface' provides a way to configure IEEE 802.11 231 parameters for a specific WLAN service, and reuse the MIBs defined in 232 IEEE 802.11 standard and its amendments. 234 To provide data forwarding service, system will dynamically create 235 logical interface of 'WLAN BSS Interface'. The interface SHOULD be 236 modeled as an ifEntry and provide appropriate interface information. 237 The interface enables the virtual AP function. 239 Some specific interpretations of ifTable for CAPWAP-DOT11-MIB are as 240 follow. 242 1) WLAN Service Interface 244 Object Use for the CAPWAP-DOT11-MIB 246 ifIndex Each interface of 'WLAN Service Interface' type 247 maybe be represented by an ifEntry. 249 ifDescr Description of the interface of 'WLAN Service 250 Interface' type. 252 ifType IANAifType of 'WLAN Service Interface'. 254 ifName Textual name (unique on this system) of the interface 255 or an octet string of zero length. 257 ifAlias The nonvolatile 'alias' name for the interface, as 258 specified by a network manager. 260 ifPhysAddress Unused. 262 ifAdminStatus This variable indicates the administrator's intent as 263 to whether PHY should be enabled, disabled. Could be 264 always enabled. 266 ifOperStatus This value reflects the actual or operational status 267 of interface. Could be always enabled. 269 Also see [RFC2863]. 271 ifLastChange The value of sysUpTime at the time the interface 272 entered its current operational state. 273 Also see [RFC2863]. 275 The other objects such as ifInOctets, ifOutOctets, ifInErrors, 276 ifOutErrors are unused. 278 2) WLAN BSS Interface 280 Object Use for the CAPWAP-DOT11-MIB 282 ifIndex Each interface of 'WLAN BSS Interface' type maybe 283 be represented by an ifEntry. 285 ifDescr Description of the interface of 'WLAN BSS Interface' 286 type. 288 ifType IANAifType of 'WLAN BSS Interface'. 290 ifName Textual name (unique on this system) of the interface 291 or an octet string of zero length. 293 ifAlias The nonvolatile 'alias' name for the interface, as 294 specified by a network manager. 296 ifPhysAddress The physical address of interface, i.e. WTP assigned 297 BSSID. 299 ifAdminStatus This variable indicates the administrator's intent as 300 to whether PHY should be enabled, disabled, or 301 running in some diagnostic testing mode on this 302 interface. 303 Also see [RFC2863]. 305 ifOperStatus This value reflects the actual or operational status 306 of interface. 307 Also see [RFC2863]. 309 ifLastChange The value of sysUpTime at the time the interface 310 entered its current operational state. 311 Also see [RFC2863]. 313 ifInOctets The number of octets received as IEEE 802.11 frames. 315 ifOutOctets The number of octets transmitted as IEEE 802.11 316 frames. 318 ifInErrors The number of inbound IEEE 802.11 frames dropped due 319 to uncorrectable errors. 321 ifInUnknownProtos 322 The number of received IEEE 802.11 frame discarded 323 during frame header validation, including frames with 324 unrecognized label values. 326 ifOutErrors The number of outbound IEEE 802.11 frames dropped due 327 to uncorrectable errors. 329 7.3. Relationship to CAPWAP-BASE-MIB 331 The CAPWAP-BASE-MIB provides a way to manage and control WTP and 332 radio objects. Especially, CAPWAP-BASE-MIB has a mechanism of 'WTP 333 Virtual Radio Interface' which enable system to reuse the MIBs 334 defined in IEEE 802.11 standard and its amendments. With it, 335 administrator could configure an IEEE 802.11 AP radio's parameter and 336 query radio's traffic statistics. Based on CAPWAP-BASE-MIB, CAPWAP- 337 DOT11-MIB provides more information from WLAN service perspective. 339 7.4. Relationship to the MIBs defined in IEEE 802.11 standard and its 340 amendments 342 Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface' 343 ifType, the MIB module is able to reuse MIB objects in the MIBs 344 defined in IEEE 802.11 standard and its amendments. 346 In the 802.11 binding document [I-D.ietf-capwap-protocol-binding- 347 ieee80211], it involves a part of MIB objects defined by IEEE 802.11 348 standard and its amendments. Although CAPWAP-DOT11-MIB uses the 349 802.11 binding document as a reference, it could reuse all the MIB 350 objects defined by IEEE 802.11 standard and its amendments , and not 351 limited by the scope of the 802.11 binding document. 353 7.5. MIB modules required for IMPORTS 355 The following MIB modules are required for IMPORTS: SNMPv2-SMI 356 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 357 [RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib]. 359 8. Example of CAPWAP-DOT11-MIB Usage 361 In the CAPWAP-BASE-MIB, each PHY radio is identified by WTP Id and 362 radio ID, and which has a corresponding 'WTP Virtual Radio Interface' 363 on the AC. The IEEE 802.11 MIB associated with this interface 364 can be used to configure IEEE 802.11 wireless binding parameters for 365 radio such as RTS Threshold. 367 In the CAPWAP 802.11 Binding MIB, each WLAN service is identified 368 by WLAN Id, and which has a corresponding 'WLAN Service Interface' 369 on the AC. The MIBs defined in IEEE 802.11 standard and its 370 amendments associated with this interface can be used to configure 371 WLAN parameters for a WLAN service, such as Authentication Algorithm. 373 The 'WLAN BSS Interface', created by binding 'WTP Virtual Radio 374 Interface' and 'WLAN Service Interface', is used for data forwarding. 375 Combining the example provided in the [I-D.ietf-capwap-base-mib], 376 the following is a whole example for configuration and management of 377 WTP, radio and WLAN service for IEEE 802.11 binding. 379 1) Identify each PHY radio by 'WTP Virtual Radio Interface' 380 According to [I-D.ietf-capwap-protocol-specification], each radio on 381 a WTP will be identified by a radio Id. Each WTP could be identified 382 by its serial number. 383 When configuration for a WTP is prepared before a WTP connects to AC, 384 the following information is available in the 385 CapwapBaseRadioBindTable. 387 In CapwapBaseRadioBindTable 388 { 389 capwapBaseWTPId = 12345678, 390 capwapBaseRadioId = 1, 391 capwapBaseWtpVirtualRadioifIndex = 10, 392 capwapBaseWirelessBinding = dot11(2) 393 } 395 Suppose WTP's serial number is 12345678, and first PHY radio's id 396 is 1. On the AC, the ifIndex of 'WTP Virtual Radio Interface' is 397 10 which represents the PHY radio 1. 398 By the mechanism of 'WTP Virtual Radio Interface', it seemed that WTP 399 PHY radios are located on the AC. 400 The interface of 'WTP Virtual Radio Interface' is modeled by ifTable. 402 In ifTable 403 { 404 ifIndex = 10, 405 ifDescr = 'WTP Virtual Radio Interface', 406 ifType = IANAifType of 'WTP Virtual Radio 407 Interface', 408 ifMtu = 0, 409 ifSpeed = 0, 410 ifPhysAddress = 0.0.0.0.0.0, 411 ifAdminStatus = true, 412 ifOperStatus = false, 413 ifLastChange = 0, 414 ifInOctets = 0, 415 ifInUcastPkts = 0, 416 ifInDiscards = 0, 417 ifInErrors = 0, 418 ifInUnknownProtos = 0, 419 ifOutOctets = 0, 420 ifOutUcastPkts = 0, 421 ifOutDiscards = 0, 422 ifOutErrors = 0 423 } 425 2) Configure IEEE 802.11 wireless binding parameters for 'WTP Virtual 426 Radio Interface' 427 It will be done on the AC through the MIBs defined in IEEE 802.11 428 standard and its amendments. 429 For example, to configure parameter for 'WTP Virtual Radio Interface' 430 by IEEE 802.11 Dot11OperationTable. 432 In Dot11OperationTable 433 { 434 ifIndex = 10, 435 dot11MACAddress = 0.0.0.0.0.0, 436 dot11RTSThreshold = 2347, 437 dot11ShortRetryLimit = 7, 438 dot11LongRetryLimit = 4, 439 dot11FragmentationThreshold = 256, 440 dot11MaxTransmitMSDULifetime = 512, 441 dot11MaxReceiveLifetime = 512, 442 dot11ManufacturerID = 'capwap', 443 dot11ProductID = 'capwap' 444 } 446 In the example, it supposes ifIndex of a 'WTP Virtual Radio 447 Interface' is 10. 449 3) Configure WLAN service 451 WLAN service configuration will be done through CAPWAP-DOT11-MIB, 452 and the MIBs defined in IEEE 802.11 standard and its amendments. 454 First step is to create a 'WLAN Service Interface' through 455 CAPWAP-DOT11-MIB on the AC. 457 In CapwapDot11WlanConfigTable 458 { 459 capwapDot11WlanId = 1, 460 capwapDot11WlanServiceIfIndex = 20, 461 capwapDot11WlanMacType = splitMAC(2), 462 capwapDot11WlanTunnelMode = dot3Tunnel(2), 463 capwapDot11WlanConfigRowStatus = create 464 } 466 Here supposes to configure a WLAN service which is identified by 467 capwapDot11WlanId 1. A 'WLAN Service Interface' is created 468 for it and identified by ifIndex 20. 469 Corresponding to 'WLAN Service Interface', it SHOULD be modeled as an 470 ifEntry on the AC and provide appropriate interface information. 472 In ifTable 473 { 474 ifIndex = 20, 475 ifDescr = 'WLAN Service Interface', 476 ifType = IANAifType of 'WLAN Service Interface', 477 ifMtu = 0, 478 ifSpeed = 0, 479 ifPhysAddress = 0.0.0.0.0.0, 480 ifAdminStatus = true, 481 ifOperStatus = true, 482 ifLastChange = 0, 483 ifInOctets = 0, 484 ifInUcastPkts = 0, 485 ifInDiscards = 0, 486 ifInErrors = 0, 487 ifInUnknownProtos = 0, 488 ifOutOctets = 0, 489 ifOutUcastPkts = 0, 490 ifOutDiscards = 0, 491 ifOutErrors = 0 492 } 494 Second step is to configure WLAN parameters of 'WLAN Service 495 Interface' through the MIBs defined in IEEE 802.11 standard and 496 its amendments on the AC. 498 In Dot11AuthenticationAlgorithmsTable 499 { 500 ifIndex = 20, 501 dot11AuthenticationAlgorithmsIndex = 1, 502 dot11AuthenticationAlgorithm = Shared Key, 503 dot11AuthenticationAlgorithmsEnable = true 504 } 506 Here ifIndex 20 is for interface of 'WLAN Service Interface' 507 ifType. Suppose the index of authentication algorithm is 1. 509 4) Bind WLAN service to WTP radio 510 On the AC, through CapwapDot11WlanBindTable, it configures which 511 WLAN service (identified by capwapDot11WlanId) will be provided 512 on which radio (identified by ifIndex). 513 Suppose capwapDot11WlanMacType of WLAN service is splitMAC(2), 514 the interface of 'WLAN BSS Interface' will be created on the AC. 515 The AC will use it for split data forwarding. Here supposes ifIndex 516 of interface in 'WLAN BSS Interface' ifType is 30. 518 In CapwapDot11WlanBindTable 519 { 520 ifIndex = 10, 521 capwapDot11WlanId = 1, 522 capwapDot11WlanBssIfIndex = 30, 523 capwapDot11WlanBssRowStatus = create 524 } 526 5) WTP reports its current configuration status 528 After join phase and before WTP get configuration from AC, it will 529 report its current configuration status to AC through configuration 530 status request message. The MIB data will be updated on the AC. 531 As an example, for ifIndex 10 (which identifies an interface of 'WLAN 532 Virtual Radio Interface' ifType), its ifOperStatus in ifTable will 533 be updated with current radio operational status. 535 6) Query WTP and radio statistics data 536 After WTPs come to run status, administrator could query WTP and 537 radio statistics data through CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB. 538 For example, through dot11CountersTable in the IEEE 802.11 MIB, 539 administrator could query counter data for radio which is identified 540 by ifIndex of a 'WLAN Virtual Radio Interface'. 542 7) Query other statistics data 544 For example, administrator could query the configuration of 545 WLAN service through Dot11AuthenticationAlgorithmsTable and statistic 546 data of 'WLAN BSS Interface' through ifTable; 548 9. Definitions 550 CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN 552 IMPORTS 553 RowStatus, TEXTUAL-CONVENTION 554 FROM SNMPv2-TC 555 OBJECT-GROUP, MODULE-COMPLIANCE 556 FROM SNMPv2-CONF 557 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 558 FROM SNMPv2-SMI 560 ifIndex, InterfaceIndex 561 FROM IF-MIB 562 CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC 563 FROM CAPWAP-BASE-MIB; 565 capwapDot11MIB MODULE-IDENTITY 566 LAST-UPDATED "200810270000Z" -- Oct 27th, 2008 567 ORGANIZATION "IETF Control And Provisioning of Wireless Access 568 Points (CAPWAP) Working Group 569 http://www.ietf.org/html.charters/capwap-charter.html" 570 CONTACT-INFO 571 "General Discussion: capwap@frascone.com 572 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 574 Yang Shi 575 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 576 District,Beijing,China(100085) 577 Email: young@h3c.com 579 David T. Perkins 580 228 Bayview Dr 581 San Carlos, CA 94070 582 USA 583 Phone: +1 408 394-8702 584 Email: dperkins@snmpinfo.com 586 Chris Elliott 587 Cisco Systems, Inc. 588 7025 Kit Creek Rd., P.O. Box 14987 589 Research Triangle Park 27709 590 USA 591 Phone: +1 919-392-2146 592 Email: chelliot@cisco.com 594 Yong Zhang 595 Fortinet, Inc. 596 1090 Kifer Road 597 Sunnyvale, CA 94086 598 USA 599 Email: yzhang@fortinet.com" 601 DESCRIPTION 602 "Copyright (C) 2008 The Internet Society. This version of 603 the MIB module is part of RFC xxx; see the RFC itself 604 for full legal notices. 606 This MIB module contains managed object definitions for 607 the IEEE 802.11 bindings for the CAPWAP Protocol." 609 REVISION "200810270000Z" 610 DESCRIPTION 611 "Initial version, published as RFC xxx" 612 ::= { mib-2 xxx } 614 -- Textual conventions 616 CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION 617 DISPLAY-HINT "d" 618 STATUS current 619 DESCRIPTION 620 "Represents an unique identifier of a WLAN." 621 SYNTAX Unsigned32 (1..16) 623 -- Top level components of this MIB 625 -- Tables, Scalars 626 capwapDot11Objects OBJECT IDENTIFIER 627 ::= { capwapDot11MIB 1 } 628 -- Conformance 629 capwapDot11Conformance OBJECT IDENTIFIER 630 ::= { capwapDot11MIB 2 } 632 -- capwapDot11WlanConfigTable Table 634 capwapDot11WlanConfigTable OBJECT-TYPE 635 SYNTAX SEQUENCE OF CapwapDot11WlanConfigEntry 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "A table of objects that display and control the WLAN 640 service. 641 Values of all read-create objects in this 642 table are persistent at restart/reboot." 643 ::= { capwapDot11Objects 1 } 645 capwapDot11WlanConfigEntry OBJECT-TYPE 646 SYNTAX CapwapDot11WlanConfigEntry 647 MAX-ACCESS not-accessible 648 STATUS current 649 DESCRIPTION 650 "A set of objects that display and control the WLAN 651 service." 652 INDEX { capwapDot11WlanId } 653 ::= { capwapDot11WlanConfigTable 1 } 655 CapwapDot11WlanConfigEntry ::= 656 SEQUENCE { 657 capwapDot11WlanId CapwapDot11WlanIdTC, 658 capwapDot11WlanServiceIfIndex InterfaceIndex, 659 capwapDot11WlanMacType CapwapBaseMacTypeTC, 660 capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC, 661 capwapDot11WlanConfigRowStatus RowStatus 662 } 664 capwapDot11WlanId OBJECT-TYPE 665 SYNTAX CapwapDot11WlanIdTC 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "Represents the WLAN Id for a WLAN which has a 670 capwapDot11WlanServiceIfIndex interface corresponding to it." 671 REFERENCE 672 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 673 RFC xxx." 674 ::= { capwapDot11WlanConfigEntry 1 } 676 capwapDot11WlanServiceIfIndex OBJECT-TYPE 677 SYNTAX InterfaceIndex 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "Represents the index value that uniquely identifies a 682 'WLAN Service Interface'. The interface identified by a 683 particular value of this index is the same interface as 684 identified by the same value of ifIndex. 685 Before WTPs connect to AC and get configuration, administrator 686 will prepare configuration for them. For a specific WLAN 687 service, a logical interface of 'WLAN Service Interface' 688 ifType will be created, and administrator could configure WLAN 689 parameter through it. For example, according to IEEE 802.11 690 '6.1. IEEE 802.11 Add WLAN' in the 691 [I-D.ietf-capwap-protocol-binding-ieee80211], administrator 692 could configure Auth Type for a WLAN. The 'WLAN 693 Service Interface' provides a way to uniquely identify each 694 WLAN by logical on the AC. As most MIBs use ifIndex to 695 identify an interface for configuration and statistic data, 696 for example, dot11AuthenticationAlgorithmsTable in IEEE 802.11 697 MIB use ifIndex as index, and dot11AuthenticationAlgorithm 698 object is for Auth Type mentioned in the CAPWAP '6.1. IEEE 699 802.11 Add WLAN', With the way of 'WLAN Service Interface', 700 it will easily reuse MIB table like 701 dot11AuthenticationAlgorithmsTable, while only care for other 702 configurations like capwapDot11WlanTunnelMode." 704 ::= { capwapDot11WlanConfigEntry 2 } 706 capwapDot11WlanMacType OBJECT-TYPE 707 SYNTAX CapwapBaseMacTypeTC 708 MAX-ACCESS read-create 709 STATUS current 710 DESCRIPTION 711 "Represents whether the WTP should support the WLAN in 712 Local or Split MAC modes." 713 REFERENCE 714 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 715 RFC xxx." 716 ::= { capwapDot11WlanConfigEntry 3 } 718 capwapDot11WlanTunnelMode OBJECT-TYPE 719 SYNTAX CapwapBaseTunnelModeTC 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "Represents the frame tunneling type to be used for 802.11 data 724 frames from all stations associated with the WLAN. 725 Bits are exclusive with each other for a specific WLAN Id." 726 REFERENCE 727 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 728 RFC xxx." 729 ::= { capwapDot11WlanConfigEntry 4 } 731 capwapDot11WlanConfigRowStatus OBJECT-TYPE 732 SYNTAX RowStatus 733 MAX-ACCESS read-create 734 STATUS current 735 DESCRIPTION 736 "This variable is used to create, modify, and/or delete a row in 737 this table." 738 ::= { capwapDot11WlanConfigEntry 5 } 740 -- End of capwapDot11WlanConfigTable Table 742 -- capwapDot11WlanBindTable Table 744 capwapDot11WlanBindTable OBJECT-TYPE 745 SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "A table of objects that display and control the mapping 750 relationship between interface of 'WTP Virtual Radio Interface' 751 interface and interface of 'WLAN BSS Interface'. 752 The PHY address for interface of 'WTP Virtual Radio 753 Interface' ifType will be base BSSID address for PHY 754 radio." 755 REFERENCE 756 "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, 757 RFC xxx." 758 ::= { capwapDot11Objects 2 } 760 capwapDot11WlanBindEntry OBJECT-TYPE 761 SYNTAX CapwapDot11WlanBindEntry 762 MAX-ACCESS not-accessible 763 STATUS current 764 DESCRIPTION 765 "A set of objects that display the mapping relationship 766 between interface of 'WTP Virtual Radio Interface' and 767 interface of 'WLAN BSS Interface'." 768 INDEX { ifIndex, capwapDot11WlanId } 769 ::= { capwapDot11WlanBindTable 1 } 771 CapwapDot11WlanBindEntry ::= 772 SEQUENCE { 773 capwapDot11WlanBssIfIndex InterfaceIndex, 774 capwapDot11WlanBssRowStatus RowStatus 775 } 777 capwapDot11WlanBssIfIndex OBJECT-TYPE 778 SYNTAX InterfaceIndex 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "Represents the index value that uniquely identifies a 783 'WLAN BSS Interface'. The interface identified by a 784 particular value of this index is the same interface as 785 identified by the same value of ifIndex. 786 Each capwapDot11WlanBssIfIndex will corresponding to a 787 WLAN service on the PHY radio which is identified by ifIndex. 788 The PHY address for capwapDot11WlanBssIfIndex is BSSID. 789 While manufacturers are free to assign BSSIDs using any 790 arbitrary mechanism, it is advised that where possible the 791 BSSIDs are assigned as a contiguous block. 792 When assigned as a block, implementations can still assign 793 any of the available BSSIDs to any WLAN. One possible method 794 is for the WTP to assign the address using the following 795 algorithm: base BSSID address + WLAN ID." 796 REFERENCE 797 "Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11, 798 RFC xxx." 800 ::= { capwapDot11WlanBindEntry 1 } 802 capwapDot11WlanBssRowStatus OBJECT-TYPE 803 SYNTAX RowStatus 804 MAX-ACCESS read-create 805 STATUS current 806 DESCRIPTION 807 "This variable is used to create, modify, and/or delete a row 808 in this table." 809 ::= { capwapDot11WlanBindEntry 2 } 811 -- End of capwapDot11WlanBindTable Table 813 -- Module compliance 815 capwapDot11Groups OBJECT IDENTIFIER 816 ::= { capwapDot11Conformance 1 } 818 capwapDot11Compliances OBJECT IDENTIFIER 819 ::= { capwapDot11Conformance 2 } 821 capwapDot11Compliance MODULE-COMPLIANCE 822 STATUS current 823 DESCRIPTION 824 "Describes the requirements for conformance to the 825 CAPWAP-DOT11-MIB." 827 MODULE -- this module 828 MANDATORY-GROUPS { 829 capwapDot11WlanConfigGroup, 830 capwapDot11WlanBindGroup 831 } 832 ::= { capwapDot11Compliances 1 } 834 capwapDot11WlanConfigGroup OBJECT-GROUP 835 OBJECTS { 836 capwapDot11WlanServiceIfIndex, 837 capwapDot11WlanMacType, 838 capwapDot11WlanTunnelMode, 839 capwapDot11WlanConfigRowStatus 840 } 841 STATUS current 842 DESCRIPTION 843 "The collection of objects which are used to configure 844 property of WLAN." 845 ::= { capwapDot11Groups 1 } 847 capwapDot11WlanBindGroup OBJECT-GROUP 848 OBJECTS { 849 capwapDot11WlanBssIfIndex, 850 capwapDot11WlanBssRowStatus 851 } 852 STATUS current 853 DESCRIPTION 854 "The collection of objects which are used to configure 855 WLAN BSS." 856 ::= { capwapDot11Groups 2 } 858 END 860 10. Security Considerations 862 There are a number of management objects defined in this MIB module 863 with a MAX-ACCESS clause of read-write and/or read-create. Such 864 objects may be considered sensitive or vulnerable in some network 865 environments. The support for SET operations in a non-secure 866 environment without proper protection can have a negative effect on 867 network operations. The followings are the tables and objects and 868 their sensitivity/vulnerability: 870 o - Unauthorized changes to the capwapDot11WlanConfigTable and 871 capwapDot11WlanBindTable may disrupt allocation of resources in 872 the network, also change the behavior of WLAN system such as MAC 873 type. 875 SNMP versions prior to SNMPv3 did not include adequate security. 876 Even if the network itself is secure (for example by using IPSec), 877 even then, there is no control as to who on the secure network is 878 allowed to access and GET/SET (read/change/create/delete) the objects 879 in this MIB module. 881 It is RECOMMENDED that implementers consider the security features as 882 provided by the SNMPv3 framework (see [RFC3410], section 8), 883 including full support for the SNMPv3 cryptographic mechanisms (for 884 authentication and privacy). 886 Further, deployment of SNMP versions prior to SNMPv3 is NOT 887 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 888 enable cryptographic security. It is then a customer/operator 889 responsibility to ensure that the SNMP entity giving access to an 890 instance of this MIB module is properly configured to give access to 891 the objects only to those principals (users) that have legitimate 892 rights to indeed GET or SET (change/create/delete) them. 894 11. IANA Considerations 896 11.1. IANA Considerations for CAPWAP-DOT11-MIB 898 The MIB module in this document uses the following IANA-assigned 899 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 901 Descriptor OBJECT IDENTIFIER value 902 ---------- ----------------------- 904 capwapDot11MIB { mib-2 XXX } 906 11.2. IANA Considerations for ifType 908 Require IANA to assign a ifType for 'WLAN Service Interface' type. 910 Require IANA to assign a ifType for 'WLAN BSS Interface' type. 912 12. Contributors 914 This MIB is based on contributions from Long Gao. 916 13. Acknowledgements 918 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 919 Dutta, Yujin Zhao, Haitao Zhang. 921 14. References 923 14.1. Normative References 925 [RFC2119] Bradner, S., "Key words 926 for use in RFCs to 927 Indicate Requirement 928 Levels", BCP 14, 929 RFC 2119, March 1997. 931 [RFC2578] McCloghrie, K., Ed., 932 Perkins, D., Ed., and 933 J. Schoenwaelder, Ed., 934 "Structure of 935 Management Information 936 Version 2 (SMIv2)", 937 STD 58, RFC 2578, 938 April 1999. 940 [RFC2579] McCloghrie, K., Ed., 941 Perkins, D., Ed., and 942 J. Schoenwaelder, Ed., 943 "Textual Conventions 944 for SMIv2", STD 58, 945 RFC 2579, April 1999. 947 [RFC2580] McCloghrie, K., 948 Perkins, D., and J. 949 Schoenwaelder, 950 "Conformance Statements 951 for SMIv2", STD 58, 952 RFC 2580, April 1999. 954 [RFC2863] McCloghrie, K. and F. 955 Kastenholz, "The 956 Interfaces Group MIB", 957 RFC 2863, June 2000. 959 [RFC3418] Presuhn, R., 960 "Management Information 961 Base (MIB) for the 962 Simple Network 963 Management Protocol 964 (SNMP)", STD 62, 965 RFC 3418, 966 December 2002. 968 [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., 969 Elliott, C., and Y. 970 Zhang, "CAPWAP Protocol 971 Base MIB", draft-ietf- 972 capwap-base-mib-01 973 (work in progress), 974 October 2008. 976 [I-D.ietf-capwap-protocol-specification] Montemurro, M., 977 Stanley, D., and P. 978 Calhoun, "CAPWAP 979 Protocol 980 Specification", draft- 981 ietf-capwap-protocol- 982 specification-14 (work 983 in progress), 984 October 2008. 986 [I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M., 987 Stanley, D., and P. 988 Calhoun, "CAPWAP 989 Protocol Binding for 990 IEEE 802.11", draft- 991 ietf-capwap-protocol- 992 binding-ieee80211-11 993 (work in progress), 994 October 2008. 996 14.2. Informative References 998 [RFC3410] Case, J., Mundy, R., 999 Partain, D., and B. 1000 Stewart, "Introduction 1001 and Applicability 1002 Statements for 1003 Internet-Standard 1004 Management Framework", 1005 RFC 3410, 1006 December 2002. 1008 Authors' Addresses 1010 Yang Shi (editor) 1011 H3C Tech. Co., Ltd 1012 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 1013 Beijing 1014 China(100085) 1016 Phone: +86 010 82775276 1017 EMail: young@h3c.com 1019 David Perkins (editor) 1020 SNMPinfo 1021 288 Quailbrook Ct San Carlos, 1022 CA 94070 1023 USA 1025 Phone: +1 408 394-8702 1026 EMail: dperkins@snmpinfo.com 1027 Chris Elliott (editor) 1028 Cisco Systems, Inc. 1029 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 1030 27709 1031 USA 1033 Phone: +1 919-392-2146 1034 EMail: chelliot@cisco.com 1036 Yong Zhang (editor) 1037 Fortinet, Inc. 1038 1090 Kifer Road 1039 Sunnyvale, CA 94086 1040 USA 1042 EMail: yzhang@fortinet.com 1044 Full Copyright Statement 1046 Copyright (C) The IETF Trust (2008). 1048 This document is subject to the rights, licenses and restrictions 1049 contained in BCP 78, and except as set forth therein, the authors 1050 retain all their rights. 1052 This document and the information contained herein are provided on an 1053 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1054 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1055 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1056 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1057 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1058 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1060 Intellectual Property 1062 The IETF takes no position regarding the validity or scope of any 1063 Intellectual Property Rights or other rights that might be claimed to 1064 pertain to the implementation or use of the technology described in 1065 this document or the extent to which any license under such rights 1066 might or might not be available; nor does it represent that it has 1067 made any independent effort to identify any such rights. Information 1068 on the procedures with respect to rights in RFC documents can be 1069 found in BCP 78 and BCP 79. 1071 Copies of IPR disclosures made to the IETF Secretariat and any 1072 assurances of licenses to be made available, or the result of an 1073 attempt made to obtain a general license or permission for the use of 1074 such proprietary rights by implementers or users of this 1075 specification can be obtained from the IETF on-line IPR repository at 1076 http://www.ietf.org/ipr. 1078 The IETF invites any interested party to bring to its attention any 1079 copyrights, patents or patent applications, or other proprietary 1080 rights that may cover technology that may be required to implement 1081 this standard. Please address the information to the IETF at 1082 ietf-ipr@ietf.org.