Dear colleagues, At RIPE 76 I shared some ideas about how to produce longitudinal measurements related to routing (in)security (https://ripe76.ripe.net/archives/video/147/). The request from the WG was to share a more detailed description of the framework as it shapes up. I attach the description of the framework and the metrics that we (with NLNetLabs as a partner) started to calculate and store. It also contains references to the data sources. The latter are to be extended, we are already working with a few data providers, and if you have ideas about other potential ones - appreciate your suggestions. Below is the summary of the framework: Measurements To measure MANRS readiness for a particular network a set of metrics has been proposed, one for each action. For example, to measure to what degree Filtering (Action 1) is implemented we will measure the number of routing incidents where the network was implicated either as a culprit or an accomplice and their duration. That will produce a number – an indication of the degree of compliance, or a MANRS readiness index (MR-index) for Action 1 for a specified period of time. The measurements are passive, which means that they do not require cooperation for a measured network. That allows us to measure the MR-indices not only for the members of the MANRS initiative, but for all networks in the Internet (at the moment more than 60,000). Metrics Action: Filtering M1 route leak by the AS M2 route misorigination by the AS M1C route leak by a direct customer M2C route hijack by a direct customer M3 bogon prefixes by the AS M4 Bogon ASNs by the AS Action: Anti-spoofing M5 IP Spoofing by the AS M5C IP Spoofing by a direct customer Action: Coordination M8 contact registration (RIR, IRR, PeeringDB) Action: Facilitate global Validation M7IRR Not registered routes M7RPKI Not registered ROAs M7RPKIN Incorrect ROAs Appreciate your feedback and suggestions. Regards, Andrei