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