Re: [quicwg/base-drafts] #3348 Clarify that you can use any issued CID at any time, even during the handshake (#3438)

Kazuho Oku <> Fri, 07 February 2020 08:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4CB0312013B for <>; Fri, 7 Feb 2020 00:55:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 vhWTVP-l3A8Q for <>; Fri, 7 Feb 2020 00:55:24 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 837A21200DE for <>; Fri, 7 Feb 2020 00:55:24 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 95FC3960501 for <>; Fri, 7 Feb 2020 00:55:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1581065723; bh=r4wIGRsn1RWysu973qbgIAFtNHltOitNC3aJk9CZ/XQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0Xr+tfy0+eC+iEKlFd8xCqZDGc7LyDvcNvGQgMM2k+VJs/Il53ERwG0eqUDRvX0Tg axrF7nSk4VTSikveoxiZan84g6PG1u3GtYumV79+Ht5Ioe/iE6NjckmI7kpOZk7JEx kk3fzq0Bh1wn1ArhVZwfIm1bp4o00vcvOVQpWwB8=
Date: Fri, 07 Feb 2020 00:55:23 -0800
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3438/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] #3348 Clarify that you can use any issued CID at any time, even during the handshake (#3438)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3d25fb8d862_78a33fb3ca2cd9641572cd"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
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, 07 Feb 2020 08:55:26 -0000

kazuho commented on this pull request.

> @@ -1002,7 +1002,9 @@ When an endpoint issues a connection ID, it MUST accept packets that carry this
 connection ID for the duration of the connection or until its peer invalidates
 the connection ID via a RETIRE_CONNECTION_ID frame
 ({{frame-retire-connection-id}}).  Connection IDs that are issued and not
-retired are considered active; any active connection ID can be used.
+retired are considered active; any active connection ID is valid for use at any
+time, including during the handshake.  This includes the connection ID issued by

Maybe add "in any packet type", considering that the original issue was if the CID of a Handshake packet can change?

Note: CID of a server-sent Initial packet might also use a CID delivered by a NCID frame, when 0-RTT is being used.

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