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

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



> @@ -2057,11 +2057,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 connection migration if the packet that initiates
+migration uses a different connection ID to packets received on any previous
+path.

I wonder if using the term "initiate a connection migration" is correct, as to me it seems to imply what [section 9.2](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.9.2) talks, but not [path probing (section 9.1)](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.9.1).

Shouldn't we better state that, an endpoint MUST use a new connection ID when responding to a packet on a new path, using a new connection ID?

-- 
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#pullrequestreview-275257914