RFC 8311

Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation, January 2018

Canonical URL:
https://www.rfc-editor.org/rfc/rfc8311.txt
File formats:
Plain TextPDF
Status:
PROPOSED STANDARD
Updates:
RFC 3168, RFC 4341, RFC 4342, RFC 5622, RFC 6679
Author:
D. Black
Stream:
IETF
Source:
tsvwg (tsv)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC8311

Discuss this RFC: Send questions or comments to tsvwg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

This memo updates RFC 3168, which specifies Explicit Congestion Notification (ECN) as an alternative to packet drops for indicating network congestion to endpoints. It relaxes restrictions in RFC 3168 that hinder experimentation towards benefits beyond just removal of loss. This memo summarizes the anticipated areas of experimentation and updates RFC 3168 to enable experimentation in these areas. An Experimental RFC in the IETF document stream is required to take advantage of any of these enabling updates. In addition, this memo makes related updates to the ECN specifications for RTP in RFC 6679 and for the Datagram Congestion Control Protocol (DCCP) in RFCs 4341, 4342, and 5622. This memo also records the conclusion of the ECN nonce experiment in RFC 3540 and provides the rationale for reclassification of RFC 3540 from Experimental to Historic; this reclassification enables new experimental use of the ECT(1) codepoint.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader