Earlier quoted context omitted.
Obligatory: http://xkcd.com/195/ Edit: I wish there was an updated version.
What is that way of ordering numbers called? If I knew the name I could google it but that's what I'm missing.
[deleted]
Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
41–50 of 111 posts
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#42There are unallocated /8's that are privately routed. A lot are controlled by the U.S. DoD. But every time they come up, the response is always "so what? use IPv6!" I generally agree. Putting those in circulation would actually be a bad thing. It would allow IPv4 to continue to zombie-walk for another couple years, maybe another decade, and in so doing to become more deeply entrenched, harming us in the long-run. IPv…
> It really, really pains me that so many cloud providers are taking so damn long to support IPv6. Does Amazon even support it yet? I don't work at Amazon, but I spoke with someone about this recently, and I believe the issue is that Amazon provides virtual hardware and a virtual networking stack, and the tooling required to virtualize the networking stack in IPv6 isn't mature enough yet. For providers that offer ded…
KimeraLive.com supports IPv6 since 2012, we have more than a few private data-base servers that have IPv6 only access.
Cloud providers are not the problem, Internet Service Providers are, at home I'm stuck with IPv4 still.
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#43Earlier quoted context omitted.
The cloud provider problem is definitely real. I have an idea for a service that requires both IPv4 and IPv6, but Linode and Rackspace were the two I found that both support native IPv6. Otherwise, it's something involving a HE.net tunnel, which I'm not comfortable with for more than experimental use.
A note on Rackspace: we see about 2–3% of the VMs we allocate come with only an IPv4 address. We have no idea why — we suspect it's a bug on Rackspace's side (we allocate everything automatically, through the same code path, so it isn't us!). We currently only use the IPv4 address (I know, I know!), but it does present a bit of a problem when/if we decide to move.
Rackspace also doesn't support IPv6 if you use RackConnect, which is a bummer.
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#44Peak ipv4!
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#45I've seen headlines like this for literally 5 years at least. "IANA finally out of IPv4 addresses", "IANA allocates last X block", etc. When will it finally be impossible to buy an IPv4 address?
It becomes more and more impossible every day. Last time I tried to acquire a new IPv4, the distributor (my VPS host) required a technical reason for the request. If the request wasn't up to par, you would be denied an IPv4 + given an IPv6.
15 years ago I had to fill out an IP justification form - the justification was I had multiple SSL sites that all needed separate IP addresses. Wasn't a big deal, but was told it was standard practice (it was a smaller server center). And then I've had other dedicated server companies give me a block of 8 (5 usable) as just part of the monthly price.
What seems so wasteful is the "3 unusable" out of the 8 that are allocated. I have a vague understanding that those 3 are used for some routing/addressing stuff internally, but it's always felt incredibly wasteful.
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#46Earlier quoted context omitted.
Ford has as much reason as anyone else to need a block. Consider subcontractors needing to connect to servers in a particular department.
Ford has an entire /8, a significant chunk of the entire address space. Ford does not have as much reason to need that much address space compared to, say, major ISPs.
I would argue that Ford (and the other multinationals) have more need of an /8 than any university that is just in a single city.
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#47It would be nice if certain websites we all use every day supported v6 better...
firstmillion:~▻ host -t AAAA news.ycombinator.com
news.ycombinator.com has no AAAA record
firstmillion:~▻ host -t AAAA twitter.com
twitter.com has no AAAA record
firstmillion:~▻ host -t AAAA cloud-images.ubuntu.com
cloud-images.ubuntu.com has no AAAA record
firstmillion:~▻ host -t AAAA ubuntu.com
ubuntu.com has no AAAA record
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#48Easy problem to solve, so many entire /8 blocks are owned by single corporations, which should either be forced to sell or give up this outdated privilege. Does Xerox really need all of 13.x.x.x? Or Ford Motor Company all of 19.x.x.x?
http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_addres...
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#49Easy problem to solve, so many entire /8 blocks are owned by single corporations, which should either be forced to sell or give up this outdated privilege. Does Xerox really need all of 13.x.x.x? Or Ford Motor Company all of 19.x.x.x? http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_addres...
[deleted]
Re: Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
#50So there is a lot of sentiment that I've been hearing over time about when exactly will IPv6 become a thing. Here's how I see it:
Step -1: We started running out of IPv4 addresses. The internet is IPv4-only for all practical purposes. Nobody is doing IPv6 because it's still experimental. Your weird neck-bearded friends are talking about it, that's about it.
Step 0: Inception! IPv6 is now a standard and you can route IPv6 over the tubes. Two networks have connected!
Step 1: Dual stack is a thing. Now you can set up both IPv4 and IPv6 on the same network and they co-exist. Some hosts (goole.com, facebook.com) try this and finally turn it on for good in 2012.
Step 2: Dual stack intensifies. This is where we are now. You cannot yet run a full blown IPv6-only network that you want to talk to the Internet and do anything practical with it, but all your cleanly shaven friends are now telling you that you should support IPv6 first, then add IPv4 for compatibility. Google sees as much as 3.5% of their traffic over IPv6.
Step 3: The cost of any single IPv4 address rises dramatically. For an end user it's already roughly $1/month. Buying in bulk is much cheaper, but not free like it used to be. ISP's and other service providers (Amazon, Rackspace, Digital Ocean) are going to start noticing the costs on their bottom lines. Severe restrictions are imposed by IPS's and service providers on anything but the bare minimum of IPv4 usage.
Step 4: The future. The first IPv6-only networks start to pop up. They use special network translation to talk to IPv4-only internet. (You can do this at home now! It's called NAT64: http://www.litech.org/tayga/).
Step 5. The number of IPv6-only networks is growing rapidly. IPv4 is now a legacy protocol. All your friends are telling you that they cannot believe we are still using IPv4 and how much of a pain it is to support it. Sales of T-shirts with "There is no place like 127.0.0.1" drop dramatically.
Step 6. The same people that put together IPv6 World Launch Day put together an IPv4 funeral. Major companies turn off IPv4 presence.
The crucial point here is not that someone demands IPv6 by calling their ISP, etc. It is fun to play with and you should at least get a tunnel set up through Hurricane Electric if you are reading this, but the demand here does not matter. What matters is supply: supply of IPv4 that is. Once that goes to nil, the cost rises and some executive at every ISP and service provider has a bright idea to save the company millions by switching everyone to IPv6. That's it. We, the people in the trenches, cannot affect this. We cannot speed it up and we cannot slow it down. The invisible hand of the market will make IPv6 happen all on its own.