Thoughts on World IPv6 Day

| | Comments (2) | TrackBacks (0)

As I'm sure you've heard by now, June 8, 2011 is World IPv6 Day. On that day, several major content providers will turn on IPv6 on their public-facing services for a 24-hour period and see what happens. For some time, there's been concern that turning on IPv6 on a web site's main URL (e.g., www.foo.com) would cause unacceptable levels of breakage (see, for example, slide 6 of this talk by Google at RIPE 57).

Nevertheless, forward-looking organizations realized that they needed to start deploying IPv6. They did this by putting IPv6 at a different URL (such as ipv6.google.com or www.v6.facebook.com), or by whitelisting approved domains for IPv6 access. These approaches let them get operational experience with IPv6 without impacting the vast majority of IPv4-only users (currently estimated at over 99% of the Internet). Nevertheless, URL tricks and whitelisting aren't scalable, long-term solutions, and there's a desire to see what would happen if we lit up IPv6 for real. Some sites have bitten the bullet and turned on IPv6 on their main site, with few problems. Others are more timid and want a limited-scope trial. Hence, IPv6 Day.

I'm certainly in favor of this, but the timing concerns me. The IANA IPv4 pool (the central pool of IPv4 addresses) is due to run out any day now, but IPv6 Day isn't for another six months. So, we'll end up doing out first large-scale production test of IPv6 after the first milestone of IPv4 depletion. This concerns me. The IT industry as a whole has dragged its feet with IPv6 for over a decade. Further delay seems ill-advised. I'm also worried that sites will turn off IPv6 at the end of the day. At the point, we should be leaving IPv6 enabled everywhere we can, unless there's a major problem. I hope that the hard work of many organizations leading up to IPv6 Day will mitigate most of the problems, and that we can use the results as reason to turn IPv6 on and leave it on.

Nevertheless, I give kudos to sites like Yahoo for stepping up and participating, even if it means some short-term breakage. The need to deploy IPv6 is too urgent to let fears of short-term problems paralyze us. I hope other sites with IPv6 pilots participate, like CNN and Wikipedia.

Penn State readers, consider this my public call to you to enable IPv6 on your services. Our internal audits reveal high levels of IPv6 support in several major services. Several highly visible services could be IPv6-enabled very easily (by slapping v6 addresses on a few load-balancers). Network admins should also deploy IPv6 to client machines, to increase the audience for IPv6-accessible content (it will also help reduce breakage from user-created IPv6 tunnels). There's no reason, other than willpower, why PSU can't participate in IPv6 Day.

0 TrackBacks

Listed below are links to blogs that reference this entry: Thoughts on World IPv6 Day.

TrackBack URL for this entry: https://blogs.psu.edu/mt4/mt-tb.cgi/223613

2 Comments

tommyfun said:

I'm trying to push my school to deploy ipv6 over a separate ssid on our wireless network. IPv6 needs to get a push from the college campus. Keep up the good work!!!!

Gerald said:

I've heard of the ivp6 switch for awhile. My concern is-If my university is not ready when the switch comes, will I still be able to access my school classes online? We seem to be always lagging behine to curve.

Leave a comment