draft-ietf-capwap-802dot11-mib-03.txt   draft-ietf-capwap-802dot11-mib-04.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd Internet-Draft H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: September 4, 2009 SNMPinfo Expires: December 1, 2009 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
March 3, 2009 May 30, 2009
CAPWAP Protocol Binding MIB for IEEE 802.11 CAPWAP Protocol Binding MIB for IEEE 802.11
draft-ietf-capwap-802dot11-mib-03 draft-ietf-capwap-802dot11-mib-04
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 4, 2009. This Internet-Draft will expire on December 1, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 20 skipping to change at page 2, line 20
of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless
binding. binding.
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. Requirements and Constraints . . . . . . . . . . . . . . . 5 5.1. WLAN Profile . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Mechanism of Reusing Wireless Binding MIB Module . . . . . 5 5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6
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 . . . . 8 7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 7
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 . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13
10. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . . 20
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 21 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 21
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 21 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 21
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 21 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 21
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
14.1. Normative References . . . . . . . . . . . . . . . . . . . 21 14.1. Normative References . . . . . . . . . . . . . . . . . . . 21
14.2. Informative References . . . . . . . . . . . . . . . . . . 23 14.2. Informative References . . . . . . . . . . . . . . . . . . 23
Appendix A. Appendix A. Changes between -03 and -02 . . . . . . . 23 Appendix A. Appendix A. Changes between -04 and -03 . . . . . . . 23
1. Introduction 1. Introduction
The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines The CAPWAP Protocol [RFC5415] defines a standard, interoperable
a standard, interoperable protocol, which enables an Access protocol, which enables an Access Controller (AC) to manage a
Controller (AC) to manage a collection of Wireless Termination collection of Wireless Termination Points(WTPs). CAPWAP supports the
Points(WTPs). CAPWAP supports the use of various wireless use of various wireless technologies by the WTPs, with one specified
technologies by the WTPs, with one being specified in the CAPWAP in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416].
Protocol Binding for IEEE 802.11
[I-D.ietf-capwap-protocol-binding-ieee80211].
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 WLAN and a way to reuse the MIB module covers both configuration for WLAN and a way to reuse the IEEE 802.11
defined in IEEE 802.11 standard. MIB module [IEEE.802-11.2007].
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
[I-D.ietf-capwap-protocol-specification], the CAPWAP Protocol Binding [RFC5415], the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] and
for IEEE 802.11 [I-D.ietf-capwap-protocol-binding-ieee80211] and
CAPWAP Protocol Base MIB [I-D.ietf-capwap-base-mib]. CAPWAP Protocol Base MIB [I-D.ietf-capwap-base-mib].
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 PHY to transmit and receive contains an RF antenna and wireless PHY to transmit and receive
station traffic for wireless access networks. station traffic for wireless access networks.
skipping to change at page 4, line 24 skipping to change at page 4, line 22
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. In Split MAC mode all L2 wireless
data and management frames are encapsulated via the CAPWAP protocol data and management frames are encapsulated via the CAPWAP protocol
and exchanged between the AC and the WTPs. The Local MAC mode of and exchanged between the AC and the WTPs. The Local MAC mode of
operation allows for the data frames to be either locally bridged, or operation allows the data frames to be either locally bridged, or
tunneled as 802.3 frames. 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 binding for IEEE 802.11, provided in [RFC5416].
[I-D.ietf-capwap-protocol-binding-ieee80211].
WLAN: The WLAN refers to a logical component instantiated on a WTP WLAN: A WLAN refers to a logical component instantiated on a WTP
device. A single physical WTP may operate a number of WLANs. Each device. A single physical WTP MAY operate a number of WLANs. Each
Basic Service Set Identifier (BSSID) and its constituent wireless Basic Service Set Identifier (BSSID) and its constituent wireless
terminal radios is denoted as a distinct WLAN on a physical WTP. To terminal radios are denoted as a distinct WLAN on a physical WTP. To
support a physical WTP with multiple WLANs is an important feature 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 for CAPWAP protocol's 802.11 binding, and it is also for MIB module
design. design.
Wireless Binding MIB Module: Other Standards Developing Organizations Wireless Binding MIB Module: Other Standards Developing Organizations
(SDOs), such as IEEE already defined MIB module for a specific (SDOs), such as IEEE already defined MIB module for a specific
wireless technology, e.g., the MIB module in IEEE 802.11 standard wireless technology, e.g., the IEEE 802.11 MIB module
[IEEE.802-11.2007]. Such MIB modules are called as wireless binding [IEEE.802-11.2007]. Such MIB modules are called wireless binding MIB
MIB module defined by other SDOs. 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 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 [I-D.ietf-capwap-protocol-binding-ieee80211] example, the protocol of [RFC5416] defines WLAN conception. Also,
defines WLAN conception. Also, Local or Split MAC modes could be Local or Split MAC modes could be specified for a WLAN. The MAC mode
specified for a WLAN. The MAC mode for a WLAN is not in the scope of for a WLAN is not in the scope of IEEE 802.11 [IEEE.802-11.2007]. In
IEEE 802.11 [IEEE.802-11.2007]. In such cases, in addition to the such cases, in addition to the existing wireless binding MIB modules
existing wireless binding MIB modules defined by other SDOs, a CAPWAP defined by other SDOs, a CAPWAP protocol wireless binding MIB module
protocol wireless binding MIB module is required to be defined for a is required to be defined for a wireless binding.
wireless binding.
4. Conventions 4. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
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. Requirements and Constraints 5.1. WLAN Profile
The MIB module in IEEE 802.11 standard [IEEE.802-11.2007] already has A WLAN profile stores configuration parameters such as MAC type and
MIB objects definition for most IEEE 802.11 Message Elements in the tunnel mode for a WLAN. Each WLAN profile is identified by a profile
the CAPWAP Protocol Binding for IEEE 802.11 identifier. The operator needs to create WLAN profiles before WTPs
[I-D.ietf-capwap-protocol-binding-ieee80211]. As a CAPWAP Protocol connect to the AC. To provide WLAN service, the operator SHOULD bind
WLAN profiles to a WTP Virtual Radio Interface which corresponding to
a PHY radio. During the binding operation, the AC MUST select an
unused WLAN ID between one(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 WLAN ID is 16, the operator could configure more
than 16 WLAN Profiles on the AC.
5.2. Requirements and Constraints
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
Protocol Binding for IEEE 802.11 [RFC5416]. As a CAPWAP Protocol
802.11 binding MIB module, the CAPWAP-DOT11-MIB module MUST be able 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. Also, the to reuse such MIB objects in the IEEE 802.11 MIB module and support
functions such as MAC mode for WLAN in the functions such as MAC mode for WLAN in the [RFC5416] which are not in
[I-D.ietf-capwap-protocol-binding-ieee80211] are not in the scope of the scope of IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST
IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST support such support such functions.
functions.
In summary, the CAPWAP-DOT11-MIB module is designed to satisfy the In summary, the CAPWAP-DOT11-MIB module needs to support:
following requirements and constraints:
- Could easily reuse wireless binding MIB module in the IEEE 802.11 - Reuse of wireless binding MIB modules in the IEEE 802.11 standard;
standard;
- From AC to centrally manage and configure WLAN; - Centralized manage and configuration of WLAN profiles on the AC;
- Operators could configure MAC type and tunnel mode for a specific - Configuration of a MAC type and tunnel mode for a specific WLAN
WLAN. profile.
5.2. Mechanism of Reusing Wireless Binding MIB Module 5.3. Mechanism of Reusing Wireless Binding MIB Module
Before coming to details of CAPWAP-DOT11-MIB module, it will In the IEEE 802.11 MIB module, the MIB tables such as
introduce how it is able to reuse the MIB module in IEEE 802.11 Dot11AuthenticationAlgorithmsTable are able to support WLAN
standard. According to [I-D.ietf-capwap-protocol-binding-ieee80211], configuration (such as authentication algorithm), and these tables
each WLAN is identified by WLAN Id. In the MIB module of IEEE 802.11 use the ifIndex as the index which works well in the autonomous WLAN
standard, the MIB tables such as Dot11AuthenticationAlgorithmsTable architecture.
are able to support wireless configuration (such as authentication
algorithm), and these tables use ifIndex as index. To support 802.11
parameters for a specific WLAN, and consider that the operator has to
prepare configurations for each WLAN on the AC before WTPs connect to
AC. A WLAN could be abstracted as a 'WLAN Service Interface' on the
AC, and which could be identified by ifIndex. The MIB objects in the
MIB module of IEEE 802.11 standard which are associated with this
interface can be used to configure WLAN parameters for a WLAN, such
as Authentication Algorithm. On the AC, the MIB table
CapwapDot11WlanTable in the CAPWAP-DOT11-MIB module will indicate the
mapping relation between a 'WLAN Id" and ifIndex of a 'WLAN Service
Interface'. With ifIndex of a 'WLAN Service Interface', system is
able to reuse the MIB module in the IEEE 802.11 standard.
In the CAPWAP-BASE-MIB module, each PHY radio is identified by WTP Id Reuse of such wireless binding MIB modules is very important to
and radio ID, and has a corresponding 'WTP Virtual Radio Interface' centralized WLAN architectures. The key point is to abstract a WLAN
on the AC. The IEEE 802.11 MIB module associated with this interface profile as a WLAN Profile Interface on the AC, which could be
can be used to configure IEEE 802.11 wireless binding parameters for identified by an ifIndex. The MIB objects in the IEEE 802.11 MIB
radio such as RTS Threshold. The 'WLAN BSS Interface', created by module which are associated with this interface can be used to
binding 'WTP Virtual Radio Interface' and WLAN, is used for data configure WLAN parameters for the WLAN, such as authentication
forwarding. algorithm. With the ifIndex of a WLAN Profile Interface, the AC is
able to reuse the IEEE 802.11 MIB module.
6. Structure of the MIB Module 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 BSS
Interface, created by binding WLAN to WTP Virtual Radio Interface, is
used for data forwarding.
The MIB objects were derived from the CAPWAP protocol binding for 6. Structure of MIB Module
802.11 document [I-D.ietf-capwap-protocol-binding-ieee80211].
The MIB objects are derived from the CAPWAP protocol binding for IEEE
802.11 document [RFC5416].
1) capwapDot11WlanTable 1) capwapDot11WlanTable
The table is used for providing configuration such as MAC type and so The table allows the operator to display and configure WLAN profiles,
on for WLANs. For a specific WLAN which is identified by such as specifying the MAC type and tunnel mode for a WLAN. Also, it
capwapDot11WlanId, an interface of 'WLAN Service Interface' ifType helps the AC to configure a WLAN through the IEEE 802.11 MIB module.
will be created. By the ifIndex of interface, it provides a way to
reuse the MIB module in IEEE 802.11 standard. For example, according
to [I-D.ietf-capwap-protocol-binding-ieee80211], Auth Type needs to
be configured for a WLAN. In the IEEE 802.11 MIB module, the MIB
object dot11AuthenticationAlgorithm in the
dot11AuthenticationAlgorithmsTable is corresponding to Auth Type.
Considering both capwapDot11WlanTable and
dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP-
DOT11-MIB module are able to easily reuse
dot11AuthenticationAlgorithm object in IEEE 802.11 MIB module. It is
same for other objects in the MIB module of IEEE 802.11 standard.
2) capwapDot11WlanBindTable 2) capwapDot11WlanBindTable
The table provides a way to bind WLAN to a radio, then supports The table provides a way to bind WLAN profiles to a WTP Virtual Radio
multiple WLANs on a physical WTP. The binding operation will Interface which has a PHY radio corresponding to it. A binding
dynamically create 'WLAN BSS Interface', and this logical interface operation dynamically creates a WLAN BSS Interface, which is used for
is used for data forwarding function. 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 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 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 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. The CAPWAP-DOT11-MIB entity and certain other system-wide data.
module does not duplicate those objects.
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.
For each WLAN, it will have a logical interface of 'WLAN Service Each WLAN profile corresponds to a WLAN Profile Interface on the AC.
Interface' responding to it on the AC. The interface MUST be modeled The interface MUST be modeled as an ifEntry, and ifEntry objects such
as an ifEntry and provide appropriate interface information. 'WLAN as ifIndex, ifDescr, ifName, ifAlias are to be used as per [RFC2863].
Service Interface' provides a way to configure IEEE 802.11 parameters The WLAN Profile Interface provides a way to configure IEEE 802.11
for a specific WLAN, and reuse the MIB module in IEEE 802.11 parameters for a specific WLAN, and reuse the IEEE 802.11 MIB module.
standard.
Also, the system (AC) MUST have a mechanism that preserves the values Also, the AC MUST have a mechanism that preserves the value of the
of ifIndex of 'WLAN Service Interface' ifType in the ifTable at AC WLAN Profile Interfaces' ifIndexes in the ifTable at AC reboot.
reboot.
To provide data forwarding service, system will dynamically create To provide data forwarding service, the AC dynamically creates WLAN
logical interface of 'WLAN BSS Interface'. The interface MUST be BSS Interfaces. A WLAN BSS Interface MUST be modeled as an ifEntry,
modeled as an ifEntry and provide appropriate interface information. and ifEntry objects such as ifIndex, ifDescr, ifName, ifAlias are to
The interface enables a single physical WTP to support multiple be used as per [RFC2863]. The interface enables a single physical
WLANs. WTP to support multiple WLANs.
Also, the system (AC) MUST have a mechanism that preserves the values Also, the AC MUST have a mechanism that preserves the value of the
of ifIndex of 'WLAN BSS Interface' ifType in the ifTable at AC WLAN BSS Interfaces' ifIndexes in the ifTable at AC reboot.
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, CAPWAP-BASE-MIB module has a and radio objects. Especially, it provides the WTP Virtual Radio
mechanism of 'WTP Virtual Radio Interface' which enable system to Interface mechanism to enable the AC to reuse the IEEE 802.11 MIB
reuse the MIB module in IEEE 802.11 standard. With it, operator module. With this mechanism, an operator could configure an IEEE
could configure an IEEE 802.11 AP radio's parameter and query radio's 802.11 radio's parameters and view the radio's traffic statistics on
traffic statistics. Based on CAPWAP-BASE-MIB module, CAPWAP-DOT11- the AC. Based on the CAPWAP-BASE-MIB module, the CAPWAP-DOT11-MIB
MIB module provides more information from WLAN perspective. module provides more WLAN information.
7.4. Relationship to MIB Module in IEEE 802.11 Standard 7.4. Relationship to MIB Module in IEEE 802.11 Standard
Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface' With the ifIndex of WLAN Profile Interface and WLAN BSS Interface,
ifType, the MIB module is able to reuse MIB module in the IEEE 802.11 the MIB module is able to reuse the IEEE 802.11 MIB module
standard [IEEE.802-11.2007]. The CAPWAP-DOT11-MIB module does not [IEEE.802-11.2007]. The CAPWAP-DOT11-MIB module does not duplicate
duplicate those objects in the MIB module of IEEE 802.11 standard. those objects in the IEEE 802.11 MIB module.
In the CAPWAP Protocol Binding for IEEE 802.11 The CAPWAP Protocol Binding for IEEE 802.11 [RFC5416] involves some
[I-D.ietf-capwap-protocol-binding-ieee80211], it involves a part of of the MIB objects defined in IEEE 802.11 standard. Although CAPWAP-
MIB objects defined by IEEE 802.11 standard. Although CAPWAP-DOT11- DOT11-MIB module uses it [RFC5416] as a reference, it could reuse all
MIB module uses it [I-D.ietf-capwap-protocol-binding-ieee80211] as a the MIB objects in the IEEE 802.11 standard , and is not limited by
reference, it could reuse all the MIB objects in the IEEE 802.11 the scope of CAPWAP Protocol Binding for IEEE 802.11.
standard , and not 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 [I-D.ietf-capwap-base-mib].
8. Example of CAPWAP-DOT11-MIB Module Usage 8. Example of CAPWAP-DOT11-MIB Module Usage
The following is a whole example for configuration and management of 1) Create a WTP profile
WTP, radio and WLAN for IEEE 802.11 binding.
1) Identify the PHY radio by 'WTP Virtual Radio Interface' Suppose the WTP's serial identifier is '12345678'. Creates a WTP
profile for it through the CapwapBaseWtpProfileTable
[I-D.ietf-capwap-base-mib] as follows:
According to [I-D.ietf-capwap-protocol-specification], each radio on In CapwapBaseWtpProfileTable
a WTP will be identified by a radio Id. Each WTP could be identified {
by its serial number. capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 12345678',
capwapBaseWtpProfileWTPSerialId = '12345678',
capwapBaseWtpProfileWTPModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 12345678',
capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIp = '192.168.0.100',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.168.0.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
capwapBaseWtpProfileWtpReportInterval = 120,
capwapBaseWtpProfileWtpSilentInterval = 30,
capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpWaitDTLSTimer = 60,
capwapBaseWtpProfileWtpEcnSupport = limited(0)
}
Suppose a WTP's serial number is '12345678', and first radio id is 1. Suppose the WTP with model number 'WTP123' has one PHY radio and this
On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' PHY radio is identified by ID 1. The creation of this WTP profile
ifType is 10 which represents the PHY radio 1. The following triggers the AC to automatically create a WTP Virtual Radio Interface
information is obtained in the CapwapBaseWirelessBindingTable. 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.
In CapwapBaseWirelessBindingTable In CapwapBaseWirelessBindingTable
{ {
capwapBaseWtpStateWtpId = '12345678', capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1, capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10, capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2) capwapBaseWirelessBindingType = dot11(2)
} }
By the mechanism of 'WTP Virtual Radio Interface', it seems WTP PHY
radios are located on the AC. The interface of 'WTP Virtual Radio The WTP Virtual Radio Interfaces on the AC correspond to the PHY
Interface' ifType is modeled by ifTable [RFC2863]. radios on the WTP. The WTP Virtual Radio Interface is modeled by
ifTable [RFC2863].
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface', ifDescr = 'WTP Virtual Radio Interface',
ifType = xxx, ifType = xxx,
RFC Editor - please replace xxx with the value RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WTP Virtual Radio Interface' allocated by IANA for IANAifType of WTP Virtual Radio Interface
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '000000', ifPhysAddress = '000000',
ifAdminStatus = true, ifAdminStatus = true(1),
ifOperStatus = false, 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) Configure specific wireless binding parameters for 'WTP Virtual 2) Query the ifIndexes of WTP Virtual Radio Interfaces
Radio Interface'
It will be done on the AC through the MIB module defined in IEEE Before configuring PHY radios, the operator needs to get the
802.11 standard. ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY
radios.
For example, to configure parameter for 'WTP Virtual Radio Interface' As the CapwapBaseWirelessBindingTable already stores the mappings
by Dot11OperationTable [IEEE.802-11.2007]. 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 a invalid ifIndex
value (0) is returned.
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 a invalid ifIndex value (0), so the 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.
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
module.
The following shows an example of configuring parameters for a WTP
Virtual Radio Interface with ifIndex 10 through the
Dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0, dot11MACAddress = '000000',
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'
} }
In the example, it supposes ifIndex of a 'WTP Virtual Radio 4) Configure a WLAN Profile
Interface' is 10.
3) Configure WLAN
WLAN configuration will be done through CAPWAP-DOT11-MIB Module, and WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB
the MIB module defined in IEEE 802.11 standard Module, and IEEE 802.11 MIB module.
First step is to create a 'WLAN Service Interface' through CAPWAP- The first step is to create a WLAN Profile Interface through the
DOT11-MIB Module on the AC. CAPWAP-DOT11-MIB module on the AC.
Here supposes to configure a WLAN which is identified by For example, when you configure a WLAN profile which is identified by
capwapDot11WlanId 1, and CapwapDot11WlanTable would create a row capwapDot11WlanProfileId 1, the CapwapDot11WlanTable creates the
object for it. following row object for it.
In CapwapDot11WlanTable In CapwapDot11WlanTable
{ {
capwapDot11WlanId = 1, capwapDot11WlanProfileId = 1,
capwapDot11WlanServiceIfIndex = 20, capwapDot11WlanProfileIfIndex = 20,
capwapDot11WlanMacType = splitMAC(2), capwapDot11WlanMacType = splitMAC(2),
capwapDot11WlanTunnelMode = dot3Tunnel(2), capwapDot11WlanTunnelMode = dot3Tunnel(2),
capwapDot11WlanRowStatus = create capwapDot11WlanRowStatus = createAndGo(4)
} }
The creation operation of a row object would trigger AC system to The creation of a row object triggers the AC to automatically create
automatically create a 'WLAN Service Interface' and it is identified a WLAN Profile Interface and it is identified by ifIndex 20 without
by ifIndex 20. It does not require operator to manually create a manual intervention.
'WLAN Service Interface'.
Corresponding to 'WLAN Service Interface', it MUST be modeled as an A WLAN Profile Interface MUST be modeled as an ifEntry on the AC
ifEntry on the AC and provide appropriate interface information. which provides appropriate interface information. The
CapwapDot11WlanTable would keep the mapping relationship between CapwapDot11WlanTable stores the mappings between
capwapDot11WlanId and ifIndex of a 'WLAN Service Interface'. capwapDot11WlanProfileIds and the ifIndexes of WLAN Profile
Interfaces.
In ifTable In ifTable
{ {
ifIndex = 20, ifIndex = 20,
ifDescr = 'WLAN Service Interface', ifDescr = 'WLAN Profile Interface',
ifType = xxx, ifType = xxx,
RFC Editor - please replace xxx with the value RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WLAN Service Interface' allocated by IANA for IANAifType of 'WLAN Profile Interface'
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0, ifPhysAddress = '000000',
ifAdminStatus = true, ifAdminStatus = true(1),
ifOperStatus = true, 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
} }
Second step is to configure WLAN parameters of 'WLAN Service The second step is to configure WLAN parameters for the WLAN Profile
Interface' through the MIB module defined in IEEE 802.11 standard on Interface through the IEEE 802.11 MIB module on the AC.
the AC.
Suppose operator to configure authentication algorithm for a WLAN. The following example configures an authentication algorithm for a
WLAN.
In Dot11AuthenticationAlgorithmsTable In Dot11AuthenticationAlgorithmsTable
{ {
ifIndex = 20, ifIndex = 20,
dot11AuthenticationAlgorithmsIndex = 1, dot11AuthenticationAlgorithmsIndex = 1,
dot11AuthenticationAlgorithm = Shared Key, dot11AuthenticationAlgorithm = Shared Key(2),
dot11AuthenticationAlgorithmsEnable = true dot11AuthenticationAlgorithmsEnable = true(1)
} }
Here ifIndex 20 is for interface of 'WLAN Service Interface' ifType. Here ifIndex 20 identifies the WLAN Profile Interface and the index
Suppose the index of authentication algorithm is 1. of the configured authentication algorithm is 1.
4) Bind WLAN to WTP radio 5) Bind WLAN Profiles to a WTP radio
On the AC, through CapwapDot11WlanBindTable in the CAPWAP-DOT11-MIB, On the AC, the CapwapDot11WlanBindTable in the CAPWAP-DOT11-MIB
it configures which WLAN (identified by capwapDot11WlanId) will be stores the bindings between WLAN profiles(identified by
provided on which 'WTP Virtual Radio Interface' (identified by capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces
ifIndex). (identified by the ifIndex).
Here supposes to bind a WLAN (capwapDot11WlanId is 1) with a For example, after the operator binds a WLAN profile with
interface of 'WTP Virtual Radio Interface'(ifIndex is 10). The capwapDot11WlanProfileId 1 to WTP Virtual Radio Interface with
CapwapDot11WlanBindTable would create a row object for it. ifIndex 10, the CapwapDot11WlanBindTable creates the following row
object.
In CapwapDot11WlanBindTable In CapwapDot11WlanBindTable
{ {
ifIndex = 10, ifIndex = 10,
capwapDot11WlanId = 1, capwapDot11WlanProfileId = 1,
capwapDot11WlanBindBssIfIndex = 30, capwapDot11WlanBindBssIfIndex = 30,
capwapDot11WlanBindBssRowStatus = create capwapDot11WlanBindRowStatus = createAndGo(4)
} }
Suppose capwapDot11WlanMacType of WLAN is splitMAC(2), the creation If the capwapDot11WlanMacType of the WLAN is splitMAC(2), the
operation of a row object on the CapwapDot11WlanBindTable would creation of the row object in the CapwapDot11WlanBindTable triggers
trigger AC system to automatically create a 'WLAN BSS Interface' and the AC to automatically create a WLAN BSS Interface identified by
it is identified by ifIndex 30. It does not require operator to ifIndex 30 without manual intervention.
manually create a 'WLAN BSS Interface'.
Corresponding to 'WLAN BSS Interface', it MUST be modeled as an
ifEntry on the AC and provide appropriate interface information.
CapwapDot11WlanBindTable would keep the mapping relationship among
ifIndex of a 'WTP Virtual Radio Interface', WLAN and ifIndex of a
'WLAN BSS Interface'.
5) WTP reports its current configuration status 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.
After join phase and before WTP get configuration from AC, it will 6) Current configuration status report from the WTP to the AC
report its current configuration status to AC through configuration Before a WTP that has joined the AC gets configuration from the AC,
status request message. The MIB data will be updated on the AC. As it needs to report its current configuration status by sending a
an example, for ifIndex 10 (which identifies an interface of 'WLAN configuration status request message to the AC, which uses the
Virtual Radio Interface' ifType), its ifOperStatus in ifTable will be message to update corresponding MIB objects on the AC. For example,
updated with current radio operational status. 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].
6) Query WTP and radio statistics data 7) Query WTP and radio statistics data
After WTPs come to run status, operator could query WTP and radio After WTPs start to run, the operator could query WTP and radio
statistics data through CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB module. statistics data through the CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB
For example, through dot11CountersTable [IEEE.802-11.2007], operator modules. For example, through the dot11CountersTable
could query counter data for radio which is identified by ifIndex of [IEEE.802-11.2007], the operator could query counter data of a radio
a 'WLAN Virtual Radio Interface'. which is identified by the ifIndex of the corresponding WLAN Virtual
Radio Interface.
7) Query other statistics data 8) Query other statistics data
For example, operator could query the configuration of WLAN through The operator could query the configuration of a WLAN through the
Dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and statistic Dot11AuthenticationAlgorithmsTable [IEEE.802-11.2007] and the
data of 'WLAN BSS Interface' through ifTable; statistic 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 "200903030000Z" -- March 3th, 2009 LAST-UPDATED "200905300000Z" -- May 30th, 2009
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 Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China(100085) District,Beijing,China(100085)
Email: young@h3c.com Email: young@h3c.com
David T. Perkins David T. Perkins
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
skipping to change at page 14, line 13 skipping to change at page 14, line 38
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2009 The Internet Society. This version of "Copyright (C) 2009 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. 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 "200903030000Z" REVISION "200905300000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxx" "Initial version, published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual conventions -- Textual conventions
CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents an unique identifier of a WLAN. "Represents the unique identifier of a WLAN."
According to REFERENCE, the value of WLAN ID MUST be between SYNTAX Unsigned32 (1..16)
one (1) and 16, and it is specified for a radio of WTP.
The SYNTAX of capwapDot11WlanId is defined as CapwapDot11WlanIdProfileTC ::= TEXTUAL-CONVENTION
CapwapDot11WlanIdTC, and capwapDot11WlanId is WLAN configured DISPLAY-HINT "d"
on the AC (NOT on the WTP). STATUS current
As AC could have more WLANs configured than WTP, the value of DESCRIPTION
capwapDot11WlanId could be more than 16. "Represents the unique identifier of a WLAN profile."
SYNTAX CapwapDot11WlanIdTC "
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
SYNTAX Unsigned32 (1..512) SYNTAX Unsigned32 (1..512)
-- Top level components of this MIB module -- Top level components of this MIB module
-- Tables, Scalars -- Tables, Scalars
capwapDot11Objects OBJECT IDENTIFIER capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 } ::= { capwapDot11MIB 1 }
-- Conformance -- Conformance
capwapDot11Conformance OBJECT IDENTIFIER capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 } ::= { capwapDot11MIB 2 }
-- capwapDot11WlanTable Table -- capwapDot11WlanTable Table
capwapDot11WlanTable OBJECT-TYPE capwapDot11WlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WlanEntry SYNTAX SEQUENCE OF CapwapDot11WlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display and control WLANs. "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 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 display and control WLANs." "A set of objects that store the settings of a WLAN profile."
INDEX { capwapDot11WlanId } INDEX { capwapDot11WlanProfileId }
::= { capwapDot11WlanTable 1 } ::= { capwapDot11WlanTable 1 }
CapwapDot11WlanEntry ::= CapwapDot11WlanEntry ::=
SEQUENCE { SEQUENCE {
capwapDot11WlanId CapwapDot11WlanIdTC, capwapDot11WlanProfileId CapwapDot11WlanIdProfileTC,
capwapDot11WlanServiceIfIndex InterfaceIndex, capwapDot11WlanProfileIfIndex InterfaceIndex,
capwapDot11WlanMacType CapwapBaseMacTypeTC, capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC, capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WlanRowStatus RowStatus capwapDot11WlanRowStatus RowStatus
} }
capwapDot11WlanId OBJECT-TYPE capwapDot11WlanProfileId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdTC SYNTAX CapwapDot11WlanIdProfileTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the WLAN Id for a WLAN which has a "Represents the identifier of a WLAN profile which has a
capwapDot11WlanServiceIfIndex interface corresponding to it." corresponding capwapDot11WlanProfileIfIndex."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WlanEntry 1 } ::= { capwapDot11WlanEntry 1 }
capwapDot11WlanServiceIfIndex 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 Service 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 ifIndex. identified by the same value of the ifIndex.
The creation operation of a row object on the The creation of a row object in the capwapDot11WlanTable
capwapDot11WlanTable would trigger AC system to automatically triggers the AC to automatically create an WLAN Profile
create a 'WLAN Service Interface' and it is identified by Interface identified by an ifIndex without manual
ifIndex. It does not require operator to manually create a intervention.
'WLAN Service Interface'. Most MIB tables in the IEEE 802.11 MIB module
Before WTPs connect to AC and get configuration, operator [IEEE.802-11.2007] use an ifIndex to identify an interface
will prepare configuration for them. For a specific WLAN, to facilitate the configuration and maintenance, for example,
a logical interface of 'WLAN Service Interface' dot11AuthenticationAlgorithmsTable.
ifType will be created by system, and operator could Using the ifIndex of a WLAN Profile Interface, the Operator
configure WLAN parameter through it. could configure a WLAN through the IEEE 802.11 MIB module."
For example, according to IEEE 802.11 '6.1. IEEE 802.11
Add WLAN' in the [I-D.ietf-capwap-protocol-binding-ieee80211],
operator could configure Auth Type for a WLAN. The 'WLAN
Service Interface' provides a way to uniquely identify each
WLAN by logical on the AC. As most MIB modules use ifIndex to
identify an interface for configuration and statistic data,
for example, dot11AuthenticationAlgorithmsTable in IEEE 802.11
MIB module use ifIndex as index, and
dot11AuthenticationAlgorithm object is for Auth Type mentioned
in the CAPWAP '6.1. IEEE 802.11 Add WLAN'
[I-D.ietf-capwap-protocol-binding-ieee80211], With the way of
'WLAN Service Interface', it will easily reuse MIB table like
dot11AuthenticationAlgorithmsTable in the IEEE 802.11 standard,
while only care for other configurations like
capwapDot11WlanTunnelMode."
::= { 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 xxx." 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 type to be used for 802.11 data "Represents the frame tunneling mode to be used for IEEE 802.11
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 Id, and Bits are exclusive with each other for a specific WLAN profile,
only one tunnel mode could be configured. and only one tunnel mode could be configured.
If 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 xxx." 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 in "This variable is used to create, modify, and/or delete a row
this table." in this table.
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 } ::= { 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 of objects that configure which WLAN "A table that stores bindings between WLAN profiles
(identified by capwapDot11WlanId) will be provided on (identified by capwapDot11WlanProfileId) and
which 'WTP Virtual Radio Interface' (identified by ifIndex) WTP Virtual Radio Interfaces. The WTP Virtual Radio Interfaces
Also, display and control the mapping on the AC correspond to PHY radios on the WTPs. It also stores
relationship between interface of 'WTP Virtual Radio Interface' the mappings between WLAN IDs and WLAN BSS Interfaces.
interface and interface of 'WLAN BSS Interface'. Values of all objects in this table are persistent at
The PHY address for interface of 'WTP Virtual Radio restart/reboot."
Interface' ifType will be base BSSID address for PHY
radio."
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 xxx." 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 display the mapping relationship "A set of objects that stores the binding of a WLAN profile
between interface of 'WTP Virtual Radio Interface' and to a WTP Virtual Radio Interface. It also stores the mapping
interface of 'WLAN BSS Interface'. between WLAN ID and WLAN BSS Interface.
The INDEX object ifIndex is the ifIndex of an interface The INDEX object ifIndex is the ifIndex of a WTP Virtual
'WTP Virtual Radio Interface'." Radio Interface."
INDEX { ifIndex, capwapDot11WlanId } INDEX { ifIndex, capwapDot11WlanProfileId }
::= { capwapDot11WlanBindTable 1 } ::= { capwapDot11WlanBindTable 1 }
CapwapDot11WlanBindEntry ::= CapwapDot11WlanBindEntry ::=
SEQUENCE { SEQUENCE {
capwapDot11WlanBindWlanId CapwapDot11WlanIdTC,
capwapDot11WlanBindBssIfIndex InterfaceIndex, capwapDot11WlanBindBssIfIndex InterfaceIndex,
capwapDot11WlanBindBssRowStatus RowStatus 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 (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 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 ifIndex. The ifIndex here identified by the same value of the ifIndex.
is for an interface of 'WLAN BSS Interface'. The ifIndex here is for a WLAN BSS Interface.
For a WLAN configuration on a radio, an interface of 'WLAN
BSS Interface' will correspond to it. The creation of a row object in the capwapDot11WlanBindTable
The creation operation of a row object on the triggers the AC to automatically create a WLAN BSS Interface
capwapDot11WlanBindTable would trigger AC system to identified by an ifIndex without manual intervention.
automatically create a 'WLAN BSS Interface' and it is The PHY address of the capwapDot11WlanBindBssIfIndex is the
identified by ifIndex. It does not require operator to manually BSSID. While manufacturers are free to assign BSSIDs by using
create a 'WLAN BSS Interface'. any arbitrary mechanism, it is advised that where possible the
The PHY address for capwapDot11WlanBindBssIfIndex is BSSID.
While manufacturers are free to assign BSSIDs using 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 xxx." RFC 5416."
::= { capwapDot11WlanBindEntry 1 } ::= { capwapDot11WlanBindEntry 2 }
capwapDot11WlanBindBssRowStatus 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."
::= { capwapDot11WlanBindEntry 2 } ::= { 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
::= { capwapDot11Conformance 2 } ::= { capwapDot11Conformance 2 }
skipping to change at page 19, line 32 skipping to change at page 20, line 7
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
capwapDot11WlanGroup, capwapDot11WlanGroup,
capwapDot11WlanBindGroup capwapDot11WlanBindGroup
} }
::= { capwapDot11Compliances 1 } ::= { capwapDot11Compliances 1 }
capwapDot11WlanGroup OBJECT-GROUP capwapDot11WlanGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDot11WlanServiceIfIndex, capwapDot11WlanProfileIfIndex,
capwapDot11WlanMacType, capwapDot11WlanMacType,
capwapDot11WlanTunnelMode, capwapDot11WlanTunnelMode,
capwapDot11WlanRowStatus capwapDot11WlanRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "A collection of objects which are used to configure
property of WLAN." the properties of a WLAN profile."
::= { capwapDot11Groups 1 } ::= { capwapDot11Groups 1 }
capwapDot11WlanBindGroup OBJECT-GROUP capwapDot11WlanBindGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDot11WlanBindWlanId,
capwapDot11WlanBindBssIfIndex, capwapDot11WlanBindBssIfIndex,
capwapDot11WlanBindBssRowStatus capwapDot11WlanBindRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "A collection of objects which are used to bind the
WLAN BSS." 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 followings 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, also change the behavior of WLAN system such as MAC
type. 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
skipping to change at page 21, line 17 skipping to change at page 21, line 32
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 values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
capwapDot11MIB { mib-2 XXX } capwapDot11MIB { mib-2 XXX }
11.2. IANA Considerations for ifType 11.2. IANA Considerations for ifType
Require IANA to assign a ifType for 'WLAN Service Interface' type. Require IANA to assign a ifType for the WLAN Profile Interface.
Require IANA to assign a ifType for 'WLAN BSS Interface' type. Require IANA to assign a ifType for the 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
The authors wish to thank David Harrington, Fei Fang, Yu Liu, Sachin The authors wish to thank David Harrington, Fei Fang, Xuebin Zhu, Hao
Dutta, Yujin Zhao, Haitao Zhang, Hao Song. Song, Yu Liu, Sachin Dutta, Yujin Zhao, Haitao Zhang, Hao Song.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words [RFC2119] Bradner, S., "Key words for use in RFCs
for use in RFCs to to Indicate Requirement Levels", BCP 14,
Indicate Requirement
Levels", BCP 14,
RFC 2119, March 1997. RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed.,
Perkins, D., Ed., and and J. Schoenwaelder, Ed., "Structure of
J. Schoenwaelder, Ed., Management Information Version 2
"Structure of (SMIv2)", STD 58, RFC 2578, April 1999.
Management Information
Version 2 (SMIv2)",
STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed.,
Perkins, D., Ed., and and J. Schoenwaelder, Ed., "Textual
J. Schoenwaelder, Ed., Conventions for SMIv2", STD 58, RFC 2579,
"Textual Conventions April 1999.
for SMIv2", STD 58,
RFC 2579, April 1999.
[RFC2580] McCloghrie, K., [RFC2580] McCloghrie, K., Perkins, D., and J.
Perkins, D., and J. Schoenwaelder, "Conformance Statements
Schoenwaelder, for SMIv2", STD 58, RFC 2580, April 1999.
"Conformance Statements
for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. [RFC2863] McCloghrie, K. and F. Kastenholz, "The
Kastenholz, "The Interfaces Group MIB", RFC 2863,
Interfaces Group MIB", June 2000.
RFC 2863, June 2000.
[RFC3418] Presuhn, R., [RFC3418] Presuhn, R., "Management Information Base
"Management Information (MIB) for the Simple Network Management
Base (MIB) for the Protocol (SNMP)", STD 62, RFC 3418,
Simple Network
Management Protocol
(SNMP)", STD 62,
RFC 3418,
December 2002. December 2002.
[I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y.
Elliott, C., and Y. Zhang, "CAPWAP Protocol Base MIB",
Zhang, "CAPWAP Protocol draft-ietf-capwap-base-mib-04 (work in
Base MIB", draft-ietf- progress), February 2009.
capwap-base-mib-03
(work in progress),
November 2008.
[I-D.ietf-capwap-protocol-specification] Montemurro, M., [RFC5415] Calhoun, P., Montemurro, M., and D.
Stanley, D., and P. Stanley, "Control And Provisioning of
Calhoun, "CAPWAP Wireless Access Points (CAPWAP) Protocol
Protocol Specification", RFC 5415, March 2009.
Specification", draft-
ietf-capwap-protocol-
specification-15 (work
in progress),
November 2008.
[I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M., [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, D., and P. Stanley, "Control and Provisioning of
Calhoun, "CAPWAP Wireless Access Points (CAPWAP) Protocol
Protocol Binding for Binding for IEEE 802.11", RFC 5416,
IEEE 802.11", draft- March 2009.
ietf-capwap-protocol-
binding-ieee80211-12
(work in progress),
November 2008.
[IEEE.802-11.2007] "Information technology [IEEE.802-11.2007] "Information technology -
- Telecommunications Telecommunications and information
and information exchange between systems - Local and
exchange between metropolitan area networks - Specific
systems - Local and requirements - Part 11: Wireless LAN
metropolitan area Medium Access Control (MAC) and Physical
networks - Specific Layer (PHY) specifications",
requirements - Part 11: IEEE Standard 802.11, 2007, <http://
Wireless LAN Medium standards.ieee.org/getieee802/download/
Access Control (MAC)
and Physical Layer
(PHY) specifications",
IEEE Standard 802.11,
2007, <http://
standards.ieee.org/
getieee802/download/
802.11-2007.pdf>. 802.11-2007.pdf>.
14.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Partain, D., and B. Stewart, "Introduction and Applicability
Stewart, "Introduction Statements for Internet-Standard
and Applicability Management Framework", RFC 3410,
Statements for
Internet-Standard
Management Framework",
RFC 3410,
December 2002. December 2002.
[RFC4347] Rescorla, E. and N. [RFC4347] Rescorla, E. and N. Modadugu, "Datagram
Modadugu, "Datagram Transport Layer Security", RFC 4347,
Transport Layer
Security", RFC 4347,
April 2006. April 2006.
Appendix A. Appendix A. Changes between -03 and -02 Appendix A. Appendix A. Changes between -04 and -03
T1. T4. In order for ifIndex to be used as a common handler for the
CAPWAP MIB and for the interface specific MIB modules like a dot11
MIB from IEEE one needs to ensure that the same numbering scheme and
mapping is used by all MIB modules, and that it behaves identically
for events like interface card swapping, reset or power loss. I do
not see how this can happen, I am not sure that this is possible at
all, and in any case there is no text in the document that explains
this mechanism.
--------------------------------------------------------------
In the Capwap Digest, Vol 39, Issue 4, we gave the text to explain a
mechanism that preserves the values of ifIndex, Request mailing list
to confirm it.
In the section of "Relationship to the IF-MIB", add text:
Also, the system (AC) MUST have a mechanism that preserves the values
of ifIndex of 'WLAN Service Interface' ifType in the ifTable at AC
reboot.
Also, the system (AC) MUST have a mechanism that preserves the values
of ifIndex of 'WLAN BSS Interface' ifType in the ifTable at AC
reboot.
T2. Is the WLAN Service interface described in Section 7.2 modeled
by capwapDot11WlanConfigTable? If so please say it and make this
clear by using a more explicit naming convention. The model here is
not clear to me. On one hand you say 'the interface SHOULD be
modeled as an ifEntry ...' Why only a SHOULD and not a MUST? What
is the procedure for the manager? Is he looking for all 802.11
interfaces on the AC and then creates manually a WLAN Service entry
in the table for each? What if the ifNumber does not correspond to a
802.11 interface? What if the 802.11 interface disappears?
-----------------------------------------------------------------
1) The "WLAN Service interface" is modeled by
capwapDot11WlanConfigTable, and capwapDot11WlanConfigTable is rename
as capwapDot11WlanTable.
2) Yes, the the interface MUST be modeled as an ifEntry, not SHOULD
be
3) What is the procedure for the manager? Is he looking for all
802.11 interfaces on the AC and then creates manually a WLAN Service
entry in the table for each?
Please refer to the section of Example of CAPWAP-DOT11-MIB Module
Usage (the section is updated in the new version).
The creation operation of a row object on capwapDot11WlanTable would
trigger system to create "WLAN service Interface", and it does not
require operator to manually create a "WLAN service Interface".
In the section of "Relationship to the IF-MIB", add text:
Also, the system (AC) MUST have a mechanism that preserves the values
of ifIndex of 'WLAN Service Interface' ifType in the ifTable at AC
reboot.
T3. What 'could be always enabled' means for ifAdminStatus and
ifOperStatus in the WLAN Service Interface table? Either change this
to MUST or explain in what cases these should be other than enabled.
--------------------------------------------------------------
The section for interpration of specific MIB objects in the iftable
was removed in the new version. Reader could refer to RFC2863
T4. What does the statement that 'the other objects such as
ifInOctets ... are unused' relative to the VLAN Service interface
mean? Counters are always zero?
--------------------------------------------------------------
The section for interpration of specific MIB objects in the iftable
was removed in the new version. Reader could refer to RFC2863
T5. In 7.4 - does the text mean that the manager can reuse objects
from the IEEE 802.11 MIB modules, or that values of these objects are
being duplicates in this MIB module? (why? Which ones?) In any case
the IEEE 802.11 standard that defines these objects must be a
Normative Reference for this document.
-----------------------------------------------------------------
Yes
1)the text mean that the manager can reuse objects from the IEEE
802.11 MIB modules, and the section of "Mechanism of Reusing Wireless
Binding MIB Module" give explain to it.
2) also, add one text of "The CAPWAP-DOT11-MIB module does not
duplicate those objects in the MIB module of IEEE 802.11 standard."
in the section of "7.4. Relationship to MIB Module in IEEE 802.11
Standard"
3) yes, IEEE 802.11 standard was added as a Normative Reference.
T6. The RFCs that define all MIB modules required for IMPORTSs must
be Normative References to this document.
-----------------------------------------------------------------
add reference to RFC3411 in the section of "MIB modules required for
IMPORTS", add "SNMP-FRAMEWORK-MIB [RFC3411],"
T7. The value of the object capwapBaseWTPId in the example is the
string '12345678' not the integer 12345678
-----------------------------------------------------------------
Yes, it is change into '12345678'
T8. The names of the objects in the capwapDot11WlanConfigTable are
not consistent (similar prefix) to capwapDot11WlanConfigEntry.
---------------------------------------------------------
Yes, they are changed with:
CapwapDot11WlanEntry ::=
SEQUENCE {
capwapDot11WlanId CapwapDot11WlanIdTC,
capwapDot11WlanServiceIfIndex InterfaceIndex,
capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WlanRowStatus RowStatus
}
T9. The names of the objects in the capwapDot11WlanBindTable are not
consistent (similar prefix) to capwapDot11WlanBindEntry.
---------------------------------------------------------
Yes, they are changed with:
CapwapDot11WlanBindEntry ::=
SEQUENCE {
capwapDot11WlanBindBssIfIndex InterfaceIndex,
capwapDot11WlanBindBssRowStatus RowStatus
}
T10. What does 'Bits are exclusive for each other for a specific
WLAN Id' mean for capwapDot11WlanTunnelMode? That only one tunnel
mode can be configured (one bit set)? I assume this does not include
the bit unused(0). What happens if the manager sets more than one
bit, ore no bit, or unused(0) - how does the agent behave in this
case?
-----------------------------------------------------------------
1) Yes, unused(0) is removed.
2) The description is updated with:
Bits are exclusive with each other for a specific WLAN Id, and only
one tunnel mode could be configured. If 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."
T11. What is the persistency of the capwapDot11WlanTunnelMode at
agent reboot? Is the whole table persistent at agent reboot?
-----------------------------------------------------------------
Yes, it should be whole table persistent instead of previous
statement "Values of all read-create objects in this table are
persistent at restart/reboot."
T12. I do not understand how does row creation in the
capwapDot11WlanBindTable work. It is indexed by ifIndex and
capwapDot11WlanId. The only visible object in this table except
RowStatus is capwapDot11WlanBssIfIndex which is read-only and the
description says that 'it is the same interface as identified by the
same value of ifIndex. But the manager cannot read its value until
the row exists. How does the manager know its value in order to
create the row in the table?
----------------------------------------------------------------
The old description would lead to misunderstanding when it says "The
interface identified by a particular value of this index is the same
interface as identified by the same value of ifIndex". In fact, the
ifIndex here is not a ifIndex in the INDEX { ifIndex (it is a
"Wireless virtual radio interface), capwapDot11WlanId }, while it is
a "WLAN "WLAN BSS Interface".
To clarify it, the following text is added to the description of
capwapDot11WlanBindBssIfIndex:
The ifIndex here is for an interface of 'WLAN BSS Interface'. For a
WLAN configuration on a radio, an interface of 'WLAN BSS Interface'
will correspond to it. The creation operation of a row object on the
capwapDot11WlanBindTable would trigger AC system to automatically
create a 'WLAN BSS Interface' and it is identified by ifIndex. It
does not require operator to manually create a 'WLAN BSS Interface'.
For the table of capwapDot11WlanBindTable, the description is updated
with the following text:
A table of objects that configure which WLAN (identified by
capwapDot11WlanId) will be provided on which 'WTP Virtual Radio
Interface' (identified by ifIndex) Also, display and control the
mapping relationship between interface of 'WTP Virtual Radio
Interface' interface and interface of 'WLAN BSS Interface'. The PHY
address for interface of 'WTP Virtual Radio Interface' ifType will be
base BSSID address for PHY radio.
Values of all bjects in this table are persistent at restart/reboot.
For the table of capwapDot11WlanBindEntry, the description is updated
with the following text:
A set of objects that display the mapping relationship between
interface of 'WTP Virtual Radio Interface' and interface of 'WLAN BSS
Interface'. The Index object ifIndex is a ifIndex of a 'WTP Virtual
Radio Interface'.
T13. Is the capwapDot11WlanBindTable persistent at agent reboot?
-----------------------------------------------------------------
Yes, The whole table is persistent at restart/reboot.
E1. Not all acronyms are expanded at first occurrence - e.g. WTP
-----------------------------------------------------------------
The Terminology section is updated with more Terminology such as
CAPWAP,WTP,AC, Wireless Binding,Split and Local MAC and so on.
E2. Please avoid using the construct 'the MIBs' (e.g. in Section 5).
s/the MIBs/the MIB modules/
-----------------------------------------------------------------
use either "MIB module" or "MIB modules" in the document
E3. There is no need to include sections 6.1 and 6.2, they provide
no new or specific information for this MIB module.
----------------------------------------------------------------
Yes, they were removed
E4. I suggest for this document to be verified by a native English
speaker for English spelling and grammar.
E5. ifIndex, ifDescr, ifName, ifAlias in the WLAN Service Interface 1) To close the issue 67 "Dot11 MIB should add a new Terminology WLAN
and WLAN BSS Interface table contain no specific information, I Profile"
suggest to just mention that they are used as per RFC 2863
-------------------------------------------------------------- --------------------------------------------------------------
The section for interpration of specific MIB objects in the iftable Add a new section 5.1. WLAN Profile, update the section 8, update
was removed in the new version. Reader could refer to RFC2863 the related MIB objects, replace the "WLAN Service Interface" with
"WLAN Profile Interface".
Other changes made by authors:
1) reorganized the section of overview, and divided it into the
following sub sections:
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5
5.2. Mechanism of Reusing Wireless Binding MIB Module . . . . . 5
2) Update some words in the section of" Example of CAPWAP-DOT11-MIB
Module Usage, especially explain how interfaces of
"WLAN service Interface" and "WLAN BSS Interface" are created.
3) Modify the value scope of CapwapDot11WlanIdTC from (1, 16) to
(1, 512), and description of it.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
H3C Tech. Co., Ltd H3C Tech. Co., Ltd
Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District,
Beijing Beijing
China(100085) China(100085)
Phone: +86 010 82775276 Phone: +86 010 82775276
 End of changes. 134 change blocks. 
708 lines changed or deleted 434 lines changed or added

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