Re: [tsvwg] path forward on L4S issue #16

[Sebastian Moeller <[e-mail]>]

Hi Ingemar,

to gently push back on some details.

> On Jun 10, 2020, at 15:59, Ingemar Johansson S <[e-mail]> wrote:
> 
> [...]I understand that traffic shaping on outgoing interfaces can be
> applied in a Linux host but don't see why they become a problem especially
> as there are qdiscs that support dualQ.
> [...]

	There seems to be a single out-of-the-mainline-Linux-tree repository (https://github.com/L4STeam/linux) for both the dual queue coupled AQM and TCP Prague. 
	I would not call that prrof of sufficient existence of "qdiscs that support dualQ" to allow Linux system admins to switch over to dualqand I do not see how even inclusion into the mainline kernel* would this solves the issue for currently deployed Linux machines, which often use vendor kernels which do not necessarily track mainline closely, especially for server distributions.
	I would respectfully argue that for safety considerations one should look at the current state of the internet and not potential less problematic states one would like to find the internet in...

Best Regards
	Sebastian


*) As far as I can tell there have been no attempts at upstreaming the dual queue coupled AQM yet, so it is not clear what/if survives the contact with the linux kernel maintainers.