Prevent route leaking with ASPA and BGP roles#
Netnod Tech Meeting 2026 digest Program Core pick 6 October 2026
Speakers: Johan Ervenius - Arista Networks
- Why: Route leaks remain one of the highest-impact, recurring Internet failures, and this covers the two current standards-track defenses — ASPA (RPKI-based AS provider authorization) and BGP roles (RFC 9234 OTC) — which is directly relevant to the PM's network-security and BGP-internals interests and to any operator's routing hygiene roadmap.
- What: A technical talk on deploying ASPA and BGP role/OTC mechanisms to prevent route leaks. (from title only)
- How: ASPA lets an AS cryptographically authorize its providers, enabling a validator on the receiving AS to detect and reject leaks; BGP roles add a per-session role (e.g., customer/provider/peer) signaled in the session so OTC-marked routes from the wrong direction can be dropped. This framing is from the standards, not the talk's confirmed content.
- Where applicable: Broadly applicable standards work, though the speaker is from Arista — expect standards content rather than a product pitch, but verify the deployment guidance isn't vendor-feature-shaped.