Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 577
    • Issues 577
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 117
    • Merge requests 117
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #89
Closed
Open
Issue created Feb 21, 2018 by Vicky Risk@vickyDeveloper

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

Assignee
Assign to
Time tracking