RFC 8805 on A Format for Self-Published IP Geolocation Feeds
rfc-editor@rfc-editor.org Thu, 06 August 2020 23:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80EA13A07F7 for <ietf-announce@ietfa.amsl.com>; Thu, 6 Aug 2020 16:36:23 -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, 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 MjfgE6nlwnuE for <ietf-announce@ietfa.amsl.com>; Thu, 6 Aug 2020 16:36:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C8E3A07ED for <ietf-announce@ietf.org>; Thu, 6 Aug 2020 16:36:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5FAE6F40762; Thu, 6 Aug 2020 16:36:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8805 on A Format for Self-Published IP Geolocation Feeds
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200806233613.5FAE6F40762@rfc-editor.org>
Date: Thu, 06 Aug 2020 16:36:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/VzSTyT5igULjqjaUWQByYV4hpYQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2020 23:36:23 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8805 Title: A Format for Self-Published IP Geolocation Feeds Author: E. Kline, K. Duleba, Z. Szamonek, S. Moser, W. Kumari Status: Informational Stream: Independent Date: August 2020 Mailbox: ek@loon.com, kduleba@google.com, zszami@google.com, smoser@google.com, warren@kumari.net Pages: 23 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-google-self-published-geofeeds-09.txt URL: https://www.rfc-editor.org/info/rfc8805 DOI: 10.17487/RFC8805 This document records a format whereby a network operator can publish a mapping of IP address prefixes to simplified geolocation information, colloquially termed a "geolocation feed". Interested parties can poll and parse these feeds to update or merge with other geolocation data sources and procedures. This format intentionally only allows specifying coarse-level location. Some technical organizations operating networks that move from one conference location to the next have already experimentally published small geolocation feeds. This document describes a currently deployed format. At least one consumer (Google) has incorporated these feeds into a geolocation data pipeline, and a significant number of ISPs are using it to inform them where their prefixes should be geolocated. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC