Internet Engineering Task Force (IETF) Y. Shi, Ed.
Request for Comments: 5834 Hangzhou H3C Tech. Co., Ltd.
Category: Informational D. Perkins, Ed.
ISSN: 2070-1721 C. Elliott, Ed.
Internet Engineering Task Force (IETF) Y. Shi, Ed.
Request for Comments: 5834 Hangzhou H3C Tech. Co., Ltd.
Category: Informational D. Perkins, Ed.
ISSN: 2070-1721 C. Elliott, Ed.
Y. Zhang, Ed. Fortinet, Inc. May 2010
张勇，Ed.Fortinet，Inc.2010年5月
Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding MIB for IEEE 802.11
IEEE 802.11无线接入点（CAPWAP）协议绑定MIB的控制和配置
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it describes managed objects for modeling the Control And Provisioning of Wireless Access Points (CAPWAP) protocol for IEEE 802.11 wireless binding. This MIB module is presented as a basis for future work on the management of the CAPWAP protocol using the Simple Network Management Protocol (SNMP).
此备忘录定义了用于网络管理协议的管理信息库（MIB）的一部分。特别是，它描述了用于为IEEE 802.11无线绑定的无线接入点（CAPWAP）协议的控制和供应建模的托管对象。此MIB模块是使用简单网络管理协议（SNMP）管理CAPWAP协议的未来工作的基础。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5834.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5834.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. WLAN Profile . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5
5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6
6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7
7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7
7.4. Relationship to MIB Module in the IEEE 802.11 Standard . . 8
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 21
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 22
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 22
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
14.2. Informative References . . . . . . . . . . . . . . . . . . 24
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. WLAN Profile . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5
5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6
6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7
7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7
7.4. Relationship to MIB Module in the IEEE 802.11 Standard . . 8
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 21
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 22
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 22
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
14.2. Informative References . . . . . . . . . . . . . . . . . . 24
The CAPWAP protocol [RFC5415] defines a standard, interoperable protocol, which enables an Access Controller (AC) to manage a collection of Wireless Termination Points (WTPs). CAPWAP supports the use of various wireless technologies by the WTPs, with one specified in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416].
CAPWAP协议[RFC5415]定义了一个标准的、可互操作的协议，该协议使接入控制器（AC）能够管理无线终端点（WTP）的集合。CAPWAP支持WTP使用各种无线技术，其中一种在IEEE 802.11[RFC5416]的CAPWAP协议绑定中指定。
This document defines a MIB module that can be used to manage CAPWAP implementations for IEEE 802.11 wireless binding. This MIB module covers both configuration for Wireless Local Area Network (WLAN) and a way to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. It is presented as a basis for future work on the SNMP management of the CAPWAP protocol.
本文档定义了一个MIB模块，可用于管理IEEE 802.11无线绑定的CAPWAP实现。该MIB模块包括无线局域网（WLAN）的配置和重用IEEE 802.11 MIB模块的方法[IEEE.802-11.2007]。它是CAPWAP协议SNMP管理未来工作的基础。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This document uses terminology from the CAPWAP protocol specification [RFC5415], the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416], and the CAPWAP Protocol Base MIB [RFC5833].
本文档使用CAPWAP协议规范[RFC5415]、IEEE 802.11的CAPWAP协议绑定[RFC5416]和CAPWAP协议基础MIB[RFC5833]中的术语。
Access Controller (AC): The network entity that provides WTP access to the network infrastructure in the data plane, control plane, management plane, or a combination therein.
访问控制器（AC）：提供WTP访问数据平面、控制平面、管理平面或其中组合中网络基础设施的网络实体。
Wireless Termination Point (WTP): The physical or network entity that contains an RF antenna and wireless physical layer (PHY) to transmit and receive station traffic for wireless access networks.
无线终端点（WTP）：包含RF天线和无线物理层（PHY）的物理或网络实体，用于发送和接收无线接入网络的站点流量。
Control And Provisioning of Wireless Access Points (CAPWAP): It is a generic protocol defining AC and WTP control and data plane communication via a CAPWAP protocol transport mechanism. CAPWAP control messages, and optionally CAPWAP data messages, are secured using Datagram Transport Layer Security (DTLS) [RFC4347].
无线接入点的控制和供应（CAPWAP）：它是一种通用协议，通过CAPWAP协议传输机制定义AC和WTP控制和数据平面通信。CAPWAP控制消息和可选的CAPWAP数据消息使用数据报传输层安全性（DTLS）[RFC4347]进行保护。
CAPWAP Control Channel: A bi-directional flow defined by the AC IP Address, WTP IP Address, AC control port, WTP control port, and the transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control packets are sent and received.
CAPWAP控制通道：由AC IP地址、WTP IP地址、AC控制端口、WTP控制端口和传输层协议（UDP或UDP Lite）定义的双向流，通过该协议发送和接收CAPWAP控制数据包。
CAPWAP Data Channel: A bi-directional flow defined by the AC IP Address, WTP IP Address, AC data port, WTP data port, and the transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data packets are sent and received.
CAPWAP数据通道：由AC IP地址、WTP IP地址、AC数据端口、WTP数据端口和传输层协议（UDP或UDP Lite）定义的双向流，通过该协议发送和接收CAPWAP数据包。
Station (STA): A device that contains an interface to a wireless medium (WM).
工作站（STA）：包含无线媒体（WM）接口的设备。
Split and Local MAC: The CAPWAP protocol supports two modes of operation: Split and Local MAC (medium access control). In Split MAC mode, all Layer 2 wireless data and management frames are encapsulated via the CAPWAP protocol and exchanged between the AC and the WTPs. The Local MAC mode of operation allows the data frames to be either locally bridged or tunneled as 802.3 frames.
拆分和本地MAC:CAPWAP协议支持两种操作模式：拆分和本地MAC（介质访问控制）。在拆分MAC模式下，所有第2层无线数据和管理帧通过CAPWAP协议封装，并在AC和WTP之间交换。本地MAC操作模式允许数据帧作为802.3帧进行本地桥接或隧道传输。
Wireless Binding: The CAPWAP protocol is independent of a specific WTP radio technology, as well its associated wireless link layer protocol. Elements of the CAPWAP protocol are designed to accommodate the specific needs of each wireless technology in a standard way. Implementation of the CAPWAP protocol for a particular wireless technology MUST define a binding protocol for it, e.g., the binding for IEEE 802.11, provided in [RFC5416].
无线绑定：CAPWAP协议独立于特定的WTP无线电技术及其相关的无线链路层协议。CAPWAP协议的元素旨在以标准方式满足每种无线技术的特定需求。特定无线技术的CAPWAP协议的实施必须为其定义绑定协议，例如[RFC5416]中提供的IEEE 802.11绑定。
Wireless Local Area Network (WLAN): A WLAN refers to a logical component instantiated on a WTP device. A single physical WTP MAY operate a number of WLANs. Each Basic Service Set Identifier (BSSID) and its constituent wireless terminal radios are denoted as a distinct WLAN on a physical WTP. To support a physical WTP with multiple WLANs is an important feature for CAPWAP protocol's 802.11 binding, and it is also for MIB module design.
无线局域网（WLAN）：WLAN是指WTP设备上实例化的逻辑组件。单个物理WTP可以操作多个wlan。每个基本服务集标识符（BSSID）及其组成的无线终端无线电在物理WTP上表示为不同的WLAN。支持具有多个WLAN的物理WTP是CAPWAP协议802.11绑定的一个重要功能，也是MIB模块设计的一个重要功能。
Wireless Binding MIB Module: Other Standards Development Organizations (SDOs), such as IEEE, already defined MIB modules for specific wireless technologies, e.g., the IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are called wireless binding MIB modules.
无线绑定MIB模块：其他标准开发组织（SDO），如IEEE，已经为特定无线技术定义了MIB模块，例如IEEE 802.11 MIB模块[IEEE.802-11.2007]。这种MIB模块称为无线绑定MIB模块。
CAPWAP Protocol Wireless Binding MIB Module: It is a MIB module corresponding to the CAPWAP Protocol Binding for a wireless binding. Sometimes, not all the technology-specific message elements in a CAPWAP binding protocol have MIB objects defined by other SDOs. For example, the protocol of [RFC5416] defines WLAN conception. Also, Local or Split MAC modes could be specified for a WLAN. The MAC mode for a WLAN is not in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in addition to the existing wireless binding MIB modules defined by other SDOs, a CAPWAP protocol wireless binding MIB module is required to be defined for a wireless binding.
CAPWAP协议无线绑定MIB模块：是与无线绑定的CAPWAP协议绑定相对应的MIB模块。有时，CAPWAP绑定协议中并非所有特定于技术的消息元素都具有由其他SDO定义的MIB对象。例如，[RFC5416]的协议定义了WLAN的概念。此外，可以为WLAN指定本地或分割MAC模式。WLAN的MAC模式不在IEEE 802.11[IEEE.802-11.2007]的范围内。在这种情况下，除了其他SDO定义的现有无线绑定MIB模块外，还需要为无线绑定定义CAPWAP协议无线绑定MIB模块。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
A WLAN profile stores configuration parameters such as MAC type and tunnel mode for a WLAN. Each WLAN profile is identified by a profile identifier. The operator needs to create WLAN profiles before WTPs connect to the AC. To provide WLAN service, the operator SHOULD bind WLAN profiles to a WTP Virtual Radio Interface that corresponds to a PHY radio. During the binding operation, the AC MUST select an unused WLAN ID between 1 and 16 [RFC5416]. For example, to bind one more WLAN profile to a radio that has been bound with a WLAN profile, the AC SHOULD allocate WLAN ID 2 to the radio. Although the maximum value of a WLAN ID is 16, the operator could configure more than 16 WLAN Profiles on the AC.
WLAN配置文件存储配置参数，例如WLAN的MAC类型和隧道模式。每个WLAN配置文件由配置文件标识符标识。在WTP连接到AC之前，运营商需要创建WLAN配置文件。为了提供WLAN服务，运营商应将WLAN配置文件绑定到对应于物理层无线电的WTP虚拟无线电接口。在绑定操作期间，AC必须选择介于1和16之间的未使用WLAN ID[RFC5416]。例如，要将一个或多个WLAN配置文件绑定到已绑定WLAN配置文件的收音机，AC应将WLAN ID 2分配给该收音机。尽管WLAN ID的最大值为16，但操作员可以在AC上配置16个以上的WLAN配置文件。
The IEEE 802.11 MIB module [IEEE.802-11.2007] already defines MIB objects for most IEEE 802.11 Message Elements in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416]. As a CAPWAP protocol 802.11 binding MIB module, the CAPWAP-DOT11-MIB module MUST be able to reuse such MIB objects in the IEEE 802.11 MIB module and support functions (such as MAC mode for WLAN in the [RFC5416]) that are not in the scope of IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST support such functions.
IEEE 802.11 MIB模块[IEEE.802-11.2007]已经为IEEE 802.11[RFC5416]的CAPWAP协议绑定中的大多数IEEE 802.11消息元素定义了MIB对象。作为CAPWAP协议802.11绑定MIB模块，CAPWAP-DOT11-MIB模块必须能够在IEEE 802.11 MIB模块中重用此类MIB对象，并支持不在IEEE 802.11标准范围内的功能（如[RFC5416]中WLAN的MAC模式）。CAPWAP-DOT11-MIB模块必须支持此类功能。
In summary, the CAPWAP-DOT11-MIB module needs to support:
总之，CAPWAP-DOT11-MIB模块需要支持：
- Reuse of wireless binding MIB modules in the IEEE 802.11 standard;
- 在IEEE 802.11标准中重用无线绑定MIB模块；
- Centralized management and configuration of WLAN profiles on the AC;
- 集中管理和配置AC上的WLAN配置文件；
- Configuration of a MAC type and tunnel mode for a specific WLAN profile.
- 为特定WLAN配置文件配置MAC类型和隧道模式。
In the IEEE 802.11 MIB module, the MIB tables such as dot11AuthenticationAlgorithmsTable are able to support WLAN configuration (such as authentication algorithm), and these tables use the ifIndex as the index which works well in the autonomous WLAN architecture.
在IEEE 802.11 MIB模块中，MIB表（如dot11AuthenticationAlgorithmsTable）能够支持WLAN配置（如身份验证算法），并且这些表使用ifIndex作为索引，该索引在自主WLAN体系结构中运行良好。
Reuse of such wireless binding MIB modules is very important to centralized WLAN architectures. The key point is to abstract a WLAN profile as a WLAN Profile Interface on the AC, which could be identified by an ifIndex. The MIB objects in the IEEE 802.11 MIB module which are associated with this interface can be used to configure WLAN parameters for the WLAN, such as authentication algorithm. With the ifIndex of a WLAN Profile Interface, the AC is able to reuse the IEEE 802.11 MIB module.
这种无线绑定MIB模块的重用对于集中式WLAN架构非常重要。关键点是将WLAN配置文件抽象为AC上的WLAN配置文件接口，该接口可以通过ifIndex识别。IEEE 802.11 MIB模块中与此接口关联的MIB对象可用于为WLAN配置WLAN参数，例如身份验证算法。通过WLAN配置文件接口的iIndex，AC能够重用IEEE 802.11 MIB模块。
In the CAPWAP-BASE-MIB module, each PHY radio is identified by a WTP ID and a radio ID, and has a corresponding WTP Virtual Radio Interface on the AC. The IEEE 802.11 MIB module associated with this interface can be used to configure IEEE 802.11 wireless binding parameters for the radio such as RTS Threshold. A WLAN Basic Service Set (BSS) Interface, created by binding a WLAN to a WTP Virtual Radio Interface, is used for data forwarding.
在CAPWAP-BASE-MIB模块中，每个PHY无线电由WTP ID和无线电ID标识，并在AC上具有相应的WTP虚拟无线电接口。与此接口相关联的IEEE 802.11 MIB模块可用于为无线电配置IEEE 802.11无线绑定参数，如RTS阈值。通过将WLAN绑定到WTP虚拟无线电接口创建的WLAN基本服务集（BSS）接口用于数据转发。
The MIB objects are derived from the CAPWAP protocol binding for IEEE 802.11 document [RFC5416].
MIB对象源自IEEE 802.11文档[RFC5416]的CAPWAP协议绑定。
capwapDot11WlanTable
capwapDot11WlanTable
The table allows the operator to display and configure WLAN profiles, such as specifying the MAC type and tunnel mode for a WLAN. Also, it helps the AC to configure a WLAN through the IEEE 802.11 MIB module.
该表允许操作员显示和配置WLAN配置文件，例如指定WLAN的MAC类型和隧道模式。此外，它还帮助AC通过IEEE 802.11 MIB模块配置WLAN。
capwapDot11WlanBindTable
capwapDot11WlanBindTable
The table provides a way to bind WLAN profiles to a WTP Virtual Radio Interface, which has a corresponding PHY radio. A binding operation dynamically creates a WLAN BSS Interface, which is used for data forwarding.
该表提供了将WLAN配置文件绑定到WTP虚拟无线电接口的方法，该接口具有相应的PHY无线电。绑定操作动态创建用于数据转发的WLAN BSS接口。
The CAPWAP-DOT11-MIB module does not duplicate the objects of the 'system' group in the SNMPv2-MIB [RFC3418] that is defined as being mandatory for all systems, and the objects apply to the entity as a whole. The 'system' group provides identification of the management entity and certain other system-wide data.
CAPWAP-DOT11-MIB模块不会复制SNMPv2 MIB[RFC3418]中定义为所有系统必需的“系统”组的对象，这些对象作为一个整体应用于实体。“系统”组提供管理实体和某些其他系统范围数据的标识。
The Interfaces Group [RFC2863] defines generic managed objects for managing interfaces. This memo contains the media-specific extensions to the Interfaces Group for managing WLAN that are modeled as interfaces.
接口组[RFC2863]定义了用于管理接口的通用托管对象。此备忘录包含接口组的媒体特定扩展，用于管理建模为接口的WLAN。
Each WLAN profile corresponds to a WLAN Profile Interface on the AC. The interface MUST be modeled as an ifEntry, and ifEntry objects such as ifIndex, ifDescr, ifName, and ifAlias are to be used as per [RFC2863]. The WLAN Profile Interface provides a way to configure IEEE 802.11 parameters for a specific WLAN and reuse the IEEE 802.11 MIB module.
每个WLAN配置文件对应于AC上的WLAN配置文件接口。该接口必须建模为ifEntry，并且ifEntry对象（如ifIndex、ifDescr、ifName和ifAlias）将按照[RFC2863]使用。WLAN配置文件接口提供了为特定WLAN配置IEEE 802.11参数和重用IEEE 802.11 MIB模块的方法。
To provide data forwarding service, the AC dynamically creates WLAN BSS Interfaces. A WLAN BSS Interface MUST be modeled as an ifEntry, and ifEntry objects such as ifIndex, ifDescr, ifName, and ifAlias are to be used as per [RFC2863]. The interface enables a single physical WTP to support multiple WLANs.
为了提供数据转发服务，AC动态创建WLAN BSS接口。WLAN BSS接口必须建模为ifEntry，ifEntry对象（如ifIndex、ifDescr、ifName和ifAlias）将按照[RFC2863]使用。该接口使单个物理WTP能够支持多个WLAN。
Also, the AC MUST have a mechanism that preserves the value of the ifIndexes (of both the WLAN Profile Interfaces and the WLAN BSS Interfaces) in the ifTable at AC reboot.
此外，AC必须具有在AC重新启动时保留ifTable中IFIndex（WLAN配置文件接口和WLAN BSS接口）值的机制。
The CAPWAP-BASE-MIB module provides a way to manage and control WTP and radio objects. Especially, it provides the WTP Virtual Radio Interface mechanism to enable the AC to reuse the IEEE 802.11 MIB module. With this mechanism, an operator could configure an IEEE
CAPWAP-BASE-MIB模块提供了一种管理和控制WTP和无线电对象的方法。特别是，它提供了WTP虚拟无线电接口机制，使AC能够重用IEEE 802.11 MIB模块。通过这种机制，操作员可以配置IEEE
802.11 radio's parameters and view the radio's traffic statistics on the AC. Based on the CAPWAP-BASE-MIB module, the CAPWAP-DOT11-MIB module provides more WLAN information.
802.11无线电参数并查看AC上的无线电通信统计数据。基于CAPWAP-BASE-MIB模块，CAPWAP-DOT11-MIB模块提供更多WLAN信息。
With the ifIndex of WLAN Profile Interface and WLAN BSS Interface, the MIB module is able to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. The CAPWAP-DOT11-MIB module does not duplicate those objects in the IEEE 802.11 MIB module.
通过WLAN配置文件接口和WLAN BSS接口的iIndex，MIB模块能够重用IEEE 802.11 MIB模块[IEEE.802-11.2007]。CAPWAP-DOT11-MIB模块不会复制IEEE 802.11 MIB模块中的这些对象。
The CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] involves some of the MIB objects defined in the IEEE 802.11 standard. Although CAPWAP-DOT11-MIB module uses it [RFC5416] as a reference, it could reuse all the MIB objects in the IEEE 802.11 standard , and is not limited by the scope of CAPWAP Protocol Binding for IEEE 802.11.
IEEE 802.11的CAPWAP协议绑定[RFC5416]涉及IEEE 802.11标准中定义的一些MIB对象。尽管CAPWAP-DOT11-MIB模块使用它[RFC5416]作为参考，但它可以重用IEEE 802.11标准中的所有MIB对象，并且不受IEEE 802.11 CAPWAP协议绑定范围的限制。
The following MIB modules are required for IMPORTS: SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], and CAPWAP-BASE-MIB [RFC5833].
导入需要以下MIB模块：SNMPv2 SMI[RFC2578]、SNMPv2 TC[RFC2579]、SNMPv2 CONF[RFC2580]、IF-MIB[RFC2863]和CAPWAP-BASE-MIB[RFC5833]。
1) Create a WTP profile.
1) 创建WTP配置文件。
Suppose the WTP's base MAC address is '00:01:01:01:01:00'. Creates a WTP profile for it through the capwapBaseWtpProfileTable [RFC5833] as follows:
假设WTP的基本MAC地址为“00:01:01:01:01:00”。通过capwapBaseWtpProfileTable[RFC5833]为其创建WTP配置文件，如下所示：
In capwapBaseWtpProfileTable { capwapBaseWtpProfileId = 1, capwapBaseWtpProfileName = 'WTP Profile 123456', capwapBaseWtpProfileWtpMacAddress = '00:01:01:01:01:00', capwapBaseWtpProfileWTPModelNumber = 'WTP123', capwapBaseWtpProfileWtpName = 'WTP 123456', capwapBaseWtpProfileWtpLocation = 'office', capwapBaseWtpProfileWtpStaticIpEnable = true(1), capwapBaseWtpProfileWtpStaticIpType = ipv4(1), capwapBaseWtpProfileWtpStaticIpAddress = '192.0.2.10', capwapBaseWtpProfileWtpNetmask = '255.255.255.0', capwapBaseWtpProfileWtpGateway = '192.0.2.1', capwapBaseWtpProfileWtpFallbackEnable = true(1), capwapBaseWtpProfileWtpEchoInterval = 30, capwapBaseWtpProfileWtpIdleTimeout = 300, capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
在capwapBaseWtpProfileTable{capwapBaseWtpProfileId=1中，capwapBaseWtpProfileName='WTP Profile 123456'，CapwapBaseWTPProfileUpmacAddress='00:01:01:00'，StaticCapwapBaseWTPProfileUpModelNumber='WTP123'，CapwapBaseWTPProfileUpName='WTP 123456'，CapwapBaseWTPProfileUpLocation='office'，CapwapBaseWTPProfileUpipleUpportEnable=true（1），CapwapBaseWTPProfileUpStaticIPType=ipv4（1），CapwapBaseWTPProfileUpStaticIPAddress='192.0.2.10'，CapwapBaseWTPProfileUpNetMask='255.255.0'，CapwapBaseWTPProfileUpGateway='192.0.2.1'，CapwapBaseWTPProfileUpFallbackEnable=true（1），capwapbbasewtpprofilewtpechointerval=30，capwapbbasewtpprofilewtpidletimeout=300，capwapbbasewtpprofilewtmpaxdiscoveryinterval=20，
capwapBaseWtpProfileWtpReportInterval = 120, capwapBaseWtpProfileWtpStatisticsTimer = 120, capwapBaseWtpProfileWtpEcnSupport = limited(0) }
CapwapBaseWTPProfileUpReportInterval=120，CapwapBaseWTPProfileUpStatisticsTimer=120，CapwapBaseWTPProfileUppecnSupport=limited（0）}
Suppose the WTP with model number 'WTP123' has one PHY radio and this PHY radio is identified by ID 1. The creation of this WTP profile triggers the AC to automatically create a WTP Virtual Radio Interface and add a new row object to the capwapBaseWirelessBindingTable without manual intervention. Suppose the ifIndex of the WTP Virtual Radio Interface is 10. The following information is stored in the capwapBaseWirelessBindingTable.
假设型号为“WTP123”的WTP有一个PHY无线电，该PHY无线电由ID 1标识。创建此WTP配置文件会触发AC自动创建WTP虚拟无线电接口，并在无需手动干预的情况下向CapwapBaseWirelessBinding表添加新的行对象。假设WTP虚拟无线电接口的ifIndex为10。以下信息存储在CapwapBaseWirelessBinding表中。
In capwapBaseWirelessBindingTable
{
capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2)
}
In capwapBaseWirelessBindingTable
{
capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2)
}
The WTP Virtual Radio Interfaces on the AC correspond to the PHY radios on the WTP. The WTP Virtual Radio Interface is modeled by ifTable [RFC2863].
AC上的WTP虚拟无线电接口对应于WTP上的PHY无线电。WTP虚拟无线电接口由ifTable[RFC2863]建模。
In ifTable
{
ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface',
ifType = 254,
ifMtu = 0,
ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1),
ifOperStatus = false(0),
ifLastChange = 0,
ifInOctets = 0,
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
In ifTable
{
ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface',
ifType = 254,
ifMtu = 0,
ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1),
ifOperStatus = false(0),
ifLastChange = 0,
ifInOctets = 0,
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
2) Query the ifIndexes of WTP Virtual Radio Interfaces.
2) 查询WTP虚拟无线电接口的IFIndex。
Before configuring PHY radios, the operator needs to get the ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY radios.
在配置PHY无线电之前，操作员需要获取与PHY无线电相对应的WTP虚拟无线电接口的IFIndex。
As the capwapBaseWirelessBindingTable already stores the mappings between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio Interfaces, the operator can get the ifIndex information by querying this table. Such a query operation SHOULD run from radio ID 1 to radio ID 31 (according to [RFC5415]), and stop when an invalid ifIndex value (0) is returned.
由于capwapBaseWirelessBindingTable已经存储了物理层无线电（无线电ID）和WTP虚拟无线电接口的ifIndex之间的映射，操作员可以通过查询该表来获取ifIndex信息。这种查询操作应该从无线电ID 1运行到无线电ID 31（根据[RFC5415]），并在返回无效的ifIndex值（0）时停止。
This example uses capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 1 as inputs to query the capwapBaseWirelessBindingTable, and gets capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, and gets an invalid ifIndex value (0), so the query operation ends. This method gets not only the ifIndexes of WTP Virtual Radio Interfaces, but also the numbers of PHY radios. Besides checking whether the ifIndex value is valid, the operator SHOULD check whether the capwapBaseWirelessBindingType is the desired binding type.
此示例使用capwapBaseWtpProfileId=1和capwapBaseWirelessBindingRadioId=1作为输入来查询capwapBaseWirelessBindingTable，并获取capwapBaseWirelessBindingVirtualRadioIfIndex=10。然后它使用capwapBaseWtpProfileId=1和capwapBaseWirelessBindingRadioId=2，并获取无效的ifIndex值（0），因此查询操作结束。该方法不仅可以获取WTP虚拟无线电接口的IFIndex，还可以获取PHY无线电的数量。除了检查ifIndex值是否有效外，操作员还应检查capwapBaseWirelessBindingType是否为所需的绑定类型。
3) Configure IEEE 802.11 parameters for a WTP Virtual Radio Interface
3) 为WTP虚拟无线电接口配置IEEE 802.11参数
This configuration is made on the AC through the IEEE 802.11 MIB module.
此配置通过IEEE 802.11 MIB模块在AC上进行。
The following shows an example of configuring parameters for a WTP Virtual Radio Interface with ifIndex 10 through the dot11OperationTable [IEEE.802-11.2007].
下面显示了通过dot11OperationTable[IEEE.802-11.2007]为具有ifIndex 10的WTP虚拟无线电接口配置参数的示例。
In dot11OperationTable { ifIndex = 10, dot11MACAddress = '00:00:00:00:00:00', dot11RTSThreshold = 2347, dot11ShortRetryLimit = 7, dot11LongRetryLimit = 4, dot11FragmentationThreshold = 256, dot11MaxTransmitMSDULifetime = 512, dot11MaxReceiveLifetime = 512, dot11ManufacturerID = 'capwap', dot11ProductID = 'capwap', dot11CAPLimit = 2, dot11HCCWmin = 0,
在DOT11操作表中{ifIndex=10，dot11MACAddress='00:00:00:00'，dot11RTSThreshold=2347，dot11ShortRetryLimit=7，dot11LongRetryLimit=4，DOT1FragmentationThreshold=256，DOT11MaxTransmitmDulifeTime=512，dot11MaxReceiveLifetime=512，DOT1ManufactureRid='capwap'，capwap=2，dot11HCCWmin=0，
dot11HCCWmax = 0, dot11HCCAIFSN = 1, dot11ADDBAResponseTimeout = 1, dot11ADDTSResponseTimeout = 1, dot11ChannelUtilizationBeaconInterval = 50, dot11ScheduleTimeout = 10, dot11DLSResponseTimeout = 10, dot11QAPMissingAckRetryLimit = 1, dot11EDCAAveragingPeriod = 5 }
dot11HCCWmax=0，dot11HCCAIFSN=1，Dot11AddBareSponsetTimeout=1，Dot11AddTSResponsetTimeout=1，dot11ChannelUtilizationBeaconInterval=50，dot11ScheduleTimeout=10，Dot11DlsResponsetTimeout=10，dot11QAPMissingAckRetryLimit=1，dot11EDCAAveragingPeriod=5}
4) Configure a WLAN Profile.
4) 配置WLAN配置文件。
WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB module, and IEEE 802.11 MIB module.
通过CAPWAP-DOT11-MIB模块和IEEE 802.11 MIB模块在AC上进行WLAN配置。
The first step is to create a WLAN Profile Interface through the CAPWAP-DOT11-MIB module on the AC.
第一步是通过AC上的CAPWAP-DOT11-MIB模块创建WLAN配置文件接口。
For example, when you configure a WLAN profile that is identified by capwapDot11WlanProfileId 1, the capwapDot11WlanTable creates the following row object for it.
例如，配置由capwapDot11WlanProfileId 1标识的WLAN配置文件时，capwapDot11WlanTable将为其创建以下行对象。
In capwapDot11WlanTable
{
capwapDot11WlanProfileId = 1,
capwapDot11WlanProfileIfIndex = 20,
capwapDot11WlanMacType = splitMAC(2),
capwapDot11WlanTunnelMode = dot3Tunnel(2),
capwapDot11WlanRowStatus = createAndGo(4)
}
In capwapDot11WlanTable
{
capwapDot11WlanProfileId = 1,
capwapDot11WlanProfileIfIndex = 20,
capwapDot11WlanMacType = splitMAC(2),
capwapDot11WlanTunnelMode = dot3Tunnel(2),
capwapDot11WlanRowStatus = createAndGo(4)
}
The creation of a row object triggers the AC to automatically create a WLAN Profile Interface and it is identified by ifIndex 20 without manual intervention.
创建行对象会触发AC自动创建WLAN配置文件接口，并由ifIndex 20识别，无需手动干预。
A WLAN Profile Interface MUST be modeled as an ifEntry on the AC that provides appropriate interface information. The capwapDot11WlanTable stores the mappings between capwapDot11WlanProfileIds and the ifIndexes of WLAN Profile Interfaces.
WLAN配置文件接口必须建模为AC上提供适当接口信息的ifEntry。capwapDot11WlanTable存储capwapDot11WlanProfileIds和WLAN配置文件接口的IFINDEX之间的映射。
In ifTable { ifIndex = 20, ifDescr = 'WLAN Profile Interface', ifType = 252, ifMtu = 0,
在ifTable{ifIndex=20中，ifDescr='WLAN配置文件接口'，ifType=252，ifMtu=0，
ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1),
ifOperStatus = true(1),
ifLastChange = 0,
ifInOctets = 0,
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1),
ifOperStatus = true(1),
ifLastChange = 0,
ifInOctets = 0,
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
The second step is to configure WLAN parameters for the WLAN Profile Interface through the IEEE 802.11 MIB module on the AC.
第二步是通过AC上的IEEE 802.11 MIB模块为WLAN配置文件接口配置WLAN参数。
The following example configures an authentication algorithm for a WLAN.
以下示例为WLAN配置身份验证算法。
In dot11AuthenticationAlgorithmsTable
{
ifIndex = 20,
dot11AuthenticationAlgorithmsIndex = 1,
dot11AuthenticationAlgorithm = Shared Key(2),
dot11AuthenticationAlgorithmsEnable = true(1)
}
In dot11AuthenticationAlgorithmsTable
{
ifIndex = 20,
dot11AuthenticationAlgorithmsIndex = 1,
dot11AuthenticationAlgorithm = Shared Key(2),
dot11AuthenticationAlgorithmsEnable = true(1)
}
Here, ifIndex 20 identifies the WLAN Profile Interface, and the index of the configured authentication algorithm is 1.
这里，ifIndex 20识别WLAN简档接口，并且所配置的认证算法的索引为1。
5) Bind WLAN Profiles to a WTP radio.
5) 将WLAN配置文件绑定到WTP收音机。
On the AC, the capwapDot11WlanBindTable in the CAPWAP-DOT11-MIB stores the bindings between WLAN profiles(identified by capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces (identified by the ifIndex).
在AC上，CAPWAP-DOT11-MIB中的capwapDot11WlanBindTable存储WLAN配置文件（由capwapDot11WlanProfileId标识）和WTP虚拟无线电接口（由ifIndex标识）之间的绑定。
For example, after the operator binds a WLAN profile with capwapDot11WlanProfileId 1 to WTP Virtual Radio Interface with ifIndex 10, the capwapDot11WlanBindTable creates the following row object.
例如，操作员将capwapDot11WlanProfileId为1的WLAN配置文件绑定到ifIndex为10的WTP虚拟无线电接口后，capwapDot11WlanBindTable将创建以下行对象。
In capwapDot11WlanBindTable
{
ifIndex = 10,
capwapDot11WlanProfileId = 1,
capwapDot11WlanBindBssIfIndex = 30,
capwapDot11WlanBindRowStatus = createAndGo(4)
}
In capwapDot11WlanBindTable
{
ifIndex = 10,
capwapDot11WlanProfileId = 1,
capwapDot11WlanBindBssIfIndex = 30,
capwapDot11WlanBindRowStatus = createAndGo(4)
}
If the capwapDot11WlanMacType of the WLAN is splitMAC(2), the creation of the row object in the capwapDot11WlanBindTable triggers the AC to automatically create a WLAN BSS Interface identified by ifIndex 30 without manual intervention.
如果WLAN的capwapDot11WlanMacType为splitMAC（2），则在capwapDot11WlanBindTable中创建行对象会触发AC自动创建由ifIndex 30标识的WLAN BSS接口，而无需手动干预。
The WLAN BSS Interface MUST be modeled as an ifEntry on the AC, which provides appropriate interface information. The capwapDot11WlanBindTable stores the mappings among the ifIndex of a WTP Virtual Radio Interface, WLAN profile ID, WLAN ID, and the ifIndex of a WLAN BSS Interface.
WLAN BSS接口必须建模为AC上的ifEntry，它提供适当的接口信息。capwapDot11WlanBindTable存储WTP虚拟无线电接口的ifIndex、WLAN配置文件ID、WLAN ID和WLAN BSS接口的ifIndex之间的映射。
6) Get the current configuration status report from the WTP to the AC.
6) 从WTP向AC获取当前配置状态报告。
Before a WTP that has joined the AC gets configuration from the AC, it needs to report its current configuration status by sending a configuration status request message to the AC, which uses the message to update corresponding MIB objects on the AC. For example, for ifIndex 10 (which identifies a WLAN Virtual Radio Interface), its ifOperStatus in the ifTable is updated according to the current radio operational status in the CAPWAP message [RFC5415].
在加入AC的WTP从AC获取配置之前，它需要通过向AC发送配置状态请求消息来报告其当前配置状态，AC使用该消息更新AC上的相应MIB对象。例如，对于ifIndex 10（识别WLAN虚拟无线电接口），根据CAPWAP消息[RFC5415]中的当前无线电操作状态，更新ifTable中的IFOperaStatus。
7) Query WTP and radio statistical data.
7) 查询WTP和无线电统计数据。
After WTPs start to run, the operator could query WTP and radio statistics data through the CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB modules. For example, through the dot11CountersTable [IEEE.802-11.2007], the operator could query counter data of a radio that is identified by the ifIndex of the corresponding WLAN Virtual Radio Interface.
WTPs开始运行后，操作员可以通过CAPWAP-BASE-MIB和CAPWAP-DOT11-MIB模块查询WTP和无线电统计数据。例如，通过dot11CountersTable[IEEE.802-11.2007]，运营商可以查询由相应WLAN虚拟无线电接口的ifIndex标识的无线电的计数器数据。
8) Query other statistical data.
8) 查询其他统计数据。
The operator could query the configuration of a WLAN through the dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and the statistical data of a WLAN BSS Interface through the ifTable [RFC2863].
运营商可以通过dot11AuthenticationAlgorithmsTable[IEEE.802-11.2007]查询WLAN的配置，并通过ifTable[RFC2863]查询WLAN BSS接口的统计数据。
CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN
CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN
IMPORTS RowStatus, TEXTUAL-CONVENTION FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 FROM SNMPv2-SMI ifIndex, InterfaceIndex FROM IF-MIB CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC FROM CAPWAP-BASE-MIB;
从SNMPv2 TC对象组导入行状态、文本约定、从SNMPv2 CONF导入模块符合性模块标识、对象类型、mib-2、从SNMPv2 SMI iIndex导入未签名32、从IF-mib CapwapBaseMacTypeTC导入接口索引、从CAPWAP-BASE-mib导入CAPWAPBASETUNNELMODEC；
capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "201004300000Z" -- 30 April 2010
ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO
"General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "201004300000Z" -- 30 April 2010
ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO
"General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi (editor) Hangzhou H3C Tech. Co., Ltd. Beijing R&D Center of H3C, Digital Technology Plaza NO. 9 Shangdi 9th Street, Haidian District Beijing 100085 China Phone: +86 010 82775276 Email: rishyang@gmail.com
杨石（编辑）杭州华三科技有限公司北京华三研发中心北京市海淀区上地九街9号数码科技广场100085中国电话：+86 010 82775276电子邮件：rishyang@gmail.com
David T. Perkins (editor) 228 Bayview Dr. San Carlos, CA 94070 USA Phone: +1 408 394-8702 Email: dperkins@dsperkins.com
David T.Perkins（编辑）228 Bayview美国加利福尼亚州圣卡洛斯博士94070电话：+1 408 394-8702电子邮件：dperkins@dsperkins.com
Chris Elliott (editor) 1516 Kent St. Durham, NC 27707 USA Phone: +1 919-308-1216 Email: chelliot@pobox.com
Chris Elliott（编辑）1516美国北卡罗来纳州肯特圣达勒姆市27707电话：+1 919-308-1216电子邮件：chelliot@pobox.com
Yong Zhang (editor) Fortinet, Inc. 1090 Kifer Road Sunnyvale, CA 94086 USA Email: yzhang@fortinet.com"
张勇（编辑）Fortinet，Inc.地址：美国加利福尼亚州森尼维尔基弗路1090号邮编：94086电子邮件：yzhang@fortinet.com"
DESCRIPTION "Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved.
描述“版权所有（c）2010 IETF信托基金和被确定为代码作者的人员。保留所有权利。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 5834; see the RFC itself for full legal notices.
此版本的MIB模块是RFC 5834的一部分；有关完整的法律通知，请参见RFC本身。
This MIB module contains managed object definitions for
CAPWAP Protocol binding for IEEE 802.11."
REVISION "201004300000Z"
DESCRIPTION
"Initial version, published as RFC 5834"
::= { mib-2 195 }
This MIB module contains managed object definitions for
CAPWAP Protocol binding for IEEE 802.11."
REVISION "201004300000Z"
DESCRIPTION
"Initial version, published as RFC 5834"
::= { mib-2 195 }
-- Textual conventions
--文本约定
CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a Wireless Local Area
Network (WLAN)."
SYNTAX Unsigned32 (1..16)
CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a Wireless Local Area
Network (WLAN)."
SYNTAX Unsigned32 (1..16)
CapwapDot11WlanIdProfileTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a WLAN profile."
SYNTAX Unsigned32 (1..512)
CapwapDot11WlanIdProfileTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a WLAN profile."
SYNTAX Unsigned32 (1..512)
-- Top level components of this MIB module
--此MIB模块的顶级组件
-- Tables, Scalars
--表、标量
capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 }
-- Conformance
capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 }
capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 }
-- Conformance
capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 }
-- capwapDot11WlanTable Table
--CAPWAPDOT11W可移植表
capwapDot11WlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that allows the operator to display and configure
WLAN profiles, such as specifying the MAC type and tunnel mode
for a WLAN. Also, it helps the AC to configure a WLAN through
the IEEE 802.11 MIB module.
Values of all objects in this table are persistent at
restart/reboot."
::= { capwapDot11Objects 1 }
capwapDot11WlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that allows the operator to display and configure
WLAN profiles, such as specifying the MAC type and tunnel mode
for a WLAN. Also, it helps the AC to configure a WLAN through
the IEEE 802.11 MIB module.
Values of all objects in this table are persistent at
restart/reboot."
::= { capwapDot11Objects 1 }
capwapDot11WlanEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that stores the settings of a WLAN profile."
INDEX { capwapDot11WlanProfileId }
::= { capwapDot11WlanTable 1 }
capwapDot11WlanEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that stores the settings of a WLAN profile."
INDEX { capwapDot11WlanProfileId }
::= { capwapDot11WlanTable 1 }
CapwapDot11WlanEntry ::=
SEQUENCE {
capwapDot11WlanProfileId CapwapDot11WlanIdProfileTC,
capwapDot11WlanProfileIfIndex InterfaceIndex,
capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WlanRowStatus RowStatus
}
CapwapDot11WlanEntry ::=
SEQUENCE {
capwapDot11WlanProfileId CapwapDot11WlanIdProfileTC,
capwapDot11WlanProfileIfIndex InterfaceIndex,
capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WlanRowStatus RowStatus
}
capwapDot11WlanProfileId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdProfileTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the identifier of a WLAN profile that has a
corresponding capwapDot11WlanProfileIfIndex."
::= { capwapDot11WlanEntry 1 }
capwapDot11WlanProfileId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdProfileTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the identifier of a WLAN profile that has a
corresponding capwapDot11WlanProfileIfIndex."
::= { capwapDot11WlanEntry 1 }
capwapDot11WlanProfileIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the index value that uniquely identifies a
WLAN Profile Interface. The interface identified by a
particular value of this index is the same interface as
identified by the same value of the ifIndex.
The creation of a row object in the capwapDot11WlanTable
triggers the AC to automatically create an WLAN Profile
Interface identified by an ifIndex without manual
intervention.
Most MIB tables in the IEEE 802.11 MIB module
[IEEE.802-11.2007] use an ifIndex to identify an interface
to facilitate the configuration and maintenance, for example,
dot11AuthenticationAlgorithmsTable.
Using the ifIndex of a WLAN Profile Interface, the Operator
could configure a WLAN through the IEEE 802.11 MIB module."
::= { capwapDot11WlanEntry 2 }
capwapDot11WlanProfileIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the index value that uniquely identifies a
WLAN Profile Interface. The interface identified by a
particular value of this index is the same interface as
identified by the same value of the ifIndex.
The creation of a row object in the capwapDot11WlanTable
triggers the AC to automatically create an WLAN Profile
Interface identified by an ifIndex without manual
intervention.
Most MIB tables in the IEEE 802.11 MIB module
[IEEE.802-11.2007] use an ifIndex to identify an interface
to facilitate the configuration and maintenance, for example,
dot11AuthenticationAlgorithmsTable.
Using the ifIndex of a WLAN Profile Interface, the Operator
could configure a WLAN through the IEEE 802.11 MIB module."
::= { capwapDot11WlanEntry 2 }
capwapDot11WlanMacType OBJECT-TYPE
SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether the WTP SHOULD support the WLAN in
Local or Split MAC modes."
REFERENCE
"Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11WlanEntry 3 }
capwapDot11WlanMacType OBJECT-TYPE
SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether the WTP SHOULD support the WLAN in
Local or Split MAC modes."
REFERENCE
"Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11WlanEntry 3 }
capwapDot11WlanTunnelMode OBJECT-TYPE SYNTAX CapwapBaseTunnelModeTC MAX-ACCESS read-create STATUS current DESCRIPTION "Represents the frame tunneling mode to be used for IEEE 802.11 data frames from all stations associated with the WLAN. Bits are exclusive with each other for a specific WLAN profile, and only one tunnel mode could be configured. If the operator set more than one bit, the value of the Response-PDU's error-status field is set to 'wrongValue', and the value of its error-index field is set to the index of the failed variable binding." REFERENCE "Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
CAPWAPDOT11WLANTUNELMODE对象类型语法CapwapBaseTunnelModeTC MAX-ACCESS读取创建状态当前说明“表示用于来自与WLAN关联的所有站点的IEEE 802.11数据帧的帧隧道模式。对于特定的WLAN配置文件，位之间是互斥的，并且只能配置一种隧道模式。如果操作员设置了多个位，则响应PDU的错误状态字段的值设置为“错误值”，其错误索引字段的值设置为失败变量绑定的索引。“参考”IEEE 802.11 CAPWAP协议绑定第6.1节，
RFC 5416."
::= { capwapDot11WlanEntry 4 }
RFC 5416."
::= { capwapDot11WlanEntry 4 }
capwapDot11WlanRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table. All the objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row: a. change the row status to 'notInService', b. change the values of the row c. change the row status to 'active' The capwapDot11WlanRowStatus may be changed to 'active' if all the managed objects in the conceptual row with MAX-ACCESS read-create have been assigned valid values.
capwapDot11WlanRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前描述此变量用于创建、修改和/或删除此表中的行。只有当相应概念行中的此对象的值不是“活动”时，才能修改行中的所有对象。因此，要修改此概念行中的一个或多个对象，请执行以下操作：a。将行状态更改为“notInService”，b。更改行c的值。将行状态更改为“活动”如果已为概念行中具有MAX-ACCESS read create的所有托管对象分配了有效值，则capwapDot11WlanRowStatus可能会更改为“活动”。
When the operator deletes a WLAN profile, the AC SHOULD
check whether the WLAN profile is bound with a radio.
If yes, the value of the Response-PDU's error-status field
is set to 'inconsistentValue', and the value of its
error-index field is set to the index of the failed variable
binding. If not, the row object could be deleted."
::= { capwapDot11WlanEntry 5 }
When the operator deletes a WLAN profile, the AC SHOULD
check whether the WLAN profile is bound with a radio.
If yes, the value of the Response-PDU's error-status field
is set to 'inconsistentValue', and the value of its
error-index field is set to the index of the failed variable
binding. If not, the row object could be deleted."
::= { capwapDot11WlanEntry 5 }
-- End of capwapDot11WlanTable Table
--capwapDot11WlanTable表格末尾
-- capwapDot11WlanBindTable Table
--capwapDot11WlanBindTable表格
capwapDot11WlanBindTable OBJECT-TYPE SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that stores bindings between WLAN profiles (identified by capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces. The WTP Virtual Radio Interfaces on the AC correspond to physical layer (PHY) radios on the WTPs. It also stores the mappings between WLAN IDs and WLAN Basic Service Set (BSS) Interfaces. Values of all objects in this table are persistent at restart/reboot." REFERENCE
capwapDot11WlanBindTable CapwapDot11WlanBindEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“存储WLAN配置文件（由capwapDot11WlanProfileId标识）和WTP虚拟无线电接口之间绑定的表。AC上的WTP虚拟无线电接口对应于物理层（PHY）WTPs上的无线电。它还存储WLAN ID和WLAN基本服务集（BSS）接口之间的映射。此表中所有对象的值在重新启动/重新启动时保持不变。“参考
"Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11Objects 2 }
"Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11Objects 2 }
capwapDot11WlanBindEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that stores the binding of a WLAN profile
to a WTP Virtual Radio Interface. It also stores the mapping
between WLAN ID and WLAN BSS Interface.
The INDEX object ifIndex is the ifIndex of a WTP Virtual
Radio Interface."
INDEX { ifIndex, capwapDot11WlanProfileId }
::= { capwapDot11WlanBindTable 1 }
capwapDot11WlanBindEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that stores the binding of a WLAN profile
to a WTP Virtual Radio Interface. It also stores the mapping
between WLAN ID and WLAN BSS Interface.
The INDEX object ifIndex is the ifIndex of a WTP Virtual
Radio Interface."
INDEX { ifIndex, capwapDot11WlanProfileId }
::= { capwapDot11WlanBindTable 1 }
CapwapDot11WlanBindEntry ::=
SEQUENCE {
capwapDot11WlanBindWlanId CapwapDot11WlanIdTC,
capwapDot11WlanBindBssIfIndex InterfaceIndex,
capwapDot11WlanBindRowStatus RowStatus
}
CapwapDot11WlanBindEntry ::=
SEQUENCE {
capwapDot11WlanBindWlanId CapwapDot11WlanIdTC,
capwapDot11WlanBindBssIfIndex InterfaceIndex,
capwapDot11WlanBindRowStatus RowStatus
}
capwapDot11WlanBindWlanId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the WLAN ID of a WLAN.
During a binding operation, the AC MUST select an unused
WLAN ID from between 1 and 16 [RFC5416]. For example, to bind
another WLAN profile to a radio that has been bound with
a WLAN profile, WLAN ID 2 should be assigned."
REFERENCE
"Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11WlanBindEntry 1 }
capwapDot11WlanBindWlanId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the WLAN ID of a WLAN.
During a binding operation, the AC MUST select an unused
WLAN ID from between 1 and 16 [RFC5416]. For example, to bind
another WLAN profile to a radio that has been bound with
a WLAN profile, WLAN ID 2 should be assigned."
REFERENCE
"Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11WlanBindEntry 1 }
capwapDot11WlanBindBssIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the index value that uniquely identifies a WLAN BSS Interface. The interface identified by a particular value of this index is the same interface as identified by the same value of the ifIndex.
CAPWAPDOT11WLANBINDBSSIFTINDEX对象类型语法接口索引MAX-ACCESS只读状态当前描述”表示唯一标识WLAN BSS接口的索引值。此索引的特定值标识的接口与ifIndex的相同值标识的接口相同。
The ifIndex here is for a WLAN BSS Interface.
The creation of a row object in the capwapDot11WlanBindTable
triggers the AC to automatically create a WLAN BSS Interface
identified by an ifIndex without manual intervention.
The PHY address of the capwapDot11WlanBindBssIfIndex is the
BSSID. While manufacturers are free to assign BSSIDs by using
any arbitrary mechanism, it is advised that where possible the
BSSIDs are assigned as a contiguous block.
When assigned as a block, implementations can still assign
any of the available BSSIDs to any WLAN. One possible method
is for the WTP to assign the address using the following
algorithm: base BSSID address + WLAN ID."
REFERENCE
"Section 2.4 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11WlanBindEntry 2 }
The ifIndex here is for a WLAN BSS Interface.
The creation of a row object in the capwapDot11WlanBindTable
triggers the AC to automatically create a WLAN BSS Interface
identified by an ifIndex without manual intervention.
The PHY address of the capwapDot11WlanBindBssIfIndex is the
BSSID. While manufacturers are free to assign BSSIDs by using
any arbitrary mechanism, it is advised that where possible the
BSSIDs are assigned as a contiguous block.
When assigned as a block, implementations can still assign
any of the available BSSIDs to any WLAN. One possible method
is for the WTP to assign the address using the following
algorithm: base BSSID address + WLAN ID."
REFERENCE
"Section 2.4 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416."
::= { capwapDot11WlanBindEntry 2 }
capwapDot11WlanBindRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row
in this table.
All the objects in a row can be modified only when the value
of this object in the corresponding conceptual row is not
'active'. Thus, to modify one or more of the objects in
this conceptual row:
a. change the row status to 'notInService',
b. change the values of the row
c. change the row status to 'active'"
::= { capwapDot11WlanBindEntry 3 }
capwapDot11WlanBindRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row
in this table.
All the objects in a row can be modified only when the value
of this object in the corresponding conceptual row is not
'active'. Thus, to modify one or more of the objects in
this conceptual row:
a. change the row status to 'notInService',
b. change the values of the row
c. change the row status to 'active'"
::= { capwapDot11WlanBindEntry 3 }
-- End of capwapDot11WlanBindTable Table
--capwapDot11WlanBindTable表格末尾
-- Module compliance
--模块符合性
capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 }
capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 }
capwapDot11Compliances OBJECT IDENTIFIER
::= { capwapDot11Conformance 2 }
capwapDot11Compliances OBJECT IDENTIFIER
::= { capwapDot11Conformance 2 }
capwapDot11Compliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance to the
CAPWAPDOT11合规模块-合规状态当前描述”描述了符合
CAPWAP-DOT11-MIB module."
CAPWAP-DOT11-MIB模块。”
MODULE -- this module
MANDATORY-GROUPS {
capwapDot11WlanGroup,
capwapDot11WlanBindGroup
}
::= { capwapDot11Compliances 1 }
MODULE -- this module
MANDATORY-GROUPS {
capwapDot11WlanGroup,
capwapDot11WlanBindGroup
}
::= { capwapDot11Compliances 1 }
capwapDot11WlanGroup OBJECT-GROUP
OBJECTS {
capwapDot11WlanProfileIfIndex,
capwapDot11WlanMacType,
capwapDot11WlanTunnelMode,
capwapDot11WlanRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to configure
the properties of a WLAN profile."
::= { capwapDot11Groups 1 }
capwapDot11WlanGroup OBJECT-GROUP
OBJECTS {
capwapDot11WlanProfileIfIndex,
capwapDot11WlanMacType,
capwapDot11WlanTunnelMode,
capwapDot11WlanRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to configure
the properties of a WLAN profile."
::= { capwapDot11Groups 1 }
capwapDot11WlanBindGroup OBJECT-GROUP
OBJECTS {
capwapDot11WlanBindWlanId,
capwapDot11WlanBindBssIfIndex,
capwapDot11WlanBindRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to bind the
WLAN profiles with a radio."
::= { capwapDot11Groups 2 }
capwapDot11WlanBindGroup OBJECT-GROUP
OBJECTS {
capwapDot11WlanBindWlanId,
capwapDot11WlanBindBssIfIndex,
capwapDot11WlanBindRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to bind the
WLAN profiles with a radio."
::= { capwapDot11Groups 2 }
END
终止
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects MAY be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The following are the tables and objects and their sensitivity/vulnerability:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o Unauthorized changes to the capwapDot11WlanTable and capwapDot11WlanBindTable MAY disrupt allocation of resources in the network, and also change the behavior of the WLAN system such as MAC type.
o 对capwapDot11WlanTable和capwapDot11WlanBindTable的未经授权的更改可能会中断网络中的资源分配，并且还会更改WLAN系统的行为，例如MAC类型。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配对象标识符值：
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapDot11MIB { mib-2 195 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapDot11MIB { mib-2 195 }
IANA has assigned the following ifTypes:
IANA已分配以下IFT类型：
Decimal Name Description
------- ------------ -------------------------------
252 capwapDot11Profile WLAN Profile Interface
253 capwapDot11Bss WLAN BSS Interface
Decimal Name Description
------- ------------ -------------------------------
252 capwapDot11Profile WLAN Profile Interface
253 capwapDot11Bss WLAN BSS Interface
This MIB module is based on contributions from Long Gao.
此MIB模块基于Long Gao的贡献。
Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, and Elwyn Davies for helpful comments on this document and guiding some technical solutions.
感谢David Harrington、Dan Romascanu、Abhijit Choudhury和Elwyn Davies对本文档提出了有益的意见，并指导了一些技术解决方案。
The authors also thank their friends and coworkers Fei Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao Zhang, Xiansen Cai, and Xiaolan Wan.
作者还感谢他们的朋友和同事费芳、朱学斌、宋浩、刘宇、萨钦·杜塔、王菊、赵宇金、张海涛、蔡先森和万小兰。
[IEEE.802-11.2007] "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications", IEEE Standard 802.11, 2007, <htt p://standards.ieee.org/getieee802/download/ 802.11-2007.pdf>.
[IEEE.802-11.2007]“信息技术-系统间的电信和信息交换-局域网和城域网-特定要求-第11部分：无线局域网介质访问控制（MAC）和物理层（PHY）规范”，IEEE标准802.112007，<htt p://standards.ieee.org/getieee802/download/802.11-2007.pdf>。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002.
[RFC3418]Presohn，R.，“简单网络管理协议（SNMP）的管理信息库（MIB）”，STD 62，RFC 3418，2002年12月。
[RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification", RFC 5415, March 2009.
[RFC5415]Calhoun，P.，Montemurro，M.，和D.Stanley，“无线接入点的控制和供应（CAPWAP）协议规范”，RFC 5415，2009年3月。
[RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11", RFC 5416, March 2009.
[RFC5416]Calhoun，P.，Montemurro，M.，和D.Stanley，“IEEE 802.11无线接入点（CAPWAP）协议绑定的控制和供应”，RFC 5416，2009年3月。
[RFC5833] Shi, Y., Ed., Perkins, D., Ed., Elliott, C., Ed., and Y. Zhang, Ed., "Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB", RFC 5833, May 2010.
[RFC5833]Shi，Y.，Ed.，Perkins，D.，Ed.，Elliott，C.，Ed.，和Y.Zhang，Ed.，“无线接入点（CAPWAP）协议基础MIB的控制和供应”，RFC 5833，2010年5月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer Security", RFC 4347, April 2006.
[RFC4347]Rescorla，E.和N.Modadugu，“数据报传输层安全”，RFC 4347，2006年4月。
Authors' Addresses
作者地址
Yang Shi (editor) Hangzhou H3C Tech. Co., Ltd. Beijing R&D Center of H3C, Digital Technology Plaza NO. 9 Shangdi 9th Street, Haidian District Beijing 100085 China
杨石（编辑）杭州华三科技有限公司中国北京海淀区上地九街9号数码科技广场华三北京研发中心100085
Phone: +86 010 82775276
EMail: rishyang@gmail.com
Phone: +86 010 82775276
EMail: rishyang@gmail.com
David T. Perkins (editor) 228 Bayview Dr. San Carlos, CA 94070 USA
David T.Perkins（编辑）228 Bayview圣卡洛斯博士，美国加利福尼亚州94070
Phone: +1 408 394-8702
EMail: dperkins@dsperkins.com
Phone: +1 408 394-8702
EMail: dperkins@dsperkins.com
Chris Elliott (editor) 1516 Kent St. Durham, NC 27707 USA
克里斯·埃利奥特（编辑）美国北卡罗来纳州达勒姆肯特街1516号，邮编27707
Phone: +1 919-308-1216
EMail: chelliot@pobox.com
Phone: +1 919-308-1216
EMail: chelliot@pobox.com
Yong Zhang (editor) Fortinet, Inc. 1090 Kifer Road Sunnyvale, CA 94086 USA
张勇（编辑）美国加利福尼亚州桑尼维尔基弗路1090号富通公司，邮编94086
EMail: yzhang@fortinet.com
EMail: yzhang@fortinet.com