draft-ietf-opsawg-capwap-alt-tunnel-09.txt   draft-ietf-opsawg-capwap-alt-tunnel-10.txt 
Opsawg Working Group R. Zhang Opsawg Working Group R. Zhang
Internet-Draft China Telecom Internet-Draft China Telecom
Intended status: Standards Track R. Pazhyannur Intended status: Experimental R. Pazhyannur
Expires: November 3, 2017 S. Gundavelli Expires: March 9, 2018 S. Gundavelli
Cisco Cisco
Z. Cao Z. Cao
H. Deng H. Deng
Z. Du Z. Du
Huawei Huawei
May 2, 2017 September 5, 2017
Alternate Tunnel Encapsulation for Data Frames in CAPWAP Alternate Tunnel Encapsulation for Data Frames in CAPWAP
draft-ietf-opsawg-capwap-alt-tunnel-09 draft-ietf-opsawg-capwap-alt-tunnel-10
Abstract Abstract
Control and Provisioning of Wireless Access Points (CAPWAP) defines a Control and Provisioning of Wireless Access Points (CAPWAP) defines a
specification to encapsulate a station's data frames between the specification to encapsulate a station's data frames between the
Wireless Transmission Point (WTP) and Access Controller (AC). Wireless Transmission Point (WTP) and Access Controller (AC).
Specifically, the station's IEEE 802.11 data frames can be either Specifically, the station's IEEE 802.11 data frames can be either
locally bridged or tunneled to the AC. When tunneled, a CAPWAP data locally bridged or tunneled to the AC. When tunneled, a CAPWAP data
channel is used for tunneling. In many deployments encapsulating channel is used for tunneling. In many deployments encapsulating
data frames to an entity other than the AC (for example to an Access data frames to an entity other than the AC (for example to an Access
skipping to change at page 1, line 46 skipping to change at page 1, line 46
encapsulation types while configuring the WTP. encapsulation types while configuring the WTP.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 3, 2017. This Internet-Draft will expire on March 9, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions used in this document . . . . . . . . . . . . 7 1.1. Conventions used in this document . . . . . . . . . . . . 7
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7
1.3. History of the document . . . . . . . . . . . . . . . . . 8
2. Alternate Tunnel Encapsulation Overview . . . . . . . . . . . 8 2. Alternate Tunnel Encapsulation Overview . . . . . . . . . . . 8
3. CAPWAP Protocol Message Elements Extensions . . . . . . . . . 11 3. CAPWAP Protocol Message Elements Extensions . . . . . . . . . 11
3.1. Supported Alternate Tunnel Encapsulations . . . . . . . . 11 3.1. Supported Alternate Tunnel Encapsulations . . . . . . . . 11
3.2. Alternate Tunnel Encapsulations Type . . . . . . . . . . 11 3.2. Alternate Tunnel Encapsulations Type . . . . . . . . . . 11
3.3. IEEE 802.11 WTP Alternate Tunnel Failure Indication . . . 12 3.3. IEEE 802.11 WTP Alternate Tunnel Failure Indication . . . 12
4. Alternate Tunnel Types . . . . . . . . . . . . . . . . . . . 13 4. Alternate Tunnel Types . . . . . . . . . . . . . . . . . . . 13
4.1. CAPWAP based Alternate Tunnel . . . . . . . . . . . . . . 13 4.1. CAPWAP based Alternate Tunnel . . . . . . . . . . . . . . 13
4.2. PMIPv6 based Alternate Tunnel . . . . . . . . . . . . . . 14 4.2. PMIPv6 based Alternate Tunnel . . . . . . . . . . . . . . 14
4.3. GRE based Alternate Tunnel . . . . . . . . . . . . . . . 15 4.3. GRE based Alternate Tunnel . . . . . . . . . . . . . . . 15
5. Alternate Tunnel Information Elements . . . . . . . . . . . . 15 5. Alternate Tunnel Information Elements . . . . . . . . . . . . 15
skipping to change at page 8, line 17 skipping to change at page 8, line 17
transport-layer protocol (UDP or UDP-Lite) over which CAPWAP Control transport-layer protocol (UDP or UDP-Lite) over which CAPWAP Control
packets are sent and received. packets are sent and received.
CAPWAP Data Channel: A bi-directional flow defined by the AC IP CAPWAP Data Channel: A bi-directional flow defined by the AC IP
Address, WTP IP Address, AC data port, WTP data port, and the Address, WTP IP Address, AC data port, WTP data port, and the
transport-layer protocol (UDP or UDP-Lite) over which CAPWAP Data transport-layer protocol (UDP or UDP-Lite) over which CAPWAP Data
packets are sent and received. In certain WTP modes, the CAPWAP Data packets are sent and received. In certain WTP modes, the CAPWAP Data
Channel only transports IEEE 802.11 management frames and not the Channel only transports IEEE 802.11 management frames and not the
data plane (user traffic). data plane (user traffic).
1.3. History of the document
This document was started to accommodate Service Provider's need of a
more flexible deployment mode with alternative tunnels [RFC7494].
Experiments and tests have been done for this alt-tunnel network
infrastructure. However important, the deployment of relevant
technology is yet to complete. This experimental document is
intended to serve as a historical reference for any future work as to
the operational and deployment requirements..
2. Alternate Tunnel Encapsulation Overview 2. Alternate Tunnel Encapsulation Overview
+-+-+-+-+-+-+ +-+-+-+-+-+-+ +-+-+-+-+-+-+ +-+-+-+-+-+-+
| WTP | | AC | | WTP | | AC |
+-+-+-+-+-+-+ +-+-+-+-+-+-+ +-+-+-+-+-+-+ +-+-+-+-+-+-+
|Join Request[Supported Alternate Tunnel | |Join Request[Supported Alternate Tunnel |
| Encapsulations ] | | Encapsulations ] |
|---------------------------------------->| |---------------------------------------->|
| | | |
|Join Response | |Join Response |
|<----------------------------------------| |<----------------------------------------|
skipping to change at page 23, line 37 skipping to change at page 23, line 37
Chen, Chunju Shao, Li Xue, Jianjie You, Jin Li, Joe Touch, Alexey Chen, Chunju Shao, Li Xue, Jianjie You, Jin Li, Joe Touch, Alexey
Melnikov, Kathleen Moriarty, Mirja Kuehlewind, Catherine Meadows, and Melnikov, Kathleen Moriarty, Mirja Kuehlewind, Catherine Meadows, and
Paul Kyzivat for their valuable comments. Paul Kyzivat for their valuable comments.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,
DOI 10.17487/RFC2003, October 1996, DOI 10.17487/RFC2003, October 1996,
<http://www.rfc-editor.org/info/rfc2003>. <https://www.rfc-editor.org/info/rfc2003>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>. December 1998, <https://www.rfc-editor.org/info/rfc2460>.
[RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, [RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn,
G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"", G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"",
RFC 2661, DOI 10.17487/RFC2661, August 1999, RFC 2661, DOI 10.17487/RFC2661, August 1999,
<http://www.rfc-editor.org/info/rfc2661>. <https://www.rfc-editor.org/info/rfc2661>.
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,
DOI 10.17487/RFC2784, March 2000, DOI 10.17487/RFC2784, March 2000,
<http://www.rfc-editor.org/info/rfc2784>. <https://www.rfc-editor.org/info/rfc2784>.
[RFC2890] Dommety, G., "Key and Sequence Number Extensions to GRE", [RFC2890] Dommety, G., "Key and Sequence Number Extensions to GRE",
RFC 2890, DOI 10.17487/RFC2890, September 2000, RFC 2890, DOI 10.17487/RFC2890, September 2000,
<http://www.rfc-editor.org/info/rfc2890>. <https://www.rfc-editor.org/info/rfc2890>.
[RFC3828] Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., Ed., [RFC3828] Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., Ed.,
and G. Fairhurst, Ed., "The Lightweight User Datagram and G. Fairhurst, Ed., "The Lightweight User Datagram
Protocol (UDP-Lite)", RFC 3828, DOI 10.17487/RFC3828, July Protocol (UDP-Lite)", RFC 3828, DOI 10.17487/RFC3828, July
2004, <http://www.rfc-editor.org/info/rfc3828>. 2004, <https://www.rfc-editor.org/info/rfc3828>.
[RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., [RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed.,
"Layer Two Tunneling Protocol - Version 3 (L2TPv3)", "Layer Two Tunneling Protocol - Version 3 (L2TPv3)",
RFC 3931, DOI 10.17487/RFC3931, March 2005, RFC 3931, DOI 10.17487/RFC3931, March 2005,
<http://www.rfc-editor.org/info/rfc3931>. <https://www.rfc-editor.org/info/rfc3931>.
[RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, [RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control And Provisioning of Wireless Access Points Ed., "Control And Provisioning of Wireless Access Points
(CAPWAP) Protocol Specification", RFC 5415, (CAPWAP) Protocol Specification", RFC 5415,
DOI 10.17487/RFC5415, March 2009, DOI 10.17487/RFC5415, March 2009,
<http://www.rfc-editor.org/info/rfc5415>. <https://www.rfc-editor.org/info/rfc5415>.
[RFC5416] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, [RFC5416] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control and Provisioning of Wireless Access Points Ed., "Control and Provisioning of Wireless Access Points
(CAPWAP) Protocol Binding for IEEE 802.11", RFC 5416, (CAPWAP) Protocol Binding for IEEE 802.11", RFC 5416,
DOI 10.17487/RFC5416, March 2009, DOI 10.17487/RFC5416, March 2009,
<http://www.rfc-editor.org/info/rfc5416>. <https://www.rfc-editor.org/info/rfc5416>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-intarea-tunnels] [I-D.ietf-intarea-tunnels]
Touch, J. and M. Townsley, "IP Tunnels in the Internet Touch, J. and M. Townsley, "IP Tunnels in the Internet
Architecture", draft-ietf-intarea-tunnels-05 (work in Architecture", draft-ietf-intarea-tunnels-07 (work in
progress), March 2017. progress), June 2017.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
RFC 5213, DOI 10.17487/RFC5213, August 2008, RFC 5213, DOI 10.17487/RFC5213, August 2008,
<http://www.rfc-editor.org/info/rfc5213>. <https://www.rfc-editor.org/info/rfc5213>.
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010, Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010,
<http://www.rfc-editor.org/info/rfc5844>. <https://www.rfc-editor.org/info/rfc5844>.
[RFC7494] Shao, C., Deng, H., Pazhyannur, R., Bari, F., Zhang, R.,
and S. Matsushima, "IEEE 802.11 Medium Access Control
(MAC) Profile for Control and Provisioning of Wireless
Access Points (CAPWAP)", RFC 7494, DOI 10.17487/RFC7494,
April 2015, <https://www.rfc-editor.org/info/rfc7494>.
[TS29281] "3rd Generation Partnership Project; Technical [TS29281] "3rd Generation Partnership Project; Technical
Specification Group Core Network and Terminals; General Specification Group Core Network and Terminals; General
Packet Radio System (GPRS) Tunnelling Protocol User Plane Packet Radio System (GPRS) Tunnelling Protocol User Plane
(GTPv1-U)", 2016. (GTPv1-U)", 2016.
Authors' Addresses Authors' Addresses
Rong Zhang Rong Zhang
China Telecom China Telecom
skipping to change at page 26, line 15 skipping to change at page 26, line 15
Huawei Huawei
Xinxi Rd. 3 Xinxi Rd. 3
Beijing 100085 Beijing 100085
China China
Email: denghui02@gmail.com Email: denghui02@gmail.com
Zongpeng Du Zongpeng Du
Huawei Huawei
No.156 Beiqing Rd. Z-park, HaiDian District No.156 Beiqing Rd. Z-park, HaiDian District
Beijing 100095 Beijing 100095
China China
Email: duzongpeng@huawei.com Email: duzongpeng@huawei.com
 End of changes. 22 change blocks. 
22 lines changed or deleted 39 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/