Re: [100attendees] Incorrect GeoIP for IETF network addresses
Chris Morrow <morrowc@google.com> Mon, 13 November 2017 03:11 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 0058F127077 for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:11:25 -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 fdlB-vjq0a7F for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:11:23 -0800 (PST)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 AD279128796 for <100attendees@ietf.org>; Sun, 12 Nov 2017 19:11:18 -0800 (PST)
Received: by mail-it0-x22e.google.com with SMTP id c3so7705034itc.3 for <100attendees@ietf.org>; Sun, 12 Nov 2017 19:11:18 -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=dmJeRAw5Ujt8YTsktmYuQwQRMXG5tv+OD7DyNupecP8=; b=el10Gmhks6bRCyUCV7u/4n+z3eH1yoWfK7BCz363Hn3TilySh0soaY3cyZ7r75/xa/ rx1uUC9BfksLPix44WOhRAqnpe+omVi8UzXs4vMCeqWKfnXNJa4mWn0A/WbRSZI4+9Xy 7L55UAGeVgMf1GiEh4ZFEK7J3LGvqUvuXqVCClzYL/1KZeHZeW/Tq/xgfstg6kO1bszs H9NHznt8pzEh41TkxiUO9FyU7u6WGFGoeWHuWuvpTTL55IijHbcQ2kn3OXOVyWGreixN LEg6GMFBfCAZ7KxwJBHqq72VOCkxnS32oUZKIhSYDi096SxTWqWpYaCGWHrMeCKVRcRK mm+Q==
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=dmJeRAw5Ujt8YTsktmYuQwQRMXG5tv+OD7DyNupecP8=; b=MsziEDqPUjJh0OQUK2j9UiomY832YS2gM6/ad84dHltl+nVAfNwDqUFQb0dN/iz3DW GvpGtfpuQTWoq//liYURooKj6PsPVZNsHo/pNUccp++0dPX/7/+E+piwVjV9HfVO6KFi Y7FqkMT+db8spg6Z9bt8I1j4tHNrWgun4DuAAWtebsBJ59ru9Ej+K7oahhN5GoIu7nwX 9TAyW3Pm404QCNSj8gGiHt6O3EHWZcjJsnnKbJ8gGZ/6/nl7nOeTchApwIDPMOf3jK6n v/myJIAEB9GvSFUSHBBmGSDkeRuq+JHCOt8mWlBiYX9c3b03pxXKHq+yeepfbQgIp7Mh VZbg==
X-Gm-Message-State: AJaThX45+DKRIPwL4LZdaFGfbSQPcce38c8LwCs4ljWqXzooh2cPvY32 /s0NNjytUuw9K+6qMG8YIcDGQegvtbt7icchUNm+PlyV
X-Google-Smtp-Source: AGs4zMbMi052CQrn0BMQY3JWAeUcVdEXKBEM/8UaWdt/g5ly25MrTwuiWH40PNxPZ44SCJw0+uRqul8phIyiQgTKZVI=
X-Received: by 10.36.9.146 with SMTP id 140mr430295itm.54.1510542677577; Sun, 12 Nov 2017 19:11:17 -0800 (PST)
MIME-Version: 1.0
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com> <CAHw9_iKgvnf7GToqv0gYaooaOP5wFv2SRRXYrQr7Mge0ENWrRQ@mail.gmail.com> <554E768D-2B2C-4E0D-AE83-075626656B7C@cablelabs.com>
In-Reply-To: <554E768D-2B2C-4E0D-AE83-075626656B7C@cablelabs.com>
From: Chris Morrow <morrowc@google.com>
Date: Mon, 13 Nov 2017 03:11:06 +0000
Message-ID: <CAMeF8nC1H9W3TXmk1XSWjzt=uyGGq8sRv=n3dLioiBbmPQ2pQA@mail.gmail.com>
To: Darshak Thakore <d.thakore@cablelabs.com>
Cc: 100attendees@ietf.org
Content-Type: multipart/alternative; boundary="001a1135b4fab7be94055dd49f2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/zEGoeKc_vkQqDmXVBLu8aIrmHXk>
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:11:25 -0000
On Mon, Nov 13, 2017 at 2:00 PM Darshak Thakore <d.thakore@cablelabs.com> wrote: > Thanks all for the feedback > So here are the results of my experiment > > 1. Google Chrome (logged into my google profile) - Just going to > maps.google.com takes me to www.google.com.sg/maps (which is expected) > and shows me Singapore location and the “My Location” button shows that it > acquired my location from my phone history (I have a pixel connected to the > same account). However clicking on the button takes me to Hilton Prague > 2. Google Chrome Incognito – Takes me to google.com.sg but clicking on > “My Location” takes me to Hilton Prague > 3. Firefox (logged into my google account) – Same behavior as Chrome – > clicking “My Location” takes me to Prague > 4. Firefox Incognito – Takes me to Prague > 5. Safari – going to maps.google.com takes me to google.com.sg/maps AND > clicking on Location, it actually seems to work right > > all of the above is odd, I'd be happy to see your tests (in the noc). > Jim, I’ll swing by the NOC in Indiana shortly to see if can collect some > data points > > Darshak > > On 11/12/17, 7:44 PM, "Warren Kumari" <warren@kumari.net> wrote: > > CableLabs WARNING: The sender of this email could not be validated and > may not match the person in the "From" field. > > On Mon, 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, this is a long, and ongoing problem -- there are many geo-location > databases, and getting all of them updated is hard. > Erik Kline wrote a document which helps with this -- > https://tools.ietf.org/html/draft-google-self-published-geofeeds-02 > and the IETF has published these... > > Also, many of the geo solutions also include stuff like the BSSID / > MAC address of the radio you are connected to... > > > 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) > > > > So, thi time we thought we got this right for Google / Google Maps at > least -- for me / other people who have tried this it seems to finally > believe that we are were, er, we are... > > W > > > > > > > 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 > > https://www.ietf.org/mailman/listinfo/100attendees > > > > > > -- > I don't think the execution is relevant when it was obviously a bad > idea in the first place. > This is like putting rabid weasels in your pants, and later expressing > regret at having chosen those particular rabid weasels and that pair > of pants. > ---maf > > > _______________________________________________ > 100attendees mailing list > 100attendees@ietf.org > https://www.ietf.org/mailman/listinfo/100attendees >
- [100attendees] Incorrect GeoIP for IETF network a… Darshak Thakore
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Bob Hinden
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Carlos M. Martinez
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Jim Martin
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Warren Kumari
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Mike Bishop
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Darshak Thakore
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Michal Krsek
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Darshak Thakore
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Michal Krsek
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Jim Martin
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Michal Krsek
- Re: [100attendees] Incorrect GeoIP for IETF netwo… joel jaeggli