Anycast multi-region Caddy setup using QUIC's preferred address mechanism #6014
Labels
deferred ⏰
We'll come back to this later
feature ⚙️
New feature or request
upstream ⬆️
Relates to some dependency of this project
The following setup should (in theory) be possible: Multiple Caddy instances authoritative for the same (set of) domain(s) running on geographically distributed servers reachable under the same anycast IP address. The browser connects to the ~closest server, completes the QUIC handshake, and then migrates to the unicast address (to guarantee stable routing over the lifetime of the connection) using QUIC's Server Preferred Address mechanism.
The blog post on quic.video (search for anycast) has a good description and some diagrams.
Protocol-wise, all the required elements are in place. Implementation-wise, this would need proper support for preferred address in quic-go, and I'm still trying to confirm if major browsers have actually implemented this feature.
I'm opening this issue to document the idea, and to see if there's interest in making it happen. I could see setups where this would be very interesting, but I don't know how peoples' deployments look like, so maybe this is just a crazy idea.
The text was updated successfully, but these errors were encountered: