geo-whois 1. situation apps want location information for users –content localization, lbs,...
DESCRIPTION
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 3TRANSCRIPT
![Page 1: Geo-WHOIS 1. Situation Apps want location information for users –Content localization, LBS, fraud…](https://reader036.vdocument.in/reader036/viewer/2022090107/5a4d1bec7f8b9ab0599e481b/html5/thumbnails/1.jpg)
1
Geo-WHOIS
![Page 2: Geo-WHOIS 1. Situation Apps want location information for users –Content localization, LBS, fraud…](https://reader036.vdocument.in/reader036/viewer/2022090107/5a4d1bec7f8b9ab0599e481b/html5/thumbnails/2.jpg)
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, …
![Page 3: Geo-WHOIS 1. Situation Apps want location information for users –Content localization, LBS, fraud…](https://reader036.vdocument.in/reader036/viewer/2022090107/5a4d1bec7f8b9ab0599e481b/html5/thumbnails/3.jpg)
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
![Page 4: Geo-WHOIS 1. Situation Apps want location information for users –Content localization, LBS, fraud…](https://reader036.vdocument.in/reader036/viewer/2022090107/5a4d1bec7f8b9ab0599e481b/html5/thumbnails/4.jpg)
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