Specifying Alternate Semantics for the Explicit Congestion Notification Field
RFC 4774, “Specifying Alternate Semantics for the Explicit Congestion Notification Field”, is a Best Current Practice document published in November 2006 by S. Floyd. It has since been updated by RFC 6040. The canonical text is published by the RFC Editor.
Abstract
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 4774 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4773 Administration of the IANA Special Purpose IPv6 Address Block
- RFC 4775 Procedures for Protocol Extensions and Variations
- RFC 4772 Security Implications of Using the Data Encryption Standard
- RFC 4776 Dynamic Host Configuration Protocol Option for Civic Addresses Configuration Information
- RFC 4777 IBM's iSeries Telnet Enhancements
- RFC 4769 IANA Registration for an Enumservice Containing Public Switched Telephone Network Signaling Information
- RFC 4768 Desired Enhancements to Generic Security Services Application Program Interface Version 3 Naming
- RFC 4783 GMPLS - Communication of Alarm Information