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

Bob Hinden <bob.hinden@gmail.com> Mon, 13 November 2017 02:45 UTC

Return-Path: <bob.hinden@gmail.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 C8F48127B73 for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 usTwtpE-BVmy for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:45:26 -0800 (PST)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (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 25F8112871F for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:45:20 -0800 (PST)
Received: by mail-wr0-x235.google.com with SMTP id u97so13175081wrc.1 for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:45:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=nrwUPoEkO35Xbr3XTSuYSCAhxQV0a9m4BSLLwE0r1UY=; b=jFqQo1XdJfOWEIK8T/c+OrX0JDut3QbxVd4+Trzc/avUzz2IF8ZezIrAWlo+VZIrJ3 uKRoMv7cG+njPEqqkRLjNK4LQyQaw0nODwW74YPivfQ3cnN0dFauEpFaxbAGFnm/p3HL Dn4s7RKhm3L4fAtmiGD9hPYAQREIEqKWaFamClwoBEWn+1x3Xj46cPyFd2cmUcZFRaUm 7gtJ39+jA+QaKCbN0tWyqv1pOurOApsPipkCLwKIGyJG7poWVEc8IyVIjeKPFflQVDkD IDmf+CEL2icpUr5SJoqbIU6GmlXisFBF8BWRMCpnEzwLGwNNzwYJNOlgkCAq+KnY4rX1 GDRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=nrwUPoEkO35Xbr3XTSuYSCAhxQV0a9m4BSLLwE0r1UY=; b=lkpQq9xs69x6rMruSc1kRGwn9ebisk/tSDxdCICt0kRNqU5Fu0X5pGI9+6iBnEy2ys piKBQoT3o8JYwcbRKeS7eD8si+roccxTdaXtNwfsZagv7KNktHg7l9zgIJ2lpupaHH9K mMB1E7C/LM3y/CPyjuy8TzA0bnCWSD32vPEBZeL1G+fCTm2yMrWmYt5NN4UIyd8l7TMf x/meWf9P0xbF8LDXI9/dcwA7yB3mUpdJV563TFUko3Mdv8T2G7JhNTH71vdUN5T2rCdB qJ+fYK9vpJUDggZs45Nixqrgsyw0YizXNfjsEedQstoJw+aKLbzHUDNPiktVXFUj4zRc U1mQ==
X-Gm-Message-State: AJaThX4qSbbM40gsLXiqeP+VMMDeHuo9hJBi3+LbrpFugrWftB/8Ws+0 I/zWc+lCoNRTz3ITG12v2zubh9sF
X-Google-Smtp-Source: AGs4zMYqMzKzRDlZDB18TqyFbBto4bOuLB/jUD6uPrC7eGMTSuGjWXp9Wi4G3D7hi+XuAbtzgXELmw==
X-Received: by 10.223.161.210 with SMTP id v18mr6137759wrv.76.1510541118731; Sun, 12 Nov 2017 18:45:18 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:1d89:6327:9256:69ce? ([2001:67c:370:128:1d89:6327:9256:69ce]) by smtp.gmail.com with ESMTPSA id z35sm19624145wrc.9.2017.11.12.18.45.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Nov 2017 18:45:18 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <6CD3D82B-7DDD-4293-8BEC-9C110759C80E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_019FF53A-26E5-48B8-8DCB-E4826A69463E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 13 Nov 2017 10:45:14 +0800
In-Reply-To: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "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.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/9Ah6CHW0TDh5-k8SlkxKPRvJGxI>
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:45:33 -0000

Darshak,

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

When I do the same, it shows my location in Singapore.  I am using Safari on MacOS 10.12 over IPv6.

Bob