<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.google-self-published-geofeeds" target="https://datatracker.ietf.org/doc/html/draft-google-self-published-geofeeds-09">
   <front>
      <title>A Format for Self-Published IP Geolocation Feeds</title>
      <author initials="E." surname="Kline" fullname="Erik Kline">
         <organization>Loon LLC</organization>
      </author>
      <author initials="K." surname="Duleba" fullname="Krzysztof Duleba">
         <organization>Google Switzerland GmbH</organization>
      </author>
      <author initials="Z." surname="Szamonek" fullname="Zoltan Szamonek">
         <organization>Google Switzerland GmbH</organization>
      </author>
      <author initials="S." surname="Moser" fullname="Stefan Moser">
         <organization>Google Switzerland GmbH</organization>
      </author>
      <author initials="W." surname="Kumari" fullname="Warren Kumari">
         <organization>Google</organization>
      </author>
      <date month="February" day="7" year="2020" />
      <abstract>
	 <t>This document records a format whereby a network operator can publish a mapping of IP address prefixes to simplified geolocation information, colloquially termed a &quot;geolocation feed&quot;. 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-google-self-published-geofeeds-09" />
   
</reference>
