Suppressing BGP Zombies with Route Status Transparency
summary
Route Status Transparency (RoST) introduces a counter per prefix-interface and a shared repository so ASes can cryptographically verify that a route was actually withdrawn rather than suppressed; repositories store periodic RPKI-signed Merkle batches so fetches return compact proofs and signatures. RoST is BGP-compatible, resists malicious repositories and ASes, and simulation on AS-level topology plus real BGP datasets show low storage/bandwidth/computation overhead; with ~60% adoption about 80% of ASes detect suppression.
AI-written summary · about
chapters (7)
- 0:00BGP zombies problem
- 2:11BGP withdraw suppression zombies
- 4:21BGP zombies impact on routing
- 5:47Route Status Transparency solution
- 9:53Security in Route Status Transparency
- 12:44Partial adoption benefits for ROS
- 14:09Summary of solution
related talks
21mStealth BGP Hijacks with uRPF Filtering
32mLet's talk about routing security
12mxBGP: Faster Innovation in Routing Protocols
22mBGP Vortex: Update Message Floods Can Create Internet Instabilities
35mRoute to Bugs: Analyzing the Security of BGP Message Parsing
35mROTE: Rollback Protection for Trusted Execution
14mTANGO: Secure Collaborative Route Control across the Public Internet
33mAdvanced rp_ filter