Consensus Calls for Transport/TLS issues, pre-Singapore

Mark Nottingham <> Thu, 14 November 2019 01:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4C2C512004E for <>; Wed, 13 Nov 2019 17:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=zMeGTAXP; dkim=pass (2048-bit key) header.b=OM9gXxGB
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id K56tz_N4f8l7 for <>; Wed, 13 Nov 2019 17:25:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EDCD2120044 for <>; Wed, 13 Nov 2019 17:25:51 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 0E7A022076; Wed, 13 Nov 2019 20:25:51 -0500 (EST)
Received: from mailfrontend1 ([]) by compute3.internal (MEProxy); Wed, 13 Nov 2019 20:25:51 -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=joS9LUq+3WRQwhos7iRmO4LFBH7eu5 TufdoJd2IcyGg=; b=zMeGTAXPjNjTx/DcwFm7fqB8arMp6K8Mft0C6q5n6dcVT7 KX+DmAfOn4SZRMhKmowBG3CQZPntT457lrWAG9yLIgskTRCRCGYBkZhJ/weS/ByV R/zUzmXrdnge1lEkf08EN/KEdhm8IaErzC3E9zkzRaCgt3who7TFt4Ptem6Hrw2o kwTHGIGWJo5RdF2iAMIZRKnP+KL4AQAYc0X6xHZzE01S3G+Ds3s9ldMkHGoOzuga Q63tuqVHrT9ZD3L+fwSFcaUdj8nyixIEatVjMLO0SaCUpP/unYBwyxXVR53S2rGG 7d6ytxT03BF8SRJDFrqlVxDtIEuFrlxe2Q0IWlvg==
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=joS9LU q+3WRQwhos7iRmO4LFBH7eu5TufdoJd2IcyGg=; b=OM9gXxGB5taJI0pZkrvTjM /1zdYtCiQu8EapQlxyAe6jA5hTCXO7wzkSi0TEw+CUV5NdkPodI3+TchS/nwOtlE oczUQqH3tgL2uHQnkxjsBCbaxHOALP9bJbOw+X3g12YtrGveDbjAbJYLcsK/538v X/TPQOGWGaZjSOH/b6rjYi4IDwXjCK0jL9COY5OpNlj0IB4Uer4ALpodgPq3kwFn VtFu+oxGXKIEBNzsZkzT8OuRztr8VDC2ZYjZEzjrTk6ScL9MaqNffafbGo8Mfcqg HNtLv6i29B/kVEKixRGjv174QqWHl6/S1SJpGefGLyQi0Q35ZxjEYP7P5GAftxlQ ==
X-ME-Sender: <xms:Hq3MXVwMCm7k7rj9jqGIyBpBXrdIk4nTfOSiHqkjY4tI2bCBFYCuVA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudefvddgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfgguffkfffvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfp ohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepgh hithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepudduledrudejrdduheekrddv hedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuve hluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:Hq3MXQKgbMAKw98iOcUk1XZHj8MHW0csKYx3HZWqZa6eYtrt2lBEbQ> <xmx:Hq3MXSMJvuXwOu4PgPxu1zum1ECOrvFzHuO5JqNH2iLMgxGOByIS9A> <xmx:Hq3MXRMLBR-57rDp_Jz2qH7zOhvZYIsZq73wjzOe5atyW0F9dh4MTg> <xmx:Hq3MXRV0P9OPHkgUjJjd0_erK4j0zCLn5_PdOJQ2k68DGJndFQTltA>
Received: from (unknown []) by (Postfix) with ESMTPA id 6A73B80061; Wed, 13 Nov 2019 20:25:49 -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: Consensus Calls for Transport/TLS issues, pre-Singapore
Message-Id: <>
Date: Thu, 14 Nov 2019 12:25:46 +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: Thu, 14 Nov 2019 01:25:54 -0000

The following issues have proposals for resolution, and discussion so far seems to support consensus to accept them. If you object, please do so on the issue or in response to this message (changing the Subject appropriately!). Absent any pushback, we'll direct the editors to incorporate them late next week. Note that by default we won't discuss these issues in Singapore, unless something comes up.

See <> for the current state of issues in the Late Stage process, itself defined at <>;.

* #3127: NEW_TOKEN and Retry tokens must be distinguishable

* #3158: Application close should be disallowed in Initial or Handshake

* #3155: The method of identifying "the same server"

* #2475: Invalid CONNECTION_CLOSE frames

* #3168: Allow servers to close connections immediately when the token is corrupted

* #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers shouldn't be used

* #3014: Handling of corrupt Retry packets

* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST

Mark Nottingham