draft-ietf-capwap-802dot11-mib-06.txt   rfc5834.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force (IETF) Y. Shi, Ed.
Internet-Draft Hangzhou H3C Tech. Co., Ltd. Request for Comments: 5834 Hangzhou H3C Tech. Co., Ltd.
Intended status: Informational D. Perkins, Ed. Category: Informational D. Perkins, Ed.
Expires: July 6, 2010 SNMPinfo ISSN: 2070-1721 C. Elliott, Ed.
C. Elliott, Ed.
Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
January 2, 2010 May 2010
CAPWAP Protocol Binding MIB for IEEE 802.11 Control and Provisioning of Wireless Access Points (CAPWAP) Protocol
draft-ietf-capwap-802dot11-mib-06 Binding MIB for IEEE 802.11
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it for use with network management protocols. In particular, it
describes managed objects for modeling the Control And Provisioning describes managed objects for modeling the Control And Provisioning
of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless of Wireless Access Points (CAPWAP) protocol for IEEE 802.11 wireless
binding. 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).
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (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.
This Internet-Draft will expire on July 6, 2010. 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.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. WLAN Profile . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. WLAN Profile . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5 5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5
5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6 5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6
6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6 6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7
7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7 7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7
7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 7 7.4. Relationship to MIB Module in the IEEE 802.11 Standard . . 8
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8 8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 21 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 22 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 22
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 22 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 22
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
14.1. Normative References . . . . . . . . . . . . . . . . . . . 23 14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
14.2. Informative References . . . . . . . . . . . . . . . . . . 24 14.2. Informative References . . . . . . . . . . . . . . . . . . 24
Appendix A. Appendix A. Changes between -06 and -05 . . . . . . . 24
1. Introduction 1. Introduction
The CAPWAP Protocol [RFC5415] defines a standard, interoperable The CAPWAP protocol [RFC5415] defines a standard, interoperable
protocol, which enables an Access Controller (AC) to manage a protocol, which enables an Access Controller (AC) to manage a
collection of Wireless Termination Points(WTPs). CAPWAP supports the collection of Wireless Termination Points (WTPs). CAPWAP supports
use of various wireless technologies by the WTPs, with one specified the use of various wireless technologies by the WTPs, with one
in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416]. specified in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416].
This document defines a MIB module that can be used to manage CAPWAP This document defines a MIB module that can be used to manage CAPWAP
implementations for IEEE 802.11 wireless binding. This MIB module implementations for IEEE 802.11 wireless binding. This MIB module
covers both configuration for Wireless Local Area Network (WLAN) and covers both configuration for Wireless Local Area Network (WLAN) and
a way to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. 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.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Terminology 3. Terminology
This document uses terminology from the CAPWAP Protocol specification This document uses terminology from the CAPWAP protocol specification
[RFC5415], the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] and [RFC5415], the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416], and
CAPWAP Protocol Base MIB [I-D.ietf-capwap-base-mib]. the CAPWAP Protocol Base MIB [RFC5833].
Access Controller (AC): The network entity that provides WTP access Access Controller (AC): The network entity that provides WTP access
to the network infrastructure in the data plane, control plane, to the network infrastructure in the data plane, control plane,
management plane, or a combination therein. management plane, or a combination therein.
Wireless Termination Point (WTP): The physical or network entity that Wireless Termination Point (WTP): The physical or network entity that
contains an RF antenna and wireless physical layer (PHY) to transmit contains an RF antenna and wireless physical layer (PHY) to transmit
and receive station traffic for wireless access networks. and receive station traffic for wireless access networks.
Control And Provisioning of Wireless Access Points (CAPWAP): It is a Control And Provisioning of Wireless Access Points (CAPWAP): It is a
generic protocol defining AC and WTP control and data plane generic protocol defining AC and WTP control and data plane
communication via a CAPWAP protocol transport mechanism. CAPWAP communication via a CAPWAP protocol transport mechanism. CAPWAP
control messages, and optionally CAPWAP data messages, are secured control messages, and optionally CAPWAP data messages, are secured
using Datagram Transport Layer Security (DTLS) [RFC4347]. using Datagram Transport Layer Security (DTLS) [RFC4347].
CAPWAP Control Channel: A bi-directional flow defined by the AC IP CAPWAP Control Channel: A bi-directional flow defined by the AC IP
Address, WTP IP Address, AC control port, WTP control port and the Address, WTP IP Address, AC control port, WTP control port, and the
transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control
packets are sent and received. packets are sent and received.
CAPWAP Data Channel: A bi-directional flow defined by the AC IP CAPWAP Data Channel: A bi-directional flow defined by the AC IP
Address, WTP IP Address, AC data port, WTP data port, and the Address, WTP IP Address, AC data port, WTP data port, and the
transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data
packets are sent and received. packets are sent and received.
Station (STA): A device that contains an interface to a wireless Station (STA): A device that contains an interface to a wireless
medium (WM). medium (WM).
Split and Local MAC: The CAPWAP protocol supports two modes of Split and Local MAC: The CAPWAP protocol supports two modes of
operation: Split and Local MAC. In Split MAC mode all L2 wireless operation: Split and Local MAC (medium access control). In Split MAC
data and management frames are encapsulated via the CAPWAP protocol mode, all Layer 2 wireless data and management frames are
and exchanged between the AC and the WTPs. The Local MAC mode of encapsulated via the CAPWAP protocol and exchanged between the AC and
operation allows the data frames to be either locally bridged, or the WTPs. The Local MAC mode of operation allows the data frames to
tunneled as 802.3 frames. be either locally bridged or tunneled as 802.3 frames.
Wireless Binding: The CAPWAP protocol is independent of a specific Wireless Binding: The CAPWAP protocol is independent of a specific
WTP radio technology, as well its associated wireless link layer WTP radio technology, as well its associated wireless link layer
protocol. Elements of the CAPWAP protocol are designed to protocol. Elements of the CAPWAP protocol are designed to
accommodate the specific needs of each wireless technology in a accommodate the specific needs of each wireless technology in a
standard way. Implementation of the CAPWAP protocol for a particular standard way. Implementation of the CAPWAP protocol for a particular
wireless technology MUST define a binding protocol for it, e.g., the wireless technology MUST define a binding protocol for it, e.g., the
binding for IEEE 802.11, provided in [RFC5416]. binding for IEEE 802.11, provided in [RFC5416].
Wireless Local Area Network (WLAN): A WLAN refers to a logical Wireless Local Area Network (WLAN): A WLAN refers to a logical
component instantiated on a WTP device. A single physical WTP MAY component instantiated on a WTP device. A single physical WTP MAY
operate a number of WLANs. Each Basic Service Set Identifier (BSSID) operate a number of WLANs. Each Basic Service Set Identifier (BSSID)
and its constituent wireless terminal radios are denoted as a and its constituent wireless terminal radios are denoted as a
distinct WLAN on a physical WTP. To support a physical WTP with distinct WLAN on a physical WTP. To support a physical WTP with
multiple WLANs is an important feature for CAPWAP protocol's 802.11 multiple WLANs is an important feature for CAPWAP protocol's 802.11
binding, and it is also for MIB module design. binding, and it is also for MIB module design.
Wireless Binding MIB Module: Other Standards Developing Organizations Wireless Binding MIB Module: Other Standards Development
(SDOs), such as IEEE already defined MIB module for a specific Organizations (SDOs), such as IEEE, already defined MIB modules for
wireless technology, e.g., the IEEE 802.11 MIB module specific wireless technologies, e.g., the IEEE 802.11 MIB module
[IEEE.802-11.2007]. Such MIB modules are called wireless binding MIB [IEEE.802-11.2007]. Such MIB modules are called wireless binding MIB
modules. modules.
CAPWAP Protocol Wireless Binding MIB Module: It is a MIB module CAPWAP Protocol Wireless Binding MIB Module: It is a MIB module
corresponding to the CAPWAP Protocol Binding for a Wireless binding. corresponding to the CAPWAP Protocol Binding for a wireless binding.
Sometimes, not all the technology-specific message elements in a Sometimes, not all the technology-specific message elements in a
CAPWAP binding protocol have MIB objects defined by other SDOs. For CAPWAP binding protocol have MIB objects defined by other SDOs. For
example, the protocol of [RFC5416] defines WLAN conception. Also, example, the protocol of [RFC5416] defines WLAN conception. Also,
Local or Split MAC modes could be specified for a WLAN. The MAC mode 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 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 such cases, in addition to the existing wireless binding MIB modules
defined by other SDOs, a CAPWAP protocol wireless binding MIB module defined by other SDOs, a CAPWAP protocol wireless binding MIB module
is required to be defined for a wireless binding. is required to be defined for a wireless binding.
4. Conventions 4. Conventions
skipping to change at page 5, line 23 skipping to change at page 5, line 30
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
5. Overview 5. Overview
5.1. WLAN Profile 5.1. WLAN Profile
A WLAN profile stores configuration parameters such as MAC type and A WLAN profile stores configuration parameters such as MAC type and
tunnel mode for a WLAN. Each WLAN profile is identified by a profile tunnel mode for a WLAN. Each WLAN profile is identified by a profile
identifier. The operator needs to create WLAN profiles before WTPs identifier. The operator needs to create WLAN profiles before WTPs
connect to the AC. To provide WLAN service, the operator SHOULD bind connect to the AC. To provide WLAN service, the operator SHOULD bind
WLAN profiles to a WTP Virtual Radio Interface which corresponding to WLAN profiles to a WTP Virtual Radio Interface that corresponds to a
a PHY radio. During the binding operation, the AC MUST select an PHY radio. During the binding operation, the AC MUST select an
unused WLAN ID between one(1) and 16 [RFC5416]. For example, to bind unused WLAN ID between 1 and 16 [RFC5416]. For example, to bind one
one more WLAN profile to a radio that has been bound with a WLAN more WLAN profile to a radio that has been bound with a WLAN profile,
profile, the AC SHOULD allocate WLAN ID 2 to the radio. Although the the AC SHOULD allocate WLAN ID 2 to the radio. Although the maximum
maximum value of WLAN ID is 16, the operator could configure more value of a WLAN ID is 16, the operator could configure more than 16
than 16 WLAN Profiles on the AC. WLAN Profiles on the AC.
5.2. Requirements and Constraints 5.2. Requirements and Constraints
The IEEE 802.11 MIB module [IEEE.802-11.2007] already defines MIB The IEEE 802.11 MIB module [IEEE.802-11.2007] already defines MIB
objects for most IEEE 802.11 Message Elements in the the CAPWAP objects for most IEEE 802.11 Message Elements in the CAPWAP Protocol
Protocol Binding for IEEE 802.11 [RFC5416]. As a CAPWAP Protocol Binding for IEEE 802.11 [RFC5416]. As a CAPWAP protocol 802.11
802.11 binding MIB module, the CAPWAP-DOT11-MIB module MUST be able binding MIB module, the CAPWAP-DOT11-MIB module MUST be able to reuse
to reuse such MIB objects in the IEEE 802.11 MIB module and support such MIB objects in the IEEE 802.11 MIB module and support functions
functions such as MAC mode for WLAN in the [RFC5416] which are not in (such as MAC mode for WLAN in the [RFC5416]) that are not in the
the scope of IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST scope of IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST
support such functions. support such functions.
In summary, the CAPWAP-DOT11-MIB module needs to support: In summary, the CAPWAP-DOT11-MIB module needs to support:
- Reuse of wireless binding MIB modules in the IEEE 802.11 standard; - Reuse of wireless binding MIB modules in the IEEE 802.11 standard;
- Centralized management and configuration of WLAN profiles on the - Centralized management and configuration of WLAN profiles on the
AC; AC;
- Configuration of a MAC type and tunnel mode for a specific WLAN - Configuration of a MAC type and tunnel mode for a specific WLAN
profile. profile.
5.3. Mechanism of Reusing Wireless Binding MIB Module 5.3. Mechanism of Reusing Wireless Binding MIB Module
In the IEEE 802.11 MIB module, the MIB tables such as In the IEEE 802.11 MIB module, the MIB tables such as
Dot11AuthenticationAlgorithmsTable are able to support WLAN dot11AuthenticationAlgorithmsTable are able to support WLAN
configuration (such as authentication algorithm), and these tables configuration (such as authentication algorithm), and these tables
use the ifIndex as the index which works well in the autonomous WLAN use the ifIndex as the index which works well in the autonomous WLAN
architecture. architecture.
Reuse of such wireless binding MIB modules is very important to Reuse of such wireless binding MIB modules is very important to
centralized WLAN architectures. The key point is to abstract a WLAN centralized WLAN architectures. The key point is to abstract a WLAN
profile as a WLAN Profile Interface on the AC, which could be 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 identified by an ifIndex. The MIB objects in the IEEE 802.11 MIB
module which are associated with this interface can be used to module which are associated with this interface can be used to
configure WLAN parameters for the WLAN, such as authentication configure WLAN parameters for the WLAN, such as authentication
algorithm. With the ifIndex of a WLAN Profile Interface, the AC is algorithm. With the ifIndex of a WLAN Profile Interface, the AC is
able to reuse the IEEE 802.11 MIB module. able to reuse the IEEE 802.11 MIB module.
In the CAPWAP-BASE-MIB module, each PHY radio is identified by a WTP 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 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 on the AC. The IEEE 802.11 MIB module associated with this
interface can be used to configure IEEE 802.11 wireless binding interface can be used to configure IEEE 802.11 wireless binding
parameters for the radio such as RTS Threshold. A WLAN Basic Service parameters for the radio such as RTS Threshold. A WLAN Basic Service
Set (BSS) Interface, created by binding WLAN to WTP Virtual Radio Set (BSS) Interface, created by binding a WLAN to a WTP Virtual Radio
Interface, is used for data forwarding. Interface, is used for data forwarding.
6. Structure of MIB Module 6. Structure of MIB Module
The MIB objects are derived from the CAPWAP protocol binding for IEEE The MIB objects are derived from the CAPWAP protocol binding for IEEE
802.11 document [RFC5416]. 802.11 document [RFC5416].
1) capwapDot11WlanTable capwapDot11WlanTable
The table allows the operator to display and configure WLAN profiles, The table allows the operator to display and configure WLAN
such as specifying the MAC type and tunnel mode for a WLAN. Also, it profiles, such as specifying the MAC type and tunnel mode for a
helps the AC to configure a WLAN through the IEEE 802.11 MIB module. WLAN. Also, it helps the AC to configure a WLAN through the IEEE
802.11 MIB module.
2) capwapDot11WlanBindTable capwapDot11WlanBindTable
The table provides a way to bind WLAN profiles to a WTP Virtual Radio The table provides a way to bind WLAN profiles to a WTP Virtual
Interface which has a PHY radio corresponding to it. A binding Radio Interface, which has a corresponding PHY radio. A binding
operation dynamically creates a WLAN BSS Interface, which is used for operation dynamically creates a WLAN BSS Interface, which is used
data forwarding. for data forwarding.
7. Relationship to Other MIB Modules 7. Relationship to Other MIB Modules
7.1. Relationship to SNMPv2-MIB Module 7.1. Relationship to SNMPv2-MIB Module
The CAPWAP-DOT11-MIB module does not duplicate the objects of the The CAPWAP-DOT11-MIB module does not duplicate the objects of the
'system' group in the SNMPv2-MIB [RFC3418] that is defined as being '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 mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. entity and certain other system-wide data.
7.2. Relationship to IF-MIB Module 7.2. Relationship to IF-MIB Module
skipping to change at page 7, line 21 skipping to change at page 7, line 31
7.2. Relationship to IF-MIB Module 7.2. Relationship to IF-MIB Module
The Interfaces Group [RFC2863] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing WLAN that are modeled extensions to the Interfaces Group for managing WLAN that are modeled
as interfaces. as interfaces.
Each WLAN profile corresponds to a WLAN Profile Interface on the AC. Each WLAN profile corresponds to a WLAN Profile Interface on the AC.
The interface MUST be modeled as an ifEntry, and ifEntry objects such The interface MUST be modeled as an ifEntry, and ifEntry objects such
as ifIndex, ifDescr, ifName, ifAlias are to be used as per [RFC2863]. as ifIndex, ifDescr, ifName, and ifAlias are to be used as per
The WLAN Profile Interface provides a way to configure IEEE 802.11 [RFC2863]. The WLAN Profile Interface provides a way to configure
parameters for a specific WLAN, and reuse the IEEE 802.11 MIB module. IEEE 802.11 parameters for a specific WLAN and reuse the IEEE 802.11
MIB module.
To provide data forwarding service, the AC dynamically creates WLAN To provide data forwarding service, the AC dynamically creates WLAN
BSS Interfaces. A WLAN BSS Interface MUST be modeled as an ifEntry, BSS Interfaces. A WLAN BSS Interface MUST be modeled as an ifEntry,
and ifEntry objects such as ifIndex, ifDescr, ifName, ifAlias are to and ifEntry objects such as ifIndex, ifDescr, ifName, and ifAlias are
be used as per [RFC2863]. The interface enables a single physical to be used as per [RFC2863]. The interface enables a single physical
WTP to support multiple WLANs. WTP to support multiple WLANs.
Also, the AC MUST have a mechanism that preserves the value of both Also, the AC MUST have a mechanism that preserves the value of the
the WLAN Profile Interfaces' and the WLAN BSS Interfaces' ifIndexes ifIndexes (of both the WLAN Profile Interfaces and the WLAN BSS
in the ifTable at AC reboot. Interfaces) in the ifTable at AC reboot.
7.3. Relationship to CAPWAP-BASE-MIB Module 7.3. Relationship to CAPWAP-BASE-MIB Module
The CAPWAP-BASE-MIB module provides a way to manage and control WTP The CAPWAP-BASE-MIB module provides a way to manage and control WTP
and radio objects. Especially, it provides the WTP Virtual Radio and radio objects. Especially, it provides the WTP Virtual Radio
Interface mechanism to enable the AC to reuse the IEEE 802.11 MIB Interface mechanism to enable the AC to reuse the IEEE 802.11 MIB
module. With this mechanism, an operator could configure an IEEE module. With this mechanism, an operator could configure an IEEE
802.11 radio's parameters and view the radio's traffic statistics on 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 the AC. Based on the CAPWAP-BASE-MIB module, the CAPWAP-DOT11-MIB
module provides more WLAN information. module provides more WLAN information.
7.4. Relationship to MIB Module in IEEE 802.11 Standard 7.4. Relationship to MIB Module in the IEEE 802.11 Standard
With the ifIndex of WLAN Profile Interface and WLAN BSS Interface, With the ifIndex of WLAN Profile Interface and WLAN BSS Interface,
the MIB module is able to reuse the IEEE 802.11 MIB module 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 [IEEE.802-11.2007]. The CAPWAP-DOT11-MIB module does not duplicate
those objects in the IEEE 802.11 MIB module. those objects in the IEEE 802.11 MIB module.
The CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] involves some The CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] involves some
of the MIB objects defined in IEEE 802.11 standard. Although CAPWAP- of the MIB objects defined in the IEEE 802.11 standard. Although
DOT11-MIB module uses it [RFC5416] as a reference, it could reuse all CAPWAP-DOT11-MIB module uses it [RFC5416] as a reference, it could
the MIB objects in the IEEE 802.11 standard , and is not limited by reuse all the MIB objects in the IEEE 802.11 standard , and is not
the scope of CAPWAP Protocol Binding for IEEE 802.11. limited by the scope of CAPWAP Protocol Binding for IEEE 802.11.
7.5. MIB Modules Required for IMPORTS 7.5. MIB Modules Required for IMPORTS
The following MIB modules are required for IMPORTS: SNMPv2-SMI The following MIB modules are required for IMPORTS: SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
[RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib]. [RFC2863], and CAPWAP-BASE-MIB [RFC5833].
8. Example of CAPWAP-DOT11-MIB Module Usage 8. Example of CAPWAP-DOT11-MIB Module Usage
1) Create a WTP profile 1) Create a WTP profile.
Suppose the WTP's base MAC address is '00:01:01:01:01:00'. Creates a Suppose the WTP's base MAC address is '00:01:01:01:01:00'.
WTP profile for it through the CapwapBaseWtpProfileTable Creates a WTP profile for it through the capwapBaseWtpProfileTable
[I-D.ietf-capwap-base-mib] as follows: [RFC5833] as follows:
In CapwapBaseWtpProfileTable In capwapBaseWtpProfileTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 123456', capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00', capwapBaseWtpProfileWtpMacAddress = '00:01:01:01:01:00',
capwapBaseWtpProfileWTPModelNumber = 'WTP123', capwapBaseWtpProfileWTPModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 123456', capwapBaseWtpProfileWtpName = 'WTP 123456',
capwapBaseWtpProfileWtpLocation = 'office', capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1), capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1), capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIp = '192.0.2.10', capwapBaseWtpProfileWtpStaticIpAddress = '192.0.2.10',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0', capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.0.2.1', capwapBaseWtpProfileWtpGateway = '192.0.2.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1), capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30, capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300, capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
capwapBaseWtpProfileWtpReportInterval = 120, capwapBaseWtpProfileWtpReportInterval = 120,
capwapBaseWtpProfileWtpSilentInterval = 30,
capwapBaseWtpProfileWtpStatisticsTimer = 120, capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpWaitDTLSTimer = 60,
capwapBaseWtpProfileWtpEcnSupport = limited(0) capwapBaseWtpProfileWtpEcnSupport = limited(0)
} }
Suppose the WTP with model number 'WTP123' has one PHY radio and this Suppose the WTP with model number 'WTP123' has one PHY radio and
PHY radio is identified by ID 1. The creation of this WTP profile this PHY radio is identified by ID 1. The creation of this WTP
triggers the AC to automatically create a WTP Virtual Radio Interface profile triggers the AC to automatically create a WTP Virtual
and add a new row object to the CapwapBaseWirelessBindingTable Radio Interface and add a new row object to the
without manual intervention. Suppose the ifIndex of the WTP Virtual capwapBaseWirelessBindingTable without manual intervention.
Radio Interface is 10. The following information is stored in the Suppose the ifIndex of the WTP Virtual Radio Interface is 10. The
CapwapBaseWirelessBindingTable. following information is stored in the
capwapBaseWirelessBindingTable.
In CapwapBaseWirelessBindingTable In capwapBaseWirelessBindingTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1, capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10, capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2) capwapBaseWirelessBindingType = dot11(2)
} }
The WTP Virtual Radio Interfaces on the AC correspond to the PHY The WTP Virtual Radio Interfaces on the AC correspond to the PHY
radios on the WTP. The WTP Virtual Radio Interface is modeled by radios on the WTP. The WTP Virtual Radio Interface is modeled by
ifTable [RFC2863]. ifTable [RFC2863].
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface', ifDescr = 'WTP Virtual Radio Interface',
ifType = xxx, ifType = 254,
RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of WTP Virtual Radio Interface
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00', ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1), ifAdminStatus = true(1),
ifOperStatus = false(0), ifOperStatus = false(0),
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
ifOutDiscards = 0, ifOutDiscards = 0,
ifOutErrors = 0 ifOutErrors = 0
} }
2) Query the ifIndexes of WTP Virtual Radio Interfaces 2) Query the ifIndexes of WTP Virtual Radio Interfaces.
Before configuring PHY radios, the operator needs to get the Before configuring PHY radios, the operator needs to get the
ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY
radios. radios.
As the CapwapBaseWirelessBindingTable already stores the mappings As the capwapBaseWirelessBindingTable already stores the mappings
between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual
Interfaces, the operator can get the ifIndex information by querying Radio Interfaces, the operator can get the ifIndex information by
this table. Such a query operation SHOULD run from radio ID 1 to querying this table. Such a query operation SHOULD run from radio
radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex ID 1 to radio ID 31 (according to [RFC5415]), and stop when an
value (0) is returned. invalid ifIndex value (0) is returned.
This example uses capwapBaseWtpProfileId = 1 and This example uses capwapBaseWtpProfileId = 1 and
capwapBaseWirelessBindingRadioId = 1 as inputs to query the capwapBaseWirelessBindingRadioId = 1 as inputs to query the
CapwapBaseWirelessBindingTable, and gets capwapBaseWirelessBindingTable, and gets
capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses
capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId =
and gets a invalid ifIndex value (0), so the the query operation 2, and gets an invalid ifIndex value (0), so the query operation
ends. This method gets not only the ifIndexes of WTP Virtual Radio ends. This method gets not only the ifIndexes of WTP Virtual
Interfaces, but also the numbers of PHY radios. Besides checking Radio Interfaces, but also the numbers of PHY radios. Besides
whether the ifIndex value is valid, the operator SHOULD check whether checking whether the ifIndex value is valid, the operator SHOULD
the capwapBaseWirelessBindingType is the desired binding type. check whether the capwapBaseWirelessBindingType is the desired
binding type.
3) Configure IEEE 802.11 parameters for a WTP Virtual Radio Interface 3) Configure IEEE 802.11 parameters for a WTP Virtual Radio Interface
This configuration is made on the AC through the IEEE 802.11 MIB This configuration is made on the AC through the IEEE 802.11 MIB
module. module.
The following shows an example of configuring parameters for a WTP The following shows an example of configuring parameters for a WTP
Virtual Radio Interface with ifIndex 10 through the Virtual Radio Interface with ifIndex 10 through the
Dot11OperationTable [IEEE.802-11.2007]. dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = '00:00:00:00:00:00', dot11MACAddress = '00:00:00:00:00:00',
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = 'capwap', dot11ManufacturerID = 'capwap',
dot11ProductID = 'capwap' dot11ProductID = 'capwap',
dot11CAPLimit = 2, dot11CAPLimit = 2,
dot11HCCWmin = 0, dot11HCCWmin = 0,
dot11HCCWmax = 0, dot11HCCWmax = 0,
dot11HCCAIFSN = 1, dot11HCCAIFSN = 1,
dot11ADDBAResponseTimeout = 1, dot11ADDBAResponseTimeout = 1,
dot11ADDTSResponseTimeout = 1, dot11ADDTSResponseTimeout = 1,
dot11ChannelUtilizationBeaconInterval = 50, dot11ChannelUtilizationBeaconInterval = 50,
dot11ScheduleTimeout = 10, dot11ScheduleTimeout = 10,
dot11DLSResponseTimeout = 10, dot11DLSResponseTimeout = 10,
dot11QAPMissingAckRetryLimit = 1, dot11QAPMissingAckRetryLimit = 1,
skipping to change at page 11, line 4 skipping to change at page 11, line 13
dot11HCCWmin = 0, dot11HCCWmin = 0,
dot11HCCWmax = 0, dot11HCCWmax = 0,
dot11HCCAIFSN = 1, dot11HCCAIFSN = 1,
dot11ADDBAResponseTimeout = 1, dot11ADDBAResponseTimeout = 1,
dot11ADDTSResponseTimeout = 1, dot11ADDTSResponseTimeout = 1,
dot11ChannelUtilizationBeaconInterval = 50, dot11ChannelUtilizationBeaconInterval = 50,
dot11ScheduleTimeout = 10, dot11ScheduleTimeout = 10,
dot11DLSResponseTimeout = 10, dot11DLSResponseTimeout = 10,
dot11QAPMissingAckRetryLimit = 1, dot11QAPMissingAckRetryLimit = 1,
dot11EDCAAveragingPeriod = 5 dot11EDCAAveragingPeriod = 5
} }
4) Configure a WLAN Profile 4) Configure a WLAN Profile.
WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB
Module, and IEEE 802.11 MIB module. module, and IEEE 802.11 MIB module.
The first step is to create a WLAN Profile Interface through the The first step is to create a WLAN Profile Interface through the
CAPWAP-DOT11-MIB module on the AC. CAPWAP-DOT11-MIB module on the AC.
For example, when you configure a WLAN profile which is identified by For example, when you configure a WLAN profile that is identified
capwapDot11WlanProfileId 1, the CapwapDot11WlanTable creates the by capwapDot11WlanProfileId 1, the capwapDot11WlanTable creates
following row object for it. the following row object for it.
In CapwapDot11WlanTable In capwapDot11WlanTable
{ {
capwapDot11WlanProfileId = 1, capwapDot11WlanProfileId = 1,
capwapDot11WlanProfileIfIndex = 20, capwapDot11WlanProfileIfIndex = 20,
capwapDot11WlanMacType = splitMAC(2), capwapDot11WlanMacType = splitMAC(2),
capwapDot11WlanTunnelMode = dot3Tunnel(2), capwapDot11WlanTunnelMode = dot3Tunnel(2),
capwapDot11WlanRowStatus = createAndGo(4) capwapDot11WlanRowStatus = createAndGo(4)
} }
The creation of a row object triggers the AC to automatically create The creation of a row object triggers the AC to automatically
a WLAN Profile Interface and it is identified by ifIndex 20 without create a WLAN Profile Interface and it is identified by ifIndex 20
manual intervention. without manual intervention.
A WLAN Profile Interface MUST be modeled as an ifEntry on the AC A WLAN Profile Interface MUST be modeled as an ifEntry on the AC
which provides appropriate interface information. The that provides appropriate interface information. The
CapwapDot11WlanTable stores the mappings between capwapDot11WlanTable stores the mappings between
capwapDot11WlanProfileIds and the ifIndexes of WLAN Profile capwapDot11WlanProfileIds and the ifIndexes of WLAN Profile
Interfaces. Interfaces.
In ifTable In ifTable
{ {
ifIndex = 20, ifIndex = 20,
ifDescr = 'WLAN Profile Interface', ifDescr = 'WLAN Profile Interface',
ifType = xxx, ifType = 252,
RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WLAN Profile Interface'
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00', ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1), ifAdminStatus = true(1),
ifOperStatus = true(1), ifOperStatus = true(1),
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
ifOutDiscards = 0, ifOutDiscards = 0,
ifOutErrors = 0 ifOutErrors = 0
} }
The second step is to configure WLAN parameters for the WLAN Profile The second step is to configure WLAN parameters for the WLAN
Interface through the IEEE 802.11 MIB module on the AC. Profile Interface through the IEEE 802.11 MIB module on the AC.
The following example configures an authentication algorithm for a The following example configures an authentication algorithm for a
WLAN. WLAN.
In Dot11AuthenticationAlgorithmsTable In dot11AuthenticationAlgorithmsTable
{ {
ifIndex = 20, ifIndex = 20,
dot11AuthenticationAlgorithmsIndex = 1, dot11AuthenticationAlgorithmsIndex = 1,
dot11AuthenticationAlgorithm = Shared Key(2), dot11AuthenticationAlgorithm = Shared Key(2),
dot11AuthenticationAlgorithmsEnable = true(1) dot11AuthenticationAlgorithmsEnable = true(1)
} }
Here ifIndex 20 identifies the WLAN Profile Interface and the index Here, ifIndex 20 identifies the WLAN Profile Interface, and the
of the configured authentication algorithm is 1. index of the configured authentication algorithm is 1.
5) Bind WLAN Profiles to a WTP radio 5) Bind WLAN Profiles to a WTP radio.
On the AC, the CapwapDot11WlanBindTable in the CAPWAP-DOT11-MIB On the AC, the capwapDot11WlanBindTable in the CAPWAP-DOT11-MIB
stores the bindings between WLAN profiles(identified by stores the bindings between WLAN profiles(identified by
capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces
(identified by the ifIndex). (identified by the ifIndex).
For example, after the operator binds a WLAN profile with For example, after the operator binds a WLAN profile with
capwapDot11WlanProfileId 1 to WTP Virtual Radio Interface with capwapDot11WlanProfileId 1 to WTP Virtual Radio Interface with
ifIndex 10, the CapwapDot11WlanBindTable creates the following row ifIndex 10, the capwapDot11WlanBindTable creates the following row
object. object.
In CapwapDot11WlanBindTable In capwapDot11WlanBindTable
{ {
ifIndex = 10, ifIndex = 10,
capwapDot11WlanProfileId = 1, capwapDot11WlanProfileId = 1,
capwapDot11WlanBindBssIfIndex = 30, capwapDot11WlanBindBssIfIndex = 30,
capwapDot11WlanBindRowStatus = createAndGo(4) capwapDot11WlanBindRowStatus = createAndGo(4)
} }
If the capwapDot11WlanMacType of the WLAN is splitMAC(2), the If the capwapDot11WlanMacType of the WLAN is splitMAC(2), the
creation of the row object in the CapwapDot11WlanBindTable triggers creation of the row object in the capwapDot11WlanBindTable
the AC to automatically create a WLAN BSS Interface identified by triggers the AC to automatically create a WLAN BSS Interface
ifIndex 30 without manual intervention. identified by ifIndex 30 without manual intervention.
The WLAN BSS Interface MUST be modeled as an ifEntry on the AC, which The WLAN BSS Interface MUST be modeled as an ifEntry on the AC,
provides appropriate interface information. The which provides appropriate interface information. The
CapwapDot11WlanBindTable stores the mappings among the ifIndex of a capwapDot11WlanBindTable stores the mappings among the ifIndex of
WTP Virtual Radio Interface, WLAN profile ID, WLAN ID and the ifIndex a WTP Virtual Radio Interface, WLAN profile ID, WLAN ID, and the
of a WLAN BSS Interface. ifIndex of a WLAN BSS Interface.
6) Current configuration status report from the WTP to the AC 6) Get the current configuration status report from the WTP to the
AC.
Before a WTP that has joined the AC gets configuration from the AC, Before a WTP that has joined the AC gets configuration from the
it needs to report its current configuration status by sending a AC, it needs to report its current configuration status by sending
configuration status request message to the AC, which uses the a configuration status request message to the AC, which uses the
message to update corresponding MIB objects on the AC. For example, message to update corresponding MIB objects on the AC. For
for ifIndex 10 (which identifies a WLAN Virtual Radio Interface), its example, for ifIndex 10 (which identifies a WLAN Virtual Radio
ifOperStatus in the ifTable is updated according to the current radio Interface), its ifOperStatus in the ifTable is updated according
operational status in the CAPWAP message [RFC5415]. to the current radio operational status in the CAPWAP message
[RFC5415].
7) Query WTP and radio statistics data 7) Query WTP and radio statistical data.
After WTPs start to run, the operator could query WTP and radio After WTPs start to run, the operator could query WTP and radio
statistics data through the CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB statistics data through the CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB
modules. For example, through the dot11CountersTable modules. For example, through the dot11CountersTable
[IEEE.802-11.2007], the operator could query counter data of a radio [IEEE.802-11.2007], the operator could query counter data of a
which is identified by the ifIndex of the corresponding WLAN Virtual radio that is identified by the ifIndex of the corresponding WLAN
Radio Interface. Virtual Radio Interface.
8) Query other statistics data 8) Query other statistical data.
The operator could query the configuration of a WLAN through the The operator could query the configuration of a WLAN through the
Dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and the dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and the
statistic data of a WLAN BSS Interface through the ifTable [RFC2863]; statistical data of a WLAN BSS Interface through the ifTable
[RFC2863].
9. Definitions 9. Definitions
CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
RowStatus, TEXTUAL-CONVENTION RowStatus, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB FROM IF-MIB
CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC
FROM CAPWAP-BASE-MIB; FROM CAPWAP-BASE-MIB;
capwapDot11MIB MODULE-IDENTITY capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "201001020000Z" -- Jan 2th, 2010 LAST-UPDATED "201004300000Z" -- 30 April 2010
ORGANIZATION "IETF Control And Provisioning of Wireless Access ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html" http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO CONTACT-INFO
"General Discussion: capwap@frascone.com "General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd. Hangzhou H3C Tech. Co., Ltd.
Beijing R&D Center of H3C, Digital Technology Plaza, Beijing R&D Center of H3C, Digital Technology Plaza
NO.9 Shangdi 9th Street,Haidian District, NO. 9 Shangdi 9th Street, Haidian District
Beijing Beijing 100085
China(100085) China
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com Email: rishyang@gmail.com
David T. Perkins David T. Perkins (editor)
228 Bayview Dr 228 Bayview Dr.
San Carlos, CA 94070 San Carlos, CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@dsperkins.com
Chris Elliott Chris Elliott (editor)
Cisco Systems, Inc. 1516 Kent St.
7025 Kit Creek Rd., P.O. Box 14987 Durham, NC 27707
Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-308-1216
Email: chelliot@cisco.com Email: chelliot@pobox.com
Yong Zhang Yong Zhang (editor)
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2010 The Internet Society. This version of "Copyright (c) 2010 IETF Trust and the persons identified as
the MIB module is part of RFC xxx; see the RFC itself authors of the code. All rights reserved.
for full legal notices.
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).
This version of this MIB module is part of RFC 5834;
see the RFC itself for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
CAPWAP Protocol binding for IEEE 802.11." CAPWAP Protocol binding for IEEE 802.11."
REVISION "201001020000Z" REVISION "201004300000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxx" "Initial version, published as RFC 5834"
::= { mib-2 xxx } ::= { mib-2 195 }
-- Textual conventions -- Textual conventions
CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a Wireless Local Area "Represents the unique identifier of a Wireless Local Area
Network(WLAN)." Network (WLAN)."
SYNTAX Unsigned32 (1..16) SYNTAX Unsigned32 (1..16)
CapwapDot11WlanIdProfileTC ::= TEXTUAL-CONVENTION CapwapDot11WlanIdProfileTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WLAN profile." "Represents the unique identifier of a WLAN profile."
SYNTAX Unsigned32 (1..512) SYNTAX Unsigned32 (1..512)
-- Top level components of this MIB module -- Top level components of this MIB module
skipping to change at page 16, line 22 skipping to change at page 16, line 30
the IEEE 802.11 MIB module. the IEEE 802.11 MIB module.
Values of all objects in this table are persistent at Values of all objects in this table are persistent at
restart/reboot." restart/reboot."
::= { capwapDot11Objects 1 } ::= { capwapDot11Objects 1 }
capwapDot11WlanEntry OBJECT-TYPE capwapDot11WlanEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanEntry SYNTAX CapwapDot11WlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that store the settings of a WLAN profile." "A set of objects that stores the settings of a WLAN profile."
INDEX { capwapDot11WlanProfileId } INDEX { capwapDot11WlanProfileId }
::= { capwapDot11WlanTable 1 } ::= { capwapDot11WlanTable 1 }
CapwapDot11WlanEntry ::= CapwapDot11WlanEntry ::=
SEQUENCE { SEQUENCE {
capwapDot11WlanProfileId CapwapDot11WlanIdProfileTC, capwapDot11WlanProfileId CapwapDot11WlanIdProfileTC,
capwapDot11WlanProfileIfIndex InterfaceIndex, capwapDot11WlanProfileIfIndex InterfaceIndex,
capwapDot11WlanMacType CapwapBaseMacTypeTC, capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC, capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WlanRowStatus RowStatus capwapDot11WlanRowStatus RowStatus
} }
capwapDot11WlanProfileId OBJECT-TYPE capwapDot11WlanProfileId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdProfileTC SYNTAX CapwapDot11WlanIdProfileTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the identifier of a WLAN profile which has a "Represents the identifier of a WLAN profile that has a
corresponding capwapDot11WlanProfileIfIndex." corresponding capwapDot11WlanProfileIfIndex."
::= { capwapDot11WlanEntry 1 } ::= { capwapDot11WlanEntry 1 }
capwapDot11WlanProfileIfIndex OBJECT-TYPE capwapDot11WlanProfileIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the index value that uniquely identifies a "Represents the index value that uniquely identifies a
WLAN Profile Interface. The interface identified by a WLAN Profile Interface. The interface identified by a
particular value of this index is the same interface as particular value of this index is the same interface as
identified by the same value of the ifIndex. identified by the same value of the ifIndex.
The creation of a row object in the capwapDot11WlanTable The creation of a row object in the capwapDot11WlanTable
triggers the AC to automatically create an WLAN Profile triggers the AC to automatically create an WLAN Profile
Interface identified by an ifIndex without manual Interface identified by an ifIndex without manual
intervention. intervention.
Most MIB tables in the IEEE 802.11 MIB module Most MIB tables in the IEEE 802.11 MIB module
[IEEE.802-11.2007] use an ifIndex to identify an interface [IEEE.802-11.2007] use an ifIndex to identify an interface
to facilitate the configuration and maintenance, for example, to facilitate the configuration and maintenance, for example,
dot11AuthenticationAlgorithmsTable. dot11AuthenticationAlgorithmsTable.
skipping to change at page 17, line 25 skipping to change at page 17, line 34
::= { capwapDot11WlanEntry 2 } ::= { capwapDot11WlanEntry 2 }
capwapDot11WlanMacType OBJECT-TYPE capwapDot11WlanMacType OBJECT-TYPE
SYNTAX CapwapBaseMacTypeTC SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the WTP SHOULD support the WLAN in "Represents whether the WTP SHOULD support the WLAN in
Local or Split MAC modes." Local or Split MAC modes."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416." RFC 5416."
::= { capwapDot11WlanEntry 3 } ::= { capwapDot11WlanEntry 3 }
capwapDot11WlanTunnelMode OBJECT-TYPE capwapDot11WlanTunnelMode OBJECT-TYPE
SYNTAX CapwapBaseTunnelModeTC SYNTAX CapwapBaseTunnelModeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the frame tunneling mode to be used for IEEE 802.11 "Represents the frame tunneling mode to be used for IEEE 802.11
data frames from all stations associated with the WLAN. data frames from all stations associated with the WLAN.
Bits are exclusive with each other for a specific WLAN profile, Bits are exclusive with each other for a specific WLAN profile,
and only one tunnel mode could be configured. and only one tunnel mode could be configured.
If the operator set more than one bit, the value of the If the operator set more than one bit, the value of the
Response-PDU's error-status field is set to `wrongValue', Response-PDU's error-status field is set to 'wrongValue',
and the value of its error-index field is set to the index of and the value of its error-index field is set to the index of
the failed variable binding." the failed variable binding."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416." RFC 5416."
::= { capwapDot11WlanEntry 4 } ::= { capwapDot11WlanEntry 4 }
capwapDot11WlanRowStatus OBJECT-TYPE capwapDot11WlanRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row "This variable is used to create, modify, and/or delete a row
in this table. in this table.
All the objects in a row can be modified only when the value All the objects in a row can be modified only when the value
of this object in the corresponding conceptual row is not of this object in the corresponding conceptual row is not
''active''. Thus to modify one or more of the objects in 'active'. Thus, to modify one or more of the objects in
this conceptual row, this conceptual row:
a. change the row status to ''notInService'', a. change the row status to 'notInService',
b. change the values of the row b. change the values of the row
c. change the row status to ''active'' c. change the row status to 'active'
The capwapDot11WlanRowStatus may be changed to ''active'' The capwapDot11WlanRowStatus may be changed to 'active'
if all the managed objects in the conceptual row with if all the managed objects in the conceptual row with
MAX-ACCESS read-create have been assigned valid values. MAX-ACCESS read-create have been assigned valid values.
When the operator deletes a WLAN profile, the AC SHOULD When the operator deletes a WLAN profile, the AC SHOULD
check whether the WLAN profile is bound with a radio. check whether the WLAN profile is bound with a radio.
If yes, the value of the Response-PDU's error-status field If yes, the value of the Response-PDU's error-status field
is set to `inconsistentValue', and the value of its is set to 'inconsistentValue', and the value of its
error-index field is set to the index of the failed variable error-index field is set to the index of the failed variable
binding. If not, the row object could be deleted." binding. If not, the row object could be deleted."
::= { capwapDot11WlanEntry 5 } ::= { capwapDot11WlanEntry 5 }
-- End of capwapDot11WlanTable Table -- End of capwapDot11WlanTable Table
-- capwapDot11WlanBindTable Table -- capwapDot11WlanBindTable Table
capwapDot11WlanBindTable OBJECT-TYPE capwapDot11WlanBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that stores bindings between WLAN profiles "A table that stores bindings between WLAN profiles
(identified by capwapDot11WlanProfileId) and WTP Virtual Radio (identified by capwapDot11WlanProfileId) and WTP Virtual Radio
Interfaces. The WTP Virtual Radio Interfaces on the AC Interfaces. The WTP Virtual Radio Interfaces on the AC
correspond to physical layer (PHY) radios on the WTPs. correspond to physical layer (PHY) radios on the WTPs.
It also stores the mappings between WLAN IDs and WLAN It also stores the mappings between WLAN IDs and WLAN
Basic Service Set (BSS) Interfaces. Basic Service Set (BSS) Interfaces.
Values of all objects in this table are persistent at Values of all objects in this table are persistent at
restart/reboot." restart/reboot."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416." RFC 5416."
::= { capwapDot11Objects 2 } ::= { capwapDot11Objects 2 }
capwapDot11WlanBindEntry OBJECT-TYPE capwapDot11WlanBindEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanBindEntry SYNTAX CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that stores the binding of a WLAN profile "A set of objects that stores the binding of a WLAN profile
to a WTP Virtual Radio Interface. It also stores the mapping to a WTP Virtual Radio Interface. It also stores the mapping
between WLAN ID and WLAN BSS Interface. between WLAN ID and WLAN BSS Interface.
The INDEX object ifIndex is the ifIndex of a WTP Virtual The INDEX object ifIndex is the ifIndex of a WTP Virtual
Radio Interface." Radio Interface."
INDEX { ifIndex, capwapDot11WlanProfileId } INDEX { ifIndex, capwapDot11WlanProfileId }
::= { capwapDot11WlanBindTable 1 } ::= { capwapDot11WlanBindTable 1 }
CapwapDot11WlanBindEntry ::= CapwapDot11WlanBindEntry ::=
SEQUENCE { SEQUENCE {
capwapDot11WlanBindWlanId CapwapDot11WlanIdTC, capwapDot11WlanBindWlanId CapwapDot11WlanIdTC,
capwapDot11WlanBindBssIfIndex InterfaceIndex, capwapDot11WlanBindBssIfIndex InterfaceIndex,
capwapDot11WlanBindRowStatus RowStatus capwapDot11WlanBindRowStatus RowStatus
} }
capwapDot11WlanBindWlanId OBJECT-TYPE capwapDot11WlanBindWlanId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdTC SYNTAX CapwapDot11WlanIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the WLAN ID of a WLAN. "Represents the WLAN ID of a WLAN.
During a binding operation, the AC MUST select an unused During a binding operation, the AC MUST select an unused
WLAN ID from (1) and 16 [RFC5416]. For example, to bind WLAN ID from between 1 and 16 [RFC5416]. For example, to bind
another WLAN profile to a radio that has been bound with another WLAN profile to a radio that has been bound with
a WLAN profile, WLAN ID 2 should be assigned." a WLAN profile, WLAN ID 2 should be assigned."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416." RFC 5416."
::= { capwapDot11WlanBindEntry 1 } ::= { capwapDot11WlanBindEntry 1 }
capwapDot11WlanBindBssIfIndex OBJECT-TYPE capwapDot11WlanBindBssIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the index value that uniquely identifies a "Represents the index value that uniquely identifies a
WLAN BSS Interface. The interface identified by a WLAN BSS Interface. The interface identified by a
particular value of this index is the same interface as particular value of this index is the same interface as
identified by the same value of the ifIndex. identified by the same value of the ifIndex.
The ifIndex here is for a WLAN BSS Interface. The ifIndex here is for a WLAN BSS Interface.
The creation of a row object in the capwapDot11WlanBindTable The creation of a row object in the capwapDot11WlanBindTable
triggers the AC to automatically create a WLAN BSS Interface triggers the AC to automatically create a WLAN BSS Interface
identified by an ifIndex without manual intervention. identified by an ifIndex without manual intervention.
The PHY address of the capwapDot11WlanBindBssIfIndex is the The PHY address of the capwapDot11WlanBindBssIfIndex is the
BSSID. While manufacturers are free to assign BSSIDs by using BSSID. While manufacturers are free to assign BSSIDs by using
any arbitrary mechanism, it is advised that where possible the any arbitrary mechanism, it is advised that where possible the
BSSIDs are assigned as a contiguous block. BSSIDs are assigned as a contiguous block.
When assigned as a block, implementations can still assign When assigned as a block, implementations can still assign
any of the available BSSIDs to any WLAN. One possible method any of the available BSSIDs to any WLAN. One possible method
is for the WTP to assign the address using the following is for the WTP to assign the address using the following
algorithm: base BSSID address + WLAN ID." algorithm: base BSSID address + WLAN ID."
REFERENCE REFERENCE
"Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11, "Section 2.4 of CAPWAP Protocol Binding for IEEE 802.11,
RFC 5416." RFC 5416."
::= { capwapDot11WlanBindEntry 2 } ::= { capwapDot11WlanBindEntry 2 }
capwapDot11WlanBindRowStatus OBJECT-TYPE capwapDot11WlanBindRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row "This variable is used to create, modify, and/or delete a row
in this table. in this table.
All the objects in a row can be modified only when the value All the objects in a row can be modified only when the value
of this object in the corresponding conceptual row is not of this object in the corresponding conceptual row is not
''active''. Thus to modify one or more of the objects in 'active'. Thus, to modify one or more of the objects in
this conceptual row, this conceptual row:
a. change the row status to ''notInService'', a. change the row status to 'notInService',
b. change the values of the row b. change the values of the row
c. change the row status to ''active''" c. change the row status to 'active'"
::= { capwapDot11WlanBindEntry 3 } ::= { capwapDot11WlanBindEntry 3 }
-- End of capwapDot11WlanBindTable Table -- End of capwapDot11WlanBindTable Table
-- Module compliance -- Module compliance
capwapDot11Groups OBJECT IDENTIFIER capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 } ::= { capwapDot11Conformance 1 }
capwapDot11Compliances OBJECT IDENTIFIER capwapDot11Compliances OBJECT IDENTIFIER
skipping to change at page 21, line 14 skipping to change at page 21, line 22
capwapDot11WlanGroup OBJECT-GROUP capwapDot11WlanGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDot11WlanProfileIfIndex, capwapDot11WlanProfileIfIndex,
capwapDot11WlanMacType, capwapDot11WlanMacType,
capwapDot11WlanTunnelMode, capwapDot11WlanTunnelMode,
capwapDot11WlanRowStatus capwapDot11WlanRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to configure "A collection of objects that is used to configure
the properties of a WLAN profile." the properties of a WLAN profile."
::= { capwapDot11Groups 1 } ::= { capwapDot11Groups 1 }
capwapDot11WlanBindGroup OBJECT-GROUP capwapDot11WlanBindGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDot11WlanBindWlanId, capwapDot11WlanBindWlanId,
capwapDot11WlanBindBssIfIndex, capwapDot11WlanBindBssIfIndex,
capwapDot11WlanBindRowStatus capwapDot11WlanBindRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to bind the "A collection of objects that is used to bind the
WLAN profiles with a radio." WLAN profiles with a radio."
::= { capwapDot11Groups 2 } ::= { capwapDot11Groups 2 }
END END
10. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB module 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 with a MAX-ACCESS clause of read-write and/or read-create. Such
objects MAY be considered sensitive or vulnerable in some network objects MAY be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. The followings are the tables and objects and network operations. The following are the tables and objects and
their sensitivity/vulnerability: their sensitivity/vulnerability:
o - Unauthorized changes to the capwapDot11WlanTable and o Unauthorized changes to the capwapDot11WlanTable and
capwapDot11WlanBindTable MAY disrupt allocation of resources in capwapDot11WlanBindTable MAY disrupt allocation of resources in
the network, also change the behavior of WLAN system such as MAC the network, and also change the behavior of the WLAN system such
type. as MAC type.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
skipping to change at page 22, line 23 skipping to change at page 22, line 34
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations 11. IANA Considerations
11.1. IANA Considerations for CAPWAP-DOT11-MIB Module 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapDot11MIB { mib-2 XXX } Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapDot11MIB { mib-2 195 }
11.2. IANA Considerations for ifType 11.2. IANA Considerations for ifType
Require IANA to assign a ifType for the WLAN Profile Interface. IANA has assigned the following ifTypes:
Require IANA to assign a ifType for the WLAN BSS Interface. Decimal Name Description
------- ------------ -------------------------------
252 capwapDot11Profile WLAN Profile Interface
253 capwapDot11Bss WLAN BSS Interface
12. Contributors 12. Contributors
This MIB module is based on contributions from Long Gao. This MIB module is based on contributions from Long Gao.
13. Acknowledgements 13. Acknowledgements
Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury and Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, and
Elwyn Davies for helpful comments on this document and guiding some Elwyn Davies for helpful comments on this document and guiding some
technique solution. technical solutions.
The authors also thank their friends and coworkers Fei Fang, Xuebin The authors also thank their friends and coworkers Fei Fang, Xuebin
Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao
Zhang, Xiansen Cai and Xiaolan Wan. Zhang, Xiansen Cai, and Xiaolan Wan.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs [IEEE.802-11.2007] "Information technology - Telecommunications and
to Indicate Requirement Levels", BCP 14, information exchange between systems - Local and
RFC 2119, March 1997. 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>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2119] Bradner, S., "Key words for use in RFCs to
and J. Schoenwaelder, Ed., "Structure of Indicate Requirement Levels", BCP 14, RFC 2119,
Management Information Version 2 March 1997.
(SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
and J. Schoenwaelder, Ed., "Textual Schoenwaelder, Ed., "Structure of Management
Conventions for SMIv2", STD 58, RFC 2579, Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999. April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, "Conformance Statements Schoenwaelder, Ed., "Textual Conventions for
for SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The [RFC2580] McCloghrie, K., Perkins, D., and J.
Interfaces Group MIB", RFC 2863, Schoenwaelder, "Conformance Statements for
June 2000. SMIv2", STD 58, RFC 2580, April 1999.
[RFC3418] Presuhn, R., "Management Information Base [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
(MIB) for the Simple Network Management Group MIB", RFC 2863, June 2000.
Protocol (SNMP)", STD 62, RFC 3418,
December 2002.
[I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y. [RFC3418] Presuhn, R., "Management Information Base (MIB)
Zhang, "CAPWAP Protocol Base MIB", for the Simple Network Management Protocol
draft-ietf-capwap-base-mib-07 (work in (SNMP)", STD 62, RFC 3418, December 2002.
progress), Jan 2010.
[RFC5415] Calhoun, P., Montemurro, M., and D. [RFC5415] Calhoun, P., Montemurro, M., and D. Stanley,
Stanley, "Control And Provisioning of "Control And Provisioning of Wireless Access
Wireless Access Points (CAPWAP) Protocol Points (CAPWAP) Protocol Specification",
Specification", RFC 5415, March 2009. RFC 5415, March 2009.
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC5416] Calhoun, P., Montemurro, M., and D. Stanley,
Stanley, "Control and Provisioning of "Control and Provisioning of Wireless Access
Wireless Access Points (CAPWAP) Protocol Points (CAPWAP) Protocol Binding for IEEE
Binding for IEEE 802.11", RFC 5416, 802.11", RFC 5416, March 2009.
March 2009.
[IEEE.802-11.2007] "Information technology - [RFC5833] Shi, Y., Ed., Perkins, D., Ed., Elliott, C., Ed.,
Telecommunications and information and Y. Zhang, Ed., "Control and Provisioning of
exchange between systems - Local and Wireless Access Points (CAPWAP) Protocol Base
metropolitan area networks - Specific MIB", RFC 5833, May 2010.
requirements - Part 11: Wireless LAN
Medium Access Control (MAC) and Physical
Layer (PHY) specifications",
IEEE Standard 802.11, 2007, <http://
standards.ieee.org/getieee802/download/
802.11-2007.pdf>.
14.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Stewart, "Introduction and Applicability "Introduction and Applicability Statements for
Statements for Internet-Standard Internet-Standard Management Framework",
Management Framework", RFC 3410, RFC 3410, December 2002.
December 2002.
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram
Transport Layer Security", RFC 4347,
April 2006.
RFC Editor - please remove the appendix before publication of the RFC
Appendix A. Appendix A. Changes between -06 and -05
1) Close IESG review issues raised by Elwyn Davies
--------------------------------------------------------------
Close some editorial problems such as giving an expansion to the [RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport
keywords WLAN, PHY and BSS. Layer Security", RFC 4347, April 2006.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd. Hangzhou H3C Tech. Co., Ltd.
Beijing R&D Center of H3C, Digital Technology Plaza, Beijing R&D Center of H3C, Digital Technology Plaza
NO.9 Shangdi 9th Street,Haidian District, NO. 9 Shangdi 9th Street, Haidian District
Beijing Beijing 100085
China(100085) China
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com EMail: rishyang@gmail.com
David Perkins (editor)
SNMPinfo David T. Perkins (editor)
288 Quailbrook Ct San Carlos, 228 Bayview Dr.
CA 94070 San Carlos, CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
EMail: dperkins@snmpinfo.com EMail: dperkins@dsperkins.com
Chris Elliott (editor) Chris Elliott (editor)
Cisco Systems, Inc. 1516 Kent St.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park Durham, NC 27707
27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-308-1216
EMail: chelliot@gmail.com EMail: chelliot@pobox.com
Yong Zhang (editor) Yong Zhang (editor)
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
EMail: yzhang@fortinet.com EMail: yzhang@fortinet.com
 End of changes. 148 change blocks. 
356 lines changed or deleted 342 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/