Re: [quicwg/base-drafts] Bundle new client connection ID and path challenge in migration probes (#1730)

[MikkelFJ <[e-mail]>]

mikkelfj commented on this pull request.



> @@ -2366,11 +2366,16 @@ genuine migrations.  Changing port number can cause a peer to reset its
 congestion state (see {{migration-cc}}), so the port SHOULD only be changed
 infrequently.
 
-Endpoints could also have their activity correlated if their peers keep using
-the same destination connection ID after migration. Nodes that initiate a
-migration need to provide their peers with new connection IDs. The goal is
+Endpoints that use connection IDs with length greater than zero
+could also have their activity correlated if their peers keep using
+the same destination connection ID after migration. If a node receives
+packets through a newly used connection ID, it SHOULD select an

Yes, it would seem rather pointerless to change CID otherwise. Responding with an old CID is the same as the peer never changing CID. The only reason is running out of CID's and not being that sensitive to linkability. As we now, opting out voluntarily does not work well in crypto.

-- 
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/1730#discussion_r216406711