Agentic data science with the Data Agent Kit
cloud.google.com·6h ago
Security
Cloudflare Blog·Aug 18·5 min read
BGP Role model: tracking the adoption of RFC 9234
TL;DR
RFC 9234 enables routers to autonomously reject route leaks using BGP Roles and the Only to Customer attribute. Our analysis revealed that two Tier 1 networks are unexpectedly stripping the Only to Customer attribute.
✦ Why It Matters
Evaluate your network's BGP configuration to ensure compliance with RFC 9234 and prevent potential route leaks.
Key Takeaways
- Implement RFC 9234 to prevent route leaks in BGP.
- Monitor OTC attributes from peers to assess compliance.
- Engage with networks stripping OTC to improve routing stability.
- Utilize Cloudflare's data for insights on BGP adoption.
How It Works
RFC 9234 introduces BGP Roles to define relationships between Autonomous Systems (ASes) and the OTC attribute to mark routes that should not propagate beyond customers. This allows routers to automatically reject leaked routes based on the defined relationships, reducing reliance on complex manual policies.