BGP Role model: tracking the adoption of RFC 9234
- ID
- 15244
- Status
- summarized
- Published
- 18 Aug 2026, 11:21 PM
- Fetched
- 19 Aug 2026, 12:54 AM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/rfc9234-bgp-role-model/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 4.0
- Created
- 19 Aug 2026, 12:56 AM
- Tags
- Audience
- developerssaas_founders
What happened
Cloudflare analyzed the adoption of RFC 9234, which uses BGP Roles and the 'Only to Customer' (OTC) attribute to prevent route leaks at the protocol level. They discovered that two large Tier-1 networks are unexpectedly stripping the OTC attribute from routes, which undermines the route leak prevention capabilities for early adopters.
Why it matters
If you operate an Autonomous System (AS) and manage BGP routing, you should enable BGP Roles to automatically reject route leaks without writing complex policies, but you must be aware that some Tier-1 transit providers are currently stripping the OTC attribute, which can break this protection.
Discussion angle
The transition from manual, error-prone BGP routing policies to protocol-level intent using BGP Roles, and the real-world friction caused by Tier-1 networks stripping the OTC attribute.