Action 1: Prevent propagation of incorrect routing information
We filter at the edge based IRR, RPKI Status and some additional filters on bogons and so on.
Action 2: Prevent traffic with spoofed source IP addresses
We use static firewall rules and additional policy based routing to only allow traffic generated from our own prefixes onto the internet.
Action 3: Facilitate global operational communication and coordination
PeeringDB, and RIPE NCC whois contain updated and active contact data.
Action 4: Facilitate validation of routing information on a global scale
.