Stefano,
> Subject: QUIC connection migration to an IPv4-only network when connected to > a server's IPv6 address > > Hi all, > > > I'm trying to solve the following common scenario: a client has a QUIC > connection to a server's IPv6 address and has to migrate the connection to an > IPv4-only network. > > > Currently, our implementation will attempt to connect to the server's IPv6 > address via the IPv4-only network and will (expectedly) fail. > > > I can think of two main solutions, the client could instead migrate to the > IPv4: > > Provided in the preferred_address extension, during the initial TLS handshake > > Returned by the A query, that was sent alongside the AAAA query that > contained the IPv6 address currently being used by the client > The best approach is to standardize a QUIC extension that indicates that the server has several IP addresses. This would be an excellent use case for https://datatracker.ietf.org/doc/html/draft-piraux-quic-additional-addresses-04 Olivier
