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

Alexandre PETRESCU <alexandre.petrescu@cea.fr> Mon, 13 November 2017 03:12 UTC

Return-Path: <alexandre.petrescu@cea.fr>
X-Original-To: 100attendees@ietfa.amsl.com
Delivered-To: 100attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FFAD1293DA for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:12:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtTKkchvdsiN for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:12:44 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F395127077 for <100attendees@ietf.org>; Sun, 12 Nov 2017 19:12:44 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAD3Cgfm014106 for <100attendees@ietf.org>; Mon, 13 Nov 2017 04:12:42 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B46CD200F16 for <100attendees@ietf.org>; Mon, 13 Nov 2017 04:12:42 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A6785200CA6 for <100attendees@ietf.org>; Mon, 13 Nov 2017 04:12:42 +0100 (CET)
Received: from [132.166.84.2] ([132.166.84.2]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAD3CeR9007269 for <100attendees@ietf.org>; Mon, 13 Nov 2017 04:12:41 +0100
To: 100attendees@ietf.org
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com> <CAMeF8nB4WaMwi0LV8WwBHNaMTyomBExv0=M9TFNGzm-3bWNHWw@mail.gmail.com>
From: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
Organization: CEA
Message-ID: <dccbfa53-45dc-44df-e2dc-34ab18af17b5@cea.fr>
Date: Mon, 13 Nov 2017 04:12:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAMeF8nB4WaMwi0LV8WwBHNaMTyomBExv0=M9TFNGzm-3bWNHWw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms090202060305080905010002"
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/hHWCzRD33mZaiiBufoHegfrUNgw>
Subject: Re: [100attendees] Incorrect GeoIP for IETF network addresses
X-BeenThere: 100attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Mailing list of IETF 100 attendees that have opted in on this list." <100attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/100attendees>, <mailto:100attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/100attendees/>
List-Post: <mailto:100attendees@ietf.org>
List-Help: <mailto:100attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/100attendees>, <mailto:100attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 03:12:47 -0000

Le 13/11/2017 à 03:43, Chris Morrow a écrit :
>
>
>
> On Mon, Nov 13, 2017 at 1:35 PM Darshak Thakore 
> <d.thakore@cablelabs.com <mailto:d.thakore@cablelabs.com>> 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.

It seems like a database is updated too late, or that there is latency 
between update and visibility.

It is the as if the DNS were updated towards a fixed prefix that IETF 
meetings would carry wherever it moves.

But I am not sure IETF meetings use same IP addresses wherever the 
meeting moves?

Is the IPv6 DNS resolver address constant at IETF meetings?

Alex