[179304] in North American Network Operators' Group
Re: Fixing Google geolocation screwups
daemon@ATHENA.MIT.EDU (Max Tulyev)
Wed Apr 8 09:26:54 2015
X-Original-To: nanog@nanog.org
Date: Wed, 08 Apr 2015 16:26:49 +0300
From: Max Tulyev <maxtul@netassist.ua>
To: Jeroen Massar <jeroen@massar.ch>, nanog@nanog.org
In-Reply-To: <55251764.5060204@massar.ch>
Errors-To: nanog-bounces@nanog.org
On 04/08/15 14:56, Jeroen Massar wrote:
> That stated, properly providing a WHOIS entry for each prefix
> (inetnum/inet6num) is a good idea as that kind of indicates that that
> prefix is fixed in that location and not just moving around.
[skip]
> Do make sure though that you do not show any foreign address in the
> whois data (even if that is the correct entity that the prefix is
> registered under)
Seems that it is contrary to each other ;)
I thought to do something like automated whois query on tunnel
destination and put that (geo)data to each /48 inet6num tunnelled. But
as I don't believe it will help, so priority of that task is low and not
yet realized.
