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

Jim Martin <jim@daedelus.com> Mon, 13 November 2017 02:42 UTC

Return-Path: <jim@daedelus.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 C79901271DF for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 vVVFlrBTqYBy for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:42:07 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A797127A90 for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:41:57 -0800 (PST)
Received: from imladris.daedelus.com (imladris.daedelus.com [206.197.161.143]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 63602880D1; Sun, 12 Nov 2017 18:41:53 -0800 (PST)
Received: from [IPv6:2001:67c:370::6d20:7c15:3c3c:c70e] (unknown [IPv6:2001:67c:370:0:6d20:7c15:3c3c:c70e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by imladris.daedelus.com (Postfix) with ESMTP id CFB951308395; Sun, 12 Nov 2017 18:41:50 -0800 (PST)
From: Jim Martin <jim@daedelus.com>
Message-Id: <52A5E595-D18B-456E-8242-C2B7A4CC2AB7@daedelus.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F70073A6-8A8C-4174-841D-B1AE27B19FA4"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.11\))
Date: Mon, 13 Nov 2017 10:41:38 +0800
In-Reply-To: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
Cc: "100attendees@ietf.org" <100attendees@ietf.org>
To: Darshak Thakore <d.thakore@cablelabs.com>
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
X-Mailer: Apple Mail (2.3445.5.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/sWQ8mi_yHHaeOjUxzyBnlKQCM_4>
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:42:10 -0000

Darshak,
	This is a sadly complicated issue. There is no geolocation standard, so it’s a matter of trying to update the various organizations that provide geolocation services. We work closely with Google, and  try to work with SkyHook (the geolocation that Apple uses for BSSID based location) and MaxMind (a common location provider). Unfortunately, these are a bit hit or miss, as they’re not really setup for a non-trivial network to move around the world. We continue to work on it, and are always open to help, if anyone has suggestions. 

	BTW: In terms of google maps, it “works for me” on my Mac using Safari right now. Swing by the NOC in Indiana if you get the chance so we can try to understand the differences in results. Thanks!

	-Jim


> On Nov 13, 2017, at 10:34 AM, 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
>  
> Darshak
> _______________________________________________
> 100attendees mailing list
> 100attendees@ietf.org <mailto:100attendees@ietf.org>
> https://www.ietf.org/mailman/listinfo/100attendees <https://www.ietf.org/mailman/listinfo/100attendees>