Action 1: Prevent propagation of incorrect routing information
1. Always request a signed Letter Of Authorization for any customer prefix/asn transiting our ASN.
2. Ensure strict inbound filters, reject Bogon, our own ASN, RFC1918 prefixes, matching customers prefix length for an announcement.
3. Ensure strict outbound filtering, matching specific communities values + prefix list of the transit customer, matching customers prefix length for an announcement.
4. Ensure RPKI validation is implemented and all relevant ROAs are up to date.
Action 2: Prevent traffic with spoofed source IP addresses
Agile Solutions Provider (PTY) Ltd makes use of uRPF Strict Mode, on the customer peering edge routers.
Action 3: Facilitate global operational communication and coordination
All relevant IRR (AfriNic) information is always updated upon change.
Ensuring an up to date AS Set (AS-AGILESP) and Route Set (RS-AGILESP).
Action 4: Facilitate validation of routing information on a global scale
We ensure that the RPKI certificate(s) and ROAs are kept up to date