RFC CAPWAP Protocol Base MIB May CAPWAP Control Channel: A bi-directional flow defined by the AC IP Address, WTP IP Address, AC control. The Control And Provisioning of Wireless Access Points (CAPWAP) protocol is a standard, The protocol specification is described in RFC RFC (part 1 of 6): Control And Provisioning of Wireless Access Points ( CAPWAP) Protocol Specification.

Author: Gardakora Kazibar
Country: Mozambique
Language: English (Spanish)
Genre: Medical
Published (Last): 3 March 2008
Pages: 409
PDF File Size: 6.51 Mb
ePub File Size: 17.14 Mb
ISBN: 368-8-83102-974-9
Downloads: 21883
Price: Free* [*Free Regsitration Required]
Uploader: Niramar

If a timer expires while the AP is in the Acquiring phase before receiving a “client hello”, the AP goes back to Discovery mode. The proposal cites the availability of IPsec for general data traffic, and does not provide any mechanism of encrypting data messages between the controller and AP, only control cqpwap, and the key exchange process between both devices.

Current Status and Overview of the CAPWAP Protocol

Receiver and Session Manager [fig7]. Currently, their WLAN controllers can only interface with Meru brand access points, utilizing a proprietary protocol. Aruba also claims that as of Marchno vendor has implemented CAPWAP per the [RFC] specifications, instead claiming that vendors have been using proprietary extensions to complete the specification. Vendors such as Trapeze criticized the specification, as it makes assumptions about the topology of the network that the WLAN will be deployed on, as well as assumptions about the complexity and functionality implemented by the AP, by allowing only Local and Split MAC implementations.

The AC may also provide centralized bridging, forwarding, and encryption of user traffic. More specifically, it fails to define key duties rcc in [Section 2.


Current Status and Overview of the CAPWAP Protocol

CAPWAP only seeks to relay what a device is and is not capable of, in order to classify and provision the device into operation. The firmware is used to program radio capabilities on the AP. The controller awaits a Discovery Request from an AP.

Oligopolies are typically resistant to destabilization of the market, introduced by large paradigm shifts, such as the shift that is promised by CAPWAP. This is accomplished by the AP broadcasting a Discovery Request. However, the Principal and Receiver thread share sent and received packets with each other.

Overview of CAPWAP (Cisco Wireless LAN Controllers)

The controller can then authenticate the AP, and negotiate its advertised capabilities, such as being Current vendor solutions and interoperability is also covered, and the current state and trends in the enterprise WLAN market caowap discussed. Contributing Authors This section lists and acknowledges the authors of significant text and concepts included in rgc specification.

A standard that ensures compatibility between vendors is necessary to prevent vendor lock-in. The cost per unit is much lower than Fat APs, as the only logic necessary for functioning is the radio hardware and a simple wired interface, with memory to store firmware. Communication between a controller and AP must be encrypted, as all data sent to and received by the AP will be tunneled over the local LAN to or from the controller.

Vendors do not have a clearly defined set of protocols that must be implemented, in order to be compatible with other vendors.

This would allow for more rapid reaction to new innovations in the WLAN sector, as well as improve implementation quality. During this initialization, as well as operation, periodic control messages must be rtc between the AP and the controller, for management and statistical purposes.


To provide an extensible protocol that is not bound to a specific wireless technology.

SLAPP attempted to solve a more general problem, not limiting itself to Local MAC has the benefit of being able to perform all of the MAC functions quickly, without having to rely on the controller.

The controller opens a channel to the AP, which stays open for the up time of the access point. LWAPP tried to solve the specific frc of associating APs to controllers, and managing firmware and configuration updates.

However, the process is slow, as upgrade paths are not necessarily direct and simple. The controller acts as a management station, configuration station, and potentially a router.

CAPWAP, Control And Provisioning of Wireless Access Points

The status of interoperability between vendors currently was discussed, as well as the plans of each vendor to support CAPWAP in the future. A single Receiver thread receives and processes any requests from APs. To centralize the authentication and policy enforcement functions for a wireless network.

Because SLAPP supports both layer 2 and 3, access points may be in completely different routed networks as the controller, or even across the Internet.

SLAPP was designed as a simple, extensible protocol that could be ffc to other wireless standards, and allow for newer authentication schemes and control protocols to be implemented on top of SLAPP.