Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
draft-briscoe-tsvwg-ecn-encap-guidelines-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Bob Briscoe | ||
| Last updated | 2011-03-02 | ||
| Replaced by | draft-ietf-tsvwg-ecn-encap-guidelines | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The purpose of this document is to guide the design of congestion notification in any lower layer 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 to the destination transport endpoint. Following these guidelines should assure interworking between new encapsulations of congestion notification, whether specified by the IETF or other standards bodies.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)