News for hackers. Stuff that matters.
Re:The IPv6 Mess by jsz0 on Friday April 02, 2010 @04:40AM (#1236195)
"It gets worse. The IPv6 designers don't have a transition plan"

This is either an old article or the author is not up to speed. Good example why you should date your articles. I met with Cisco a couple months ago and they detailed their IPV6 strategy to us from the service provider perspective. In short: They're throwing a bunch of different strategies at the problem to cover all the bases. It's not an elegant solution. More like brute force with a focus on preserving total interoperability. This stuff is already in the wild today on a small scale. It works. Comcast, COX, TWC, etc all have active deployments and are looking at large scale rollouts over the next year.

http://www.ict-partner.net/en/US/prod/collateral/iosswrel/ps...

Re:The IPv6 Mess by loup-vaillant on Friday April 02, 2010 @05:15AM (#1236217)
The article is dated, but not outdated. The page you linked to is clear: "IPv4 and IPv6 protocols are not directly compatible, and hence various techniques are necessary for their coexistence". If IPv6 were compatible with IPv4 in the first place, the "various techniques" wouldn't be necessary, and transition would have taken years, not decades.
Re:The IPv6 Mess by Chronos on Sunday April 04, 2010 @08:43PM (#1241090)
How would you propose making IPv6 compatible with IPv4? Recall that every IPv4 application in the history of Berkeley Sockets has 32-bit address buffers hardcoded into the binary.
Re:The IPv6 Mess by loup-vaillant on Monday April 05, 2010 @04:47PM (#1243019)
How this hard-coded size renders backward compatibility difficult?