Search RFCs
RFC 8311
Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation,January 2018
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 3168,RFC 4341,RFC 4342,RFC 5622,RFC 6679
- Author:
- D. Black
- Stream:
- IETF
- Source:
- tsvwg (wit)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8311
Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8311
Abstract
This memo updates RFC 3168, which specifies Explicit CongestionNotification (ECN) as an alternative to packet drops for indicatingnetwork congestion to endpoints. It relaxes restrictions in RFC 3168that hinder experimentation towards benefits beyond just removal ofloss. This memo summarizes the anticipated areas of experimentationand updates RFC 3168 to enable experimentation in these areas. AnExperimental RFC in the IETF document stream is required to takeadvantage of any of these enabling updates. In addition, this memomakes related updates to the ECN specifications for RTP in RFC 6679and for the Datagram Congestion Control Protocol (DCCP) in RFCs 4341,4342, and 5622. This memo also records the conclusion of the ECNnonce experiment in RFC 3540 and provides the rationale forreclassification of RFC 3540 from Experimental to Historic; thisreclassification enables new experimental use of the ECT(1)codepoint.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.