Low Latency, Low Loss Scalable throughput (L4S) is being proposed as the new default Internet service. L4S can be considered as an `incrementally deployable clean-slate' for new Internet flow-rate control mechanisms. Because, for a brief period, researchers are free to develop host and network mechanisms in tandem, somewhat unconstrained by any pre-existing legacy.
Scaling requirements represent the main constraints on a clean-slate design space. This document confines its scope to the steady state. It aims to resolve the tensions between a number of apparently conflicting scalability requirements for L4S congestion controllers. It has been produced to inform and provide structure to the debate as researchers work towards pre-standardization consensus on this issue.
This work is important, because clean-slate opportunities like this arise only rarely and will only be available briefly---for roughly one year. The decisions we make now will tend to dirty the slate again, probably for many decades.
[1]
Adel Javanmard,et al.
Analysis of DCTCP: stability, convergence, and fairness
,
2011,
SIGMETRICS.
[2]
Sally Floyd,et al.
Comments on the Usefulness of Simple Best-Effort Traffic
,
2008,
RFC.
[3]
Bob Briscoe,et al.
‘ Data Centre to the Home ’ : Ultra-Low Latency for All
,
2015
.
[4]
Bob Briscoe,et al.
Scaling TCP's Congestion Window for Small Round Trip Times
,
2019,
ArXiv.
[5]
Bob Briscoe,et al.
Flow rate fairness: dismantling a religion
,
2007,
CCRV.
[6]
David L. Black,et al.
The Addition of Explicit Congestion Notification (ECN) to IP
,
2001,
RFC.
[7]
Vern Paxson,et al.
TCP Congestion Control
,
1999,
RFC.