Re: [quicwg/base-drafts] Clarify section on negotiating connection IDs (#3349)

Eric Kinnear <> Thu, 06 February 2020 11:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7D3C412023E for <>; Thu, 6 Feb 2020 03:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_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 utILtFU-znpe for <>; Thu, 6 Feb 2020 03:30:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2123A12009C for <>; Thu, 6 Feb 2020 03:30:25 -0800 (PST)
Date: Thu, 06 Feb 2020 03:30:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580988625; bh=hLHj8y57UKeLTj2liemon724YkiEhLEw4TleUbxbuvw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=brqBCatIgAWWBmvd76sbTi8icuk3r9od4+X1sx0LkqxcLTwN72zA8SIOr7EPDwmB5 4NsD0DU55XZC3hUAGZrTpR4HaN7Y06hv+dP7+V2OcG4iJxXfEhv3CEEUmVFjMrdZUE CcW9DsXHA5RT+Un2Mtp8MKRP9rvdsgjdywFEIfKo=
From: Eric Kinnear <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3349/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify section on negotiating connection IDs (#3349)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3bf8d13522a_75bd3f9c772cd9601269ed"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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: Thu, 06 Feb 2020 11:30:29 -0000

erickinnear commented on this pull request.

> -from the server, it MUST discard any packet it receives with a different Source
-Connection ID.
-A client MUST only change the value it sends in the Destination Connection ID in
-response to the first packet of each type it receives from the server (Retry or
-Initial); a server MUST set its value based on the Initial packet.  Any
-additional changes are not permitted; if subsequent packets of those types
-include a different Source Connection ID, they MUST be discarded.  This avoids
-problems that might arise from stateless processing of multiple Initial packets
-producing different connection IDs.
-The connection ID can change over the lifetime of a connection, especially in
-response to connection migration ({{migration}}); see {{issue-cid}} for details.
+the SCID supplied by the server as the DCID for subsequent packets, including
+all subsequent 0-RTT packets. This means that a client might change the DCID
+twice during connection establishment, once in response to a Retry and once in

Given the resolution of #3348, we should likely update this to not set an expectation that you change twice maximum, technically they can change as many times as you give them CIDs / as many times as they want to switch between all active CIDs.

The reference to {{issue-cid}} later will point people at some clarification about this too, so that looks great.

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