Warian

Implementation of MANRS Actions

• Action 1: Prevent propagation of incorrect routing information Validation of customer announcements are done through statically and explicitly configured ingress filters. Ownership of the various resources are validated through various sources before the filter is created and the BGP peering established.
• Action 2: Prevent traffic with spoofed source IP addresses We have implemented CAIDA Spoofer Software on resilient servers in different countries and we have also applied strict uRPF filters on all of our network ingress and egress points.
• Action 3: Facilitate global operational communication and coordination We maintain a PeeringDB record with up-to-date information for abuse, peering and NOC related requests. We maintain a RIPE IRR entry with up-to-date information for our AS and Organisation. We also have contact information on our website.
• Action 4: Facilitate validation of routing information on a global scale We have published our routing policy, ASNs and prefixes in the RIPE IRRDB: * http://www.db.ripe.net/whois?searchtext=AS56911&object_type=aut-num&recursive=ON * http://www.db.ripe.net/whois?searchtext=AS60888&object_type=aut-num&recursive=ONWe also have valid ROAs as verified by RIPE for all the prefixes associated with AS56911