Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
draft-floyd-ecn-alternates-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Sally Floyd | ||
| Last updated | 2005-08-19 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
ps
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-floyd-ecn-alternates-02.txt
Abstract
There have been a number of proposals for alternate semantics for the ECN field in the IP header [ECN]. This document discusses some of the issues in defining alternate semantics for the ECN field, and specifies requirements for a safe co-existence in an Internet that could include routers that do not understand the defined alternate semantics. This document evolved as a result of discussions with the authors of one recent proposal for such alternate semantics.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)