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

[Jana Iyengar <[e-mail]>]

janaiyengar commented on this pull request.



> -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.
+Endpoints that supply connection IDs with length greater than zero could have
+their activity correlated if their peers keep using the same destination
+connection ID after migration.  To ensure that packets sent on different paths
+cannot be correlated, endpoints SHOULD provide with new connection IDs before

```suggestion
cannot be correlated, endpoints SHOULD supply new connection IDs to their peers before the peers migrate.
```

And drop the rest of this paragraph, I don't think it adds anything.

-- 
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#pullrequestreview-199970145