zlacker

> even if it's only been standardised in 2016, it's been a de-factor standard for quite a while, especially in the internet-technology-years.

If archive.is thinks that Internet standards should be adopted so quickly, it's weird that they don't support IPv6 considering it's been a standard since 1998!

Obviously I'm kidding, but only kind of. When it comes to insisting on adopting new standards, edns-client-subnet is a weird hill to die on, especially considering it was always meant to be optional.

> does Cloudflare the CDN simply disregard ECS when receiving requests from DNS.Google, or do they take it into account?

I don't think they have a reason to use it because they use TCP anycast. Looking at https://cachecheck.opendns.com/ they seem to return the same IPs regardless of geography.

>>profmo+(OP)
When you talk about ECS being optional, you also have to keep the context in mind.

* Yes, if you're running a local resolver for your LAN, or have a website on a single server, of course ECS should be optional.

* If you're running a CDN (and archive.today does), or if you're running a public resolver at 100+ POPs, then, no, ECS is not meant to be optional.

>>cnst+32
"not meant to be optional" is surely a suggestion and not a requirement?

i.e it's not "(...CDN...) then ECS should not be optional"