Less Than 1 Year Until The Internet Runs Out of Addresses
readwriteweb.com
readwriteweb.com
The train has already left the station on NAT; end-users (and components in the "internet of things") expect transient addresses, and large-scale apps are designed so that rendezvous points are the only things that need fixed addressing.
Meanwhile, we'll eventually hit a point of scarcity with IPv4 addresses where allocations will stop being political and become market-driven instead.
Finally, all talk about a shangri-la of direct v6 addressing ignores the fact that no matter how quickly ISPs adopt the protocols, and even after the majority of Internet software that end-users demand are ported to handle v6 addressing, BGP routing still isn't going to scale to individual direct addresses. What's the current situation on prefix filtering at the major ISPs? How easy is it to get a /24 (even) portable?
http://www.circleid.com/posts/20090609_verizon_mandates_ipv6...
"The device shall support IPv6. The device may support IPv4"
This is requirements for the LTE devices from Verizon. Of course all the devices being linux-based, I expect dualstack for quite some time.
As for provider-independent addresses, I understand you should be able to get /48: http://www.ripe.net/ripe/docs/ripe-483.html
As for the Locator-ID split problem (which what the BGP scaling problem is about), there are a number of experiments going on at the moment. LISP (http://tools.ietf.org/html/draft-farinacci-lisp) is one of them. There was a few more but with less memorable names (edit: memorable for me. because I did hear more about LISP)
Of course the world is not going to end. It will just start developing an ever increasing slice of IPv6-only, whereas IPv4 growth is bounded.
Google, Facebook, YouTube, Netflix are already IPv6-enabled. This is "The Internet" for your average mom and pop consumer type. And maintaining the NATs with the few million hosts behind is a bit of work. So I would not be surprised if a cheaper "IPv6-only internet" options might emerge.
Full disclosure: my day job is at cisco. And untangling the creative NAT configurations and bugs caused by them has paid my bills for the past 10 years. Everything posted here is my personal opinion and not of my employer.
"The device SHALL support IPv6. The device MAY support the Internet."
Pure grandstanding.
This is also a Windows problem believe it or not.
Class E block has 268 million addresses but no existing version of Windows will see/talk to them.
If Windows can't talk to those IP addresses they're actually within spec. Though it is a useless waste of a lot of bits.
http://support.microsoft.com/default.aspx?scid=kb;en-us;2815...
A lot of ISPs already have policies for not having daemons on ports, so they could use that as justification for not having your own IP completely accessible from every port (which I don't believe would be possible without explicit port forwarding from the ISP itself).
What would this mean for end users' internet? Not much, but IPv4 IPs would be shared by multiple users (hopefully not many at first). A lot of websites have session policies and all sorts of mess based on the remote address, so it will be interesting to see how the aging webapps deal with the change.
I figure servers will get first priority at v4 addresses. Yeah, there's useless crap going on like IRC vhosts, but I figure once the market closes in on the addresses people will likely sell them (hell, I know people squatting on address blocks until the 'apocalypse', thinking they'll score a huge profit!).
Fun times.
For a major part of the users "The Internet" == "The Web", and applications like Skype use any available transport including avian carriers, this limits the impact.
But does having NAT increase the code complexity and increase the maintenance cost ? It does.
So, I would treat it as a short-term high-interest loan. If you do not have other choice - sure, go for it. But if you can avoid it - you will avoid a couple of gray hairs too.
http://article.gmane.org/gmane.org.arin.ppml/8304
Plus, both internet connections at my workplace gave us 6 IPs without us even asking for them.
As for hte reasons "WHY" - it was never supposed to be a judgement as to relative value - only that they were actually needed and going to be used. IP addresses were never meant to have value in the first place.
* We already have our /48 bought & deployed in production.
There might be a business in there setting up a clearing house for IP addresses.