RFC 7560: Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback
In plain English — editorial summary, not part of the RFC
Explicit Congestion Notification (ECN) is a mechanism where network nodes can mark IP packets, instead of dropping them, to indicate congestion to the endpoints. An ECN-capable receiver will feed this information back to the sender. ECN is specified for TCP in such a way that it can only feed back one congestion signal per Round-Trip Time (RTT). In contrast, ECN for other transport protocols, such as RTP/UDP and SCTP, is specified with more accurate ECN feedback. Recent new TCP mechanisms (like Congestion Exposure (ConEx) or Data Center TCP (DCTCP)) need more accurate ECN feedback in the case where more than one marking is received in one RTT. This document specifies requirements for an update to the TCP protocol to provide more accurate ECN feedback.
Document record
- Document ID
- RFC7560
- Published
- August 2015
- Authors
- M. Kuehlewind; R. Scheffenegger; B. Briscoe
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 9406HyStart++: Modified Slow Start for TCPCurrent
May 2023
- RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted
April 2003
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 2011
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?