RFC 4118: Architecture Taxonomy for Control and Provisioning of Wireless Access Points (CAPWAP)
In plain English — editorial summary, not part of the RFC
This document provides a taxonomy of the architectures employed in the existing IEEE 802.11 products in the market, by analyzing Wireless LAN (WLAN) functions and services and describing the different variants in distributing these functions and services among the architectural entities. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4118
- Published
- June 2005
- Authors
- L. Yang; P. Zerfos; E. Sadot
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4017Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANsCurrent
March 2005
- RFC 5415Control And Provisioning of Wireless Access Points (CAPWAP) Protocol SpecificationUpdated
March 2009
- 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 7494IEEE 802.11 Medium Access Control (MAC) Profile for Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2015
- RFC 4334Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)Current
February 2006
- RFC 4116IPv4 Multihoming Practices and LimitationsCurrent
July 2005
- RFC 4131Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy PlusUpdated
September 2005
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?