zlacker

[parent] [thread] 3 comments
1. pierat+(OP)[view] [source] 2023-08-02 17:04:36
> In this particular case we truncate EDNS to protect the privacy of users

In other words, you want the data, but prevent others from seeing your advantage?

This is what archive.is is doing, and you stomp your collective feet at.

> because we believe 1) privacy is a fundamental human right; and 2) the original sin of the Internet is that IP addresses are too closely tied to the identities of individuals and services.

If you cared about that, you wouldn't either block Tor or send us through captcha-hell just to pull a single webpage.

> Truncating EDNS is trying to honor #1 and overcome #2. So is our work on protocols like Oblivious DNS. This work, frankly, upsets some of our customers or potential customers (like Archive.is). But it’s the right thing to do for the long term health of the Internet.

'Upsets'? Wow. Talk about a "Rules for thee but not for me."

replies(1): >>cmeach+Iw
2. cmeach+Iw[view] [source] 2023-08-02 19:14:45
>>pierat+(OP)
What advantage? Is there reason to believe that 1.1.1.1 treats CloudFlare's CDN specially and forwards EDNS info or similar?
replies(1): >>nora-p+gN
◧◩
3. nora-p+gN[view] [source] [discussion] 2023-08-02 20:14:55
>>cmeach+Iw
EDNS absence does affect cheap DNS-based CDNs and has to effect on expensive AnyCast CDNs (one of them is CloudFlare CDN).
replies(1): >>supriy+o02
◧◩◪
4. supriy+o02[view] [source] [discussion] 2023-08-03 04:25:32
>>nora-p+gN
Amazon’s Cloudfront is anything but cheap, but they too are based on DNS based routing.
[go to top]