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

Well, I hope that this PR fixes that so that the one case I outlined - running out of CID's become impossible, leaving only the don't care case which is not a strong enough of case for a SHOULD. If there are edge cases I think packets should be dropped or parked, otherwise the large volume of work on linkability is void. It could be that some adversary could delay packets to force linkability to happen.

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