After Launch Day: Taking Stock of IPv6 Adoption 244
darthcamaro writes "So how did World IPv6 Launch go? Surprisingly well, according to participants at the event. Google said it has seen 150% growth in IPv6 traffic, Facebook now has 27 million IPv6 users and Akamai is serving 100x more IPv6 traffic. But it's still a 'brocolli' technology. 'I've said in the past that IPv6 is a 'broccoli' technology,' Leslie Daigle, CTO of the Internet Society said. 'I still think it is a tech everybody knows it would be good if we ate more of it but nobody wants to eat it without the cheese sauce.'" Reader SmartAboutThings adds a few data points: "According to Google statistics, Romania leads the way with a 6.55% adoption rate, followed by France with 4.67%. Japan is on the third place so far with 1.57% but it seems here 'users still experience significant reliability or latency issues connecting to IPv6-enabled websites.' In the U.S. and China the users have noticed infrequent issues connecting to the new protocol, but still the adoption rate is 0.93% and 0.58%, respectively."
Re:Privacy Concerns (Score:3, Insightful)
Re:IPV6 is BROCCOLI!? (Score:5, Insightful)
To be fair, broccoli is good if it's fresh and is in the "goldilocks zone" - not too crisp, not too soggy. Brussels sprouts are similar: Obviously don't give them to me raw, but I'd prefer to not eat a soggy bitter mass of plant pulp.
Can't say I've ever had kale. I enjoy collard greens, does that count?
Re:Quick Fix (Score:4, Insightful)
Routers and end systems would still need to be taught how to speak a new protocol; machines that only know how to construct and decode packets in IPv4 format would be unable to deal with your "extended addresses". What exactly would you gain?
Also, IPv6 is much more than just an extension of the addressing space. I won't bother listing all the niceties here since it has been done before (and you can find them easily). But to think that everything IPv6 has to offer is a lot more addresses is extremely narrow-minded.
Re:Privacy Concerns (Score:2, Insightful)
No, they won't. It would be more work for them to give out a single IPv6 address than to give out a block. The official recommendation for residential customers is a /56, in Comcasts trials so far they've been giving out /64s. That's 18,446,744,073,709,551,616 addresses for each home. I don't think you remotely understand the size of the IPv6 space. NAT will die.
Re:Privacy Concerns (Score:4, Insightful)
Mostly because a lot of enterprise IT departments have serious issues with anything new and thus "scary" and "untested". Hell, I know places that still critical production systems on NT4 and think Subversion is too new and untested to be used as a production VCS so they just stick to CVS since "everyone knows it and it works".
On a similar note, these are the kind of places that mandate that all database queries be made as stored procedures (T-SQL, of course) since that's the only "safe" way of accessing a database. Bring up parameterized queries and they look at you like you're mad. In places like that they have working security put in place 10 - 15 years ago and they have no intention of changing anything until they absolutely have to. In their world security "needs" NAT (because that's what their equally old firewall appliance needs).
Re:Quick Fix (Score:5, Insightful)
Extending an IPv4 stack to use 64 bit addressing
Almost as much work as IPv6. You would still have to change out ALL of the hardware in the world and still have to update ALL of the software. If it's going to be the same amount of large scale work, just do it correctly the first time.