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

Or, you could just reply on the old path until you have a new CID. It might work, or it might trigger retransmission.

-- 
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_r216460456