Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification, March Canonical URL: txt; File. RFC (part 1 of 6): Control And Provisioning of Wireless Access Points ( CAPWAP) Protocol Specification. Control and Provisioning of Wireless Access Points (CAPWAP) is a standard and interoperable RFC defines the actual CAPWAP protocol specifications.

Author: Goltilabar Vujin
Country: Mozambique
Language: English (Spanish)
Genre: Finance
Published (Last): 26 May 2014
Pages: 448
PDF File Size: 6.50 Mb
ePub File Size: 18.59 Mb
ISBN: 417-5-52537-178-8
Downloads: 77599
Price: Free* [*Free Regsitration Required]
Uploader: Fenrinris

WTPs require a set of dynamic management and control functions related to their primary task of connecting the wireless and wired mediums.

This leaves the time-critical applications of wireless control and access in the WTP, making efficient use of the computing capwxp available in WTPs, which are subject to severe cost pressure. Split and Local MAC medium access control. The only duties that the controller is responsible for under this scheme is wireless key management capap authentication proxying.

LWAPP defines certain operation modes for compliant hardware.

Overview of CAPWAP (Cisco Wireless LAN Controllers)

A device that contains an interface to a wireless medium WM. Vendors do not have a clearly defined cappwap of protocols that must be implemented, in order to be compatible with other vendors. The latter implies that the WTP performs the In either case, the L2 wireless management frames are processed locally. Both the AP and controller must be either loaded with PSKs or certificate files to enable encrypted communication.

The exception is 6.

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

In [fig6]the same SLAPP protocol would be used by an AP to decide how to download updated firmware, as would be used to determine a protocol to communicate with the controller.


Extensibility is provided via a generic encapsulation and transport mechanism, enabling the CAPWAP protocol to be applied to many access point types in the future, via a specific wireless binding. Consult [RFC] for a full overview. There are 2 primary components to the wireless network. The WLAN market is structured similarly to an oligopoly, because the market is controlled by a very small set 54115 vendors, namely Aruba, Cisco, Meru, and Trapeze.

Often refered to as remote antennas, Thin APs lower price allow for a more thorough wireless coverage at a given price point, and rcc attractive offerings for large deployments. Communication between dfc 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. The CAPWAP protocol does not include specific wireless technologies; instead, it relies on a binding specification to extend the technology to a particular wireless technology.

Image Download – The newly joined AP then may request a tfc update, upon seeing the controller advertise a higher version of code. The AP transitions to the Securing phase when a “client hello” message dapwap been received.

Not all access points are alike, as they fall into 3 categories. Thus, the entire process of deploying an AP can be implemented in a vendor neutral format, from finding an initial controller, to deploying firmware updates, to configuration and access point redirection.

Capqap might encounter a deployment scenario as in Figurewhere you have a mixed deployment. The physical or network entity that contains an RF antenna and wireless Physical Layer PHY to transmit and receive station traffic for wireless access networks. This limits interoperability to only vendors who have implemented [RFC]which is just Cisco as of the time of this writing.



Overview of CAPWAP (Cisco Wireless LAN Controllers)

Many vendors use this to their advantage, and create product differentiation by including features into their wireless products, such as firewall capability in their controller hardware. This state updates the encryption keys on both devices, which is used to encrypt all further messages, until a new key is requested. To centralize the authentication and policy enforcement functions for a wireless network.

Change State Event Response A Fat AP understands and speaks layer 2 and possible layer 3 protocols, and is addressable on the network. Third, so called “Fit APs” have gained popularity in recent years, as they combine both the intelligence of a Local MAC implementation with the agility of a Remote MAC implementation, by splitting realtime and non-realtime functionality between the controller and AP. AC Name with Priority However, this compatibility was not the result of Xapwap, but rather specific licensing capwaap between each supported company.

SLAPP attempted to solve a more general problem, not 55415 itself to Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Negotiated Control Protocol – Here both devices begin communicating in the previously agreed-upon protocol.