From an email list 2022/04/21:
Geofeed is specified in RFC 8805. Finding and using Geofeed data is described in RFC 9092.
Example in the wild:
$ whois -h whois.ripe.net 146.75.0.0 | fgrep geofeed: geofeed: https://ip-geolocation.fastly.com/
Another example below, in this instance the geofeed information is stored in a 'remarks:' attribute. Unfortunately this particular RIR does not (yet?) properly support the native RPSL geofeed attribute for IPv6 /48 PI blocks.
$ whois -h whois.ripe.net 2001:67c:208c::/48 | grep geofeed remarks: Geofeed https://sobornost.net/geofeed.csv
Both approaches work.
----
Besides geofeed, there are also geoidx records in IRRs but whether geolocation services actually use geofeed or geoidx remains to be seen. You can see some geoidx: at this IRR entry in TC: bgp.net example
----
A helpful resource: Geo & VPN Services - the RFC only works if they're pulling your feed and they'd only know that if you contact them in the first place.
----
- RFC 3693: Geopriv Requirements
- RFC 5870: A Uniform Resource Identifier for Geographic Locations
- RFC 6288: URN Namespace for the Defence Geospatial Information Working Group (DGIWG)
- RFC 6397: Multi-Threaded Routing Toolkit (MRT) BGP Routing Information Export Format with Geo-Location Extensions
- RFC 6772: Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
- RFC 7942: The GeoJSON Format
- RFC 8142: GeoJSON Text Sequences
- RFC 8805: A Format for Self-Published IP Geolocation Feeds
- RFC 9092: Finding and Using Geofeed Data