North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: RIPE NCC publishes case study of youtube.com hijack
The report states:
Sunday, 24 February 2008, 20:07 (UTC): AS36561 (YouTube) starts announcing 18.104.22.168/24. With two identical prefixes in the routing system, BGP policy rules, such as preferring the shortest AS path, determine which route is chosen. This means that AS17557 (Pakistan Telecom) continues to attract some of YouTube's traffic.
It's worth noting that from where I sit, it appears as though none of Youtube's transit providers accepted this announcement. Only their peers.
The point is -- Restrictive customer filtering can also bite you in the butt. Trying to require your providers to do a "ge 19 le 25" (or whatever your largest supernet is), rather than filters for specific prefix sizes seems a worthwhile endeavor so you can de-aggregate on the fly, as necessary.
Tom Quilling wrote:
for those interested in the matter