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

[Martin Thomson <[e-mail]>]

Leaving aside the migration that happens without the knowledge of the migrating endpoint (like NAT rebinding), this is tricky, if not impossible.  And it's not a property of versions, but of our invariants.

The most obvious problem here is that a handshake uses the long header, which we don't use at any time afterwards.  So we have the migrating endpoint understand the need to make its packets indistinguishable and use the long header when it knows that it has migrated.

Firstly, as Lucas says, it would be trivial for a middlebox to apply the static packet protection keys for that version of QUIC to determine that the packet isn't protected with those keys.  We know from experience with TLS that middleboxes do exactly that sort of thing.

So what do we gain by doing this?  It seems like we just create a bunch of hoops for these middleboxes to jump through, none of which are especially challenging.

-- 
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#issuecomment-357812374