geo-whois 1. situation apps want location information for users –content localization, lbs,...

4
Geo-WHOIS 1

Upload: bruno-phillips

Post on 20-Jan-2018

212 views

Category:

Documents


0 download

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 3

TRANSCRIPT

Page 1: Geo-WHOIS 1. Situation Apps want location information for users –Content localization, LBS, fraud…

1

Geo-WHOIS

Page 2: Geo-WHOIS 1. Situation Apps want location information for users –Content localization, LBS, fraud…

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…

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…

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