[quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)

[Lucas Clemente <[e-mail]>]

One of the major features of QUIC over TCP is the option of seamless connection migration. One can conceive of a situation where a network middle-man (e.g. an ISP, firewall implementer, etc) might have an interest in blocking this feature, e.g. by detecting connection migrations to their network and dropping those packets. I propose that we think of a way to make a connection migration indistinguishable from a "normal" new connection.

One solution I can think of would be to have the client send a "fake" initial packet with 0-RTT encryption (which would then be discarded by the server as undecryptable). The first few packets sent on the new address would also need to have the version bit set – which the server would have to ignore.

This would also require initial packet number randomization (see #35).

Thanks for @lcolitti for pointing this issue out.

-- 
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/issues/203