<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tsvwg-rfc6040update-shim" target="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-23">
   <front>
      <title>Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim</title>
      <author initials="B." surname="Briscoe" fullname="Bob Briscoe">
         <organization>Independent</organization>
      </author>
      <date month="December" day="5" year="2023" />
      <abstract>
	 <t>   RFC 6040 on &quot;Tunnelling of Explicit Congestion Notification&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tsvwg-rfc6040update-shim-23" />
   
</reference>
