Gonna multi-reply on this one:

@Benjamin:

> I was able to get access without peering with 15169 by getting access to the ISP portal (isp.google.com) which does have Geofeed processing for my AS, but I am unsure if you will get access without being an eyeball network.

Thanks; I'll give that bash. I think our org might have tried this previously before my time, but will see where we get to.

@Christopher:

> For what it's worth I attempted to get access by filling out the same portal and was told to go pound sand, so your results may very.

Good to know. :fingers-crossed:

@Job:

Thanks! I was aware of the RIPE whois option, but the relevant resources for us are in ARIN.  I wasn't aware of the RPSL *remark* option for providing that.  We should be able to give that a bash.

Can anyone confirm if Google respects the remark-based option?  Given the authors and some of the wording, I would hope so?

-- 
Hugo Slabbert


On Tue, Aug 30, 2022 at 12:48 PM Job Snijders <job@fastly.com> wrote:
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