Peace,
On Tue, Aug 3, 2021, 6:53 PM Christian Huitema <huitema@xxxxxxxxxxx> wrote:
The anycast connection stability issue is addressed in QUIC. During the
initial handshake, QUIC servers can provide a "preferred address" (IP or
IPv6 and port number), and the client can immediately migrate the
connection to use that address. This was specifically designed to
support servers listening on anycast addresses, so the connection can be
pinned to an unicast address specific to the server.
From the operational standpoint, this only addresses one particular scenario where anycast ensures latency reduction (think CDNs). However, in the today's Internet, the unicast nodes most adjacent to the client are already advertised through DNS records, which also saves a handshake if compared to the solution QUIC offers.
There are use cases where unicast is not fit, and the server address must be kept anycast at all times.
--
Töma
