A Format for Self-published IP Geolocation Feeds
draft-google-self-published-geofeeds-07

Document Type Active Internet-Draft (individual)
Last updated 2020-01-21 (latest revision 2020-01-02)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf htmlized bibtex
IETF conflict review conflict-review-google-self-published-geofeeds
Stream ISE state In IESG Review
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2020-01-19)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - No Actions Needed
Network Working Group                                           E. Kline
Internet-Draft                                                  Loon LLC
Intended status: Informational                                 K. Duleba
Expires: July 5, 2020                                        Z. Szamonek
                                                                S. Moser
                                                 Google Switzerland GmbH
                                                               W. Kumari
                                                                  Google
                                                         January 2, 2020

            A Format for Self-published IP Geolocation Feeds
                draft-google-self-published-geofeeds-07

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 5, 2020.

Kline, et al.             Expires July 5, 2020                  [Page 1]
Internet-Draft         Self-published IP Geofeeds           January 2020

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Notation . . . . . . . . . . . . . . . . . .   3
     1.3.  Assumptions About Publication . . . . . . . . . . . . . .   4
   2.  Self-Published IP Geolocation Feeds . . . . . . . . . . . . .   4
     2.1.  Specification . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.1.  Geolocation Feed Individual Entry Fields  . . . . . .   5
         2.1.1.1.  IP Prefix . . . . . . . . . . . . . . . . . . . .   5
         2.1.1.2.  Country . . . . . . . . . . . . . . . . . . . . .   5
         2.1.1.3.  Region  . . . . . . . . . . . . . . . . . . . . .   5
         2.1.1.4.  City  . . . . . . . . . . . . . . . . . . . . . .   5
         2.1.1.5.  Postal Code . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  Prefixes With No Geolocation Information  . . . . . .   6
       2.1.3.  Additional Parsing Requirements . . . . . . . . . . .   6
     2.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Consuming Self-Published IP Geolocation Feeds . . . . . . . .   8
     3.1.  Feed Integrity  . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Verification of Authority . . . . . . . . . . . . . . . .   8
     3.3.  Verification of Accuracy  . . . . . . . . . . . . . . . .   8
     3.4.  Refreshing Feed Information . . . . . . . . . . . . . . .   9
   4.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   9
   5.  Relation to Other Work  . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  Planned Future Work . . . . . . . . . . . . . . . . . . . . .  11
   8.  Finding Self-Published IP Geolocation Feeds . . . . . . . . .  11
Show full document text