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

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9332

        Title:      Dual-Queue Coupled Active Queue Management (AQM) for
                    Low Latency, Low Loss, and Scalable Throughput (L4S)
        Author:     K. De Schepper,
                    B. Briscoe, Ed.,
                    G. White
        Status:     Experimental
        Stream:     IETF
        Date:       January 2023
        Mailbox:    [email protected],
                    [email protected],
                    [email protected]
        Pages:      52
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-aqm-dualq-coupled-25.txt

        URL:        https://www.rfc-editor.org/info/rfc9332

        DOI:        10.17487/RFC9332

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.

This document is a product of the Transport Area Working Group Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC