The World is going to run out of IPs in 768 days

[DNR]

This is a thread currently running in slashdot.
http://tech.slashdot.org/article.pl?sid ... 24/1254235

Posted by CmdrTaco on Wednesday September 24, @09:23AM
from the blame-canada dept.
JagsLive writes
"China is running out of IP addresses unless it makes the switch to IPv6. According to the China Internet Network Information Center, under the current allocation speed, China's IPv4 address resources can only meet the demand of 830 more days and if no proper measures are taken by then, new Chinese netizens will not be able to gain normal access to the Internet. Li Kai, director in charge of the IP business for CNNIC's international department, says that if a netizen wants to get access to the Internet, an IP address will be necessary to analyze the domain name and view the pages. At present, most of the networks in China use IPv4 addresses. As a basic resource for the Internet, the IPv4 addresses are limited and 80% of the final allocation IP addresses have been used."

In the comments someone said this about the world IP:

Try the whole world. According to this counter [entne.jp], the world will be out of IPv4 addresses in 768 days.

http://entne.jp/tool/toollist/index_en.html

IPv6

http://www.enterprisenetworkingplanet.c ... hp/3633211
Address Dissection
Let's take another look at our example IPv6 address:

20013c4d0000:0000ef12
______________|____|___________________
global prefix subnet Interface ID

The prefix identifies it as a global unicast address. It has three parts: the network identifier, the subnet, and the interface identifier.

The global routing prefix comes from a pool assigned to you, either by direct assignment from a Regional Internet Registry like APNIC, ARIN, or RIPE NCC, or more likely from your Internet service provider. The subnet and interface IDs are controlled by you, the hardworking local network administrator.

You'll probably be running mixed IPv6/IPv4 networks for some time. IPv6 addresses must total 128 bits. IPv4 addresses are represented like this:

0000:0000:0000:0000:0000:0000:192.168.1.25

Eight blocks of 16 bits each are required in an IPv6 address. The IPv4 address occupies 32 bits, so that is why there are only seven colon-delimited blocks.

The localhost address is 0000:0000:0000:0000:0000:0000:0000:0001.

Naturally we want shortcuts, because these are long and all those zeroes are just dumb-looking. Leading zeroes can be omitted, and contiguous blocks of zeroes can be omitted entirely, so we end up with these:

20013c4d0:0ef12
20013c4def12
::192.168.1.25
::1

I usually end up counting on my fingers, which is probably not the best method. ipv6calc is invaluable for checking your work. Suppose you're not sure if your compressed notation is correct. ipv6calc displays the uncompressed notation:

$ ipv6calc --in ipv6addr --out ipv6addr --printuncompressed ::1
0:0:0:0:0:0:0:1
$ ipv6calc --in ipv6addr --out ipv6addr --printfulluncompressed 20013c4def12
20013c4d0000:0000ef12

Next week we'll get to the fun part: setting up a local IPv6 network, connecting to a public IPv6 network and learning how to calculate and assign IPv6 addresses.

Resources


IPv6: Facts and Fiction

Current Status of IPv6 Support for Networking Applications

APNIC Root Server Trial FAQ

Linux IPv6 Howto

Address Dissection
Let's take another look at our example IPv6 address:

20013c4d0000:0000ef12
______________|____|___________________
global prefix subnet Interface ID

The prefix identifies it as a global unicast address. It has three parts: the network identifier, the subnet, and the interface identifier.

The global routing prefix comes from a pool assigned to you, either by direct assignment from a Regional Internet Registry like APNIC, ARIN, or RIPE NCC, or more likely from your Internet service provider. The subnet and interface IDs are controlled by you, the hardworking local network administrator.

You'll probably be running mixed IPv6/IPv4 networks for some time. IPv6 addresses must total 128 bits. IPv4 addresses are represented like this:

0000:0000:0000:0000:0000:0000:192.168.1.25

Eight blocks of 16 bits each are required in an IPv6 address. The IPv4 address occupies 32 bits, so that is why there are only seven colon-delimited blocks.

The localhost address is 0000:0000:0000:0000:0000:0000:0000:0001.

Naturally we want shortcuts, because these are long and all those zeroes are just dumb-looking. Leading zeroes can be omitted, and contiguous blocks of zeroes can be omitted entirely, so we end up with these:

20013c4d0:0ef12
20013c4def12
::192.168.1.25
::1

I usually end up counting on my fingers, which is probably not the best method. ipv6calc is invaluable for checking your work. Suppose you're not sure if your compressed notation is correct. ipv6calc displays the uncompressed notation:

$ ipv6calc --in ipv6addr --out ipv6addr --printuncompressed ::1
0:0:0:0:0:0:0:1
$ ipv6calc --in ipv6addr --out ipv6addr --printfulluncompressed 20013c4def12
20013c4d0000:0000ef12

Resources

Current Status of IPv6 Support for Networking Applications
http://www.deepspace6.net/docs/ipv6_sta ... _apps.html

APNIC Root Server Trial FAQ
http://www.apnic.net/info/faq/rootserver-faq.html

Linux IPv6 Howto
http://www.bieringer.de/linux/IPv6/

DNR

[bad_brain]

from what I have heard it might become a problem to get low amounts of IPv6 IPs from the RIRs (regional internet registries), they will most likely give them away only in packs of hundreds or even thousands because there will be such a huge amount available. ok, this is not affecting end-users, but little hosting companies might get into financial problems (or have to buy smaller amounts from resellers).

but well, it's still a long way to IPv6 anyway, the support for IPv6 addresses is still more than bad (ask mab, he had real "fun times" with IPv6 already)....maybe the problem will still be underestimated and we can look forward to some nice chaos soon...

[Still_Learning]

I've got a couple prime top level domains , should i prepay for the next 10 years while its still is 10$ a year or do you think the price will not change for yearly renewel prices? I have heard of some compansy chargeing like 25$ a year for a .com domain

[bad_brain]

domains have nothing to do with IPv4 or IPv6.....IPv6 IPs can be used for everything IPv4 ones can be used to too. so domain resellers can't say "oh, no more IPv4 IPs left, we increase the prices!".....
how much money is charged for a domain depends only on the company, if you pay 10 bucks/year now it's not likely they will increase the fee to 25 bucks, their customers would tell them to f*ck off. and even if they would do you can still move your domain to another registrar....all big registrars do this even for free....

[TheKingOfHearts]

this was brought up by my teacher too.

i said why not add more numbers?

he told me that all of it works only for this protocol.

im actually really curious of what will happen then.

would IP's be like buying a gold ring...

[Big-E]

im actually really curious of what will happen then..

Lets just say subnets will be more important than ever. Subnetting over WAN..hmm, wonder how that would work.

[tch0rt]

subnets are a minefield as it is if some fool doesnt give you the right details (I HATE SUBNETS ARRRGGGG)
subnet over WAN sounds like 1 big headache Im quiting IT and becoming a pr0nstar
loads of benifits and I dont have to say "is it turned on, check the plug" then think "you retard how did you expect it to work unplugged"

[DNR]

Remember, when subnetting runs out, then its on to IPv6, and devices that use both IPv4 and IPv6 protocol. Check out the tools for cross IPv commo:

NAT-PT (Network Address Translation - Protocol Translation) is an IETF RFC specification for an IPv4 to IPv6 protocol translator. This is a NAT-PT implementation for the Linux platform designed to run in userspace.
-
46Bouncer is a very simple tool that is able to accept TCP/UDP connections in IPv4/6 and forward them to an application in IPv6/4. In other words, it acts as a proxy between the IPv4 and IPv6 world (and vice versa).

DNR

[Big-E]

IPv6 addresses are just too hard to remember, I can remember an IPv4 address just fine..toss in too many variables. Ekk. I am not looking forward to IPv6..I will probably work with it every single day soon enough.