Open molangning opened 6 months ago
With browsers dropping support for the ftp://
protocol altogether perhaps this field should just be named url:
. For the database and serial should we match the irrdv4 configuration field names of import_source:
and import_serial_source:
?
It should be, but are those values available to the public? I am not familiar with the irrd protocol so please be patient.
Thanks, @molangning! As @merit-schelcj mentioned above, we will attempt to rewrite the fields to align with the irrd route object source format. I think that's the best way to go in terms of consistency and standardization.
Also, rdap connection info is another good thing to have, alongside scripts that regularly checks if the databases are still up and accessible. I have the checker scripts that can update the data accordingly here https://github.com/molangning/irr-tracker
@molangning #36 is approved and ready to be merged. For the tracker you proposed, please go ahead and open a separate issue to outline what you think the requirements for this might be and how we could integrate it into the static site. Feel free to also open a pull request for this as well.
Sure, I will open one soon, thanks a lot!
There are some inconsistency in
ftp_site
fromregistry-list.json
whereftp_site
field (LACNIC)I propose a new format where each registries have both database and serial number files defined inside ftp_site with their uri schemes specified. Similarly, the database and serial number file path can be split into different fields. Additionally, a new field
http_sites
can be added to accommodate for the http sites.