My company just got it's ipv6 allocation. They gave us a /32. Let's walk through this math for those of you watching from home.
/32 is the number of bits. The full length of an ipv6 address is 128 bits. Represented in binary, this means that the highest possible number is all 1's, for a total of 128 of them:
To convert this number into decimal, you start way over at the right, and continuously increment by the powers of 2. The first position is 1, the second is 2, the third is four, the fifth is 8, the sixth is 16, the seventh is 32, and so on and so forth. If you bother to follow those powers of two all the way out to 128 bits, you end up with a really big number. 170,141,183,460,469,000,000,000,000,000,000,000,000 to be exact. This is the maximum number of ip addresses able to be assigned out of the ipv6 pool.
Our allocation of a /32 means that, starting from the left, you count out 32 binary bit positions and flip them to a 1, and the remaining 96 binary positions are all 0. This gives us a total allocation of 79,228,162,514,264,300,000,000,000,000 ip address. If you were to write me a check giving me a dollar for every one of our ip addresses, you'd need a check that was about 3 feet wide so that you could write out the number in english. You'd be writing me a check for seventy-nine octillion, two hundred twenty-eight septillion, one hundred sixty-two sextillion, five hundred fourteen quintillion, two hundred sixty-four quadrillion, three hundred trillion dollars.
So, my company has personally been given enough ipv6 addresses to assign every single cell in your body well over 1 quadrillion ip addresses. Every. Single. Cell.
From what I've been hearing, this is the norm. They gave one guy a /48 for his websites, of which he has a small handful. One septillion ip addresses. For a few websites.
Let's extrapolate that our /32 is the norm for anyone needing more than a handful of ip addresses. Divide the biggest possible 128 bit number by our /32 allocation.
That's the kind of number you don't need any help spelling out. A little better than 2 billion. How many ipv4 addresses are there? Double that. 4 billion, though the way ipv4 has been carved up means that substantially less than that is usable.
It took us 30 years to approach exhaustion of the ipv4 space, though the last 15 years has seen such an exponential increase, the first 15 years is nothing but a drop in a bit-bucket in comparison.
I've argued repeatedly that there's so much ipv4 space that is absolutely WASTED that there really isn't that much of a crunch if they started enforcing utilization standards. MIT, for example, has 16 million public ipv4 addresses of their very own. Why? Because, when it was allocated to them so many years ago, they could get away with it. 16 million. For a college. Do they need 16 million publicly facing ip addresses? NO.
And, of course, there's no place like 127.0.0.1 is there? Another 16 MILLION ip addresses wasted on localhost. Why? Because back when it was assigned, they could. Who cares, right? When there's 4 billion addresses, what's 16 million here or there, just between friends?
Xerox, 16 million. HP, 16 million. Ford, 16 million. Halliburton, 16 million. Prudential, 16 million. Merck, 16 million.
Do any of these companies need 16 million publicly facing ipv4 addresses? NO. That's over 83 million ip addresses wasted right there. Yes, HP recently purchased a company that produced cell phones. Do those cell phones need PUBLIC ipv4 addresses? NO. The specifics of the wastefulness of the ipv4 space are a separate rant, though.
My point is that this pattern of wastefulness is not only continuing with ipv6, it's getting much, much WORSE. Insanely sized allocations to anyone who asks for a few ips? Really? What good is having this seemingly vast amount of address space, if (going back to the handful of websites example) the wastefulness of this space increases by not 1 or 2 or 10, but TWENTY-FIVE orders of magnitude?
The view from this boat looks a lot like it did 30 years ago.
Post a Comment