%% You should probably cite draft-ietf-tcpm-accurate-ecn instead of this I-D. @techreport{kuehlewind-tcpm-accurate-ecn-02, number = {draft-kuehlewind-tcpm-accurate-ecn-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-kuehlewind-tcpm-accurate-ecn/02/}, author = {Mirja Kühlewind and Richard Scheffenegger}, title = {{More Accurate ECN Feedback in TCP}}, pagetotal = 14, year = 2013, month = jun, day = 20, abstract = {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. ECN-capable receivers 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 document specifies a different scheme for the ECN feedback in the TCP header to provide more than one feedback signal per RTT. Furthermore this document specifies a re-use of the Urgent Pointer in the TCP header if the URG flag is not set to increase the robustness of the proposed ECN feedback scheme.}, }