Re: [100attendees] Incorrect GeoIP for IETF network addresses

[Alexandre PETRESCU <[e-mail]>]

Le 13/11/2017 à 04:16, Chris Morrow a écrit :
>
>
>
> On Mon, Nov 13, 2017 at 2:12 PM Alexandre PETRESCU 
> <[e-mail] <mailto:[e-mail]>> wrote:
>
>
>     Le 13/11/2017 à 03:43, Chris Morrow a écrit :
>>
>>
>>
>>     On Mon, Nov 13, 2017 at 1:35 PM Darshak Thakore
>>     <[e-mail] <mailto:[e-mail]>> wrote:
>>
>>         Hi all,
>>
>>         Is there a way to update the geoIP that the IETF IP addresses
>>         resolve to? I’ve been seeing this behavior for the past few
>>         IETF’s where on google maps (or on bing maps for that matter)
>>         in a browser, when I allow geo-location (while connected to
>>         the IETF* networks) it always resolves to the previous IETF
>>         venue. So today when I click “Your location” button on google
>>         maps, it shows that I’m at Hilton Prague and when I was in
>>         Prague, it showed me Chicago (and so on)
>>
>>         Just wanted to know if there’s something I/we can do to make
>>         it resolve to the right venue
>>
>>
>>     When I open an incognito browser (with no profile, a fresh
>>     browser instance) I see singapore in 'https://maps.google.com'.
>>     When I open https://maps.bing.com in the same browser instance I
>>     see: Atlanta, GA (an ietf was there... a very long time ago?)
>>     When I open https://maps.yahoo.com I get some search results and
>>     a map in there of Dallas, TX.
>>
>>     My android phone's 'maps' application shows me local/Singapore
>>     locations while inside the hotel... It thinks I'm near the
>>     carlton/mint-museum/raffles-hotel... so it's close enough?
>
>     I wonder why this happens this way.
>
>
> {reasons}

It's good to know that it's known why it happens.

>     It seems like a database is updated too late, or that there is
>     latency between update and visibility.
>
>
> my example has the process working though?
>
>     It is the as if the DNS were updated towards a fixed prefix that
>     IETF meetings would carry wherever it moves.
>
>
> I'm not sure that DNS matters quite yet though?
> The ip prefix the IETF network uses is the same (both v4 and v6) for 
> each meeting.
>
>     But I am not sure IETF meetings use same IP addresses wherever the
>     meeting moves?
>
>
> we do.
>
>     Is the IPv6 DNS resolver address constant at IETF meetings?
>
>
> the resolvers are the same, yes.

Ah, that could be part of the reasons then.  I suppose then there is 
tunnelling between Singapore and the home of these constant IP addreses.

For that to work one would need the IP-to-coordinates converters to 
consider also tunnelling - these quantum leaps between worlds, these VPN 
gateways tresspassing country legislation on content delivery, etc.

Or one would need to update the IP routes in the Internet whenever IETF 
moves.  It is possible.

Or update the LOC entries in DNS (if LOC entries are used).  It is also 
possible.

Just some speculation...

Alex

>     Alex
>
>     _______________________________________________
>     100attendees mailing list
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/100attendees
>