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

Sebastian Moeller <moeller0@gmx.de> Wed, 10 June 2020 14:34 UTC

Return-Path: <moeller0@gmx.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C156B3A08EB for <tsvwg@ietfa.amsl.com>; Wed, 10 Jun 2020 07:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBqum8yTtU3r for <tsvwg@ietfa.amsl.com>; Wed, 10 Jun 2020 07:34:53 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA4F93A08E4 for <tsvwg@ietf.org>; Wed, 10 Jun 2020 07:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1591799688; bh=SoGhipAMGHcSo7AiJlXCG/PF3r92Mxb48HAmy1w5oGM=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=U3VMWp7UCXqQoe0NlmoAgoZU3iGxjm6jw8eqlOd6W9wpyjfKFgB3BaVAhcYNYNiYH chox2iEpWXMtlLkUUPu2xwsT4eSMzkJwt7W3LZTUCY64KFziVHLRaDUZxtDcLe+JUu C1VMsK1hxigTsqRcGBi1TCuhvWBudlgcvoPYqAB8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [10.11.12.3] ([134.76.241.253]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MOiHf-1jZt1b1K8d-00QAMC; Wed, 10 Jun 2020 16:34:48 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <HE1PR0701MB2876726FC67BD2850B5D39FAC2830@HE1PR0701MB2876.eurprd07.prod.outlook.com>
Date: Wed, 10 Jun 2020 16:34:46 +0200
Cc: Jonathan Morton <chromatix99@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E17FCDCD-6D2D-4773-98AA-44EB54A79F62@gmx.de>
References: <HE1PR0701MB2876AA3CBBA215B9FB895B0AC2820@HE1PR0701MB2876.eurprd07.prod.outlook.com> <3637517F-63A0-4862-9885-AB5EA7E6C273@gmail.com> <VI1PR0701MB2877E21B7F406C3DFCFF08BCC2820@VI1PR0701MB2877.eurprd07.prod.outlook.com> <92525827-39B6-4E88-B453-660F8FE22523@gmx.de> <VI1PR0701MB287768D465C37DC46A459C12C2820@VI1PR0701MB2877.eurprd07.prod.outlook.com> <57D7632A-594E-47BC-B6B0-5FBC22AAFE37@gmail.com> <DF67B660-DE2B-4EB8-AD77-5FECF27D1BAC@gmx.de> <HE1PR0701MB287679D1842F15FCDAC6223EC2820@HE1PR0701MB2876.eurprd07.prod.outlook.com> <7EEF7075-396F-4565-89C6-674CBB1E6CB8@gmx.de> <HE1PR0701MB28767A1E570A705EBC65EFC4C2830@HE1PR0701MB2876.eurprd07.prod.outlook.com> <5ADEBD56-1A2C-4C34-9132-E50A4A7A4A42@gmx.de> <HE1PR0701MB287695F2245A480A43DB5F9BC2830@HE1PR0701MB2876.eurprd07.prod.outlook.com> <EEB9B5D1-5F06-4BA6-A078-BE9C26D0EAD6@gmail.com> <HE1PR0701MB2876726FC67BD2850B5D39FAC2830@HE1PR0701MB2876.eurprd07.prod.outlook.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-Provags-ID: V03:K1:5jM5hEuktImcHRvAkT/tDveuKILIAeLNYbGvq7Jfz8SxetpZ/Ab rsuYSbaIGN4rAFmbWsNfVfl7qji2HN++A6+kv88/a0mx74piEr7ml0Ihlgft5rHNPwG3sYu GLQiPEzYuP1dlPuDVaThcW31PSIRsVfzo87lMdJuBX1UnNjJ5DwDeaLYTBiha3vVxsQxiPs C+14lcITXfWNpr5qr4tYw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:LOxpTix5B6g=:wNpeiX5Da5YJS8LGXCTe/I VhU/r4BZPgPwBC+HJfkTGhJZ4IP/OMz+icBVm2wVMsnnTm7Rxuv5+3yvJzUSC5IvPD1oG+Vde A34ShyFBsTEuYdbQ4SjraVZmAvpdstGEoFLQV4+Gk3YaysctO8eMiek3oz3lYrdtqJk2ar1Ay yIimvLO0TJSCA5kTFIZCakq6dzWk+kXdqt1jZgz4PAG5FSC3vxXBZb4AnXd8lj5TpgZON7ttF c1fEg8MN+U9SccPn33kruM/ehj5KRXWqd5vPGw94+G/qb3Nok6n0KUCTfI4AdWbwumCo0I6ri O/cuzHOhNQ5JOwOW/dFBjlyDlemzldGeGqht5Hi3+tzptVPI2t7N80UtPin8dPdz7giNOD+mx L5ISx0k6DbmflIMNa8/UPlyYji0DOK9lpL6Mc2P239cvwKvoNBaTFAa1V/mYQUt5fNxFRxDDf 2ePJ1uBym8dA66mZRY8VgDd6siQ6dL+/jCIBSFo9Ph3iWIUGa2hpuUMxBecjSx7S+tIK3v6PR Xj6F0tC18DX6xJpT+GbWuE8QAPDgeQ3+rH5zZ23TnEzzG4swwc8xilf8xkpRykAmecyVjeag5 uwKY1tCiWevf7xJAh9uPpOVqfUtJYsZlP0kj/3ui1glbLijWi4hb3TFIOA4P/veRcoNI0wXZc traQHCjF2g/xce0hx2e6R2AOg4T97p1lnaxuMolq7uS9yGwS82vimhcNVZ+S0vGJGFKDuFD2v TyvHVSwxWrmbVZc02SZYHFg64W/jAWqWUbTllpdUOpBnc75gB/pOv5l5nBS/FdRwXEqc2v6/a sznKEAqe9z8k0sf/v8LX7SXfhYyLh+OgMm3yIPBradISC3W71ebJOnRK6h4Ry0JynhfGXMpQW JBrigrvfnZJnfKYYf8wqr8HrfsyRKdWmh1mrOGyJtgBhvOUo4CPVby9hGeJ24L7gaHMAfY7Nv sc3iF7/aSPp02/1vMsRpzruO2FLXz0aqVfT2ThroSpm1z7sltI2lQborG5OO1jcJOLz1i61Gq hBx71OiAqcpZIRmf+MwXQSwAmHIhYOLbVCT5qaJ1ZffkbC5dL52dNCh9i9ru3PI0xRTuw07PZ jHJr9pI/FICIy24hyuYDQMqvs9f++OXn2XSVy4mMhHPX7+2xSeZEur8shd9wNIluwVGEiMj6+ lsGSKJYGQhYjPVGIfKTpAit1a1G4kzEMH/ypN/uFWGOEzW2nvhDHwAXI3Mny2Z9+3IVRXJjGO p6jrMj6JJ7v3Of2pq
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/tyn0vWtFKrae5tm5xkapKK1fq1k>
Subject: Re: [tsvwg] path forward on L4S issue #16
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2020 14:34:55 -0000

Hi Ingemar,

to gently push back on some details.

> On Jun 10, 2020, at 15:59, Ingemar Johansson S <ingemar.s.johansson@ericsson.com> 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.