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.
|Published (Last):||13 July 2010|
|PDF File Size:||1.91 Mb|
|ePub File Size:||4.55 Mb|
|Price:||Free* [*Free Regsitration Required]|
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. However, some control messages are transmitted unencrypted, such as Discovery Requests and Responses, because of the lack a preexisting association between the 2 devices. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
In that case, the AP would take longer to join because the code versions would obviously be different. 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. Overall convergence for the APs to come online will take longer in this scenario. The Principal thread creates a Receiver thread, to handle the responses from the controller.
SLAPP was designed as a simple, extensible protocol that could be extended to other wireless standards, and allow for newer authentication schemes and control protocols to be implemented on top of SLAPP. There are 6 main portions of a controller’s duties. Firstly, it should enable a centralized management solution of the various hardware in a typical WLAN deployment. Receiver and Session Manager [fig7]. These 3 MAC layer concepts will be discussed in greater detail in [Section 2.
Overview of CAPWAP (Cisco Wireless LAN Controllers)
This document describes the base CAPWAP protocol, while separate binding extensions will enable its use with additional wireless technologies. Second, it should make configuration of multiple hardware types transparent, and ensure configurations are consistent across the network. The network entity that provides WTP access to the network infrastructure in the data plane, control plane, management plane, or a combination therein. Instead, this protocol leaves the market vulnerable to more proprietary firmware and configuration exchange protocols running on rtc of SLAPP.
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. AC Name with Priority Inter-AC and station-to-AC communication are strictly outside the scope of this document.
The AP handles the capeap of traffic between itself and its clients, with the controller provided keys. Run – Both the controller and AP operate in the Run state. The state machine in [fig6] show the 4 states attainable during protocol negotiation by a device.
The second program is run on each AP, in order to facilitate communication between the AP and controller. Once received, the controller moves to the Acquiring phase without responding yet. Local MAC refers to the location of the This would allow for more rapid reaction to new innovations in the WLAN sector, as well as improve implementation quality. AP Discovery allows a controller to take ownership of an AP, or potentially redirect control to another controller.
A device that contains an interface to a wireless medium WM. This creates some inconveniences, rfd, in that both APs and controllers need to be preconfigured in order to associate with each other. 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. The protocol must enable centralized management cappwap the components of a WLAN, allow for transparent support rrc different vendor’s hardware, be able to provide monitoring of capeap and software configuration and status, frc finally ensure network security.
The creation of a vendor neutral protocol is a potential boon to consumers of enterprise grade managed wireless solutions.
Rather, it attempts to provide the framework with which devices may request a specific configuration method, which is then layered on top of SLAPP. An overview of the architecture and protocols use in access point AP to controller communication in enterprise grade wireless networks. Figure 2 shows the Local MAC mode, in which a station transmits a wireless frame that is encapsulated in an Converting Protected Data into Unprotected Data.
RFC – Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
From the Run state, an AP and controller may exchange new key material, by entering the Key Update state. Both the AP and controller must be either loaded with PSKs or certificate files to enable encrypted communication. The AP would only implement the The DTLS tunnel allows for different authentication styles, ranging from full stream encryption, to one way encryption, to anonymous authentication.
The security model is not ported over from LWAPP, as there were many concerns about the validity of the security. It was initially designed by Airespace, which was later bought out by Cisco in Vendors have expressed doubt about the dfc of an overarching standard for AP-controller interaction [Judge06]because of the lack of visibility to the end user.
Current Status and Overview of the CAPWAP Protocol
Securing – This phase establishes an encrypted tunnel, over which a protocol can be agreed upon. Configure – An AP with a sufficient version of code may then request to be configured capwal the controller. Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol. Non-realtime capabilities are authentication procedures, fragmenting and defragmenting frames, and more.
The exception is 6.
Overview of CAPWAP (Cisco Wireless LAN Controllers)
Research In Motion D. The challenges facing wireless networks with rfd to standardized management and provisioning are difficult. To centralize the authentication and policy enforcement functions for a wireless network.