Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field, November 2006
- File formats:
- BEST CURRENT PRACTICE
- Updated by:
- RFC 6040
- S. Floyd
- tsvwg (tsv)
Cite this BCP: TXT
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC
There have been a number of proposals for alternate semantics for the Explicit Congestion Notification (ECN) field in the IP header RFC 3168. This document discusses some of the issues in defining alternate semantics for the ECN field, and specifies requirements for a safe coexistence 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. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.