API Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 9331
[ACTIVE]

The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)

Metadata

Publisher
IETF
Doc Type
Experimental
Pages
52
Abstract
This specification defines the protocol to be used for a new network service called Low Latency, Low Loss, and Scalable throughput (L4S). L4S uses an Explicit Congestion Notification (ECN) scheme at the IP layer that is similar to the original (or 'Classic') ECN approach, except as specified within. L4S uses 'Scalable' congestion control, which induces much more frequent control signals from the network, and it responds to them with much more fine-grained adjustments so that very low (typically sub-millisecond on average) and consistently low queuing delay becomes possible for L4S traffic without compromising link utilization. Thus, even capacity-seeking (TCP-like) traffic can have high bandwidth and very low delay at the same time, even during periods of high traffic load. The L4S identifier defined in this document distinguishes L4S from 'Classic' (e.g., TCP-Reno-friendly) traffic. Then, network bottlenecks can be incrementally modified to distinguish and isolate existing traffic that still follows the Classic behaviour, to prevent it from degrading the low queuing delay and low loss of L4S traffic. This Experimental specification defines the rules that L4S transports and network elements need to follow, with the intention that L4S flows neither harm each other's performance nor that of Classic traffic. It also suggests open questions to be investigated during experimentation. Examples of new Active Queue Management (AQM) marking algorithms and new transports (whether TCP-like or real time) are specified separately.
Publication Date
2023-01-01
Status Note
Experimental
DOI
10.17487/RFC9331
Link
https://doi.org/10.17487/RFC9331
Author(s)
Koen De Schepper
Bob Briscoe
Keyword(s)
Burstiness, Queuing Delay, One-way Delay, RTT, Jitter, Congestion Control, Congestion Avoidance, Quality Of Service, QoS, Quality of Experience, QoE, AQM, ECN, Pacing
Latest version of IETF RFC 9331

Document Versions — IETF RFC 9331

  • ▶ IETF RFC 9331 (2023-01-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC9331.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 9331, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S). Available at https://doi.org/10.17487/RFC9331
Snippet:
IETF RFC 9331, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S). Available at https://doi.org/10.17487/RFC9331

HTML (ISO 690 compliant)

Preview:
IETF RFC 9331, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S). Available at https://doi.org/10.17487/RFC9331
Snippet:
<span class="citation"><cite>IETF RFC 9331</cite>, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S). Available at <a href="https://doi.org/10.17487/RFC9331" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9331</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 9331, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
doi: 10.17487/RFC9331
url: https://doi.org/10.17487/RFC9331
Snippet:
<li>
<cite id="bib-rfc9331">IETF RFC 9331</cite>, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
<span class="doi">10.17487/RFC9331</span>
</li>

Referenced By