Re: [quicwg/base-drafts] Simultaneous connection migration (#490)

[Martin Thomson <[e-mail]>]

OK, simplest possible migration, change of port number on both ends, same connection ID.  I don't understand how this would work.  Whichever peer sends first will send to a port on which the other side isn't listening.  Same happens if the IP and port change together.   It's worse if the connection ID is changed and that seems highly likely given that this is why you migrate in the first place.

We already have an unwritten caveat on migration in that the migrating endpoint has to be the one to speak first.  We probably have an additional unwritten caveat that only a client can migrate, given that a changing source address likely runs afoul of any firewalls and NATs and we more or less assume that the server isn't afflicted with that sort of curse.

As for costs, I don't know what the solution looks like, so I can't even speculate on costs.

-- 
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/490#issuecomment-299053847