One document matched: draft-yangshi-capwap-802dot11-mib-01.txt
Differences from draft-yangshi-capwap-802dot11-mib-00.txt
Internet Engineering Task Force Yang Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd
Intended status: Standards Track Perkins, Ed.
Expires: June 9, 2008 SNMPinfo
Chris, Ed.
Cisco Systems, Inc.
December 7, 2007
CAPWAP Protocol Binding MIB for IEEE 802.11
draft-yangshi-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 June 9, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
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.
Yang Shi, et al. Expires June 9, 2008 [Page 1]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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. Textual Conventions . . . . . . . . . . . . . . . . . . . 4
6.2. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5
6.3. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5
6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 5
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 6
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6
7.3. Relationship to CAPWAP Base MIB . . . . . . . . . . . . . 8
7.4. Relationship to IEEE 802.11 MIB . . . . . . . . . . . . . 8
7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Usage . . . . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 18
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 19
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 19
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
14.1. Normative References . . . . . . . . . . . . . . . . . . . 19
14.2. Informative References . . . . . . . . . . . . . . . . . . 20
Yang Shi, et al. Expires June 9, 2008 [Page 2]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
1. Introduction
Current work is under way in the IETF to specify the CAPWAP Protocol
[I-D.ietf-capwap-protocol-specification], 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 IEEE 802.11 MIB
standard in series defined by IEEE 802.11 WG.
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 is 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
Yang Shi, et al. Expires June 9, 2008 [Page 3]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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, also could easily
reuse current and future IEEE 802.11 MIB standards.
It is designed to satisfy the following requirements and constraints:
- The MIB module could easily reuse current and future IEEE 802.11
MIB standard in series defined by IEEE 802.11 WG, 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-MIB-DOT11 module, it will
introduce how it is able to reuse IEEE MIB standard. As centralized
Wireless architecture, the operator has to prepare configurations for
each wireless at AC side before WTPs connect to AC. Under
centralized Wireless architectures, according to [I-D.ietf-capwap-
protocol-specification], each WLAN service is identifed by WLAN Id.
According to IEEE 802.11 MIB standards, the MIB tables such as
Dot11AuthenticationAlgorithmsTable are able to support wireless
configuration (such as authentication algorithm), and these tables
use ifIndex as index. A Wireless service could be abstracted as an
interface on the AC side, and which could be identified by ifIndex.
On the AC side, the MIB table CapwapDot11WirelessConfigTable 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 IEEE MIBs.
6. Structure of the MIB Module
6.1. Textual Conventions
The following textual conventions are defined:
Yang Shi, et al. Expires June 9, 2008 [Page 4]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
CapwapDot11WLANId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for WLAN Id."
SYNTAX Unsigned32
6.2. The capwapDot11Objects Subtree
The subtree provides information for configuration parameters of WLAN
service and binding WLAN service to a specific radio.
6.3. The capwapDot11Conformance Subtree
The subtree provides conformance information of MIB objects.
6.4. Brief Description of MIB Objects
The MIB objects were derived from the CAPWAP protocol 802.11 binding
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 IEEE 802.11 MIB. For example, according to
[I-D.ietf-capwap-protocol-binding-ieee80211], there is a TLV of
authentication Type for a WLAN. In IEEE 802.11 MIB, the MIB object
dot11AuthenticationAlgorithm in the
dot11AuthenticationAlgorithmsTable is corresponding to Auth Type TLV.
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 IEEE 802.11 MIBs'
reuse.
2) capwapDot11WLANBindTable
The table provides a way to bind WLAN service to a radio, then
support 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
Yang Shi, et al. Expires June 9, 2008 [Page 5]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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.
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 at AC side. The interface SHOULD be
modeled as an ifEntry and provide appropriate interface information.
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.
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
Yang Shi, et al. Expires June 9, 2008 [Page 6]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
always enabled.
ifOperStatus This value reflects the actual or operational status
of interface. Could be always enabled.
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.
One possible method is for the WTP to assign the
address for 'WLAN BSS Interface' using the following
algorithm: base BSSID address + WLAN ID.
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.
Yang Shi, et al. Expires June 9, 2008 [Page 7]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
Also see [RFC2863].
ifInOctets The number of octets received as 802.11 frames.
ifOutOctets The number of octets transmitted as 802.11
frames.
ifInErrors The number of 802.11 frames dropped due to
uncorrectable errors.
ifInUnknownProtos
The number of received 802.11 frame discarded during
frame header validation, including frames with
unrecognized label values.
ifOutErrors See [RFC2863].
7.3. Relationship to CAPWAP Base MIB
The CAPWAP Base MIB provides a way to manage and control WTP and
radio objects. Based on it, CAPWAP-DOT11-MIB provides more
information from WLAN service perspective.
7.4. Relationship to IEEE 802.11 MIB
Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface'
ifType, the MIB module is able to reuse MIB objects in the IEEE
802.11 MIB.
7.5. MIB modules required for IMPORTS
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and
CAPWAP-MIB [I-D.ietf-capwap-base-mib].
8. Example of CAPWAP-DOT11-MIB Usage
Combining the example in the [I-D.ietf-capwap-base-mib], here give
a whole example for configuration and management of WTP, radio and
WLAN object.
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 CapwapRadioBindTable.
In CapwapRadioBindTable
Yang Shi, et al. Expires June 9, 2008 [Page 8]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
{
capwapWTPId = 12345678
capwapRadioId = 1
capwapWTPVirtualRadioifIndex = 10,
capwapWirelessBinding = dot11(2),
}
Suppse WTP's serial number is 12345678, and first PHY radio's id is 1.
At AC side, 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 at AC side.
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,
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 at the AC side through IEEE 802.11 MIB.
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,
Yang Shi, et al. Expires June 9, 2008 [Page 9]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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
IEEE 802.11 MIB.
First step is to create a "WLAN Service Interface" through
CAPWAP-DOT11-MIB at AC side.
In CapwapDot11WLANConfigTable
{
capwapDot11WLANId = 1,
capwapDot11WLANServiceIfIndex = 20,
capwapWTPMACType = splitMAC(2),
capwapWTPTunnelMode = dot3Tunnel,
capwapDot11WLANConfigRowStatus = create
}
Here supposes to configure a WLAN serivce 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 at AC side 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 IEEE 802.11 MIB at AC side.
Yang Shi, et al. Expires June 9, 2008 [Page 10]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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
At AC side, through CapwapDot11WLANBindTable, it configures which
WLAN service (identified by capwapDot11WLANId) will be provided on
which radio (identifed by ifIndex). Suppose capwapWTPMACType of WLAN
service is splitMAC(2), the interface of 'WLAN BSS Interface'
will be created at AC side.
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 message. The MIB data will be updated at AC side.
For example, for the 802.11 binding, WTP will update data in the
ifTable and IEEE 802.11 MIB so on according to message content.
As a example for ifIndex 10 (which identify an interface of
"WLAN Virtual Radio Interface" ifType), its ifOperStatus in ifTable
will be updated with current radio operational status in the message.
6) Query WTP and radio statistics data
After WTPs come to run status, administrator could query WTP and
radio statistics data through CAPWAP-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.
Query statistic data of 'WLAN BSS Interface' through ifTable;
Yang Shi, et al. Expires June 9, 2008 [Page 11]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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
FROM SNMPv2-SMI
ifIndex, InterfaceIndex
FROM IF-MIB
CapwapWTPMACType, CapwapWTPTunnelMode
FROM CAPWAP-MIB;
capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "200712070000Z" -- Dec 07, 2007
ORGANIZATION "IETF CAPWAP working Group"
CONTACT-INFO
"Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China
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"
DESCRIPTION
"Copyright (C) 2007 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
the IEEE 802.11 bindings for the CAPWAP Protocol."
REVISION "200712070000Z"
Yang Shi, et al. Expires June 9, 2008 [Page 12]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
DESCRIPTION
"Initial version, published as RFC xxx"
::= { mib-2 xxx }
-- Textual conventions
CapwapDot11WLANId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for WLAN Id."
SYNTAX Unsigned32
-- Top level components of this MIB
capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 }
capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 }
-- capwapDot11WLANConfigTable Table
capwapDot11WLANConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WLANConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of the configuration for WLAN."
::= { capwapDot11Objects 1 }
capwapDot11WLANConfigEntry OBJECT-TYPE
SYNTAX CapwapDot11WLANConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing the configuration parameters for a specific
WLAN."
INDEX { capwapDot11WLANId }
::= { capwapDot11WLANConfigTable 1 }
CapwapDot11WLANConfigEntry ::=
SEQUENCE {
capwapDot11WLANId CapwapDot11WLANId,
capwapDot11WLANServiceIfIndex InterfaceIndex,
capwapWTPMACType CapwapWTPMACType,
capwapWTPTunnelMode CapwapWTPTunnelMode,
capwapDot11WLANConfigRowStatus RowStatus
Yang Shi, et al. Expires June 9, 2008 [Page 13]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
}
capwapDot11WLANId OBJECT-TYPE
SYNTAX CapwapDot11WLANId
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 ifIndex for an interface of 'WLAN Service
Interface' ifType.
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 specify Auth Type for a WLAN. The 'WLAN Service
Interface' provides a way to uniquely identify each WLAN by
logical at AC side. As most MIBs use ifIndex to identify an
interface for configuration and statistic data, for example,
dot11AuthenticationAlgorithmsTable in 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 capwapWTPTunnelMode."
::= { capwapDot11WLANConfigEntry 2 }
capwapWTPMACType OBJECT-TYPE
SYNTAX CapwapWTPMACType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents specifies whether the WTP should run the WLAN in
Local or Split MAC modes."
REFERENCE
Yang Shi, et al. Expires June 9, 2008 [Page 14]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WLANConfigEntry 3 }
capwapWTPTunnelMode OBJECT-TYPE
SYNTAX CapwapWTPTunnelMode
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."
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 list of the mapping relationship between interface of
'WTP Virtual Radio Interface' and interface of
'WLAN BSS Interface'."
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
Yang Shi, et al. Expires June 9, 2008 [Page 15]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
"An entry containing information of each BSS under a specific
radio.
The PHY address for interface of 'WTP Virtual Radio Interface'
ifType will be base BSSID address for PHY radio."
INDEX { ifIndex, capwapDot11WLANId }
::= { capwapDot11WLANBindTable 1 }
CapwapDot11WLANBindEntry ::=
SEQUENCE {
capwapDot11WLANBSSIfIndex InterfaceIndex,
capwapDot11WLANBSSRowStatus RowStatus
}
capwapDot11WLANBSSIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents a ifIndex for an interface of
'WLAN BSS Interface' ifType. Each capwapDot11WLANBSSIfIndex will
corresponding to a WLAN service on the PHY radio which is
identified by ifIndex.
When CapwapWTPMACType is localMAC(1), the interface of
'WLAN BSS Interface' will be created at AP side.
The AP will use interface for local data forwarding.
When CapwapWTPMACType is splitMAC(2), the interface of
'WLAN BSS Interface' will be created at AC side.
The AC will use it for split data forwarding.
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."
::= { 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."
Yang Shi, et al. Expires June 9, 2008 [Page 16]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
::= { capwapDot11WLANBindEntry 2 }
-- Conformance statements
capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 }
capwapDot11Compliances OBJECT IDENTIFIER
::= { capwapDot11Conformance 2 }
-- Object groups
capwapDot11WLANConfigGroup OBJECT-GROUP
OBJECTS {
capwapDot11WLANId,
capwapDot11WLANServiceIfIndex,
capwapWTPMACType,
capwapWTPTunnelMode,
capwapDot11WLANConfigRowStatus
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure
property of WLAN."
::= { capwapDot11Groups 1 }
capwapDot11WLANBindGroup OBJECT-GROUP
OBJECTS {
capwapDot11WLANBSSIfIndex,
capwapDot11WLANBSSRowStatus
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure
WLAN BSS."
::= { capwapDot11Groups 2 }
-- Compliance statements
capwapDot11Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for ACs that support WTPs
supporting 802.11 bindings."
MODULE -- this module
Yang Shi, et al. Expires June 9, 2008 [Page 17]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
MANDATORY-GROUPS { capwapDot11WLANConfigGroup,
capwapDot11WLANBindGroup }
::= { capwapDot11Compliances 1 }
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. These 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
Yang Shi, et al. Expires June 9, 2008 [Page 18]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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, Zhifei Zhang, Xiansen Cai and Hao
Wao.
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.,
Yang Shi, et al. Expires June 9, 2008 [Page 19]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
"Textual Conventions
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-protocol-specification] Calhoun, P., "CAPWAP
Protocol
Specification", draft-
ietf-capwap-protocol-
specification-08 (work
in progress),
November 2007.
[I-D.ietf-capwap-protocol-binding-ieee80211] Calhoun, P., "CAPWAP
Protocol Binding for
IEEE 802.11", draft-
ietf-capwap-protocol-
binding-ieee80211-05
(work in progress),
November 2007.
14.2. Informative References
[RFC3410] Case, J., Mundy, R.,
Partain, D., and B.
Stewart, "Introduction
and Applicability
Statements for
Yang Shi, et al. Expires June 9, 2008 [Page 20]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
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
D. 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
Yang Shi, et al. Expires June 9, 2008 [Page 21]
Internet-Draft CAPWAP Protocol Binding MIB December 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
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.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Yang Shi, et al. Expires June 9, 2008 [Page 22]
| PAFTECH AB 2003-2026 | 2026-04-24 02:44:39 |