Internet Engineering Task Force                              Y. Shi, Ed.
Internet-Draft                               Hangzhou H3C Tech. Co., Ltd
Intended status: Standards Track                         D. Perkins, Ed.
Expires: September 1, November 30, 2009                                      SNMPinfo
                                                         C. Elliott, Ed.
                                                     Cisco Systems, Inc.
                                                           Y. Zhang, Ed.
                                                          Fortinet, Inc.
                                                       February 28,
                                                            May 29, 2009

                        CAPWAP Protocol Base MIB
                     draft-ietf-capwap-base-mib-04
                     draft-ietf-capwap-base-mib-05

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and 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 September 1, November 30, 2009.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols.  In particular, it
   describes the managed objects for modeling the Control And
   Provisioning of Wireless Access Points (CAPWAP) Protocol.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  The Internet-Standard Management Framework . . . . . . . . . .  3
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   5.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     5.1.  Requirements and Constraints . . . . . . . . . . . . . . .  5  4
     5.2.  Wireless Binding MIB Modules . . . . . . . . . . . . . . .  5
     5.3.  Design Objectives  . . . . . . . . . . . . . . . . . . . .  5
     5.4.  Design Idea  . . . . . . . . . . . . . . . . . . . . . . .  6
     5.5.  Mechanism of Reusing Wireless Binding MIB Modules  . . . .  6
     5.6.  CAPWAP Protocol Wireless Binding MIB Module  . . . . . . .  7
     5.7.  WTP Profile  . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Structure of the MIB Module  . . . . . . . . . . . . . . . . .  7
   7.  Relationship to Other MIB Modules  . . . . . . . . . . . . . .  8
     7.1.  Relationship to SNMPv2-MIB Module  . . . . . . . . . . . .  8  9
     7.2.  Relationship to IF-MIB Module  . . . . . . . . . . . . . .  8  9
     7.3.  Relationship to ENTITY-MIB Module  . . . . . . . . . . . .  9
     7.4.  Relationship to Wireless Binding MIB Modules . . . . . . .  9 10
     7.5.  MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10
   8.  Example of CAPWAP-BASE-MIB Module Usage  . . . . . . . . . . . 10
   9.  CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12 14
     9.1.  CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 13 14
     9.2.  CAPWAP Protocol Variables  . . . . . . . . . . . . . . . . 16 17
     9.3.  CAPWAP Messages for CAPWAP Control Message Extension . . . 16 17
       9.3.1.  Configuration Status Response Message  . . . . . . . . 16 17
       9.3.2.  Configuration Update Response Message  . . . . . . . . 17 18
   10. Definitions  . . . . . . . . . . . . . . . . . . . . . . . . . 17 18
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 65 70
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 67 71
     12.1. IANA Considerations for CAPWAP-BASE-MIB module Module . . . . . . 67 71
     12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 67 71
   13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 67 71
   14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67 71
   15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67 72
     15.1. Normative References . . . . . . . . . . . . . . . . . . . 67 72
     15.2. Informative References . . . . . . . . . . . . . . . . . . 69 73
   Appendix A.  Appendix A. Changes between -04 -05 and -03 -04 . . . . . . . 71 74

1.  Introduction

   The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] [RFC5415] defines a standard, interoperable
   protocol, which enables an Access Controller (AC) to manage a
   collection of Wireless Termination Points(WTPs).

   This document defines a MIB module that can be used to manage the
   CAPWAP implementations.  This MIB module covers both configuration
   and WTP status-monitoring aspects of CAPWAP, and provides a way to
   reuse MIB modules for any wireless technology.

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 CAPWAP Protocol specification
   [I-D.ietf-capwap-protocol-specification]
   [RFC5415] and the Architecture Taxonomy for CAPWAP [RFC4118].

   Access Controller (AC): The network entity that provides WTP access
   to the network infrastructure in the data plane, control plane,
   management plane, or a combination therein.

   Wireless Termination Point (WTP): The physical or network entity that
   contains an RF antenna and wireless PHY to transmit and receive
   station traffic for wireless access networks.

   Control And Provisioning of Wireless Access Points (CAPWAP): It is a
   generic protocol defining AC and WTP control and data plane
   communication via a CAPWAP protocol transport mechanism.  CAPWAP
   control messages, and optionally CAPWAP data messages, are secured
   using Datagram Transport Layer Security (DTLS) [RFC4347].

   CAPWAP Control Channel: A bi-directional flow defined by the AC IP
   Address, WTP IP Address, AC control port, WTP control port and the
   transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control
   packets are sent and received.

   CAPWAP Data Channel: A bi-directional flow defined by the AC IP
   Address, WTP IP Address, AC data port, WTP data port, and the
   transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data
   packets are sent and received.

   Station (STA): A device that contains an interface to a wireless
   medium (WM).

   Split and Local MAC: The CAPWAP protocol supports two modes of
   operation: Split and Local MAC.  In Split MAC mode all L2 wireless
   data and management frames are encapsulated via the CAPWAP protocol
   and exchanged between the AC and the WTPs.  The Local MAC mode of
   operation allows for
   the data frames to be either locally bridged, or tunneled as 802.3
   frames.

   Wireless Binding: The CAPWAP protocol is independent of a specific
   WTP radio technology, as well its associated wireless link layer
   protocol.  Elements of the CAPWAP protocol are designed to
   accommodate the specific needs of each wireless technology in a
   standard way.  Implementation of the CAPWAP protocol for a particular
   wireless technology MUST defining define a binding protocol for it, e.g., the
   binding for IEEE 802.11, provided in
   [I-D.ietf-capwap-protocol-binding-ieee80211]. [RFC5416].

   Autonomous WLAN Architecture: It is the traditional autonomous WLAN
   architecture, in which each WTP is a single physical device that
   implements all the wireless services.

   Centralized WLAN Architecture: It is an emerging hierarchical
   architecture utilizing one or more centralized controllers for
   managing a large number of WTP devices.  It can be said that the full
   wireless functions are implemented across multiple physical network
   devices, namely, the WTPs and ACs.

4.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

5.  Overview

5.1.  Requirements and Constraints

   The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to
   satisfy the following requirements to:

   - Support centralized management and constraints: monitoring of WTPs from the AC;
   - From AC Allow operators to centrally manage make configurations for WTPs before and monitor WTPs; after
   they connect to the AC;

   - Supports Support querying of CAPWAP protocol parameters queries; parameters;

   - Supports showing WTPs Support displaying of WTPs' current state; state and configuration;

   - Provides the Provide basic property information of about the AC, WTP, radio and
   station objects'
   basic property and their relationship;

   - Supports indicating the 'WTP Virtual Radio Interface' and PHY
   radio's mapping relationship; relationships;

   - Provides Provide counters for WTP, radio's events on WTPs and radios such as reboot event, hardware event
   failure and so on;
   hardware failure;

   - Provides the Provide various notifications like such as channel up, join failure up and so on. join failure.

5.2.  Wireless Binding MIB Modules

   Other Standards Developing Organizations (SDOs), such as IEEE, have
   already defined MIB modules for a specific wireless technology, e.g.,
   the MIB module in
   IEEE 802.11 standard MIB module [IEEE.802-11.2007].  Such MIB modules are
   called as wireless binding MIB module. modules.

5.3.  Design Objectives

   This document brings forward introduces a mechanism to avoid redefining MIB objects
   in the existing MIB modules for a specific wireless technology, in another
   other words, a mechanism to reuse wireless binding MIB modules
   defined by other SDOs.

   In summary, the CAPWAP-BASE-MIB module have has the following design
   objectives:

   - To implement an architecture that uses SNMP for the management and
   control of wireless networks, and answering the operators operator's
   requirements for centralized management, whatever the deployment or configuration
   of the network wireless
   devices are configured and deployed (centralized, distributed, autonomous, or some
   mix);

   - To be consistent with the CAPWAP protocol;

   - To be independent of any wireless technologies and have ability be able to reuse
   wireless binding MIB modules defined by other SDOs;

   - To enable interoperability between vendors;

   - To meet operator requirements for the centralized wireless
   architectures. WLAN architecture.

5.4.  Design Idea

   The basic design idea of the CAPWAP-BASE-MIB module is:

   - The CAPWAP-BASE-MIB module MUST be run on the AC devices and is NOT
   REQUIRED on the WTP devices.  It follows the same idea model as the CAPWAP
   protocol: Centralized Control;

   - It is designed to accommodate the specific needs of each wireless
   technology in a standard way.  It is independent of any wireless
   technologies;

   - The ifIndex [RFC2863] will be is used as a common handler for corresponding
   interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific
   wireless technologies
   MIB modules; technologies;

   - The operator could manage and control the centralized wireless WLAN
   architectures using multiple MIB modules defined by multiple SDOs,
   while keeping them loosely coupled.

5.5.  Mechanism of Reusing Wireless Binding MIB Modules

   Before coming to details of CAPWAP-BASE-MIB module, it will introduce
   how CAPWAP-BASE-MIB module is able to be independent of any wireless
   technologies and reuse wireless binding MIB modules defined by other
   SDOs.  As centralized Wireless architecture, the operator has to
   prepare configuration on the AC before WTPs connects to AC.

   For any wireless technology, the configuration and management of radio is
   radios are very important.  Under centralized WLAN architecture, according to
   [I-D.ietf-capwap-protocol-specification], a specific PHY radio could
   be identified by identifier of a WTP and radio (WTP id + radio id).  As usual, wireless binding MIB modules
   support radio management on
   its their own.  For example, the MIB tables
   such as the Dot11OperationTable [IEEE.802-11.2007] are able to
   support WTP radio configuration.  These tables use the ifIndex as the
   index, and work well under autonomous WLAN architecture.

   To reuse such wireless binding MIB modules is very important, important to
   centralized WLAN architectures.  According to [RFC5415], a specific
   PHY radio could be identified by the combination of the identifiers
   of the WTP and radio (WTP ID + radio ID), so the key point is to reuse make
   use of the ifIndex idea of ifIndex.  So it is required and find a way to maintain the mapping relationship mappings
   between 'WTP id ID + radio id' ID' and
   'ifIndex'. the ifIndex.  As a generic mechanism,
   an ifIndex can identify an interface in an abstract way, and it does
   NOT care for an the interface's PHY location (either on the WTP or AC).
   The AC can have interfaces of 'WTP WTP Virtual Radio Interface' ifType, which will Interfaces to logically represent
   PHY radios on the WTP.  It looks like that PHY radios are located on
   the AC, and PHY location of the WTP (radio) is hidden to the
   operator.  Operator  The operator can operate radios by through MIB tables with
   the ifIndex of 'WTP a WTP Virtual Radio
   Interface'. Interface.  As an a type of abstract
   interface, 'WTP the WTP Virtual Radio Interface' Interface could be used by any
   wireless technology such as IEEE 802.11 and 802.16.  The table of
   capwapBaseWirelessBindingTable in the CAPWAP-
   BASE-MIB CAPWAP-BASE-MIB module is used
   to indicate store the such mapping relationship mappings between the 'WTP id + ID+ Radio id' ID' and IfIndex. the ifIndex.

5.6.  CAPWAP Protocol Wireless Binding MIB Module

   According to the CAPWAP Protocol specification
   [I-D.ietf-capwap-protocol-specification], [RFC5415], when
   defining a binding for wireless technologies, the authors MUST
   include any necessary definitions for technology-specific messages
   and all technology-
   specific technology-specific message elements for those messages.  A
   CAPWAP binding protocol is required for a specific wireless binding
   technology, e.g., the protocol of [I-D.ietf-capwap-protocol-binding-ieee80211] [RFC5416] for IEEE 802.11 binding.

   Sometimes, not all the technology-specific message elements in a
   CAPWAP binding protocol have MIB objects defined by other SDOs.  For
   example, the protocol of [I-D.ietf-capwap-protocol-binding-ieee80211] [RFC5416] defines WLAN conception.  The WLAN
   refers to a logical component instantiated on a WTP device.  A single
   physical WTP may MAY operate a number of WLANs.  Also, Local or Split MAC
   modes could be specified for a WLAN.  The MAC mode for a WLAN is not
   in the scope of IEEE 802.11 [IEEE.802-11.2007].  In such cases, in
   addition to the existing wireless binding MIB modules defined by
   other SDOs, a CAPWAP protocol wireless binding MIB module is required
   to be defined for a wireless binding, e.g, the CAPWAP Protocol
   Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib].

5.7.  WTP Profile

   In a centralized WLAN architecture, a WTP profile is used to make
   configurations such as static IP address for a WTP before and after
   it connects to the AC.  It MUST contain the serial number [RFC5415]
   of the WTP because the CAPWAP message received from the WTP contains
   its serial number and the AC uses this serial number to find the
   corresponding WTP profile.

   Another important function of WTP profile is to trigger the creation
   of WTP Virtual Radio Interfaces on the AC.  To implement this
   function, a WTP profile MUST include the WTP's model number
   [RFC5415], which reflects the number of PHY radios on the WTP.  In
   this way, the creation of a WTP profile triggers the AC to
   automatically create the same number of WTP Virtual Radio Interfaces
   corresponding to the WTP's PHY radios without manual intervention.
   With the ifIndexes of WTP Virtual Radio Interfaces, the operator
   could configure and manage the WTP's PHY radios through the wireless
   binding MIB modules.

6.  Structure of the MIB Module

   The MIB objects were are derived from the CAPWAP protocol document
   [I-D.ietf-capwap-protocol-specification].
   [RFC5415].

   1) capwapBaseAcNameListTable
   The AC name list table is used to configure the AC name list.

   2) capwapBaseMacAclTable

   The ACL table is used to configure stations' Access Control
   List(ACL).

   3) capwapBaseWtpStateTable capwapBaseWtpProfileTable

   The WTPs status WTP profile table is used to indicate configure WTP profiles for WTPs to
   be managed before they connect to the AC.  An operator could change a
   WTP's current configuration by changing the values of parameters in
   the corresponding WTP profile.

   4) capwapBaseWtpStateTable

   The WTPs status table is used to indicate each WTP's CAPWAP FSM
   state.

   4)
   state, and helps operator to query WTPs' current configuration.

   5) capwapBaseWtpTable

   The WTPs table is used for providing property and configuration
   information in details for display properties of WTPs in running state.

   5)

   6) capwapBaseWirelessBindingTable

   The wireless binding table is used to indicate display the mapping
   relationship mappings between logical interface of 'WTP
   WTP Virtual Radio
   Interface' ifType Interfaces and PHY radios, and the wireless binding
   type for each PHY radio.

   6)

   7) capwapBaseStationTable

   The station table is used for providing stations' basic property
   information.

   7)

   8) capwapBaseWtpEventsStatsTable

   The WTP events statistic table is used for collecting WTP reboot
   count, link failure count, hardware failure count and so on.

   8)

   9) capwapBaseRadioEventsStatsTable

   The radio events statistic table is used for collecting radio reset
   count, channel change count, hardware failure count and so on.

7.  Relationship to Other MIB Modules

7.1.  Relationship to SNMPv2-MIB Module

   The CAPWAP-BASE-MIB module does not duplicate the objects of the
   'system' group in the SNMPv2-MIB [RFC3418] that is defined as being
   mandatory for all systems, and the objects apply to the entity as a
   whole.  The 'system' group provides identification of the management
   entity and certain other system-wide data.  The CAPWAP-BASE-MIB
   module does not duplicate those objects.

7.2.  Relationship to IF-MIB Module

   The Interfaces Group [RFC2863] defines generic managed objects for
   managing interfaces.  This memo contains the media-specific
   extensions to the Interfaces Group for managing WTP radio object PHY radios that
   are modeled as interfaces.

   The IF-MIB module is required to support be supported on the AC.  For each  Each PHY
   radio on the WTP, it will have WTP corresponds to a logical interface of 'WTP WTP Virtual Radio
   Interface' ifType Interface on the
   AC.  'WTP  The WTP Virtual Radio Interface' Interface provides a way to configure the
   radio's parameters and query radio's traffic statistics, and reuse
   wireless binding modules defined by other SDOs.  The interface MUST
   be modeled as an ifEntry ifEntry, and provide appropriate
   interface information. ifEntry objects such as ifIndex,
   ifDescr, ifName, ifAlias are to be used as per [RFC2863].

   Also, as an ifIndex [RFC2863] will be is used as a common handler for a
   corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless
   technologies MIB modules, the system (AC) AC MUST have a mechanism that preserves
   the values of ifIndex the ifIndexes in the ifTable at AC reboot.

7.3.  Relationship to ENTITY-MIB Module

   The ENTITY-MIB module [RFC4133] meets the need for a standardized way
   of representing a single agent, which supports multiple instances of
   one MIB.  It could express a certain relationship between multiple
   entities, and provide entity properties for each entity.

   Under the wireless

   In a centralized architectures, WLAN architecture, the SNMP agent will run runs on the AC,
   and is not required on the WTP.  By  With the ENTITY-MIB module on the
   AC, it could keep entity information such as firmware revision and
   software revision of the AC and WTPs.  From the ENTITY-MIB module module's
   perspective, the overall physical entity (AC) is a 'compound' of
   multiple physical entities (WTPs which connects (that is, the WTPs connected to AC), and
   all entities are each identified by a Physical index.  In the  The
   capwapBaseWtpTable of the CAPWAP-BASE-MIB module, it module uses the
   capwapBaseWtpPhyIndex object to keep store the mapping relationship mappings of WTP object
   between CAPWAP-BASE-MIB and ENTITY-MIB module. modules.

   By combining the MIB modules, operators could query AC and WTP's the status and properties.
   properties of the AC and WTPs.  For example, they could get a WTP's
   current status through the CAPWAP-BASE-MIB module, and a WTP's
   software revision information through the ENTITY-MIB module.  The
   CAPWAP-BASE-MIB module does not duplicate those objects defined in
   the ENTITY-MIB module.

7.4.  Relationship to Wireless Binding MIB Modules

   The wireless binding MIB module of a wireless technology (such as
   [IEEE.802-11.2007]) is required to support be supported on the AC.  The CAPWAP-
   BASE-MIB
   CAPWAP-BASE-MIB module is able to support any wireless binding.
   Through
   ifIndex the ifIndexes of 'WTP WTP Virtual Radio Interface' ifType, Interfaces, it provides a
   consistent and abstract way of reusing MIB objects in the wireless
   binding MIB modules.  The CAPWAP-BASE-MIB module does not duplicate
   those objects defined in the wireless binding MIB modules.

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], SNMP-
   FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB
   [RFC4133].

8.  Example of CAPWAP-BASE-MIB Module Usage

   With the idea of 'WTP Virtual Radio Interface' in the mind, the usage
   of the MIB modules will be easily understood.

   Here takes IEEE 802.11 binding as an example.

   1) Identify the PHY radio by 'WTP Virtual Radio Interface'

   According example to [I-D.ietf-capwap-protocol-specification], each radio on show how the MIB
   modules operate.

   1) Create a WTP will be identified by a radio Id.  Each WTP could be identified
   by its serial number. profile

   Suppose a the WTP's serial number identifier is '12345678'.  Create the WTP
   profile as follows:

     In CapwapBaseWtpProfileTable
     {
       capwapBaseWtpProfileId                  = 1,
       capwapBaseWtpProfileName                = 'WTP Profile 12345678',
       capwapBaseWtpProfileWTPSerialId         = '12345678',
       capwapBaseWtpProfileWTPModelNumber      = 'WTP123',
       capwapBaseWtpProfileWtpName             = 'WTP 12345678',
       capwapBaseWtpProfileWtpLocation                = 'office',
       capwapBaseWtpProfileWtpStaticIpEnable          = true(1),
       capwapBaseWtpProfileWtpStaticIpType            = ipv4(1),
       capwapBaseWtpProfileWtpStaticIp                = '192.168.0.100',
       capwapBaseWtpProfileWtpNetmask                 = '255.255.255.0',
       capwapBaseWtpProfileWtpGateway                 = '192.168.0.1',
       capwapBaseWtpProfileWtpFallbackEnable          = true(1),
       capwapBaseWtpProfileWtpEchoInterval            = 30,
       capwapBaseWtpProfileWtpIdleTimeout             = 300,
       capwapBaseWtpProfileWtpMaxDiscoveryInterval    = 20,
       capwapBaseWtpProfileWtpReportInterval          = 120,
       capwapBaseWtpProfileWtpSilentInterval          = 30,
       capwapBaseWtpProfileWtpStatisticsTimer         = 120,
       capwapBaseWtpProfileWtpWaitDTLSTimer           = 60,
       capwapBaseWtpProfileWtpEcnSupport              = limited(0)
     }

   Suppose the WTP with model number 'WTP123' has one PHY radio and first this
   PHY radio id is identified by ID 1.
   On  The creation of this WTP profile
   triggers the AC, AC to automatically create a WTP Virtual Radio Interface
   and add a new row object to the CapwapBaseWirelessBindingTable
   without manual intervention.  Suppose the ifIndex of interface in 'WTP the WTP Virtual
   Radio Interface'
   ifType Interface is 10 which represents the PHY radio 1. 10.  The following information is obtained stored in the
   CapwapBaseWirelessBindingTable.

      In CapwapBaseWirelessBindingTable
      {
        capwapBaseWtpStateWtpId
        capwapBaseWtpProfileId                          = '12345678', 1,
        capwapBaseWirelessBindingRadioId                = 1,
        capwapBaseWirelessBindingVirtualRadioIfIndex    = 10,
        capwapBaseWirelessBindingType                   = dot11(2)
      }

   By the mechanism of 'WTP

   The WTP Virtual Radio Interface', it seems WTP Interfaces on the AC correspond to the PHY
   radios are located on the AC. WTP.  The interface of 'WTP WTP Virtual Radio
   Interface' ifType Interface is modeled by
   ifTable [RFC2863].

      In ifTable
      {
        ifIndex              = 10,
        ifDescr              = 'WTP Virtual Radio Interface',
        ifType               = xxx,
   RFC Editor - please replace xxx with the value
   allocated by IANA for IANAifType of 'WTP WTP Virtual Radio Interface' Interface
        ifMtu                = 0,
        ifSpeed              = 0,
        ifPhysAddress        = '000000',
        ifAdminStatus        = true, true(1),
        ifOperStatus         = false, false(0),
        ifLastChange         = 0,
        ifInOctets           = 0,
        ifInUcastPkts        = 0,
        ifInDiscards         = 0,
        ifInErrors           = 0,
        ifInUnknownProtos    = 0,
        ifOutOctets          = 0,
        ifOutUcastPkts       = 0,
        ifOutDiscards        = 0,
        ifOutErrors          = 0
       }

   2) Configure specific wireless binding parameters for 'WTP Query the ifIndexes of WTP Virtual Radio Interface'

   It will be done on Interfaces

   Before configuring PHY radios, the AC through specific wireless binding MIB
   module such as IEEE 802.11 MIB module.

   For example, operator needs to configure parameter for 'WTP Virtual Radio Interface'
   by IEEE 802.11 Dot11OperationTable [IEEE.802-11.2007].

      In Dot11OperationTable
      {
        ifIndex                         = 10,
        dot11MACAddress                 = '000000',
        dot11RTSThreshold               = 2347,
        dot11ShortRetryLimit            = 7,
        dot11LongRetryLimit             = 4,
        dot11FragmentationThreshold     = 256,
        dot11MaxTransmitMSDULifetime    = 512,
        dot11MaxReceiveLifetime         = 512,
        dot11ManufacturerID             = 'capwap',
        dot11ProductID                  = 'capwap'
      }

   In get the example, it suppose ifIndex
   ifIndexes of an interface in 'WTP WTP Virtual Radio Interface' ifType is 10.

   3) WTP reports its current configuration status

   According Interfaces corresponding to [I-D.ietf-capwap-protocol-specification], after join
   phase the PHY
   radios.

   As CapwapBaseWirelessBindingTable already stores the mappings between
   PHY radios (Radio IDs) and before the ifIndexes of WTP Virtual Radio
   Interfaces, the operator can get configuration the ifIndex information by querying
   this table.  Such a query operation SHOULD run from radio ID 1 to
   radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex
   value (0) is returned.

   This example uses capwapBaseWtpProfileId = 1 and
   capwapBaseWirelessBindingRadioId = 1 as inputs to query the
   CapwapBaseWirelessBindingTable, and gets
   capwapBaseWirelessBindingVirtualRadioIfIndex = 10.  Then it uses
   capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2,
   and gets a invalid ifIndex value (0), so the the query operation
   ends.  This method gets not only the ifIndexes of WTP Virtual Radio
   Interfaces, but also the numbers of PHY radios.  Besides checking
   whether the ifIndex value is valid, the operator SHOULD check whether
   the capwapBaseWirelessBindingType is the desired binding type.

   3) Configure specific wireless binding parameters for a WTP Virtual
   Radio Interface

   This configuration is made on the AC through a specific wireless
   binding MIB module such as the IEEE 802.11 MIB module.

   The following shows an example of configuring parameters for a WTP
   Virtual Radio Interface with ifIndex 10 through the IEEE 802.11
   Dot11OperationTable [IEEE.802-11.2007].

      In Dot11OperationTable
      {
        ifIndex                         = 10,
        dot11MACAddress                 = '000000',
        dot11RTSThreshold               = 2347,
        dot11ShortRetryLimit            = 7,
        dot11LongRetryLimit             = 4,
        dot11FragmentationThreshold     = 256,
        dot11MaxTransmitMSDULifetime    = 512,
        dot11MaxReceiveLifetime         = 512,
        dot11ManufacturerID             = 'capwap',
        dot11ProductID                  = 'capwap'
      }

   4) Current configuration status report from the WTP to the AC

   According to [RFC5415], before a WTP that has joined the AC gets
   configuration from the AC, it will needs to report its current
   configuration status to AC through by sending a configuration status request message.  The data of
   message to the AC, which use the message to update MIB objects will be updated on the
   AC.  For example, for IEEE 802.11 binding, WTP will update the AC updates data in the
   ifTable [RFC2863] and IEEE 802.11 MIB module so on according to message
   content.  As an example for the
   message.  For ifIndex 10, its ifOperStatus in ifTable
   will be is updated
   according to the current radio operational status in the CAPWAP
   message.

   4)

   5) Query WTP and radio statistics data

   After WTPs come start to run status, run, the operator could query WTP and radio
   statistics data through CAPWAP-BASE-MIB and specific binding MIB
   module.
   module on the AC.  For example, through dot11CountersTable in the
   IEEE 802.11 MIB module, the operator could query the counter data for radio which is
   identified by ifIndex of
   a virtual radio interface.  With
   capwapBaseWtpTable table in using the ifIndex of the corresponding WTP Virtual Radio
   Interface.  With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB
   module, the operator could query configuration and the properties of WTPs which are in run
   status.

   5) running WTPs.

   6) MIB operations through a CAPWAP protocol wireless binding MIB
   module
   For example, for CAPWAP IEEE 802.11 binding protocol
   [I-D.ietf-capwap-protocol-binding-ieee80211], [RFC5416], Some
   MIB operations such as MAC mode configuration for a WLAN depend on
   the CAPWAP Protocol Binding MIB for IEEE 802.11
   [I-D.ietf-capwap-802dot11-mib].
   In the [I-D.ietf-capwap-802dot11-mib], it will give  For more explain.

   6) information, refer to
   [I-D.ietf-capwap-802dot11-mib].

   7) Query other properties of a WTP

   The Operator could query MIB objects in the ENTITY-MIB [RFC4133]
   module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable
   of CAPWAP-BASE-MIB module.  The properties of a WTP such as software
   version, hardware version and so on are available in the ENTITY-MIB module.

9.  CAPWAP Message Element Extension

   This section describes the CAPWAP control message extension for
   CAPWAP protocol to support CAPWAP-BASE-MIB module.

   To enable CAPWAP protocol timers and variables
   [I-D.ietf-capwap-protocol-specification] [RFC5415] manageable
   through CAPWAP protocol, the following capwap message element
   extensions are defined using Vendor Specific Payload message element
   in this section.  These message elements are used by WTP to report
   extra configuration information to the AC.

      CAPWAP Message Element          Vendor Identifier       Element ID

      CAPWAP Protocol Timers          Id assigned by IANA           1
      CAPWAP Protocol Variables       Id assigned by IANA           2

9.1.  CAPWAP Protocol Timers

         0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                       Vendor Identifier                       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |         Element ID             |     DataChannelKeepAlive     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    DataChannelDeadInterval     |     DiscoveryInterval        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |      DTLSSessionDelete         |         EchoInterval         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                            IdleTimeout                        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    ImageDataStartTimer         |     MaxDiscoveryInterval     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       ReportInterval           |      RetransmitInterval      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       SilentInterval           |        StatisticsTimer       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |           WaitDTLS             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
   Type:   37 for Vendor Specific Payload

   Length:   34

   Vendor Identifier:   A 32-bit value containing the IANA assigned "SMI
      Network Management Private Enterprise Codes".

   Element ID:   The Element ID field is set to 1 for CAPWAP Protocol
      Timers.

   DataChannelKeepAlive:  A 16-bit value representing the time,
      in seconds, that is used by the WTP to determine the next
      must transmit the Data Channel Keep Alive. (see section 4.7.2 of
      [I-D.ietf-capwap-protocol-specification]).
      [RFC5415]).

   DataChannelDeadInterval:  A 16-bit value representing the minimum
      time, in seconds, a WTP MUST wait without having received a Data
      Channel Alive packets may MAY be considered dead.  The value of this
      timer MUST be no less than 2*DataChannelKeepAlive seconds and
      no greater that 240 seconds (see section 4.7.3 of [I-D.ietf-
      capwap-protocol-specification]). [RFC5415]).

   DiscoveryInterval:  A 16-bit value representing the minimum time, in
      seconds, that a WTP MUST wait after receiving a Discovery Response
      message, before initiating a DTLS handshake (see section 4.7.5 of
      [I-D.ietf-capwap-protocol-specification]).
      [RFC5415]).

   DTLSSessionDelete:  A 16-bit value representing the minimum time, in
      seconds, a WTP MUST wait for DTLS session deletion (see section
      4.7.6 of [I-D.ietf-capwap-protocol-specification]). [RFC5415]).

   EchoInterval:  A 16-bit value representing the minimum time, in
      seconds, between sending Echo Request messages to the AC with
      which the WTP has joined (see section 4.7.7 of [I-D.ietf-capwap-
      protocol-specification]). [RFC5415]).

   IdleTimeout:  A 32-bit value representing the idle timeout value that
      the WTP SHOULD enforce for its active station. The default Idle
      Timeout is 300 seconds (see section 4.7.8 of [I-D.ietf-capwap-
      protocol-specification]). [RFC5415]).

   ImageDataStartTimer:  A 16-bit value representing the number of
      seconds the WTP will wait for its peer to transmit the Image
      Data Request (see section 4.7.9 of [I-D.ietf-capwap-protocol-
      specification]). [RFC5415]).

   MaxDiscoveryInterval:  A 16-bit value representing the maximum time
      allowed between sending Discovery Request messages, in seconds.

      This value MUST be no less than 2 seconds and no greater than 180
      seconds (see section 4.7.10 of [I-D.ietf-capwap-protocol-
      specification]). [RFC5415]).

   ReportInterval:  A 16-bit value representing the time, in seconds,
      that is used by the WTP to determine the interval the WTP uses
      between sending the Decryption Error message elements to inform
      the AC of decryption errors (see section 4.7.11 of [I-D.ietf-
      capwap-protocol-specification]). [RFC5415]).

   RetransmitInterval:  A 16-bit value representing the minimum time,
      in seconds, in which a non-acknowledged CAPWAP packet will be
      retransmitted (see section 4.7.12 of [I-D.ietf-capwap-protocol-
      specification]). [RFC5415]).

   SilentInterval:  The minimum time, in seconds, a WTP MUST wait before
      it MAY again send Discovery Request messages or attempt to
      establish DTLS session (see section 4.7.13 of [I-D.ietf-capwap-
      protocol-specification]). [RFC5415]).

   StatisticsTimer: A 16-bit value representing the time, in seconds,
      that is used by the WTP to determine the interval the WTP uses
      between the WTP Events Requests it transmits to the AC to
      communicate its statistics (see section 4.7.14 of [I-D.ietf-
      capwap-protocol-specification]). [RFC5415]).

   WaitDTLS:  A 16-bit value representing the maximum time, in seconds,
      a WTP MUST wait without having received a DTLS Handshake message
      from an AC. This timer MUST be greater than 30 seconds (see
      section 4.7.15 of [I-D.ietf-capwap-protocol-
      specification]). [RFC5415]).

9.2.  CAPWAP Protocol Variables

         0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                       Vendor Identifier                       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |             Element ID         |        MaxDiscoveries        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |    MaxFailedDTLSSessionRetry   |         MaxRetransmit        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Type:   37 for Vendor Specific Payload

   Length:   12

   Vendor Identifier:   A 32-bit value containing the IANA assigned "SMI
      Network Management Private Enterprise Codes".

   Element ID:   The Element ID field is set to 2 for CAPWAP Protocol
      Variables.

   MaxDiscoveries:  A 16-bit value representing the maximum number of
      Discovery Request messages that will be sent after a WTP boots
      (see section 4.8.5 of [-D.ietf-capwap-protocol-specification]). [RFC5415]).

   MaxFailedDTLSSessionRetry:  A 16-bit value representing the maximum
      number of failed DTLS session establishment attempts before the
      CAPWAP device enters a silent period (see section 4.8.6 of
      [I-D.ietf-capwap-protocol-specification]).
      [RFC5415]).

   MaxRetransmit:  A 16-bit value representing the maximum number of
      retransmissions for a given CAPWAP packet before the link layer
      considers the peer dead (see section 4.8.7 of [I-D.ietf-capwap-
      protocol-specification]). [RFC5415]).

9.3.  CAPWAP Messages for CAPWAP Control Message Extension

   For CAPWAP Control Message Extension, the following CAPWAP messages
   will be used.

9.3.1.  Configuration Status Response Message

   The following message elements MAY be included in the CAPWAP
   Configuration Status Response Message.

   - CAPWAP Protocol Timers, see Section Section 9.1

   - CAPWAP Protocol Variables, see Section Section 9.2

9.3.2.  Configuration Update Response Message

   The following message elements MAY be included in the CAPWAP
   Configuration Update Response Message.

   - CAPWAP Protocol Timers, see Section Section 9.1

   - CAPWAP Protocol Variables, see Section Section 9.2

10.  Definitions

CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN

IMPORTS

   PhysAddress, TEXTUAL-CONVENTION, TruthValue,
   DateAndTime, RowStatus
       FROM SNMPv2-TC
   InterfaceIndex
       FROM IF-MIB
   PhysicalIndex
       FROM ENTITY-MIB
   SnmpAdminString
       FROM SNMP-FRAMEWORK-MIB
   NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE
       FROM SNMPv2-CONF
   MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2,
   Integer32, Unsigned32, Counter32
       FROM SNMPv2-SMI
   InetAddressType, InetAddress
       FROM INET-ADDRESS-MIB;

capwapBaseMIB MODULE-IDENTITY
    LAST-UPDATED "200902280000Z" "200905290000Z"        -- Feb 28th, May 29th, 2009
    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) 2009 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 CAPWAP Protocol."
    REVISION    "200902280000Z"    "200905290000Z"
    DESCRIPTION
        "Initial version published as RFC xxx"
         ::= { mib-2 xxx }

-- Textual Conventions

CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION
    DISPLAY-HINT "d"
    STATUS      current
    DESCRIPTION
        "Represents the unique identifier of a WTP profile."
    SYNTAX      Unsigned32 (0..4096)

CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
                DISPLAY-HINT "32a"
    STATUS      current
    DESCRIPTION
        "Represents an the unique identifier of a WTP instance.
         As usual, a serial number of WTP will be is used."
    SYNTAX      OCTET STRING (SIZE (0..32))

CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION
                DISPLAY-HINT "1x:"
    STATUS      current
    DESCRIPTION
        "Represents an the unique identifier of a station instance.
         As usual, the MAC address of the station will be is used."
    SYNTAX      OCTET STRING (SIZE (6))

CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
    DISPLAY-HINT "d"
    STATUS      current
    DESCRIPTION
        "Represents an the unique identifier of a radio on a WTP."
    SYNTAX      Unsigned32 (1..31)

CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "Represents the tunneling modes of operation that are
         supported by the a WTP.
         The WTP MAY support more than one option, represented by
         the bit field below:
           localBridging(0) - Local Bridging Mode bridging mode
           dot3Tunnel(1)    - 802.3 Frame Tunnel Mode frame tunnel mode
           nativeTunnel(2)  - Native Frame Tunnel Mode" frame tunnel mode"
    REFERENCE
        "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 5415."
    SYNTAX      BITS {
                  localBridging(0),
                  dot3Tunnel(1),
                  nativeTunnel(2)
                }

CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "Represents the MAC mode of operation supported by the a WTP.
         The following enumerated values are supported:
           localMAC(0) - Local-MAC Mode mode
           splitMAC(1) - Split-MAC Mode mode
           both(2)     - Both Local-MAC and Split-MAC"
    REFERENCE
        "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 5415."
    SYNTAX      INTEGER {
                  localMAC(0),
                  splitMAC(1),
                  both(2)
                }

CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "Represents the channel type for CAPWAP protocol.
         The following enumerated values are supported:
           data(1)    - data Channel Data channel
           control(2) - control Channel" Control channel"
    SYNTAX      INTEGER {
                  data(1),
                  control(2)
                }

CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "Represents the authentication credential type for a WTP.
         The following enumerated values are supported:
           other(1) - Other method, for example, vendor specific
           clear(2) - Clear text and no authentication
           x509(3)  - X.509 Certificate certificate authentication
           psk(4)   - Pre-Shared Secret secret authentication
         As mandatory requirement, CAPWAP control channel
         authentication should SHOULD use DTLS, and either by certificate or
         PSK. For data channel, DTLS is optional."
    SYNTAX      INTEGER {
                  other(1),
                  clear(2),
                  x509(3),
                  psk(4)
                }

-- Top level components of this MIB module

-- Notifications
capwapBaseNotifications OBJECT IDENTIFIER
    ::= { capwapBaseMIB 0 }
-- Tables, Scalars
capwapBaseObjects OBJECT IDENTIFIER
    ::= { capwapBaseMIB 1 }
-- Conformance
capwapBaseConformance OBJECT IDENTIFIER
    ::= { capwapBaseMIB 2 }

-- AC Objects Group

capwapBaseAc OBJECT IDENTIFIER
    ::= { capwapBaseObjects 1 }

capwapBaseWtpSessions OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the total number of WTPs which are connecting to
         the AC."
    REFERENCE
        "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 1 }

capwapBaseWtpSessionsLimit  OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the maximum number of WTP sessions configured for on
         the AC." AC.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 2 }

capwapBaseStationSessions  OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the total number of stations which are accessing
         the wireless service provided by the AC."
    REFERENCE
        "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 3 }

capwapBaseStationSessionsLimit  OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the maximum number of station sessions configured
         on the AC.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 4 }

capwapBaseDataChannelDTLSPolicyOptions  OBJECT-TYPE
    SYNTAX      BITS {
                  other(0),
                  clear(1),
                  dtls(2)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The AC communicates its policy on the use of DTLS for
         the
         CAPWAP data channel.
         The AC MAY support more than one option, represented by the bit
         field below:
           other(0) - Other method, for example, vendor specific
           clear(1) - Clear Text text
           dtls(2)  - DTLS"
    REFERENCE
       "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 5 }

capwapBaseDataChannelDTLSPolicyConfig  OBJECT-TYPE
    SYNTAX      INTEGER {
                  other(0),
                  clear(1),
                  dtls(2)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the security policy configured on the AC for
         CAPWAP data channel.
         The value of the object is persistent at restart/reboot.
         The following enumerated values are supported:
           other(0) - Other method, for example, vendor specific
           clear(1) - Clear Text text
           dtls(2)  - DTLS"
    REFERENCE
       "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 6 }

capwapBaseControlChannelAuthenOptions  OBJECT-TYPE
    SYNTAX      BITS {
                  x509(0),
                  psk(1)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the authentication credential type supported by the
         AC for CAPWAP control channel.

         The AC MAY support more than one option, represented by the bit
         field below:
           x509(0) - X.509 Certificate Based certificate based
           psk(1)  - Pre-Shared Secret" secret"
    REFERENCE
       "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 7 }

capwapBaseControlChannelAuthenConfig  OBJECT-TYPE
    SYNTAX      INTEGER {
                  x509(1),
                  psk(2)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the authentication credential type configured for on
         the AC for CAPWAP control channel.
         The value of the object is persistent at restart/reboot.
         The following enumerated values are supported:
           x509(1) - X.509 Certificate Based certificate based
           psk(2)  - Pre-Shared Secret" secret"
    REFERENCE
       "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 8 }

-- capwapBaseAcNameListTable table

capwapBaseAcNameListTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseAcNameListEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of objects that display configure the AC name list." list.
         Values of all read-create objects in this table are
         persistent at restart/reboot."
    REFERENCE
        "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 9 }

capwapBaseAcNameListEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseAcNameListEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that configure the AC name list.
         Values of all read-create objects in this table are persistent
         at restart/reboot." list."
    INDEX { capwapBaseAcNameListId }
    ::= { capwapBaseAcNameListTable 1 }

CapwapBaseAcNameListEntry ::= SEQUENCE {
      capwapBaseAcNameListId          Unsigned32,
      capwapBaseAcNameListName        OCTET STRING,
      capwapBaseAcNameListPriority    Unsigned32,
      capwapBaseAcNameListRowStatus   RowStatus
    }

capwapBaseAcNameListId OBJECT-TYPE
    SYNTAX      Unsigned32 (1..255)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents a the unique id for identifier of a AC Name list."
    ::= { capwapBaseAcNameListEntry 1 }

capwapBaseAcNameListName OBJECT-TYPE
    SYNTAX      OCTET STRING(SIZE(512))
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Represents the name of an AC, and it is expected to be
         an UTF-8 encoded string."
    REFERENCE
        "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAcNameListEntry 2 }

capwapBaseAcNameListPriority OBJECT-TYPE
    SYNTAX      Unsigned32 (1..255)
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Represents the priority order of the preferred AC.
         For instance, the value of one (1) is used to set the primary
         AC, the value of two (2) is used to set the secondary, secondary AC, etc."
    REFERENCE
        "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAcNameListEntry 3 }

capwapBaseAcNameListRowStatus 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."
    ::= { capwapBaseAcNameListEntry 4 }

-- End of capwapBaseAcNameListTable table

-- capwapBaseMacAclTable table

capwapBaseMacAclTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseMacAclEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of objects that configure station Access Control
         List
         Lists (ACL).
         The WTP will not provide service to the MAC addresses
         configured in this table." table.
         Values of all read-create objects in this table are persistent
         at AC restart/reboot."
    REFERENCE
        "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseAc 10 }

capwapBaseMacAclEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseMacAclEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that configure station Access Control
         List (ACL).
         Values of all read-create objects in this table are persisten
         at AC restart/reboot." (ACL)."
    INDEX { capwapBaseMacAclId }
    ::= { capwapBaseMacAclTable 1 }

CapwapBaseMacAclEntry ::= SEQUENCE {
      capwapBaseMacAclId           Unsigned32,
      capwapBaseMacAclStationId    CapwapBaseStationIdTC,
      capwapBaseMacAclRowStatus    RowStatus
    }

capwapBaseMacAclId OBJECT-TYPE
    SYNTAX      Unsigned32 (1..255)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents a the unique id for a identifier of an ACL."
    ::= { capwapBaseMacAclEntry 1 }

capwapBaseMacAclStationId OBJECT-TYPE
    SYNTAX      CapwapBaseStationIdTC
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Represents a station's the MAC address of a station to which WTPs will
         no longer provides service to it." service."
    REFERENCE
        "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseMacAclEntry 2 }

capwapBaseMacAclRowStatus 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."
    ::= { capwapBaseMacAclEntry 3 }

-- End of capwapBaseMacAclTable table

-- End of AC Objects Group

-- WTP Objects Group

capwapBaseWtps OBJECT IDENTIFIER
    ::= { capwapBaseObjects 2 }

-- capwapBaseWtpStateTable table

capwapBaseWtpStateTable capwapBaseWtpProfileTable Table

capwapBaseWtpProfileTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseWtpStateEntry CapwapBaseWtpProfileEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of objects that display WTP CAPWAP FSM state."
    ::= { capwapBaseWtps 1 }

capwapBaseWtpStateEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseWtpStateEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that display configure WTP CAPWAP FSM state."
    INDEX profiles for WTPs to
         be managed before they connect to the AC.
         An operator could change a WTP's configuration by changing
         the values of parameters in the corresponding WTP profile.
         Values of all read-create objects in this table are
         persistent at restart/reboot."
    ::= { capwapBaseWtpStateWtpId capwapBaseWtps 1 }

capwapBaseWtpProfileEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseWtpProfileEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that configure and display a WTP profile."
    INDEX { capwapBaseWtpProfileId }
    ::= { capwapBaseWtpStateTable capwapBaseWtpProfileTable 1 }

CapwapBaseWtpStateEntry

CapwapBaseWtpProfileEntry ::= SEQUENCE {
      capwapBaseWtpStateWtpId
      capwapBaseWtpProfileId                  CapwapBaseWtpProfileIdTC,
      capwapBaseWtpProfileName                       SnmpAdminString,
      capwapBaseWtpProfileWTPSerialId                CapwapBaseWtpIdTC,
      capwapBaseWtpStateWtpIpAddressType
      capwapBaseWtpProfileWTPModelNumber             SnmpAdminString,
      capwapBaseWtpProfileWtpName                    OCTET STRING,
      capwapBaseWtpProfileWtpLocation                OCTET STRING,
      capwapBaseWtpProfileWtpStaticIpEnable          TruthValue,
      capwapBaseWtpProfileWtpStaticIpType            InetAddressType,
      capwapBaseWtpStateWtpIpAddress
      capwapBaseWtpProfileWtpStaticIp                InetAddress,
      capwapBaseWtpStateWtpPhyAddress       PhysAddress,
      capwapBaseWtpState                    INTEGER
      capwapBaseWtpProfileWtpNetmask                 InetAddress,
      capwapBaseWtpProfileWtpGateway                 InetAddress,
      capwapBaseWtpProfileWtpFallbackEnable          INTEGER,
      capwapBaseWtpProfileWtpEchoInterval            Unsigned32,
      capwapBaseWtpProfileWtpIdleTimeout             Unsigned32,
      capwapBaseWtpProfileWtpMaxDiscoveryInterval    Unsigned32,
      capwapBaseWtpProfileWtpReportInterval          Unsigned32,
      capwapBaseWtpProfileWtpSilentInterval          Unsigned32,
      capwapBaseWtpProfileWtpStatisticsTimer         Unsigned32,
      capwapBaseWtpProfileWtpWaitDTLSTimer           Unsigned32,
      capwapBaseWtpProfileWtpEcnSupport              INTEGER,
      capwapBaseWtpProfileRowStatus                  RowStatus
    }

capwapBaseWtpStateWtpId

capwapBaseWtpProfileId OBJECT-TYPE
    SYNTAX      CapwapBaseWtpIdTC      CapwapBaseWtpProfileIdTC
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the unique identifier of a WTP." WTP profile."
    ::= { capwapBaseWtpStateEntry capwapBaseWtpProfileEntry 1 }

capwapBaseWtpStateWtpIpAddressType

capwapBaseWtpProfileName  OBJECT-TYPE
    SYNTAX      InetAddressType      SnmpAdminString
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the type of IP address name of a WTP." WTP profile."
    ::= { capwapBaseWtpStateEntry capwapBaseWtpProfileEntry 2 }

capwapBaseWtpStateWtpIpAddress

capwapBaseWtpProfileWTPSerialId  OBJECT-TYPE
    SYNTAX      InetAddress      CapwapBaseWtpIdTC
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the IP address serial identifier of a WTP." WTP.
         A WTP profile MUST contain the serial number of the WTP
         because the CAPWAP message received from the WTP contains
         its serial number and the AC uses the serial number to
         find the corresponding WTP profile."
    REFERENCE
        "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseWtpStateEntry capwapBaseWtpProfileEntry 3 }

capwapBaseWtpStateWtpPhyAddress

capwapBaseWtpProfileWTPModelNumber  OBJECT-TYPE
    SYNTAX      PhysAddress      SnmpAdminString
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the model number of a WTP.
         A WTP profile MUST include the WTP's model number, which
         reflects the number of PHY address radios on the WTP.
         In this way, the creation of a WTP." WTP profile triggers the AC
         to automatically create the same number of WTP Virtual Radio
         Interfaces corresponding to the WTP's PHY radios without
         manual intervention. With the ifIndexes of WTP Virtual
         Radio Interfaces, the operator could configure and manage
         the WTP's PHY radios through the wireless binding MIB
         modules."
    REFERENCE
        "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseWtpStateEntry capwapBaseWtpProfileEntry 4 }

capwapBaseWtpState

capwapBaseWtpProfileWtpName  OBJECT-TYPE
    SYNTAX      INTEGER {
                  dtls(1),
                  join(2),
                  image(3),
                  configure(4),
                  dataCheck(5),
                  run(6),
                  clear(7),
                  unknown(8)
                }      OCTET STRING(SIZE(512))
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the various possible CAPWAP FSM states name of WTP
         The following enumerated values are supported:

           dtls(1)      - DTLS negotiation states, which include
                          DTLS Setup, Authorize, DTLS Connect
           join(2)      - WTP is joining with AC
           image(3)     - WTP is downloading software
           configure(4) - WTP is getting configuration from AC
           dataCheck(5) - AC is waiting for the Data Channel Keep
                          Alive Packet
           run(6)       - WTP comes to run state
           clear(7)     - WTP recoveries default configuration
           unknown(8)   - Operator already prepare configuration
                          for WTP, while WTP has not contact with AC
                          till now" WTP."
    REFERENCE
        "Section 2.3.1. 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpStateEntry capwapBaseWtpProfileEntry 5 }

-- End of capwapBaseWtpStateTable Table

-- capwapBaseWtpTable Table

capwapBaseWtpTable

capwapBaseWtpProfileWtpLocation  OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseWtpEntry      OCTET STRING(SIZE(1024))
    MAX-ACCESS  not-accessible  read-create
    STATUS      current
    DESCRIPTION
        "A table
        "Represents the location of objects that display and control WTPs in
         running state. Values the WTP."
    REFERENCE
        "Section 4.6.30. of all read-write objects in this
         table are persistent at restart/reboot." CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseWtps 2 capwapBaseWtpProfileEntry 6 }

capwapBaseWtpEntry

capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE
    SYNTAX      CapwapBaseWtpEntry      TruthValue
    MAX-ACCESS  not-accessible  read-create
    STATUS      current
    DESCRIPTION
        "A set
        "Represents whether the WTP SHOULD use a static IP address
         or not. A value of objects that display and control false disables the static IP address,
         while a WTP in
         running state."
    INDEX { capwapBaseWtpCurrId }
    ::= { capwapBaseWtpTable 1 }

CapwapBaseWtpEntry value of true enables it."
    REFERENCE
        "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415."
    ::= SEQUENCE {
      capwapBaseWtpCurrId                       CapwapBaseWtpIdTC,
      capwapBaseWtpPhyIndex                     PhysicalIndex,
      capwapBaseWtpName                         OCTET STRING,
      capwapBaseWtpLocation                     OCTET STRING,
      capwapBaseWtpBaseMacAddress               PhysAddress,
      capwapBaseWtpTunnelModeOptions            CapwapBaseTunnelModeTC,
      capwapBaseWtpMacTypeOptions               CapwapBaseMacTypeTC,
      capwapBaseWtpDiscoveryType                INTEGER,
      capwapBaseWtpRadiosInUseNum               Unsigned32,
      capwapBaseWtpRadioNumLimit                Unsigned32,
      capwapBaseWtpStaticIpEnable               TruthValue,
      capwapBaseWtpStaticIpType                 InetAddressType,
      capwapBaseWtpStaticIp                     InetAddress,
      capwapBaseWtpNetmask                      InetAddress,
      capwapBaseWtpGateway                      InetAddress,
      capwapBaseWtpFallbackEnable               INTEGER,
      capwapBaseWtpRetransmitCount              Counter32,
      capwapBaseWtpMaxDiscoveries               Unsigned32,
      capwapBaseWtpMaxFailedDTLSSessionRetry    Unsigned32,
      capwapBaseWtpMaxRetransmit                Unsigned32,
      capwapBaseWtpDataChannelKeepAliveTimer    Unsigned32,
      capwapBaseWtpDataChannelDeadInterval      Unsigned32,
      capwapBaseWtpDiscoveryInterval            Unsigned32,
      capwapBaseWtpDTLSSessionDeleteTimer       Unsigned32,
      capwapBaseWtpEchoInterval                 Unsigned32,
      capwapBaseWtpIdleTimeout                  Unsigned32,
      capwapBaseWtpImageDataStartTimer          Unsigned32,
      capwapBaseWtpMaxDiscoveryInterval         Unsigned32,
      capwapBaseWtpReportInterval               Unsigned32,
      capwapBaseWtpRetransmitInterval           Unsigned32,
      capwapBaseWtpSilentInterval               Unsigned32,
      capwapBaseWtpStatisticsTimer              Unsigned32,
      capwapBaseWtpWaitDTLSTimer                Unsigned32,
      capwapBaseWtpEcnSupport                   INTEGER capwapBaseWtpProfileEntry 7 }

capwapBaseWtpCurrId

capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE
    SYNTAX      CapwapBaseWtpIdTC      InetAddressType
    MAX-ACCESS  not-accessible  read-create
    STATUS      current
    DESCRIPTION
        "Represents the unique identifier of a WTP which is
         in running state." static IP address type used by the WTP, IPv4
         or IPv6."
    ::= { capwapBaseWtpEntry 1 capwapBaseWtpProfileEntry 8 }

capwapBaseWtpPhyIndex

capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE
    SYNTAX      PhysicalIndex      InetAddress
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the unique physical index of a physical entity
         in
        "When capwapBaseWtpProfileWtpStaticIpEnable is true,
         it represents the ENTITY-MIB module. The information such as software
         version of specific WTP could static IP address to be accessed through the index."
    ::= { capwapBaseWtpEntry 2 }

capwapBaseWtpName  OBJECT-TYPE
    SYNTAX      OCTET STRING(SIZE(512))
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents assigned to the name of a WTP."
    REFERENCE
        "Section 4.6.45. 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEntry 3 capwapBaseWtpProfileEntry 9 }

capwapBaseWtpLocation

capwapBaseWtpProfileWtpNetmask OBJECT-TYPE
    SYNTAX      OCTET STRING(SIZE(1024))      InetAddress
    MAX-ACCESS  read-write  read-create
    STATUS      current
    DESCRIPTION
        "Represents
        "When capwapBaseWtpProfileWtpStaticIpEnable is true,
         it represents the netmask to be assigned to the location of a WTP."
    REFERENCE
        "Section 4.6.30. 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEntry 4 capwapBaseWtpProfileEntry 10 }

capwapBaseWtpBaseMacAddress

capwapBaseWtpProfileWtpGateway OBJECT-TYPE
    SYNTAX      PhysAddress      InetAddress
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents
        "When capwapBaseWtpProfileWtpStaticIpEnable is true,
         it represents the WTP's Base MAC Address, which MAY gateway to be assigned to the primary Ethernet interface." WTP."
    REFERENCE
        "Section 4.6.40. 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEntry 5 capwapBaseWtpProfileEntry 11 }

capwapBaseWtpTunnelModeOptions

capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE
    SYNTAX      CapwapBaseTunnelModeTC      INTEGER {
                  enabled(1),
                  disabled(2)
                }
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents whether to enable or disable automatic CAPWAP
         fallback in the tunneling modes of operation supported by
         the WTP." event that a WTP detects its preferred AC,
         and is not currently connected to it.
         The following enumerated values are supported:
           enabled(1)  - The fallback mode is enabled
           disabled(2) - The fallback mode is disabled"
    REFERENCE
        "Section 4.6.43. 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { enabled }
     ::= { capwapBaseWtpEntry 6 capwapBaseWtpProfileEntry 12 }

capwapBaseWtpMacTypeOptions

capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE
    SYNTAX      CapwapBaseMacTypeTC      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the MAC mode of operation supported by minimum time, in seconds, between sending Echo
         Request messages to the WTP." AC that the WTP has joined."
    REFERENCE
        "Section 4.6.44. 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 30 }
    ::= { capwapBaseWtpEntry 7 capwapBaseWtpProfileEntry 13 }

capwapBaseWtpDiscoveryType

capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE
    SYNTAX      INTEGER {
                  unknown(0),
                  staticConfig(1),
                  dhcp(2),
                  dns(3),
                  acRef(4)
                }
    MAX-ACCESS  read-only      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Represents how WTP discovers the AC.
         The following enumerated values are supported:
           unknown(0)      - Unknown
           staticConfig(1) - Static Configuration
           dhcp(2)         - DHCP
           dns(3)          - DNS
           acRef(4)        - AC Referral" idle timeout value that the WTP SHOULD enforce
         for its active stations."
    REFERENCE
        "Section 4.6.21. 4.7.8. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 300 }
    ::= { capwapBaseWtpEntry 8 capwapBaseWtpProfileEntry 14 }

capwapBaseWtpRadiosInUseNum

capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE
    SYNTAX      Unsigned32 (0..255) (2..180)
    UNITS       "second"
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the number of radios maximum time allowed between sending Discovery
         Request messages, in use on the WTP." seconds."
    REFERENCE
        "Section 4.6.41. 4.7.10. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 20 }
    ::= { capwapBaseWtpEntry 9 capwapBaseWtpProfileEntry 15 }

capwapBaseWtpRadioNumLimit

capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE
    SYNTAX      Unsigned32 (0..255)
    UNITS       "second"
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents the maximum radio number supported by the WTP." interval for WTP to send Decryption Error
         report."
    REFERENCE
        "Section 4.6.41. 4.7.11. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 120 }
    ::= { capwapBaseWtpEntry 10 capwapBaseWtpProfileEntry 16 }

capwapBaseWtpStaticIpEnable

capwapBaseWtpProfileWtpSilentInterval OBJECT-TYPE
    SYNTAX      TruthValue      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-write  read-create
    STATUS      current
    DESCRIPTION
        "Represents whether the WTP should use minimum time, in seconds, a static IP address WTP MUST wait
         before it MAY again send Discovery Request messages or not. A value of false disables the static IP address,
         while
         attempt to a value of true enables it." establish DTLS session."
    REFERENCE
        "Section 4.6.48. 4.7.13. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 30 }
    ::= { capwapBaseWtpEntry 11 capwapBaseWtpProfileEntry 17 }

capwapBaseWtpStaticIpType

capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE
    SYNTAX      InetAddressType      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-write  read-create
    STATUS      current
    DESCRIPTION
        "Represents whether the interval the WTP uses IPv4 or IPv6 static IP address."
    ::= { capwapBaseWtpEntry 12 }

capwapBaseWtpStaticIp OBJECT-TYPE
    SYNTAX      InetAddress
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "When capwapBaseWtpStaticIpEnable is true, it represents between the
         static IP address to assign WTP Events
         Requests it transmits to the WTP." AC to communicate its statistics,
         in seconds."
    REFERENCE
        "Section 4.6.48. 4.7.14. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 120 }
    ::= { capwapBaseWtpEntry 13 capwapBaseWtpProfileEntry 18 }

capwapBaseWtpNetmask

capwapBaseWtpProfileWtpWaitDTLSTimer OBJECT-TYPE
    SYNTAX      InetAddress      Unsigned32 (30..4294967295)
    UNITS       "second"
    MAX-ACCESS  read-write  read-create
    STATUS      current
    DESCRIPTION
        "When capwapBaseWtpStaticIpEnable is true, it represents the
         netmask to assign to
        "Represents the WTP."
    REFERENCE
        "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
    ::= { capwapBaseWtpEntry 14 }

capwapBaseWtpGateway OBJECT-TYPE
    SYNTAX      InetAddress
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "When capwapBaseWtpStaticIpEnable is true, it represents the
         gateway to assign to the WTP." maximum time, in seconds, an AC MUST wait
         without having received a DTLS Handshake message from an AC.
         This timer MUST be greater than 30 seconds."
    REFERENCE
        "Section 4.6.48. 4.7.15. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 60 }
    ::= { capwapBaseWtpEntry 15 capwapBaseWtpProfileEntry 19 }

capwapBaseWtpFallbackEnable

capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE
    SYNTAX      INTEGER {
                  enabled(1),
                  disabled(2)
                  limited(0),
                  fullAndLimited(1)
                }
    MAX-ACCESS  read-write  read-create
    STATUS      current
    DESCRIPTION
        "Represents whether to enable or disable automatic CAPWAP
         fallback in the event that a WTP detects its preferred AC, and
         is not currently connected to it. support for the Explicit Congestion Notification
         (ECN) bits, as defined in [RFC3168].
         The following enumerated values are supported:
           enabled(1)
           limited(0)        - The fallback mode is enabled
           disabled(2) Limited ECN support
           fullAndLimited(1) - The fallback mode is disabled" Full and limited ECN support"
    REFERENCE
        "Section 4.6.42. 4.6.25. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { enabled } 5415."
    ::= { capwapBaseWtpEntry 16 capwapBaseWtpProfileEntry 20 }

capwapBaseWtpRetransmitCount

capwapBaseWtpProfileRowStatus OBJECT-TYPE
    SYNTAX      Counter32      RowStatus
    MAX-ACCESS  read-only  read-create
    STATUS      current
    DESCRIPTION
        "Represents
        "This variable is used to create, modify, and/or delete a row
         in this table.
         Deleting a WTP profile in use will disconnect the number of retransmissions for WTP to
         the AC. So the network management system SHOULD
         ask the operator to confirm such an operation.
         When a given
         CAPWAP packet."
    REFERENCE
        "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." WTP profile entry is removed from the table,
         the corresponding WTP Virtual Radio Interfaces are also
         removed from the CapwapBaseWirelessBindingTable and
         ifTable [RFC2863].
         Also, the related object instances SHOULD be removed from
         the wireless binding MIB modules such as IEEE 802.11
         MIB module [IEEE.802-11.2007]."
    ::= { capwapBaseWtpEntry 17 capwapBaseWtpProfileEntry 21 }

capwapBaseWtpMaxDiscoveries

-- End of capwapBaseWtpProfileTable table

-- capwapBaseWtpStateTable table

capwapBaseWtpStateTable OBJECT-TYPE
    SYNTAX      Unsigned32      SEQUENCE OF CapwapBaseWtpStateEntry
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represent the maximum number
        "A table of Discovery Request messages objects that will be sent after a WTP boots."
    REFERENCE
        "Section 4.8.5. of indicate each WTP's CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 10 } FSM
         state, and helps the operator to query the WTPs' current
         configuration."
    ::= { capwapBaseWtpEntry 18 capwapBaseWtps 2 }

capwapBaseWtpMaxFailedDTLSSessionRetry

capwapBaseWtpStateEntry  OBJECT-TYPE
    SYNTAX      Unsigned32      CapwapBaseWtpStateEntry
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represent the maximum number
        "A set of failed DTLS session
         establishment attempts before objects that display the WTP's CAPWAP device enters FSM state.
         Also, the operator could query the current configuration
         of a
         silent period."
    REFERENCE
        "Section 4.8.6. WTP by using the identifier of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL the corresponding
         WTP profile."
    INDEX { 3 capwapBaseWtpStateWtpId }
    ::= { capwapBaseWtpEntry 19 capwapBaseWtpStateTable 1 }

capwapBaseWtpMaxRetransmit

CapwapBaseWtpStateEntry ::= SEQUENCE {
      capwapBaseWtpStateWtpId                   CapwapBaseWtpIdTC,
      capwapBaseWtpStateWtpIpAddressType        InetAddressType,
      capwapBaseWtpStateWtpIpAddress            InetAddress,
      capwapBaseWtpStateWtpBaseMacAddress       PhysAddress,
      capwapBaseWtpState                        INTEGER,
      capwapBaseWtpStateWtpCurrWtpProfileId     CapwapBaseWtpProfileIdTC
    }

capwapBaseWtpStateWtpId OBJECT-TYPE
    SYNTAX      Unsigned32      CapwapBaseWtpIdTC
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represent
        "Represents the maximum number unique identifier of retransmission for a given
         CAPWAP packet before the link layer considers the peer dead."
    REFERENCE
        "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 5 } WTP."
    ::= { capwapBaseWtpEntry 20 capwapBaseWtpStateEntry 1 }

capwapBaseWtpDataChannelKeepAliveTimer

capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      InetAddressType
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the next opportunity, in seconds, the WTP must
         transmit the Data Channel Keep Alive message."
    REFERENCE
        "Section 4.7.2. IP address type of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 30 } a WTP."
    ::= { capwapBaseWtpEntry 21 capwapBaseWtpStateEntry 2 }

capwapBaseWtpDataChannelDeadInterval

capwapBaseWtpStateWtpIpAddress OBJECT-TYPE
    SYNTAX      Unsigned32 (0..240)
    UNITS       "second"      InetAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, a WTP MUST wait
         without having received a Data Channel Keep Alive packet
         before the destination for the Data Channel Keep Alive
         packets may be considered dead."
    REFERENCE
        "Section 4.7.3. IP address of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 60 } a WTP."
    ::= { capwapBaseWtpEntry 22 capwapBaseWtpStateEntry 3 }

capwapBaseWtpDiscoveryInterval

capwapBaseWtpStateWtpBaseMacAddress  OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      PhysAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, that a WTP MUST
         wait after receiving a Discovery Response message, before
         initiating a DTLS handshake." WTP's Base MAC Address, which MAY be
         assigned to the primary Ethernet interface."
    REFERENCE
        "Section 4.7.5. 4.6.40. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 5 } 5415."
    ::= { capwapBaseWtpEntry 23 capwapBaseWtpStateEntry 4 }

capwapBaseWtpDTLSSessionDeleteTimer

capwapBaseWtpState  OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      INTEGER {
                  dtls(1),
                  join(2),
                  image(3),
                  configure(4),
                  dataCheck(5),
                  run(6),
                  reset(7),
                  dtlsTeardown(8),
                  unknown(9)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, a various possible CAPWAP FSM states of WTP MUST wait
         The following enumerated values are supported:
           dtls(1)         - DTLS negotiation states, which include
                             DTLS setup, authorize, DTLS connect
           join(2)         - The WTP is joining with the AC
           image(3)        - The WTP is downloading software
           configure(4)    - The WTP is getting configuration from
                             the AC
           dataCheck(5)    - The AC is waiting for the Data Channel Keep
                             Alive Packet
           run(6)          - The WTP enters the running state
           reset(7)        - The AC transmits a reset request message
                             to the WTP
           dtlsTeardown(8) - DTLS session deletion." is tear down
           unknown(9)      - Operator already prepared configuration
                             for the WTP, while the WTP has not contact
                             with the AC till now"
    REFERENCE
        "Section 4.7.6. 2.3.1. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 5 } 5415."
    ::= { capwapBaseWtpEntry 24 capwapBaseWtpStateEntry 5 }

capwapBaseWtpEchoInterval

capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      CapwapBaseWtpProfileIdTC
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, between sending Echo
         Request messages to the AC current identifier of a WTP profile.
         The operator could query a WTP's current configuration
         with which the WTP has joined."
    REFERENCE
        "Section 4.7.7. identifier of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 30 } a WTP profile."
    ::= { capwapBaseWtpEntry 25 capwapBaseWtpStateEntry 6 }

capwapBaseWtpIdleTimeout

-- End of capwapBaseWtpStateTable Table

-- capwapBaseWtpTable Table

capwapBaseWtpTable OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      SEQUENCE OF CapwapBaseWtpEntry
    MAX-ACCESS  read-write  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the idle timeout value
        "A table of objects that the WTP SHOULD enforce
         for its active stations."
    REFERENCE
        "Section 4.7.8. display properties of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL the WTPs
         in running state."
    ::= { 300 capwapBaseWtps 3 }

capwapBaseWtpEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseWtpEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that display properties of the WTPs
         in running state."
    INDEX { capwapBaseWtpCurrId }
    ::= { capwapBaseWtpEntry 26 capwapBaseWtpTable 1 }

CapwapBaseWtpEntry ::= SEQUENCE {
      capwapBaseWtpCurrId                       CapwapBaseWtpIdTC,
      capwapBaseWtpPhyIndex                     PhysicalIndex,
      capwapBaseWtpBaseMacAddress               PhysAddress,
      capwapBaseWtpTunnelModeOptions            CapwapBaseTunnelModeTC,
      capwapBaseWtpMacTypeOptions               CapwapBaseMacTypeTC,
      capwapBaseWtpDiscoveryType                INTEGER,
      capwapBaseWtpRadiosInUseNum               Unsigned32,
      capwapBaseWtpRadioNumLimit                Unsigned32,
      capwapBaseWtpRetransmitCount              Counter32,
      capwapBaseWtpMaxDiscoveries               Unsigned32,
      capwapBaseWtpMaxFailedDTLSSessionRetry    Unsigned32,
      capwapBaseWtpMaxRetransmit                Unsigned32,
      capwapBaseWtpDataChannelKeepAliveTimer    Unsigned32,
      capwapBaseWtpDataChannelDeadInterval      Unsigned32,
      capwapBaseWtpDiscoveryInterval            Unsigned32,
      capwapBaseWtpDTLSSessionDeleteTimer       Unsigned32,
      capwapBaseWtpImageDataStartTimer          Unsigned32,
      capwapBaseWtpRetransmitInterval           Unsigned32
    }

capwapBaseWtpCurrId OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      CapwapBaseWtpIdTC
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the number unique identifier of seconds the a WTP will wait for its peer
         to transmit the Image Data Request."
    REFERENCE
        "Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 30 } in running state."
    ::= { capwapBaseWtpEntry 27 1 }

capwapBaseWtpMaxDiscoveryInterval

capwapBaseWtpPhyIndex OBJECT-TYPE
    SYNTAX      Unsigned32 (2..180)
    UNITS       "second"      PhysicalIndex
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the maximum time allowed between sending Discovery
         Request messages, unique physical index of a physical entity
         in seconds.  This value MUST be no less than
         2 seconds and no greater than 180 seconds."
    REFERENCE
        "Section 4.7.10. the ENTITY-MIB module [RFC4133].
         The information such as software version of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 20 } a specific WTP
         could be accessed through the index."
    ::= { capwapBaseWtpEntry 28 2 }

capwapBaseWtpReportInterval

capwapBaseWtpBaseMacAddress  OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      PhysAddress
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the interval for WTP WTP's Base MAC Address, which MAY be assigned
         to send Decryption Error
         report." the primary Ethernet interface."
    REFERENCE
        "Section 4.7.11. 4.6.40. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 120 } 5415."
    ::= { capwapBaseWtpEntry 29 3 }

capwapBaseWtpRetransmitInterval

capwapBaseWtpTunnelModeOptions  OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      CapwapBaseTunnelModeTC
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, in which a
         non-acknowledged CAPWAP packet will be retransmitted." tunneling modes of operation supported by
         the WTP."
    REFERENCE
        "Section 4.7.12. 4.6.43. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 3 } 5415."
    ::= { capwapBaseWtpEntry 30 4 }

capwapBaseWtpSilentInterval

capwapBaseWtpMacTypeOptions  OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      CapwapBaseMacTypeTC
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, a WTP MUST wait
         before it MAY again send Discovery Request messages or attempt
         to a establish DTLS session." MAC mode of operation supported by the WTP."
    REFERENCE
        "Section 4.7.13. 4.6.44. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 30 } 5415."
    ::= { capwapBaseWtpEntry 31 5 }

capwapBaseWtpStatisticsTimer

capwapBaseWtpDiscoveryType OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      INTEGER {
                  unknown(0),
                  staticConfig(1),
                  dhcp(2),
                  dns(3),
                  acRef(4)
                }
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the interval the WTP uses between how the WTP Events
         Requests it transmits to discovers the AC.
         The following enumerated values are supported:
           unknown(0)      - Unknown
           staticConfig(1) - Static configuration
           dhcp(2)         - DHCP
           dns(3)          - DNS
           acRef(4)        - AC to communicate its statistics,
         in seconds." referral"
    REFERENCE
        "Section 4.7.14. 4.6.21. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 120 } 5415."
    ::= { capwapBaseWtpEntry 32 6 }

capwapBaseWtpWaitDTLSTimer

capwapBaseWtpRadiosInUseNum OBJECT-TYPE
    SYNTAX      Unsigned32 (30..4294967295)
    UNITS       "second" (0..255)
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the maximum time, number of radios in seconds, an AC MUST wait
         without having received a DTLS Handshake message from an AC.

         This timer MUST be greater than 30 seconds." use on the WTP."
    REFERENCE
        "Section 4.7.15. 4.6.41. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 60 } 5415."
    ::= { capwapBaseWtpEntry 33 7 }

capwapBaseWtpEcnSupport

capwapBaseWtpRadioNumLimit OBJECT-TYPE
    SYNTAX      INTEGER {
                  limited(0),
                  fullAndLimited(1)
                }      Unsigned32 (0..255)
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the support for maximum radio number supported by the Explicit Congestion Notification
         (ECN) bits, as defined in [RFC3168]." WTP."
    REFERENCE
        "Section 4.7.25. 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEntry 34 8 }

-- End of capwapBaseWtpTable table

-- capwapBaseWirelessBindingTable Table

capwapBaseWirelessBindingTable

capwapBaseWtpRetransmitCount OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseWirelessBindingEntry      Counter32
    UNITS       "retransmissions"
    MAX-ACCESS  not-accessible  read-only
    STATUS      current
    DESCRIPTION
        "A table of objects that display
        "Represents the mapping relationship
         between specific interface number of 'WTP Virtual Radio Interface'
         ifType and PHY radio, and wireless binding type retransmissions for a specific radio. The mapping relationship in this table
         is persistent at restart/reboot." given
         CAPWAP packet."
    REFERENCE
        "Section 4.8.8. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseWtps 3 capwapBaseWtpEntry 9 }

capwapBaseWirelessBindingEntry

capwapBaseWtpMaxDiscoveries OBJECT-TYPE
    SYNTAX      CapwapBaseWirelessBindingEntry      Unsigned32
    MAX-ACCESS  not-accessible  read-only
    STATUS      current
    DESCRIPTION
        "A set
        "Represents the maximum number of objects Discovery Request messages
         that display the mapping relationship
         between 'WTP Virtual Radio Interface' and PHY radio, and
         wireless binding type for will be sent after a specific radio."
    INDEX {
      capwapBaseWtpStateWtpId,
      capwapBaseWirelessBindingRadioId
    }
    ::= WTP boots."
    REFERENCE
        "Section 4.8.5. of CAPWAP Protocol Specification, RFC 5415."
    DEFVAL { capwapBaseWirelessBindingTable 1 10 }

CapwapBaseWirelessBindingEntry
    ::= SEQUENCE {
      capwapBaseWirelessBindingRadioId              CapwapBaseRadioIdTC,
      capwapBaseWirelessBindingVirtualRadioIfIndex  InterfaceIndex,
      capwapBaseWirelessBindingType                 INTEGER capwapBaseWtpEntry 10 }

capwapBaseWirelessBindingRadioId

capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE
    SYNTAX      CapwapBaseRadioIdTC      Unsigned32
    MAX-ACCESS  not-accessible  read-only
    STATUS      current
    DESCRIPTION
        "Represents the identifier maximum number of failed DTLS session
         establishment attempts before the CAPWAP device enters a PHY radio on a WTP, and only
         requires unique on a WTP.
         For example, WTP A and WTP B will use same value of
         capwapBaseWirelessBindingRadioId for their first radio."
         silent period."
    REFERENCE
        "Section 4.3. 4.8.6. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 3 }
    ::= { capwapBaseWirelessBindingEntry 1 capwapBaseWtpEntry 11 }

capwapBaseWirelessBindingVirtualRadioIfIndex

capwapBaseWtpMaxRetransmit OBJECT-TYPE
    SYNTAX      InterfaceIndex      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the index value that uniquely identifies a
         'WLAN Virtual Radio Interface'. The interface identified by
         a particular value of this index is the same interface as
         identified by the same value maximum number of ifIndex.
         Before WTPs connect to AC and get configuration, operator
         will prepare configuration retransmission for them. On a given
         CAPWAP packet before the AC, there are
         interfaces of 'WTP Virtual Radio Interface' ifType which
         represent PHY radio interfaces on link layer considers the WTP.
         As most MIB modules use ifIndex to identify an interface for
         configuration and statistic data, for example, IEEE 802.11 MIB
         module. It will be very easy to reuse other wireless binding
         MIB modules through 'WTP Virtual Radio Interface'." peer dead."
    REFERENCE
        "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415."
    DEFVAL { 5 }
    ::= { capwapBaseWirelessBindingEntry 2 capwapBaseWtpEntry 12 }

capwapBaseWirelessBindingType

capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE
    SYNTAX      INTEGER {
                  dot11(1),
                  epc(3)
                }      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the wireless binding type for radio.
         The following enumerated values are supported:
           dot11(1)     - IEEE 802.11
           epc(3)       - EPCGlobal" next opportunity, in seconds, the WTP must
         transmit the Data Channel Keep Alive message."
    REFERENCE
        "Section 4.3. 4.7.2. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 30 }
    ::= { capwapBaseWirelessBindingEntry 3 capwapBaseWtpEntry 13 }

-- End of capwapBaseWirelessBindingTable Table

-- capwapBaseStationTable Table

capwapBaseStationTable

capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseStationEntry      Unsigned32 (0..240)
    UNITS       "second"
    MAX-ACCESS  not-accessible  read-only
    STATUS      current
    DESCRIPTION
        "A table of objects that display stations which are accessing
        "Represents the wireless service provided by minimum time, in seconds, a WTP MUST wait
         without having received a Data Channel Keep Alive packet
         before the AC." destination for the Data Channel Keep Alive
         packets MAY be considered dead."
    REFERENCE
        "Section 4.6.8. 4.7.3. of CAPWAP Protocol Specification, RFC xxx."
    ::= { capwapBaseWtps 4 }

capwapBaseStationEntry OBJECT-TYPE
    SYNTAX      CapwapBaseStationEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that display a station which is
         associated with the specific radio on the WTP."
    INDEX {
      capwapBaseWtpCurrId,
      capwapBaseWirelessBindingRadioId,
      capwapBaseStationId
    }
    ::= 5415."
    DEFVAL { capwapBaseStationTable 1 60 }

CapwapBaseStationEntry
    ::= SEQUENCE {
      capwapBaseStationId           CapwapBaseStationIdTC,
      capwapBaseStationAddedTime    DateAndTime,
      capwapBaseStationVlanName     SnmpAdminString capwapBaseWtpEntry 14 }

capwapBaseStationId

capwapBaseWtpDiscoveryInterval OBJECT-TYPE
    SYNTAX      CapwapBaseStationIdTC      Unsigned32
    UNITS       "second"
    MAX-ACCESS  not-accessible  read-only
    STATUS      current
    DESCRIPTION
        "Represents the unique identifier of the station." minimum time, in seconds, that a WTP MUST
         wait after receiving a Discovery Response message, before
         initiating a DTLS handshake."
    REFERENCE
        "Section 4.6.8. 4.7.5. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 5 }
    ::= { capwapBaseStationEntry 1 capwapBaseWtpEntry 15 }

capwapBaseStationAddedTime

capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE
    SYNTAX      DateAndTime      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the time when the station is added." minimum time, in seconds, a WTP MUST wait
         for DTLS session deletion."
    REFERENCE
        "Section 4.6.8. 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 5 }
     ::= { capwapBaseStationEntry 2 capwapBaseWtpEntry 16 }

capwapBaseStationVlanName

capwapBaseWtpImageDataStartTimer OBJECT-TYPE
    SYNTAX      SnmpAdminString (SIZE (0..32))      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents VLAN name to which the station is associated." number of seconds the WTP will wait for its
         peer to transmit the Image Data Request."
    REFERENCE
        "Section 4.6.8. 4.7.9. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 30 }
    ::= { capwapBaseStationEntry capwapBaseWtpEntry 17 }

capwapBaseWtpRetransmitInterval OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, in which a
         non-acknowledged CAPWAP packet will be retransmitted."
    REFERENCE
        "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415."
    DEFVAL { 3 }
    ::= { capwapBaseWtpEntry 18 }

-- End of capwapBaseStationTable Table capwapBaseWtpTable table

--  capwapBaseWtpEventsStatsTable

capwapBaseWtpEventsStatsTable capwapBaseWirelessBindingTable Table

capwapBaseWirelessBindingTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseWtpEventsStatsEntry CapwapBaseWirelessBindingEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of objects that display WTPs' events statistics."
    REFERENCE
        "Section 4.6.47. the mappings between
         WTP Virtual Radio Interfaces and PHY radios, and the
         wireless binding type for each PHY radio.
         Values of CAPWAP Protocol Specification, RFC xxx." all objects in this table are persistent at
         restart/reboot."
    ::= { capwapBaseWtps 5 4 }

capwapBaseWtpEventsStatsEntry

capwapBaseWirelessBindingEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseWtpEventsStatsEntry      CapwapBaseWirelessBindingEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that display the events statistic data
         of mapping between
         a WTP."
    REFERENCE
        "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." specific WTP Virtual Radio Interface and a PHY
         radio, and the wireless binding type for the PHY radio."
    INDEX { capwapBaseWtpCurrId
      capwapBaseWtpProfileId,
      capwapBaseWirelessBindingRadioId
    }
    ::= { capwapBaseWtpEventsStatsTable capwapBaseWirelessBindingTable 1 }

CapwapBaseWtpEventsStatsEntry

CapwapBaseWirelessBindingEntry ::= SEQUENCE {
      capwapBaseWtpEventsStatsRebootCount            Counter32,
      capwapBaseWtpEventsStatsInitCount              Counter32,
      capwapBaseWtpEventsStatsLinkFailureCount       Counter32,
      capwapBaseWtpEventsStatsSwFailureCount         Counter32,
      capwapBaseWtpEventsStatsHwFailureCount         Counter32,
      capwapBaseWtpEventsStatsOtherFailureCount      Counter32,
      capwapBaseWtpEventsStatsUnknownFailureCount    Counter32,
      capwapBaseWtpEventsStatsLastFailureType
      capwapBaseWirelessBindingRadioId              CapwapBaseRadioIdTC,
      capwapBaseWirelessBindingVirtualRadioIfIndex  InterfaceIndex,
      capwapBaseWirelessBindingType                 INTEGER
    }

capwapBaseWtpEventsStatsRebootCount

capwapBaseWirelessBindingRadioId OBJECT-TYPE
    SYNTAX      Counter32      CapwapBaseRadioIdTC
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the number identifier of reboots that have occurred due a PHY radio on a WTP, which
         is required to be unique on a WTP.
         For example, WTP crash. A and WTP B use a same value of 65535 implies that this information is
         not available on the WTP."
         capwapBaseWirelessBindingRadioId for their first radio."
    REFERENCE
        "Section 4.6.47. 4.3. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEventsStatsEntry capwapBaseWirelessBindingEntry 1 }

capwapBaseWtpEventsStatsInitCount

capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE
    SYNTAX      Counter32      InterfaceIndex
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of reboots index value that have occurred at the
         request of uniquely identifies a CAPWAP protocol message, such as a change in
         configuration that required
         WLAN Virtual Radio Interface. The interface identified by
         a reboot or an explicit CAPWAP
         protocol reset request.  A particular value of 65535 implies that this
         information index is not available on the WTP."
    REFERENCE
        "Section 4.6.47. same interface as
         identified by the same value of CAPWAP Protocol Specification, RFC xxx." the ifIndex.
         Before WTPs contact the AC to get configuration,
         the operator configures WTP profiles for them.
         The creation of a WTP profile triggers system to automatically
         create a specific number of WTP Virtual Radio Interfaces and
         add a new row object in the capwapBaseWirelessBindingTable
         without manual intervention.
         As most MIB modules use the ifIndex to identify an interface
         for configuration and statistic data, for example, IEEE 802.11
         MIB module [IEEE.802-11.2007]
         It will be easy to reuse other wireless binding MIB modules
         through the WTP Virtual Radio Interface in the Centralized
         WLAN Architecture."
    ::= { capwapBaseWtpEventsStatsEntry capwapBaseWirelessBindingEntry 2 }

capwapBaseWtpEventsStatsLinkFailureCount

capwapBaseWirelessBindingType OBJECT-TYPE
    SYNTAX      Counter32      INTEGER {
                  dot11(1),
                  epc(3)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that a CAPWAP protocol
         connection with an AC has failed due to link failure." wireless binding type for the radio.
         The following enumerated values are supported:
           dot11(1) - IEEE 802.11
           epc(3)   - EPCGlobal"
    REFERENCE
        "Section 4.6.47. 4.3. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEventsStatsEntry capwapBaseWirelessBindingEntry 3 }

capwapBaseWtpEventsStatsSwFailureCount

-- End of capwapBaseWirelessBindingTable Table

-- capwapBaseStationTable Table

capwapBaseStationTable OBJECT-TYPE
    SYNTAX      Counter32      SEQUENCE OF CapwapBaseStationEntry
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the number
        "A table of times objects that a CAPWAP protocol
         connection with an AC has failed due to software related
         reasons." display stations which are accessing
         the wireless service provided by the AC."
    REFERENCE
        "Section 4.6.47. 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEventsStatsEntry 4 capwapBaseWtps 5 }

capwapBaseWtpEventsStatsHwFailureCount

capwapBaseStationEntry OBJECT-TYPE
    SYNTAX      Counter32      CapwapBaseStationEntry
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the number
        "A set of times objects that display a CAPWAP protocol
         connection with an AC has failed due to hardware related
         reasons."
    REFERENCE
        "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." station which is
         associated with the specific radio on the WTP."
    INDEX {
      capwapBaseWtpCurrId,
      capwapBaseWirelessBindingRadioId,
      capwapBaseStationId
    }
    ::= { capwapBaseWtpEventsStatsEntry 5 capwapBaseStationTable 1 }

capwapBaseWtpEventsStatsOtherFailureCount

CapwapBaseStationEntry ::= SEQUENCE {
      capwapBaseStationId           CapwapBaseStationIdTC,
      capwapBaseStationAddedTime    DateAndTime,
      capwapBaseStationVlanName     SnmpAdminString
    }

capwapBaseStationId OBJECT-TYPE
    SYNTAX      Counter32      CapwapBaseStationIdTC
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the number unique identifier of times that a CAPWAP protocol
         connection with an AC has failed due to known reasons, other
         than AC initiated, link, software or hardware failure." the station."
    REFERENCE
        "Section 4.6.47. 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEventsStatsEntry 6 capwapBaseStationEntry 1 }

capwapBaseWtpEventsStatsUnknownFailureCount

capwapBaseStationAddedTime OBJECT-TYPE
    SYNTAX      Counter32      DateAndTime
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that a CAPWAP protocol
         connection with an AC has failed for unknown reasons." time when the station is added."
    REFERENCE
        "Section 4.6.47. 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEventsStatsEntry 7 capwapBaseStationEntry 2 }

capwapBaseWtpEventsStatsLastFailureType

capwapBaseStationVlanName OBJECT-TYPE
    SYNTAX      INTEGER {
                  notSupport(0),
                  acInit(1),
                  linkFailure(2),
                  swFailure(3),
                  hwFailure(4),
                  otherFailure(5),
                  unknown(255)
                }      SnmpAdminString (SIZE (0..32))
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents VLAN name to which the failure type of the most recent WTP failure.
         The following enumerated values are supported:
           notSupport(0)   - Not Supported
           acInit(1)       - AC Initiated
           linkFailure(2)  - Link Failure
           swFailure(3)    - Software Failure
           hwFailure(4)    - Hardware Failure
           otherFailure(5) - Other Failure
           unknown(255)    - Unknown (e.g., WTP doesn't keep track
                             of info)" station is associated."
    REFERENCE
        "Section 4.6.47. 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtpEventsStatsEntry 8 capwapBaseStationEntry 3 }

-- End of capwapBaseWtpEventsStatsTable table capwapBaseStationTable Table

--  capwapBaseRadioEventsStatsTable table

capwapBaseRadioEventsStatsTable  capwapBaseWtpEventsStatsTable

capwapBaseWtpEventsStatsTable  OBJECT-TYPE
    SYNTAX      SEQUENCE OF CapwapBaseRadioEventsStatsEntry CapwapBaseWtpEventsStatsEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of objects that display statistics on radios behavior,
         and reasons why the WTP radio has been reset." WTPs' events statistics."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtps 6 }

capwapBaseRadioEventsStatsEntry

capwapBaseWtpEventsStatsEntry  OBJECT-TYPE
    SYNTAX      CapwapBaseRadioEventsStatsEntry      CapwapBaseWtpEventsStatsEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that display the events statistic data
         of
         events happened on a specific radio of a WTP."
    REFERENCE
        "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
    INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId capwapBaseWtpCurrId }
    ::= { capwapBaseRadioEventsStatsTable capwapBaseWtpEventsStatsTable 1 }

CapwapBaseRadioEventsStatsEntry

CapwapBaseWtpEventsStatsEntry ::= SEQUENCE {
      capwapBaseRadioEventsStatsResetCount
      capwapBaseWtpEventsStatsRebootCount            Counter32,
      capwapBaseRadioEventsStatsSwFailCount
      capwapBaseWtpEventsStatsInitCount              Counter32,
      capwapBaseRadioEventsStatsHwFailCount
      capwapBaseWtpEventsStatsLinkFailureCount       Counter32,
      capwapBaseRadioEventsStatsOtherFailCount
      capwapBaseWtpEventsStatsSwFailureCount         Counter32,
      capwapBaseRadioEventsStatsUnknownFailCount
      capwapBaseWtpEventsStatsHwFailureCount         Counter32,
      capwapBaseRadioEventsStatsConfigUpdateCount     Counter32,
      capwapBaseRadioEventsStatsChannelChangeCount    Counter32,
      capwapBaseRadioEventsStatsBandChangeCount
      capwapBaseWtpEventsStatsOtherFailureCount      Counter32,
      capwapBaseRadioEventsStatsCurrentNoiseFloor     Integer32,
      capwapBaseRadioEventsStatsDecryptErrorCount
      capwapBaseWtpEventsStatsUnknownFailureCount    Counter32,
      capwapBaseRadioEventsStatsLastFailType
      capwapBaseWtpEventsStatsLastFailureType        INTEGER
    }

capwapBaseRadioEventsStatsResetCount

capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times reboots that have occurred due to a
         WTP crash.  A value of 65535 implies that this information is
         not available on the radio has been
         reset." WTP."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 1 }

capwapBaseRadioEventsStatsSwFailCount

capwapBaseWtpEventsStatsInitCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times reboots that have occurred at the radio has failed due
         to software related reasons."
         request of a CAPWAP protocol message, such as a change in
         configuration that requires a reboot or an explicit CAPWAP
         protocol reset request.  A value of 65535 implies that this
         information is not available on the WTP."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 2 }

capwapBaseRadioEventsStatsHwFailCount

capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that the radio a CAPWAP protocol
         connection with an AC has failed due to hardware related reasons." link failures."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 3 }

capwapBaseRadioEventsStatsOtherFailCount

capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that the radio a CAPWAP protocol
         connection with an AC has failed due to
         known reasons, other than software or hardware failure." related
         reasons."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 4 }

capwapBaseRadioEventsStatsUnknownFailCount

capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that the radio a CAPWAP protocol
         connection with an AC has failed for
         unknown due to hardware related
         reasons."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 5 }

capwapBaseRadioEventsStatsConfigUpdateCount

capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that the radio configuration a CAPWAP protocol
         connection with an AC has
         been updated." failed due to known reasons, other
         than the AC initiated, link, software or hardware failures."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 6 }

capwapBaseRadioEventsStatsChannelChangeCount

capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of times that the radio channel a CAPWAP protocol
         connection with an AC has
         been changed." failed for unknown reasons."
    REFERENCE
        "Section 4.6.46. 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry capwapBaseWtpEventsStatsEntry 7 }

capwapBaseRadioEventsStatsBandChangeCount

capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE
    SYNTAX      Counter32      INTEGER {
                  notSupport(0),
                  acInit(1),
                  linkFailure(2),
                  swFailure(3),
                  hwFailure(4),
                  otherFailure(5),
                  unknown(255)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number failure type of times that the radio has changed
         frequency bands."
    REFERENCE
        "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
    ::= { capwapBaseRadioEventsStatsEntry 8 }

capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE most recent WTP failure.
         The following enumerated values are supported:
           notSupport(0)   - Not supported
           acInit(1)       - The AC initiated
           linkFailure(2)  - Link failure
           swFailure(3)    - Software failure
           hwFailure(4)    - Hardware failure
           otherFailure(5) - Other failure
           unknown(255)    - Unknown (e.g., WTP doesn't keep track
                             of info)"
    REFERENCE
        "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseWtpEventsStatsEntry 8 }

--  End of capwapBaseWtpEventsStatsTable table

--  capwapBaseRadioEventsStatsTable table

capwapBaseRadioEventsStatsTable  OBJECT-TYPE
    SYNTAX      Integer32
    UNITS       "dBm"      SEQUENCE OF CapwapBaseRadioEventsStatsEntry
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "Represents the noise floor
        "A table of objects that display statistics on radios behavior,
         and reasons why the WTP radio receiver in units of
         dBm." has been reset."
    REFERENCE
        "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseWtps 7 }

capwapBaseRadioEventsStatsEntry 9  OBJECT-TYPE
    SYNTAX      CapwapBaseRadioEventsStatsEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of objects that display the statistic data of
         events happened on a specific radio of a WTP."
    INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId }
    ::= { capwapBaseRadioEventsStatsTable 1 }

CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
      capwapBaseRadioEventsStatsResetCount            Counter32,
      capwapBaseRadioEventsStatsSwFailCount           Counter32,
      capwapBaseRadioEventsStatsHwFailCount           Counter32,
      capwapBaseRadioEventsStatsOtherFailCount        Counter32,
      capwapBaseRadioEventsStatsUnknownFailCount      Counter32,
      capwapBaseRadioEventsStatsConfigUpdateCount     Counter32,
      capwapBaseRadioEventsStatsChannelChangeCount    Counter32,
      capwapBaseRadioEventsStatsBandChangeCount       Counter32,
      capwapBaseRadioEventsStatsCurrentNoiseFloor     Integer32,
      capwapBaseRadioEventsStatsDecryptErrorCount     Counter32,
      capwapBaseRadioEventsStatsLastFailType          INTEGER
    }

capwapBaseRadioEventsStatsResetCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of decryption errors times that occurred on the
         WTP.  Note that this field is only valid in cases where the WTP
         provides encryption/decryption services." radio has been
         reset."
    REFERENCE
        "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry 10 1 }

capwapBaseRadioEventsStatsLastFailType

capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE
    SYNTAX      INTEGER {
                  notSupport(0),
                  swFailure(1),
                  hwFailure(2),
                  otherFailure(3),
                  unknown(255)
                }      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the failure type number of times that the most recent radio failure.
         The following enumerated values are supported:
           notSupport(0)   - Not Supported
           swFailure(1)    - Software Failure
           hwFailure(2)    - Hardware Failure
           otherFailure(3) - Other Failure
           unknown(255)    - Unknown" has failed due
         to software related reasons."
    REFERENCE
        "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseRadioEventsStatsEntry 11 2 }

--  End

capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of capwapBaseRadioEventsStatsTable table
-- End times that the radio has failed due
         to hardware related reasons."
    REFERENCE
        "Section 4.6.46. of WTP Objects Group

-- CAPWAP Base Parameters Group

capwapBaseParameters OBJECT IDENTIFIER Protocol Specification, RFC 5415."
    ::= { capwapBaseObjects capwapBaseRadioEventsStatsEntry 3 }

capwapBaseAcMaxRetransmit

capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE
    SYNTAX      Unsigned32      Counter32
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represent
        "Represents the maximum number of retransmission for a given
         CAPWAP packet before the link layer considers the peer dead.
         The value of times that the object is persistent at restart/reboot." radio has failed due to
         known reasons, other than software or hardware failure."
    REFERENCE
        "Section 4.8.7. 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 5 } 5415."
    ::= { capwapBaseParameters 1 capwapBaseRadioEventsStatsEntry 4 }

capwapBaseAcChangeStatePendingTimer

capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      Counter32
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the maximum time, in seconds, the AC will wait
         for the Change State Event Request from the WTP after having
         transmitted a successful Configuration Status Response
         message.
         The value number of times that the object is persistent at restart/reboot." radio has failed for
         unknown reasons."
    REFERENCE
        "Section 4.7.1. 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 25 } 5415."
    ::= { capwapBaseParameters 2 capwapBaseRadioEventsStatsEntry 5 }

capwapBaseAcDataCheckTimer

capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      Counter32
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents The the number of seconds the AC will wait for
         the Data Channel Keep Alive, which is required by times that the radio configuration has
         been updated."
    REFERENCE
        "Section 4.6.46. of CAPWAP state machine's Data Check state.
         The AC resets the state machine if this timer expires
         prior to transitioning to Protocol Specification, RFC 5415."
    ::= { capwapBaseRadioEventsStatsEntry 6 }

capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the next state.
         The value number of times that the object is persistent at restart/reboot." radio channel has
         been changed."
    REFERENCE
        "Section 4.7.4. 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 30 } 5415."
    ::= { capwapBaseParameters 3 capwapBaseRadioEventsStatsEntry 7 }

capwapBaseAcDTLSSessionDeleteTimer

capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"      Counter32
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, an AC MUST wait
         for DTLS session deletion.
         The value number of times that the object is persistent at restart/reboot." radio has changed
         frequency bands."
    REFERENCE
        "Section 4.7.6. 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL { 5 } 5415."
    ::= { capwapBaseParameters 4 capwapBaseRadioEventsStatsEntry 8 }

capwapBaseAcEchoInterval

capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE
    SYNTAX      Unsigned32      Integer32
    UNITS       "second"       "dBm"
    MAX-ACCESS  read-write  read-only
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, between sending Echo
         Request messages to noise floor of the AC with which radio receiver in units of
         dBm."
    REFERENCE
        "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseRadioEventsStatsEntry 9 }

capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the WTP has joined.
         The value number of decryption errors that have occurred
         on the object WTP.  Note that this field is persistent at restart/reboot." only valid in cases where
         the WTP provides encryption/decryption services."
    REFERENCE
        "Section 4.7.7. 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
    DEFVAL 5415."
    ::= { 30 capwapBaseRadioEventsStatsEntry 10 }

capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE
    SYNTAX      INTEGER {
                  notSupport(0),
                  swFailure(1),
                  hwFailure(2),
                  otherFailure(3),
                  unknown(255)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the failure type of the most recent radio failure.
         The following enumerated values are supported:
           notSupport(0)   - Not supported
           swFailure(1)    - Software failure
           hwFailure(2)    - Hardware failure
           otherFailure(3) - Other failure
           unknown(255)    - Unknown"
    REFERENCE
        "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseRadioEventsStatsEntry 11 }

--  End of capwapBaseRadioEventsStatsTable table

-- End of WTP Objects Group

-- CAPWAP Base Parameters Group

capwapBaseParameters 5 OBJECT IDENTIFIER
    ::= { capwapBaseObjects 3 }

capwapBaseAcRetransmitInterval

capwapBaseAcMaxRetransmit OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the minimum time, in seconds, in which maximum number of retransmissions for a
         non-acknowledged given
         CAPWAP packet will be retransmitted. before the link layer considers the peer dead.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.7.12. 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 3 5 }
    ::= { capwapBaseParameters 6 1 }

capwapBaseAcSilentInterval

capwapBaseAcChangeStatePendingTimer OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the minimum maximum time, in seconds, during which the AC
         SHOULD ignore all CAPWAP and DTLS packets received will wait
         for the Change State Event Request from the WTP that is in the Sulking state. after having
         transmitted a successful Configuration Status Response
         message.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.7.13. 4.7.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 30 25 }
    ::= { capwapBaseParameters 7 2 }

capwapBaseAcWaitDTLSTimer

capwapBaseAcDataCheckTimer OBJECT-TYPE
    SYNTAX      Unsigned32 (30..4294967295)
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents The number of seconds the maximum time, in seconds, an AC MUST will wait
         without having received a DTLS Handshake message from an AC.
         This for
         the Data Channel Keep Alive, which is required by the
         CAPWAP state machine's Data Check state.
         The AC resets the state machine if this timer MUST be greater than 30 seconds. expires
         prior to transitioning to the next state.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.7.15. 4.7.4. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 60 30 }
    ::= { capwapBaseParameters 8 3 }

capwapBaseAcWaitJoinTimer

capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE
    SYNTAX      Unsigned32 (20..4294967295)
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the maximum minimum time, in seconds, an the AC will MUST wait after
         the
         for DTLS session has been established until it receives the
         Join Request from the WTP. This timer MUST be greater than 20
         seconds. deletion.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.7.16. 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 60 5 }
    ::= { capwapBaseParameters 9 4 }

capwapBaseAcEcnSupport

capwapBaseAcEchoInterval OBJECT-TYPE
    SYNTAX      INTEGER {
                  limited(0),
                  fullAndLimited(1)
                }      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Represents the support for the Explicit Congestion Notification
         (ECN) bits, as defined minimum time, in [RFC3168]. seconds, between sending Echo
         Request messages to the AC with which the WTP has joined.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.7.25. 4.7.7. of CAPWAP Protocol Specification, RFC xxx."
    ::= 5415."
    DEFVAL { capwapBaseParameters 10 30 }

-- End of CAPWAP Base Parameters Group

-- CAPWAP Statistics Group

capwapBaseStats OBJECT IDENTIFIER
    ::= { capwapBaseObjects 4 capwapBaseParameters 5 }

capwapBaseFailedDTLSAuthFailCount

capwapBaseAcRetransmitInterval OBJECT-TYPE
    SYNTAX      Counter32      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only  read-write
    STATUS      current
    DESCRIPTION
        "Represents the number minimum time, in seconds, in which a
         non-acknowledged CAPWAP packet will be retransmitted.

         The value of failed DTLS session
         establishment attempts due to authentication failures." the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.8.3. 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 5415."
    DEFVAL { 3 }
    ::= { capwapBaseStats 1 capwapBaseParameters 6 }

capwapBaseFailedDTLSSessionCount

capwapBaseAcSilentInterval OBJECT-TYPE
    SYNTAX      Counter32      Unsigned32
    UNITS       "second"
    MAX-ACCESS  read-only  read-write
    STATUS      current
    DESCRIPTION
        "Represents the number of failed minimum time, in seconds, during which the AC
         SHOULD ignore all CAPWAP and DTLS session
         establishment attempts." packets received from the
         WTP that is in the Sulking state.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.8.4. 4.7.13. of CAPWAP Protocol Specification, RFC xxx."
    ::= 5415."
    DEFVAL { capwapBaseStats 2 30 }

-- Notifications

capwapBaseChannelUp NOTIFICATION-TYPE
    OBJECTS
    ::= {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfChannelType,
                  capwapBaseNtfAuthenMethod capwapBaseParameters 7 }

capwapBaseAcWaitDTLSTimer OBJECT-TYPE
    SYNTAX      Unsigned32 (30..4294967295)
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "This notification is sent by
        "Represents the maximum time, in seconds, the AC when MUST wait
         without having received a CAPWAP channel
         established. DTLS Handshake message from an AC.
         This timer MUST be greater than 30 seconds.
         The notification is separated for data or control
         channel."
    ::= { capwapBaseNotifications 1 }

capwapBaseChannelDown NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfChannelType,
                  capwapBaseNtfChannelDownReason
                }
    STATUS      current
    DESCRIPTION
        "This notification value of the object is sent by AC when persistent at restart/reboot."
    REFERENCE
        "Section 4.7.15. of CAPWAP channel becomes
         down. The notification is separated for data or control
         channel."
    ::= Protocol Specification, RFC 5415."
    DEFVAL { capwapBaseNotifications 2 60 }

capwapBaseDecryptErrorReport NOTIFICATION-TYPE
    OBJECTS
    ::= {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfRadioId,
                  capwapBaseNtfStationIdList capwapBaseParameters 8 }

capwapBaseAcWaitJoinTimer OBJECT-TYPE
    SYNTAX      Unsigned32 (20..4294967295)
    UNITS       "second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "This notification is generated when a WTP that
        "Represents the maximum time, in seconds, the AC will wait
         after the DTLS session has occurred
         decryption error since been established until it receives
         the last report." Join Request from the WTP. This timer MUST be greater
         than 20 seconds.
         The value of the object is persistent at restart/reboot."
    REFERENCE
        "Section 4.6.17. 4.7.16. of CAPWAP Protocol Specification, RFC xxx."
    ::= 5415."
    DEFVAL { capwapBaseNotifications 3 60 }

capwapBaseJoinFailure NOTIFICATION-TYPE
    OBJECTS
    ::= {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfJoinFailureReason capwapBaseParameters 9 }

capwapBaseAcEcnSupport OBJECT-TYPE
    SYNTAX      INTEGER {
                  limited(0),
                  fullAndLimited(1)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "This notification
        "Represents the support for the Explicit Congestion Notification
         (ECN) bits, as defined in [RFC3168].
         The value of the object is generated when a WTP fails to join." persistent at restart/reboot.
         The following enumerated values are supported:
           limited(0)        - Limited ECN support
           fullAndLimited(1) - Full and limited ECN support"
    REFERENCE
        "Section 4.6.35. 4.6.25. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifications capwapBaseParameters 10 }

-- End of CAPWAP Base Parameters Group

-- CAPWAP Statistics Group

capwapBaseStats OBJECT IDENTIFIER
    ::= { capwapBaseObjects 4 }

capwapBaseImageUpgradeFailure

capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of failed DTLS session establishment
         attempts due to authentication failures."
    REFERENCE
        "Section 4.8.3. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseStats 1 }

capwapBaseFailedDTLSSessionCount OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Represents the number of failed DTLS session
         establishment attempts."
    REFERENCE
        "Section 4.8.4. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseStats 2 }

-- Notifications

capwapBaseChannelUp NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfImageFailureReason
                  capwapBaseNtfChannelType,
                  capwapBaseNtfAuthenMethod
                }
    STATUS      current
    DESCRIPTION
        "This notification is generated sent by the AC when a WTP fails to update
         firmware image."
    REFERENCE
        "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." channel
         established.
         The notification is separated for data or control channel."
    ::= { capwapBaseNotifications 5 1 }

capwapBaseConfigMsgError

capwapBaseChannelDown NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfConfigMsgErrorType,
                  capwapBaseNtfMsgErrorElements
                  capwapBaseNtfChannelType,
                  capwapBaseNtfChannelDownReason
                }
    STATUS      current
    DESCRIPTION
        "This notification is generated when a WTP received message
         elements in sent by the configuration management messages which it was
         unable to apply locally."
    REFERENCE
        "Section 4.6.35. of AC when CAPWAP Protocol Specification, RFC xxx." channel
         becomes down.
         The notification is separated for data or control channel."
    ::= { capwapBaseNotifications 6 2 }

capwapBaseRadioOperableStatus

capwapBaseDecryptErrorReport NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfRadioId,
                  capwapBaseNtfRadioOperStatusFlag,
                  capwapBaseNtfRadioStatusCause
                  capwapBaseNtfStationIdList
                }
    STATUS      current
    DESCRIPTION
        "The
        "This notification is generated when a radio's operational state
         is changed." WTP that has occurred
         decryption error since the last report."
    REFERENCE
        "Section 4.6.34. 4.6.17. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifications 7 3 }

capwapBaseAuthenticationFailure

capwapBaseJoinFailure NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfChannelType,
                  capwapBaseNtfAuthenMethod,
                  capwapBaseNtfJoinFailureReason
                }
    STATUS      current
    DESCRIPTION
        "This notification is generated when a WTP fails to join."
    REFERENCE
        "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseNotifications 4 }

capwapBaseImageUpgradeFailure NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfImageFailureReason
                }
    STATUS      current
    DESCRIPTION
        "This notification is generated when a WTP fails to update
         the firmware image."
    REFERENCE
        "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseNotifications 5 }

capwapBaseConfigMsgError NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfConfigMsgErrorType,
                  capwapBaseNtfMsgErrorElements
                }
    STATUS      current
    DESCRIPTION
        "This notification is generated when a WTP receives message
         elements in the configuration management messages which it
         is unable to apply locally."
    REFERENCE
        "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseNotifications 6 }

capwapBaseRadioOperableStatus NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfRadioId,
                  capwapBaseNtfRadioOperStatusFlag,
                  capwapBaseNtfRadioStatusCause
                }
    STATUS      current
    DESCRIPTION
        "The notification is generated when a radio's operational state
         is changed."
    REFERENCE
        "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415."
    ::= { capwapBaseNotifications 7 }

capwapBaseAuthenticationFailure NOTIFICATION-TYPE
    OBJECTS     {
                  capwapBaseNtfWtpId,
                  capwapBaseNtfChannelType,
                  capwapBaseNtfAuthenMethod,
                  capwapBaseNtfAuthenFailureReason
                }
    STATUS      current
    DESCRIPTION
        "The notification will notify the notifies an authentication failure event,
         and provides the reason for it."
    ::= { capwapBaseNotifications 8 }

-- Objects used only in notifications

-- for notifications
capwapBaseNotifyVarObjects OBJECT IDENTIFIER
    ::= { capwapBaseObjects 5 }

capwapBaseNtfWtpId OBJECT-TYPE
    SYNTAX      CapwapBaseWtpIdTC
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the unique identifier of a WTP."
    ::= { capwapBaseNotifyVarObjects 1 }

capwapBaseNtfRadioId OBJECT-TYPE
    SYNTAX      CapwapBaseRadioIdTC
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the identifier of a PHY radio on a WTP, and which is
         only
         requires required to be unique on a WTP.
         For example, WTP A and WTP B will can use the same value of
         capwapBaseNtfRadioId for their first radio."
    REFERENCE
        "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 2 }

capwapBaseNtfChannelType OBJECT-TYPE
    SYNTAX      CapwapBaseChannelTypeTC
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the channel type for CAPWAP protocol."
    ::= { capwapBaseNotifyVarObjects 3 }

capwapBaseNtfAuthenMethod OBJECT-TYPE
    SYNTAX      CapwapBaseAuthenMethodTC
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents authentication method for CAPWAP Channel."
    ::= { capwapBaseNotifyVarObjects 4 }

capwapBaseNtfChannelDownReason OBJECT-TYPE
    SYNTAX      INTEGER {
                  timeout(1),
                  rekeyfailure(2),
                  acRebootWtp(3),
                  dtlsError(4),
                  maxRetransmit(5)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the reason for Channel down.
         The following enumerated values are supported:
           timeout(1)       - The keep alive is timeout
           rekeyfailure(2)  - Rekey process is failed, channel will be
                              broken
           acRebootWtp(3)   - The AC reboot WTP
           dtlsError(4)     - DTLS notifications: DTLSAborted,
                              DTLSReassemblyFailure, DTLSPeerDisconnect,
                              or frequent DTLSDecapFailure
           maxRetransmit(5) - The underlying reliable transport's
                              RetransmitCount counter has reached the
                              MaxRetransmit variable"
    ::= { capwapBaseNotifyVarObjects 5 }

capwapBaseNtfStationIdList OBJECT-TYPE
    SYNTAX      OCTET STRING
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the a list of station id which use semicolons to
         separate each station id." identifiers separated by
         semicolons."
    REFERENCE
        "Section 4.6.8. 4.6.17. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 6 }

capwapBaseNtfAuthenFailureReason OBJECT-TYPE
    SYNTAX      INTEGER {
                  keyMismatch(1),
                  invalidCA(2),
                  micError(3),
                  timeout(4),
                  invalidCert(2),
                  reassemblyFailure(3),
                  decapFailure(4),
                  encapFailure(5),
                  timeout(6),
                  unknown(8)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents reason for WTP authorization failure.
         The following enumerated values are supported:
           keyMismatch(1)       - WTP's and AC's key is are not matched
           invalidCA(2)
           invalidCert(2)       - ca Certification is not valid
           micError(3)
           reassemblyFailure(3) - Fragment reassembly failure
           decapFailure(4)      - Decapsulation error
           encapFailure(5)      - detect MIC Encapsulation error
           timeout(4)
           timeout(6)           - WaitDTLS Timer is timer timeout
           unknown(8)           - Unknown reason"
    REFERENCE
        "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 7 }

capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE
    SYNTAX      INTEGER {
                  operable(0),
                  inoperable(1)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the operation status of a radio.
         The following enumerated values are supported:
           operable(0)   - To indicate The radio is operable
           inoperable(1) - To indicate The radio is inoperable, and the
                           capwapBaseNtfRadioStatusCause object will
                           give
                           gives the reason in details"
    REFERENCE
        "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 8 }

capwapBaseNtfRadioStatusCause OBJECT-TYPE
    SYNTAX      INTEGER {
                  normal(0),
                  hwError(1),
                  swError(2),
                  adminSet(3)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the reason the why radio is out of service.
         The following enumerated values are supported:
           normal(0)   - Normal Status status
           hwError(1)  - Radio Failure failure
           swError(2)  - Software Failure failure
           adminSet(3) - Administratively Set" set"
    REFERENCE
        "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 9 }

capwapBaseNtfJoinFailureReason  OBJECT-TYPE
    SYNTAX      INTEGER {
                  unspecified(1),
                  resDepletion(2),
                  unknownSource(3),
                  incorrectData(4),
                  sessionIdInUse(5),
                  notSupportHw(6),
                  notSupportBinding(7)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the reason of join failure.
         The following enumerated values are supported:
           unspecified(1)       - unspecified Unspecified failure reason
           resDepletion(2)      - Resource Depletion depletion
           unknownSource(3)     - Unknown Source source
           incorrectData(4)     - Incorrect Data data
           sessionIdInUse(5)    - Session ID already in use
           notSupportHw(6)      - WTP Hardware hardware not supported
           notSupportBinding(7) - Binding Not Supported" not supported"
    REFERENCE
        "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 10 }

capwapBaseNtfImageFailureReason  OBJECT-TYPE
    SYNTAX      INTEGER {
                  invalidChecksum(1),
                  invalidLength(2),
                  other(3),
                  inStorage(4)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the reason of image failure.
         The following enumerated values are supported:
           invalidChecksum(1) - Invalid Checksum checksum
           invalidLength(2)   - Invalid Data Length data length
           other(3)           - Other Error error
           inStorage(4)       - Image Already Present" already present"
    REFERENCE
        "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 11 }

capwapBaseNtfConfigMsgErrorType  OBJECT-TYPE
    SYNTAX      INTEGER {
                  unknownElement(1),
                  unsupportedElement(2),
                  unknownValue(3),
                  unsupportedValue(4)
                }
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the type of configuration message error.
         The following enumerated values are supported:
           unknownElement(1)     - Unknown Message Element message element
           unsupportedElement(2) - Unsupported Message Element message element
           unknownValue(3)       - Unknown Message Element Value message element value
           unsupportedValue(4)   - Unsupported Message Element Value" message element value"
    REFERENCE
        "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 5415."
   ::= { capwapBaseNotifyVarObjects 12 }

capwapBaseNtfMsgErrorElements  OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "Represents the message elements sent by the AC in the
         Configuration Status Response message that caused the error."
    REFERENCE
        "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 5415."
    ::= { capwapBaseNotifyVarObjects 13 }

-- Module compliance

capwapBaseCompliances OBJECT IDENTIFIER
    ::= { capwapBaseConformance 1 }

capwapBaseGroups OBJECT IDENTIFIER
    ::= { capwapBaseConformance 2 }

capwapBaseCompliance MODULE-COMPLIANCE
   STATUS current
   DESCRIPTION
       "Describes the requirements for conformance to the
        CAPWAP-BASE-MIB module."

   MODULE -- this module
     MANDATORY-GROUPS {
       capwapBaseAcNodeGroup,
       capwapBaseWtpProfileGroup,
       capwapBaseWtpStateGroup,
       capwapBaseWtpsGroup,
       capwapBaseRadiosGroup,
       capwapBaseStationsGroup
       capwapBaseWtpGroup,
       capwapBaseRadioGroup,
       capwapBaseStationGroup
     }

     GROUP capwapBaseAcNodeGroup2
     DESCRIPTION
         "The capwapBaseAcNodeGroup2 group is optional."

     GROUP capwapBaseAcNameListGroup
     DESCRIPTION
         "The capwapBaseAcNameListGroup group is optional."

     GROUP capwapBaseMacAclsGroup
     DESCRIPTION
         "The capwapBaseMacAclsGroup group is optional."

     GROUP capwapBaseWtpsGroup2 capwapBaseWtpProfileGroup2
     DESCRIPTION
         "The capwapBaseWtpsGroup2 capwapBaseWtpProfileGroup2 group is optional."

     GROUP capwapBaseWtpGroup2
     DESCRIPTION
         "The capwapBaseWtpGroup2 group is optional."

     GROUP capwapBaseWtpEventsStatsGroup
     DESCRIPTION
         "The capwapBaseWtpEventsStatsGroup group is optional."

     GROUP capwapBaseRadioEventsStatsGroup
     DESCRIPTION
         "The capwapBaseRadioEventsStatsGroup group is optional."

     GROUP capwapBaseParametersGroup
     DESCRIPTION
         "The capwapBaseParametersGroup group is optional."

     GROUP capwapBaseStatsGroup
     DESCRIPTION
         "The capwapBaseStatsGroup group is optional."

     GROUP capwapBaseNotificationGroup capwapBaseNotificationsGroup
     DESCRIPTION
          "The capwapBaseNotificationsGroup group capwapBaseNotificationGroup is optional."

     GROUP capwapBaseNotifyVarGroup capwapBaseNotifyVarsGroup
     DESCRIPTION
         "The capwapBaseNotifyVarGroup capwapBaseNotifyVarsGroup group is optional.
          If capwapBaseNotificationGroup capwapBaseNotificationsGroup is supported,
          this group must be implemented."
     ::= { capwapBaseCompliances 1 }

capwapBaseAcNodeGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpSessions,
      capwapBaseWtpSessionsLimit,
      capwapBaseStationSessions,
      capwapBaseStationSessionsLimit
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to represent
         the basic properties for the AC from the CAPWAP
         protocol perspective."
    ::= { capwapBaseGroups 1 }

capwapBaseAcNodeGroup2   OBJECT-GROUP
    OBJECTS {
      capwapBaseDataChannelDTLSPolicyOptions,
      capwapBaseDataChannelDTLSPolicyConfig,
      capwapBaseControlChannelAuthenOptions,
      capwapBaseControlChannelAuthenConfig
     }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to represent
         the other properties such as security for the AC from
         the CAPWAP protocol perspective."
    ::= { capwapBaseGroups 2 }

capwapBaseAcNameListGroup  OBJECT-GROUP
    OBJECTS {
      capwapBaseAcNameListName,
      capwapBaseAcNameListPriority,
      capwapBaseAcNameListRowStatus
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to configure
         the AC name list."
    ::= { capwapBaseGroups 3 }

capwapBaseMacAclsGroup  OBJECT-GROUP
    OBJECTS {
      capwapBaseMacAclStationId,
      capwapBaseMacAclRowStatus
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to configure
         the stations ACL."
    ::= { capwapBaseGroups 4 }

capwapBaseWtpStateGroup

capwapBaseWtpProfileGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpStateWtpIpAddressType,
      capwapBaseWtpProfileName,
      capwapBaseWtpProfileWTPSerialId,
      capwapBaseWtpProfileWTPModelNumber,
      capwapBaseWtpProfileWtpName,
      capwapBaseWtpProfileWtpLocation,
      capwapBaseWtpProfileRowStatus
    }
    STATUS  current
    DESCRIPTION
        "A collection of objects which are used to configure
         the WTP profile."
    ::= { capwapBaseGroups 5 }

capwapBaseWtpProfileGroup2    OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpProfileWtpStaticIpEnable,
      capwapBaseWtpProfileWtpStaticIpType,
      capwapBaseWtpProfileWtpStaticIp,
      capwapBaseWtpProfileWtpNetmask,
      capwapBaseWtpProfileWtpGateway,
      capwapBaseWtpProfileWtpFallbackEnable,
      capwapBaseWtpProfileWtpEchoInterval,
      capwapBaseWtpProfileWtpIdleTimeout,
      capwapBaseWtpProfileWtpMaxDiscoveryInterval,
      capwapBaseWtpProfileWtpReportInterval,
      capwapBaseWtpProfileWtpSilentInterval,
      capwapBaseWtpProfileWtpStatisticsTimer,
      capwapBaseWtpProfileWtpWaitDTLSTimer,
      capwapBaseWtpProfileWtpEcnSupport
    }
    STATUS  current
    DESCRIPTION
        "A collection of optional objects which are used to
         configure the WTP profile."
    ::= { capwapBaseGroups 6 }

capwapBaseWtpStateGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpStateWtpIpAddressType,
      capwapBaseWtpStateWtpIpAddress,
      capwapBaseWtpStateWtpPhyAddress,
      capwapBaseWtpState
      capwapBaseWtpStateWtpBaseMacAddress,
      capwapBaseWtpState,
      capwapBaseWtpStateWtpCurrWtpProfileId
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to represent
         WTP
         the WTP's state information."
    ::= { capwapBaseGroups 5 7 }

capwapBaseWtpsGroup

capwapBaseWtpGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpName,
      capwapBaseWtpLocation,
      capwapBaseWtpBaseMacAddress,
      capwapBaseWtpTunnelModeOptions,
      capwapBaseWtpMacTypeOptions,
      capwapBaseWtpDiscoveryType,
      capwapBaseWtpRadiosInUseNum,
      capwapBaseWtpRadioNumLimit,
      capwapBaseWtpEcnSupport
      capwapBaseWtpRadioNumLimit
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to represent
         configuration and
         the properties information for WTP the WTPs in running state."
    ::= { capwapBaseGroups 6 8 }

capwapBaseWtpsGroup2

capwapBaseWtpGroup2   OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpPhyIndex,
      capwapBaseWtpDiscoveryType,
      capwapBaseWtpStaticIpEnable,
      capwapBaseWtpStaticIpType,
      capwapBaseWtpStaticIp,
      capwapBaseWtpNetmask,
      capwapBaseWtpGateway,
      capwapBaseWtpFallbackEnable,
      capwapBaseWtpRetransmitCount,
      capwapBaseWtpMaxDiscoveries,
      capwapBaseWtpMaxFailedDTLSSessionRetry,
      capwapBaseWtpMaxRetransmit,
      capwapBaseWtpDataChannelKeepAliveTimer,
      capwapBaseWtpDataChannelDeadInterval,
      capwapBaseWtpDiscoveryInterval,
      capwapBaseWtpDTLSSessionDeleteTimer,
      capwapBaseWtpEchoInterval,
      capwapBaseWtpIdleTimeout,
      capwapBaseWtpImageDataStartTimer,
      capwapBaseWtpMaxDiscoveryInterval,
      capwapBaseWtpReportInterval,
      capwapBaseWtpRetransmitInterval,
      capwapBaseWtpSilentInterval,
      capwapBaseWtpStatisticsTimer,
      capwapBaseWtpWaitDTLSTimer
      capwapBaseWtpRetransmitInterval
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of optional objects which are used to represent
         configuration and
         the properties information for WTP the WTPs in running state."
    ::= { capwapBaseGroups 7 9 }

capwapBaseRadiosGroup

capwapBaseRadioGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseWirelessBindingVirtualRadioIfIndex,
      capwapBaseWirelessBindingType
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to represent
         the wireless binding type, the mapping relationship mappings between
         'WLAN the
         ifIndexes of WLAN Virtual Radio Interface' Interfaces and PHY radio." radios."
    ::= { capwapBaseGroups 8 10 }

capwapBaseStationsGroup

capwapBaseStationGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseStationAddedTime,
      capwapBaseStationVlanName
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used to represent
         the stations' basic property." properties."
    ::= { capwapBaseGroups 9 11 }

capwapBaseWtpEventsStatsGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseWtpEventsStatsRebootCount,
      capwapBaseWtpEventsStatsInitCount,
      capwapBaseWtpEventsStatsLinkFailureCount,
      capwapBaseWtpEventsStatsSwFailureCount,
      capwapBaseWtpEventsStatsHwFailureCount,
      capwapBaseWtpEventsStatsOtherFailureCount,
      capwapBaseWtpEventsStatsUnknownFailureCount,
      capwapBaseWtpEventsStatsLastFailureType
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used for collecting
         WTP reboot count, link failure count, hardware failure
         count and so on."
    ::= { capwapBaseGroups 10 12 }

capwapBaseRadioEventsStatsGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseRadioEventsStatsResetCount,
      capwapBaseRadioEventsStatsSwFailCount,
      capwapBaseRadioEventsStatsHwFailCount,
      capwapBaseRadioEventsStatsOtherFailCount,
      capwapBaseRadioEventsStatsUnknownFailCount,
      capwapBaseRadioEventsStatsConfigUpdateCount,
      capwapBaseRadioEventsStatsChannelChangeCount,
      capwapBaseRadioEventsStatsBandChangeCount,
      capwapBaseRadioEventsStatsCurrentNoiseFloor,
      capwapBaseRadioEventsStatsDecryptErrorCount,
      capwapBaseRadioEventsStatsLastFailType
    }
    STATUS  current
    DESCRIPTION
        "The
        "A collection of objects which are used for collecting
         radio reset count, channel change count, hardware failure
         count and so on"
    ::= { capwapBaseGroups 11 13 }

capwapBaseParametersGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseAcMaxRetransmit,
      capwapBaseAcChangeStatePendingTimer,
      capwapBaseAcDataCheckTimer,
      capwapBaseAcDTLSSessionDeleteTimer,
      capwapBaseAcEchoInterval,
      capwapBaseAcRetransmitInterval,
      capwapBaseAcSilentInterval,
      capwapBaseAcWaitDTLSTimer,
      capwapBaseAcWaitJoinTimer,
      capwapBaseAcEcnSupport
    }
    STATUS  current
    DESCRIPTION
        "Objects used for the CAPWAP protocol." protocol's parameters."
    ::= { capwapBaseGroups 12 14 }

capwapBaseStatsGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseFailedDTLSAuthFailCount,
      capwapBaseFailedDTLSSessionCount
    }
    STATUS  current
    DESCRIPTION
        "Objects used for collecting the CAPWAP protocol." protocol's statistic."
    ::= { capwapBaseGroups 13 15 }

capwapBaseNotificationGroup

capwapBaseNotificationsGroup    NOTIFICATION-GROUP
    NOTIFICATIONS {
      capwapBaseChannelUp,
      capwapBaseChannelDown,
      capwapBaseDecryptErrorReport,
      capwapBaseJoinFailure,
      capwapBaseImageUpgradeFailure,
      capwapBaseConfigMsgError,
      capwapBaseRadioOperableStatus,
      capwapBaseAuthenticationFailure
    }
    STATUS  current
    DESCRIPTION
        "The Collection
        "A collection of notifications in this MIB module."
    ::= { capwapBaseGroups 14 16 }

capwapBaseNotifyVarGroup

capwapBaseNotifyVarsGroup    OBJECT-GROUP
    OBJECTS {
      capwapBaseNtfWtpId,
      capwapBaseNtfRadioId,
      capwapBaseNtfChannelType,
      capwapBaseNtfAuthenMethod,
      capwapBaseNtfChannelDownReason,
      capwapBaseNtfStationIdList,
      capwapBaseNtfAuthenFailureReason,
      capwapBaseNtfRadioOperStatusFlag,
      capwapBaseNtfRadioStatusCause,
      capwapBaseNtfJoinFailureReason,
      capwapBaseNtfImageFailureReason,
      capwapBaseNtfConfigMsgErrorType,
      capwapBaseNtfMsgErrorElements
    }
    STATUS  current
    DESCRIPTION
        "Objects used for notification." notifications."
    ::= { capwapBaseGroups 15 17 }

END

11.  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 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:

   - Unauthorized changes to the capwapBaseWtpTable, capwapBaseWtProfileTable, and writable
   objects under capwapBaseAcs group may MAY disrupt allocation of resources
   in the network.  For example, a WTP's static IP address could be
   changed by set capwapBaseWtpStaticIp capwapBaseWtpProfileWtpStaticIp object.

   - Unauthorized changes to writable objects under the capwapBaseAc
   group, it may MAY disrupt allocation of resources in the network.  For
   example, a invalid value for capwapBaseWtpSessionsLimit object will
   increase the AC's traffic burden.  Also, some objects such as
   capwapBaseDataChannelDTLSPolicyConfig may MAY cause network unsafe.

   - Unauthorized changes to the capwapBaseMacAclTable, it may MAY cause
   legal stations could not unable to access the network any more while illegal
   stations have chance to access the network.

   - Unauthorized changes to writable objects under the
   capwapBaseParameters group, it may MAY influence CAPWAP protocol
   behaviour and status.  For example, the an invalid value set for the
   capwapBaseAcDataCheckTimer may MAY influence the CAPWAP state machine.

   Some of the readable objects in this MIB module (i.e., objects with a
   MAX-ACCESS other than not-accessible) may MAY be considered sensitive or
   vulnerable in some network environments.  It is thus important to
   control even GET and/or NOTIFY access to these objects and possibly
   to even encrypt the values of these objects when sending them over
   the network via SNMP.  The followings are the tables and objects and
   their sensitivity/vulnerability:

   - The capwapBaseDataChannelDTLSPolicyOptions and
   capwapBaseControlChannelAuthenOptions under the capwapBaseAc group
   exposes the current security option for CAPWAP data and control
   channel.
   channels.

   - The capwapBaseWtpTable exposes a WTP's important information like IP
   address,
   tunnel mode, MAC type and so on.

   - The capwapBaseWtpEventsStatsTable exposes a WTP's failure
   information.

   - The capwapBaseRadioEventsStatsTable exposes a radio's failure
   information.

   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, the 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.

12.  IANA Considerations

12.1.  IANA Considerations for CAPWAP-BASE-MIB module Module

        The MIB module in this document uses the following IANA-assigned
        OBJECT IDENTIFIER values recorded in the SMI Numbers registry:

        Descriptor        OBJECT IDENTIFIER value
        ----------        -----------------------

        capwapBaseMIB  { mib-2 XXX }

12.2.  IANA Considerations for ifType

   Require IANA to assign a ifType for 'WTP the WTP Virtual Radio Interface'
   type. Interface.

13.  Contributors

   This MIB module is based on contributions from Long Gao.

14.  Acknowledgements

   The authors wish to thank David Harrington, Fei Fang, Xuebin Zhu, Hao
   Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao Zhang.

15.  References

15.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 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.

   [RFC3411]                       Harrington, D., Presuhn, R., and B.
                                   Wijnen, "An Architecture for
                                   Describing Simple Network Management
                                   Protocol (SNMP) Management
                                   Frameworks", STD 62, RFC 3411,
                                   December 2002.

   [RFC3418]                       Presuhn, R., "Management Information
                                   Base (MIB) for the Simple Network
                                   Management Protocol (SNMP)", STD 62,
                                   RFC 3418, December 2002.

   [RFC4001]                       Daniele, M., Haberman, B., Routhier,
                                   S., and J. Schoenwaelder, "Textual
                                   Conventions for Internet Network
                                   Addresses", RFC 4001, February 2005.

   [RFC4133]                       Bierman, A. and K. McCloghrie,
                                   "Entity MIB (Version 3)", RFC 4133,
                                   August 2005.

   [I-D.ietf-capwap-protocol-specification]

   [RFC5415]                       Calhoun, P., Montemurro, M.,
                                                 Stanley, D., and P.
                                                 Calhoun, "CAPWAP D.

                                   Stanley, "Control And Provisioning of
                                   Wireless Access Points (CAPWAP)
                                   Protocol Specification", draft-
                                                 ietf-capwap-protocol-
                                                 specification-15 (work
                                                 in progress),
                                                 November 2008. RFC 5415,
                                   March 2009.

15.2.  Informative References

   [IEEE.802-11.2007]              "Information technology -
                                   Telecommunications and information
                                   exchange between systems - Local and
                                   metropolitan area networks - Specific
                                   requirements - Part 11: Wireless LAN
                                   Medium Access Control (MAC) and
                                   Physical Layer (PHY) specifications",
                                   IEEE Standard 802.11, 2007, <http://
                                   standards.ieee.org/getieee802/
                                   download/802.11-2007.pdf>.

   [RFC3168]                       Ramakrishnan, K., Floyd, S., and D.
                                   Black, "The Addition of Explicit
                                   Congestion Notification (ECN) to IP",
                                   RFC 3168, September 2001.

   [RFC3410]                       Case, J., Mundy, R., Partain, D., and
                                   B. Stewart, "Introduction and
                                   Applicability Statements for
                                   Internet-Standard Management
                                   Framework", RFC 3410, December 2002.

   [RFC4118]                       Yang, L., Zerfos, P., and E. Sadot,
                                   "Architecture Taxonomy for Control
                                   and Provisioning of Wireless Access
                                   Points (CAPWAP)", RFC 4118,
                                   June 2005.

   [RFC4347]                       Rescorla, E. and N. Modadugu,
                                   "Datagram Transport Layer Security",
                                   RFC 4347, April 2006.

   [IEEE.802-11.2007]                            "Information technology
                                                 - Telecommunications

   [RFC5416]                       Calhoun, P., Montemurro, M., and information
                                                 exchange between
                                                 systems - Local D.
                                   Stanley, "Control and
                                                 metropolitan area
                                                 networks - Specific
                                                 requirements - Part 11: Provisioning of
                                   Wireless LAN Medium Access Control (MAC)
                                                 and Physical Layer
                                                 (PHY) specifications",
                                                 IEEE Standard 802.11,
                                                 2007, <http://
                                                 standards.ieee.org/
                                                 getieee802/download/
                                                 802.11-2007.pdf>.

   [I-D.ietf-capwap-protocol-binding-ieee80211]  Montemurro, M.,
                                                 Stanley, D., and P.
                                                 Calhoun, "CAPWAP Points (CAPWAP)
                                   Protocol Binding for IEEE 802.11", draft-
                                                 ietf-capwap-protocol-
                                                 binding-ieee80211-12
                                                 (work in progress),
                                                 November 2008.
                                   RFC 5416, March 2009.

   [I-D.ietf-capwap-802dot11-mib]  Shi, Y., Perkins, D., Elliott, C.,
                                   and Y. Zhang, "CAPWAP Protocol
                                   Binding MIB for IEEE 802.11", draft-ietf-
                                                 capwap-802dot11-mib-02
                                   (work in progress), October 2008.

Appendix A.  Appendix A. Changes between -04 -05 and -03

 T1. Running smilint results in the following errors:
 mibs/CAPWAP-BASE-MIB:480: [5] {index-exceeds-too-large} warning: index
 of row `capwapBaseWtpStateEntry' can exceed OID size limit by 6
 subidentifier(s)
 mibs/CAPWAP-BASE-MIB:582: [5] {index-exceeds-too-large} warning: index
 of row `capwapBaseWtpEntry' can exceed OID size limit by 6
 subidentifier(s)
 mibs/CAPWAP-BASE-MIB:1090: [5] {index-exceeds-too-large} warning: index
 of row `capwapBaseRadioBindEntry' can exceed OID size limit by 7
 subidentifier(s)
 mibs/CAPWAP-BASE-MIB:1181: [5] {index-exceeds-too-large} warning: index
 of row `capwapBaseStationEntry' can exceed OID size limit by 13
 subidentifier(s)
 mibs/CAPWAP-BASE-MIB:1249: [5] {index-exceeds-too-large} warning: index
 of row `capwapBaseWtpRebootStatsEntry' can exceed OID size limit by 6
 subidentifier(s)
 mibs/CAPWAP-BASE-MIB:1408: [5] {index-exceeds-too-large} warning: index
 of row `capwapBaseRadioStatsEntry' can exceed OID size limit by 7
 subidentifier(s)

 The reason is that these tables are indexed with objects of SYNTAX of
 CapwapBaseWtpIdTC which has a maximal size of 128, equal to the maximal
 size allowed for the whole OID. Reducing the maximal size of -04

   1) To close the TC issue 68 "Suggest Let Base MIB to
 anything less or equal than 115 solves the problem. Support a WTP
   Profile"

   --------------------------------------------------------------

   Refer to entPhysicalSerialNum in RFC4133 and Dan's comment, define
   CapwapBaseWtpIdTC with OCTET STRING (SIZE (0..32))

   IF we use SnmpAdminString (SIZE (0..32)), libsmi would generate
   error: textual convention `CapwapBaseWtpIdTC' can not be derived from
   the textual convention `SnmpAdminString'

   T2.  Section 5 - ' To reuse current MIB standards and future
   extensions for

   Add a wireless binding technology' - it is not clear what
   'future extensions' may be and I would not commit to using them in
   advance, so I would suggest to drop this

   -------------------------------------------------------------

   Change it into " To be independent of any wireless technologies and
   have ability to reuse wireless binding MIB modules defined by other
   SDOs;"

   T3 What are new section 5.7.  WTP Profile, update the 'MIB standards of other SDOs' that need to be reused?
   Please refer to them specifically at least by providing one example -
   for instance where does Dot11OperationTable come from?

   --------------------------------------------------------------

   It is changed into:

   The text give section 8, add a definition new
   table of " 5.2.  Wireless Binding MIB Modules"

   For Dot11OperationTable, the chang is:

   For example, capwapBaseWtpProfileTable and update the related MIB tables such as Dot11OperationTable [IEEE.802-
   11.2007] are able to support WTP radio configuration.

   T4.  In order for ifIndex to be used as a common handler for the
   CAPWAP MIB and for the interface specific MIB modules like a dot11
   MIB from IEEE one needs to ensure that the same numbering scheme and
   mapping is used by all MIB modules, and that it behaves identically
   for events like interface card swapping, reset or power loss.  I do
   not see how this can happen, I am not sure that this is possible at
   all, and in any case there is no text in the CAPWAP MIB that explains
   this mechanism.

   --------------------------------------------------------------

   in the Capwap Digest, Vol 39, Issue 4, we gave the text to explain a
   mechanism that preserves the values of ifIndex, Request mailing list
   to confirm it.

   In the section of "Relationship to the IF-MIB", add text "Also, as
   ifIndex[RFC2863] will be used as common handler for corresponding
   interfaces in the CAPWAP-BASE-MIB and specific wireless technologies
   MIB modules, the system (AC) MUST have a mechanisms that preserves
   the values of ifIndex in the ifTable at AC reboot."

   T5.  Section 7.2 - 'The interface SHOULD be modeled as an ifEntry' -
   Is a SHOULD enough or rather a MUST is required here taking into
   account the requirements in Section 5.

   -----------------------------------------------------------------

   It is changed into:MUST be

   T6.  The documents that define the MIB modules required for IMPORTs
   must be listed in the Normative References section.

   -----------------------------------------------------------------
   add reference to RFC3411 in the section of "MIB modules required for
   IMPORTS", add "SNMP-FRAMEWORK-MIB [RFC3411],"

   T7.  In the example in Section 8 capwapBaseWtpId equals the
   representation of the OCTET STRING '12345678' and not the number
   12345678

   ----------------------------------------------------------------

   Yes, it is change into '12345678'

   T8.  In the example in Section 8 ifPhysicalAddress should have six
   zeros.

   -----------------------------------------------------------------

   Yes, it is change into '000000'

   T9.  What is the Vendor Identifier mentioned in Section 9 as being
   assigned by IANA?  Is this something specific for this MIB document -
   in this case it needs to be mentioned in the IANA considerations
   section?

   -----------------------------------------------------------------

   The description of Vendor Identifie is changed into: Vendor
   Identifier: A 32-bit value containing the IANA assigned "SMI Network
   Management Private Enterprise Codes"

   T10.  Why does one need a special TC for CapwapBaseWtpIdTC?  If this
   is typically a serial number, then SnmpAdminString SIZE (1..128)
   should do.

   -----------------------------------------------------------------

   Station, radio, WTP are main objects to management by MIB drafts.
   They would appear in the serval table and notification.  Suggest to
   have a TC for them.

   T11.  In any case why is the SIZE in this TC fixed at 128?
   -----------------------------------------------------------------

   Refer to entPhysicalSerialNum in RFC4133 and Dan's comment, define
   CapwapBaseWtpIdTC with OCTET STRING (SIZE (0..32))

   T12.  A number of read-write objects do not have the persistency
   behavior defined in case of agent reboot -
   capwapBaseStationSessionsLimit, capwapBaseDataChannelSecConfig,
   capwapBaseControlChannelAuthenConfig

   -----------------------------------------------------------------

   Add the "The value of the object is persistent at restart/reboot." in
   the description of
   capwapBaseAcMaxRetransmit,capwapBaseAcChangeStatePendingTimer, capwap
   BaseAcDataCheckTimer,capwapBaseAcDTLSSessionDeleteTimer,capwapBaseAcE
   choInterval, capwapBaseAcWaitJoinTimer,
   capwapBaseAcWaitDTLSTimer,capwapBaseAcSilentInterval,
   capwapBaseAcRetransmitInterval

   T13 - Is more than one security policy possible to be configured on a
   given AC?  If not, then why is capwapBaseDataChannelSecConfig a BIT?

   -----------------------------------------------------------------

   Yes, the data type of capwapBaseDataChannelSecConfig should be
   INTEGER

   T14 - the name of capwapBaseDataChannelSecOptions should better be
   something that includes DTLSPolicy to make clear to what fields in
   the AC Descriptor it corresponds.  The DESCRIPTION should also be
   consistent with the text in the protocol document

   -----------------------------------------------------------------

   To make it consistent with protocol, change
   capwapBaseDataChannelSecOptions with
   capwapBaseDataChannelDTLSPolicyOptions.  Change
   capwapBaseDataChannelSecConfig with
   capwapBaseDataChannelDTLSPolicyConfig Also, the DESCRIPTION should
   also be consistent with the text in the protocol document

   T15 - is more than one credential type possible to be configured on a
   given AC?  If not then why is capwapBaseControlChannelAuthenConfig a
   BIT?
   -----------------------------------------------------------------

   Yes, the data type of capwapBaseControlChannelSecConfig should be
   INTEGER

   T16 - it would be good for management applications writers to mention
   in the DESCRIPTION clause thatcapwapBaseAcnameListName is expected to
   be a UTF-8 encoded string

   -----------------------------------------------------------------
   Yes, it is added

   T17 - Object names in capwapBaseWtpStateTable do not respect the
   naming conditions relative to capwapBaseWtpStateEntry

   ---------------------------------------------------------------

   Add one more WtpState in the object name.  For example,
   capwapBaseWtpId is to changed into capwapBaseWtpStateWtpId, other
   objects are similiar.

   all objects with new name:

   CapwapBaseWtpStateEntry ::= SEQUENCE {
         capwapBaseWtpStateWtpId               CapwapBaseWtpIdTC,
         capwapBaseWtpStateWtpIpAddressType    InetAddressType,
         capwapBaseWtpStateWtpIpAddress        InetAddress,
         capwapBaseWtpStateWtpPhyAddress       PhysAddress,
         capwapBaseWtpState                    INTEGER
       }

   T18 - same for capwapBaseWtpStateTable

   -----------------------------------------------------------------

   Same as above

   T19 - capwapBaseWtpName is of SYNTAX AsnmpAdminString which is
   limited to SIZE 255, while the WTP name can be up to 512 characters

   --------------------------------------------------------------

   change with OCTET STRING(SIZE(512))

   T20 - same about capwapbaseWtpLocation which can be up to 1024
   characters in length

   -----------------------------------------------------------------

   change with OCTET STRING(SIZE(1024))

   T21 - Section 4.8 defines default value for a number of variables.
   However, these are not reflected in the MIB - for example why is
   there not a DEFAULT clause that will set capwapBaseWtpFallbackEnable
   to enabled(1) as per 4.8.9?  Or capwapBaseWtpMaxDiscoveries which has
   a default of 10 defined in 4.8.5

   -------------------------------------------------------------------
   Added DEFVAL { enabled } for capwapBaseWtpFallbackEnable.
   capwapBaseWtpMaxDiscoveries already has DEFVAL { 10 }.

   T22 - why does the MIB support reserved(0) for
   capwapBaseWtpFallbackEnable.  Does setting to reserved(0) by the
   management application have any significance?

   -----------------------------------------------------------------

   The reserved(0) is removed for capwapBaseWtpFallbackEnable

   T23 - According to 4.8.8 capwapBaseWtpRetransmitCount is a monotonous
   increasing counter.  The appropriate SYNTAX for such an object is
   Counter32 and not Unsigned32

   -----------------------------------------------------------------

   Yes, capwapBaseWtpRetransmitCount should use Counter32

   T24 - it would be useful to define UNITS clauses for objects like
   capwapBaseWtpRetransmitCount

   -----------------------------------------------------------------

   It seemed capwapBaseWtpRetransmitCount does not require a UNIT.

   T25 - define a range (2..180) for capwapBaseWtpMaxDiscoveryInterval

   ----------------------------------------------------------------

   add value scope of (0..24) to capwapBaseWtpDataChannelDeadInterval
   add value scope of (2..180) to capwapBaseWtpMaxDiscoveryInterval
   add value scope of (30..4294967295) to capwapBaseWtpWaitDTLSTimer
   add value scope of (30..4294967295) to capwapBaseAcWaitDTLSTimer
   add value scope of (20..4294967295) to capwapBaseAcWaitJoinTimer

   T27 - Object names in capwapBaseRadioBindTable do not respect the
   naming conditions relative to capwapBaseRadioBindEntry

   --------------------------------------------------------------------

   Change all objects (entry, table)'s prefix from capwapBaseRadioBind
   to capwapBaseWirelessBinding.

   change CapwapBaseRadioBindTable to CapwapBaseWirelessBindingTable

   The Objects with new name:

CapwapBaseWirelessBindingEntry ::= SEQUENCE {
    capwapBaseWirelessBindingRadioId                CapwapBaseRadioIdTC,
    capwapBaseWirelessBindingVirtualRadioIfIndex    InterfaceIndex,
    capwapBaseWirelessBindingType                   INTEGER
  }

   T28 - What do the values reserved(0) and reserved(2) in
   capwapBaseRadioWirelessBinding mean?  Are they ever returned by an
   agent?

   -----------------------------------------------------------------

   removed the reserved(0) and reserved(2) from the object definition.

   T29 - in other IETF documents (like RFC 4363) VLAN names are defined
   as SnmpAdminString (SIZE (0..32)).  I suggest the same for
   capwapBaseStationVlanName.  I am aware that section 4.6.8 allows for
   names up to 512, but I do not find this justified.  In any case, if
   the full size defined in 4.6.8 is to be accommodated, then
   SnmpAdminString would not be sufficient as its size is limited to
   256.

   -----------------------------------------------------------------

   capwapBaseStationVlanName use SnmpAdminString (SIZE (0..32))

   T30 - Object names in capwapBaseWtpRebootStatsTable do not respect
   the naming conditions relative to capwapBaseWtpRebootStatsEntry

   ------------------------------------------------------------------

   Change table name from capwapBaseWtpRebootStatTable to
   capwapBaseWtpEventsStatsTable.

   The objects also do similar changes, for example, change
   capwapBaseWtpRebootCount to capwapBaseWtpEventsStatsRebootCount

   The objects with new name:

   CapwapBaseWtpEventsStatsEntry ::= SEQUENCE {
         capwapBaseWtpEventsStatsRebootCount            Counter32,
         capwapBaseWtpEventsStatsInitCount              Counter32,
         capwapBaseWtpEventsStatsLinkFailureCount       Counter32,
         capwapBaseWtpEventsStatsSwFailureCount         Counter32,
         capwapBaseWtpEventsStatsHwFailureCount         Counter32,
         capwapBaseWtpEventsStatsOtherFailureCount      Counter32,
         capwapBaseWtpEventsStatsUnknownFailureCount    Counter32,
         capwapBaseWtpEventsStatsLastFailureType        INTEGER
       }

   T31 - Object names in capwapBaseWtpRadioStatsTable do not respect the
   naming conditions relative to capwapBaseWtpRadioStatsEntry

   ----------------------------------------------------------------

   Change table name from capwapBaseWtpRadioStatsTable to
   capwapBaseRadioEventsStatsTable.  The objects also do similar
   changes, for example, change capwapBaseRadioSwFailCount to
   capwapBaseRadioEventsStatsSwFailCount.

   The objects with new name:

   CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
         capwapBaseRadioEventsStatsResetCount            Counter32,
         capwapBaseRadioEventsStatsSwFailCount           Counter32,
         capwapBaseRadioEventsStatsHwFailCount           Counter32,
         capwapBaseRadioEventsStatsOtherFailCount        Counter32,
         capwapBaseRadioEventsStatsUnknownFailCount      Counter32,
         capwapBaseRadioEventsStatsConfigUpdateCount     Counter32,
         capwapBaseRadioEventsStatsChannelChangeCount    Counter32,
         capwapBaseRadioEventsStatsBandChangeCount       Counter32,
         capwapBaseRadioEventsStatsCurrentNoiseFloor     Integer32,
         capwapBaseRadioEventsStatsDecryptErrorCount     Counter32,
         capwapBaseRadioEventsStatsLastFailType          INTEGER
       }

   E1.  Even if this document uses terminology borrowed from other
   CAPWAP documents, acronyms like WTP, AC, etc. should be expanded at
   the first occurrence.

   -----------------------------------------------------------------

   The Terminology section is updated with more Terminology such as
   Autonomous WLAN Architecture, Centralized WLAN Architecture, Wireless
   Binding,Split and Local MAC and so on.

   E2.  It would be good for the document to be grammar and spelling
   checked by a native English speaker.

   E3.  No need for sections 6.1, 6.2, 6.3 - these are standard in any
   MIB module and their content is well known

   -----------------------------------------------------------------

   Ok, there are removed
   E4.  In Section 7.2 there is no need to mention information that is
   not specific to the CAPWAP MIB

   --------------------------------------------------------------------

   Removed the "Some specific interpretations of ifTable for CAPWAP-
   BASE-MIB are as follow." and the interpretations followed it.

   E5.  In the example in Section 8 ifType should be equal with the
   value assigned by IANA for the ifType - you may mark it xxx and enter
   an editor note saying 'RFC Editor - please replace xxx with the value
   allocated by IANA for IANAifType of 'WTP Virtual Radio Interface')

   -----------------------------------------------------------------

   It is done according to the comment

   E6.  Please indicate specifically for each field for the protocols
   timers message the exact reference in than CAPWAP protocol document.

   -----------------------------------------------------------------

   The section was updated according to protocol

   E7.  The numbering of referred paragraphs in the REFERENCE clauses
   are not synchronized with the latest version of the CAPWAP protocol
   document as per http://www.rfc-editor.org/rfc/rfc3411.txt

   -------------------------------------------------------------------

   The REFERENCE clauses for the following TCs or objects are changed
   with new id:

   CapwapBaseTunnelModeTC
   Section 4.6.42 to Section 4.6.43

   CapwapBaseMacTypeTC
   Section 4.6.43 to Section 4.6.44

   capwapBaseWtpName
   Section 4.6.44 to Section 4.6.45

   capwapBaseWtpLocation
   Section 4.6.29 to Section 4.6.30

   capwapBaseWtpBaseMacAddress
   Section 4.6.39 to Section 4.6.40
   capwapBaseTunnelModeOptions
   Section 4.6.42 to Section 4.6.43

   capwapBaseMacTypeOptions
   Section 4.6.43 to Section 4.6.44

   capwapBaseWtpRadiosInUseNum and capwapBaseWtpRadioNumLimit
   Section 4.6.40 to Section 4.6.41

   capwapBaseWtpStaticIpEnable, capwapBaseWtpStaticIp,
   capwapBaseWtpNetmask,capwapBaseWtpGateway
   Section 4.6.47 to Section 4.6.48

   capwapBaseWtpFallbackEnable
   Section 4.6.41 to Section 4.6.42

   all the objects in the capwapBaseWtpRebootStatsTable
   Section 4.6.46 to Section 4.6.47
   all the objects in the capwapBaseRadioStatsTable
   Section 4.6.45 to Section 4.6.46

   capwapBaseJoinFailure,capwapBaseImageUpgradeFailure,
   capwapBaseConfigMsgError
   Section 4.6.34 to Section 4.6.35

   capwapBaseRadioOperableStatus,capwapBaseNtfRadioOperStatusFlag,
   capwapBaseNtfRadioStatusCause
   Section 4.6.33 to Section 4.6.34

   capwapBaseNtfJoinFailureReason,capwapBaseNtfImageFailureReason
   Section 4.6.34 to Section 4.6.35

   capwapBaseNtfConfigMsgErrorType,capwapBaseNtfMsgErrorElements
   Section 4.6.35 to Section 4.6.36

   E8.  No need to repeat the text in the DESCRIPTION clause if a TC is
   used (e.g. capwapBaseTunnelModeOption, capwapBaseMacTypeOptions)

   ----------------------------------------------------------------

   Change the description of them, and only talk about the function of
   objects.

   E9 - capwapBaseWtpMaxRetransmitCnt is not a counter so the suffix Cnt
   should be dropped from the name.

   -------------------------------------------------------------------
   Change capwapBaseWtpMaxRetransmitCnt into capwapBaseWtpMaxRetransmit

   E10 - capwapBaseAcMaxRetransmitCnt is not a counter so the suffix Cnt
   should be dropped from the name.

   -------------------------------------------------------------------

   Change capwapBaseAcMaxRetransmitCnt into capwapBaseAcMaxRetransmit

Other changes made by authors:
1) To keep Terminology consistent
   change "MIBs" with "MIB modules", change "MIB standards" with "MIB
   modules".
2) Replace "As a generic mechanism, it is independent of any wireless
   technologies and defined by an independent MIB file" with
   "It is designed to accommodate the specific needs of each wireless
   technology in a standard way. It is independent of any wireless
   technologies;"
3) add reference to [IEEE.802-11.2007],[I-D.ietf-capwap-protocol-binding
-ieee80211] and [I-D.ietf-capwap-802dot11-mib]
4) Respect the naming conditions to capwapBaseWtpTable,
change capwapBaseMacTypeOptions to capwapBaseWtpMacTypeOptions
change capwapBaseTunnelModeOptions to capwapBaseWtpTunnelModeOptions
5) Change IPV6 to IPv6, IPV4 to IPv4
6) remove redundant "the" in the R"Represents the the next"
7) reorganized the section of overview, and divided it into the
following sub sections:
   5.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     5.1.  Requirements and Constraints . . . . . . . . . . . . . . .  5
     5.2.  Wireless Binding MIB Modules . . . . . . . . . . . . . . .  5
     5.3.  Design Objectives  . . . . . . . . . . . . . . . . . . . .  5
     5.4.  Design Idea  . . . . . . . . . . . . . . . . . . . . . . .  6
     5.5.  Mechanism of Reusing Wireless Binding MIB Modules  . . . .  6
     5.6.  CAPWAP Protocol Wireless Binding MIB Module  . . . . . . .  7
  Especially, add the Terminology of "CAPWAP Protocol Wireless Binding
  MIB Module" and "Wireless Binding MIB Module".

8) Remove unused(0) from CapwapBaseTunnelModeTC,
capwapBaseControlChannelAuthenOptions
and capwapBaseControlChannelAuthenConfig
9) Update some words in the section of" Example of CAPWAP-BASE-MIB
Module Usage"
10) Added capwapBaseAcEcnSupport, capwapBaseWtpEcnSupport
   objects.

Authors' Addresses

   Yang Shi (editor)
   Hangzhou 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
   Yong Zhang (editor)
   Fortinet, Inc.
   1090 Kifer Road
   Sunnyvale, CA 94086
   USA

   EMail: yzhang@fortinet.com