Cloudflare: Tracking RFC 9234 Adoption (Stopping BGP Route Leaks)
Nie udało się dodać produktów
Nie udało się dodać tytułu do koszyka.
Nie udało się dodać tytułu do schowka.
„Usuń ze schowka“ nie powiodło się.
„Obserwuj podcast“ nie powiodło się
„Przestań obserwować podcast“ nie powiodło się
-
Czyta:
-
Autor:
Route leaks — when a BGP announcement propagates beyond where it should, often black-holing traffic — have historically been guarded by hand-written operator filters. Jordan and Riley walk through how RFC 9234 moves that protection into the protocol itself, using the BGP Role capability (neighbors negotiate provider/customer/peer up front) and the Only-to-Customer (OTC) attribute (routes get stamped so compliant routers auto-reject leaked ones), enforcing "valley-free" routing automatically. The catch from Cloudflare's real-world measurement: some large Tier-1 networks strip the OTC attribute as they forward routes, undermining protection for everyone downstream — a classic internet collective-action problem where the safety property only fully holds if the backbone cooperates. Source: BGP Role model: tracking the adoption of RFC 9234 — The Cloudflare Blog, Aug 18 2026 — https://blog.cloudflare.com/rfc9234-bgp-role-model/ This is commentary/summary in the hosts' own words, not a reproduction of the article.