Re: [tsvwg] David Black (individual) on safety of L4S for the Internet

Sebastian Moeller <moeller0@gmx.de> Sat, 09 May 2020 17:17 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 72A553A0D06 for <tsvwg@ietfa.amsl.com>; Sat, 9 May 2020 10:17:55 -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 vF8HOjA4IeC9 for <tsvwg@ietfa.amsl.com>; Sat, 9 May 2020 10:17:54 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 73E243A0D01 for <tsvwg@ietf.org>; Sat, 9 May 2020 10:17:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1589044664; bh=JJia8TsSgrEoAGCoPDc0aBFVp9/8gFDCJ3I3oOadhb4=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=BcBHLxAwDqV/CbER2+AZTSJhnrGJ6eW+iRF2PkUBLsNPjpinCmYQJ2EBWQYxN4du1 HYSDAvl5ib4tRx/Q5qOnBWr9S9Co7cDNZznRYKsKfEZ1Lw3Ta/KPTviRxGYiHSa9Mr SYfJJRsz1X7xQdnLXM2QlX8cyhyO04FGF1BCqIgk=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from hms-beagle2.lan ([77.0.111.15]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MtfJX-1jGUeV3ERb-00v5Z1; Sat, 09 May 2020 19:17:44 +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: <CADVnQymWXqfiVc0P8GAXBa9P_R54P6DkQnjNQeFZ1p3bsLLLRQ@mail.gmail.com>
Date: Sat, 09 May 2020 19:17:43 +0200
Cc: Jonathan Morton <chromatix99@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D957FCEC-0570-4097-94D3-248B48117F4B@gmx.de>
References: <MN2PR19MB4045DBC270D70DECE5F2B4AC83A20@MN2PR19MB4045.namprd19.prod.outlook.com> <CADVnQymXFe7o4M_GgwqxDP0x5UsAKE+1oQcavyDTF04gP-S34Q@mail.gmail.com> <6E67B51E-6F0A-4BC9-9A77-478F6C5B1222@gmail.com> <CADVnQymz-p_OF_QLOWHt2hPngLzUE=GkCm0epDb4SccbEDzRmA@mail.gmail.com> <3C64B584-1A0E-4C8D-9325-09724289877C@gmail.com> <CADVnQymWXqfiVc0P8GAXBa9P_R54P6DkQnjNQeFZ1p3bsLLLRQ@mail.gmail.com>
To: Neal Cardwell <ncardwell=40google.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.104.14)
X-Provags-ID: V03:K1:g5UdidZqwnu6+bhghRHJRKUhZrxcIsgYlMrhWWwYSpS+I9pHs5k cpYzUwdOQCG/PCAqyG68gbqBOhB4ClghsOSPC4EOaV8FmCUeYPKaQPgzYUCPnemP2/Rvfdu oi8U7AfN0EBhyKp88jT56obGE9NtY+pCMbJgZWUWUTG6RrW82BNz6vq4CsZxZ3tOO61WIbx AnzRbDWrDROCP7bQi3OmA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:8aL5hWcf43U=:fwc8th5TdedTpEUW/aFTn5 i1tFY8wDKNbDDyfyyakeTmFPlPfsKrGPRq9+k+5XAUhXeYy0Ner/NI0lR2nMo+l57scEcmtNX 3AMePQdlW/jt8TWWjFGcAbefGTvXuywiOqXPDdWwIHSHzkbJjjUjhL+pTTY4iheF5FpHooWPV FHQSNpQXaHVU/GbnRr9qBzluON2eGTWDqbS3Uljei6FgSqxcljuMJ8/jlVHdV6BzoYwWYv2DX s2gzG6wVOm2NiHlo9EunH5xpZSRcLVvcNsHjx/pWGGC3atokO2z9iN5obsQMg1SaLi5RY/FPj 2R4LaeBE/ZN0+mtMrLr0c7gWhF3MsbvMO7kAZ3TLD0iT9mPWHwVdAUvpTn6MBzFPQ3nzEkrS9 m1OHi1pUHAt76bBkNJi3vN8gycKN4+OT4V4W7DAK6A32FXnwAc0UHuLny2CmZoon1TfBXeDT+ 30zu+Hr1cLV3KZ4yO/bC19ezLLkKMH6rCcqiItof/ANkP0Ee3rM8pDUdn28oUdAzFJdA3/CDn j674+WC6WhZ/C7P72VAjrAraLAloVxATBGCxW7VWbUmIxXDa7oqnQeyNgILHwhGoBpbNQc4qx SlOCfcsw6NQbs4f7YwlNGAKZVZCgveD67DMU1/+pfqx9EaYea2lN39Dzcb1kwMF+JR8d9E6k1 ae3i754xfz0HudSRMfW7dYng4kMqbCJ1bOd5ravhZd/fOBY2Bj4fahOgX/MhwagHbAoZRLDDE 52JcBfymII9gRoxsdHJR0hA8FxYfx2k7fR7kTAMb4o6kVB6xhpubmTcH4n9bz9AAh/RtL6Ww/ T2WB67sDGhuKW/5dv+t6Sr8hAxKF7g1nk+vUdbbpd+tMFVM5No+XMV1GcocLDlqiKw8Lj+boP r8PaTXTkTan3XgXwlopQOk2go3gROdeup8Vbva5kJQtfIaQK4MBreuYbWfeV9WVvu32MGMWQj We8LjYHnK9g0ntsagc6m0BMT+XlBEKV1IgbuwENNDY/r/PYT0S0tRUyGdTKJoyjg3qGQYwgN3 DscW3+5tX4E5Q8HBZmCu47pdBgNPuiHan6CojxN1C9ZlMrzQX4rr2LkQgEvmCr5iaU+SGJ0Mx Mhw94CjQ7W1dyo6nE+QWRUs4KOPx1ku3DhdrhhJPaIXOMtVxy83+uZOZ4eN6tzu/B0Qctr0rh jGHFusqxZn6BaGEULJN5y4KloHdyyYYVRyEljF+7YGoL54VHXk7o9yLhl4dLpsT4/CpbLnsd+ miw0F7qs/TvUBu5qd
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/X_oCXYOH-Zy5n5I4ovhhY9__byM>
Subject: Re: [tsvwg] David Black (individual) on safety of L4S for the Internet
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: Sat, 09 May 2020 17:17:57 -0000

Hi Neal,


> On May 9, 2020, at 15:54, Neal Cardwell <ncardwell=40google.com@dmarc.ietf.org> wrote:
> 
> On Sat, May 9, 2020 at 5:42 AM Jonathan Morton <chromatix99@gmail.com> wrote:
>> [...]
> 
> It is not the case that L4S expects "the whole Internet" to be
> upgraded. AFAICT the L4S ecosystem is expecting something like the
> following:
> 
> *If* you are one of the few ISPs that has deployed RFC3168 ECN
> bottlenecks that do not have FQ or other mechanisms to ensure robust
> fairness properties in the face of flows that mark ECT(0|1) and do not
> follow RFC3168, *and* you are not comfortable with the L4S mechanisms
> to infer the presence of RFC3168 bottlenecks, then you should either
> (a) upgrade your RFC3168 ECN bottlenecks to something with more robust
> fairness properties (e.g. fq_codel or cake), or (b) simply change your
> existing DSCP rewriting rules at the ISP ingress to bleach ECT(1) to
> Not-ECT (or any other mechanism of your chosing to treat ECT(1) as
> Not-ECT).
> 
> neal

	[SM] IMHO this expectation really is demanding that others clean up the mess L4S will have made, no?
Other AQMs that presently work well and standards-compliant will need to change to allow L4S to work outside of existing RFC3168 rules. And that for rather little gains L4S offers over the state of the art ... (fq_codel based AQM can deliver a median of around 5ms under load with bog-standard 1/sqrt(p)type TCP flows, sure 1ms < 5 ms, and what ever many nines L4S secifies is larger than the median, but we are still talking relative small differences compared to the multiple 100s of miliseconds without any AQM, but that later is the wrong reference point to judge the L4S costs against IMHO)

	Your proposed remedy, using FQ to isolate the fall-out of L4S flows lack of CE responsiveness to themselves, is exactly what L4S itself eschews on the argument that FQ is computationally too expensive. Now, I am not convinced that that is actually technically correct (and assume L4S FQ-allergy is mostly driven by Bob Briscoe's known position on FQ) but still that is a self-inconsistent position to take IMHO: to allow L4S to get by cheaply, existing users are required to up their game at a considerable computational cost. 

I am not saying that this is not a valid position to take, but the consequences should be explicitly discussed.

Also, as a nit, the 2 ECN bits live outside the 6-bit DSCP field, so DSCP rewriting rules might not be the right term?

Best Regards
	Sebastian