Re: [100attendees] Incorrect GeoIP for IETF network addresses
Mike Bishop <mbishop@evequefou.be> Mon, 13 November 2017 02:52 UTC
Return-Path: <mbishop@evequefou.be>
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 E9944128ACA
for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
HTML_MESSAGE=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 (1024-bit key)
header.d=evequefou.onmicrosoft.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 7TvoXnzE7x2r for <100attendees@ietfa.amsl.com>;
Sun, 12 Nov 2017 18:52:04 -0800 (PST)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com
(mail-by2nam01on0111.outbound.protection.outlook.com [104.47.34.111])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 373E0127B52
for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:52:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=evequefou.onmicrosoft.com; s=selector1-evequefou-be;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
bh=dfxlREMh4H4MfPdZTuZcHXBg9Vhph4yNIrrf9uhIGnA=;
b=Mc6o9qDOiv9f32/CIZS834+m4G/yJm47wLBuFZHaxb3AtP3wirtOAd5LJ81TQaFDsbHvxvK2PNPB7WDHErhCCZ0nwc9Ee8MQ6RPItyWvq5H5VpTvb2AL4TJwLMY2pRTi5YwAg/nPqmnqFIio1kaNKYmj+9DguvJ5Fg8qfX6fP3E=
Received: from MWHPR08MB2432.namprd08.prod.outlook.com (10.169.203.136) by
MWHPR08MB2429.namprd08.prod.outlook.com (10.169.203.20) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
15.20.218.12; Mon, 13 Nov 2017 02:52:01 +0000
Received: from MWHPR08MB2432.namprd08.prod.outlook.com ([10.169.203.136]) by
MWHPR08MB2432.namprd08.prod.outlook.com ([10.169.203.136]) with mapi id
15.20.0218.015; Mon, 13 Nov 2017 02:52:01 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Jim Martin <jim@daedelus.com>, Darshak Thakore <d.thakore@cablelabs.com>
CC: "100attendees@ietf.org" <100attendees@ietf.org>
Thread-Topic: [100attendees] Incorrect GeoIP for IETF network addresses
Thread-Index: AQHTXCf3mWiGz+tsl02HkYfeWvY9hKMRmYsAgAACF5A=
Date: Mon, 13 Nov 2017 02:52:01 +0000
Message-ID: <MWHPR08MB2432297B11CA2EF0619C43DFDA2B0@MWHPR08MB2432.namprd08.prod.outlook.com>
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
<52A5E595-D18B-456E-8242-C2B7A4CC2AB7@daedelus.com>
In-Reply-To: <52A5E595-D18B-456E-8242-C2B7A4CC2AB7@daedelus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=mbishop@evequefou.be;
x-originating-ip: [2001:67c:370:1998:25bf:ef23:4f10:d942]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR08MB2429;
6:LFdwmWkBd9BfWpuef16RKy7NacCiIf0234axEgdTsjfX8oVUE0zxkDqZZ0IW88FF6zEEe8ERasiInpo0maAGl0czp4gHadMSqOz0t8sL7vFiV5Sgte1XUOaz7UqlsEt14gAsv/AxW/28lYvg9Pz+8SFhTbsJB6iosoCPZJ3mBd6Icgma60UiT7BVm35256eehwDQK9zrhdhHG0pM9fEah9s86bUFmpnpn9UmLd2O0p0yAxMovruGXnsNRgHx5clr46RKB+yLb6C8RAhLKcn4ZQC1iIWbXLLvFwpP5/LhG3AvHJ/WFbhGMNO2i3yI4i3aFR1311McbTqEbOiiTmOkwIIa0EzjlwUp6lpuCuP2UDU=;
5:hMIuHPkvqMlHr3dqcuiWLCnLp3JWw4Ju8JZV8zc+wcUL1n8YBqZUmrcabKArVCCzKKEc0KxkbFZPng3eBITfI1unKnh6u7Z/RgG8R4k41plrSlwZqTvZzsmY466jcTo4yaqYjIOwNnQhO5qSYhmf/iMXwO5PhKZGVb4QQ78vzGw=;
24:wQhq/3TECEkwCG5YUV1pp4E9oa/Z6PdNukVhq1y3RR+qmf8cuIuU81Qo25tbPdBYNUMzy7pmdWButoU7/DoC1gnuuXD7kdue3oIAUiURa6I=;
7:kldRA2kvDBfHtNhL6UcySY/mIFsbM5ai3ZPEQDdLPnQYO5ILb4ZvnrtlrorrjuqPkPaJhAsVWBy4FIaiaao7oX5ZVhPjnAWL7CgwISyjG4+sXB5RoQA41dTJijDZf8/17i+6BcOVscWfZkZBfoi9hnmzLmNlJXfnECN+w4X8zTMru8m7Vg8DCXndtdyoElCUYLNOOdQuTI/kDy72wdYBvdp2DxAFMz4mjDs1iAR99fjOh+Ho5oGL4mB9dOj/zZaE
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: b277b782-5872-4758-2efc-08d52a4183eb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(22001)(4534020)(4602075)(4603075)(4627115)(201702281549075)(2017052603199);
SRVR:MWHPR08MB2429;
x-ms-traffictypediagnostic: MWHPR08MB2429:
x-microsoft-antispam-prvs: <MWHPR08MB2429D99FC17F046B48A484BBDA2B0@MWHPR08MB2429.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(10201501046)(3231022)(3002001)(93006095)(93001095)(100000703101)(100105400095)(6041248)(2016111802025)(20161123560025)(20161123564025)(20161123562025)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6043046)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095);
SRVR:MWHPR08MB2429; BCL:0; PCL:0;
RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);
SRVR:MWHPR08MB2429;
x-forefront-prvs: 0490BBA1F0
x-forefront-antispam-report: SFV:NSPM;
SFS:(10019020)(979002)(376002)(346002)(39830400002)(24454002)(199003)(51694002)(189002)(53754006)(6506006)(99286004)(6436002)(105586002)(966005)(106356001)(478600001)(7696004)(77096006)(25786009)(97736004)(189998001)(316002)(19609705001)(50986999)(74482002)(2900100001)(54356999)(76176999)(110136005)(2906002)(5660300001)(6116002)(236005)(8936002)(2950100002)(68736007)(606006)(55016002)(74316002)(53936002)(101416001)(9686003)(102836003)(790700001)(6306002)(54896002)(14454004)(7736002)(3280700002)(3660700001)(53546010)(33656002)(6246003)(229853002)(8676002)(4326008)(81156014)(81166006)(86362001)(969003)(989001)(999001)(1009001)(1019001);
DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR08MB2429;
H:MWHPR08MB2432.namprd08.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;
A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: evequefou.be does not designate
permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary="_000_MWHPR08MB2432297B11CA2EF0619C43DFDA2B0MWHPR08MB2432namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: b277b782-5872-4758-2efc-08d52a4183eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Nov 2017 02:52:01.6012 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR08MB2429
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/Tlx0cy0NOy8y6zB4cfa0MFt8yaM>
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:52:07 -0000
I’ve also pursued this with another providers which used the “sightings” of BSSIDs and cell signals and how they handle updates, when I moved a portable cell spot. The issue turned out to be that it requires: * GPS-enabled clients to report the new location in sufficient volume to cause the service to reconsider the location * The service-side database to be updated * Clients to age out their cache of the previous location of the BSSID/cell. As a result, the expected time for clients to see the new location was 10-15 days, by which point we won’t be here any more. From: 100attendees [mailto:100attendees-bounces@ietf.org] On Behalf Of Jim Martin Sent: Monday, November 13, 2017 10:42 AM To: Darshak Thakore <d.thakore@cablelabs.com> Cc: 100attendees@ietf.org Subject: Re: [100attendees] Incorrect GeoIP for IETF network addresses 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<mailto: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
- [100attendees] Incorrect GeoIP for IETF network a… Darshak Thakore
- 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… Bob Hinden
- 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