Action 1: Filtering of Route Announcements
The route servers perform RPKI validation and it is recommended (but not required) that members sign their routes. Routes that fail RPKI validation are dropped; valid and unknown routes are accepted.Additionally, routes are filtered based on the IRR object provided during onboarding. Routes that are not a part of the member’s AS-SET will be dropped.
Action 2-1: Offer assistance to its members to maintain accurate routing information in an appropriate repository (IRR and/or RPKI)
Community IX regularly audits our members filtered prefixes and reaches out to the appropriate parties within the member orgs to update and resolve any outstanding prefix announcements that are being rejected on policy.
Action 2-3: Indicate MANRS participation on the member list and the website
Community IX utilizes IXP Manager which displays members MANRS participation status to other members automatically.
Action 3: Protect the peering platform
Action 4: Facilitate global operational communication and coordination between network operators
We maintain a separate mailing list for each of our IXes that notices are posted to by Community IX and members may also communicate among themselves.Membership directories are available within our IXP Manager based portal.
Action 5: Provide monitoring and debugging tools to the members
Yes, we provide a Looking Glass to both authenticated and non-authenticated users of our portals:FL-IX: https://my.fl-ix.net/lg