Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|Authors||Bob Briscoe , John Kaippallimalil , Patricia Thaler|
|Last updated||2014-09-08 (Latest revision 2014-03-07)|
|RFC stream||Internet Engineering Task Force (IETF)|
GENART Last Call review (of -20) by Susan Hares Ready w/issues
ARTART Last Call review (of -20) by Paul Kyzivat Ready w/nits
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Associated WG milestone||
|Send notices to||(None)|
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 between new lower layer congestion notification mechanisms, whether specified by the IETF or other standards bodies.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)