On Wed, Oct 01, 2008 at 07:53:03AM -0700, Andrew Lentvorski wrote:
Well, the continuing frustratation^Wmigration from IPv4 to IPv6 shows this is *very* tightly coupled. It is not very easy to rip out. The problem, of course, if the fact that you have to replace the state machines on *both* sides simultaneously.
Except that I don't think the lack of migration to IPv6 has anything to do with problems in the underlying protocol. Most modern operating systems already support IPv6. A bigger problem is that the API between the client application and the TCP stack changes when you move to IPv6. But, probably killing it even more than that is the lack of infrastructure. I've never had an ISP at home that supported IPv6, other than having a 6-4 gateway that sometimes works. I can do IPv6 at work, and happily browse the 5 websites that are on IPv6. David -- KPLUG-LPSG@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
