Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Thu, 07 November 2019 12:38 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA76120251 for <quic@ietfa.amsl.com>; Thu, 7 Nov 2019 04:38:29 -0800 (PST)
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 W2-XeQ9JKR-a for <quic@ietfa.amsl.com>; Thu, 7 Nov 2019 04:38:27 -0800 (PST)
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 0C970120152 for <quic@ietf.org>; Thu, 7 Nov 2019 04:38:26 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:f9a2:f494:9c7a:603c]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id DF7201B00064; Thu, 7 Nov 2019 12:38:18 +0000 (GMT)
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Mike Bishop <mbishop@evequefou.be>, Mark Nottingham <mnot@mnot.net>, Ryan Hamilton <rch@google.com>
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com> <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net> <BN6PR2201MB1700F28E83B7E752473192D7DA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <0693b533-a492-de2b-7a96-64c5f56d6882@erg.abdn.ac.uk>
Date: Thu, 7 Nov 2019 12:38:18 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <BN6PR2201MB1700F28E83B7E752473192D7DA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UKwai9hvt4x8bioXZh6UZwhJfoU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2019 12:38:30 -0000

I don't think Recovery has that level of maturity yet.

To me, QUIC transport contains protocol specs that are the same as other 
protocols - albeit inter-twined with the encryption model and 
HTTP-specific aspects, but the recovery spec is focused on the protocol 
mechanisms, and needs to be correct with respect to the implications on 
other transport flows sharing capacity with QUIC.

In that space, we indeed need to get the spec correct. That may mean 
late comments (alas); but hopefully things will move faster if we focus 
on resolving issues and if work separates a little to http3 v recovery 
topic, actually most of the comments seem to come from a few people. If 
the process somehow impeded that I would be concerned.

Maybe I might feel happier after a detailed review of the latest text in 
24 and a check through the issues -  I undertake to do this before the 
Singapore meeting!

Gorry


On 06/11/2019 15:59, Mike Bishop wrote:
> Also, the design team is an HTTP design team focused on having a coherent story around prioritization across HTTP versions.  They/we might propose text back to HTTP/3, or they might define HTTP/3 extensions in an HTTPbis document, or they might do something else entirely.  This working group should consider the design team output if it comes before the document is done, and if not will need to make a decision about whether to proceed without it.
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org>; On Behalf Of Mark Nottingham
> Sent: Tuesday, November 5, 2019 8:41 PM
> To: Ryan Hamilton <rch@google.com>;
> Cc: Lars Eggert <lars@eggert.org>;; IETF QUIC WG <quic@ietf.org>;
> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
>
> Hi Ryan,
>
> I think our intent was that it's an open issue, but I see that we haven't captured that in the current issues list. Good catch; let's go ahead and open one.
>
> Cheers,
>
>
>> On 6 Nov 2019, at 12:35 pm, Ryan Hamilton <rch@google.com>; wrote:
>>
>> For QPACK and Recovery, this sounds great to me. For  HTTP/3, as I understand it, we still have a design team working on priorities. Can you clarify how this effort is affected by the late stage process? (Or is is basically unaffected as it is an open issue?)
>>
>> On Tue, Nov 5, 2019 at 5:02 PM Mark Nottingham <mnot@mnot.net>; wrote:
>> Previously, we've moved to the 'late-stage process' documented at [1] for the Transport and TLS drafts. The chairs and editors now feel that it's time to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>>
>> As before, this is because we're getting to a stage we feel the documents would benefit from slower and slightly more formal process, so that the rate of change is not so high, changes that do occur are well-vetted, and the documents get closer to reflecting consensus in the working group.
>>
>> If we do this, we're saying that we have gained consensus on what remains in these documents, excepting their outstanding issues. As per our charter:
>>
>> """
>> Note that consensus is required both for changes to the current protocol mechanisms and retention of current mechanisms. In particular, because something is in the initial document set does not imply that there is consensus around the feature or around how it is specified.
>> """
>>
>> That doesn't mean that new issues can't be raised against those drafts. However, new issues against them will be judged for whether they contain new information (in particular, security or interoperability impact), a clear technical defect, or have significant (in the judgement of the chairs) support for further discussion. If the issue isn't well-described or atomic, it may be closed with a request to refactor, or refactored for you.
>>
>> Again, this does not affect editorial issues.
>>
>> Practically speaking, it means that new issues will be triaged by the Chairs -- not the editors (although they can still "claim" purely editorial issues) -- and those that don't meet the criteria above will be closed. Those that do will be labeled (again, by the Chairs only) as `design`.
>>
>> It also means that all of the closed `design` issues against these drafts will be marked as `has-consensus`. Additionally, the `quicv2` issues against them will be closed and marked `has-consensus`.
>>
>> The issues that will be labeled `has-consensus` (and closed, if still open) are listed here:
>>
>> https://github.com/quicwg/base-drafts/issues?q=is%3Aissue+is%3Aclosed+label%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>>
>> We believe that all of these issues have been discussed and the group has formed consensus on them; this only formalises that.
>>
>> If you have concerns or questions, please discuss them on-list; barring pushback, we'll adopt this on 15-Nov-2019.
>>
>> Cheers,
>>
>> 1. https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-process
>>
>> --
>> Mark and Lars, QUIC WG Chairs
>>
> --
> Mark Nottingham   https://www.mnot.net/