Re: [tsvwg] L4S vs SCE

Wesley Eddy <wes@mti-systems.com> Tue, 19 November 2019 17:24 UTC

Return-Path: <wes@mti-systems.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 5AA0912007C for <tsvwg@ietfa.amsl.com>; Tue, 19 Nov 2019 09:24:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mti-systems-com.20150623.gappssmtp.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 0wh9esAYK1vO for <tsvwg@ietfa.amsl.com>; Tue, 19 Nov 2019 09:24:24 -0800 (PST)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 BD753120112 for <tsvwg@ietf.org>; Tue, 19 Nov 2019 09:24:23 -0800 (PST)
Received: by mail-qt1-x833.google.com with SMTP id y10so25492169qto.3 for <tsvwg@ietf.org>; Tue, 19 Nov 2019 09:24:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=lvfByEYYjKzlvkaB//sP0+3/hJgRtLF4RgWJmEXc2Eg=; b=Ua3KeukUunlpe8E0NkU1jLKYgOs8xfLEoVf32DcVH+IwZ0xaSH1OIXa2leViX1zUq0 XhqYBzjl6z/0GmZJiGvc1tNFVl1/H9CvV2sh9pbEo21TIdDA8IsAgqFeflaJVRnnAUuh CdXOqWXS3+odcSUSbO5FZb9YxG+qihn1qhkhDVWQHxfFPqeIm2yx2CCMjn3zKOFkmCu6 h1V5CNl3Tk33EaAIbHQyuHEyuihsRqgOs9Pu7r6lk5sb8dt9Y+2ifnOoHtkhTNXV6b4Y 0DgcV14gq1f9XaFPSfOEr5aE2dLVovK3Thd4D7AUMRfk/4cuc+2q4KsRSYJ/1T0TAkBl 9cqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=lvfByEYYjKzlvkaB//sP0+3/hJgRtLF4RgWJmEXc2Eg=; b=pyHgxXtLgZ21S+DRYgWJ/sjO7t12I9i19y/9u0QDzW3gQ/xXBHNmUSp0qdq4ym1J+n g4U7kHYyxMqvTbCixLZo7JMSpwKq/yKbHgXvKfFTzYHW2tmJqqMPM4Z4qG/AWYTzPa9A kueMW4/wbrubD4kh8HvMGchtJoErv5Oypk9V/28o7CYIQB3O3JFFF51fJS7n7+65rkGE uglaeZ0cGsmeIv09feqMVzzoQLyAuCvKAuQdaCt338e0t1Oa2a7ANZZpYUZyPw6dxK6+ FlYLMjZ1YpQN37C6heMgietcUCjkhu67hKoGc24sKoKn/JhUIbfNTvr+4opVp3wPYdUG q1Fw==
X-Gm-Message-State: APjAAAVDP8z8kv0GU5/ws9F2I4cqlMuqfDibKZ18AVXf3WZoSxa8iYBu +Gg8ejsrHZK8WkzGv7AvFab1Bg==
X-Google-Smtp-Source: APXvYqx8/X/3LDYa5xioleH0ZBq2/AvX1YUD5yIGYOUoQ7TIbEa2EMmHyJrq8Da/AVG7pnkaTV3xeg==
X-Received: by 2002:ac8:27a2:: with SMTP id w31mr33967573qtw.227.1574184262718; Tue, 19 Nov 2019 09:24:22 -0800 (PST)
Received: from [10.100.1.112] (rrcs-69-135-1-122.central.biz.rr.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id l11sm10457543qtq.20.2019.11.19.09.24.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 09:24:22 -0800 (PST)
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, Sebastian Moeller <moeller0@gmx.de>, "De Schepper, Koen (Koen)" <koen.de_schepper@nokia.com>, "Bob Briscoe (ietf@bobbriscoe.net)" <ietf@bobbriscoe.net>, Greg White <g.white@CableLabs.com>, Jonathan Morton <chromatix99@gmail.com>, "4bone@gndrsh.dnsmgr.net" <4bone@gndrsh.dnsmgr.net>
References: <HE1PR07MB44250F3C4E6A744DDCC3DAFCC24C0@HE1PR07MB4425.eurprd07.prod.outlook.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <ad7b763e-b3dd-36cf-a9c5-7de99476babb@mti-systems.com>
Date: Tue, 19 Nov 2019 12:24:17 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <HE1PR07MB44250F3C4E6A744DDCC3DAFCC24C0@HE1PR07MB4425.eurprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------FB473AF55AED53A871032550"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/-V02Uf_ap1Dx3U-0uEyqe38Np8I>
Subject: Re: [tsvwg] L4S vs SCE
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: Tue, 19 Nov 2019 17:24:26 -0000

On 11/19/2019 7:12 AM, Ingemar Johansson S wrote:
> Hi Chairs + others
>
> I am not convinced that all these L4S vs SCE mail threads will make us any wiser.
>   
> The first question is around how safe L4S is to deploy on the internet and the proof points for either option differ widely.
>
> The other question is if we should have another ECN experiment (SCE) at this stage, also here I see that we have vastly differing opinions.
>
> In both discussion points I see that the discussion is going in circles.
> My personal conclusion is that on a technical level it will be real hard to come to an agreement.
>
> On a more non-technical matter, I have argued (rightly or wrongly) about the connection to work in 3GPP, admittedly so far only proposed work. Others have pointed out work related to WiFi and DOCSIS, how much should this weight in here ?
>
> Are the chairs any wiser ? :-)


Hi Ingemar, just speaking for myself and not any other co-chairs ... 
here are a couple of thoughts:

Yes, I'm getting a few positive things out of the threads.  For 
instance, there are some points it seems like everyone might agree on, 
including:

  * work on testing and publishing results has been very helpful
  * importance of RTT fairness
  * impact of the TCP Prague (or other end-host/transport) behaviors on
    the dual-queue performance
  * maybe some other things

I think where there are big issues, confusions, and disagreements 
causing back-and-forth, seems to be around:

  * entangled evaluation of L4S with TCP Prague (I see this badly in the
    threads ... From what I can tell, the public test Prague code
    doesn't yet meet all the Prague requirements in the L4S draft, and
    that's caused some explosion of emails.)
  * maybe lack of understanding about how and where people are hoping to
    use/deploy L4S?  (like as an operator, what else would be there that
    mitigates some of the concerns people have, and that supports
    gathering experimental results, etc)
  * concern that there can only be one of L4S or SCE happening
  * maybe some other things

It probably would be good if we all focus messages on making important 
new points and observations, not picking apart each sentence in replies 
or re-iterating points several times.  That would be in the spirit of 
working together towards the best outcomes, in contrast to just holding 
a public debate.  There are 700+ subscribers on TSVWG, and posters 
should continue to keep this in mind.