Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim
draft-ietf-tsvwg-rfc6040update-shim-23

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: David Black <david.black@dell.com>, The IESG <iesg@ietf.org>, draft-ietf-tsvwg-rfc6040update-shim@ietf.org, gorry@erg.abdn.ac.uk, martin.h.duke@gmail.com, rfc-editor@rfc-editor.org, tsvwg-chairs@ietf.org, tsvwg@ietf.org
Subject: Protocol Action: 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' to Proposed Standard (draft-ietf-tsvwg-rfc6040update-shim-23.txt)

The IESG has approved the following document:
- 'Propagating Explicit Congestion Notification Across IP Tunnel Headers
   Separated by a Shim'
  (draft-ietf-tsvwg-rfc6040update-shim-23.txt) as Proposed Standard

This document is the product of the Transport and Services Working Group.

The IESG contact persons are Zaheduzzaman Sarker and Martin Duke.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/

Ballot Text

Technical Summary

   RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the
   rules for propagation of ECN consistent for all forms of IP in IP
   tunnel.  This specification updates RFC 6040 to clarify that its
   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
   packet forwarding.  It surveys widely deployed IP tunnelling
   protocols that use such shim header(s) and updates the specifications
   of those that do not mention ECN propagation (that is RFC 2661, RFC
   3931, RFC 2784, RFC 4380 and RFC 7450, which respectively specify
   L2TPv2, L2TPv3, GRE, Teredo and AMT).  This specification also
   updates RFC 6040 with configuration requirements needed to make any
   legacy tunnel ingress safe.

Working Group Summary

The WG reached consensus following a WGLC that concluded on 25th April 2021,
and rev 14 was thought to resolve the WG comments. This document has a
dependency on ietf-tsvwg-ecn-encap-guidelines, and that document has stalled
publication of this draft. Since rev-14, the author has continued to correct
text and respond to Shepherd comments. 

Document Quality

There are a wide variety of tunnel specifications and implementations, some of
these are thought to follow the design described in this document.

Personnel

   The Document Shepherd for this document is Gorry Fairhurst. The
   Responsible Area Director is Martin Duke.

RFC Editor Note