An improved version of the online tool is now available. The new version 1.05 is still in beta but should work pretty good.
The major new features are:
- Complete rewrite of the underlying engine. The new engine is easier to add features to.
- Better organized output that also outputs the different pools.
- Better organized form for input.
- Ability to specify if the E-blocks are usable or not.
- More options for number of months of demand that should be used when calculating the low threshold for when the RIR should allocates. Now the user can select from either 3,4,6,9 months.
- Better algorithm for when the RIR requests more space from IANA. The previous version was to aggressive under certain circumstances.
Please submit comments or suggestions.
The wireless operators in US seem to continue to grow their networks. Verizon wireless allocated a /10 or about 4 million addresses in December 2008. Yesterday, it was Sprints turn. Sprint allocated 126.96.36.199 – 188.8.131.52 (1 x /12, 1 x /14 and 1 x /15) totaling about 1.5 Million addresses.
Some interesting statistics about the depletion of IPv4 addresses in different regions.
Fastest growth increase
Latin America and the Caribbean is the region with the highest increase of growth. Second place goes perhaps a little bit surprising to Africa and third place to Asia Pacific. Africa has however very limited usage to begin with so although they are growing fast, their current burn rate per day is only about 9000 IPv4-addresses per day. The expansion of the Internet in North America is almost linear without any increase in the growth.
Daily Burn Rate
Here is a list of the current daily burnrate of IPv4 addresses per region. Asia and the Pacific are currently burning the most IPv4 addresses, over 5 million addresses per month.
Some of my statistics have started to be wrong lately. I tracked down the problem to the 188/8 block.
The RIPE NCC statistics (such as http://www.db.ripe.net/whois?-rTroute-set+RS-IP-ALLOCATIONS-TO-RIPE-NCC-FROM-IANA) claims that the 188/8 is allocated to RIPE NCC from IANA.
When looking at the IANA site (http://www.iana.org/assignments/ipv4-address-space/) it says that it is administered by RIPE NCC, but not allocated to RIPE NCC. This would indicate that 188/8 would be in the various pool.
This has an impact on the size of the RIPE NCC pool. Without the 188/8 the RIPE pool is about 2.3 x /8 with the block the pool is about 3.3 x /8. My model assumes that RIPE only have 2.3 x /8 in their pool. This will not cover the stipulated 9 months of demand for RIPE NCC and they should therefore request more space from IANA.