Skip to main content

Problem Statement and Requirements for a More Accurate ECN Feedback

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Mirja Kühlewind , Richard Scheffenegger
Last updated 2013-05-13 (Latest revision 2012-10-15)
Replaced by draft-ietf-tcpm-accecn-reqs
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tcpm-accecn-reqs
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Explicit Congestion Notification (ECN) is an IP/TCP mechanism where network nodes can mark IP packets instead of dropping them to indicate congestion to the end-points. An ECN-capable receiver will feedback this information to the sender. ECN is specified for TCP in such a way that only one feedback signal can be transmitted per Round-Trip Time (RTT). Recently, new TCP mechanisms like ConEx or DCTCP need more accurate ECN feedback information in the case where more than one marking is received in one RTT. This documents specifies requirement for different ECN feedback scheme in the TCP header to provide more than one feedback signal per RTT.


Mirja Kühlewind
Richard Scheffenegger

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