Re: wireless geolocation

Warren Kumari <warren@kumari.net> Tue, 06 June 2017 16:48 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A48126DCA for <ietf@ietfa.amsl.com>; Tue, 6 Jun 2017 09:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 Lpy4meVH6eYM for <ietf@ietfa.amsl.com>; Tue, 6 Jun 2017 09:48:45 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (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 A2D23128D69 for <ietf@ietf.org>; Tue, 6 Jun 2017 09:48:45 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id q15so11733681uaa.2 for <ietf@ietf.org>; Tue, 06 Jun 2017 09:48:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4qEWrqnpIEHxF1uZAedL5mRxRzm9fgwXsewc8SpvzjE=; b=XkpM031GsjeWiweOed9oMgsNUAez6vD/YnpkX2NW0K/0+8zFs/HaID+6KZlXPLlFbn h+RJYQ6RUCkOD6Kdtpjxdqp7p0JF/+0KwTJaiN/NM7Caks5uPNV+8Gp0UlyfySdhlZba TM2sFqL9e1vqwWloZxq+JAodxT5UhtZFNRaX8xUFVH6mK+n/iJk2xptsJXPQFslzhTf4 B755/m3HNo6CsuWZZlpx5bO39gPNqS4AZwtVorrg0wk8k6GJNP3kb05lcbPsGbo8eaSP ZoNpLvPXkcf7wqVIf8HpuopE48wj1hp6iFCkqeHRXUssbcdtxZ+WrFzMWVATvtNNeJXW cQlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4qEWrqnpIEHxF1uZAedL5mRxRzm9fgwXsewc8SpvzjE=; b=la8Aiy5eAwUZrklKgdq+eJJnTSfzTVKEst3Y7Wye/atIghMQCLCxLCjABZgGvDfOAK 5VTdknnAJ241uOF3GS9+o3TLWFx8SbS9ATjM9+YXBjyI193b9aT/tF4XGndDir0SKKJV hT+EMVD/uwPzEhovNnD9WVy8eOCTY4Kbk1oQ9OgoNHBDDsuX5EPIWmqT9zjhXti9hTAq 87dkz7bDzcnLZQ3l10+rGDQWCkOAaovDxRAR5cD/dDkm0AdQSt5VLropQYxmSjPAABO/ WxjfouGhiY8GLoAH5Z/bZT8rgtrqfjSAgm3XoqyYBUophGycbB/Fo7BZTaPZCfdwc4/Y e53g==
X-Gm-Message-State: AODbwcBO4JBV6eIZlAuILjshSc65gnwNQYKNPlJfAkNTiBsWw4sOrAlK u5R6JPp6wRvtiTdYv7lNuTVzjpAldF8BFW6RjQ==
X-Received: by 10.159.59.94 with SMTP id j30mr13114861uah.72.1496767724645; Tue, 06 Jun 2017 09:48:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.82.198 with HTTP; Tue, 6 Jun 2017 09:48:04 -0700 (PDT)
In-Reply-To: <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com>
References: <m27f0pqgbc.wl-randy@psg.com> <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 06 Jun 2017 12:48:04 -0400
Message-ID: <CAHw9_iKpKJA4ruNSR=Zq3ocu7ORwHVrNCnF3H0LJqDL5FrPMuA@mail.gmail.com>
Subject: Re: wireless geolocation
To: Ted Lemon <mellon@fugue.com>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iErPr_JyPHjHx5ndjqmeDXSpok0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jun 2017 16:48:47 -0000

On Tue, Jun 6, 2017 at 12:35 PM, Ted Lemon <mellon@fugue.com> wrote:
> Why do we even have a stable IP address range anymore?   It seems like an unnecessary lift.   If we just take what the ISP offers (IPv4 and IPv6) and use that, why is that not good enough?

Because we use a *large* amount of address space - we (currently) give
everyone a public IP address, we have multiple SSIDs / networks, etc.
ISPs would be quite unlikely to be willing to give us a big enough
block, we (often) also have multiple providers, etc. We would also
need to renumber all of our infrastructure, redo DNS, etc.

We currently publish geo-location info in
https://tools.ietf.org/html/draft-google-self-published-geofeeds-02
format -- noc.ietf.org/geo/google.csv. This gets updated (assuming I /
we don't forget :-)) before each meeting, and should be imported by
google in advance of the meeting...

But, much of the issue is location being tied to the MAC address of
the APs, not just the source IP. There are lots of geo providers, and
they all need to be updated, etc.


W

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