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

ianswett <> Fri, 07 February 2020 10:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 49495120853 for <>; Fri, 7 Feb 2020 02:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 XU-jCPFLR2Dj for <>; Fri, 7 Feb 2020 02:50:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8B427120838 for <>; Fri, 7 Feb 2020 02:50:39 -0800 (PST)
Date: Fri, 07 Feb 2020 02:50:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1581072638; bh=ubIJ9EhClJQBT0KaJ37SEiUyzoqEIdRpCVRZQmYAau0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vEv1iS3X/LgG9e0S1rRNl+iOXNcn0yXTMt1Sh+O8BHn5hOh6Y2xUg86R49Sj0+UWj Tpxaztuukz303+hejLcy7QNyiriuaOTcQdCfhr6LErU3muQuHoTLrlgYmkWSxuez3q E3LZ7nOCX55dH3luZxyN4oPJAac6IFxmwHjk9/uA=
From: ianswett <>
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_5e3d40fed059e_13a33fc9b0ecd95c1700d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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 10:50:41 -0000

ianswett 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

Discard-Initial currently says:
"A client stops both sending and processing Initial packets when it sends its first Handshake packet."

If a client processed an Initial, Handshake and 0.5RTT from the server, then it could start using the CID in NEW_CONNECTION_ID in Initial packet if it sent the Initial packet right before the Handshake packet.

Of course, if the Initial was dropped it wouldn't matter, so this is a bit irrelevant, but I wanted to make sure others realized it was not just Handshake, because I missed that previously.

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