To quote myself from a post I made on another site:
According to IANA [iana.org], of the 256/8 IPv4 blocks, there are 31 Unallocated blocks and 16 Reserved for Future Use. Those 47 blocks means that approximately 18.36% of the IPv4 space is currently sitting empty. That's not even counting the the 16/8 blocks reserved for Multicast, the 127/8 block reserved for a single IP (127.0.0.1), or counting any unallocated blocks in the CIDR networks.
Anyone who says we're running out of IPv4 addresses needs to go back and look at what is actually allocated and what isn't. Since nearly 20% of the IPv4 space is currently empty, I can't see how they can make the claim that we're running out of addresses with a straight face.
Anyone who says we're running out of IPv4 addresses needs to go back and look at what is actually allocated and what isn't.
Done. Note that we've been averaging between 10 and 15/8 blocks assigned per year in total space, which using very simply math against a total of 31 means we have a short number of years. If you'd like to see the actual assignment numbers and some more advanced models, go here: http://www.potaroo.net/tools/ipv4/index.html [potaroo.net].
16 Reserved for Future Use. Those 47 blocks means that approximately 18.36% of the IPv4 space is currently sitting empty. That's not even counting the the 16/8 blocks reserved for Multicast, the 127/8 block reserved for a single IP (127.0.0.1).
Except that the reserved, multicast and loopback networks can't be used since many (most?) IPv4 stacks just plain won't support doing global scoped unicast on those addresses. If you're going to demand that the whole world upgrades their IPv4 stacks to support the reallocation of addresses that were never intended to be public unicast addresses, you may as well demand they upgrade to IPv6 instead.
Since nearly 20% of the IPv4 space is currently empty, I can't see how they can make the claim that we're running out of addresses with a straight face.
People can make the claim with a straight face because they have a clue what they are talking about - something
16 Reserved for Future Use. Those 47 blocks means that approximately 18.36% of the IPv4 space is currently sitting empty. That's not even counting the the 16/8 blocks reserved for Multicast, the 127/8 block reserved for a single IP (127.0.0.1).
Except that the reserved, multicast and loopback networks can't be used since many (most?) IPv4 stacks just plain won't support doing global scoped unicast on those addresses. If you're going to demand that the whole world upgrades their IPv4 stacks to support the re
I'll admit, I haven't checked the source code for any modern TCP/IP stacks, but I wouldn't be surprised if they support global unicast on any of the Reserved blocks past the Multicast range.
I suggest you check then, because you're dead wrong.
And that's ignoring all the misconfigured systems out there - not just end systems, but also routers and firewalls. After ECN was introduced it took many years before it was really feasible to use it over the internet because of the number of buggy routers that dropped any packet with the ECN flag set. And if you've ever had to pass traffic over a path with a lower MTU than either endpoint then you'll know just how many systems drop ICMP type 3.4 packets
Business is a good game -- lots of competition and minimum of rules.
You keep score with money.
-- Nolan Bushnell, founder of Atari
18+% of IPv4 addresses unused (Score:1, Troll)
To quote myself from a post I made on another site:
According to IANA [iana.org], of the 256 /8 IPv4 blocks, there are 31 Unallocated blocks and 16 Reserved for Future Use. Those 47 blocks means that approximately 18.36% of the IPv4 space is currently sitting empty. That's not even counting the the 16 /8 blocks reserved for Multicast, the 127/8 block reserved for a single IP (127.0.0.1), or counting any unallocated blocks in the CIDR networks.
Anyone who says we're running out of IPv4 addresses needs to go back and look at what is actually allocated and what isn't. Since nearly 20% of the IPv4 space is currently empty, I can't see how they can make the claim that we're running out of addresses with a straight face.
Re: (Score:1)
Anyone who says we're running out of IPv4 addresses needs to go back and look at what is actually allocated and what isn't.
Done. Note that we've been averaging between 10 and 15 /8 blocks assigned per year in total space, which using very simply math against a total of 31 means we have a short number of years. If you'd like to see the actual assignment numbers and some more advanced models, go here: http://www.potaroo.net/tools/ipv4/index.html [potaroo.net].
With respect to use of the 16 Reserved-for-Future-Use blocks, please review http://tools.ietf.org/html/draft-fuller-240space-02 [ietf.org]; it is not certain if this space will be made available f
Re: (Score:2)
16 Reserved for Future Use. Those 47 blocks means that approximately 18.36% of the IPv4 space is currently sitting empty. That's not even counting the the 16 /8 blocks reserved for Multicast, the 127/8 block reserved for a single IP (127.0.0.1).
Except that the reserved, multicast and loopback networks can't be used since many (most?) IPv4 stacks just plain won't support doing global scoped unicast on those addresses. If you're going to demand that the whole world upgrades their IPv4 stacks to support the reallocation of addresses that were never intended to be public unicast addresses, you may as well demand they upgrade to IPv6 instead.
Since nearly 20% of the IPv4 space is currently empty, I can't see how they can make the claim that we're running out of addresses with a straight face.
People can make the claim with a straight face because they have a clue what they are talking about - something
Re: (Score:2)
Re: (Score:2)
I'll admit, I haven't checked the source code for any modern TCP/IP stacks, but I wouldn't be surprised if they support global unicast on any of the Reserved blocks past the Multicast range.
I suggest you check then, because you're dead wrong.
And that's ignoring all the misconfigured systems out there - not just end systems, but also routers and firewalls. After ECN was introduced it took many years before it was really feasible to use it over the internet because of the number of buggy routers that dropped any packet with the ECN flag set. And if you've ever had to pass traffic over a path with a lower MTU than either endpoint then you'll know just how many systems drop ICMP type 3.4 packets