Re: [quicwg/base-drafts] introduce a max_connection_ids transport parameter (#1998)

Christian Huitema <> Thu, 07 February 2019 20:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B7814130E6F for <>; Thu, 7 Feb 2019 12:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oh_BVLzWrMNw for <>; Thu, 7 Feb 2019 12:49:14 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 89EBC130E6C for <>; Thu, 7 Feb 2019 12:49:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Wvr0uh0ZvVJfBt6aJW7Zcn1UR9s=; b=wAz/qiUX+Pgn4ahw Ms4R9X0gsPC6ILuqMrdphaj9hj0xCciC99bNyKzgmqO0al7x1wVnYEPHZ5DN/Bto dUWPaIHPRbhVDd2y8nQP1U1y5Ace7ll45zqe3c2xWW6awjw62y0bxJBWW9WUS0VZ ziwbq3nAfbepvSmRR1O0F5cnTQ4=
Received: by with SMTP id filter1789p1mdw1-31814-5C5C99C8-18 2019-02-07 20:49:12.453541286 +0000 UTC m=+171620.913269127
Received: from (unknown []) by (SG) with ESMTP id L4Y8duwnRniCKRnJzArMMg for <>; Thu, 07 Feb 2019 20:49:12.451 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 6C5D180032 for <>; Thu, 7 Feb 2019 12:49:12 -0800 (PST)
Date: Thu, 07 Feb 2019 20:49:12 +0000 (UTC)
From: Christian Huitema <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/1998/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] introduce a max_connection_ids transport parameter (#1998)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5c99c86ad3c_36b33fa6636d45b810090"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0ohQLg3ujWVH5VsXcJKVIIwJr9iw/iCexU7B 5HwDJRk9nnWFcBq8zb9nI4QTlmYmvhBaP2PdrtZrq9rp0wVaMccoBVRbbwwXeodccW5exg3Khxp+7u Z5VTPpI8tt4g1u3jqcp6GOhtS7x1n5fSwK0/JNgjuxpBUyocpBtPP2t0kZj1Cn6so2LdNTcgZPcLY0 s=
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Feb 2019 20:49:17 -0000

huitema commented on this pull request.

> @@ -3981,6 +3979,12 @@ A client MUST NOT include an original connection ID, a stateless reset token, or
 a preferred address.  A server MUST treat receipt of any of these transport
 parameters as a connection error of type TRANSPORT_PARAMETER_ERROR.
+max_connection_ids (0x000e):
+: The maximum number of connection IDs that the peer is willing to store.
+  This value includes only connection IDs sent in NEW_CONNECTION_ID frames.

@MikeBishop yes indeed, the server always sends at least 1 CID, so a limit of 0 appears to break. But this is easily worked around by only applying the test to NCID frames. This is easier than special-casing the handling of CID[0] and CID[1]/SPA. In particular, the logic for handling RETIRE_CID and creation of new NCID becomes much simpler.

As I mentioned before, a default of 0 does not work very well, because the default for migration disabled is also 0 -- yet enabling migration without any NCID would be a protocol violation. The default should be at least 2 (initial and SPA), and I would prefer 3.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: