Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
draft-ietf-tsvwg-ecn-encap-guidelines-16

Document Type Expired Internet-Draft (tsvwg WG)
Authors Bob Briscoe , John Kaippallimalil
Last updated 2021-11-26 (Latest revision 2021-05-25)
Replaces draft-briscoe-tsvwg-ecn-encap-guidelines
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Doc Shepherd Follow-up Underway
Associated WG milestone
Apr 2022
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" <david.black@dell.com>
Email authors Email WG IPR References Referenced by Nits
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ietf-tsvwg-ecn-encap-guidelines-16.txt

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.

Authors

Bob Briscoe
John Kaippallimalil

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