New Geolocation protocol with greater privacy protection for end user
Can we try to design a new way to specify the end-users geographic location, for purposes of sending them to an efficient, local content source (as an alternative to EDNS client-subnet-identifier)?
Goals
- Provide authority with information about client geography suitable for routing purposes
- Minimize excessive cache bloating by only carving out caches at a level of specificity actually useful for content routing
- Avoid identifying the client by IP address or other specific identifier (preserving privacy)
Ideas
- The resolver could tag the query with a geo location, rather than forwarding client ID to the authority
- We could consider using the LOC rr (type 29)
- The IATA code (closest airport) is probably granular enough for content routing
- Adding the AS of the network the user is on might also be relevant and useful
We should discuss with the other open source DNS developers, perhaps in our usual get-together at the next IETF
To upload designs, you'll need to enable LFS. More information