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):||11 August 2005|
|PDF File Size:||9.50 Mb|
|ePub File Size:||3.87 Mb|
|Price:||Free* [*Free Regsitration Required]|
The creation of a vendor neutral protocol is a potential boon to consumers of enterprise grade managed wireless solutions. It usually falls to the vendor to create a specific implementation. The only duties that the controller is responsible for under this scheme is wireless key management and authentication proxying.
Non-realtime capabilities are authentication procedures, fragmenting and defragmenting frames, and more. The nature of such systems is of such czpwap, that vendor implementations can vary widely in their scope and features, leading to incompatibilities between vendors.
Contributing Authors This section lists and cappwap the authors of significant text and concepts included in this specification. The division between the sending and receiving of CAPWAP messages is that the communication between the AP and controller is not necessarily synchronous, and the capsap may send a request while the Principal thread is sending. Conventions Used in This Document The controller implements most of the management and configuration logic. The Receiver is then responsible for processing the packets, and either dropping the packets, or moving a good connection into a Session Manager Thread.
The status of interoperability between vendors currently was discussed, as well as the plans of each vendor to support CAPWAP in the future. 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.
A single Receiver thread receives and processes any requests from APs. It was initially designed by Airespace, which was later bought out by Cisco in The wireless key exchange is handled in a fully encrypted fashion, by utilizing preshared keys PSKsor a security certificate model.
Current Status and Overview of the CAPWAP Protocol
The AP typically contains some amount of logic, however, that amount is governed by the MAC architecture that the AP implements, which will be covered capawp [Section 2]. Finally configuration takes place, and the AP is set into active mode.
This would be a similar scenario to two controllers running different versions of code. Oligopolies are typically resistant to destabilization of the market, introduced by large paradigm shifts, such as the shift that is promised by CAPWAP.
RFC – part 1 of 6
This document uses additional terminology defined in [ RFC ]. Critics of SLAPP argue that it is an incomplete specification, as it enforces no minimal compatibility. The AP then downloads the firmware, and once completed, enters the Reset state, and then attempts to rejoin a controller.
Primary Discovery Request Message However, some have been met with criticism. In some vendor’s access points, even wireless encryption is not even performed at the AP. It was seen as overly complex, as well as lacking in security, as portions of the control stream are unencrypted, and the entire data stream between controller and AP are unencrypted.
Information on RFC » RFC Editor
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. A large corporate network with hundreds of APs could use a more centralized solution, which is realized by Thin APs. This protocol can be anything, as long as both sides agreed on it.
This lack of customer mobility leads to less innovative product offerings from the wireless vendors. 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 Receiver-From-STA thread can pass along messages through the Principal thread, which are sent back to the controller for processing.
Overview of CAPWAP (Cisco Wireless LAN Controllers)
The frc then moves into the Negotiated Control Protocol state. Decryption Error Report Period The state machine in [fig6] show the 4 fapwap attainable during protocol negotiation by a device. The size of many wireless networks in large companies and universities also introduces many problems of maintaining a consistent configuration across many similar devices, with potentially different hardware capabilities and physical locations. To enable shifting of the higher-level protocol processing from the WTP.
As mentioned in [Section 4. Once received, the controller moves to the Acquiring phase without responding yet. Discovery – New Capsap must seek out a controller with which to associate. Thin APs may be found in AP-controller style deployments. You might encounter a deployment scenario as in Figurewhere you have a mixed deployment. This is accomplished by the AP broadcasting a Discovery Request. The controller processes the Discovery Request, and if valid, responds in the positive, and moves to Securing.
The latter implies that the WTP performs the Local MAC refers to the location of 5145 The second program is run on each AP, in order to facilitate communication between the AP and controller. A standard that ensures compatibility between vendors is necessary to prevent vendor lock-in.
Acquiring – This state represents both devices connecting to each other, to begin encrypting their communications. Thin APs have their MAC layers implemented entirely on the controller, and use tunneling to a controller to have all of their frames processed for forwarding onto the back haul network. However, the header does not warrant any particular attention, and as such, will not be covered by this paper. However, this simplicity does not come at the expense of flexibility.
If a timer expires while the AP is in the Acquiring phase before receiving a “client hello”, the AP goes back to Discovery mode. A device that contains an interface to a wireless medium WM.