One Step Closer to IPv6 281
gbjbaanb writes "IPv6 came a step closer yesterday as ICANN added IPv6 host records to the root DNS servers, reports the BBC. 'Paul Twomey, president of Icann which oversees the addressing system, told the BBC News website there was a need to start moving to IPv6. "There's pressure for people to make the conversion to IPv6," he said. "We're pushing this as a major issue." The reason for the urgency, he said, was because the unallocated addresses from the total of 4,294,967,296 possible with IPv4 was rapidly running out. "We're down to 14% of the unallocated addresses out of the whole pool for version 4," he said. Projections suggest that this unallocated pool will run out by 2011 at the latest.'"
Just Like Oil (Score:5, Insightful)
Re:Just Like Oil (Score:3, Insightful)
Re:Just Like Oil (Score:3, Insightful)
Re:Sad (Score:3, Insightful)
Also, without IPv6, there's only a maximum of 2^32 Linksys routers that will be needed. IPv4 is unfairly capping the maximum number of needed NAT routers, and thus unfairly capping the profits of Cisco. We must think of the cost of IPv4 in terms of corporate profits, or we are doomed. Our economy depends on exponential growth, and that applies to addresses on the Internets too.
IPV6, a lame solution for no problem (Score:2, Insightful)
Forcing v6 will be a disaster. It's better to force people to better implement v4 and take that time to design a system that will expand the address space while not causing so many issues.
This will be anonymous coward because I know almost everyone on
Re:Just Like Oil (Score:3, Insightful)
Re:2011 (Score:3, Insightful)
If google, microsoft, redhat, CNN and the BBC (insert favourite site here) all go ipv6 (and by that I mean google starts indexing it too), that will be the year of ipv6. No way in hell it's going to happen before that.. I know of exactly zero useful ipv6 websites - I'm connected here but it's never been used.
Without any websites to actually *visit* on ipv6 ordinary users aren't going to go through the hassle, so ISPs see no demand and won't implement it (even though it would be a nice revenue stream for them - $10/month for 256 ipv6 addresses for example (and I really can't see them giving any more, seriously.. It's more likely to be 8 or 16 to separate the 'home' ($10/mo) users from the 'business' ($50/mo) users who get 256)).
Of course without any home routers that support it it's all moot anyway (hacked linkysys routers don't count).
Re:I don't expect much to change (Score:5, Insightful)
If a user wants a public IP. That's more cost. If they want a *fixed* IP.. go talk to the business services manager over there.
If they do implement ipv6 it'll be done the same way. 1 ipv6 address per account (ipv6 NAT exists and has done for a while). If you want 8 of them that's more cost. If you want more than 256.. see that guy in a suit waving? Go hand him your chequebook.
And before anyone says 'but but we'll all get 16 million addresses!'.. yeah, over the rotting corpses of every major ISP in the world.
It's a sham - the Internet is mostly dark (Score:2, Insightful)
Try it yourself - hack up some script to randomly generate IPs and then ping sweep the network blocks. You'll probably be quite surprised at the result.
A while back, I wanted to have a way to detect if a host was "offline" so that it could modify its behavior. (EG: halt outgoing SOAP requests if the server's network connection was disrupted, preventing bogus error messages from entering the system)
My first thought was to randomly generate 10 IP addresses, then ping them to see if they were offline, guessing that at least 50% would respond. Basically, none did. So, then I tried randomizing addresses and keeping a list of only those that had, at one time, responded. Even that turned out to be unfruitful. So finally, I took a dictionary and randomly created domain names from 1-2 normal dictionary words, pinging those, and keeping a list. That yielded some 40% usable responses, allowing me to keep a list of fairly trustworthy ping hosts to determine the online status of the server in question.
Bottom line: The shortage in the global IP pool is an artifact brought on by grossly inefficient/incompetent management of the global IP pool. The idea that we're running out of addresses purely ignores the fact that the vast, vast majority of the addresses we now have are simply unused.
IP6 won't matter til Google supports it (Score:5, Insightful)
That means that I can do a DNS query using nothing but IP6 packets - NOT IP4 packets.
That means that I can do an HTTP transfer from Google's servers using nothing but IP6 packets - NOT IP4 packets.
Hell, wake me up when there's a AAAA record for Slashdot.
This is a *baby* step towards IP6 being useful.
Re:Just Like Oil (Score:3, Insightful)
Re:It's a sham - the Internet is mostly dark (Score:2, Insightful)
Most large server farms block ICMP/ping at the border. Relying on ping to indicate whether an IP is occupied is just wrong.
Granted, I'm with you on the "large empty pool" theory.
Re:Just Like Oil (Score:4, Insightful)
It would be nice to have a perfectly efficient method of coercion to force ISP's to actually spend their subsidies on broadband penetration, but no one in power seems to be interested. It's the same story as IPv6 up to now. ICANN seems to be taking the lead finally. Hopefully someone will follow suit in the broadband arena.
Re:IP6 won't matter til Google supports it (Score:4, Insightful)
Now Google can register an AAAA record, do you think they will? If they couldn't register one, do you think they would?
Re:It's a sham - the Internet is mostly dark (Score:5, Insightful)
The sad part is, most of the IP addresses in question are... dark. Nothing there. Even though we're approaching 85% allocation, utilization is probably around 1-2%. No, I'm not kidding.
And you have ANY hard data to back that up ? No. Others are trying to come up with better metrics (http://www.potaroo.net/tools/ipv4/index.html is exceptionally verbose), but you ? You are not kidding about thinking that it maybe probably is around 1-2% ... Wow.
Try it yourself - hack up some script to randomly generate IPs and then ping sweep the network blocks. You'll probably be quite surprised at the result.
Bzzzt. No, I would not be -- nor should anybody be. First of all, it's not a requirement for every address to be routable to (and you can check that much better by looking at what percentage of prefixes are actually advertized). Second, many, MANY hosts and networks are behind firewalls, intrusion detection & response systems, etc. -- a "simple pingscan" can easily land you in a black hole at the network border after a couple of pings -- if access to those machines is even allowed from your network. Sure, in consumer broadband connections you don't often have such firewalls restricting inbound access, but that's not the "entire internet". Hell, go ping amazon.com and see what you get back. Nada, that's what.
A while back, I wanted to have a way to detect if a host was "offline" so that it could modify its behavior. (EG: halt outgoing SOAP requests if the server's network connection was disrupted, preventing bogus error messages from entering the system)
A problem many others have faced and solved before you.
My first thought was to randomly generate 10 IP addresses, then ping them to see if they were offline, guessing that at least 50% would respond.
Accounting for the different classes of addresses, unroutable space, bogons, etc. in that random calculation would be more work than the result is worth, especially seeing as how the state of netblocks can change over time. I wonder, why was your first thought to crap out (at least) 10 packets to the net that really are not needed ? What possible reason could there be for you to automatically ping a cellphone in Singapore ? Just imagine everybody doing this, just to check whether they are "online" ...
How about choosing some well-known addresses (such as one of your own servers in a different locale, or possibly "well-known" servers that you know will respond and that don't mind a ping from you every now and then ... Not only do you get a 100% response rate when everything is working correctly, you also forego abusing bandwidth in remote locales you are not at all interested in.
Basically, none did. So, then I tried randomizing addresses and keeping a list of only those that had, at one time, responded. Even that turned out to be unfruitful.
You know, while still a bit dickish, it might have occured to you that most of {a-m}.root-servers.net do reply to ping or DNS requests. So do, in all likelihood, a router in your upstream, or DNS resolvers you know about. Instead, you now latch on to addresses that respond. The cellphone in Singapore, for instance.
So finally, I took a dictionary and randomly created domain names from 1-2 normal dictionary words, pinging those, and keeping a list.
Ah. So now that flooding ICMP out to the net is not enough, you have to litter it with bogus DNS requests the reply to which you are not really interested in. Again, imagine EVERYBODY doing this. Why not pick 10 known domain names and always ping those ? At least the results will be cached, and you may even choose ones whose owners you know and can ask whether they mind to be flooded with icmp every now and then.
That yielded some 40% usable responses, allowing me to keep a list of fairly
Re:Just Like Oil (Score:4, Insightful)
We are not addicted to oil just because we are lazy. We are addicted to oil because it is so god-damn good. We will be badly screwed if it runs out, and no amount of innovation will bring such a wonderfully convenient energy source back. In comparison, and, come to think of it, not even in comparison, IP6 is a complete and total triviality.
Re:IBM may actually use a lot of 9 (Score:3, Insightful)
Re:Just Like Oil (Score:3, Insightful)
6to4 is pretty similar to configured tunnels, but it structures its IPv6 addresses in such a way that each endpoint can automatically discover the IPv4 address of the other endpoint. Thus 6to4 requires no configuration or state in the network.
Re:Just Like Oil (Score:2, Insightful)
And yeah, the chorus of people screaming about how IPv4 isn't going to run out sound a whole lot like the people who think we have limitless oil -- and perhaps we do, but in both cases, it's going to be damned expensive to retrieve and distribute.
Re:It's a sham - the Internet is mostly dark (Score:3, Insightful)
Re:Sad (Score:5, Insightful)
http://www.arin.net/registration/guidelines/ipv6_initial_alloc.html [arin.net]
Re:You are right (Score:2, Insightful)
Re:Oh Noes The Internets! (Score:3, Insightful)
Re:Sad (Score:3, Insightful)
Have you not paid your 2008 ARIN fees?
Are you not an ISP?
You can't come up with the US$35 for a
How is ARIN blocking you in any way?
Are you just trolling
I don't understand your complaint. If you already have an IPv4 allocation from ARIN, getting an IPv6 allocation requires only filling out the form, sending it in, and getting your allocation. They stick the $35 onto your ARIN fee at the next billing cycle. It's even easier than getting an IPv4 allocation now.
the AC