RFC 4565: Evaluation of Candidate Control and Provisioning of Wireless Access Points (CAPWAP) Protocols
In plain English — editorial summary, not part of the RFC
This document is a record of the process and findings of the Control and Provisioning of Wireless Access Points Working Group (CAPWAP WG) evaluation team. The evaluation team reviewed the 4 candidate protocols as they were submitted to the working group on June 26, 2005. his memo provides information for the Internet community.
Document record
- Document ID
- RFC4565
- Published
- July 2006
- Authors
- D. Loher; D. Nelson; O. Volinsky; B. Sarikaya
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 31
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4564Objectives for Control and Provisioning of Wireless Access Points (CAPWAP)Current
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
- RFC 4546Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF InterfacesUpdated
June 2006
- RFC 4608Source-Specific Protocol Independent Multicast in 232/8Current
August 2006
- RFC 4609Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and EnhancementsCurrent
October 2006
- RFC 4611Multicast Source Discovery Protocol (MSDP) Deployment ScenariosCurrent
August 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?