Support connection migration

[lucas-clemente]

No description provided.

[heri16]

Would really like this to be implemented and tested. Is there anything i can help with to make this happen. Would the connection migration logic be built into #931 or #1095 ?

[marten-seemann]

Connection migration happens at the QUIC later, not the h2quic layer. We won’t support connection migration to quic-go until the mechanism is fully specified by the IETF.

[xushichang0]

I want to check the latest status of connection migration implementation. Is it supported now? The IETF draft has a full section on this. Thanks!

[marten-seemann]

It's not yet implemented.

[machao0322]

Thanks for your contribution! The implementation of QUIC is a great help for me!
Is connection migration supported now?

[khalid-huang]

+1

[yrashk]

Now that RFC9000 is out, perhaps it might be worth looking into this matter again? Happy to offer any help necessary.

[niknah]

I have tried to use this tool as something to keep a ssh connection running. It was disconnecting more than direct TCP even when I'm not changing my IP, just moving across the wifi mesh. Even if it supported connection migration, it wouldn't be reliable enough for me to use.

[ka1tte]

Are there any plans for connection migration recently?

[zzhlong]

Quic go is currently used
Start the long connection between the server and the client to communicate with each other
The client network switching will result in the inability to receive the server messages, and will disconnect after the timeout set by the client
Is there an example of connection migration?
I'm looking forward to it. It will help me a lot. Thank you !!

[hetelek]

@marten-seemann, regarding your comment here: #3727 (comment)

On the client side, we’d somehow need to detect new network interfaces and migrate to a new connection there. Or maybe that would be the responsibility of the application and the connection would migrate to a new DialListener?

For my use case, it'd be fine for the application to be responsible for detecting network interface changes and initiating the migration. Some ideas:

• conn.Reconnect() - the app could call this to attempt to migrate/re-establish the connection, using the system default route. For example, I could call this after the default system route changes from cell -> wifi.
• conn.MigrateTo("1.2.3.4") - the app could call this to migrate the connection to a specific interface.

[marten-seemann]

I just posted an API suggestion in #3990. Note that this doesn’t mean that this API will actually be implemented any time soon.