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: Shagar Grojar
Country: Kuwait
Language: English (Spanish)
Genre: Sex
Published (Last): 16 November 2007
Pages: 312
PDF File Size: 20.36 Mb
ePub File Size: 5.19 Mb
ISBN: 435-4-80528-821-2
Downloads: 89310
Price: Free* [*Free Regsitration Required]
Uploader: Jushicage

A device that contains an interface to a wireless medium WM. Third, monitoring the status of both hardware and software configurations is necessary to ensure a properly operating network. The proposal cites the availability of IPsec for general data traffic, and does not provide any mechanism of encrypting data messages capap the controller and AP, only control messages, and the key vapwap process between both devices.

Discovery – New APs must seek out a controller with which to associate. The network entity that provides WTP access to the network infrastructure in the data plane, control plane, management plane, or a combination therein. In this survey, a look at different proposed standards for enabling WLAN controllers rfx support multi-vendor APs, and how to solve the problems introduced by the AP-controller architecture, has been taken. Vendors have expressed doubt about the importance of an overarching standard for Frc interaction [Judge06]because of the lack of visibility to the end user.

The AP forwards packets to the controller, and maintains normal operation. Currently, their WLAN controllers can only interface with Meru brand access points, utilizing a proprietary protocol.

The paper covers the current architecture of enterprise WLAN deployments, as well as proposed protocols that attempt to simplify their management and configuration, and allow inter-vendor compatibility of access points APs and controllers. The AP broadcasts a Discovery Request, and upon reception of the response, moves to the Acquiring phase as well.


However, some control messages are transmitted unencrypted, such as Discovery Requests and Responses, because of the lack a preexisting association between the 2 devices. Run – Both the controller and AP operate in the Run state. Finally configuration takes place, and the AP is set into active mode. Fat APs are much more complex, and cost much more per unit than their thinner cousins.

To centralize the authentication and policy enforcement functions for a wireless network. To provide an extensible protocol that is not bound to a specific wireless technology.

To enable shifting of the higher-level protocol processing from the WTP. Network Working Group P.

RFC – Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification

The need for flexible wireless network infrastructure will become more pronounced as WLANs become larger and more widespread.

However, the protocol itself is not finalized, resulting in both hesitation to implement on vendor’s parts, and incomplete or incompatible vapwap implementations. A standard that ensures compatibility between vendors is necessary to prevent vendor lock-in. Table of Contents 1. The creation of a vendor neutral protocol is a potential boon to consumers of enterprise grade managed wireless capwwp.

With the typical usage case, data from an access point is tunneled back to the controller for processing, and sending onto the back haul network. There is no back haul required for Fat APs, because it can put packets and frames directly on the wire, in contrast to Thin AP implementations.

These 3 MAC layer concepts will be discussed in greater detail in rf 2. Centralization of these functions will enable reduced cost and higher efficiency by applying the capabilities of network processing silicon to the wireless network, as in wired LANs.

SLAPP operates as the framework to make a connection between two devices, and negotiate a protocol. This thread is used to accept non-realtime requests from the associated client stations, such as any message in Split MAC that may need to be forwarded to the controller in the CAPWAP protocol.


Allowing these functions to be performed from a centralized AC in an interoperable fashion increases manageability and allows network operators to more tightly control their wireless network infrastructure. Image Download – The newly joined AP cawpap may request a firmware update, upon seeing the controller advertise a higher version of code. The controller then authenticates the AP, and begins uploading firmware to the AP.

Overview of CAPWAP (Cisco Wireless LAN Controllers)

The controller and AP will exchange 2 types of messages: Thin APs may be found in Dfc style deployments. Once received, the controller moves to the Acquiring phase without responding yet.

The migration towards a unified standard will be long, and not necessarily even happen, because each vendor already supports its own proprietary protocols, and sees little motivation to commoditize their AP hardware by introducing CAPWAP across the industry. Meru Air Traffic Control software may be used to provision and manage APs, but provides no multi vendor support. Deletion of Protected Records The controller opens a channel to the AP, which stays open for the up time of the access point.

From the Run state, an AP and controller may exchange new key material, by entering rcf Key Update state. The Principal thread creates a Receiver thread, to handle the responses from the controller. It was initially designed by Airespace, which was later bought out by Cisco in Distribution of this memo is unlimited.

Those binding specifications for the IEEE