- Areas ServedBR
Implementation of MANRS Actions
- Action 1: Prevent propagation of incorrect routing information In our AS, we filter out our prefixes and our customers (downstreans) exactly as BCP 194 (https://tools.ietf.org/html/bcp194) indicates. We do not allow prefixes for IPv4 more specific than / 24, and for IPv6 not more specific than / 48 and prefixes that do not originate in your ASN (ASPath). We always analyze documentation registered with the NIRs for new downstreans to validate that their prefixes are correctly informed for the new policies. We do not publish prefixes that are from other ASNs.
- Action 3: Facilitate global operational communication and coordination We have a record in Peering Db, where we basically leave public information like ASN, traffic and connection with IXs. Contacts are very important, and we leave them there for any eventuality, all contacts are validated and accessed daily.
- Action 4: Facilitate validation of routing information on a global scale
Why Radar Internet Supports MANRS
Congratulations on the great work of encouraging good operational practices on the internet I see this as the only way to have a cleaner and safer internet. I will disclose to my friends who also take care of autonomous systems.CTO Radar Internet