IETF Logo Mail Archive

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

Chris Morrow <morrowc@google.com> Mon, 13 November 2017 03:16 UTC

Return-Path: <morrowc@google.com>
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 F0E2012700F for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:16:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 63CCSQaySFKQ for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:16:23 -0800 (PST)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BB92127876 for <100attendees@ietf.org>; Sun, 12 Nov 2017 19:16:21 -0800 (PST)
Received: by mail-io0-x22b.google.com with SMTP id 189so19092988iow.10 for <100attendees@ietf.org>; Sun, 12 Nov 2017 19:16:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3DHl7ad/GLIt58dkKPueIRdhFU1ZtY0SpfMITDJC0t8=; b=BCglkm0dyShpdPydQLJ3usn8resxK7ClIAhY9R7gBuFiktncSDylxD6ByaxX8bwaCg fIvGsBAchq0Wq/qZW5VzKKVP1qJ6ncoCaIth9o4giBKGh998u1miz+rArce3AZh6tHyo b+68e7Mmv+tO6BD27YykClBKeZRESbWy/Vm2bG12x55FOMUVHtTsNsvjjVwlecute7xq lQiF35VziBFfg9M+7erMcsNg6IsUbTidMjCxW1z8FFrPVh1SVjmSp4X/mgk0LDuwnMzE wyHotAfsg13ipQkr9yd3GWysPTA1tPEiRTXxCjKDYKczZc/njqxiA1jKuoOnLLsKAZR6 L8xQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3DHl7ad/GLIt58dkKPueIRdhFU1ZtY0SpfMITDJC0t8=; b=cFRCNDu+Sbl7FD7Sjs4tkwzsfy+wGsiD/316+W3fNVcb9uYkfvyoKIqF0sOirimIBA DNKQ/urEbdtQb0tf5xQwxFBZdDuf7Bw4T5FXVhUREyd7Ws4Iypb/lPreFIe47UvqtzVu J+ncj5+s0GOwQSTt6jgwBUqs+I4c2rarph58LEwYQRfDpZ+hj0SMcTMOwpiAbHPWgglU gu4ULDBLlC4FYnjYSgVuHfQMETNJPPZE6w14agIachMGXfxly1fADuHBfP/13C3YrMEb Wti0OczyncOKeu3t03BWZekSmjl1bZwNktZMxt8DgNOBWTIUZRWEYYZLBW6AhiOSxVwH ET+Q==
X-Gm-Message-State: AJaThX4zHU2jEd27H/PVHNMDbdWYWqw+3OMkwF2NVGzjulP+CHk2vJJ+ 8aZ9qSGfUFb2vc+iKqzixh+W0hO1EJy/rgWFmZuX4hq9
X-Google-Smtp-Source: AGs4zMYWMixoRpjFukKGvkRzX+7a8jR9dGPqpDsAdpZ+Cy2K3//rK0o6d/PIvqrENcLT+VaNU9/cG+LAql/XcXWynAw=
X-Received: by 10.107.181.215 with SMTP id e206mr8533735iof.98.1510542980419; Sun, 12 Nov 2017 19:16:20 -0800 (PST)
MIME-Version: 1.0
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com> <CAMeF8nB4WaMwi0LV8WwBHNaMTyomBExv0=M9TFNGzm-3bWNHWw@mail.gmail.com> <dccbfa53-45dc-44df-e2dc-34ab18af17b5@cea.fr>
In-Reply-To: <dccbfa53-45dc-44df-e2dc-34ab18af17b5@cea.fr>
From: Chris Morrow <morrowc@google.com>
Date: Mon, 13 Nov 2017 03:16:09 +0000
Message-ID: <CAMeF8nBHd-OrmDMZo6qUmoMGNc5MfPj0cjJnkQbCypni5xpuMA@mail.gmail.com>
To: alexandre.petrescu@cea.fr
Cc: 100attendees@ietf.org
Content-Type: multipart/alternative; boundary="001a114446ccc4935c055dd4b1ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/6OBoFQm_Id0teKLLiBCIHvQl-y4>
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:16:32 -0000

On Mon, Nov 13, 2017 at 2:12 PM Alexandre PETRESCU <
alexandre.petrescu@cea.fr> wrote:

>
> 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>
> 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 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.


> Alex
>
> _______________________________________________
> 100attendees mailing list
> 100attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/100attendees
>

v2.8.7 | Report a Bug | By Email