Slashdot Mirror
After Launch Day: Taking Stock of IPv6 Adoption
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."
What a terrible metaphor. Everyone knows that IPv6 is closer to a Brussels Sprout.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
http://blogs.voxeo.com/speakingofstandards/2011/05/22/fun-with-ipv6-addresses-check-out-facebooks-aaaa-record-in-dns/
On the consumer front only just recently did home WiFi routers start shipping or start getting IPv6 support, even then finding an ISP that will provision you is next to impossible.
On the enterprise front gear has been labeled as IPv6 ready or compatible or even listed it as a feature for a long time. However if you work in security and have to implement policy control over content, you quickly see that the functionality is years behind when applied to IPv6 flows... At an enterprise level switching isn't easy without swamping out a lot of gear, or reducing expectations... IPv6 enabled deep inspection, and application layer inspection tools are only now becoming available, or only now becoming mature enough to roll out.
EA David Gardner -"... but the consumers have proven that actually what they want is fun."
So, it sounds disgusting and nobody wants it? Cheese sauce on cake?
That would explain a lot.
Lost at C:>. Found at C.
I've never understood this concern. With IPv6 I have, say, 2^64 addresses to use. I could use a different source IP address for each and every HTTP request I send out. Even at 1000 requests a second we'll all be long dead before you had to reuse a source address.
IPv6 gives you loads of room to hide. This is my concern - address based blocklists will quickly become infeasible.
There can be a real difference between "Can do IPv6" and "Can do IPv6 with realistic traffic." Most high end Cisco gear, even older stuff could be updated to support IPv6. However the problem is that it is all in software, all on the rather small CPU. So sure it'll work if you have only a couple IPv6 flows, however if everything went IPv6 it'd fall over. You need support in the ASICs for it, and that means buying new hardware.
Of course being high end it isn't so cheap. We upgraded all our stuff on campus to do IPv6 and it was millions to get all the hardware needed. Now we are large, but not compared to many ISPs. So it isn't so easy to just say "Oh buy a bunch of new equipment to replace the perfectly good stuff you already have."
IPv6 is coming, slowly, but it isn't going to be a fast process and anyone who things people, ISPs, etc should "Just do it," hasn't spent any real time looking at what is involved.
I've never understood this concern.
Me either.
IPv6 gives you loads of room to hide. This is my concern - address based blocklists will quickly become infeasible
It it won't be that much different with v6 and a slight change in mindset. Instead ofblocking an IP you go after the prefix instead.
For example an ISP customer is abusing my service and I want to block him. I don't go after his IPv6 IP I go after his entire /64, /48 prefix or whatever it is his ISP allocated to him. He can change his local bits all he wants he is still blocked.
There are other examples where it is difficult such as blocking some computers on the same /64 segment as others you want to allow however when we look at this problem today all we see most of the time is a NAT for the whole network with a single IP.
The address space is bigger and there is more room to hide yet allocation is still hierarchical and we still know what blocks are allocated to who via SWIP or working an ISPs abuse channels.
In one pot, put some kale, some olive oil, water, a little salt and pepper, and let simmer on low heat. In another pan, brown up some ground beef, with some chopped onions, green peppers. Add in a can of salsa or crushed tomatos. If desired, some hot sauce or jalapenos can be added. While that's cooking, do up some Kraft Dinner according to the directions on the box. When the KD is ready, add in the ground beef mix, and serve. Throw out the kale.
Note: This recipe works well for broccoli, Brussels sprouts, cauliflower, spinach, and many others.
When our name is on the back of your car, we're behind you all the way!
Why isn't slashdot accessible over IPv6?
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.