RFC 8511: TCP Alternative Backoff with ECN (ABE)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8511
- Published
- December 2018
- Authors
- N. Khademi; M. Welzl; G. Armitage; G. Fairhurst
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8516"Too Many Requests" Response Code for the Constrained Application ProtocolCurrent
January 2019
- RFC 8540Stream Control Transmission Protocol: Errata and Issues in RFC 4960Obsoleted
February 2019
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 8441Bootstrapping WebSockets with HTTP/2Current
September 2018
- RFC 8586Loop Detection in Content Delivery Networks (CDNs)Current
April 2019
- RFC 8436Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) RegistryCurrent
August 2018
- RFC 8435Parallel NFS (pNFS) Flexible File LayoutCurrent
August 2018
- RFC 8587NFS Version 4.0 Trunking UpdateCurrent
May 2019
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?