Action 1: Filtering of Route Announcements
Any routes that members announce will be validated by RPKI (RFC6811, RFC7115) and checked against Internet Routing Registry (IRR) data.If the result is RPKI Invalid, the route is rejected.
If the result is RPKI NotFound/Unknown, we check if the route is resolvable for its origin ASN (this will be the case if a proper route object exists). Depending on the result, it might be accepted or rejected.
Action 2-1: Offer assistance to its members to maintain accurate routing information in an appropriate repository (IRR and/or RPKI)
We help participants when they join. Also, if a high number of filtered prefixes
appear over time, the 1-IX team will contact our member and advise on how to solve the problem.
Action 2-2: Offer assistance in implementing MANRS ISP Actions for the members
We can provide consultations to our members to create route-objects and ROAs.
Action 2-3: Indicate MANRS participation on the member list and the website
https://1-ix.net/participants/
Action 3: Protect the peering platform
https://1-ix.net/peering-policy/
Action 5: Provide monitoring and debugging tools to the members
https://lg.1-ix.net/