Slashdot Mirror
Free IPv4 Pool Now Down To Seven /8s
Zocalo writes "For those of you keeping score, ICANN just allocated another four /8 IPv4 blocks; 23/8 and 100/8 to ARIN, 5/8 and 37/8 to RIPE, leaving just seven /8s unassigned. In effect however, this means that there are now just two /8s available before the entire pool will be assigned due to an arrangement whereby the five Regional Internet Registries would each automatically receive one of the final five /8s once that threshold was met. The IPv4 Address Report counter at Potaroo.net is pending an update and still saying 96 days, but it's now starting to look doubtful that we're going to even make it to January."
http://en.wikipedia.org/wiki/IPv4_address_exhaustion
No kitty, this is my pot pie!
THE INTERWEBZ EXPLODZ!!! Ok no seriously, once ICANN allocates the final blocks the IPv4 space will be declared as "used up" but it is still up to the regional RIRs to *use* those IPs. ie if ICANN issues IPs they are not automatically used. Thus it will still be a while after that when they are really all used up. Even then we could maybe see a sharing of sub-blocks between regional RIRs (?) For example AfriNic will probably have quite a surplus if it receives another /8 range.
Lastly there are (not so preferable) technologies available such as NAT to allow the internet to continue functioning as it did (more or less).
In the end we will need to move to IPv6.
Here is a good blog post on why this wouldn't work: http://packetlife.net/blog/2010/oct/14/ipv4-exhaustion-what-about-class-e-addresses/
it is still up to the regional RIRs to *use* those IPs
Regional Internet Registry.
sic transit gloria mundi
status of comcast ip6 http://www.comcast6.net/ at&t - lagging http://www.networkworld.com/news/2010/102710-att-ipv6.html
3ffe:1900:4545:3:200:f8ff:fe21:67cf
That would be 63.254.25.0.69.69.0.3.2.0.248.255.254.33.103.207 using your scheme which is horrible. Is also leaves out the most useful compression feature, so you can write 3ffe:1900::/32 instead of 63.254.25.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0/32. Just counting out the correct numbers of .0 is horrible.
Practical real life IPv6 addresses often use compression: ipv6.l.google.com has IPv6 address 2a00:1450:8005::63, ipv6.myip.dk has IPv6 address 2001:470:27:f9::2, ipv6.net has IPv6 address 2a00:1188:5:2::8. If you care about your address you can make it short, since the last 64 bits is yours to decide.
Any iOS device with 4.0 or later supports IPv6, including your iPhone.
Actually it does support TLS, it just doesn't support SNI. Or actually IE and Safari only, because they use the windows library. Firefox and Chrome use the library first developed at Netscape and Opera uses OpenSSL.
But as SNI is the part that adds 'Namebased virtual hosts' to TLS, the result is the same as you mentioned. Everything that wants to use a certificate still needs it's own IPv4-address (and/or IPv6 address) for now.
New things are always on the horizon
Configure your home router to pass the port for whatever service you want to access from work to the system that can deal with it at home. Connect to that address using that port.
This is where the trouble begins. You can do this today because it is _your_ router doing the NAT. With no more IPv4 available, you will be sharing your IPv4 with your neighbours. This means carrier NAT. How do you program your ISPs router? You don't.
Privacy
a handful of selfish greedy people are no match for millions of selfish, greedy people -u4ya
Well, first of all, it sort of is. The typical way to get an address on an IPv6 network is stateless auto-configuration, which basically allows your client to combine an advertised route prefix with the EUI-64 (basically a longer version of a MAC address that can be generated from a MAC address) to determine its IP. You don't need any configuration for new clients and they always get the same IP address. Note that Windows Vista/7 use a hashing function with random data and the MAC address so that you can't track a single machine based on its IPv6 address, which solves privacy concerns.
Second, you can't just use the MAC address because it's not easy to route traffic that way. Routing works today because networks are assigned contiguous blocks of addresses, so it's easy to tell where to route traffic based on the address prefix. If we just had MAC addresses (which contain no information about which devices are connected to which networks), routing would require huge tables that would frequently change. This works OK for a small to medium sized network (e.g. switched Ethernet) but it doesn't work at all for the Internet. Even medium-large organizations need to use subnets to effectively manage traffic, which aren't possible without network prefixes.
What is the difference for IPv6 ?
Their currently is one IPv6-DNS-blocklist, they use something like: 5 bad IP's in one /64, block the whole /64, 5 bad /64 block the whole /48. Or some system like that.
Or do you mean their isn't enough tooling yet ?
New things are always on the horizon