BGP Role model: tracking the adoption of RFC 9234

RFC 9234 lets routers reject route leaks on their own, using BGP Roles and the Only to Customer attribute.

The short version

• We measured who has deployed it, and found two Tier 1 networks unexpectedly stripping OTC.
• Before the measurements, let’s talk about how BGP Roles and the OTC attribute actually work.
• Route leaks are the “propagation of routing announcements beyond their intended scope,” as defined in RFC 7908 .

What happened

The intended scope is determined by AS relationships: provider-to-customer or peer-to-peer. The rules are asymmetric, and it comes down to direction.

Why it matters

Routes propagate freely downward: a provider may hand a customer anything in its table.

Summary by Nerd News Network. Read the full article at Cloudflare Blog via the links above and below.