Re: [tsvwg] L4S vs SCE

"De Schepper, Koen (Nokia - BE/Antwerp)" <> Wed, 20 November 2019 12:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7532A1208AB; Wed, 20 Nov 2019 04:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VFhVnEwu5bMr; Wed, 20 Nov 2019 04:40:20 -0800 (PST)
Received: from ( [IPv6:2a01:111:f400:fe09::722]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B279612088C; Wed, 20 Nov 2019 04:40:19 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=Aqrc67JbJS7m9kVBJHX/rHGVxd6ot8sPDY0zJovjjLDLv9nHicEEWycKLbIalmXAcd5VkMrAhot4X1Gk7e32DmD2yp3LjGFSzt1R+mffxOZQ9R0OmqiHukJ4LksDlLlF+s4/w/nl+sdfY1SwS+4vMgORBcUvWrlUAaObVxcKms9jrVmP5Nv2hFTY/pi1ERDVYr0ar0ts3yjpcM17rPEjly8oFyN9uXWEnUSeJpRMR4jjgzSbCcxm2jPIGg3jYiFgqJ+NY96cjjeGxzMfTNTNnY9lsJJZ8EeoJ9SciOwwkvg6uWWSx25akKitgGswBD4vwuABHGy1pEKgGC1jLGNjpA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OVhz8IgCJr/EgJkaFeb7ksL2KvaXJKfxmH+RmfltniM=; b=a6gcF3+vdp1aDfDAB0b1Fo1+G0hWO2dbktncOMOK39vdbdDtcSBWS7doTSLRbGmMtQA6QHNQ7JIe4pSE60RBla4m/XZ/k3MuujRgv/+gMdhu2JNxHkdaVGnra8zsUFUbzTWqYqCPivxGZdStvm6Dbb6pDVVq6hCQOuYnPBgQwMF6N7mT/x31vsqc4ikm6YqSidIliPuNW/2KPoszlMiV0qpojPib7U4B8+T3k3p/4BFDtq2Rw9aP2oHwCzSOl/yxcCfEk3RemY6NihLnsxQr0zxhWuxAZpKXZ8anaPKZLjIyJzCltJElaLPcCAwCOWodQNN0x/VOEeTRpWAoVMIA+g==
ARC-Authentication-Results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OVhz8IgCJr/EgJkaFeb7ksL2KvaXJKfxmH+RmfltniM=; b=EAiT7PvHfPljOjpOLEUsyoScMIs7Gy4pRN4MNkS1bzIS2GMz2HbNonK4bo/C2qsgrU2dMbn5Z9iqeBT4Gi/sh1T/ktzc/79UwS9HEphwIulSUwu0DqeH8uJzJ9JvzmMeGqqkx9Yla6usUT8s+yZd2AOBjyJDQlfCuS35jRuSr6g=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.10; Wed, 20 Nov 2019 12:40:17 +0000
Received: from ([fe80::512e:fea6:b569:32b0]) by ([fe80::512e:fea6:b569:32b0%6]) with mapi id 15.20.2474.015; Wed, 20 Nov 2019 12:40:17 +0000
From: "De Schepper, Koen (Nokia - BE/Antwerp)" <>
To: Ingemar Johansson S <>, Kyle Rose <>
CC: Sebastian Moeller <>, G Fairhurst <>, "" <>, "" <>, "" <>
Thread-Topic: [tsvwg] L4S vs SCE
Thread-Index: AdWe0nrRkrzku9jhQamw6kS06HsgqgAK7DuAABW78QAAAJnugAAJXScAAAJlnjAAASgZgAAAux5gAANtw+A=
Date: Wed, 20 Nov 2019 12:40:16 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: nl-BE, en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: b26c06a1-1f22-442a-6052-08d76db6cc12
x-ms-traffictypediagnostic: AM4PR07MB3394:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:3826;
x-forefront-prvs: 02272225C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(136003)(376002)(346002)(366004)(189003)(199004)(236005)(229853002)(7736002)(2906002)(52536014)(66476007)(66556008)(66946007)(74316002)(76116006)(64756008)(4326008)(486006)(66446008)(14454004)(316002)(54906003)(186003)(26005)(110136005)(86362001)(76176011)(11346002)(446003)(6506007)(53546011)(5660300002)(102836004)(99286004)(476003)(33656002)(66574012)(55016002)(81156014)(3846002)(7696005)(8676002)(6116002)(790700001)(6436002)(25786009)(66066001)(81166006)(6246003)(478600001)(14444005)(8936002)(256004)(71200400001)(54896002)(6306002)(71190400001)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB3394;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: WQMBybC0Y7/0bAFZsuwYe1E7sxiPdjG7o5T966y9nvLbtR6++SLykFW8WwrJ2BVGf47RaS9N6g1EFlUsLlf1P5n6t/+I+zzwGKRfHgKHjLMZfOOK9QBgBmTXzL7K7XewPe+00tVUZp/ep+V2h0yhIkfV7Z61O74Tcs05q8ec+/n/kA51pIvNgeHRmZjgLBdo3WvwliC6jJ2YfoGY/p4YLA1FZLBNfXlZPI99pLW02hMjktEOFC1VhTHBbp4+a44qOPE4i9Ox0I/8J2KMaVg05NdqL/2D0qy8oMSf2i3n5wfGYXg9rycJk3bai7Wmyi1pVn2R1I9ct7472vvxDCes9Tgk7/HeCPc9XgCpiuEsH+57ejf2aKOfVQ2AsTg/LzEPuuXFALYOjldsltimJqvlwLPKxcjsh8l4PO63YsZjSAaKMd/V5HzInlRaNmTfmy6f
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM4PR07MB345968E8C665304DFBD5B11FB94F0AM4PR07MB3459eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b26c06a1-1f22-442a-6052-08d76db6cc12
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Nov 2019 12:40:17.0257 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: uKL2ZX4GfoKuLIK6h/m3QqPFhhTNV8S/GBdd+JNcFN0ypY6UCHXe2INKllPzSCcuEeLZv7/EjJZZVILssJW1jWmMhXUDbMSn8tJkLFzPYIkvJWJZQN8NZqVZ3NlCdBl/
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB3394
Archived-At: <>
Subject: Re: [tsvwg] L4S vs SCE
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Nov 2019 12:40:24 -0000

I agree with Ingemar. Related to the chances for failing: as history learned us, the only real world chance for failing would be that the technology would not be taken up in deployments. This whole codepoint conflict is mainly damaging/creating this deployment 'issue'. The other so called show stoppers are less of an issue for most people that worked on CCs. Blowing 'issues' (not yet implemented/integrated/tested code and bugs) out of proportion is not the way to go forward here.

To give an example:

As mentioned in another thread already: the L4S codepoint, where there's a new queue and new CCs, creates a clean-slate opportunity. This is an opportunity to select new desired behavior.

One of these opportunities here is to make L4S_TCP less RTT dependent. There have been many working implementations for less RTT-dependent CCs in the past. One that is widely deployed is Cubic, which is doing this for getting more throughput for longer RTTs. The only reason why it didn’t fly for lower RTTs on the current Internet is that they would hurt themselves (get lower throughput, competing with Reno).

As we are able to define a new independent behavior and the RTT dependence in L4S is taken serious (some even call it a show stopper) this is even a must do opportunity for L4S. It is all a matter of perspective: show-stopper <-> opportunity.

Let it be clear, I am not against adopting new ideas for implementation of congestions controls and AQMs, as long as they are not contesting with the code point and requirements that were selected and agreed on as part of the L4S BoF. I'm also not against the recent vibrant energy, interest and engagement of people, but I think we can better use this energy in making things work. As you noticed, we can use the help to speed things up on the open source part.


From: Ingemar Johansson S <>
Sent: Wednesday, November 20, 2019 11:50 AM
To: Kyle Rose <>rg>; Ingemar Johansson S <>
Cc: Sebastian Moeller <>de>; G Fairhurst <>uk>;;; De Schepper, Koen (Nokia - BE/Antwerp) <>om>;; Ingemar Johansson S <>
Subject: RE: [tsvwg] L4S vs SCE


So given the imagined outcome that L4S fails.. two scenarios

If other SDOs or developers don’t pick up L4S then things are quite simple I guess, just declare the L4S drafts as deprecated, or is there more to do ?

But, if e.g. 3GPP somehow thinks that this is a good idea and adopts it.. Will the IETF send a message (LS?) to 3GPP with the message “please stop using L4S”, is this even a reasonable scenario?. After all, the fact that it is picked up by other SDOs, speaks against a failure ?


From: Kyle Rose <<>>
Sent: den 20 november 2019 11:14
To: Ingemar Johansson S <<>>
Cc: Sebastian Moeller <<>>; G Fairhurst <<>>;<>; Ingemar Johansson S <<>>;<>; De Schepper, Koen (Koen) <<>>;<>
Subject: Re: [tsvwg] L4S vs SCE

On Wed, Nov 20, 2019 at 6:04 PM Ingemar Johansson S <<>> wrote:
>       How do you expect an industry/commercial roll-out of L4S
> technology to behave, if the L4S experiment should terminated without
> adoption as a standard track RFC? Are they supposed to phase-out using
> ECT(1) as well, or is it understood that deployed L4S instances continue using
> L4S methods?

[IJ] The premise would be that L4S is declared a failure. I doubt that anybody has a good enough crystal ball to predict what happens. First it is necessary to come to the conclusion that L4S is a failure and I would argue that we are not yet there and I don't currently see that coming. Before that possible event I don't see it meaningful to speculate.

I'm going to have to go ahead and disagree with you strongly here. Given the potential consequences of cleaning up after a failed experiment without a plan worked out beforehand, this blithe approach is simply not acceptable.

In lots of cases, experiments are easy to terminate in an obvious way: for example, in one typical case, a code point can simply be abandoned, or (even better) a pollutable experimental code point returned to the available pool after some time. If that were the case here, it would not be difficult to enumerate a sequence of steps required to do so. It doesn't appear that's the case, however, so all the more reason to make sure we address this as part of the experiment setup.

A launch escape system of the necessary complexity should be a requirement of any experimental deployment. In this case, that might circumscribe the scope of the experiment itself.