%% You should probably cite draft-ietf-tsvwg-ecn-encap-guidelines-22 instead of this revision. @techreport{ietf-tsvwg-ecn-encap-guidelines-15, number = {draft-ietf-tsvwg-ecn-encap-guidelines-15}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines/15/}, author = {Bob Briscoe and John Kaippallimalil}, title = {{Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP}}, pagetotal = 38, year = 2021, month = mar, day = 8, abstract = {The purpose of this document is to guide the design of congestion notification in any lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to propagate consistently from lower layer protocols into IP. Then the IP internetwork layer can act as a portability layer to carry congestion notification from non-IP-aware congested nodes up to the transport layer (L4). Following these guidelines should assure interworking among IP layer and lower layer congestion notification mechanisms, whether specified by the IETF or other standards bodies. This document updates the advice to subnetwork designers about ECN in RFC 3819.}, }