IPv4 address exhaustion is the decreasing supply of unallocated IPv4 addresses available at the Internet Assigned Numbers Authority (IANA) and the regional Internet registries for assignment to end users and local Internet registries, such as Internet service providers.
The depletion of the IPv4 allocation pool has been a concern since the 1980s when the Internet started to experience dramatic growth. IPv4 only provided for approximately 4 billion addresses with a current primary allocation granularity of /8 blocks by IANA, a limit that is estimated to be reached before 2012. The anticipated shortage has been the driving factor in creating and adopting several new technologies, including classful networks in the 1980s, Classless Inter-Domain Routing (CIDR) methods in 1993, network address translation (NAT) and a new version of the Internet Protocol, IPv6, in 1998.
The transition of the Internet to IPv6 is the only practical and readily available long-term solution to IPv4 address exhaustion. Although the predicted IPv4 address exhaustion approaches its final stages, most ISPs, software vendors and service providers are just beginning IPv6 deployment. A 2008 study by Google indicated that IPv6 penetration was still less than one percent of Internet-enabled hosts in any country.[1]
Contents |
Every host on an IP network, such as a computer or networked printer, is assigned an IP address that is used to communicate with other hosts on the same network or globally. Internet Protocol version 4 provides approximately 4.3 billion (short scale) addresses. However, large blocks of IPv4 addresses are reserved for special uses and are unavailable for public allocation.
There are insufficient publicly routable IPv4 addresses to provide a distinct address to every Internet device or service. This problem has been mitigated for some time using network address translation (NAT), whereby a single public IP address can masquerade multiple internal local area network (LAN) hosts using private addresses. Individual hosts behind NAT appear to be sending their data from the public IP address of the translator device, and the translator maintains a mapping of each host's source address originating traffic inside the network and forwards replies from the Internet accordingly.
Exhaustion will occur on all continents approximately at the same time, as all registries follow similar allocation policies of about 12 to 18 months stock allocated at each request. Only specific organizations that requested addresses in the pre-CIDR or pre-RIR eras possibly have significant unused address space remaining.
The time remaining until the first RIR exhaustion is a short time for the entire industry to transition to IPv6. This situation is aggravated by the likelihood that until exhaustion there will be no significant demand for IPv6. David Conrad, the general manager of IANA acknowledges, "I suspect we are actually beyond a reasonable time frame where there won't be some disruption. Now it's more a question of how much." Geoff Huston claims the transition to IPv6 should have started much earlier, such that by the exhaustion date it would be completed, with all devices IPv6-capable, and IPv4 being phased out.
By the end of 2012, there will be new devices and services on the Internet that have no choice but to use only IPv6 addresses. For the rest of the Internet to be able to communicate with them older hosts must implement IPv6 as well, or utilize special translator gateway services.
Apart from enforcing long-standing assignment rules, there is no significant effort to conserve the remaining IPv4 addresses. Consequently, it is expected that IANA will first run out permanently in early 2011, and then the RIRs in early 2012, and subsequently LIRs.
Even when the RIR and IANA pools are officially exhausted, there will still be unused IPv4 addresses, however, for example: historical over-allocations and user-abandoned ranges. The existing mechanisms do not address such scenarios. Mechanisms that have been discussed for this stage have included the reclamation of unused address space, re-engineering hosts and routers to allow the use of areas of the IPv4 address space which are currently unusable for technical reasons, and the creation of a market in IPv4 addresses.
ARIN, RIPE and APNIC, and the Internet community are conducting discussions on the question whether organizations that require IPv4 addresses can acquire them from other organizations.[10]
While the primary reason for IPv4 address exhaustion is insufficient design capacity of the original Internet infrastructure, several additional driving factors have aggravated the shortcomings. Each of them increased the demand on the limited supply of addresses, often in ways unanticipated by the original designers of the network.
As IPv4 increasingly became the de facto standard for networked digital communication, the cost of embedding substantial computing power into handheld devices dropped. Mobile phones have become viable Internet hosts. New specifications of 4G devices require IPv6 addressing.
Throughout the 1990s, the predominant mode of consumer Internet access was telephone modem dialup. The rapid growth of the dialup networks increased address consumption rates, although it was common that the modem pools, and as a result, the pool of assigned IP addresses, were shared to a large degree amongst a larger customer base. By 2007, however, broadband Internet access had begun to exceed 50% penetration in many markets.[11] Broadband connections are usually always active as the gateway devices (routers, broadband modems) are rarely turned off and require only little power, so that the address uptake by Internet service providers continued at an accelerating pace.
There are hundreds of millions of households in the developed world. In 1990, only a fraction of these had Internet connectivity. Just 15 years later, almost half of them had persistent broadband connections.[12]
Organizations that obtained IP addresses in the 1980s were often allocated far more addresses than they actually required, because the initial allocation method was inadequate to reflect reasonable usage. For example, large companies or universities were assigned class A address blocks with over 16 million IPv4 addresses each, because the next smaller allocation unit (Class B network) was too small for their intended deployments.
Many organizations continue to utilize public IP addresses for devices not accessible outside their local network. From a global address allocation view point, this is inefficient in many cases, but scenarios exist where this is preferred in the organizational network implementation strategies.
Due to inefficiencies caused by subnetting, it is difficult to use all addresses in a block. The host-density ratio, as defined in RFC 3194, is an intuitive metric for utilization of IP address blocks.
Some methods of mitigation of IPv4 address exhaustion have been:
Subnetting is a popular method of managing and subdividing address space, thereby reducing additional allocations for expanding networks.
Before classful network design and later Classless Inter-Domain Routing (CIDR) were introduced, large blocks of IP addresses were allocated to individual companies and organizations. IANA could potentially reclaim these ranges and reissue the addresses in smaller blocks. However, it can be expensive in terms of cost and time to renumber a large network so these organizations will likely object and legal conflicts are foreseeable.[citation needed] Moreover, at the current rate of IPv4 address consumption, even if all of these could be reclaimed, it would only result in postponing the address exhaustion date.
Similarly, many IP addresses have been allocated to companies that no longer exist or were never used. Unfortunately, the stricter accounting of IP address allocation currently in place was not always in place and it would take quite a bit of effort to track down which addresses really are unused. Many IP address blocks are not routed in the global BGP routing tables, but are actually in use on intranets.
Some address space that was previously reserved by IANA has been added to the available pool. There are proposals to reclaim the class E network addresses.[13][14] However, many computer and router operating systems and firmware are incompatible with the use of these addresses.[15][16][17][18][19] For this reason, the proposal seeks not to redesignate the class E space for public assignment, but instead proposes to change its status from "Reserved" to "Limited Use for Large Private Internets." This would allow the use of the space on large, private networks that require more address space than is currently available through RFC 1918.
Similar to how many companies use NAT for most employee computers, an ISP can use NAT for many customers instead of giving them publicly routable IP addresses.
This has been already successfully implemented in some countries like Russia, where many broadband ISPs now have ISP-wide NAT in place, with an option of assigning a publicly routable IP address at an additional cost.[20]
The creation of markets to buy and sell IPv4 addresses has been proposed many times as an efficient means of allocation. The primary benefit of an address market would be that IPv4 addresses would continue to be available, although the market price of addresses would be expected to rise over time. These schemes have major drawbacks that have prevented their implementation, as outlined in RFC 2008:
IPv6 is currently the only viable solution to the IPv4 address shortage, endorsed and implemented by all Internet technical standards bodies and network equipment vendors. In addition to other design improvements, it replaces the 32-bit IPv4 address (4.3 billion possible hosts) with a 128-bit address for a capacity of 3.4×1038 hosts. IPv6 has been in active production deployment since June 2006 when organized worldwide efforts of testing and evaluation ceased (6bone).
|
|