Re: Open letter to Level3 concerning the global routing issues on June 12th

At 08:44 UTC on Friday 12th of June, one of your transit customers, Telekom Malaysia (AS4788) began announcing the full Internet table back to you, which you accepted and propagated to your peers and customers, causing global outages for close to 3 hours.

One thing of notice is that AS Paths were really not short, so some kind of local preference has to be in place. Although it's usual to apply local preference to transit customers, it's probably wise to only do it for prefixes belonging to customer or registered at IRRs. So, if someone does not want to filter prefixes from customers, at least could not apply larger preference to all such prefixes. Focus on the know prefixes and let AS Path sort out those weird paths. Rubens