Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 17
- Abstract
- 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.
- Publication Date
- 2015-08-01
- Status Note
- Informational
- DOI
10.17487/RFC7560- Link
- https://doi.org/10.17487/RFC7560
- Author(s)
- Mirja KühlewindRichard ScheffeneggerBob Briscoe
- Keyword(s)
- Congestion Control, TCP
Latest version of IETF RFC 7560
Document Versions — IETF RFC 7560
-
▶ IETF RFC 7560 (2015-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 3168 [Active*]
- IETF RFC 3540 [Active*]
Bibliographic Reference(s)
- IETF.draft-bensley-tcpm-dctcp-05 — DCTCP EXTERNAL
- IETF.draft-ietf-aqm-ecn-benefits-06 — ECN-BENEFITS EXTERNAL
- IETF.draft-moncaster-tcpm-rcv-cheat-03 — TEST-RCV EXTERNAL
- IETF.draft-stewart-tsvwg-sctpecn-05 — SCTP-ECN EXTERNAL
- IETF RFC 896 [Superseded*]
- IETF RFC 2018 [Active*]
- IETF RFC 3449 [Active*]
- IETF RFC 5681 [Active*]
- IETF RFC 5690 [Active*]
- IETF RFC 6093 [Superseded*]
- IETF RFC 6679 [Active*]
- IETF RFC 6789 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7560.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7560, Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback. Available at https://doi.org/10.17487/RFC7560
Snippet:
IETF RFC 7560, Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback. Available at https://doi.org/10.17487/RFC7560
HTML (ISO 690 compliant)
Preview:
IETF RFC 7560, Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback. Available at https://doi.org/10.17487/RFC7560
Snippet:
<span class="citation"><cite>IETF RFC 7560</cite>, Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback. Available at <a href="https://doi.org/10.17487/RFC7560" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7560</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7560, Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback
doi: 10.17487/RFC7560
url: https://doi.org/10.17487/RFC7560
doi: 10.17487/RFC7560
url: https://doi.org/10.17487/RFC7560
Snippet:
<li> <cite id="bib-rfc7560">IETF RFC 7560</cite>, Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback <span class="doi">10.17487/RFC7560</span> </li>
Referenced By
- IETF RFC 8085 [Active*]
- IETF RFC 9768 [Active*]