DualQ Coupled AQMs for Low Latency, Low Loss and Scalable Throughput (L4S)
draft-ietf-tsvwg-aqm-dualq-coupled-10

Document Type Expired Internet-Draft (tsvwg WG)
Last updated 2020-01-09 (latest revision 2019-07-08)
Replaces draft-briscoe-tsvwg-aqm-dualq-coupled
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document (wg milestone: Jun 2019 - Submit "DualQ Couple... )
Document shepherd Wesley Eddy
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Wesley Eddy <wes@mti-systems.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-tsvwg-aqm-dualq-coupled-10.txt

Abstract

The Low Latency Low Loss Scalable Throughput (L4S) architecture allows data flows over the public Internet to achieve consistent ultra-low queuing latency, generally zero congestion loss and scaling of per-flow throughput without the scaling problems of traditional TCP. To achieve this, L4S data flows have to use one of the family of 'Scalable' congestion controls (Data Centre TCP and TCP Prague are examples) and a form of Explicit Congestion Notification (ECN) with modified behaviour. However, until now, Scalable congestion controls did not co-exist with existing TCP Reno/Cubic traffic --- Scalable controls are so aggressive that 'Classic' TCP algorithms drive themselves to a small capacity share. Therefore, until now, L4S controls could only be deployed where a clean-slate environment could be arranged, such as in private data centres (hence the name DCTCP). This specification defines `DualQ Coupled Active Queue Management (AQM)', which enables these Scalable congestion controls to safely co-exist with Classic Internet traffic. Analytical study and implementation testing of the Coupled AQM have shown that Scalable and Classic flows competing under similar conditions run at roughly the same rate. It achieves this indirectly, without having to inspect transport layer flow identifiers. When tested in a residential broadband setting, DCTCP also achieves sub-millisecond average queuing delay and zero congestion loss under a wide range of mixes of DCTCP and `Classic' broadband Internet traffic, without compromising the performance of the Classic traffic. The solution also reduces network complexity and requires no configuration for the public Internet.

Authors

Koen Schepper (koen.de_schepper@nokia.com)
Bob Briscoe (ietf@bobbriscoe.net)
Greg White (g.white@cablelabs.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)