Re: The IPv6 Transitional Preference Problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lets make sure this does not become a bash Apple affair.

Apple's airport is the only WiFi hardware I have had that has not stopped working within 9 months due to shoddy manufacture. I have had every brand you can name and every one failed in the same way, connections became flaky and then the router started requiring regular resets.

Hang on a moment, the rant is relevant to the IPv6 transition

When I mentioned the hardware issue to a certain tech savy person known to us all they reported having no problems at all with their routers. Then I watched them using said router and rebooting it without noticing they had done it.

Can be made to work for a geek is a much lower bar than the one we face here. The premise is that we need IPv6 transition because we have the billions of users. It has to work absolutely flawlessly to be useful.


On Thu, Jun 17, 2010 at 7:38 AM, Sabahattin Gucukoglu <mail@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Just in case someone here wants to take sides, have a look at this thread on the IPv6 discussion list at Apple:
http://lists.apple.com/archives/ipv6-dev/2010/Jun/msg00000.html
(the thread actually goes back earlier than that, but I can't be bothered going looking for it because I can't stand that awful PiperMail interface)

Summary: it is a problem for some people, notably content providers, that connectivity losses result from a preference to use (advertised) v6 routes.  Mac OS X, in particular, has this habit of treating even the commonplace 6to4 routes, which of course fail occasionally for a number of reasons, just as native IPv6, and preferring them.  It has no address selection table, so it will flunk even when IPv4 would have worked fine, i.e., will not treat common v4-NAT environment as global scope.

My take: it's not their fault.  Transition mechanisms must improve, because they're needed even into the IPv4 twilight.  However, it's been noted before that an API for selection of the protocol based on application requirements is a solution to this particular paradox, and I agree with that.

Cheers,
Sabahattin
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf



--
Website: http://hallambaker.com/

_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]