RFC 8805: A Format for Self-Published IP Geolocation Feeds
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8805
- Published
- August 2020
- Authors
- E. Kline; K. Duleba; Z. Szamonek; S. Moser; W. Kumari
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9632Finding and Using Geofeed DataCurrent
August 2024
- RFC 9179A YANG Grouping for Geographic LocationsCurrent
February 2022
- RFC 7871Client Subnet in DNS QueriesCurrent
May 2016
- RFC 7199Location Configuration Extensions for Policy ManagementCurrent
April 2014
- RFC 6644Rebind Capability in DHCPv6 Reconfigure MessagesCurrent
July 2012
- RFC 6280An Architecture for Location and Location Privacy in Internet ApplicationsCurrent
July 2011
- RFC 3831Transmission of IPv6 Packets over Fibre ChannelObsoleted
July 2004
- RFC 3315Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
July 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?