BGP Role model: tracking the adoption of RFC 9234
RFC 9234 lets routers reject route leaks on their own, using BGP Roles and the Only to Customer attribute. We measured who has deployed it, and found two Tier 1 networks unexpectedly stripping OTC.
Discussion around the web
- Hacker News2 · 0 💬
Score breakdown
- Technical depth56
- Practical value60
- Originality100
- Writing quality100
- Source reputation90
- Recency77
- External engagement4
- On-site engagement0
More like this
Engineering at Meta52
Running Border Gateway Protocol in large-scale data centers
unknown·5 min read
Lyft Engineering55
Beyond A/B Testing: Using Surrogacy and Region-Splits to Measure Long-Term Effects in Marketplaces
Iraklikhorguani·unknown·8 min read
Lyft Engineering62
From Chaos to Clarity: How We Built a Unified, Self-Routing Support Ops Ticketing System at Lyft
Atulgupta·unknown·10 min read
Airbnb Engineering62
Scaling beyond one: How Airbnb evolved its data architecture for a multi-product world
Patrick Lam·unknown·10 min read
Engradar shows a summary and links to the original article. The full article is hosted on blog.cloudflare.com.