> 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 >> whois [RFC3912] services, use of the RIR's FTP [RFC0959] services >> SHOULD be the preferred access." Is the RIPE NCC expected to download >> all the geofeed files and make them available through their FTP >> service? > > I don't quite interpret it like that, I rather interpret it as the > RIPE NCC (and other RIRs) publishing a list of all prefixes and their > geofeed URL. > I imagine it like the delegated file, but just prefixes and geofeed URLs. > > But I will say it seems a bit unclear, maybe Randy Bush or one of the > other authors could comment on the intention here. again, see the actual implementation referenced in the internet-draft > For access via WHOIS, I would say no as that would probably be way too > complicated. yep >> The IETF doc 'Finding geofeeds': >> https://datatracker.ietf.org/doc/draft-ietf-opsawg-finding-geofeeds/ randy --- [email protected] `gpg --locate-external-keys --auto-key-locate wkd [email protected]` signatures are back, thanks to dmarc header butchery
