Re: [OPSAWG] Finding and Using Geofeed Data

Owen DeLong <owen@delong.com> Mon, 28 September 2020 05:49 UTC

Return-Path: <owen@delong.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9CBC3A0E59 for <opsawg@ietfa.amsl.com>; Sun, 27 Sep 2020 22:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, 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=delong.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 HB2JwqiQ4Apa for <opsawg@ietfa.amsl.com>; Sun, 27 Sep 2020 22:49:49 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 487513A0E58 for <opsawg@ietf.org>; Sun, 27 Sep 2020 22:49:48 -0700 (PDT)
Received: from [IPv6:2001:470:496b:0:250b:5d55:7927:84db] ([IPv6:2001:470:496b:0:250b:5d55:7927:84db]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id 08S5njvt1569386 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 27 Sep 2020 22:49:46 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com 08S5njvt1569386
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1601272186; bh=N+IkJ31ATDsnntvxcZaVPZB471R5RmiYY4ecNdpjkfs=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=lROgFKuaRFgKkx0rc+C7OIUNjpiIaMC4u67f5ZxetivW4PhhTSRwr4ERuDdDn5GDo 1Igg2QnD+g8LOj8aLYSaMHGNB9/hdX0hwM7Ks4/H1XtwRU0PGpO4QiuD8QmYPORZk6 zFkALd+AIll7jsMfHfP2gl21tTvQFHMwd337UJY8=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <8450cc78-8c60-ff7a-19f5-ea7335d262cd@us.ntt.net>
Date: Sun, 27 Sep 2020 22:49:44 -0700
Cc: opsawg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <72DA66D6-4C89-4B2E-954B-00BE4B71AE3F@delong.com>
References: <8450cc78-8c60-ff7a-19f5-ea7335d262cd@us.ntt.net>
To: Massimo Candela <massimo@us.ntt.net>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Sun, 27 Sep 2020 22:49:46 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/0J87Mo814I29OA5DZN4ueM3T-e4>
Subject: Re: [OPSAWG] Finding and Using Geofeed Data
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2020 05:49:53 -0000

I personally think it might be reasonable to add a standard for extended communities in BGP to represent prefix geo-data, but in general, I think it is preferable to discourage the idea that IP and physical addresses have any rational correlation whatsoever, since they really don’t and many of the instances I’ve encountered have wrong assumptions and sloppy thinking applied to create poor user experiences and those are the good ones.

Owen


> On Aug 31, 2020, at 1:45 PM, Massimo Candela <massimo@us.ntt.net> wrote:
> 
> Hi all,
> 
> IP geolocation is often essential but hard to correct when wrong, mostly
> due to the lack of a unified way to provide geolocation data.
> Internet operators may wish to publish the location of some
> of their IP addresses. RFC 8805 (geofeeds) allows network operators
> to publish "a mapping of IP address prefixes to simplified geolocation".
> Unfortunately it doesn't provide any mechanism to actually *find* the
> geofeed files.
> 
> Section 8  ("Finding Self-Published IP Geolocation Feeds") lists this
> as an open problem, and that:
>   Ad hoc mechanisms, while useful for early experimentation by
>   producers and consumers, are unlikely to be adequate for long-term,
>   widespread use by multiple parties.  Future versions of any such
>   self-published geolocation feed mechanism SHOULD address scalability
>   concerns by defining a means for automated discovery and verification
>   of operational authority of advertised prefixes.
> 
> This document provides a (simple) solution to this issue by describing
> a way to include a URL to a geofeed file in an inetnum object, and
> how to prudently consume such geolocation data.
> 
> Draft: https://tools.ietf.org/html/draft-ymbk-opsawg-finding-geofeeds-00
> 
> Please, provide your feedback.
> 
> Have a great day!
> 
> Ciao,
> Massimo
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg