Re: [quicwg/base-drafts] Prevent linkability from responding to migration (#2969)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> @@ -2057,11 +2058,17 @@ linked by any other entity.
 At any time, endpoints MAY change the Destination Connection ID they send to a
 value that has not been used on another path.
 
-An endpoint MUST use a new connection ID if it initiates connection migration.
-Using a new connection ID eliminates the use of the connection ID for linking
-activity from the same connection on different networks.  Header protection
-ensures that packet numbers cannot be used to correlate activity.  This does not
-prevent other properties of packets, such as timing and size, from being used to
+An endpoint MUST use a new connection ID if it initiates connection migration as
+described in {{initiating-migration}}.  An endpoint MUST use a new connection ID
+in response to a change in the address of a peer if the packet with the new peer
+address uses an active connection ID that has not been previously used by the
+peer.

I added a recommendation to send NEW_CONNECTION_ID when migrating.  It's a little janky, because you have to include the frame in every packet to be effective.  Unless you like the wonderful cascading loss that results from your peer being forced to drop all your packets because the golden one didn't get through.  Of course, then you need to worry about how to manage that retransmission logic...

-- 
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/2969#discussion_r315017061