Action 1: Prevent propagation of incorrect routing information
BT take the security of customer prefix routing seriously and seek to allow our customers only advertise prefixes they are authenticated and allowed to be advertising. We ensure our customers IRR database information is valid and updated before implementing new prefix advertisements.
Action 2: Prevent traffic with spoofed source IP addresses
Customer Edge ports have anti-spoofing ACLs implemented on them to ensure we prevent spoofed IP address communication through our network.
Action 3: Facilitate global operational communication and coordination
We seek to ensure our peeringdb.com and other public facing contact information is valid and reaches real network engineering staff as required.
Action 4: Facilitate validation of routing information on a global scale
For all eBGP sessions we insist on validating ROUTE and ROUTE6 objects in IRR databases before bringing up the sessions. This we feel informs our customers of the importance of routing security and we also encourage them to create ROAs for their objects and indeed offer to assist in this creation process if needed.