On Fri, Jun 10, 2011 at 9:18 AM, Noel Chiappa <jnc@xxxxxxxxxxxxxxxxxxx> wrote:
> Mac OS 10.6.4, which uses 6to4 by default, has a ~50x greater failure> ...
> rate when connecting to dual-stack servers than Mac OS 10.6.5 - and the
> only change is to not use 6to4 by default.
> So the existence of 6to4 is in itself a significant barrier for IPv6Surely you meant to say "the _incorrect configuration_ of 6to4 is in itself a
> deployment
significant barrier"?
You cannot expect something to be configured correctly if it is simply turned on without a) being managed by someone or b) detection mechanisms to see if it's working. Sadly, anycasted 6to4 meets neither of these conditions.
I get the impression that the problem comes in when 6to4 is configured on by default, and too high in the priority list (as opposed to native, other
methods, etc). So fix the real issue, don't try and prematurely kill off
something that's being used by lots of people.
I fundamentally disagree. I really don't think that 6to4 is used by "lots" of people for applications that wouldn't just use (more reliable) IPv4 if 6to4 wasn't there.
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf