Re: [quicwg/base-drafts] Connection ID DT output (#1742)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> -new connection ID for each connection ID retired with a RETIRE_CONNECTION_ID
-frame. When a receiver of a packet notices that its peer is now using a
-previously unused connection ID, it can supply its peer with a new connection ID
-using a NEW_CONNECTION_ID frame to reduce the possibility of its peer running
-out of available connection IDs.
-
-Endpoints that use connection IDs with length greater than zero could have their
-activity correlated if their peers keep using the same destination connection ID
-after migration.  An endpoint that receives a packet with a different remote
-address or destination connection ID than previously used SHOULD also switch to
-sending with a connection ID that has not previously been used.  The goal is to
-ensure absence of correlation between the pairs of client and server connection
-ID used on different paths.  To fulfill this privacy requirement, endpoints that
+An endpoint SHOULD ensure that its peer has a sufficient number of available and
+unused connection IDs.  The endpoint can do this by always supplying a new
+connection ID when a connection ID is retired by its peer or when the endpoint

Maybe move the recommendation for 8 in between the two sentences here.

-- 
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/1742#pullrequestreview-158348724