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

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to rfc-ise@rfc-editor.org
Network Working Group                                           E. Kline
Internet-Draft                                              Google Japan
Intended status: Experimental                                  K. Duleba
Expires: September 11, 2019                                  Z. Szamonek
                                                 Google Switzerland GmbH
                                                          March 10, 2019

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

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.  At least one consumer (Google) has
   incorporated these ad hoc feeds into a geolocation data pipeline, and
   is using it to allow ISPs to inform them where the prefixes live.

   [RFC Ed - Please remove publication: The IETF Meeting network
   currently publishes a feed in this format at:
   https://noc.ietf.org/geo/google.csv -- this has significantly cut
   down on the number of "Gah!  Why does the network believe I'm in
   Montreal, that was last meeting!  How am I supposed to find a pub?!"
   complaints.  A number of other meeting networks, including RIPE and
   ICANN publish this information as well, see below. ]

   [ Ed note: Text inside square brackets ([]) is additional background
   information, answers to frequently asked questions, general musings,
   etc.  They will be removed before publication.]

   [ This document is being collaborated on in Github at:
   https://github.com/google/self-published-geo . The most recent
   version of the document, open issues, etc should all be available
   here.  The authors (gratefully) accept pull requests ]

Status of This Memo

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

Kline, et al.          Expires September 11, 2019               [Page 1]
Internet-Draft         Self-published IP Geofeeds             March 2019

   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 https://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 September 11, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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 . . . . . . . . . . . . . . . . . .   4
     1.3.  Implications of 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  . . . . . . . . . . . . . . . . . . . . . .   6
         2.1.1.5.  Postal code . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  Prefixes with no geolocation information  . . . . . .   6
       2.1.3.  Additional parsing requirements . . . . . . . . . . .   6
       2.1.4.  Looking up an IP address  . . . . . . . . . . . . . .   7
     2.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  Proposed extensions . . . . . . . . . . . . . . . . . . .   8
Show full document text