Forgot your password?
typodupeerror
The Internet Networking Technology

Worldwide IPv6 Adoption: Where Do We Stand Today? 327

Posted by Soulskill
from the very-slightly-ahead-of-where-we-stood-several-years-ago dept.
skade88 writes "IPv4 is much like a limited natural resource; it can't last forever. The well of new IPv4 addresses is already running dry in many parts of the world. The solution to this problem, which was presented decades ago, is to switch to IPv6. With peak IPv4 far behind us, why do we still see limited IPv6 adoption? Ars takes a good look at where we are and where we are going with the future of IP addresses, the internet and you. Quoting: 'As with all technology, IPv6 gets better and cheaper over time. And just like with houses, people prefer waiting rather than buying when prices are dropping. To make matters worse, if you're the only one adopting IPv6, this buys you very little. You can only use the new protocol once the people you communicate with have upgraded as well. Worse still, you can't get rid of IPv4 until everyone you communicate with has adopted IPv6. And the pain of the shrinking IPv4 supplies versus the pain of having to upgrade equipment and software varies for different groups of Internet users. So some people want to move to IPv6 and leave IPv4 behind sooner rather than later, but others plan on sticking with IPv4 until the bitter end. As a result, we have a nasty Nash equilibrium: nobody can improve their own situation by unilaterally adopting IPv6.'"
This discussion has been archived. No new comments can be posted.

Worldwide IPv6 Adoption: Where Do We Stand Today?

Comments Filter:
  • by Viol8 (599362) on Friday January 04, 2013 @04:22PM (#42479477)

    We have so many test VMs appearing and disappearing on our network that we don't bother putting them in DNS, we just give out the IP4 192.168... address for the testers and devs. I dread to think what would happen if we had to give them the line noise that is an IP6 address. Whatever other merits IP6 has, the designers REALLY didn't think it through at the manual address entry level.

  • by Aqualung812 (959532) on Friday January 04, 2013 @04:28PM (#42479559)

    the designers REALLY didn't think it through at the manual address entry level.

    Yeah, they did, and they decided that the only servers that need a manual address are DNS servers and DHCP servers (if you choose to run DHCP).
    Outside of those, the only other things that need manual addresses are routers.

    Everything else should use Dynamic DNS.

    Give me a good reason why someone shouldn't be using DNS instead of direct IP address, other than lazy programmers.

  • by bartjan (197895) <bartjan@[ ]elink.net ['vri' in gap]> on Friday January 04, 2013 @04:35PM (#42479655) Homepage

    bartjan@ix:~$ ping6 slashdot.org
    unknown host
    bartjan@ix:~$

    Maybe about time to update this story from 2003 [slashdot.org]??

  • Re:That's easy. (Score:5, Insightful)

    by MajroMax (112652) on Friday January 04, 2013 @04:38PM (#42479697)

    That won't work in the long-term. The problem with carrier-grade NAT is that the ISPs have to... maintain carrier-grade NAT.

    Network Address Translation is a stateful protocol, and it's orders of magnitude more expensive to maintain connection tracking on a per-connection basis for your customers than it is to simply route packets between networks. Even ISPs that use Deep Packet Inspection have the luxury of looking at selected traffic flows; carrier-grade NAT has to cover everything or it doesn't work.

  • by gclef (96311) on Friday January 04, 2013 @04:42PM (#42479755)

    One good reason why *servers* shouldn't be using DynamicDNS? I'll give you two.

    First scenario: your server isn't responding. How do you tell the difference between a failure of the server itself and a Dynamic DNS registration failure? If you don't know it's IPv6 address, how can you tell if its fine, just not registering in DNS properly? Heck, if it's not registering properly, how do you find it at all?

    Or, more fun: the server reboots & ends up with a different dynamic IPv6 address....even if it registers the new address to its name properly, clients don't always honor DNS cache times, and will keep trying the old address for a while. You've now created an outage for no good reason.

    If you said that desktops don't need static DNS, I'd agree with you completely. But making server infrastructure totally reliant on a middle layer is asking for trouble...things'll work fine until you have a problem & need to troubleshoot. Then your reliance on an external system will bite you in the ass.

  • by Anonymous Coward on Friday January 04, 2013 @04:59PM (#42479987)

    No-one at Slashdot knows very much about this technology stuff. It's more about maintaining a nerd image by wearing weird glasses.

  • by Dagger2 (1177377) on Friday January 04, 2013 @05:31PM (#42480481)
    You've pretty much just described 6to4. We have it already.

You will be successful in your work.

Working...