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

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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DAEB612011B for <>; Tue, 5 Nov 2019 17:02:38 -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=GJqJja9Y; dkim=pass (2048-bit key) header.b=A82z0Ye+
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id B6Zar4hr4udd for <>; Tue, 5 Nov 2019 17:02:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 861A71200C3 for <>; Tue, 5 Nov 2019 17:01:43 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id E52B920BF5; Tue, 5 Nov 2019 20:01:42 -0500 (EST)
Received: from mailfrontend1 ([]) by compute3.internal (MEProxy); Tue, 05 Nov 2019 20:01:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm1; bh=RG1yH9Ze+kSNuxyrcBmz9/AjFrO10H 45SO8M3J2KQbI=; b=GJqJja9Y2OF5FwH7BJp1t3qcPgmAdSvH1S/EQtcjRSkVS3 G7Fv9v0aS+KkZ0Gm/aq5hD9AvNmOHsJr4JS7bP5sQUpYM7Hv0VwmzPMdEHaglTJ+ bUVlg6caZLpLXCle65q1ug774yJFLCcZzy25xlYfpVcWJ/ISNjx/wbO54YUQnHXi L8bBb7DnR+87rqx3752uVg3ld8gMH2EitmKf2VEGaagqM9X6hHnc9vSE44JgsTOd Muu2lOYQlxRbmmg7CqIudT3zgb7w18EfXO6206AD3X2fwFZ7fhznCjcA1bHYI9sd SSJZzx0nocbubDcqKq/aqLJ2cn1oeASjDsKht3CA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=RG1yH9 Ze+kSNuxyrcBmz9/AjFrO10H45SO8M3J2KQbI=; b=A82z0Ye+h957s17LbD9Ob+ PeJziXQfd1+GPoV54j61EEco06J4WShmBonWqGIKGxtX0ZDOh94/Pp/Fv3ErsDsW A0RhpcAJnb/+EpAsrrn90jp76BmAsDRr4JA2kaJkaSts1ecv2NI5b1N72F9uW4dx tBOLbgxGsTtyiilxGYF5/8o2wvlx2cle4Ki6KcIZG57FiKEVmoQfexhCbCo1S0p1 mGtN9J1YGLcdozk+9TBD1bpOgHixs0zB45Wyi/fuzN3ksrGg3M1Wc8izhiLIvw2j XTThl/dbvSMrCdp7NC4jziCR3ull3uBnQgYpAF8xe5Aj+aK6f42kJ3cCIyz7Q/Pg ==
X-ME-Sender: <xms:dRvCXeOx-O3zVgoAWSK9SBSN6J4JIQaMFVBP5wcHR-dHMo4OysZtSg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduiedgfedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfgguffkfffvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfp ohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhephh htthhpfegrnhguqhhprggtkhgurhgrfhhtshhtohhthhgrthhprhhotggvshhsrghsfigv lhhlrdgrshdpghhithhhuhgsrdgtohhmnecukfhppeduudelrddujedrudehkedrvdehud enucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhu shhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:dRvCXfZpQs5sECSeIlP4VA9JwJ61b310ev5pielo452UvvXn1SGEqA> <xmx:dRvCXVfn5p-v4aWhY73aIQjTVuN5u717Cvzqv-oEBPjWGuEpqA6vtA> <xmx:dRvCXWNbk8667ti_CjhAfDgZceh_POBYu-6bfvlOli9bAuxjZM9CRQ> <xmx:dhvCXYj_Vl52i4ukJyPnGZh4Ru5kr26tsZqkbIb3Dy0fIhUaEbW_iA>
Received: from (unknown []) by (Postfix) with ESMTPA id 8615C80061; Tue, 5 Nov 2019 20:01:40 -0500 (EST)
From: Mark Nottingham <>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
Message-Id: <>
Date: Wed, 6 Nov 2019 12:01:34 +1100
Cc: Lars Eggert <>
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:02:39 -0000

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.



Mark and Lars, QUIC WG Chairs