Slashdot Mirror


Proposed IPv6 Cutover By 2011-01-01

IO ERROR writes "An internet-draft published this month calls for an IPv6 transition plan which would require all Internet-facing servers to have IPv6 connectivity on or before January 1, 2011. 'Engineer and author John Curran proposes that migration to IPv6 happen in three stages. The first stage, which would happen between now and the end of 2008, would be a preparatory stage in which organizations would start to run IPv6 servers, though these servers would not be considered by outside parties as production servers. The second stage, which would take place in 2009 and 2010, would require organizations to offer IPv6 for Internet-facing servers, which could be used as production servers by outside parties. Finally, in the third stage, starting in 2011, IPv6 must be in use by public-facing servers.' Then IPv4 can go away."

3 of 398 comments (clear)

  1. I am not trying to troll right now but... by techiemikey · · Score: 5, Insightful

    who is this guy and why does he control what happens with my internets?

  2. I think you're missing the point by frovingslosh · · Score: 5, Insightful
    It's not a question if the new spec should be that large (it should, but that's not the issue). It's if we need a new spec at all. If you acknowledge that we need a new spec, IPv6 seems to be it. And it would be absurd to come up with some short sighted spec with smaller addresses just to get caught with limits again.

    Also, don't fall into the all too common trap of looking at how large 2 to 128 is and thinking that ipv6 really provides that many unique addresses. You have to look at how the bits are used, the number of useable Internet addressable devices is much smaller. Perhaps even around the size you may be thinking we need. A new addressing system can provide some nice new features. Imagine the benifit of having a portable IP addres that is yours no matter what network you connect to or where in the world you move. Kind of like having a real truly portable telephone number. As all communication merges into IP address this will be both handy and important.

    None of this should be taken to imply that I support the absurd cut over schedule in this thread. But there are some nice things designed in ipv6 and it will be a positive thing if the convesrion is done right, not switched over in a mad rush.

    --
    I'm an American. I love this country and the freedoms that we used to have.
  3. Re:not ready for prime time by Doctor+Memory · · Score: 5, Insightful

    Except for the N-word being used, this post is very informative Excuse me? "IPv6 needs work because Cisco routers don't handle it well"? It's just a troll, get over it. Cisco's probably wringing their hands with glee, because this will help them push their next-generation made-for-IPv6 routers. And if they don't have a next-generation router that handles IPv6 well, then Juniper will (deservedly) eat their lunch.

    The rest of the points in that post were similarly bogus. NAT sucks because it breaks the end-to-end IP model (which also breaks IPSec). It also requires the network to handle connections and maintain state. IPv6 also uses multicast for ARP resolution instead of broadcast, which means your NIC doesn't have to deal with a packet every time someone else on your subnet wants to contact a machine that isn't in their cache.
    --
    Just junk food for thought...