Urgent.News

What's breaking now, across thousands of outlets.

Tech

BGP roles make route-leak policy visible in the protocol

BGP roles make route-leak policy visible in the protocol Route leaks and route hijacks are different failures. A hijack advertises a prefix that the origin is not authorized to announce. A leak sends a route to a relationship where it should never travel, such as exporting a route learned from one peer to another peer or upstream. RFC 9234 adds BGP roles and the Only to Customer attribute so…

BGP roles and the optional transitive path attribute, OTC, provide a means to detect route leaks and hijacks by enforcing relationship intent in the protocol. This RFC 9234 addition to BGP involves defining relationships between eBGP sessions as provider, customer, peer, route server, route-server client, or other non-role-based relationships.

During session establishment, the routers exchange a BGP Role capability to confirm the compatibility of the relationship roles. The OTC attribute then serves as an enforcement mechanism, preventing the route from moving to an unauthorized relationship type, such as a provider route appearing on a customer's side or vice versa. While roles and OTC attributes help identify relationship violations, they do not necessarily confirm the legitimacy of the route's origin or prevent hijacking.

Therefore, operators must still rely on other policies, including prefix filters, maximum-prefix limits, RPKI origin validation, and well-documented export policies. When deploying OTC, it is essential to roll it out gradually, initially logging role confirmation and expected OTC behavior, followed by enforcing it on a subset of sessions with established peer cooperation.

Complex peering relationships should not be assigned roles; instead, they should be segregated into separate sessions representing individual relationships. Routers should reject unsupported or inconsistent role pairs and only export routes to sessions with compatible relationships. To monitor the effectiveness of OTC, inventory external sessions, noting their local and remote roles, negotiated capabilities, export policies, and enforcement statuses.

Alert on role mismatches, disappearing roles after session resets, unexpected OTC values from customers, and sudden changes in the fraction of routes with OTC. During a route-leak investigation, correlating OTC state with data from the BGP Monitoring Protocol and configuration history is crucial. If a session resets and returns without OTC enforcement, the apparent normality of the path may mask the absence of safety controls.

Ultimately, RFC 9234's usefulness relies on operators demonstrating that the relationship was negotiated and that the resulting attribute was preserved throughout the BGP path.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Monday 16 November →