Slashdot Mirror


IPv6 Rollout Japan, China in 2005

Killjoy_NL writes "The digitimes have a piece that is reporting that IPv6 will be rolled out in China and Japan in 2005. Makes me wonder when the rest of the world will follow suit" We had a good piece a couple months back about the state of IPv6. CowboyNeal is ready!

8 of 191 comments (clear)

  1. China? by Exiler · · Score: 5, Funny

    An IP address for every chinese citizen? Time to start working on IPv8!

    (-1, I Like Chinese)

    --
    Banaaaana!
    1. Re:China? by fyonn · · Score: 5, Insightful

      340282366920938463463374607431768211456 is an awfully big number. Its over a quadrillion times the number of square millimeters on the surface of this planet!

      it is a big number, but remember that ipv6 address space is very sparse in the 128bit address sense. as each customer is likely to receive a /48 network that makes the first 48 bits very dense in usage, but after that, it'll be almost empty.

      in reality the address space that can be assigned is a /48. the 96 bits after that are for the customer to use themselevs. /16 for their own subnets and 64 bits for host portion of the ip address. so thats 281474976710656 assignments. still alot mind you but ipv6 isn't effectively as big as most people claim.

      dave

  2. Slashdot IPv6 by FrostedWheat · · Score: 5, Funny

    CowboyNeal is ready!

    Yea, but is Slashdot?

    Seems the idea site to have support for IPv6. Last time I checked (late last year) Slashdot didn't do IPv6.

    Heck, they still use GIFs...

    1. Re:Slashdot IPv6 by Joe+U · · Score: 5, Informative

      Last time I checked (late last year) Slashdot didn't do IPv6

      Last time I checked, Slashdot didn't do valid HTML either.

  3. Oh, wonderful. by joeszilagyi · · Score: 5, Funny

    Another 945,478,233,526,156 IP addresses I need to blacklist from spamming me.

    --
    Dude, where's my packet?
  4. Other Countries slow to follow by pholower · · Score: 5, Insightful

    Japan also rolled out 3G wireless before everyone else. Have we incorporated as much as Japan? No. Japan has always been ahead of the curve for this type of stuff. But only because they don't have all of the infrastructure flaws other countries do. Besides, how weird would it be to type ::1 instead of 127.0.0.1?

    --
    -- johntracy.com, because everybody else is wrong.
  5. Re:IPv6: Not Ready For Prime Time by Anonymous Coward · · Score: 5, Insightful

    Hopefully you don't plan on your "disseration" being respected.

    1. That is not a problem with the protocol. It is a problem with the hardware, which Cisco CAN fix in future revs.

    2. VOIP. If every person on earth gets a VOIP cell phone in the future, you have now run out of addresses. And that doesn't even take into account non-consumer addresses, such as slashdot.org. NAT won't solve the problem, as VOIP isn't directly compatable with it. Are you now going to require that all these NAT gateways now be transparent proxies for protocols which are rather complex? Also, how would the transparent proxy handle encryption?

    3. Routing tables don't list every network. Yes, there are 64 bits for networks/routing. These won't all be used immediately. They are there for the future. Given that in the past 20 years, the the amount of RAM you can get for a given price point has gone up by ~2000 times, by the time we need routing tables that have entries for all possibly networks the RAM will be cheap enough (and fast enough) to handle it.

    4. Bandwidth is increasing When IPv4 was created, the expected speed of a connection for a HIGH END user (university) was ~64kb/sec. That is no longer true, as the same class of user would now be expected to have at least an OC12.

    It sounds like you are trying to build a new highway that will last for 20 years, but you want to only plan on the current capacity requirements, not what will be needed in 20 (or even 10) years.

  6. Re:Like the Metric System by ch-chuck · · Score: 5, Funny

    My router gets 4 octets per address and that's the way I like it!

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }