Re: [tsvwg] plan for L4S issue #29

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 30 September 2020 07:50 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 E36373A12A7 for <tsvwg@ietfa.amsl.com>; Wed, 30 Sep 2020 00:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 7Yh9ma0NnFZO for <tsvwg@ietfa.amsl.com>; Wed, 30 Sep 2020 00:50:23 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 62E7F3A12A6 for <tsvwg@ietf.org>; Wed, 30 Sep 2020 00:50:23 -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 242CF1B002CD; Wed, 30 Sep 2020 08:50:15 +0100 (BST)
To: Jonathan Morton <chromatix99@gmail.com>, Greg White <g.white@CableLabs.com>
Cc: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>, Mikael Abrahamsson <swmike=40swm.pp.se@dmarc.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <202009291549.08TFnvFV068509@gndrsh.dnsmgr.net> <c7080365-233c-5f1e-ef5c-1f42c969042a@erg.abdn.ac.uk> <73562E45-3EE7-43D4-B26B-76478AE19AF8@cablelabs.com> <94AC09FD-76B6-4A34-ADC9-AD3AAC4E5111@gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <c724e8bb-fd4a-7b9d-0493-a12b0d84582f@erg.abdn.ac.uk>
Date: Wed, 30 Sep 2020 08:50:11 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.3.1
MIME-Version: 1.0
In-Reply-To: <94AC09FD-76B6-4A34-ADC9-AD3AAC4E5111@gmail.com>
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/JXBkQrY9shNeYoL_KBa21C5k-80>
Subject: Re: [tsvwg] plan for L4S issue #29
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: Wed, 30 Sep 2020 07:50:25 -0000

On 30/09/2020 04:29, Jonathan Morton wrote:
>> On 30 Sep, 2020, at 1:48 am, Greg White <g.white@CableLabs.com> wrote:
>>
>> I believe that the WG needs to honor the consensus position
> Let me be absolutely crystal clear:  There was NO consensus position established.  Please go back and read the statements by the Chairs if you are still unclear on that point.
>
> The Chairs made an executive decision, in the absence of consensus, to allow work to continue on L4S.  Progress is therefore expected on resolving the open issues to the satisfaction of the WG as a whole.  The SCE team is respecting that decision for the time being, but we will continue to call out deficiencies that have not been rectified and any further attempts to bypass the processes of the WG.
>
> Let me quote David Black once more, for emphasis:
>
>> I am confident that TSVWG does not currently have rough consensus that the L4S experiment is safe to perform on the Internet.  RFC 7282 is relevant background reading on rough consensus.
> That is the central problem that L4S needs to resolve.  If it cannot do so, it should step aside so that alternative approaches to high-fidelity congestion control can be tried.
>
>   - Jonathan Morton

Specifically on the Interim outcomes: The currently chartered work items 
on L4S remain chartered, and the Chairs expect these to be requested for 
publication as RFCs, following a WGLC. That WGLC will (as usual) 
consider safety of the method for the proposed experimental deployment. 
There are also other ECN specifications that the WG is updating, which 
need to be finalised first.

I am confident there is energy in the Working Group to complete the 
current set of ECN-related specs, and I'd strongly encourage people to 
focus on offering text that allows this to now complete.

Gorry

(TSVWG Co-Chair)