Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP)
RFC 8350
Document | Type | RFC - Experimental (April 2018; No errata) | |
---|---|---|---|
Authors | Rong Zhang , Rajesh Pazhyannur , Sri Gundavelli , Zhen Cao , Hui Deng , Zongpeng Du | ||
Last updated | 2018-04-25 | ||
Replaces | draft-zhang-opsawg-capwap-cds | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Tianran Zhou | ||
Shepherd write-up | Show (last changed 2017-10-17) | ||
IESG | IESG state | RFC 8350 (Experimental) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Warren Kumari | ||
Send notices to | warren@kumari.net, Tianran Zhou <zhoutianran@huawei.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) R. Zhang Request for Comments: 8350 China Telecom Category: Experimental R. Pazhyannur ISSN: 2070-1721 S. Gundavelli Cisco Z. Cao H. Deng Z. Du Huawei April 2018 Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP) Abstract 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. Zhang, et al. Experimental [Page 1] RFC 8350 Alternate Tunnel April 2018 Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8350. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Zhang, et al. Experimental [Page 2] RFC 8350 Alternate Tunnel April 2018 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 7 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7 1.3. History of the Document . . . . . . . . . . . . . . . . . 8 2. Alternate Tunnel Encapsulation Overview . . . . . . . . . . . 9 3. Extensions for CAPWAP Protocol Message Elements . . . . . . . 11 3.1. Supported Alternate Tunnel Encapsulations . . . . . . . . 11 3.2. Alternate Tunnel Encapsulations Type . . . . . . . . . . 11 3.3. IEEE 802.11 WTP Alternate Tunnel Failure Indication . . . 12 4. Alternate Tunnel Types . . . . . . . . . . . . . . . . . . . 13 4.1. CAPWAP-Based Alternate Tunnel . . . . . . . . . . . . . . 13 4.2. PMIPv6-Based Alternate Tunnel . . . . . . . . . . . . . . 14 4.3. GRE-Based Alternate Tunnel . . . . . . . . . . . . . . . 15 5. Alternate Tunnel Information Elements . . . . . . . . . . . . 16Show full document text