Updating the Explicit Congestion Notification (ECN) Specification to Allow IETF Experimentation

Document Type Expired Internet-Draft (individual)
Last updated 2017-01-21 (latest revision 2016-07-20)
Replaces draft-khademi-alternativebackoff-ecn
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document relaxes recommendations and prescriptions from RFC3168 and RFC4774 that get in the way of experimentation with different ECN strategies. First, RFC3168 and RFC4774 state that, upon the receipt by an ECN-Capable transport of a single CE packet, the congestion control algorithms followed at the end-systems MUST be essentially the same as the congestion control response to a single dropped packet. This document relaxes this rule in order to encourage experimentation with different backoff strategies. Second, this document allows future IETF specifications to use the ECT(1) codepoint in ways that are currently prohibited by RFC3168. Third, this document allows future IETF experiments to use the ECT(0) or ECT(1) codepoint on any TCP segment.


Naeem Khademi (naeemk@ifi.uio.no)
Michael Welzl (michawe@ifi.uio.no)
Grenville Armitage (garmitage@swin.edu.au)
Gorry Fairhurst (gorry@erg.abdn.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)