Skip to main content

Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)
RFC 9332

Revision differences

Document history

Date By Action
2023-01-19
(System)
Received changes through RFC Editor sync (created alias RFC 9332, changed title to 'Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, …
Received changes through RFC Editor sync (created alias RFC 9332, changed title to 'Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)', changed abstract to 'This specification defines a framework for coupling the Active Queue Management (AQM) algorithms in two queues intended for flows with different responses to congestion. This provides a way for the Internet to transition from the scaling problems of standard TCP-Reno-friendly ('Classic') congestion controls to the family of 'Scalable' congestion controls. These are designed for consistently very low queuing latency, very low congestion loss, and scaling of per-flow throughput by using Explicit Congestion Notification (ECN) in a modified way. Until the Coupled Dual Queue (DualQ), these Scalable L4S congestion controls could only be deployed where a clean-slate environment could be arranged, such as in private data centres.

This specification first explains how a Coupled DualQ works. It then gives the normative requirements that are necessary for it to work well. All this is independent of which two AQMs are used, but pseudocode examples of specific AQMs are given in appendices.', changed pages to 52, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2023-01-19, changed IESG state to RFC Published)
2023-01-19
(System) RFC published