...

We've been getting a lot of requests to make processed RPKI data easily available in existing (RPSL based) workflows. This is why we added the ability to export all ROAs as route: objects in the latest release, version 2.19. Practically, this means that running an RPSL export will give you almost 450,000 highly reliable, cryptographically validated route: objects. Interesting! I was considering writing a script to do this, but the NCC beat me to it! :-)

drl wrote the script and has made the data available for years

Wouldn't it make sense to align the "created:" date with something more specific to the ROA rather then the export date?

yes

Another consideration might be to create a "expiry-date:" derived from the ROA's expiry date for easy debugging purposes.

use a remark: randy