Good call, thanks. That appears to be via the assigned resources bit ("IP Addresses" heading in Arin Online). Will give that a shot, thanks!
-- Hugo Slabbert On Tue, Aug 30, 2022 at 1:38 PM Job Snijders <j...@fastly.com> wrote: > On Tue, Aug 30, 2022 at 01:28:18PM -0700, Hugo Slabbert wrote: > > @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. > > Hmmm, there might be an obstacle due to lack of inetnum support in ARIN: > https://www.arin.net/participate/community/acsp/suggestions/2021/2021-27/ > > However there is good news: the last paragraph of RFC 9092 section 3 > suggests a workaround specific to ARIN: > > "Currently, the registry data published by ARIN are not the same > RPSL as that of the other registries (see [RFC7485] for a survey > of the WHOIS Tower of Babel); therefore, when fetching from ARIN > via FTP [RFC0959], WHOIS [RFC3912], the Registration Data Access > Protocol (RDAP) [RFC9082], etc., the "NetRange" attribute/key > MUST be treated as "inetnum", and the "Comment" attribute MUST > be treated as "remarks". > > Perhaps you insert a "Comment: Geofeed https://xxx/geofeed.csv" in the > place where NetRange blobs come from? > > Kind regards, > > Job >