Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins, Ed.
Expires: April 14, 2009 SNMPinfo
C. Elliott, Ed.
Cisco Systems, Inc.
Y. Zhang, Ed.
Fortinet, Inc.
October 11, 2008
CAPWAP Protocol Binding MIB for IEEE 802.11
draft-ietf-capwap-802dot11-mib-01
Status of This Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 14, 2009.
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.
Shi, et al. Expires April 14, 2009 [Page 1]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6.1. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5
6.2. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5
6.3. Brief Description of MIB Objects . . . . . . . . . . . . . 5
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 5
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6
7.3. Relationship to CAPWAP-BASE-MIB . . . . . . . . . . . . . 8
7.4. Relationship to the MIBs defined in IEEE 802.11
standard and its amendments . . . . . . . . . . . . . . . 8
7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Usage . . . . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 19
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 20
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 20
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
14.1. Normative References . . . . . . . . . . . . . . . . . . . 20
14.2. Informative References . . . . . . . . . . . . . . . . . . 22
Shi, et al. Expires April 14, 2009 [Page 2]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
1. Introduction
The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines
a standard, interoperable protocol, which enables an Access
Controller (AC) to manage a collection of Wireless Termination
Points(WTPs). CAPWAP supports the use of various wireless
technologies by the WTPs, with one being specified in the 802.11
binding document [I-D.ietf-capwap-protocol-binding-ieee80211].
This document defines a MIB module that can be used to manage CAPWAP
implementations for IEEE 802.11 wireless binding. This MIB module
covers both configuration for WLAN and a way to reuse the MIBs
defined in IEEE 802.11 standard and its amendments.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Terminology
This document uses terminology from the document describing the
CAPWAP Protocol specification for 802.11 binding
[I-D.ietf-capwap-protocol-binding-ieee80211]. Besides terminology
defined in the IEEE 802.11 standard and CAPWAP specification, an
important conception is WLAN service. In the document, WLAN service
refers to a logical component instantiated on a WTP device. A single
physical WTP may operate a number of WLAN services, and the way is
called as virtual AP. Each Basic Service Set Identifier (BSSID) and
its constituent wireless terminal radios are denoted as a distinct
WLAN on a physical WTP. To support physical WTP with multiple WLANs
is an important feature for CAPWAP protocol's 802.11 binding, and it
is also for MIB design.
4. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Shi, et al. Expires April 14, 2009 [Page 3]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
document are to be interpreted as described in RFC 2119 [RFC2119].
5. Overview
The [I-D.ietf-capwap-base-mib] provides a way to configure and manage
WTP and radio objects through SNMP. It's a basis for manage and
control a IEEE 802.11 binding.
The CAPWAP Protocol's IEEE 802.11 binding MIB module (CAPWAP-DOT11-
MIB) provides a way to configure WLAN service, and it also allows to
easily reuse current and future MIBs defined in IEEE 802.11 standard
and its amendments.
It is designed to satisfy the following requirements and constraints:
- The MIB module could easily reuse current and future MIBs defined
in IEEE 802.11 standard and its amendments, and not require to
redefine them.
- From AC to centrally manage and configure WLAN service;
- Operators could configure MAC type and tunnel mode for a specific
WLAN service by SNMP;
- The MIB module supports virtual AP;
Before coming to details of CAPWAP-DOT11-MIB module, it will
introduce how it is able to reuse IEEE MIB standard. According to
[I-D.ietf-capwap-protocol-binding-ieee80211], each WLAN service is
identified by WLAN Id. In the MIBs defined in IEEE 802.11 standard
and its amendments, the MIB tables such as
Dot11AuthenticationAlgorithmsTable 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 service, and consider that the operator has to prepare
configurations for each WLAN service on the AC before WTPs connect to
AC, a wireless service could be abstracted as a 'WLAN Service
Interface' on the AC, and which could be identified by ifIndex. On
the AC, the MIB table CapwapDot11WlanConfigTable 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 MIBs defined in IEEE 802.11 standard and its
amendments.
6. Structure of the MIB Module
Shi, et al. Expires April 14, 2009 [Page 4]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
6.1. The capwapDot11Objects Subtree
The subtree provides information for configuration parameters of WLAN
service and binding WLAN service to a specific radio.
6.2. The capwapDot11Conformance Subtree
The subtree provides conformance information of MIB objects.
6.3. Brief Description of MIB Objects
The MIB objects were derived from the CAPWAP protocol binding for
802.11 document [I-D.ietf-capwap-protocol-binding-ieee80211].
1) capwapDot11WlanConfigTable
The table is used for providing configuration such as MAC type and so
on for WLANs. For a specific WLAN service which is identified by
capwapDot11WlanId, an interface of 'WLAN Service Interface' ifType
will be created. By the ifIndex of interface, it provides a way to
reuse the MIBs defined in IEEE 802.11 standard and its amendments.
For example, according to
[I-D.ietf-capwap-protocol-binding-ieee80211], Auth Type needs to be
configured for a WLAN. In IEEE 802.11 MIB, the MIB object
dot11AuthenticationAlgorithm in the
dot11AuthenticationAlgorithmsTable is corresponding to Auth Type.
Considering both capwapDot11WlanConfigTable and
dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP-
DOT11-MIB are able to easily reuse dot11AuthenticationAlgorithm
object in IEEE 802.11 MIB. It is same for other objects in the MIBs
defined in IEEE 802.11 standard and its amendments.
2) capwapDot11WlanBindTable
The table provides a way to bind WLAN service to a radio, then
supports virtual AP. The binding operation will dynamically create
'WLAN BSS Interface', and this logical interface is used for data
forwarding function.
7. Relationship to Other MIB Modules
7.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The CAPWAP-DOT11-MIB does
not duplicate those objects.
Shi, et al. Expires April 14, 2009 [Page 5]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
7.2. Relationship to the IF-MIB
The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing WLAN service that are
modeled as interfaces.
For each WLAN, it will have a logical interface of 'WLAN Service
Interface' responding to it on the AC. The interface SHOULD be
modeled as an ifEntry and provide appropriate interface information.
'WLAN Service Interface' provides a way to configure IEEE 802.11
parameters for a specific WLAN service, and reuse the MIBs defined in
IEEE 802.11 standard and its amendments.
To provide data forwarding service, system will dynamically create
logical interface of 'WLAN BSS Interface'. The interface SHOULD be
modeled as an ifEntry and provide appropriate interface information.
The interface enables the virtual AP function.
Some specific interpretations of ifTable for CAPWAP-DOT11-MIB are as
follow.
1) WLAN Service Interface
Object Use for the CAPWAP-DOT11-MIB
ifIndex Each interface of 'WLAN Service Interface' type
maybe be represented by an ifEntry.
ifDescr Description of the interface of 'WLAN Service
Interface' type.
ifType IANAifType of 'WLAN Service Interface'.
ifName Textual name (unique on this system) of the interface
or an octet string of zero length.
ifAlias The nonvolatile 'alias' name for the interface, as
specified by a network manager.
ifPhysAddress Unused.
ifAdminStatus This variable indicates the administrator's intent as
to whether PHY should be enabled, disabled. Could be
always enabled.
ifOperStatus This value reflects the actual or operational status
of interface. Could be always enabled.
Shi, et al. Expires April 14, 2009 [Page 6]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
Also see [RFC2863].
ifLastChange The value of sysUpTime at the time the interface
entered its current operational state.
Also see [RFC2863].
The other objects such as ifInOctets, ifOutOctets, ifInErrors,
ifOutErrors are unused.
2) WLAN BSS Interface
Object Use for the CAPWAP-DOT11-MIB
ifIndex Each interface of 'WLAN BSS Interface' type maybe
be represented by an ifEntry.
ifDescr Description of the interface of 'WLAN BSS Interface'
type.
ifType IANAifType of 'WLAN BSS Interface'.
ifName Textual name (unique on this system) of the interface
or an octet string of zero length.
ifAlias The nonvolatile 'alias' name for the interface, as
specified by a network manager.
ifPhysAddress The physical address of interface, i.e. WTP assigned
BSSID.
ifAdminStatus This variable indicates the administrator's intent as
to whether PHY should be enabled, disabled, or
running in some diagnostic testing mode on this
interface.
Also see [RFC2863].
ifOperStatus This value reflects the actual or operational status
of interface.
Also see [RFC2863].
ifLastChange The value of sysUpTime at the time the interface
entered its current operational state.
Also see [RFC2863].
ifInOctets The number of octets received as IEEE 802.11 frames.
ifOutOctets The number of octets transmitted as IEEE 802.11
frames.
Shi, et al. Expires April 14, 2009 [Page 7]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
ifInErrors The number of inbound IEEE 802.11 frames dropped due
to uncorrectable errors.
ifInUnknownProtos
The number of received IEEE 802.11 frame discarded
during frame header validation, including frames with
unrecognized label values.
ifOutErrors The number of outbound IEEE 802.11 frames dropped due
to uncorrectable errors.
7.3. Relationship to CAPWAP-BASE-MIB
The CAPWAP-BASE-MIB provides a way to manage and control WTP and
radio objects. Especially, CAPWAP-BASE-MIB has a mechanism of 'WTP
Virtual Radio Interface' which enable system to reuse the MIBs
defined in IEEE 802.11 standard and its amendments. With it,
administrator could configure an IEEE 802.11 AP radio's parameter and
query radio's traffic statistics. Based on CAPWAP-BASE-MIB, CAPWAP-
DOT11-MIB provides more information from WLAN service perspective.
7.4. Relationship to the MIBs defined in IEEE 802.11 standard and its
amendments
Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface'
ifType, the MIB module is able to reuse MIB objects in the MIBs
defined in IEEE 802.11 standard and its amendments.
In the 802.11 binding document [I-D.ietf-capwap-protocol-binding-
ieee80211], it involves a part of MIB objects defined by IEEE 802.11
standard and its amendments. Although CAPWAP-DOT11-MIB uses the
802.11 binding document as a reference, it could reuse all the MIB
objects defined by IEEE 802.11 standard and its amendments , and not
limited by the scope of the 802.11 binding document.
7.5. MIB modules required for IMPORTS
The following MIB modules are required for IMPORTS: SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
[RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib].
8. Example of CAPWAP-DOT11-MIB Usage
In the CAPWAP-BASE-MIB, each PHY radio is identified by WTP Id and
radio ID, and which has a corresponding 'WTP Virtual Radio Interface'
on the AC. The IEEE 802.11 MIB associated with this interface
can be used to configure IEEE 802.11 wireless binding parameters for
radio such as RTS Threshold.
Shi, et al. Expires April 14, 2009 [Page 8]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
In the CAPWAP 802.11 Binding MIB, each WLAN service is identified
by WLAN Id, and which has a corresponding 'WLAN Service Interface'
on the AC. The MIBs defined in IEEE 802.11 standard and its
amendments associated with this interface can be used to configure
WLAN parameters for a WLAN service, such as Authentication Algorithm.
The 'WLAN BSS Interface', created by binding 'WTP Virtual Radio
Interface' and 'WLAN Service Interface', is used for data forwarding.
Combining the example provided in the [I-D.ietf-capwap-base-mib],
the following is a whole example for configuration and management of
WTP, radio and WLAN service for IEEE 802.11 binding.
1) Identify each PHY radio by 'WTP Virtual Radio Interface'
According to [I-D.ietf-capwap-protocol-specification], each radio on
a WTP will be identified by a radio Id. Each WTP could be identified
by its serial number.
When configuration for a WTP is prepared before a WTP connects to AC,
the following information is available in the
CapwapBaseRadioBindTable.
In CapwapBaseRadioBindTable
{
capwapBaseWTPId = 12345678,
capwapBaseRadioId = 1,
capwapBaseWtpVirtualRadioifIndex = 10,
capwapBaseWirelessBinding = dot11(2)
}
Suppose WTP's serial number is 12345678, and first PHY radio's id
is 1. On the AC, the ifIndex of 'WTP Virtual Radio Interface' is
10 which represents the PHY radio 1.
By the mechanism of 'WTP Virtual Radio Interface', it seemed that WTP
PHY radios are located on the AC.
The interface of 'WTP Virtual Radio Interface' is modeled by ifTable.
In ifTable
{
ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface',
ifType = IANAifType of 'WTP Virtual Radio
Interface',
ifMtu = 0,
ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0,
ifAdminStatus = true,
ifOperStatus = false,
ifLastChange = 0,
ifInOctets = 0,
Shi, et al. Expires April 14, 2009 [Page 9]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
2) Configure IEEE 802.11 wireless binding parameters for 'WTP Virtual
Radio Interface'
It will be done on the AC through the MIBs defined in IEEE 802.11
standard and its amendments.
For example, to configure parameter for 'WTP Virtual Radio Interface'
by IEEE 802.11 Dot11OperationTable.
In Dot11OperationTable
{
ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0,
dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = 'capwap',
dot11ProductID = 'capwap'
}
In the example, it supposes ifIndex of a 'WTP Virtual Radio
Interface' is 10.
3) Configure WLAN service
WLAN service configuration will be done through CAPWAP-DOT11-MIB,
and the MIBs defined in IEEE 802.11 standard and its amendments.
First step is to create a 'WLAN Service Interface' through
CAPWAP-DOT11-MIB on the AC.
In CapwapDot11WlanConfigTable
{
capwapDot11WlanId = 1,
capwapDot11WlanServiceIfIndex = 20,
capwapDot11WlanMacType = splitMAC(2),
capwapDot11WlanTunnelMode = dot3Tunnel(2),
Shi, et al. Expires April 14, 2009 [Page 10]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
capwapDot11WlanConfigRowStatus = create
}
Here supposes to configure a WLAN service which is identified by
capwapDot11WlanId 1. A 'WLAN Service Interface' is created
for it and identified by ifIndex 20.
Corresponding to 'WLAN Service Interface', it SHOULD be modeled as an
ifEntry on the AC and provide appropriate interface information.
In ifTable
{
ifIndex = 20,
ifDescr = 'WLAN Service Interface',
ifType = IANAifType of 'WLAN Service Interface',
ifMtu = 0,
ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0,
ifAdminStatus = true,
ifOperStatus = true,
ifLastChange = 0,
ifInOctets = 0,
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
Second step is to configure WLAN parameters of 'WLAN Service
Interface' through the MIBs defined in IEEE 802.11 standard and
its amendments on the AC.
In Dot11AuthenticationAlgorithmsTable
{
ifIndex = 20,
dot11AuthenticationAlgorithmsIndex = 1,
dot11AuthenticationAlgorithm = Shared Key,
dot11AuthenticationAlgorithmsEnable = true
}
Here ifIndex 20 is for interface of 'WLAN Service Interface'
ifType. Suppose the index of authentication algorithm is 1.
4) Bind WLAN service to WTP radio
Shi, et al. Expires April 14, 2009 [Page 11]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
On the AC, through CapwapDot11WlanBindTable, it configures which
WLAN service (identified by capwapDot11WlanId) will be provided
on which radio (identified by ifIndex).
Suppose capwapDot11WlanMacType of WLAN service is splitMAC(2),
the interface of 'WLAN BSS Interface' will be created on the AC.
The AC will use it for split data forwarding. Here supposes ifIndex
of interface in 'WLAN BSS Interface' ifType is 30.
In CapwapDot11WlanBindTable
{
ifIndex = 10,
capwapDot11WlanId = 1,
capwapDot11WlanBssIfIndex = 30,
capwapDot11WlanBssRowStatus = create
}
5) WTP reports its current configuration status
After join phase and before WTP get configuration from AC, it will
report its current configuration status to AC through configuration
status request message. The MIB data will be updated on the AC.
As an example, for ifIndex 10 (which identifies an interface of 'WLAN
Virtual Radio Interface' ifType), its ifOperStatus in ifTable will
be updated with current radio operational status.
6) Query WTP and radio statistics data
After WTPs come to run status, administrator could query WTP and
radio statistics data through CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB.
For example, through dot11CountersTable in the IEEE 802.11 MIB,
administrator could query counter data for radio which is identified
by ifIndex of a 'WLAN Virtual Radio Interface'.
7) Query other statistics data
For example, administrator could query the configuration of
WLAN service through Dot11AuthenticationAlgorithmsTable and statistic
data of 'WLAN BSS Interface' through ifTable;
9. Definitions
CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN
IMPORTS
RowStatus, TEXTUAL-CONVENTION
FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32
Shi, et al. Expires April 14, 2009 [Page 12]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
FROM SNMPv2-SMI
ifIndex, InterfaceIndex
FROM IF-MIB
CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC
FROM CAPWAP-BASE-MIB;
capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "200810110000Z" -- Oct 11th, 2008
ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO
"General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China(100085)
Email: young@h3c.com
David T. Perkins
228 Bayview Dr
San Carlos, CA 94070
USA
Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com
Chris Elliott
Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709
USA
Phone: +1 919-392-2146
Email: chelliot@cisco.com
Yong Zhang
Fortinet, Inc.
1090 Kifer Road
Sunnyvale, CA 94086
USA
Email: yzhang@fortinet.com"
DESCRIPTION
"Copyright (C) 2008 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself
for full legal notices.
This MIB module contains managed object definitions for
Shi, et al. Expires April 14, 2009 [Page 13]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
the IEEE 802.11 bindings for the CAPWAP Protocol."
REVISION "200810110000Z"
DESCRIPTION
"Initial version, published as RFC xxx"
::= { mib-2 xxx }
-- Textual conventions
CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents an unique identifier of a WLAN."
SYNTAX Unsigned32 (1..16)
-- Top level components of this MIB
-- Tables, Scalars
capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 }
-- Conformance
capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 }
-- capwapDot11WlanConfigTable Table
capwapDot11WlanConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WlanConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the WLAN
service.
Values of all read-create objects in this
table are persistent at restart/reboot."
::= { capwapDot11Objects 1 }
capwapDot11WlanConfigEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display and control the WLAN
service."
INDEX { capwapDot11WlanId }
::= { capwapDot11WlanConfigTable 1 }
Shi, et al. Expires April 14, 2009 [Page 14]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
CapwapDot11WlanConfigEntry ::=
SEQUENCE {
capwapDot11WlanId CapwapDot11WlanIdTC,
capwapDot11WlanServiceIfIndex InterfaceIndex,
capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WlanConfigRowStatus RowStatus
}
capwapDot11WlanId OBJECT-TYPE
SYNTAX CapwapDot11WlanIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the WLAN Id for a WLAN which has a
capwapDot11WlanServiceIfIndex interface corresponding to it."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WlanConfigEntry 1 }
capwapDot11WlanServiceIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the index value that uniquely identifies a
'WLAN Service Interface'. The interface identified by a
particular value of this index is the same interface as
identified by the same value of ifIndex.
Before WTPs connect to AC and get configuration, administrator
will prepare configuration for them. For a specific WLAN
service, a logical interface of 'WLAN Service Interface'
ifType will be created, and administrator could configure WLAN
parameter through it. For example, according to IEEE 802.11
'6.1. IEEE 802.11 Add WLAN' in the
[I-D.ietf-capwap-protocol-binding-ieee80211], administrator
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 MIBs use ifIndex to
identify an interface for configuration and statistic data,
for example, dot11AuthenticationAlgorithmsTable in IEEE 802.11
MIB use ifIndex as index, and dot11AuthenticationAlgorithm
object is for Auth Type mentioned in the CAPWAP '6.1. IEEE
802.11 Add WLAN', With the way of 'WLAN Service Interface',
it will easily reuse MIB table like
dot11AuthenticationAlgorithmsTable, while only care for other
configurations like capwapDot11WlanTunnelMode."
Shi, et al. Expires April 14, 2009 [Page 15]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
::= { capwapDot11WlanConfigEntry 2 }
capwapDot11WlanMacType OBJECT-TYPE
SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether the WTP should support the WLAN in
Local or Split MAC modes."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WlanConfigEntry 3 }
capwapDot11WlanTunnelMode OBJECT-TYPE
SYNTAX CapwapBaseTunnelModeTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the frame tunneling type to be used for 802.11 data
frames from all stations associated with the WLAN.
Bits are exclusive with each other for a specific WLAN Id."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WlanConfigEntry 4 }
capwapDot11WlanConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row in
this table."
::= { capwapDot11WlanConfigEntry 5 }
-- End of capwapDot11WlanConfigTable Table
-- capwapDot11WlanBindTable Table
capwapDot11WlanBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the mapping
relationship between interface of 'WTP Virtual Radio Interface'
Shi, et al. Expires April 14, 2009 [Page 16]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
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."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11Objects 2 }
capwapDot11WlanBindEntry OBJECT-TYPE
SYNTAX CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the mapping relationship
between interface of 'WTP Virtual Radio Interface' and
interface of 'WLAN BSS Interface'."
INDEX { ifIndex, capwapDot11WlanId }
::= { capwapDot11WlanBindTable 1 }
CapwapDot11WlanBindEntry ::=
SEQUENCE {
capwapDot11WlanBssIfIndex InterfaceIndex,
capwapDot11WlanBssRowStatus RowStatus
}
capwapDot11WlanBssIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the index value that uniquely identifies a
'WLAN BSS Interface'. The interface identified by a
particular value of this index is the same interface as
identified by the same value of ifIndex.
Each capwapDot11WlanBssIfIndex will corresponding to a
WLAN service on the PHY radio which is identified by ifIndex.
The PHY address for capwapDot11WlanBssIfIndex 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.
When assigned as a block, implementations can still assign
any of the available BSSIDs to any WLAN. One possible method
is for the WTP to assign the address using the following
algorithm: base BSSID address + WLAN ID."
REFERENCE
"Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
Shi, et al. Expires April 14, 2009 [Page 17]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
::= { capwapDot11WlanBindEntry 1 }
capwapDot11WlanBssRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row
in this table."
::= { capwapDot11WlanBindEntry 2 }
-- Module compliance
capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 }
capwapDot11Compliances OBJECT IDENTIFIER
::= { capwapDot11Conformance 2 }
capwapDot11Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the
CAPWAP-DOT11-MIB."
MODULE -- this module
MANDATORY-GROUPS { capwapDot11WlanConfigGroup,
capwapDot11WlanBindGroup }
::= { capwapDot11Compliances 1 }
capwapDot11WlanConfigGroup OBJECT-GROUP
OBJECTS {
capwapDot11WlanServiceIfIndex,
capwapDot11WlanMacType,
capwapDot11WlanTunnelMode,
capwapDot11WlanConfigRowStatus
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure
property of WLAN."
::= { capwapDot11Groups 1 }
capwapDot11WlanBindGroup OBJECT-GROUP
OBJECTS {
capwapDot11WlanBssIfIndex,
capwapDot11WlanBssRowStatus
Shi, et al. Expires April 14, 2009 [Page 18]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure
WLAN BSS."
::= { capwapDot11Groups 2 }
END
10. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. The followings are the tables and objects and
their sensitivity/vulnerability:
o - Unauthorized changes to the capwapDot11WlanConfigTable and
capwapDot11WlanBindTable may disrupt allocation of resources in
the network, also change the behavior of WLAN system such as MAC
type.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations
Shi, et al. Expires April 14, 2009 [Page 19]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
11.1. IANA Considerations for CAPWAP-DOT11-MIB
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapDot11MIB { mib-2 XXX }
11.2. IANA Considerations for ifType
Require IANA to assign a ifType for 'WLAN Service Interface' type.
Require IANA to assign a ifType for 'WLAN BSS Interface' type.
12. Contributors
This MIB is based on contributions from Long Gao.
13. Acknowledgements
The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin
Dutta, Yujin Zhao, Haitao Zhang.
14. References
14.1. Normative References
[RFC2119] Bradner, S., "Key words
for use in RFCs to
Indicate Requirement
Levels", BCP 14,
RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed.,
Perkins, D., Ed., and
J. Schoenwaelder, Ed.,
"Structure of
Management Information
Version 2 (SMIv2)",
STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed.,
Perkins, D., Ed., and
J. Schoenwaelder, Ed.,
"Textual Conventions
Shi, et al. Expires April 14, 2009 [Page 20]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
for SMIv2", STD 58,
RFC 2579, April 1999.
[RFC2580] McCloghrie, K.,
Perkins, D., and J.
Schoenwaelder,
"Conformance Statements
for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F.
Kastenholz, "The
Interfaces Group MIB",
RFC 2863, June 2000.
[RFC3418] Presuhn, R.,
"Management Information
Base (MIB) for the
Simple Network
Management Protocol
(SNMP)", STD 62,
RFC 3418,
December 2002.
[I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D.,
Elliott, C., and P.
Agarwal, "CAPWAP
Protocol Base MIB", dra
ft-ietf-capwap-base-
mib-00 (work in
progress), May 2008.
[I-D.ietf-capwap-protocol-specification] Montemurro, M.,
Stanley, D., and P.
Calhoun, "CAPWAP
Protocol
Specification", draft-
ietf-capwap-protocol-
specification-13 (work
in progress),
September 2008.
[I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M.,
Stanley, D., and P.
Calhoun, "CAPWAP
Protocol Binding for
IEEE 802.11", draft-
ietf-capwap-protocol-
Shi, et al. Expires April 14, 2009 [Page 21]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
binding-ieee80211-10
(work in progress),
September 2008.
14.2. Informative References
[RFC3410] Case, J., Mundy, R.,
Partain, D., and B.
Stewart, "Introduction
and Applicability
Statements for
Internet-Standard
Management Framework",
RFC 3410,
December 2002.
Authors' Addresses
Yang Shi (editor)
H3C Tech. Co., Ltd
Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District,
Beijing
China(100085)
Phone: +86 010 82775276
EMail: young@h3c.com
David Perkins (editor)
SNMPinfo
288 Quailbrook Ct San Carlos,
CA 94070
USA
Phone: +1 408 394-8702
EMail: dperkins@snmpinfo.com
Chris Elliott (editor)
Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park
27709
USA
Phone: +1 919-392-2146
EMail: chelliot@cisco.com
Shi, et al. Expires April 14, 2009 [Page 22]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
Yong Zhang (editor)
Fortinet, Inc.
1090 Kifer Road
Sunnyvale, CA 94086
USA
EMail: yzhang@fortinet.com
Shi, et al. Expires April 14, 2009 [Page 23]
Internet-Draft CAPWAP Protocol Binding MIB October 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Shi, et al. Expires April 14, 2009 [Page 24]
