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

Document Type Replaced Internet-Draft (individual)
Last updated 2014-09-05 (latest revision 2014-03-04)
Replaced by draft-ietf-tsvwg-ecn-encap-guidelines
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-ecn-encap-guidelines
Telechat date
Responsible AD (None)
Send notices to (None)

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-briscoe-tsvwg-ecn-encap-guidelines-04.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 between new lower layer congestion notification mechanisms, whether specified by the IETF or other standards bodies.

Authors

Bob Briscoe (bob.briscoe@bt.com)
John Kaippallimalil (john.kaippallimalil@huawei.com)
Patricia Thaler (pthaler@broadcom.com)

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