Hi Bob and all, see below.
Am 01.11.2016 um 01:02 schrieb Bob Briscoe: > A few people have been working away to specify and document all the > aspects of the new Low Latency, Low Loss, Scalable throughput (L4S) > service, which held a successful BoF in Berlin. As the decision was to > try to work across multiple WGs, I thought it would be useful to give ... Thanks for putting this together. > * Dual Queue Coupled AQM > o With Curvy RED for Linux (access available shortly) > o With PI2 for Linux <https://github.com/olgabo/dualpi2> [*UPDATED*] I'll repeat my concerns that I already expressed at the L4S BOF in Berlin: While I agree that we probably need to separate low-delay congestion control schemes from traditional "queue-filling" congestion schemes, I strongly suggest to avoid putting a congestion control-specific coupling scheme into the network (a classic case for applying the "end-to-end arguments in system design"). The current Dual queue coupled AQM proposal has got a coupling based on a congestion control specific dropping law p_C=(p_L/2)². So if congestion control schemes change then this coupling needs to be adapted. For example, the currently proposed scheme may fail if that vast majority of TCP traffic is using BBR other some other forthcoming CC scheme instead of Cubic, Reno, Compound etc. The same applies to draft-briscoe-tsvwg-ecn-l4s-id, section 2.5, where the dropping likelihood is defined. Regards, Roland _______________________________________________ aqm mailing list aqm@ietf.org https://www.ietf.org/mailman/listinfo/aqm
