Re: [tsvwg] L4S DSCP (was: L4S drafts: Next Steps)

Jonathan Morton <chromatix99@gmail.com> Sun, 28 March 2021 21:30 UTC

Return-Path: <chromatix99@gmail.com>
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 4FBB13A2709 for <tsvwg@ietfa.amsl.com>; Sun, 28 Mar 2021 14:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 J2r13mOIbTvO for <tsvwg@ietfa.amsl.com>; Sun, 28 Mar 2021 14:30:06 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBC1C3A2706 for <tsvwg@ietf.org>; Sun, 28 Mar 2021 14:30:05 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id f16so13773709ljm.1 for <tsvwg@ietf.org>; Sun, 28 Mar 2021 14:30:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Jgt7shWQhtEPwd/YsqaicGPW5niSD8YQQMpTt9/GJ6o=; b=btMbkKKlwgWWE8YCtnGXoAa18RkjeSzhhvTk+i1jPszC4tuNACN0YIm37AW6YbJmBG /yseWBqkf0RKWA76lrSr71As250siERTvwjbXa5GOsOSkuKZ2Pp/JpnJ7ktv4mSVSOKA mxdY3yPmtgIVtfo58Zg7y/y3KKPVXns2iUnYptoUHK7CKq/bbqs0pxKj1TjkzRNC3PSN 6g54wS9m4IBCbkuNRYfaZVsfFnMNcvJv0389VEGnO5hHId2/5Ppe0nHGq6ZZ8JNWdALw rNnFreBr7dBOqR8ArY8A+NfktrQk9OKGPUg8oAt4J76qH/GjfcMRi9Zb6lMSDtMyGrdd hgnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Jgt7shWQhtEPwd/YsqaicGPW5niSD8YQQMpTt9/GJ6o=; b=QX0oki8ac0CELu3RjN4FFEPhA1X1zxhlbWXh5aFo4keravCO9bZBTN0/p+KXUDc6OD OmIzFsPyLUFV8qRc4t124dCgbyVuH66ZcgdQCKBBBKITeEjlcltxwQmADN5fiNNGzv2n hJKmkb5HxnGScFRMMP57JlRHBurQbpNsxbaKvyRI9QPN7k0O2pJI/eJwOVAJvkQ61MDr vyW9ml9w1KrfWVBBtFylRvU7soY9gbTTe05A2BIHq6WNkwM/fjFu7ymq6tdnwH6drlvU QjJGLKC9NP9AjMhw4iaBiM0keVKMlOBfPVj+l6Thx311dCLkHNccn76/wOUHYszPTDU3 E8rQ==
X-Gm-Message-State: AOAM530PgTGLF6Fhhs+Tzs+lrGfxLvrIF8ZgIzV1acE3bNx2giJ9vurT S+at848DRvHkhR/6iPZ4T/0=
X-Google-Smtp-Source: ABdhPJyZJjiqK0nGvTcrUOTghr3lg9tmBFa2YE+yVj6tE1j6VzMclvPToOWbWY3MFC6aqadQqO2hNg==
X-Received: by 2002:a2e:3016:: with SMTP id w22mr16638782ljw.354.1616967003238; Sun, 28 Mar 2021 14:30:03 -0700 (PDT)
Received: from jonathartonsmbp.lan (178-55-25-11.bb.dnainternet.fi. [178.55.25.11]) by smtp.gmail.com with ESMTPSA id s7sm1669176lfi.140.2021.03.28.14.30.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Mar 2021 14:30:02 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <HE1PR0701MB229922BAC35171679447AF3BC27F9@HE1PR0701MB2299.eurprd07.prod.outlook.com>
Date: Mon, 29 Mar 2021 00:30:01 +0300
Cc: Sebastian Moeller <moeller0@gmx.de>, Pete Heist <pete@heistp.net>, Kyle Rose <krose@krose.org>, "C. M. Heard" <heard@pobox.com>, "De Schepper, Koen (Nokia - BE/Antwerp)" <koen.de_schepper@nokia-bell-labs.com>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B459FC22-1F43-4812-951D-6247124417C4@gmail.com>
References: <MN2PR19MB404527384A1B1DD9CFC2A3D983659@MN2PR19MB4045.namprd19.prod.outlook.com> <6f0ac4bf-bd1a-65cd-1d40-a97d4aa71aab@bobbriscoe.net> <7B4426F9-E1C5-4F88-A264-0D54C809D523@gmail.com> <AM8PR07MB74761AFC8F5BE0F9573DFF32B9629@AM8PR07MB7476.eurprd07.prod.outlook.com> <6481E606-2458-49D7-B580-8DF7B93494FD@gmx.de> <AM8PR07MB747675E421F0B7A6246C67BEB9619@AM8PR07MB7476.eurprd07.prod.outlook.com> <9A9D4AC3-43F0-4778-839B-E1E247A3C5FA@gmx.de> <AM8PR07MB7476026EA3AA7AD49622B296B9619@AM8PR07MB7476.eurprd07.prod.outlook.com> <CAJU8_nUgNa-W4wf2Vb8sUUqv4XUsSFdVQFUWwrTGw0gDshahiQ@mail.gmail.com> <92b3b23db1dc4ce11162a31acf83c0dd01868a27.camel@heistp.net> <HE1PR0701MB22999F18CBC7874B410B5E13C2609@HE1PR0701MB2299.eurprd07.prod.outlook.com> <9839D5ED-78DB-4F91-99F9-39CAB8C2121B@gmx.de> <HE1PR0701MB2299A10C53522C01802BDBBAC27F9@HE1PR0701MB2299.eurprd07.prod.outlook.com> <19119AD1-F49E-4B58-B988-E487391121AA@gmail.com> <HE1PR0701MB229922BAC35171679447AF3BC27F9@HE1PR0701MB2299.eurprd07.prod.outlook.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/5KcAFuLzcru51Neksr_3pEB8gFg>
Subject: Re: [tsvwg] L4S DSCP (was: L4S drafts: Next Steps)
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: Sun, 28 Mar 2021 21:30:10 -0000

> On 28 Mar, 2021, at 11:03 pm, Ingemar Johansson S <ingemar.s.johansson@ericsson.com> wrote:
> 
> And these that "can or will not.." will then continue to run across the internet 10 years from now ?, 20 years ?

Yes.  Exactly.

I mentioned before that Pete's Czech ISP is still running 15-year-old routers that date from their founding.  I personally still have a "UFO" Apple Airport Base Station - the original one with 802.11b, 56-bit WEP, and a 56K analogue modem - which doesn't get much *use* these days, but it still *works* and is potentially useful.  Heck, I still write code for 40-year-old computers as a hobby.

These old devices lack support for newer specifications.  But they still work just fine in an environment that does use them, because backwards compatibility was designed in when the new specifications were published.  ECN Capable transports still work with dumb drop-tail FIFOs, and Ethernet frames carrying IPv6 packets still traverse Layer 2 devices that were in the shops before IPv6 was finalised, and which require IPv4 (or maybe AppleTalk) packets to configure the settings.  That is how Internet engineering works.  In general, old network devices are expected to continue working as before, and you only need to upgrade if you want to benefit from the new technology.

But L4S is *not* designed that way.  If it is deployed as-is without effective guarding, it will break quite a lot of stuff that isn't even very old.  Your best proposal is to scrap or materially change an existing specification that is currently rapidly deploying in the Internet because people see real benefits from it.  It's entirely conceivable that Pete's Czech ISP will choose this year to finally upgrade those old routers, *specifically* for the purpose of deploying fq_codel, now that they have some experience with it - and that would start a new 15-year timer, wouldn't it?

I've personally put forward two different ways to make L4S safely deployable in the past week - one which requires only minimal technical changes to at least try out, and one which changes much more but which I think will work better overall.  As before, it looks like those suggestions are being rejected out of hand (though Koen's attitude appears to be more balanced, for a change).  This is precisely what has delayed L4S for two years and counting, and there is no end in sight.

 - Jonathan Morton