Skip to main content

More Accurate ECN Feedback in TCP
draft-kuehlewind-tcpm-accurate-ecn-05

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Bob Briscoe , Mirja Kühlewind , Richard Scheffenegger
Last updated 2015-10-19
Replaced by draft-ietf-tcpm-accurate-ecn
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tcpm-accurate-ecn
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:

Abstract

Explicit Congestion Notification (ECN) is a mechanism where network nodes can mark IP packets instead of dropping them to indicate incipient congestion to the end-points. Receivers with an ECN- capable transport protocol feed back 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 Congestion Exposure (ConEx) or Data Center TCP (DCTCP) need more accurate ECN feedback information whenever more than one marking is received in one RTT. This document specifies an experimental scheme to provide more than one feedback signal per RTT in the TCP header. Given TCP header space is scarce, it overloads the three existing ECN-related flags in the TCP header and provides additional information in a new TCP option.

Authors

Bob Briscoe
Mirja Kühlewind
Richard Scheffenegger

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