Re: [quicwg/base-drafts] Connection ID Length changes (#2473)

Mike Bishop <> Fri, 15 February 2019 19:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03F67130F3B for <>; Fri, 15 Feb 2019 11:23:37 -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 S523kal7_9Sp for <>; Fri, 15 Feb 2019 11:23:35 -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 278A612F1A2 for <>; Fri, 15 Feb 2019 11:23:35 -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=Fj0uubWbBagjaKsJvqfck2Lo/n4=; b=AYyN1Aa2g/QLA1Ql o8AvNuA8LcvB5JSOGdCgc+33Ff1OlYFXuitfAkI8vgNoJiOTn+b/4+FUV9LJygc1 RGg1O6seYZx8lrzV9ZH64u6OH/AteI5P/9pHBmDjbNvcD8lZ0Tz9WEWFzD1ng3r/ owLKn8DwBYrYPGDf+TXXb6DAw1I=
Received: by with SMTP id filter0011p1iad2-30233-5C6711B5-2E 2019-02-15 19:23:33.935756953 +0000 UTC m=+833344.611185923
Received: from (unknown []) by (SG) with ESMTP id y3lQfWbFT0aRkBH8sKwpLQ for <>; Fri, 15 Feb 2019 19:23:33.909 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id DC2EAC10DB for <>; Fri, 15 Feb 2019 11:23:33 -0800 (PST)
Date: Fri, 15 Feb 2019 19:23:33 +0000
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2473/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Connection ID Length changes (#2473)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6711b5d9efa_15b73fc1c14d45b4104826"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3nZB+rv0G0ZwKHfVbEA7bPHaPs16Etgfwgpn OEeTKYZ3vb2D2kCP02BUgd3Xa1pNsgoZhrKt0cYkxK3hLVaHP8gHbCybGTtRw2+tVGD7UtpOi6sQ4Z hGehsRc+2P9wWmYkccltoNyMb2nVls67dMpz5bbgy4xw2UfKjj0F9YNF5DudIMPGOTEoJPF39kLwvj A=
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: Fri, 15 Feb 2019 19:23:37 -0000

If you have a "mixed" connection, you lose the ability to reject packets because the CID is unknown; it might be your zero-length CID, so you have to try to process packets with unknown CIDs.  But also, if you *do* recognize the CID and it fails to decrypt, you have to decrypt it again -- it might be a ZLCID packet where the packet number happens to encrypt into a valid CID!  So I agree, let's not do that.

I don't feel strongly about requiring all CIDs on the connection to be the same length, save to note that it's not implausible for a server to reach a case where it must either kill a connection or increase the CID size being used.  (Let's say that all/enough CIDs in the previous size have been allocated already.)

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