The Benefits of Using Explicit Congestion Notification (ECN)
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 19
- Abstract
- The goal of this document is to describe the potential benefits of applications using a transport that enables Explicit Congestion Notification (ECN). The document outlines the principal gains in terms of increased throughput, reduced delay, and other benefits when ECN is used over a network path that includes equipment that supports Congestion Experienced (CE) marking. It also discusses challenges for successful deployment of ECN. It does not propose new algorithms to use ECN nor does it describe the details of implementation of ECN in endpoint devices (Internet hosts), routers, or other network devices.
- Publication Date
- 2017-03-01
- Status Note
- Informational
- DOI
10.17487/RFC8087- Link
- https://doi.org/10.17487/RFC8087
- Author(s)
- Gorry FairhurstMichael Welzl
- Keyword(s)
- ECN, AQM, SCTP, TCP
Latest version of IETF RFC 8087
Document Versions — IETF RFC 8087
-
▶ IETF RFC 8087 (2017-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2474 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 6040 [Active*]
- IETF RFC 7567 [Active*]
- IETF RFC 8085 [Active*]
Bibliographic Reference(s)
- 10.1007-978-3-319-15509-8_15 — TR15 EXTERNAL
- 10.1145-1851182.1851192 — DCTCP EXTERNAL
- 10.1145-2068816.2068833 — BA11 EXTERNAL
- 10.1145-2534169.2486014 — Fla13 EXTERNAL
- IETF draft-bensley-tcpm-dctcp-05 [Active*]
- IETF.draft-ietf-tcpm-accurate-ecn-02 — ECN-FEEDBACK EXTERNAL
- IETF.draft-ietf-tsvwg-ecn-encap-guidelines-07 — ECN EXTERNAL
- IETF.draft-kuehlewind-tcpm-ecn-fallback-01 — ECN-FALLBACK EXTERNAL
- IETF.draft-stewart-tsvwg-sctpecn-05 — SCTP-ECN EXTERNAL
- IETF RFC 768 [Active*]
- IETF RFC 1349 [Superseded*]
- IETF RFC 3649 [Active*]
- IETF RFC 3758 [Active*]
- IETF RFC 4340 [Active*]
- IETF RFC 4774 [Active*]
- IETF RFC 5562 [Active*]
- IETF RFC 5681 [Active*]
- IETF RFC 6679 [Active*]
- IETF RFC 6789 [Active*]
- IETF RFC 7928 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8087.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 8087, The Benefits of Using Explicit Congestion Notification (ECN). Available at https://doi.org/10.17487/RFC8087
Snippet:
IETF RFC 8087, The Benefits of Using Explicit Congestion Notification (ECN). Available at https://doi.org/10.17487/RFC8087
HTML (ISO 690 compliant)
Preview:
IETF RFC 8087, The Benefits of Using Explicit Congestion Notification (ECN). Available at https://doi.org/10.17487/RFC8087
Snippet:
<span class="citation"><cite>IETF RFC 8087</cite>, The Benefits of Using Explicit Congestion Notification (ECN). Available at <a href="https://doi.org/10.17487/RFC8087" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8087</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8087, The Benefits of Using Explicit Congestion Notification (ECN)
doi: 10.17487/RFC8087
url: https://doi.org/10.17487/RFC8087
doi: 10.17487/RFC8087
url: https://doi.org/10.17487/RFC8087
Snippet:
<li> <cite id="bib-rfc8087">IETF RFC 8087</cite>, The Benefits of Using Explicit Congestion Notification (ECN) <span class="doi">10.17487/RFC8087</span> </li>
Referenced By
- IETF RFC 8085 [Active*]
- IETF RFC 8504 [Active*]
- IETF RFC 8511 [Active*]
- IETF RFC 8622 [Active*]
- IETF RFC 8931 [Active*]
- IETF RFC 9000 [Active*]
- IETF RFC 9065 [Active*]
- IETF RFC 9293 [Active*]
- IETF RFC 9599 [Active*]
- IETF RFC 9601 [Active*]
- IETF RFC 9743 [Active*]