# BGP Role Model: Tracking the Adoption of RFC 9234 New protocol to prevent internet routing leaks and enhance security. - **Source:** [Cloudflare Blog](https://blog.cloudflare.com) - **Published:** 2026-08-18 - **Original article:** - **On Brifing:** https://brifing.si/s/8f93e9ac-2e3e-4738-b1a2-2bdc7d63e286 ## BGP and Route Leaks Border Gateway Protocol (BGP) is a core protocol responsible for internet traffic routing. However, misconfigurations or intentional interference can redirect traffic through unintended paths, known as 'route leaks.' These incidents can cause large-scale outages. For example, a 2017 BGP leak redirected Google's traffic through Russia and China, causing significant disruptions. ## What RFC 9234 Introduces RFC 9234 aims to prevent route leaks by introducing the 'Role' concept in BGP. This feature defines the relationship between BGP neighbors, ensuring traffic follows only designated paths. The 'Only to Customer' (OTC) attribute allows routers to automatically detect and block leaks without manual intervention, significantly improving security. ## How OTC Works The OTC attribute marks routes that should only be forwarded to customers, preventing propagation to other providers or peers. For example, a route received from a provider can only be sent to customers, not back to another provider. This enforces 'valley-free' routing, automatically blocking unauthorized paths. ## OTC Stripping by Tier-1 Networks Cloudflare's research revealed that two major Tier-1 networks strip the OTC attribute from routes they forward. This undermines RFC 9234's effectiveness. Tier-1 networks form the backbone of the internet, making this issue critical. Cloudflare is collaborating with these networks to preserve OTC and ensure full protocol adoption. ## Adoption Rates of BGP Roles Cloudflare uses its global network to measure the adoption of BGP Role configurations. So far, many networks have begun implementing RFC 9234 incrementally. However, strict mode, which rejects sessions without Role capabilities, is not yet widely adopted. Full deployment will take time, especially among Tier-1 providers. ## Impact of Route Leaks Route leaks can misdirect traffic and cause significant latency. For instance, in 2008, Pakistan Telecom's attempt to block YouTube traffic led to a global outage due to misrouting. Measures like RFC 9234 are crucial to prevent such incidents, ensuring a more stable and secure internet infrastructure. ## BGP Role Mismatches RFC 9234 rejects BGP sessions with role mismatches. For example, if one end declares 'customer' and the other 'peer,' the connection fails. This prevents misconfigurations but requires widespread adoption to be fully effective. Currently, partial deployment is more common, with strict mode being optional. ## Route Server and RS-Client Roles BGP Roles include special designations for Internet Exchange (IX) route servers. The RS (Route Server) and RS-Client roles enable transparent traffic exchange among IX members, improving routing efficiency. Route servers act like providers to their clients, redistributing prefixes seamlessly within the exchange. ## The Future of RFC 9234 RFC 9234 is a significant step toward securing BGP, but full adoption is ongoing. Tier-1 networks' support for OTC is critical. Efforts by companies like Cloudflare may accelerate this process. Long-term, the protocol promises a more resilient and secure internet routing infrastructure. ## Benefits of BGP Role Configuration BGP Role configuration reduces the need for manual routing policies, minimizing human error and outages. The OTC attribute automates leak prevention, benefiting smaller networks with limited resources. This shift toward protocol-enforced security marks a major advancement in internet routing. ## Cloudflare's Role in Adoption Cloudflare developed a unique method to track RFC 9234 adoption by monitoring OTC attribute propagation. Its global presence allows real-time insights into which networks support the feature. Collaborations with Tier-1 providers aim to resolve OTC stripping issues, paving the way for broader implementation. ## Conclusion and Recommendations RFC 9234 is a pivotal step toward securing internet routing, but adoption is still in progress. Network operators should implement BGP Roles, and Tier-1 providers must preserve OTC attributes. Cloudflare's initiatives highlight the importance of industry collaboration. A more secure internet infrastructure is within reach with concerted effort. ## Sources covering this story - https://blog.cloudflare.com/rfc9234-bgp-role-model/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._