1 / 4

Geo-WHOIS

Geo-WHOIS. Situation. Apps want location information for users Content localization, LBS, fraud mitigation, … They can’t ask the networks, so they guess WHOIS, traceroute , WiFi /cell tower, …. Problem. Apps get low-quality information Subscribers get degraded service

mio
Download Presentation

Geo-WHOIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Geo-WHOIS

  2. Situation • Apps want location information for users • Content localization, LBS, fraud mitigation, … • They can’t ask the networks, so they guess • WHOIS, traceroute, WiFi/cell tower, …

  3. Problem • Apps get low-quality information • Subscribers get degraded service • Operators don’t have a good channel to fix problems • Interim solutions are doing very bad things for privacy

  4. Solution (?) geoloc: https://lis.example.org:4802/ geoloc: geo:42.389984,-71.1471;u=2500 • Add an explicit geolocation field to WHOIS • Contents: URI pointing to location resource • HELD for granular location (prefix, address) [RFC5985] • GEO for static, generic location [RFC5870] • Indirection allows operator control of privacy • Proposals under consideration in RIPE, APNIC

More Related