This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Access Point Protocol
tunnel from FS Light-weight CAPWAP Access Points.

This MIB is used to show and configure Dynamic Host
	        Configuration Protocol (DHCP) related statistics.


The relationship between CC and the CAPWAP APs
can be depicted as follows:

+......+     +......+     +......+           +......+
+      +     +      +     +      +           +      +
+  CC  +     +  CC  +     +  CC  +           +  CC  +
+      +     +      +     +      +           +      +
+......+     +......+     +......+           +......+
..            .             .                 .
..            .             .                 .
.  .            .             .                 .
.    .            .             .                 .
.      .            .             .                 .
.        .            .             .                 .
+......+ +......+     +......+      +......+          +......+
+      + +      +     +      +      +      +          +      +
+  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +
+      + +      +     +      +      +      +          +      +
+......+ +......+     +......+      +......+          +......+
.              .             .                 .
.  .              .             .                 .
.    .              .             .                 .
.      .              .             .                 .
.        .              .             .                 .
+......+ +......+     +......+      +......+          +......+
+      + +      +     +      +      +      +          +      +
+  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +
+      + +      +     +      +      +      +          +      +
+......+ +......+     +......+      +......+          +......+


The CAPWAP tunnel exists between the controller and
the APs.  The MNs communicate with the APs through
the protocol defined by the 802.11 standard.

CAPWAP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the CAPWAP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside CAPWAP frames and forward
the CAPWAP frames to the controller.

                   GLOSSARY

Access Point ( AP )

An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.  

CAPWAP APs encapsulate all the 802.11 frames in
CAPWAP frames and sends them to the controller to which
it is logically connected.

Central Controller ( CC )

The central entity that terminates the CAPWAP protocol
tunnel from the CAPWAP APs.  Throughout this MIB,
this entity also referred to as 'controller'. 

Light Weight Access Point Protocol ( CAPWAP ) 

This is a generic protocol that defines the 
communication between the Access Points and the
Central Controller.

Mobile Node ( MN )

A roaming 802.11 wireless device in a wireless
network associated with an access point. Mobile Node,
Mobile Station(Ms) and client are used interchangeably. 

REFERENCE

[1] Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications.

[2] Draft-obara-capwap-capwap-00.txt, IETF Light 
Weight Access Point Protocol