draft-ietf-capwap-802dot11-mib-05.txt   draft-ietf-capwap-802dot11-mib-06.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft Hangzhou H3C Tech. Co., Ltd. Internet-Draft Hangzhou H3C Tech. Co., Ltd.
Intended status: Standards Track D. Perkins, Ed. Intended status: Informational D. Perkins, Ed.
Expires: February 14, 2010 SNMPinfo Expires: July 6, 2010 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
August 13, 2009 January 2, 2010
CAPWAP Protocol Binding MIB for IEEE 802.11 CAPWAP Protocol Binding MIB for IEEE 802.11
draft-ietf-capwap-802dot11-mib-05 draft-ietf-capwap-802dot11-mib-06
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it
describes managed objects for modeling the Control And Provisioning
of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless
binding.
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 45
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 February 14, 2010. This Internet-Draft will expire on July 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This memo defines a portion of the Management Information Base (MIB) described in the BSD License.
for use with network management protocols. In particular, it
describes managed objects for modeling the Control And Provisioning
of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless
binding.
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
skipping to change at page 2, line 38 skipping to change at page 2, line 41
7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 7 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 . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 22
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
14.1. Normative References . . . . . . . . . . . . . . . . . . . 22 14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
14.2. Informative References . . . . . . . . . . . . . . . . . . 23 14.2. Informative References . . . . . . . . . . . . . . . . . . 24
Appendix A. Appendix A. Changes between -05 and -04 . . . . . . . 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 the
use of various wireless technologies by the WTPs, with one specified use of various wireless technologies by the WTPs, with one specified
in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416]. 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 WLAN and a way to reuse the IEEE 802.11 covers both configuration for Wireless Local Area Network (WLAN) and
MIB module [IEEE.802-11.2007]. a way to reuse the IEEE 802.11 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).
skipping to change at page 3, line 44 skipping to change at page 3, line 44
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]. 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 physical layer (PHY) to transmit
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
skipping to change at page 4, line 33 skipping to change at page 4, line 33
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 [RFC5416]. binding for IEEE 802.11, provided in [RFC5416].
WLAN: A WLAN refers to a logical component instantiated on a WTP Wireless Local Area Network (WLAN): A WLAN refers to a logical
device. A single physical WTP MAY operate a number of WLANs. Each component instantiated on a WTP device. A single physical WTP MAY
Basic Service Set Identifier (BSSID) and its constituent wireless operate a number of WLANs. Each Basic Service Set Identifier (BSSID)
terminal radios are denoted as a distinct WLAN on a physical WTP. To and its constituent wireless terminal radios are denoted as a
support a physical WTP with multiple WLANs is an important feature distinct WLAN on a physical WTP. To support a physical WTP with
for CAPWAP protocol's 802.11 binding, and it is also for MIB module multiple WLANs is an important feature for CAPWAP protocol's 802.11
design. binding, and it is also for MIB module 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 IEEE 802.11 MIB module wireless technology, 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
skipping to change at page 5, line 46 skipping to change at page 5, line 46
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 and support to reuse such MIB objects in the IEEE 802.11 MIB module and support
functions such as MAC mode for WLAN in the [RFC5416] which are not in functions such as MAC mode for WLAN in the [RFC5416] which are not in
the scope of IEEE 802.11 standard. The CAPWAP-DOT11-MIB module MUST the 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 manage and configuration of WLAN profiles on the AC; - Centralized management and configuration of WLAN profiles on the
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
skipping to change at page 6, line 26 skipping to change at page 6, line 26
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 BSS parameters for the radio such as RTS Threshold. A WLAN Basic Service
Interface, created by binding WLAN to WTP Virtual Radio Interface, is Set (BSS) Interface, created by binding WLAN to WTP Virtual Radio
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 1) capwapDot11WlanTable
The table allows the operator to display and configure WLAN profiles, The table allows the operator to display and configure WLAN profiles,
such as specifying the MAC type and tunnel mode for a WLAN. Also, it such as specifying the MAC type and tunnel mode for a WLAN. Also, it
skipping to change at page 7, line 25 skipping to change at page 7, line 25
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, ifAlias are to be used as per [RFC2863].
The WLAN Profile Interface provides a way to configure IEEE 802.11 The WLAN Profile Interface provides a way to configure IEEE 802.11
parameters for a specific WLAN, and reuse the IEEE 802.11 MIB module. parameters for a specific WLAN, and reuse the IEEE 802.11 MIB module.
Also, the AC MUST have a mechanism that preserves the value of the
WLAN Profile Interfaces' ifIndexes in the ifTable at AC reboot.
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, ifAlias are to
be used as per [RFC2863]. The interface enables a single physical 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 the Also, the AC MUST have a mechanism that preserves the value of both
WLAN BSS Interfaces' ifIndexes in the ifTable at AC reboot. the WLAN Profile Interfaces' and the WLAN BSS Interfaces' ifIndexes
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.
skipping to change at page 8, line 36 skipping to change at page 8, line 35
In CapwapBaseWtpProfileTable In CapwapBaseWtpProfileTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 123456', capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00', capwapBaseWtpProfileWtpMacAddr = '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.168.0.100', capwapBaseWtpProfileWtpStaticIp = '192.0.2.10',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0', capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.168.0.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, capwapBaseWtpProfileWtpSilentInterval = 30,
capwapBaseWtpProfileWtpStatisticsTimer = 120, capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpWaitDTLSTimer = 60, capwapBaseWtpProfileWtpWaitDTLSTimer = 60,
capwapBaseWtpProfileWtpEcnSupport = limited(0) capwapBaseWtpProfileWtpEcnSupport = limited(0)
} }
skipping to change at page 14, line 29 skipping to change at page 14, line 22
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 "200908130000Z" -- August 13th, 2009 LAST-UPDATED "201001020000Z" -- Jan 2th, 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,
skipping to change at page 15, line 4 skipping to change at page 14, line 45
China(100085) China(100085)
Phone: +86 010 82775276 Phone: +86 010 82775276
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
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
Chris Elliott Chris Elliott
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709 Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
Email: chelliot@cisco.com Email: chelliot@cisco.com
Yong Zhang Yong Zhang
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) 2009 The Internet Society. This version of "Copyright (C) 2010 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 "200908130000Z" REVISION "201001020000Z"
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 the unique identifier of a WLAN." "Represents the unique identifier of a Wireless Local Area
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 18, line 4 skipping to change at page 17, line 45
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
of this object in the corresponding conceptual row is not
''active''. Thus to modify one or more of the objects in
this conceptual row,
a. change the row status to ''notInService'',
b. change the values of the row
c. change the row status to ''active''
The capwapDot11WlanRowStatus may be changed to ''active''
if all the managed objects in the conceptual row with
MAX-ACCESS read-create have been assigned valid values.
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 (identified by capwapDot11WlanProfileId) and WTP Virtual Radio
WTP Virtual Radio Interfaces. The WTP Virtual Radio Interfaces Interfaces. The WTP Virtual Radio Interfaces on the AC
on the AC correspond to PHY radios on the WTPs. It also stores correspond to physical layer (PHY) radios on the WTPs.
the mappings between WLAN IDs and WLAN BSS Interfaces. It also stores the mappings between WLAN IDs and WLAN
Basic Service Set (BSS) Interfaces.
Values of all objects in this table are persistent at 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
skipping to change at page 20, line 14 skipping to change at page 20, line 20
"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
of this object in the corresponding conceptual row is not
''active''. Thus to modify one or more of the objects in
this conceptual row,
a. change the row status to ''notInService'',
b. change the values of the row
c. change the row status to ''active''"
::= { capwapDot11WlanBindEntry 3 } ::= { 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 22, line 30 skipping to change at page 22, line 42
Require IANA to assign a ifType for the WLAN Profile Interface. Require IANA to assign a ifType for the WLAN Profile Interface.
Require IANA to assign a ifType for the WLAN BSS Interface. 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, Abhijit Choudhury, Fei Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury and
Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Yujin Zhao, Haitao Elwyn Davies for helpful comments on this document and guiding some
Zhang, Hao Wang. technique solution.
14. References The authors also thank their friends and coworkers Fei Fang, Xuebin
Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao
Zhang, Xiansen Cai and Xiaolan Wan.
14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs [RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels", BCP 14, to Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997. RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed.,
and J. Schoenwaelder, Ed., "Structure of and J. Schoenwaelder, Ed., "Structure of
Management Information Version 2 Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
skipping to change at page 23, line 20 skipping to change at page 23, line 35
Interfaces Group MIB", RFC 2863, Interfaces Group MIB", RFC 2863,
June 2000. June 2000.
[RFC3418] Presuhn, R., "Management Information Base [RFC3418] Presuhn, R., "Management Information Base
(MIB) for the Simple Network Management (MIB) for the Simple Network Management
Protocol (SNMP)", STD 62, RFC 3418, Protocol (SNMP)", STD 62, RFC 3418,
December 2002. December 2002.
[I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y. [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y.
Zhang, "CAPWAP Protocol Base MIB", Zhang, "CAPWAP Protocol Base MIB",
draft-ietf-capwap-base-mib-05 (work in draft-ietf-capwap-base-mib-07 (work in
progress), May 2009. progress), Jan 2010.
[RFC5415] Calhoun, P., Montemurro, M., and D. [RFC5415] Calhoun, P., Montemurro, M., and D.
Stanley, "Control And Provisioning of Stanley, "Control And Provisioning of
Wireless Access Points (CAPWAP) Protocol Wireless Access Points (CAPWAP) Protocol
Specification", RFC 5415, March 2009. Specification", RFC 5415, March 2009.
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, "Control and Provisioning of Stanley, "Control and Provisioning of
Wireless Access Points (CAPWAP) Protocol Wireless Access Points (CAPWAP) Protocol
Binding for IEEE 802.11", RFC 5416, Binding for IEEE 802.11", RFC 5416,
skipping to change at page 24, line 9 skipping to change at page 24, line 24
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Statements for Internet-Standard
Management Framework", RFC 3410, Management Framework", RFC 3410,
December 2002. December 2002.
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram [RFC4347] Rescorla, E. and N. Modadugu, "Datagram
Transport Layer Security", RFC 4347, Transport Layer Security", RFC 4347,
April 2006. April 2006.
Appendix A. Appendix A. Changes between -05 and -04 RFC Editor - please remove the appendix before publication of the RFC
All the issues are tracked by
http://www.capwap.org/cgi-bin/roundup.cgi/MIB/
1)Issue 71: For Dot11 MIB, some bugs detected post-WGLC but pre-IESG Appendix A. Appendix A. Changes between -06 and -05
The editor's address is updated. Also, update the WTP id in the 1) Close IESG review issues raised by Elwyn Davies
section 8.
2)Issue 73: For the example section in the Base and Dot11 MIB, the --------------------------------------------------------------
Dot11OperationTable is incorrect
In the draft version 04, the Dot11OperationTable follows the IEEE Close some editorial problems such as giving an expansion to the
802.11-1999 instead of IEEE 802.11-2007. It is incorrect. The draft keywords WLAN, PHY and BSS.
version 05 is updated according to IEEE 802.11-2007.
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
China(100085) China(100085)
skipping to change at page 24, line 37 skipping to change at page 25, line 4
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
China(100085) China(100085)
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com EMail: young@h3c.com
David Perkins (editor) David Perkins (editor)
SNMPinfo SNMPinfo
288 Quailbrook Ct San Carlos, 288 Quailbrook Ct San Carlos,
CA 94070 CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
EMail: dperkins@snmpinfo.com EMail: dperkins@snmpinfo.com
Chris Elliott (editor) Chris Elliott (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park
27709 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
EMail: chelliot@cisco.com EMail: chelliot@gmail.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. 38 change blocks. 
75 lines changed or deleted 94 lines changed or added

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