Dear colleagues,
Last week, on Wednesday 4 May 2022, 14:00 UTC, we held a RIPE NCC Open House on the topic of RPKI Data.
Thank you to all who participated, I thought it was a useful session and I enjoyed the discussion and feedback we received.
During the session I promised to send an e-mail to this list with a summary of all data and visualisations we currently have public for RPKI:
Visualisations:
-Generated from "delegated stats” in combination with BGP data from RIS
-No IPv6
Data:
-Daily data per Trust Anchor per 2011
Public tools:
-User interface for Relying Party software
-Shows the RPKI validity state for a combination of prefix and Autonomous System.
-API call returns a timeseries with the count of VRPs (Validated ROA Payload) for the requested resource.
My key take aways from the session:
-Ruediger Volk asked for an inventory of our current data, visualisations and tools. I started by this e-mail to the Working Group and I’m still considering how to make them easier to find on our website.
-Randy Bush noted that experiments will/might pollute our data. Ties suggested to add known experiments to the GitHub dataset description.
-Mingwei Zhang mentioned that he is currently working with Emile Aben and Agustin Formoso on “when did a VRP appear/disappear” feature for RIPEstat. This will be a very valuable addition for trouble shooting.
-John Kristoff would like to see statistics on the time it takes from the moment someone hits “submit” in the LIR portal for a ROA, to the moment the VRP is visible in the repository and when it is seen picked up by routers.
-Amreesh Phokeer suggested a more granular data set for Trust Anchor data. This is currently a daily dump. We are interested to hear how granular would be useful. Also Amreesh would be interested in statistics about revoked ROAs.
-Sacha mentioned that it would be useful to have a tool that would show how a ROA would impact a route, without actually creating that ROA, or for a prefix that you don’t have holdership of.
We’re looking into all your suggestions and where possible implement them. Stay tuned :)
If I missed something, or if you want to share your thoughts, have suggestions, please send an e-mail to the list or directly to us on
rpki@ripe.net
Kind regards,
Nathalie Trenaman
Routing Security Programme Manager
RIPE NCC