There are usually no NATs across datacenter hosts, and only firewalls that you choose to set up on your own. Such hosts may have multiple ethenet interfaces to maximize bandwidth. Or there may be private and public IP addresses, billed differently.
I can see plenty of problems of bidirectional migration though. I suspect P2P multipath will be easier. On 10 November 2020 at 15.44.54, Lars Eggert ([email protected]) wrote: On 2020-11-10, at 16:40, Mikkel Fahnøe Jørgensen <[email protected]> wrote: > On 10 November 2020 at 15.32.52, Kazuho Oku ([email protected]) wrote: >> 2. Switching between multiple paths to serve one stream. >> In this case, connection migration of QUIC v1 is sufficient. > > This only works for the client. It doesn’t work server P2P. Given the presence of NATs and firewalls in most scenarios, the client will need to initiate a flow to the server first, before the server can respond (on a new path). Lars
