GARR

Implementation of MANRS Actions

• Action 1: Prevent propagation of incorrect routing information We implement strict outbound routing policies for our prefixes (prefix-list exact), and we register route objects for all of them. We implement strict inbound routing policies from our customers ASes (prefix-list exact), and we require route objects to be registered and created.
• Action 3: Facilitate global operational communication and coordination All our contact points are maintained up to date on PeeringDB (http://as137.peeringdb.com/). All our RIPE objects have up to date contact and abuse informations.
• Action 4: Facilitate validation of routing information on a global scale We have created the as-set AS-GARR where we maintain the list of our customer ASes. This as-set is notified to all our upstreams and peers to be used for creating prefix filters. We have created ROAs for most of our prefixes (a few of them have some issues and need some additional work).