Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 9332

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

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XML
Also available:XML file for editing
 
Status:
EXPERIMENTAL
Authors:
K. De Schepper
B. Briscoe, Ed.
G. White
Stream:
IETF
Source:
tsvwg (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9332

Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9332


Abstract

This specification defines a framework for coupling the Active QueueManagement (AQM) algorithms in two queues intended for flows withdifferent responses to congestion. This provides a way for theInternet to transition from the scaling problems of standardTCP-Reno-friendly ('Classic') congestion controls to the family of'Scalable' congestion controls. These are designed for consistentlyvery low queuing latency, very low congestion loss, and scaling ofper-flow throughput by using Explicit Congestion Notification (ECN)in a modified way. Until the Coupled Dual Queue (DualQ), theseScalable L4S congestion controls could only be deployed where aclean-slate environment could be arranged, such as in private datacentres.

This specification first explains how a Coupled DualQ works. It thengives the normative requirements that are necessary for it to workwell. All this is independent of which two AQMs are used, butpseudocode examples of specific AQMs are given in appendices.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp