Re: [100attendees] Incorrect GeoIP for IETF network addresses
Alexandre PETRESCU <alexandre.petrescu@cea.fr> Mon, 13 November 2017 04:02 UTC
Return-Path: <alexandre.petrescu@cea.fr>
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 E7002128B8F
for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 20:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 mzw-IPrOlMZ4 for <100attendees@ietfa.amsl.com>;
Sun, 12 Nov 2017 20:02:19 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr
[132.168.224.13])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id DCD82126DCA
for <100attendees@ietf.org>; Sun, 12 Nov 2017 20:02:18 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21])
by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP
id vAD42Gh7003044
for <100attendees@ietf.org>; Mon, 13 Nov 2017 05:02:16 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1])
by localhost (Postfix) with SMTP id A8F18201103
for <100attendees@ietf.org>; Mon, 13 Nov 2017 05:02:16 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7])
by pisaure.intra.cea.fr (Postfix) with ESMTP id 9E8A0200C96
for <100attendees@ietf.org>; Mon, 13 Nov 2017 05:02:16 +0100 (CET)
Received: from [132.166.84.2] ([132.166.84.2])
by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id
vAD42FLL023274
for <100attendees@ietf.org>; Mon, 13 Nov 2017 05:02:15 +0100
To: 100attendees@ietf.org
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
<52A5E595-D18B-456E-8242-C2B7A4CC2AB7@daedelus.com>
<MWHPR08MB2432297B11CA2EF0619C43DFDA2B0@MWHPR08MB2432.namprd08.prod.outlook.com>
<e19ac57c-5b23-606c-1ac7-62a50f829b4f@krsek.cz>
<b64a2b74-edf9-4d3a-6593-0a1810752e45@cea.fr>
<0304086f-812b-5396-cb30-94f092ad6668@krsek.cz>
From: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
Organization: CEA
Message-ID: <6dbde6d0-c3c7-a9dd-42e1-136aef5a6187@cea.fr>
Date: Mon, 13 Nov 2017 05:02:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <0304086f-812b-5396-cb30-94f092ad6668@krsek.cz>
Content-Type: multipart/signed; protocol="application/pkcs7-signature";
micalg=sha-256; boundary="------------ms050401090708050306030302"
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/JY6p1_U9g_2K3WOTYc9A8Pg1doo>
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 04:02:21 -0000
Le 13/11/2017 à 04:34, Michal Krsek a écrit : > > Hi Alex, > > >> For BSSID: the MAC-to-coordinates mappings dont deserve much >> consideration IMHO, as it's not IP. > > Sorry for my shortcut: > > BSSID is not on IP level, BSSID - Basic Service Set ID, is a 48bit value, very much similar to MAC addresses. On an AP you have a 48bit BSSID, a 48bit MAC on the WiFi interface and a 48bit MAC on its Ethernet interface. The 3 are distinct. One would need to map the three to coordinates. Some map just the BSSID, or just the Network Name, often known as ESSID which is yet another value. Sometime the Network Name is hidden, you want it hidden, cant reveal. All these things are not IP. > on the other hand, APs are being (most likely) connected to the IP > network. And the IP network operator may signal to the devices that > this is a "mobile" network. Not proposing any particular protocol here > for now. > >> Wireshark setting 'GeoIP' fields is something non-standardised that >> should not be trusted. IT may say "Alaska" but it should not be >> taken seriously. > > There are other non-standard ways, how to handle it (like call to your > friend that works for MaxMind). 'Out-of-band' means :-) Alex
- [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