IETF Logo Mail Archive

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

Chris Morrow <morrowc@google.com> Mon, 13 November 2017 02:44 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 49419128B38 for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:44:39 -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 y-HrZOVTppsQ for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:44:37 -0800 (PST)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 583D8127077 for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:44:12 -0800 (PST)
Received: by mail-io0-x22a.google.com with SMTP id 189so19042554iow.10 for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:44:12 -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=RkVeRXeVR5iqSSoZYm3fsZ3xHqPq6W/XYuwltJKAf+4=; b=Nju6h4t7rXiKLjFRe5ry0uHDsmerNRQeWUc1NDUa8RuFvhf0r0te7ODyXg6MtLjwci 7bpFpB9xuUdi1BrsIBHjegM6LooiI9/4TyM5p6swcShO87QxUEQkTti1MQVazHRqgmFE h3pX5YeY4AO3bUK3SsFrMtFStHuz4W0lstg0gnyAiSDe31qwAp1h+sM//9cHRlJhCRfm USQvx5El2w/aoOV95gEHrsfoqywXNqhG44WZzP5m/mjmfupjnNdTe/AWM56HUvWByTzu QRFvBM79XGSSBraldvZrjd0HJw2YSsP8ZkK7HEz3WreeKvoAwdOJ/14TQRyBH3EcFkgq FfEg==
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=RkVeRXeVR5iqSSoZYm3fsZ3xHqPq6W/XYuwltJKAf+4=; b=KBtf1EcXyMwfIRXV1Y2KtrBMSxmuonFruqpyywz0xE+iHf0pIrEj4WyDtdoOhFjV5S aiKXS1grGEaelHvbXoW9XR244BcnRsepS8g8OvtzA9XPiduNIphsDZEeaerfzyDr00qC ZiqBYSElMR+G2b2skEi+dh7n9NpuMg++X8UvFGzoU2kKTm5vM1o3ZXxl9ldp7dO6+d/o CWqA+fQi7O/OrZO/9QXDtGGod8fj9Mzo7/DEtjsVQwbp4OoI4qSPkuKC3zgFzpwhVXZH zF+LDYeZ4YOGX7480i9hfB5Rk56sUPP0JIkqRfjWGjMg7208MtaS9HMxFNdXmBBXANCp KeBw==
X-Gm-Message-State: AJaThX6bLYyrVyp4hGqFIGa6x14Ozj7htfXOQrjSxnsj3jB1fvUEj+TU l2cWd7nE1d6Vfx6+xlz8s3Wu3OwslXeEXA01i48ZYa8e
X-Google-Smtp-Source: AGs4zMYAUqp3iVe2u7dzdDSe3rPHAlFTRHnC2G4F8nVDUIkULOs6Wv5LkTpdjRLVvz0ZV0F0LKk1DFJmxauIWTmKGh0=
X-Received: by 10.107.163.15 with SMTP id m15mr8634800ioe.61.1510541051294; Sun, 12 Nov 2017 18:44:11 -0800 (PST)
MIME-Version: 1.0
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
In-Reply-To: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
From: Chris Morrow <morrowc@google.com>
Date: Mon, 13 Nov 2017 02:43:57 +0000
Message-ID: <CAMeF8nB4WaMwi0LV8WwBHNaMTyomBExv0=M9TFNGzm-3bWNHWw@mail.gmail.com>
To: Darshak Thakore <d.thakore@cablelabs.com>
Cc: 100attendees@ietf.org
Content-Type: multipart/alternative; boundary="001a11402f14c888b9055dd43e29"
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/aYudvPui5pAMOQkmGU2GNvd6Mxc>
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 02:44:39 -0000

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?

v2.8.7 | Report a Bug | By Email