ipv6 and geolocation

Tue Oct 22 20:00:48 UTC 2013

it seems like solving your first complaint is the same work as solving your second:

1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. 1h IN  PTR host.example.com.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. 1h IN  LOC 40 45 33 N 73 59 07 W 100m 

________________________________________
From: Blair Trosper [blair.trosper at gmail.com]
Sent: Tuesday, October 22, 2013 3:16 PM
To: nanog at nanog.org
Subject: ipv6 and geolocation

Everyone loves IPv6, and it's a fantastic technology.  However, I've been
pondering a few quirks of v6, including the low priority of PTR, but I have
a question I want to throw out there:

Do you think IPv6 geolocatoin (GeoIP) will ever be viable?

If so, when do you think this will happen?  If not, what's the superseding
solution?  (The W3C location technology fails miserably for me 100% of the
time even on IPv4).

Two of the "big four" GeoIP providers don't even catalog IPv6, and the
other two's IPv6 database is unremarkable and usually only has the country.
 (Or, in my case, a block that's clearly in the United States is deemed as
simply "(somewhere in) Asia".)

What I'm getting at is:  IPv6 geolocation is presently rather hopeless and
useless.

Eager to hear thoughts from my fellow network thinkers!

- Blair