RFC 4564: Objectives for Control and Provisioning of Wireless Access Points (CAPWAP)
In plain English — editorial summary, not part of the RFC
This document presents objectives for an interoperable protocol for the Control and Provisioning of Wireless Access Points (CAPWAP). The document aims to establish a set of focused requirements for the development and evaluation of a CAPWAP protocol. The objectives address architecture, operation, security, and network operator requirements that are necessary to enable interoperability among Wireless Local Area Network (WLAN) devices of alternative designs. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4564
- Published
- July 2006
- Authors
- S. Govindan; H. Cheng; ZH. Yao; WH. Zhou; L. Yang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5414Wireless LAN Control Protocol (WiCoP)Obsoleted
February 2010
- RFC 5418Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 DeploymentsCurrent
March 2009
- RFC 8350Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2018
- RFC 4334Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)Current
February 2006
- RFC 4565Evaluation of Candidate Control and Provisioning of Wireless Access Points (CAPWAP) ProtocolsCurrent
July 2006
- RFC 4560Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsCurrent
June 2006
- RFC 4554Use of VLANs for IPv4-IPv6 Coexistence in Enterprise NetworksCurrent
June 2006
- RFC 4547Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination SystemsUpdated
June 2006
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?