IPv6 teredo blackout June 8th
Brian E Carpenter
brian.e.carpenter at gmail.com
Wed Feb 2 21:39:58 CET 2011
On 2011-02-03 09:21, Ole Troan wrote:
>>> I want to open up a discussion on the potential failure of the teredo relays
>>> around the world on IPv6 day and anything we can do to mitigate it.
>> See comments from other regarding Teredo. This is probably a non-issue
>> at large. I'd rather worry about 6to4...
>> I wonder what current scalable 6to4 relay implementations are out there,
>> short of DIY Linux/BSD boxes. Cisco has 6to4 since aeons - but what
>> about scaling on "hardware" forwarding platforms? Juniper unfortunately
>> still doesn't implement 6to4 relay encaps on any router platform.
>> Sparing a 10GE port on MX for tunnel service 6to4 here and there would
>> certainly be the low hanging fruit for many folks here - no joy though,
>> too late I guess.
>> No debate on the big suckage factor of global anycast 6to4 - but we all
>> should carefully consider deploying 6to4 relays to unsuck 6to4 as far as
>> possible. Question is: what do we have in the toolbox currently? Also
>> we should think of a BCP how to deploy such relays (I never operated a
>> globally advertised anycast 6to4 relay myself, so cannot comment or
>> guesstimate how many things we can do wrong when trying to do so).
> what if we combine IPv6 world day with deprecate 6to4 day?
> everyone with public 6to4 relays stop advertising the IPv4 anycast address and 2002::/16 on June 8th.
I think that would be very counter-productive. As some people know,
there is a draft in development with a set of recommendations for
reducing 6to4 and Teredo operational pain. If we could pass a law
banning firewalls from blocking Protocol 41, for example, a lot
of 6to4 problems would vanish. But that isn't going to happen either.
The mentioned draft will be out fairly soon, and we could certainly
publicise it as part of the run-up to June 8th.
More information about the ipv6-ops