Re: [quicwg/base-drafts] Remove requirement for reciprocal connection ID change (#2386)

ianswett <> Wed, 30 January 2019 03:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 59577130EED for <>; Tue, 29 Jan 2019 19:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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_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 w_u8qQ2Ahk8f for <>; Tue, 29 Jan 2019 19:39:20 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DC7E6130ED8 for <>; Tue, 29 Jan 2019 19:39:19 -0800 (PST)
Date: Tue, 29 Jan 2019 19:39:19 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548819559; bh=3IFOu66XSucMd8UgNNo9Ata36N9omkpT7xOszdPLzCw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yQxl9EP2/21ZmKpcjNxBr7IprHDC6YB28anMGaNXFvvTYSuRH4NTIcbfATb1cNPM8 3SapjhATTOncKSI9pLKWHuasxpV0s+XSRWZvx7HHpoEVRPhuKLf5RqnRPQmeY2S0NV Wv60AyOWp60DYwZTZntGFVEl/4biU/fLKarNmMvk=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2386/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Remove requirement for reciprocal connection ID change (#2386)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c511c6763b8_bd93f9e9bad45c0258579"; 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: Wed, 30 Jan 2019 03:39:23 -0000

ianswett approved this pull request.

> @@ -2110,19 +2110,10 @@ infrequently.
 Endpoints that use connection IDs with length greater than zero could have their
 activity correlated if their peers keep using the same destination connection ID
-after migration. Endpoints that receive packets with a previously unused
-Destination Connection ID SHOULD change to sending packets with a connection ID
-that has not been used on any other network path.  The goal here is to ensure
-that packets sent on different paths cannot be correlated. To fulfill this
-privacy requirement, endpoints that initiate migration and use connection IDs
-with length greater than zero SHOULD provide their peers with new connection IDs
-before migration.
-: If both endpoints change connection ID in response to seeing a change in
-  connection ID from their peer, then this can trigger an infinite sequence of
-  changes.
+after migration.  The goal here is to ensure that packets sent on different

after migration.  The goal is to ensure that packets sent on different

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