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

[janaiyengar <[e-mail]>]

So, preferred_address has slightly different semantics than what you're asking for. It currently means that the server prefers that the client use the indicated address. What you want is an _alternate_ address, something that the client can use if it migrates to a network on a different address family.

I think we can get the low-hanging fruit here by having alternate_address_v4 and alternate_address_v6 transport parameters. That said, I'm not convinced of how important this is to solve in v1. This affects only migrations, and then only those that are from networks on one address family to a different one.

I'll note that an explicit ADD/DELETE_ADDR doesn't work because of NATs (as @mikkelfj notes).  That is fine; in the spec, we've basically used receiving a packet from a new address as an implicit ADD_ADDR signal. The problem you're running into right now is that we don't support server migration in v1, which doesn't allow a server to send a packet from an unknown address to a client.

-- 
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-446811780