Re: [quicwg/base-drafts] Stronger migration handshake (#2370)

[MikkelFJ <[e-mail]>]

mikkelfj commented on this pull request.



> @@ -1847,6 +1847,11 @@ endpoint migrates to a new address.
 An endpoint MUST NOT initiate connection migration before the handshake is
 finished and the endpoint has 1-RTT keys.  The design of QUIC relies on
 endpoints retaining a stable address for the duration of the handshake.
+Clients MUST NOT initiate connection migration before they are
+certain that their peer also considers the handshake finished. This
+means that in addition to waiting for availability of 1-RTT keys,
+clients MUST wait acknowledgement by the server of one of their
+1-RTT messages before initiating connection migration.
 
 An endpoint also MUST NOT initiate connection migration if the peer sent the
 `disable_migration` transport parameter during the handshake.  An endpoint which

@huitema  > Where did we specify that only the client initiates migrations in V1?

I'm not sure, but from memory it was dropped at some point because symmetric ping pong got hairy during updates or some defence became difficult.

Maybe it didn't land? Found this:

> Caution:
If both endpoints change connection ID in response to seeing a change in connection ID from their peer, then this can trigger an infinite sequence of changes.

But there is this, which seems to be preferred address only - maybe I got it mixed up_

9.6, transport:
> Migrating a connection to a new server address mid-connection is left for future work. 

-- 
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/2370#discussion_r251257955