Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
The Internet The Almighty Buck

IPv6 Transition to Cost US $75 Billion? 462

darthcamaro writes "There are alot of reasons why the US isn't moving as quickly as Japan and Europe in migrating to IPv6. One of those reasons is likely cost. An article on Internetnews.com cites an unreleased 'Dept. of Commerce report estimating it will take $25-$75 billion to pay for the transition.'"
This discussion has been archived. No new comments can be posted.

IPv6 Transition to Cost US $75 Billion?

Comments Filter:
  • IPv6 is a mess (Score:3, Informative)

    by Marrow ( 195242 ) on Monday December 12, 2005 @08:38PM (#14243105)
    http://cr.yp.to/djbdns/ipv6mess.html [cr.yp.to]

    Do we really have to throw this much money into the volcano?
  • by shanen ( 462549 ) on Monday December 12, 2005 @08:47PM (#14243164) Homepage Journal
    Exactly the same kind of foolishness that keeps the US from going metric. If you prefer to see it as an opportunity to invest in new metric tools or IPv6 hardware and software, then it looks like an opportunity. The people who fight against such changes want to harp on the total costs, and generally refuse to consider rational transition strategies.

    To me, it mostly comes down to efficiencies. The reason we measure things in the first place is so we can perform mathematical operations on the resulting numbers. Metric units are easier and more efficient for the mathematical operations, and therefore confer some competitive advantage on the people using them. It might be a large or small advantage, but it's always there.

    IPv4 has some design limitations. IPv6 will address many of those problems, and the networks (and countries) that use that system will have competitive advantage.

    What I find amusing is that many of the same people fighting against IPv6 on grounds of cost are the same people who want to argue the damage of Hurricane Katrina wasn't so bad. After all, it will give us the "opportunity" to invest billions of dollars in rebuilding things. Hey, why don't we destroy a major city every year? Look at all the "opportunities" we'd have. However, moving to IPv6 is NOT to be equated with random destruction, but is rather a rational form of evolution.

  • by tuomoks ( 246421 ) <tuomo@descolada.com> on Monday December 12, 2005 @08:49PM (#14243177) Homepage
    A very good question (IMHO) and I know "something" about IPv6. Now, of course, if that estimate is like many other I have seen in government/corporation contarcs, like $1 million modem programs, $2 million for simple SQL queries, and so on, it may even be a low estimate. I have real problems with companies billing millions of standard UDP/TCP/IP, encryption, compress, etc interfaces. But what do I know - I just write those as slow and as complicated as I'm told. IPv6 is not "rocket sciense" but a rather well defined protocoll which, amazingly, works with IPv4.
  • June 2008 deadline (Score:3, Informative)

    by jhines ( 82154 ) <john@jhines.org> on Monday December 12, 2005 @09:06PM (#14243270) Homepage
    From the fine article,

    "The government is supposed to be on a relatively rapid path toward IPv6 migration since the Office of Management and Budget (OMB) mandated (PDF file) this past August that the federal government move to IPv6 by June 2008."

    But yes, there is an annual IT budget that is impacted by this.
  • Re:What's needed? (Score:5, Informative)

    by Michael Hunt ( 585391 ) on Monday December 12, 2005 @09:30PM (#14243404) Homepage
    You don't seem to know what you're talking about.

    Any ISP with 100k customers (or even one with an order of magnitude less) is going to be assigned a /32 (or shorter) prefix, which is guaranteed to be globally portable.

    The basic structure of an IPv6 address is:
    0-31 Top-level network bits
    32-47 16 bits for customer allocations (/48)
    48-63 Customers' subnetworks
    64-127 Local subnet addressing (EUI64)

    If you've been allocated a /48 by your ISP, sure, you'll need to renumber every time you change ISPs. If you've been allocated a /32 or shorter prefix by a RIR, then you won't.

    BGP4+ Routing tables will also be correspondingly smaller, because they'll only contain a number of /32 prefixes (a much smaller number than the current IPv4 soup, which includes prefixes as long as /24 for legacy reasons.)

    I humbly submit that you do more research in future.
  • by akmarksman ( 928492 ) on Monday December 12, 2005 @09:34PM (#14243429)
    How about NOT building that "Bridge to Nowhere" in Alaska. That would save some money.
  • by NevDull ( 170554 ) on Monday December 12, 2005 @10:38PM (#14243707) Homepage Journal
    Maybe they're calculating it based upon "router equivalents", in the same way that RIAA calculates "burner equivalents" [theregister.co.uk].
  • by billstewart ( 78916 ) on Monday December 12, 2005 @10:41PM (#14243725) Journal
    Yes, lots of the equipment gets old and eventually needs replacing, but the government really does keep equipment around long after it'd be obsolete in the commercial world - after all, a desk grunt who's typing memos at 100wpm and sending a bit of email is only generating information at ~100 baud, and as long as you stay off the Upgrade-Microsoft-Office-Every-Year treadmill, the main reason not to be using a 386 PC is that too many web pages want newer memory-hogging browsers, and even upgrading to a 3GHz Pentium doesn't mean you need a bigger router for the office if he's not downloading a lot more material.

    But upgrading custom software is a much different scale of project than simply upgrading boxes and reconfiguring some web servers. There's a huge amount of mission-critical big nasty badly-documented stuff out there running on mainframes, PCs, and Unix boxes of various sorts that knows about IPv4 and might or might not know about DNS and DHCP. Finding all of it isn't quite the same level of effort as finding Y2K bugs, but it's still a huge hard-to-estimate job.

  • Re:What's needed? (Score:3, Informative)

    by Solosoft ( 622322 ) <chris@solosoft.org> on Monday December 12, 2005 @11:03PM (#14243829) Homepage
    Windows with a patch ?

    To enable ipv6 on a Windows XP machine goto run and type "ipv6 install" wait a few minutes and boom. If you got somthing like radvd running it will fetch the info it needs and assign the address.

    Cause im running ipv6 on my WRT54Gs v4 [solosoft.org] running radvd and all my windows machines picked it up right away after typing that command. I think Windows 2000 needs a patch to get it to work but im sure by the time ipv6 becomes standard Windows 2000 will be unsupported.

    Please don't be spitting out shit ... thanks
  • Re:$25-$75 billion (Score:4, Informative)

    by JWSmythe ( 446288 ) * <jwsmytheNO@SPAMjwsmythe.com> on Monday December 12, 2005 @11:15PM (#14243867) Homepage Journal

        Actually, the current estimate on the war in Iraq is $350 billion. But hey, what's $135 billion dollars between friends. :)

        The estimated daily cost in late 2004 was $177M per day. Take a few months off of the war, and you have the cost of migration.

        There are many better ways to spend that cash though. Think schools, healthcare, infrastructure, and job training.
  • Re: cost of IPv6 (Score:3, Informative)

    by Eunuchswear ( 210685 ) on Tuesday December 13, 2005 @05:49AM (#14245160) Journal
    I don't know what percentage of active switches do IPv6, but many of the older switches will start broadcasting the IPv6 because they don't understand it. Now your switch is a hub. That will choke any network that needed switches in the first place. Even a single switch that doesn't do IPv6 could take out a large chunk of your network.
    Huh? Switches don't do IP, they switch packets based on the MAC address. They'll work with IPv6 just like they did before.
  • ...damage of Hurricane Katrina wasn't so bad. After all, it will give us the "opportunity" to invest billions of dollars in rebuilding things.

    This is known as the "broken window fallacy" or Parable of the broken window [wikipedia.org].

The moon is made of green cheese. -- John Heywood

Working...