Re: [tsvwg] dispute (Re: Results of consensus call on ECT(1) usage)

Sebastian Moeller <moeller0@gmx.de> Sat, 23 May 2020 10:12 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 3382A3A0B18 for <tsvwg@ietfa.amsl.com>; Sat, 23 May 2020 03:12:51 -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 DludLJIwE0TI for <tsvwg@ietfa.amsl.com>; Sat, 23 May 2020 03:12:49 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 875E33A0B10 for <tsvwg@ietf.org>; Sat, 23 May 2020 03:12:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1590228728; bh=kIIpBfkEP9a74sCZ+9Kvm24uKAmuf46roBr//cDFdK4=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=fpmDvpUwjOhZ9zn52yQ/sQCaf3+HExrCzkE7pFxeGDL3WCe7BWEb8iwsOhbcYgj7t zsY7uIux7tUhnPqXeTBWmgj9gjseACW2drihuEiuuhbTLopOU/qKxSESW+4+HZHPh8 dgJxGeEpG0dhixz3K+kDpLu/BtDAVzpinJioR6VU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from hms-beagle2.lan ([95.112.110.247]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MCbEf-1jm1dr2sp1-009ic7; Sat, 23 May 2020 12:12:08 +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: <30C37177-5C1F-440C-969A-A7AA33E1744D@eggert.org>
Date: Sat, 23 May 2020 12:12:05 +0200
Cc: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>, Joe Touch <touch@strayalpha.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FF39746-E794-4DD9-A6FC-FF8588CC6616@gmx.de>
References: <202005221335.04MDZEg5022015@gndrsh.dnsmgr.net> <30C37177-5C1F-440C-969A-A7AA33E1744D@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3445.104.14)
X-Provags-ID: V03:K1:yWxkzZXWdeFFvSq3syuFkMClMn0exBjA3UPlRG8yGDQwNHGi7R9 gDO2b6PK/aIVvK7Y0+t02jDyYI+x8V6VVSJMl32kx9kIe/gxvSDU5oGtG8BE4sa7eSRna2t JASLCU7TKpmaMuug0jAbVkMd81hAvd6K5wb0oRujE0lYDuOdm/IZvr/2VL01rY7cSZzmMEB v50sVPb2s0fepK9H5IoTw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:9MMHP4x1rXY=:J0cxkem5zO8mCt6HqyMHtG 2o+lAtQsTQJkEm1FELJSh0PiqAPOBW6esOW+h87tScqyFjjaEy8kXKSMPPLG/XZRudTp7daPg PihCG2kYWnLbuuvvle9Wvv3pb6NsOSZTMZGzZfJQG08tcHzEol6dlLwuAgaA5DQPi5PF9jIOi BcXrxEkMi2nETo989of6xIuEZhoocJA3uVz1IWz9vsTnQKPIKFTdH70WFLEMJ2EzenRDvSjHN PYVr34C6xtWmL5zXtoWXxybPj3YVF4GyBOb18xe4VnXV6ON6XlO8OTuiOhV/kN/zAVo1n2MPL 6CCZGjqPaYjvwc/PVAAwj8cIFSYujB+GGvTYqItVMDPULOsW0kzFlb7xDgLwoVM/kSsoQPpp2 zMzydAxviQGvT+lrOQ8w5XcwGVybVRdkmpMN7lTR4V+kUUvH6OPQgVqX2wUuBqBQXBsxfwWeP FvKTU9EwXvrDq2EjvTTVS2tzkPgq4mIaK7fUAvRKbIv2quzmgW/7IWwasiWlroZXumL6SFF/A S/28/7uzfUrEl7+UH1SQ9Rt/fVw2aqi2EMF911nSbLwUqSVpErzta2OWkn+iOvaCoUoGrhKT3 JtFsK6oHZsOJAb15+X5hZJqg64IJQ1qN4ZpB2s7hHDKyuHR/UCiutOGt2/VCVozXoUTD6QGAp /y4cv5a1BCmRE0fabOvHifPDQHWMA7I4GvQbKRpb8kA3nj4IcUIGGlU/mXo7P+XOlkgvYv454 2ED9dBbwukQfEZJ4WlztUukHoNC8jhZK/Qw8wa8Qcw+uQpnNYDyAEQg0CCKNS5fks2iq0uCU+ gGY1sgborpcVe7HEuPWy89IOTBZ247jS24N3/9HdGseF4oMTfwqiNuKDSa37MHzdSmyQomiMp v2nUy7W638cn87FfTvkk2ha+gGNnp9h5UDtwC3RTCPqqahfR5Kow+MVxAbrOsbge1cXF/7Ygh 3MnIxYGglZBV7RKlzjnH3eTpqJA0hDkeyVsgO0Izlcyh+emlrHRn8eqzrR1s4ZOUjxSnDnB1w KW/xhJVkJcqTjqXMQOrKkFKJ7MbKUUowRoY3FdomeARWjp6EfntHM7m3+6VjKryM1yotQescE 78slkYtF7ZqpeaWl+DRih53V9lJcI2+u/OvdZJnwbRNl0j+PeFLLJnCrTP2jujO9j/3HdbNuO ueIoMLYnq/eklYV/T2OJ19EN4+wSsPGMh5ofargPbVWpt7NaCzg6PC5bdcFJAMIxs9GpNqMBw gDO2v9gAfg09QfRCl
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/MppqMhgFdDE91NY0wsCNwIXrDP4>
Subject: Re: [tsvwg] dispute (Re: Results of consensus call on ECT(1) usage)
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, 23 May 2020 10:12:52 -0000

Hallo Lars,


> On May 22, 2020, at 16:25, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> On 2020-5-22, at 16:35, Rodney W. Grimes <ietf@gndrsh.dnsmgr.net> wrote:
>>> We were never given a ?none of the above? choice.
>> 
>> Which was actually itemized by the IETF Chair Alisha Cooper at the
>> very end of the Interim Meeting, I was rather shocked to not see
>> it as an option, and hench my vote was made with a comment that
>> I had been "boxed into a choice."
> 
> you can always refrain from responding to the poll?
> 
> Lars

[SM] Sue that is an option. If L4S would have been designed without side-effects for non-L4S traffic, I would happily ignored both the discussion and the poll. The fact of the matter is, that IMHO L4S will not achieve its stated goals (because its goals are considerably too ambitious, and its developers, ever the optimists, never bothered to actually test their design under even mildly adversarial conditions, what can go wrong?). 
	To add insult to injury, L4S will not only not work as promised, but it will also introduce a nice and juicy new DOS target (the LL-queue can be disrupted with simple bursts of traffic, no sustained overload necessary, try catching that with "circuit-breakers" and similar heuristics).
	As stated before, all this for essentially potentially ~1 ms of latency-under-load-increase instead of 5-10ms (as compared to the current state of the art, even still using 1/sqrt(p) CC signaling), so rather modest gains for rather unpleasant side-effects. 
	In short, a decision important enough to participate in even after the WG restricted the choices to a sub-optimal selection, since the outcome of the WG decision might affect all internet users in the future. 
	If I would not know better, I would feel that the poll got the outcome it was designed to yield; but we knew that before, there are companies that already invested in L4S and hence there are already vested interests in it proceeding along the standardization path. And to be explicit I see nothing nefarious in that, but it is not the best conditions under which to ask an engineering question about how to use ECT(1) in the future.
	
Interestingly almost nobody of those voicing their support for ECT(1) as input now, had contributed in the past when we discussed the short-comings of L4S and nobody volunteered empiric data supporting the L4S hypothesis that the criticism was overblown.

Best Regards
	Sebastian