Re: [tsvwg] Gorry Fairhurst Individual thoughts on choosing whether/how to advance ECN work.

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 25 May 2020 07:47 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 3B4573A0CD9 for <tsvwg@ietfa.amsl.com>; Mon, 25 May 2020 00:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2PjzwimTWC4M for <tsvwg@ietfa.amsl.com>; Mon, 25 May 2020 00:47:02 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 552F33A0CD7 for <tsvwg@ietf.org>; Mon, 25 May 2020 00:47:02 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id C0C671B001CF; Mon, 25 May 2020 08:46:55 +0100 (BST)
To: Sebastian Moeller <moeller0@gmx.de>, tsvwg@ietf.org
References: <dbc71da6-70f1-7369-1d2d-f08fb3b08b69@erg.abdn.ac.uk> <21483444.sDhFMENYeD@linux-9daj> <a85600da-e69f-9190-7ca1-d23a7e7246f9@bobbriscoe.net> <3267993.nvHYsSR2bi@linux-9daj> <dd8e3896-2951-537f-e3d1-9954c93348dd@bobbriscoe.net> <67CBAA42-BD37-4A19-B650-68F511FC244A@gmx.de> <af3e6272-c04d-9e81-763c-e690ed521749@bobbriscoe.net> <1565A7C1-1DF1-4C6A-AC37-14331AC87508@gmail.com> <25e34532-5a33-3ca1-5cba-b7f857874ced@erg.abdn.ac.uk> <2605AA63-8225-4585-AA7B-49ACBF3B07EB@gmx.de>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <259b9730-58ba-c2f1-6318-3c4717aa6b7e@erg.abdn.ac.uk>
Date: Mon, 25 May 2020 08:46:55 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <2605AA63-8225-4585-AA7B-49ACBF3B07EB@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/CoDLN71cSCpnuI08k5dxX7SEJ8c>
Subject: Re: [tsvwg] Gorry Fairhurst Individual thoughts on choosing whether/how to advance ECN work.
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: Mon, 25 May 2020 07:47:05 -0000

Hello,

On 24/05/2020 13:37, Sebastian Moeller wrote:
> Hi Gorry,
>
> On 24 May 2020 10:01:33 CEST, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>> On 24/05/2020 05:21, Jonathan Morton wrote:
>>> I think I'll leave Paul and Sebastian to comment further in this
>> vein.
>>>    - Jonathan Morton
>> If you decide to comment more, could you please finish that very
>> quickly
>> - the WG has decided to work on L4S.
> [SM] On the danger of stating the obvious, that decision to work on L4S makes it quite important to highlight and discuss all the pain-points of the current L4S design, implementation and drafts. Unless I misunderstand what "work on L4S" is supposed to entail...
>
>
>> There are topics that the WG needs to address, and I think this
>> discussion is not helping the WG make progress.
> [SM] For better or worse, this WG will be held partially accountable, for L4S meeting it's claims, so I consider discussion of those claims, with the eventual goal of finally de-hyping the draft text, pretty on-topic and relevant for the mailing list.
>
> BUT, since that is so obvious that I assume I must be misunderstanding your point, so please show me where/how.
>
>
>
> Best Regards
>          Sebastian
>
>> Gorry

I think it would be more normal to discuss or provide comments on a specific section of a document. If there are claims there, then maybe these do need to be looked at - it's not uncommon that the text around performance/merits in a spec need to be reviewed before a document completes WGLC.

Gorry