[100attendees] Incorrect GeoIP for IETF network addresses
Darshak Thakore <d.thakore@cablelabs.com> Mon, 13 November 2017 02:34 UTC
Return-Path: <d.thakore@cablelabs.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 1F69512778D
for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 18:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 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_NONE=-0.0001,
RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=cablelabs.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 2DACvqAeS6Hc for <100attendees@ietfa.amsl.com>;
Sun, 12 Nov 2017 18:34:51 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com
(mail-by2nam03on0115.outbound.protection.outlook.com [104.47.42.115])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 294B0127077
for <100attendees@ietf.org>; Sun, 12 Nov 2017 18:34:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com;
s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
bh=YQQX3oaUa/oIez95E2uXmxjE73yy1O5TxSbenMbv08Y=;
b=C/ya81Dbg6aGwIcs7JCbafBwCsgyXBp+K6fsRXof3jjD7gVkYsoPlOp7pPyKQBYkV2rryJ4BxUSffTo6nliM8MUYzbeRceOJTkDo72j6eRKhRGatvG4w5xVlHBmBOgUm5KAEL2XBXziyH49aFJRvPOks7EGQm85KSu6VH78f8Ss=
Received: from CY4PR06MB3431.namprd06.prod.outlook.com (10.171.247.35) by
CY4PR06MB3432.namprd06.prod.outlook.com (10.171.247.36) 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:34:45 +0000
Received: from CY4PR06MB3431.namprd06.prod.outlook.com ([10.171.247.35]) by
CY4PR06MB3431.namprd06.prod.outlook.com ([10.171.247.35]) with mapi id
15.20.0218.015; Mon, 13 Nov 2017 02:34:45 +0000
From: Darshak Thakore <d.thakore@cablelabs.com>
To: "100attendees@ietf.org" <100attendees@ietf.org>
Thread-Topic: Incorrect GeoIP for IETF network addresses
Thread-Index: AQHTXCf3mWiGz+tsl02HkYfeWvY9hA==
Date: Mon, 13 Nov 2017 02:34:45 +0000
Message-ID: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.171010
authentication-results: spf=none (sender IP is )
smtp.mailfrom=d.thakore@cablelabs.com;
x-originating-ip: [2001:67c:370:1998:909a:e602:adbf:a9ef]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR06MB3432;
6:opioT6QSAOf24sbLMbwfLIR2oeq6dfM0Q2Ih7FPN2zr9GmLaXCp5I9CmGi+5Z75KK1GFLkRoFLI8lPQwHTyz02tBN1a7aucj61jhd4BtyHDl2FCTlX7obmHZZcxYbLXvRzbfyqy0V8PqCGiEeIdrTWNw7T6xMnStELisH0Z+uy0oS+hkjqHv4I2IebRuUBbuYxd03HsPz7ZRV8igRb4bND+pF5eRfRYoTj8lVcsphtsu1VRs22C4RYl2LPD25p+SYWqrdAV5LzbHj3wcxmVGfcUIBXSt5nUUqF7NyH82IPEbB6pmTbJGcyUv7rVLMz1IjOWl+kk6Za308+km8GGZI7NRxcEfmrRPDfl3vISwfu4=;
5:kw0b1JKFYFyLOJA/zzSWkBHPJQqGHXWo+bY+siZuO4kqYlxTB0L93Mrh5xLmjaFmi9decycZrcISfOloRQpNpKhi1FPQUdKwo0dxr13eXcIArgzd+CJGO0b7ekBdrfY95BKhVtQmXQBY+VkdhFPYhRfR695O1f4Y97cv1PuLMgE=;
24:lgxOVX0eWs+B0+6FLpLrcMG2PTo+fdOoWiLaRFD1YkCFcCStaaM74mD6UlnYwiwNC8p3X5OqvkQFPB4A3VLVlYRCMe+A52PujslpBtGWVpo=;
7:/wf8W3d2badbeUZijCAq7SbMIwNTNPAnp6NxbiyMf9lqcVye6Pgu6uKQV30UUI9blmm+V69LU1PVKmyYT9EENjSrud5/ohBDSOvXs1TDWlRMtIM4U0D1qZDy898HwqVSZTvSDsic+TPasQ2khLxM+UqBbLoXWfGXCF628IMCGSOezSnpkxRirv9+Vsl/ZPo/EsdzCdqsPLG93IR+RcHCTdp0Rpkj4csgGraGbLZvkQmpVw1Syor1NVwszSuXShCz
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: b06efe9a-5d73-4b72-0033-08d52a3f1a31
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603258);
SRVR:CY4PR06MB3432;
x-ms-traffictypediagnostic: CY4PR06MB3432:
x-microsoft-antispam-prvs: <CY4PR06MB343217C3E69E82C1F37A67D2E42B0@CY4PR06MB3432.namprd06.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)(8121501046)(5005006)(3231022)(3002001)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(6041248)(20161123558100)(20161123560025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095);
SRVR:CY4PR06MB3432; BCL:0; PCL:0;
RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);
SRVR:CY4PR06MB3432;
x-forefront-prvs: 0490BBA1F0
x-forefront-antispam-report: SFV:NSPM;
SFS:(10019020)(6009001)(376002)(39830400002)(346002)(51694002)(199003)(189002)(53754006)(7736002)(33656002)(2906002)(105586002)(58126008)(106356001)(82746002)(83716003)(2501003)(5660300001)(25786009)(54896002)(6306002)(6916009)(3660700001)(6512007)(3280700002)(6486002)(36756003)(81166006)(8936002)(81156014)(77096006)(5640700003)(102836003)(101416001)(97736004)(54356999)(50986999)(189998001)(6116002)(14454004)(8676002)(6506006)(83506002)(478600001)(316002)(2351001)(99286004)(68736007)(6436002)(86362001)(53936002)(2900100001);
DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR06MB3432;
H:CY4PR06MB3431.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;
A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: cablelabs.com does not designate
permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary="_000_180DB1B198A645058B3080959DCBC1F2cablelabscom_"
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b06efe9a-5d73-4b72-0033-08d52a3f1a31
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Nov 2017 02:34:45.0766 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR06MB3432
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/AETtYv5U9AiUZjXVjElqg7OTibA>
Subject: [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:34:53 -0000
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] 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