Self-published IP Geolocation Data
draft-google-self-published-geofeeds-02

Document Type Active Internet-Draft (individual)
Last updated 2013-07-28
Stream ISE
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream ISE state Response to Review Needed
Revised I-D Needed
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
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: Informational                                 K. Duleba
Expires: January 30, 2014                                    Z. Szamonek
                                                 Google Switzerland GmbH
                                                           July 29, 2013

                   Self-published IP Geolocation Data
                draft-google-self-published-geofeeds-02

Abstract

   This document records a format whereby a network operator can publish
   a mapping of IP address ranges 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.

   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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.  This document may not be modified,
   and derivative works of it may not be created, except to format it
   for publication as an RFC or to translate it into languages other
   than English.

   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 January 30, 2014.

Copyright Notice

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

Kline, et al.           Expires January 30, 2014                [Page 1]
Internet-Draft     Self-published IP Geolocation Data          July 2013

   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.  Implications of publication  . . . . . . . . . . . . . . .  3
   2.  Self-published IP geolocation feeds  . . . . . . . . . . . . .  4
     2.1.  Specification  . . . . . . . . . . . . . . . . . . . . . .  4
       2.1.1.  Geolocation feed individual entry fields . . . . . . .  5
       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
       2.3.1.  Delegation size  . . . . . . . . . . . . . . . . . . .  8
       2.3.2.  Alternate format . . . . . . . . . . . . . . . . . . .  8
   3.  Finding self-published IP geolocation feeds  . . . . . . . . .  8
     3.1.  Ad hoc 'well known' URIs . . . . . . . . . . . . . . . . .  9
     3.2.  Using public databases of network authority  . . . . . . .  9
     3.3.  Using 'reverse' DNS with NAPTR records . . . . . . . . . .  9
   4.  Consuming self-published IP geolocation feeds  . . . . . . . . 11
     4.1.  Feed integrity . . . . . . . . . . . . . . . . . . . . . . 11
     4.2.  Verification of authority  . . . . . . . . . . . . . . . . 11
     4.3.  Verification of accuracy . . . . . . . . . . . . . . . . . 11
     4.4.  Refreshing feed information  . . . . . . . . . . . . . . . 11
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   6.  Privacy Considerations . . . . . . . . . . . . . . . . . . . . 12
   7.  Relation to other work . . . . . . . . . . . . . . . . . . . . 13
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
Show full document text