Dear Hugo, On Tue, Aug 30, 2022 at 12:34:41PM -0700, Hugo Slabbert wrote:
Google folks:
I see historical reference to needing to use the Google Peering Portal ( http://peering.google.com) if you need to provide Google with geofeed info for GeoIP info on network blocks, ref https://mailman.nanog.org/pipermail/nanog/2015-May/075229.html.
Is that still the case? Are there any avenues to provide Google with geofeed info if you're *not* currently peering with 15169? Or to get access to just the geofeed update portion of the Peering Portal?
(I don't work for Google), but ... There is a RFC detailing how to find Geofeed data (and make Geofeed data findable): https://datatracker.ietf.org/doc/html/rfc9092 The idea is that in inetnum/inet6num objects (which are maintained by the IP prefix holder), the holder can point to the location where Geofeed data can be found. There are a few methods: 1) Use the 'geofeed:' RPSL attribute (the RIPE Whois server supports this), example: $ whois -h whois.ripe.net 146.75.0.0/16 | grep geofeed geofeed: https://ip-geolocation.fastly.com/ 2) A slightly uglier hack: stick a reference to the Geofeed location in a RPSL remark (should work in databases which don't (yet) support the 'geofeed:' attribute), example: $ whois -h whois.ripe.net 2001:67c:208c::/48 | grep Geofeed remarks: Geofeed https://sobornost.net/geofeed.csv Kind regards, Job