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

[Christian Huitema <[e-mail]>]

huitema 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

@mikkelfj the whole point of this PR is to say that and ensure that it works. Do you want to specify what the server should do if the client's probe arrives before a new connection ID is available? By your logic, we want to say that the server should wait before responding to the probe.

Then, do you want to enforce that? For example, suppose that a client sent a probe with a new CID, and receives a response with an already-in-use CID. Should it just shrug and continue, or signal a protocol violation? 

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