Skip to main content

Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Bob Briscoe , John Kaippallimalil
Last updated 2023-08-23 (Latest revision 2022-07-11)
Replaces draft-briscoe-tsvwg-ecn-encap-guidelines
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Revised I-D Needed - Issue raised by WG, Doc Shepherd Follow-up Underway
Associated WG milestone
Apr 2023
Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC
Document shepherd David L. Black
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to "David Black" <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Bob Briscoe
John Kaippallimalil

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)