[OPSAWG] Finding and Using Geofeed Data

Massimo Candela <massimo@us.ntt.net> Mon, 31 August 2020 20:45 UTC

Return-Path: <massimo@us.ntt.net>
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 626EC3A0486 for <opsawg@ietfa.amsl.com>; Mon, 31 Aug 2020 13:45:28 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 CooD-Hy6_EHR for <opsawg@ietfa.amsl.com>; Mon, 31 Aug 2020 13:45:27 -0700 (PDT)
Received: from mail4.dllstx09.us.to.gin.ntt.net (mail4.dllstx09.us.to.gin.ntt.net [128.241.192.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 172DC3A046E for <opsawg@ietf.org>; Mon, 31 Aug 2020 13:45:26 -0700 (PDT)
Received: from [192.168.1.63] (host-79-43-213-233.retail.telecomitalia.it [79.43.213.233]) by mail4.dllstx09.us.to.gin.ntt.net (Postfix) with ESMTPSA id AA5F4EE0138 for <opsawg@ietf.org>; Mon, 31 Aug 2020 20:45:25 +0000 (UTC)
To: opsawg@ietf.org
From: Massimo Candela <massimo@us.ntt.net>
Message-ID: <8450cc78-8c60-ff7a-19f5-ea7335d262cd@us.ntt.net>
Date: Mon, 31 Aug 2020 22:45:24 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/cbwW1YqibIV5EoGxDG0ggqlFVt4>
Subject: [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, 31 Aug 2020 20:51:54 -0000

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