DualQ Coupled AQMs for Low Latency, Low Loss and Scalable Throughput (L4S)
draft-ietf-tsvwg-aqm-dualq-coupled-08
| Document | Type | Expired Internet-Draft (tsvwg WG) | |
|---|---|---|---|
| Authors | Koen De Schepper , Bob Briscoe , Olga Bondarenko , Ing Jyh Tsang | ||
| Last updated | 2019-05-08 (Latest revision 2018-11-04) | ||
| Replaces | draft-briscoe-tsvwg-aqm-dualq-coupled | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | Wesley Eddy | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | Wesley Eddy <wes@mti-systems.com> |
https://www.ietf.org/archive/id/draft-ietf-tsvwg-aqm-dualq-coupled-08.txt
Abstract
The Low Latency Low Loss Scalable Throughput (L4S) architecture allows data flows over the public Internet to predictably achieve ultra-low queuing latency, generally zero congestion loss and scaling of per-flow throughput without the problems of traditional TCP. To achieve this, L4S data flows use a 'scalable' congestion control similar to Data Centre TCP (DCTCP) 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 starvation. 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. The Coupled AQM ensures that a flow runs at about the same rate whether it uses DCTCP or TCP Reno/Cubic. 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 eliminates network configuration.
Authors
Koen De Schepper
Bob Briscoe
Olga Bondarenko
Ing Jyh Tsang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)