IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Fri, 15 February 2019 19:23 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03F67130F3B for <quic-issues@ietfa.amsl.com>; Fri, 15 Feb 2019 11:23:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S523kal7_9Sp for <quic-issues@ietfa.amsl.com>; Fri, 15 Feb 2019 11:23:35 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 278A612F1A2 for <quic-issues@ietf.org>; Fri, 15 Feb 2019 11:23:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; 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 filter0011p1iad2.sendgrid.net with SMTP id filter0011p1iad2-30233-5C6711B5-2E 2019-02-15 19:23:33.935756953 +0000 UTC m=+833344.611185923
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id y3lQfWbFT0aRkBH8sKwpLQ for <quic-issues@ietf.org>; Fri, 15 Feb 2019 19:23:33.909 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id DC2EAC10DB for <quic-issues@ietf.org>; Fri, 15 Feb 2019 11:23:33 -0800 (PST)
Date: Fri, 15 Feb 2019 19:23:33 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7fa37a5ea6e964cdd0a378927491d1f639992c7892cf00000001187ed3b592a169ce187d68e1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2473/464168826@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2473@github.com>
References: <quicwg/base-drafts/issues/2473@github.com>
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-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3nZB+rv0G0ZwKHfVbEA7bPHaPs16Etgfwgpn OEeTKYZ3vb2D2kCP02BUgd3Xa1pNsgoZhrKt0cYkxK3hLVaHP8gHbCybGTtRw2+tVGD7UtpOi6sQ4Z hGehsRc+2P9wWmYkccltoNyMb2nVls67dMpz5bbgy4xw2UfKjj0F9YNF5DudIMPGOTEoJPF39kLwvj A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/fy_t8Q1Gs2TzhRrrqQmSULpHRhk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=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:
https://github.com/quicwg/base-drafts/issues/2473#issuecomment-464168826

v2.23.0 | Report a Bug | By Email