Re: [quicwg/base-drafts] QUIC connection migration and IPv6 only NAT64/DNS64 Networks (#2122)

[plakhera <[e-mail]>]

"It would effectively require the server not only to have multiple addresses from the client's perspective"

Not necessarily. The issue is making existing deployments work with the clients.
For now most server deployments are IPv4 only or Dual stack.
If servers are IPv4 only, they can remain IPv4 and a client side solution can work even when one interface has IPv4 only and the other one has IPv6 only connectivity.

For servers that are IPv4 only servers, one could begin on WiFi and then synthesize IPv6 address when WiFi goes away and the connection is being migrated to cellular with IPv6 only NAT64/DNS64 connectivity.
For the other way around, if one gets synthesized AAAA from DNS64, one could try and parse out the last 32 bits and attempt a connection over WiFi with v4 only configuration.

===

The problem that needs more than just client side work-around is for making things work with dual stack sever deployments which I would become more and more common going forward.

"but require the server to have addresses that it can't tell the client about because they're local to the client (NAT64)."

I didn't get this. Can you please elaborate? Server must only communicate their public addresses that are global in scope.

-- 
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/2122#issuecomment-446617371