Hi all, On 06/04/2021 19:23, Randy Bush wrote:
I have CCed Randy Bush as I thought he might be able to clarify what was meant by the following:
To minimize the load on RIR whois [RFC3912] services, use of the RIR's FTP [RFC0959] services SHOULD be the preferred access. This also provides bulk access instead of fetching with a tweezers.
I think one of the most important things in general here is seeing what is within the scope of the db-wg to decide and what should probably be defined by the IETF spec. And also to try to get some kind of implementation out as quickly as possible while still doing it properly. Because as you mention, the remarks format appears to be used quite a bit and I imagine it probably grows in use at a decent rate. (I have no data to back this up though, it is just a guess)
massimo is more aware of the details of current deployment and how that affects the rirs. i suspect the load of the remarks: versions would be the same as that of geofeed:. the suggestion to use bulk fetch as opposed to object-by-object seems simple and the benefits should be pretty obvious i would think. see msssimo's existing tooling (cited in the internet-draft) for implementation.>> -The IETF doc 'Finding geofeeds' says "To minimize the load on RIR
At the moment there are 1350 prefixes with geofeeds coming from remarks/comments, mostly RIPE and ARIN. This number more than doubled in the last ~4 months. If a service is interested in importing all the geofeeds, the generic daily whois dumps produced by the rirs are perfect---including the public anonymized ones, since we just need the remarks. The implementation [1] uses such dumps. To the best of my knowledge, the geo providers supporting our draft are also using such dumps (apparently some were already familiar with them). Ciao, Massimo [1] https://github.com/massimocandela/geofeed-finder