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

Martin Thomson <> Tue, 25 February 2020 18:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5E683A1274 for <>; Tue, 25 Feb 2020 10:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Status: No, score=-3.098 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, 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 1SgEdqCZI7Cd for <>; Tue, 25 Feb 2020 10:13:04 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 52D793A1269 for <>; Tue, 25 Feb 2020 10:13:04 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 3BF90520A3C for <>; Tue, 25 Feb 2020 10:13:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1582654383; bh=PQ418cd8L5IvBq/YoiKdYeRThtjU7lk8u8efEoLBff0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MCmNGlwy17U3SNYTJLgCEzXG2jDASaEB6DtKPTTxbt4DHbjgPN7gh8YO19g0y7enQ N3yzURz3IdPX6Qt6i6sAqFOKdqCOT3syWAYaGlvClZAGcSTZ5CK3QcbOeiWP2zQRoo /8YwbrLONVxH2AvvAw/Y0tXg+USf8UEV9LeWwufk=
Date: Tue, 25 Feb 2020 10:13:03 -0800
From: Martin Thomson <>
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_5e5563af2bac1_3b873f856cacd95c1612cc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Tue, 25 Feb 2020 18:13:06 -0000

martinthomson 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

Perhaps: "This means that a client might have to change the connection ID it puts in the Destination Connection ID field twice during connection establishment, [..]"

These changes are mandatory, so it is appropriate to point to those as being special.

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