RFC 8350: Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP)
In plain English — editorial summary, not part of the RFC
Control and Provisioning of Wireless Access Points (CAPWAP) is a protocol for encapsulating a station's data frames between the Wireless Transmission Point (WTP) and Access Controller (AC). Specifically, the station's IEEE 802.11 data frames can be either locally bridged or tunneled to the AC. When tunneled, a CAPWAP Data Channel is used for tunneling. In many deployments, encapsulating data frames to an entity other than the AC (for example, to an Access Router (AR)) is desirable. Furthermore, it may also be desirable to use different tunnel encapsulation modes between the WTP and the Access Router. This document defines an extension to the CAPWAP protocol that supports this capability and refers to it as alternate tunnel encapsulation. The alternate tunnel encapsulation allows 1) the WTP to tunnel non-management data frames to an endpoint different from the AC and 2) the WTP to tunnel using one of many known encapsulation types, such as IP-IP, IP-GRE, or CAPWAP. The WTP may advertise support for alternate tunnel encapsulation during the discovery and join process, and the AC may select one of the supported alternate tunnel encapsulation types while configuring the WTP.
Document record
- Document ID
- RFC8350
- Published
- April 2018
- Authors
- R. Zhang; R. Pazhyannur; S. Gundavelli; Z. Cao; H. Deng; Z. Du
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- ops
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 5418Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 DeploymentsCurrent
March 2009
- RFC 4564Objectives for Control and Provisioning of Wireless Access Points (CAPWAP)Current
July 2006
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 8505Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor DiscoveryUpdated
November 2018
- RFC 8952Captive Portal ArchitectureCurrent
November 2020
- RFC 7676IPv6 Support for Generic Routing Encapsulation (GRE)Current
October 2015
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
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?