CloudFlare IPv6 BGP announcements - WTF guys?
Oliver
olipro at 8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa
Mon Jul 16 15:45:43 CEST 2012
On Saturday 14 July 2012 22:45:34 Bernhard Schmidt wrote:
> Akamai is (at least in RIPE space) now having the same problem. They
> used to announce the /32 from somewhere and additional /48s, so at least
> the traffic went somewhere. They dropped the /32 now, so everyone
> filtering strict has no route to Akamai anymore.
>
> FWIW, I'm talking about 2a02:26f0::/32. There are Akamai clusters in ISP
> PA space that still work of course.
>
> Bernhard
The whole thing is daft; even if you've got multiple upstreams, there's still
*nothing* preventing you from exposing only your /32 to the rest of the
internet and tagging more specifics with NO_EXPORT to each of your upstreams.
The only time that doesn't solve the issue is when you specifically want to
force a given prefix to a particular point through a particular upstream;
although in that case, go create a route object or arrange something with your
transit providers.
If your modus operandi is to pollute the routing tables, you deserve all the
unreachability you get.
Regards,
Oliver
More information about the ipv6-ops
mailing list