Thanks both,
So, I seem to gather that the main problem is to put forward Geolocation as
a way to return pseudo-targeted answers to end-users by using the resolver
IP as a proxy for it. This was more meant to be a use-case as to how geo
location has been used, but It is by no means my intent to pu
> Il 20/11/2020 18:49 Brian Dickson ha
> scritto:
>
> But let's not get distracted by that in the short term, where direct use
> of resolver geo has real value.
>
Also, legal/jurisdiction issues depend on geography and not on network
topology. As data localization and privacy protect
On Thu, Nov 19, 2020 at 9:35 AM Ben Schwartz wrote:
>
> I do not support the geolocation function. I think the right solution
> here is ECS. Even bad IP-geolocation from ECS will be better than using
> the recursive resolver's country-code; at least it will be estimating the
> location of the r
I support the resolver IP range discovery function. I don't think it will
be hard to come up with a reasonable format for that. An APL record with
standard address families would seem fine. A URI record pointed at a JSON
blob or a flat text file would be fine too.
I do not support the geolocati
Hey all,
Thanks a lot for providing feedback on the resolver IP ranges and location
distribution draft [0] during the dnsop meeting.
I gathered the feedbacks below as follow-ups, but, based on some of the
comments made at the "mic" or over Jabber, I would also to provide some
clarifications as to
