draft-ietf-tsvwg-rfc6040update-shim-07.txt   draft-ietf-tsvwg-rfc6040update-shim-08.txt 
Transport Area Working Group B. Briscoe Transport Area Working Group B. Briscoe
Internet-Draft Independent Internet-Draft Independent
Updates: 6040, 2661, 2784, 3931, 4380, November 12, 2018 Updates: 6040, 2661, 2784, 3931, 4380, March 29, 2019
7450 (if approved) 7450 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: May 16, 2019 Expires: September 30, 2019
Propagating Explicit Congestion Notification Across IP Tunnel Headers Propagating Explicit Congestion Notification Across IP Tunnel Headers
Separated by a Shim Separated by a Shim
draft-ietf-tsvwg-rfc6040update-shim-07 draft-ietf-tsvwg-rfc6040update-shim-08
Abstract Abstract
RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the
rules for propagation of ECN consistent for all forms of IP in IP rules for propagation of ECN consistent for all forms of IP in IP
tunnel. This specification updates RFC 6040 to clarify that its tunnel. This specification updates RFC 6040 to clarify that its
scope includes tunnels where two IP headers are separated by at least scope includes tunnels where two IP headers are separated by at least
one shim header that is not sufficient on its own for wide area one shim header that is not sufficient on its own for wide area
packet forwarding. It surveys widely deployed IP tunnelling packet forwarding. It surveys widely deployed IP tunnelling
protocols separated by such shim header(s) and updates the protocols separated by such shim header(s) and updates the
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 https://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 May 16, 2019. This Internet-Draft will expire on September 30, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://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
skipping to change at page 9, line 13 skipping to change at page 9, line 13
It is RECOMMENDED that VXLAN and VXLAN-GPE implementations comply It is RECOMMENDED that VXLAN and VXLAN-GPE implementations comply
with RFC 6040 when the VXLAN header is inserted between (or removed with RFC 6040 when the VXLAN header is inserted between (or removed
from between) IP headers. The authors of any future update to these from between) IP headers. The authors of any future update to these
specifications are encouraged to add a requirement to comply with RFC specifications are encouraged to add a requirement to comply with RFC
6040 as updated by the present specification. 6040 as updated by the present specification.
The Network Service Header (NSH [RFC8300]) has been defined as a The Network Service Header (NSH [RFC8300]) has been defined as a
shim-based encapsulation to identify the Service Function Path (SFP) shim-based encapsulation to identify the Service Function Path (SFP)
in the Service Function Chaining (SFC) architecture [RFC7665]. A in the Service Function Chaining (SFC) architecture [RFC7665]. A
proposal has been made for the processing of ECN when handling proposal has been made for the processing of ECN when handling
transport encapsulation [I-D.eastlake-sfc-nsh-ecn-support]. transport encapsulation [I-D.ietf-sfc-nsh-ecn-support].
The specifications of Geneve and GUE already refer to RFC 6040 for The specifications of Geneve and GUE already refer to RFC 6040 for
ECN encapsulation. ECN encapsulation.
Section 3.1.11 of the UDP usage guidelines [RFC8085] already explains Section 3.1.11 of the UDP usage guidelines [RFC8085] already explains
that a tunnel that encapsulates an IP header directly within a UDP/IP that a tunnel that encapsulates an IP header directly within a UDP/IP
datagram needs to follow RFC 6040 when propagating the ECN field datagram needs to follow RFC 6040 when propagating the ECN field
between inner and outer IP headers. The requirements in Section 4 between inner and outer IP headers. The requirements in Section 4
update RFC 6040 so, by reference, they automatically update RFC 8085 update RFC 6040 so, by reference, they automatically update RFC 8085
to add the important but previously unstated requirement that, if the to add the important but previously unstated requirement that, if the
skipping to change at page 17, line 17 skipping to change at page 17, line 17
authors. authors.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-tsvwg-ecn-encap-guidelines] [I-D.ietf-tsvwg-ecn-encap-guidelines]
Briscoe, B., Kaippallimalil, J., and P. Thaler, Briscoe, B., Kaippallimalil, J., and P. Thaler,
"Guidelines for Adding Congestion Notification to "Guidelines for Adding Congestion Notification to
Protocols that Encapsulate IP", draft-ietf-tsvwg-ecn- Protocols that Encapsulate IP", draft-ietf-tsvwg-ecn-
encap-guidelines-11 (work in progress), Novemeber 2018. encap-guidelines-11 (work in progress), November 2018.
[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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
DOI 10.17487/RFC2474, December 1998, DOI 10.17487/RFC2474, December 1998,
skipping to change at page 18, line 31 skipping to change at page 18, line 31
interface", Technical Specification TS 29.060. interface", Technical Specification TS 29.060.
[GTPv1-U] 3GPP, "General Packet Radio System (GPRS) Tunnelling [GTPv1-U] 3GPP, "General Packet Radio System (GPRS) Tunnelling
Protocol User Plane (GTPv1-U)", Technical Specification TS Protocol User Plane (GTPv1-U)", Technical Specification TS
29.281. 29.281.
[GTPv2-C] 3GPP, "Evolved General Packet Radio Service (GPRS) [GTPv2-C] 3GPP, "Evolved General Packet Radio Service (GPRS)
Tunnelling Protocol for Control plane (GTPv2-C)", Tunnelling Protocol for Control plane (GTPv2-C)",
Technical Specification TS 29.274. Technical Specification TS 29.274.
[I-D.eastlake-sfc-nsh-ecn-support]
Eastlake, D., Briscoe, B., and A. Malis, "Explicit
Congestion Notification (ECN) and Congestion Feedback
Using the Network Service Header (NSH)", draft-eastlake-
sfc-nsh-ecn-support-02 (work in progress), October 2018.
[I-D.ietf-intarea-gue] [I-D.ietf-intarea-gue]
Herbert, T. and O. Zia, "Generic UDP Encapsulation", Herbert, T., Yong, L., and O. Zia, "Generic UDP
draft-ietf-intarea-gue-06 (work in progress), August 2018. Encapsulation", draft-ietf-intarea-gue-07 (work in
progress), March 2019.
[I-D.ietf-nvo3-geneve] [I-D.ietf-nvo3-geneve]
Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
Network Virtualization Encapsulation", draft-ietf- Network Virtualization Encapsulation", draft-ietf-
nvo3-geneve-08 (work in progress), October 2018. nvo3-geneve-13 (work in progress), March 2019.
[I-D.ietf-nvo3-vxlan-gpe] [I-D.ietf-nvo3-vxlan-gpe]
Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol
Extension for VXLAN", draft-ietf-nvo3-vxlan-gpe-06 (work Extension for VXLAN", draft-ietf-nvo3-vxlan-gpe-06 (work
in progress), April 2018. in progress), April 2018.
[I-D.ietf-sfc-nsh-ecn-support]
Eastlake, D., Briscoe, B., and A. Malis, "Explicit
Congestion Notification (ECN) and Congestion Feedback
Using the Network Service Header (NSH)", draft-ietf-sfc-
nsh-ecn-support-00 (work in progress), February 2019.
[RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic [RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
Routing Encapsulation (GRE)", RFC 1701, Routing Encapsulation (GRE)", RFC 1701,
DOI 10.17487/RFC1701, October 1994, DOI 10.17487/RFC1701, October 1994,
<https://www.rfc-editor.org/info/rfc1701>. <https://www.rfc-editor.org/info/rfc1701>.
[RFC2637] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, [RFC2637] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little,
W., and G. Zorn, "Point-to-Point Tunneling Protocol W., and G. Zorn, "Point-to-Point Tunneling Protocol
(PPTP)", RFC 2637, DOI 10.17487/RFC2637, July 1999, (PPTP)", RFC 2637, DOI 10.17487/RFC2637, July 1999,
<https://www.rfc-editor.org/info/rfc2637>. <https://www.rfc-editor.org/info/rfc2637>.
 End of changes. 11 change blocks. 
16 lines changed or deleted 17 lines changed or added

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