Date: Mon, 04 Feb 2019 06:06:37 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab5b7d49cbdc9abf0137711514794f405cc5a6122592cf00000001187008ed92a169ce181d7dce@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2386/review/199600537@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2386@github.com>
References: <quicwg/base-drafts/pull/2386@github.com>
Subject: Re: [quicwg/base-drafts] Remove requirement for reciprocal connection
 ID change (#2386)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c5846ed541a6_4d2e3fe3a22d45b8158798";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/IRr6q1lXnGOp4mEbD0YIyqMTw1o>


----==_mimepart_5c5846ed541a6_4d2e3fe3a22d45b8158798
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

ianswett commented on 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.
-
-Caution:
-
-: 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 is to ensure that packets sent on different

+1 to Jana's suggestion.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2386#discussion_r253481352
----==_mimepart_5c5846ed541a6_4d2e3fe3a22d45b8158798
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><b>@ianswett</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/2386#discussion_r253481352">draft-ietf-quic-transport.md</a>:</p>
<pre style='color:#555'>&gt; @@ -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.
-
-Caution:
-
-: 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 is to ensure that packets sent on different
</pre>
<p>+1 to Jana's suggestion.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/2386#discussion_r253481352">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkq2O5ea_g-bSZHpF7IkSGh_V-7Uboks5vKD5tgaJpZM4aZYcZ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AWbkq4VPPlxREtYy9-EgN5RNUnHG0sR7ks5vKD5tgaJpZM4aZYcZ.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ianswett commented on #2386"}],"action":{"name":"View Pull Request","url":"https://github.com/quicwg/base-drafts/pull/2386#discussion_r253481352"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/2386#discussion_r253481352",
"url": "https://github.com/quicwg/base-drafts/pull/2386#discussion_r253481352",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5c5846ed541a6_4d2e3fe3a22d45b8158798--