ARIN Reaches Final Stage for IPv4 Address Space

ARIN today announced that it is now down to its last /8 of IPv4 address space. This is the point when remaining IPv4 capacity is considered "depleted" and more stringent allocation policies are put into effect, as outlined in the announcement. The analogous depletion state was announced and similar policies enforced by APNIC in 2011 and by RIPE in 2012. LACNIC crossed the /8 threshold in 2011 but will engage its depletion policies when it reaches one /11 (2.1M IP addresses).

The last /8 threshold means the RIR has about 16.8 million IPv4 addresses available, which may seem like a lot, but each allocation consists of hundreds if not thousands of IP addresses to ISPs and customers. Hence the more stringent allocation policies to extend the lifetime of IPv4 a bit longer. You can follow the current outlook on IPv4 lifetime by RIR on Geoff Huston's potaroo site and summarized below and updated with this recent ARIN information:

RIRProjected Exhaustion DateRemaining /8sIP addresses
APNIC19-Apr-2011 (actual)0.793713.3M
RIPE NCC14-Sep-2012 (actual)0.819313.7M
LACNIC15-Jul-20140.40596.8M
ARIN23-Apr-20141.016.8M
AFRINIC28-Jan-20203.131352.5M

The net impact is that the Internet has just over 100 million IPv4 addresses available. That's 0.1 billion, which with only about 40% Internet user penetration today, doesn't leave much capacity at all for those 4 billion plus earthlings who do not yet have Internet access. If you haven't been convinced of the inevitability of IPv6, hopefully this helps and provides ample time to plan for it. If you haven't had time or resources to plan for IPv6, now is the time to start planning. BT can help with network assessment, planning and deployment services, free IPv6 addressing tools, and commercial IP address management (IPAM) solutions. Contact us to learn more.

Comments

Post a Comment

Popular posts from this blog

Handy AAAA filter in BIND 9.8

The ISC introduced a pair of new configuration file options in BIND 9.8 to enable administrators to easily filter who may receive AAAA record type responses even if valid responses exist. For example, clients on subnets that do not have IPv6 network access can be excluded from receiving affirmative answers for AAAA queries. This feature provides simpler administration than the alternative mechanism using views. The first option, filter-aaaa-on-v4,defines whether the server will return AAAA records to certain clients. Such clients are defined by the address match list parameter of the second option, filter-aaaa. Note that BIND must be compiled with the --enable-filter-aaaa option on the configure command line to enable AAAA filtering. The syntax of these options is as follows: filter-aaaa-on-v4 (yes | no | break-dnssec) ; filter-aaaa {addr_match_list;} ; The filter-aaaa option identifies the address match list for which the filter-aaaa-on-v4 option is to be applied as described ...
Read more

Inglorious DDI

We all know how critical DHCP/DNS/IPAM (DDI) services are. Your network cannot function without them. But like most foundational elements of anything, they are certainly not glamorous...like good luck finding a home designer who specializes in home foundations. I would not be shocked should HGTV pass on my brilliant concept for a foundation building show. I suppose most people would find a show detailing footing depths and concrete pouring techniques rather boring.  Nevertheless, there are countless shows for redesigning and remodeling homes. On most episodes the foundation is out of sight, out of mind. If it's stable, no one wants to pay it attention, they just expect it to keep doing its job, supporting the structure. Once in a while a foundational issue is brought up that unexpectedly threatens to raise the budget to heighten the drama. All work stops until the issue is addressed. And you'll notice that the owner never denies paying the extra amount to fix the issue. ...
Read more

BIND 9.8.0 Adds DNS64 Support - Part 2 - How is it configured?

BIND 9.8.0 introduced a new dns64 option statement that can be configured within the server named.conf options block or within a view options block. Recall from a prior post that DNS64 configures a recursive DNS server to issue A record queries on behalf of a client requesting AAAA records, then appends the returned IPv4 address to a defined IPv6 prefix. This manufactured IPv6 address enables the querying host to connect to a NAT64 gateway which will terminate the IPv6 connection from the client and map it to an outbound IPv4 connection to the appended IPv4 address, completing the connection! Whew! BIND offers a number of useful parameters within the dns64 statement to control this process. The statement syntax is: dns64 IPv6_prefix { [clients {address_match_list };] [mapped {address_match_list };] [exclude {address_match_list };] [suffix IPv6_addr;] [recursive-only (yes|no);] [break-dnssec (yes|no);] }; The IPv6_prefix parameter is the prefix to which returned...
Read more