RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
In plain English — editorial summary, not part of the RFC
This specification defines the Control And Provisioning of Wireless Access Points (CAPWAP) Protocol, meeting the objectives defined by the CAPWAP Working Group in RFC 4564. The CAPWAP protocol is designed to be flexible, allowing it to be used for a variety of wireless technologies. This document describes the base CAPWAP protocol, while separate binding extensions will enable its use with additional wireless technologies. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5415
- Published
- March 2009
- Authors
- P. Calhoun; M. Montemurro; D. Stanley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 155
- Also known as
- —
- Obsoletes:
- RFC 5414
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5416Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11Current
March 2009
- RFC 5417Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP OptionCurrent
March 2009
- RFC 5412Lightweight Access Point ProtocolCurrent
February 2010
- RFC 4118Architecture Taxonomy for Control and Provisioning of Wireless Access Points (CAPWAP)Current
June 2005
- RFC 7124Ethernet in the First Mile Copper (EFMCu) Interfaces MIBCurrent
February 2014
- RFC 7448MIB Transfer from the IETF to the IEEE 802.3 WGCurrent
February 2015
- RFC 7494IEEE 802.11 Medium Access Control (MAC) Profile for Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2015
- RFC 9119Multicast Considerations over IEEE 802 Wireless MediaCurrent
October 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?