On Thu, Dec 10, 2015 at 2:33 PM, Jared Mauch <jared@puck.nether.net> wrote:

> On Dec 10, 2015, at 6:21 AM, Philip Homburg <philip.homburg@ripe.net> wrote:
>
> On 2015/12/10 10:11 , Willem Toorop wrote:
>> And sending arbitrary EDNS0 options? Have you ever considered that too?
>> Is it on the todo list too?
>
> Hi Willem,
>
> Just about all EDNS0 options take parameters. It is not part of the
> model to allow users to inject arbitrary binary data. Though if there is
> sufficient interest, we can add some of the options currently proposed
> (cookies, keepalive)

client-subnet? :)

- Jared

Is this really useful? I mean, if a DNS server honors client-subnet, then it doesn't really matter which node is making the lookup. you might as well loop over your local machine and change the client-subnet.

what could be very interesting though, is to map DNS servers supporting EDNS0 and ones not supporting it (i.e. which network operators should be bugged to support it...). it would be very good for network operators to see e.g. in-country adoption rate before relying on a CDN using EDNS0 as the core POP routing technology.