TCP Alternative Backoff with ECN (ABE)
Metadata
- Publisher
- IETF
- Doc Type
- Experimental
- Pages
- 12
- Abstract
- Active Queue Management (AQM) mechanisms allow for burst tolerance while enforcing short queues to minimise the time that packets spend enqueued at a bottleneck. This can cause noticeable performance degradation for TCP connections traversing such a bottleneck, especially if there are only a few flows or their bandwidth-delay product (BDP) is large. The reception of a Congestion Experienced (CE) Explicit Congestion Notification (ECN) mark indicates that an AQM mechanism is used at the bottleneck, and the bottleneck network queue is therefore likely to be short. Feedback of this signal allows the TCP sender-side ECN reaction in congestion avoidance to reduce the Congestion Window (cwnd) by a smaller amount than the congestion control algorithm's reaction to inferred packet loss. Therefore, this specification defines an experimental change to the TCP reaction specified in RFC 3168, as permitted by RFC 8311.
- Publication Date
- 2018-12-01
- Status Note
- Experimental
- DOI
10.17487/RFC8511- Link
- https://doi.org/10.17487/RFC8511
- Author(s)
- Naeem KhademiMichael WelzlGrenville ArmitageGorry Fairhurst
Latest version of IETF RFC 8511
Document Versions — IETF RFC 8511
-
▶ IETF RFC 8511 (2018-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 5681 [Active*]
- IETF RFC 7567 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8257 [Active*]
- IETF RFC 8311 [Active*]
Bibliographic Reference(s)
- 10.1109-ICC.2002.997262 — ICC2002 EXTERNAL
- 10.1145-2063166.2071893 — BUFFERBLOAT EXTERNAL
- 10.23919-IFIPNetworking.2017.8264863 — ABE2017 EXTERNAL
- IETF.draft-ietf-tcpm-accurate-ecn-07 — ACC-ECN-FEEDBACK EXTERNAL
- Stewart, L., "ABE patch review in FreeBSD", Revision 331214, March 2018, < https://svnweb.freebsd.org/ base?view=revision&revision=331214 >. EXTERNAL
- IETF RFC 8033 [Active*]
- IETF RFC 8087 [Active*]
- IETF RFC 8289 [Active*]
- IETF RFC 8312 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8511.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 8511, TCP Alternative Backoff with ECN (ABE). Available at https://doi.org/10.17487/RFC8511
Snippet:
IETF RFC 8511, TCP Alternative Backoff with ECN (ABE). Available at https://doi.org/10.17487/RFC8511
HTML (ISO 690 compliant)
Preview:
IETF RFC 8511, TCP Alternative Backoff with ECN (ABE). Available at https://doi.org/10.17487/RFC8511
Snippet:
<span class="citation"><cite>IETF RFC 8511</cite>, TCP Alternative Backoff with ECN (ABE). Available at <a href="https://doi.org/10.17487/RFC8511" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8511</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8511, TCP Alternative Backoff with ECN (ABE)
doi: 10.17487/RFC8511
url: https://doi.org/10.17487/RFC8511
doi: 10.17487/RFC8511
url: https://doi.org/10.17487/RFC8511
Snippet:
<li> <cite id="bib-rfc8511">IETF RFC 8511</cite>, TCP Alternative Backoff with ECN (ABE) <span class="doi">10.17487/RFC8511</span> </li>
Referenced By
- IETF RFC 9002 [Active*]
- IETF RFC 9330 [Active*]
- IETF RFC 9331 [Active*]
- IETF RFC 9438 [Active*]
- IETF RFC 9768 [Active*]