Slashdot Mirror


Most Enterprises Plan To Be On IPv6 By 2013

Julie188 writes "More than 70% of IT departments plan to upgrade their websites to support IPv6 within the next 24 months, according to a recent survey of more than 200 IT professionals conducted by Network World. Plus, 65% say they will have IPv6 running on their internal networks by then, too. One survey respondent, John Mann, a network architect at Monash University in Melbourne, Australia, said his organization has been making steady IPv6 progress since 2008. 'Mostly IPv6 has just worked,' he said. 'The biggest problem is maintaining forward progress with IPv6 while it is still possible to take the easy option and fall back to IPv4.'"

3 of 167 comments (clear)

  1. A statistical knee-slapper by geekmux · · Score: 2, Informative

    "...Plus, 65% say they will have IPv6 running on their internal networks by then, too."

    OK, you almost had me at upgrading corporate web servers (comprising of usually only a handful of machines serving that purpose), but do you honestly expect me to believe that 65% of corporate IT budgets are suddenly and magically going to prioritize an IPv6 transition, as they sit comfortably behind their NAT-enabled firewalled environment, the same environment that will continue to work with zero change?

    Talk about going from zero to bullshit in 4.2 seconds. If corporations haven't been listening about the impending "doom" around IPv4 for the last decade, they sure as hell aren't going to start that suddenly now.

  2. Re:Ya right maybe off XP by 2013 by camperdave · · Score: 4, Informative

    I work for a pretty good sized company and we'll be lucky to be off XP by then...

    No need to worry about that. XP has IPv6 support.

    --
    When our name is on the back of your car, we're behind you all the way!
  3. Re:and what does IPV6 do for inside network any wa by smash · · Score: 3, Informative

    If you're a business, it allows you to MERGE NETWORKS or talk between two discrete LANs in a far more convenient manner. If you've ever had to support the situation where say, you want to talk between a corp network running on 10.0.0.0/8 and another corp also using 10.0.0.0/8, you'll understand the brain damage that IPV4 NAT brings to the table.

    Ditto for home users trying to VPN into your network when they're using 10/8 or another one of the private networks on their LAN that you happen to have employed inside your LAN as well.

    IPV4 is broken and needs to die.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.