Description
Specification
The QUIC specification allows connections to be migrated. Usually this applies to the client. This means the client can migrate its connection from an old IP address and port to a new IP address and port while maintaining connection context with the server. Which is useful for mobile clients.
However I don't think anything actually prevents the server from doing this too.
Connection migration hasn't been investigated at all. So supporting this would be an interesting capability to allow Polykey agents to be mobile.
My understanding is that any given client (and or server) may find itself with a new IP/port. In that case, it would still have all the existing QUICConnection objects. Thus when they send packets out, they'd be sending from a new origin IP address and port.
There are some functions on the quiche code that apparently allows one to start the connection migration process. I'm not sure if this is done before or after the IP/port has already changed?
Additional context
Tasks
- ...
- ...
- ...