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

Mark Nottingham <> Wed, 06 November 2019 01:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 07363120041 for <>; Tue, 5 Nov 2019 17:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Status: No, score=-2.69 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=n2qTu5+R; dkim=pass (2048-bit key) header.b=LZaDCHa1
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7q2rkOMlHDOw for <>; Tue, 5 Nov 2019 17:41:37 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E4926120154 for <>; Tue, 5 Nov 2019 17:41:34 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 1E8C221EAF; Tue, 5 Nov 2019 20:41:34 -0500 (EST)
Received: from mailfrontend2 ([]) by compute3.internal (MEProxy); Tue, 05 Nov 2019 20:41:34 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=d hHxy6rjp423nbcwA2AsULYblJ8+qXZGxi1qQNlRhfo=; b=n2qTu5+RnldSO+hjQ NRVmEJ26vDYHvH9ABVkhCPJHsKXUOhQIptEHWkv2cSdbum1zaiTa9rEYRX2oPl/j OAgTgy/bIR3zn6eaB0+TMwT60WotCPAm92905A+KkpPRCszibF9H7KynhrAOcX/9 rInM08xCw81qE0Fe5LnYHsHVeyZKbltA6MyEK7DDva5iWco1+OiRmC/kGHLLWo5H KVmgYLXbQT1Fcpg8fJJ2RWbI0nW8SueFgip/PPN6tpKIdImE5hOmVN/r1aVhT/wM JjkZnroPJ2SnaG9xbIFkuX7ez37qJB0kYfcRL23EKeDu1T6FM7zbqfg4d918E1RF 96uvg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=dhHxy6rjp423nbcwA2AsULYblJ8+qXZGxi1qQNlRh fo=; b=LZaDCHa1SmO41mZHcMZAqn6/EyY7/5vDnJZQiXRqQkfiNSuu0qVdvKK1s t4hhzkzm3bR+aNQ/1zrPcONWUoS7N1IaVy1Cuj2ftVJfnTixT8g1eZoOaXrLgU7F /KEdfxd2yHtvW5ul7DFj9DaRySI1hMfx+aTW2ZuUZHwlhhCLQFIKK3SGcrSPmbw6 RUrj1GkKvhvCD8IE2o3TJAQOoGlkhsa6dj8HuaIC2KTE+ERLQ/E89/L1j+EJ0fP/ ZJ6o/C136GtdBvx6Ankqx02TjIVjhIHG6uN33NRYM3Rb9omFeVmtdTLJYGy0m2O1 asl5xYl4lxxtZafiBAg15v4+zTBpw==
X-ME-Sender: <xms:zSTCXZLVCBcClpAf_eeFaCiN9zd7TL4PMLHU-1kZlG5WN5LTip9Uqw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduiedgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh ephhhtthhpfegrnhguqhhprggtkhgurhgrfhhtshhtohhthhgrthhprhhotggvshhsrghs figvlhhlrdgrshdpghhithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepuddule drudejrdduheekrddvhedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhn ohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:zSTCXQE6bMzdFj5AdkmIZ-BiLzrro5d_8jM2pQ8fZKPCUKj94E3svA> <xmx:zSTCXQsPJqvtrgxYgvSd287Nrd4u9EhcAJPRs1XEGslkELqiHH9MPQ> <xmx:zSTCXftNqnf33jJASVs1C79NCCQMQ0knjrjCkjMMWfGAN1iHeu5DUA> <xmx:ziTCXWI_aHSqqAdNbserlt87roxTPoQmmkmDNZO3sFj9tVebFj5f2Q>
Received: from (unknown []) by (Postfix) with ESMTPA id 54AD33060074; Tue, 5 Nov 2019 20:41:32 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
From: Mark Nottingham <>
In-Reply-To: <>
Date: Wed, 6 Nov 2019 12:41:27 +1100
Cc: IETF QUIC WG <>, Lars Eggert <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Ryan Hamilton <>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 06 Nov 2019 01:41:49 -0000

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.


> On 6 Nov 2019, at 12:35 pm, Ryan Hamilton <> 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 <> 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:
> 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.
> --
> Mark and Lars, QUIC WG Chairs

Mark Nottingham