Action 1: Filtering of Route Announcements
Stuttgart-IX filters routes based on RPKI Data and falls back to IRRDB if RPKI is unknown.
The policy is published here: https://www.stuttgart-ix.de/en/routeserver.html
It's basically the "standard" IXP Manager Route Server with RPKI and strict IRRDB filtering.
Action 2-1: Offer assistance to its members to maintain accurate routing information in an appropriate repository (IRR and/or RPKI)
The Stuttgart-IX Looking Glass (https://lg.s-ix.de) highlights rejected routes with the reject reason.
The Stuttgart-IX team reaches out to new members if their announcements are rejected.
Action 2-2: Offer assistance in implementing MANRS ISP Actions for the members
The Stuttgart-IX team reaches out to new members if their announcements are rejected by the route servers.
Stuttgart-IX hosts Workshops to inform their members of IXP best pracitces.
Action 2-3: Indicate MANRS participation on the member list and the website
Compliant members are highlighted in the members list: https://portal.s-ix.de/customer/details
Action 3: Protect the peering platform
Action 4: Facilitate global operational communication and coordination between network operators
Members are required to update their information in our IXP Manager. We've just relaunched with a new IXP Manager and are actively pushing members to update their NOC contacts.
Action 5: Provide monitoring and debugging tools to the members