IPv4 address exhaustion explained

IPv4 address exhaustion is the depletion of the pool of unallocated IPv4 addresses. Because the original Internet architecture had fewer than 4.3 billion addresses available, depletion has been anticipated since the late 1980s when the Internet started experiencing dramatic growth. This depletion is one of the reasons for the development and deployment of its successor protocol, IPv6.^[1] IPv4 and IPv6 coexist on the Internet.

The IP address space is managed globally by the Internet Assigned Numbers Authority (IANA), and by five regional Internet registries (RIRs) responsible in their designated territories for assignment to end users and local Internet registries, such as Internet service providers. The main market forces that accelerated IPv4 address depletion included the rapidly growing number of Internet users, always-on devices, and mobile devices.

The anticipated shortage has been the driving factor in creating and adopting several new technologies, including network address translation (NAT), Classless Inter-Domain Routing (CIDR) in 1993, and IPv6 in 1998.

The top-level exhaustion occurred on 31 January 2011.^{[2] [3] [4] [5]} All RIRs have exhausted their address pools, except those reserved for IPv6 transition; this occurred on 15 April 2011 for the Asia-Pacific (APNIC),^{[6] [7] [8]} on 10 June 2014 for Latin America and the Caribbean (LACNIC),^[9] on 24 September 2015 for North America (ARIN),^[10] on 21 April 2017 for Africa (AfriNIC),^[11] and on 25 November 2019 for Europe, Middle East and Central Asia (RIPE NCC).^[12] These RIRs still allocate recovered addresses or addresses reserved for a special purpose. Individual ISPs still have pools of unassigned IP addresses, and could recycle addresses no longer needed by subscribers.

Vint Cerf co-created TCP/IP thinking it was an experiment and has admitted he thought 32 bits was enough.^{[13] [14] [15] [16]}

IP addressing

Every node of an Internet Protocol (IP) network, such as a computer, router, or network printer, is assigned an IP address for each network interface, used to locate and identify the node in communications with other nodes on the network. Internet Protocol version 4 provides 2³² (4,294,967,296) addresses. However, large blocks of IPv4 addresses are reserved for special uses and are unavailable for public allocation.

The IPv4 addressing structure provides an insufficient number of publicly routable addresses to provide a distinct address to every Internet device or service. This problem has been mitigated for some time by changes in the address allocation and routing infrastructure of the Internet. The transition from classful network addressing to Classless Inter-Domain Routing delayed the exhaustion of addresses substantially. In addition, network address translation (NAT) permits Internet service providers and enterprises to masquerade private network address space with only one publicly routable IPv4 address on the Internet interface of a main Internet router, instead of allocating a public address to each network device.

Address depletion

While the primary reason for IPv4 address exhaustion is insufficient capacity in the design 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.

Mobile devices: As IPv4 increasingly became the de facto standard for networked digital communication and the cost of embedding substantial computing power into hand-held devices dropped, mobile phones have become viable Internet hosts. New specifications of 4G devices require IPv6 addressing.

Always-on connections: Throughout the 1990s, the predominant mode of consumer Internet access was telephone modem dial-up. The rapid increase in the number of the dial-up 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 amongst a large customer base. By 2007, however, broadband Internet access had begun to exceed 50% penetration in many markets.^[17] Broadband connections are always active, as the gateway devices (routers, broadband modems) are rarely turned off, so that the address uptake by Internet service providers continued at an accelerating pace.

Internet demographics: The developed world consists of hundreds of millions of households. In 1990, only a small fraction of these had Internet access. Just 15 years later, almost half of them had persistent broadband connections.^[18] The many new Internet users in countries such as China and India are also driving address exhaustion.

Inefficient address use: Organizations that obtained IP addresses in the 1980s were often allocated far more addresses than they actually required, because the initial classful network 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, a class B block with 65,536 addresses, was too small for their intended deployments.

Many organizations continue to use public IP addresses for devices not accessible outside their local network. From a global address allocation viewpoint, 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 a metric for use of IP address blocks, that is used in allocation policies.

Mitigation efforts

Efforts to delay address space exhaustion started with the recognition of the problem in the early 1990s, and the introduction of a number of stop-gap refinements to make the existing structure operate more efficiently, such as CIDR methods and strict usage-based allocation policies.

The Internet Engineering Task Force (IETF) created the Routing and Addressing Group (ROAD) in November 1991 to respond to the scalability problem caused by the classful network allocation system in place at the time.^{[19] [20]}

IPv6, the successor technology to IPv4, was designed to address this problem. It supports approximately network addresses.^[21] Although the predicted depletion was already approaching its final stages, most providers of Internet services and software vendors were just beginning IPv6 deployment at that time.^[22]

Other mitigation efforts and technologies include:

• use of network address translation (NAT) which allows a private network to use one public IP address and permitting private addresses in the private network;
• use of private network addressing;^[23]
• name-based virtual hosting of web sites;
• tighter control by regional Internet registries on the allocation of addresses to local Internet registries;
• network renumbering and subnetting to reclaim large blocks of address space allocated in the early days of the Internet, when the Internet used inefficient classful network addressing.^[24]

Exhaustion dates and impact

On 31 January 2011, the last two unreserved IANA address blocks were allocated to APNIC according to RIR request procedures. This left five reserved but unallocated blocks.^{[6] [25] [26]} In accord with ICANN policies, IANA proceeded to allocate one of those five s to each RIR, exhausting the IANA pool,^[27] at a ceremony and press conference on 3 February 2011.

The various legacy address blocks with administration historically split among the RIRs were distributed to the RIRs in February 2011.^[28]

APNIC was the first regional Internet registry to run out of freely allocated IPv4 addresses, on 15 April 2011. This date marked the point where not everyone who needed an IPv4 address could be allocated one. As a consequence of this exhaustion, end-to-end connectivity as required by specific applications will not be universally available on the Internet until IPv6 is fully implemented. However, IPv6 hosts cannot directly communicate with IPv4 hosts, and have to communicate using special gateway services. This means that general-purpose computers must still have IPv4 access, for example through NAT64, in addition to the new IPv6 address, which is more effort than just supporting IPv4 or IPv6.^[29]

In early 2011, only 16–26% of computers were IPv6 capable, while only 0.2% preferred IPv6 addressing^[30] with many using transition methods such as Teredo tunneling.^[31] About 0.15% of the top million websites were IPv6 accessible in 2011.^[32] Complicating matters, 0.027% to 0.12% of visitors could not reach dual-stack sites,^[33] but a larger percentage (0.27%) could not reach IPv4-only sites.^[34] IPv4 exhaustion mitigation technologies include IPv4 address sharing to access IPv4 content, IPv6 dual-stack implementation, protocol translation to access IPv4 and IPv6-addressed content, and bridging and tunneling to bypass single protocol routers. Early signs of accelerated IPv6 adoption after IANA exhaustion are evident.^[35]

Regional exhaustion

All the RIRs have set aside a small pool of IP addresses for the transition to IPv6 (for example carrier-grade NAT), from which each RIR can typically get at most 1024 in total. ARIN and LACNIC^[36] reserves the last for IPv6 transition. APNIC, and RIPE NCC have reserved the last obtained block for IPv6 transition. AFRINIC reserves a block for this purpose.^[37] When only this last block remains, the RIR's supply of IPv4 addresses is said to be "exhausted".

APNIC was the first RIR to restrict allocations to 1024 addresses for each member, as its pool reached critical levels of one block on 14 April 2011.^{[6] [38] [39] [40] [41] [42]} The APNIC RIR is responsible for address allocation in the area of fastest Internet expansion, including the emerging markets of China and India.

RIPE NCC, the regional Internet registry for Europe, was the second RIR to deplete its address pool on 14 September 2012.^[43]

On 10 June 2014, LACNIC, the regional Internet registry for Latin America and the Caribbean, was the third RIR to deplete its address pool.^{[44] [45]}

ARIN was exhausted on 24 September 2015.^[46] ARIN has been unable to allocate large requests since July 2015, but smaller requests were still being met.^[47] After IANA exhaustion, IPv4 address space requests became subject to additional restrictions at ARIN,^[48] and became even more restrictive after reaching the last in April 2014.^[49]

On 31 March 2017, AFRINIC became the last regional Internet registry to run down to its last block of IPv4 addresses (102/8), thus triggering the first phase of its IPv4 exhaustion policy.^[50] "On 13 January 2020, AFRINIC approved an IPv4 prefix that resulted in no more than a /11 of non-reserved space to be available in the Final /8," which triggered its IPv4 Exhaustion Phase 2.^[51]

On 25 November 2019, RIPE NCC announced^[52] that it had made its "final IPv4 allocation from the last remaining addresses in our available pool. We have now run out of IPv4 addresses." RIPE NCC will continue to allocate IPv4 addresses, but only "from organisations that have gone out of business or are closed, or from networks that return addresses they no longer need. These addresses will be allocated to our members (LIRs) according to their position on a new waiting list…" The announcement also called for support for the implementation of the IPv6 roll-out.

Impact of APNIC RIR exhaustion and LIR exhaustion

Systems that require inter-continental connectivity will have to deal with exhaustion mitigation already due to APNIC exhaustion.At APNIC, existing LIRs could apply for twelve months stock before exhaustion when they were using more than 80% of allocated space allocated to them.^[53] Since 15 April 2011, the date when APNIC reached its last block, each (current or future) member will only be able to get one allocation of 1024 addresses (a block) once.^{[54] [55]} As the slope of the APNIC pool line on the "Geoff Huston's projection of the evolution of the IP pool for each RIR" chart to the right shows, the last block would have been emptied within one month without this policy. By APNIC policy, each current or future member can receive only one block from this last (there are 16384 blocks in the last block). Since there are around 3000 current APNIC members, and around 300 new APNIC members each year, APNIC expects this last block to last for many years.^[56] Since the redistribution of recovered space, APNIC is distributing an additional to each member upon request.

The 1,024 addresses in the block can be used by APNIC members to supply NAT44 or NAT64 as a service on an IPv6 network. However at a new large ISP, 1,024 IPv4 addresses might not be enough to provide IPv4 connectivity to all the customers due to the limited number of ports available per IPv4 address.^[57]

The regional Internet registries (RIRs) for Asia (APNIC) and North America have a policy called the Inter-RIR IPv4 Address Transfer Policy, which allows IPv4 addresses to be transferred from North America to Asia.^{[58] [59]} The ARIN policy was implemented on 31 July 2012.^[59]

IPv4 broker businesses have been established to facilitate these transfers.^[60]

Notable exhaustion advisories

Estimates of the time of complete IPv4 address exhaustion varied widely in the early 2000s. In 2003, Paul Wilson (director of APNIC) stated that, based on then-current rates of deployment, the available space would last for one or two decades.^[61] In September 2005, a report by Cisco Systems suggested that the pool of available addresses would deplete in as little as 4 to 5 years. In the last year before exhaustion, IPv4 allocations were accelerating, resulting in exhaustion trending to earlier dates.

• On 21 May 2007, the American Registry for Internet Numbers (ARIN), the RIR for the US, Canada and a number of island states (mostly in the Caribbean), advised the Internet community that, due to the expected exhaustion in 2010, "migration to IPv6 numbering resources is necessary for any applications which require ongoing availability from ARIN of contiguous IP numbering resources".^[62] "Applications" include general connectivity between devices on the Internet, as some devices only have an IPv6 address allocated.
• On 20 June 2007, the Latin American and Caribbean Internet Addresses Registry (LACNIC), advised "preparing its regional networks for IPv6" by 1 January 2011, for the exhaustion of IPv4 addresses "in three years time".^[63]
• On 26 June 2007, the Asia-Pacific Network Information Centre (APNIC), the RIR for the Pacific and Asia, endorsed a statement by the Japan Network Information Center (JPNIC) that to continue the expansion and development of the Internet a move towards an IPv6-based Internet is advised.^[64] This, with an eye on the expected exhaustion around 2010, would create a great restriction on the Internet.^[65]
• On 26 October 2007, the Réseaux IP Européens Network Coordination Centre (RIPE NCC), the RIR for Europe, the Middle East, and parts of Central Asia, endorsed a statement^[66] by the RIPE community urging "the widespread deployment of IPv6 be made a high priority by all stakeholders".
• On 15 April 2009, ARIN sent a letter to all CEO/Executives of companies who have IPv4 addresses allocated informing them that ARIN expects the IPv4 space will be depleted within the next two years.^[67]
• In May 2009, the RIPE NCC launched IPv6ActNow.org to help explain "IPv6 in terms everyone can understand and providing a variety of useful information aimed at promoting the global adoption of IPv6".
• On 25 August 2009, ARIN announced a joint series event in the Caribbean region to push for the implementation of IPv6. ARIN reported at this time that less than 10.9% of IPv4 address space is remaining.^[68]
• World IPv6 Day was an event sponsored and organized by the Internet Society and several large content providers to test public IPv6 deployment. It started at 00:00 UTC on 8 June 2011 and ended at 23:59 the same day. The test primarily consisted of websites publishing AAAA records, allowing IPv6 capable hosts to connect to these sites using IPv6, and for misconfigured networks to be corrected.
• World IPv6 Launch Day occurred on 6 June 2012, following the success of World IPv6 Day a year earlier. It involved many more participants and had a more ambitious goal of permanently enabling IPv6 on participant organizations' networks.
• On 24 September 2015 ARIN declared exhaustion of the ARIN IPv4 addresses pool.^[10]
• On 25 November 2019, RIPE NCC announced^[52] that it had made its "final IPv4 allocation from the last remaining addresses in our available pool."
• On 21 August 2020, LACNIC announced that it had made its final IPv4 allocation.^[69]

Post-exhaustion mitigation

By 2008 policy planning for the end-game and post-exhaustion era was underway.^[70] Several proposals have been discussed to delay shortages of IPv4 addresses:

Reclamation of unused IPv4 space

Before and during the time when classful network design was still used as allocation model, large blocks of IP addresses were allocated to some organizations. Since the use of CIDR the Internet Assigned Numbers Authority (IANA) could potentially reclaim these ranges and reissue the addresses in smaller blocks. ARIN, RIPE NCC and APNIC have a transfer policy, such that addresses can get returned, with the purpose to be reassigned to a specific recipient.^{[71] [72] [73]} However, it can be expensive in terms of cost and time to renumber a large network, so these organizations are likely to object, with legal conflicts possible. However, even if all of these were reclaimed, it would only result in postponing the date of address exhaustion.

Similarly, IP address blocks have been allocated to entities that no longer exist and some allocated IP address blocks or large portions of them have never been used. No strict accounting of IP address allocations has been undertaken, and it would take a significant amount of effort to track down which addresses really are unused, as many are in use only on intranets.

Some address space previously reserved by IANA has been added to the available pool. There have been proposals to use the class E network range of IPv4 addresses^{[74] [75]} (which would add 268.4 million IP addresses to the available pool) but many computer and router operating systems and firmware do not allow the use of these addresses.^{[76] [77] [78] [79]} For this reason, the proposals have sought not to designate the class E space for public assignment, but instead propose to permit its private use for networks that require more address space than is currently available through RFC 1918.

Several organizations have returned large blocks of IP addresses. Notably, Stanford University relinquished their Class A IP address block in 2000, making 16 million IP addresses available.^[80] Other organizations that have done so include the United States Department of Defense, BBN Technologies, and Interop.^[81]

Markets in IP addresses

The creation of markets to buy and sell IPv4 addresses has been considered to be a solution to the problem of IPv4 scarcity and a means of redistribution. The primary benefits of an IPv4 address market are that it allows buyers to maintain undisrupted local network functionality.^{[82] [83]} IPv6 adoption, while in progress, is currently still in early stages.^[84] It requires a significant investment of resources, and poses incompatibility issues with IPv4, as well as certain security and stability risks.^{[85] [86]}

• The creation of a market in IPv4 addresses would only delay the practical exhaustion of the IPv4 address space for a relatively short time, since the public Internet is still growing.
• The concept of legal ownership of IP addresses as property is explicitly denied by ARIN and RIPE NCC policy documents and by the ARIN Registration Services Agreement, although ownership rights have been postulated based on a letter from the National Science Foundation General Counsel.^[87] NSF later indicated that the view was not official, and a statement from the Department of Commerce was subsequently issued indicating that "The USG participates in the development of and is supportive of the policies, processes, and procedures agreed upon by the Internet technical community through ARIN."^{[88] [89]}
• Ad-hoc trading in addresses could lead to fragmented patterns of routing that could increase the size of the global routing table, potentially causing problems for routers with insufficient routing memory resources.
• Microsoft bought 666,624 IPv4 addresses from Nortel's liquidation sale for 7.5 million dollars in a deal brokered by Addrex.^{[90] [91]} Before exhaustion, Microsoft could have obtained addresses from ARIN without charge, provided that, as per ARIN policy, Microsoft could present ARIN with a need for them.^[92] The success of this transfer was contingent on Microsoft successfully presenting ARIN with such a justification. The purchase provided Microsoft with a supply that was sufficient for their claimed needs for growth over the next 12 months, rather than for a 3-months' period as is normally requested from ARIN.^[93]

Transition mechanisms

See main article: IPv6 transition mechanism. As the IPv4 address pool depletes, some ISPs will not be able to provide globally routable IPv4 addresses to customers. Nevertheless, customers are likely to require access to services on the IPv4 Internet. Several technologies have been developed for providing IPv4 service over an IPv6 access network.

In ISP-level IPv4 NAT, ISPs may implement IPv4 network address translation within their networks and assign private IPv4 addresses to customers. This approach may allow customers to keep using existing hardware. Some estimates for NAT argue that US ISPs have 5-10 times the number of IPs they need in order to serve their existing customers.^[94]

However the allocation of private IPv4 addresses to customers may conflict with private IP allocations on the customer networks. Furthermore, some ISPs may have to divide their network into subnets to allow them to reuse private IPv4 addresses, complicating network administration. There are also concerns that features of consumer-grade NAT such as DMZs, STUN, UPnP and application-level gateways might not be available at the ISP level. ISP-level NAT may result in multiple-level address translation which is likely to further complicate the use of technologies such as port forwarding used to run Internet servers within private networks.

NAT64 translates IPv6 requests from clients to IPv4 requests. This avoids the need to provision any IPv4 addresses to clients and allows clients that only support IPv6 to access IPv4 resources. However this approach requires a DNS server with DNS64 capability and cannot support IPv4-only client devices.

DS-Lite (Dual-Stack Light) uses tunnels from the customer premises equipment to a network address translator at the ISP.^[95] The consumer premises equipment encapsulates the IPv4 packets in an IPv6 wrapper and sends them to a host known as the AFTR element. The AFTR element de-encapsulates the packets and performs network address translation before sending them to the public Internet. The NAT in the AFTR uses the IPv6 address of the client in its NAT mapping table. This means that different clients can use the same private IPv4 addresses, therefore avoiding the need for allocating private IPv4 IP addresses to customers or using multiple NATs.

Address plus Port allows stateless sharing of public IP addresses based on TCP/UDP port numbers. Each node is allocated both an IPv4 address and a range of port numbers to use. Other nodes may be allocated the same IPv4 address but a different range of ports. The technique avoids the need for stateful address translation mechanisms in the core of the network, thus leaving end users in control of their own address translation.^[96]

Long-term solution

Deployment of IPv6 is the standards-based solution to the IPv4 address shortage.^[7] IPv6 is endorsed and implemented by all Internet technical standards bodies and network equipment vendors. It encompasses many design improvements, including the replacement of the 32-bit IPv4 address format with a 128-bit address which provides an addressing space without limitations for the foreseeable future. IPv6 has been in active production deployment since June 2006, after organized worldwide testing and evaluation in the 6bone project ceased. Interoperability for hosts using only IPv4 protocols is implemented with a variety of IPv6 transition mechanisms.

See also

• List of assigned /8 IPv4 address blocks
• 512K Day – an event in 2014, involving the exhaustion of the default allocation of hardware routing slots on many routers

External links

• [//www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml Official current state of {{IPaddr|/8}} allocations, as maintained by IANA]
• [//www.icann.org/en/news/announcements/announcement-2-10feb08-en.htm ICANN recovers Large Block of Internet Addresses (14.0.0.0/8)] 2008-02-10
• [//www.icann.org/en/resources/policy/global-addressing/proposal-ipv4-report-29nov07-en.htm Global Policy Proposal for Remaining IPv4 Address Space – Background Report] 2008-09-08
• RIR IPv4 status: [//www.apnic.net/community/ipv4-exhaustion/graphical-information APNIC] [//www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph RIPE]
• IPv6 vs. carrier-grade NAT/squeezing more out of IPv4
• IP addressing in China and the myth of address shortage

Notes and References

1. Li . Kwun-Hung . Wong . Kin-Yeung . 2021-06-14 . Empirical Analysis of IPv4 and IPv6 Networks through Dual-Stack Sites . Information . en . 12 . 6 . 246 . 10.3390/info12060246 . 2078-2489. free .
2. Web site: Free Pool of IPv4 Address Space Depleted. Smith. Lucie. Lipner. Ian. 3 February 2011. Number Resource Organization. 3 February 2011. 13 August 2011. https://web.archive.org/web/20110813211426/http://www.nro.net/news/ipv4-free-pool-depleted. live.
3. Web site: Available Pool of Unallocated IPv4 Internet Addresses Now Completely Emptied. ICANN. 3 February 2011. 10 September 2016. 8 August 2011. https://web.archive.org/web/20110808112055/http://www.icann.org/en/news/releases/release-03feb11-en.pdf. live.
4. Web site: Major Announcement Set on Dwindling Pool of Available IPv4 Internet Addresses. 10 September 2016. 13 March 2011. https://web.archive.org/web/20110313155455/http://www.icann.org/en/news/advisories/advisory-01feb11-en.pdf. live.
5. Web site: Five /8s allocated to RIRs – no unallocated IPv4 unicast /8s remain. ICANN, nanog mailing list. 3 February 2011. 27 August 2011. https://web.archive.org/web/20110827120045/http://mailman.nanog.org/pipermail/nanog/2011-February/032107.html. live.
6. Web site: Huston. Geoff. IPv4 Address Report, daily generated. 16 January 2011. 6 August 2011. https://web.archive.org/web/20110806020416/http://www.potaroo.net/tools/ipv4/index.html. live.
7. Web site: Two /8s allocated to APNIC from IANA. APNIC. 1 February 2010. 3 February 2011. dead. https://web.archive.org/web/20110807162237/http://www.apnic.net/publications/news/2011/delegation. 7 August 2011.
8. Web site: APNIC IPv4 Address Pool Reaches Final /8. APNIC. 15 April 2011. 15 April 2011. dead. https://web.archive.org/web/20110807162057/http://www.apnic.net/publications/news/2011/final-8. 7 August 2011.
9. Web site: LACNIC Enters IPv4 Exhaustion Phase - The Number Resource Organization. 10 September 2016. 13 May 2016. https://web.archive.org/web/20160513141946/https://www.nro.net/news/lacnic-enters-ipv4-exhaustion-phase. live.
10. Web site: ARIN IPv4 Free Pool Reaches Zero. American Registry for Internet Numbers. 24 September 2015. 25 September 2015. 25 September 2015. https://web.archive.org/web/20150925133021/https://www.arin.net/announcements/2015/20150924.html. live.
11. Web site: IPv4 Exhaustion - AFRINIC. Regional Internet Registry for Africa. 17 January 2020. 18 September 2020. 15 September 2020. https://web.archive.org/web/20200915081117/https://afrinic.net/exhaustion. live.
12. Web site: The RIPE NCC has run out of IPv4 Addresses. Réseaux IP Européens Network Coordination Centre. 25 November 2019. 25 November 2019. 25 November 2019. https://web.archive.org/web/20191125145354/https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses. live.
13. Web site: Perry . Tekla . 2023-05-07 . Vint Cerf on 3 Mistakes He Made in TCP/IP . live . https://web.archive.org/web/20230508022726/https://spectrum.ieee.org/vint-cerf-mistakes . 2023-05-08 . 2023-05-08 . . en.
14. Web site: Moses . Asher . Grubb . Ben . 2011-01-21 . Internet Armageddon all my fault: Google chief . live . https://web.archive.org/web/20230203001502/https://www.smh.com.au/technology/internet-armageddon-all-my-fault-google-chief-20110121-19z9i.html . 2023-02-03 . 2023-05-08 . . en.
15. Web site: Trout . Christopher . 2011-01-26 . Vint Cerf on IPv4 depletion: 'Who the hell knew how much address space we needed?' . live . https://web.archive.org/web/20230203025920/https://www.engadget.com/2011-01-26-vint-cerf-on-ipv4-depletion-who-the-hell-knew-how-much-address.html . 2023-02-03 . 2023-05-08 . . en-US.
16. Web site: 2008-01-29 . Google IPv6 Conference 2008: What will the IPv6 Internet look like? . . Cerf quote starts 13½ minutes into the video . I'm serious, the decision to put a 32-bit address space on there was the result of a year's battle among a bunch of engineers who couldn't make up their minds about 32, 128 or variable length. And after a year of fighting I said - I'm now at ARPA, I'm running the program, I'm paying for this stuff and using American tax dollars - and I wanted some progress because we didn't know if this is going to work. So I said - 32 bits, it is enough for an experiment, it is 4.3 billion terminations - even the defense department doesn't need 4.3 billion of anything and it couldn't afford to buy 4.3 billion edge devices to do a test anyway. So at the time I thought we were doing a experiment to prove the technology and that if it worked we'd have an opportunity to do a production version of it. Well - it just escaped! - it got out and people started to use it and then it became a commercial thing. So, this [IPv6] is the production attempt at making the network scalable. Only 30 years later..
17. Web site: Ferguson. Tim. Broadband adoption passes halfway mark in U.S.. CNET news.com. 18 February 2007. 10 November 2010. 15 November 2013. https://web.archive.org/web/20131115194728/http://news.cnet.com/Broadband-adoption-passes-halfway-mark-in-U.S./2110-1034_3-6160422.html. dead.
18. Web site: Projections of the Number of Households and Families in the United States: 1995 to 2010. April 1996. 10 November 2010. 17 October 2010. https://web.archive.org/web/20101017163733/http://www.census.gov/prod/1/pop/p25-1129.pdf. live.
19. 4632. Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan.
20. Book: IPv6 network administration. Niall Richard Murphy. David Malone. xvii–xix. O'Reilly Media. 2005. 0-596-00934-8.
21. Web site: World IPv6 Day: Working Together Towards a New Internet Protocol. Mark Townsley. 21 January 2011. 8 May 2011. https://web.archive.org/web/20110814065313/http://blogs.cisco.com/news/world-ipv6-day-working-together-towards-a-new-internet-protocol. 14 August 2011. dead.
22. Web site: Global IPv6 Statistics – Measuring the current state of IPv6 for ordinary users. S.H. Gunderson. October 2008. 10 November 2010. 15 August 2011. https://web.archive.org/web/20110815072414/http://meetings.ripe.net/ripe-57/presentations/Colitti-Global_IPv6_statistics_-_Measuring_the_current_state_of_IPv6_for_ordinary_users_.7gzD.pdf. live.
23. 1918. Address Allocation for Private Internets. 4.
24. Scott Hogg. Techniques for Prolonging the Lifespan of IPv4. 9 November 2011. Network World. 20 September 2016. 26 April 2024. https://web.archive.org/web/20240426184141/https://www.networkworld.com/article/739086/cisco-subnet-techniques-for-prolonging-the-lifespan-of-ipv4.html. live.
25. Web site: IANA IPv4 Address Space Registry. IANA IPv4 Address Space Registry. IANA. 31 January 2011. 5 July 2019. https://web.archive.org/web/20190705212510/https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt. live.
26. Web site: Address allocation kicks off IPv4 endgame. Computerworld. Stephen Lawson. 31 January 2011. 1 February 2011. 9 May 2012. https://web.archive.org/web/20120509115834/http://www.computerworld.com/s/article/9207438/Address_allocation_kicks_off_IPv4_endgame. live.
27. Web site: Global Policy for the Allocation of the Remaining IPv4 Address Space. 1 February 2011. 10 August 2011. https://web.archive.org/web/20110810232000/http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm. live.
28. Web site: The IPv4 Depletion site "Blog Archive" Status of the various pool. Ipv4depletion.com. 3 December 2010. 2 December 2011. 19 January 2012. https://web.archive.org/web/20120119205632/http://www.ipv4depletion.com/?p=524. live.
29. Web site: IPv6 and Transitional Myths. Fix6.net. 24 November 2010. 3 February 2011. https://web.archive.org/web/20110723130312/http://www.fix6.net/archives/2010/11/24/ipv6-and-transitional-myths. 23 July 2011. dead.
30. Web site: ISP Column - May 2011. Potaroo.net. 2 December 2011. 31 October 2011. https://web.archive.org/web/20111031094422/http://www.potaroo.net/ispcol/2011-04/teredo.html. live.
31. Web site: Stacking it Up: Experimental Observations on the operation of Dual Stack Services in today's Network. 25 February 2011. dead. https://web.archive.org/web/20110706085135/http://www.apricot-apan.asia/__data/assets/pdf_file/0012/31314/2011-02-23-dualstack-geoff.pdf. 6 July 2011. Geoff. Huston.
32. Web site: IPv6 Measurements – A Compilation – RIPE Labs. RIPE. 9 December 2009 . 2 December 2011. 21 January 2012. https://web.archive.org/web/20120121093105/https://labs.ripe.net/Members/mirjam/content-ipv6-measurement-compilation. live.
33. Web site: IPV6 Test – Introductie. https://web.archive.org/web/20090404120801/http://ipv6test.max.nl. dead. 4 April 2009. Ipv6test.max.nl. 2 December 2011.
34. Web site: ISP Column – April 2010. Potaroo.net. 2 December 2011. 28 October 2011. https://web.archive.org/web/20111028191727/http://www.potaroo.net/ispcol/2010-04/ipv6-measure.html. live.
35. Web site: Suddenly everybody's selling IPv6. Carolyn Duffy Marsan. Network World. 7 February 2011. dead. https://archive.today/20130104230557/http://www.networkworld.com/news/2011/020711-address-depletion-ipv6.html. 4 January 2013.
36. Web site: LACNIC. 10 September 2016. 4 September 2016. https://web.archive.org/web/20160904010216/http://www.lacnic.net/en/web/anuncios/2014-no-hay-mas-direcciones-ipv4-en-lac. live.
37. Web site: IPv4 Address Report. Potaroo.net. 5 May 2014. 6 August 2011. https://web.archive.org/web/20110806020416/http://www.potaroo.net/tools/ipv4/index.html. live.
38. Web site: APNIC's IPv4 pool usage. APNIC. 2 December 2011. https://web.archive.org/web/20110114193847/http://www.apnic.net/community/ipv4-exhaustion/graphical-information. 14 January 2011. dead.
39. Web site: APNIC IPv4 Address Pool Reaches Final /8. https://web.archive.org/web/20110417142306/http://mailman.apnic.net/mailing-lists/apnic-announce/archive/2011/04/msg00002.html. April 17, 2011. April 15, 2011. July 20, 2022. APNIC.
40. Web site: APNIC Allocation Rate (smoothed). 10 September 2016. 24 July 2011. https://web.archive.org/web/20110724020404/http://www.potaroo.net/tools/ipv4/fig27h.png. live.
41. Web site: The End. 10 September 2016. 28 April 2011. https://web.archive.org/web/20110428114345/http://www.potaroo.net/presentations/2011-02-25-movie.pdf. live.
42. Web site: RIR pool exhaust rates (zoomed). 10 September 2016. dead. https://web.archive.org/web/20160611023211/http://www.tndh.net/~tony/ietf/IPv4-rir-pools-zoom.jpg. 11 June 2016.
43. Web site: RIPE NCC Begins to Allocate IPv4 Address Space From the Last /8. RIPE. 19 August 2013. 16 September 2012. https://web.archive.org/web/20120916205855/http://www.ripe.net/internet-coordination/news/ripe-ncc-begins-to-allocate-ipv4-address-space-from-the-last-8. live.
44. Web site: IPv4 Address Report retrieved June 16, 2014. 27 January 2007. 6 August 2011. https://web.archive.org/web/20110806020416/http://www.potaroo.net/tools/ipv4/index.html. live.
45. Web site: No more IPv4 addresses in Latin America and the Caribbean. 16 June 2014. 3 August 2014. https://web.archive.org/web/20140803203426/http://www.lacnic.net/en/web/anuncios/2014-no-hay-mas-direcciones-ipv4-en-lac. live.
46. Web site: IPV4 Address Report. 27 January 2007. 6 August 2011. https://web.archive.org/web/20110806020416/http://www.potaroo.net/tools/ipv4/index.html. live.
47. Web site: It's official: North America out of new IPv4 addresses. 2 July 2015. 6 July 2015. 5 July 2015. https://web.archive.org/web/20150705203516/http://arstechnica.com/information-technology/2015/07/us-exhausts-new-ipv4-addresses-waitlist-begins. live.
48. Web site: information on ARIN website. ARIN. 3 February 2011. https://web.archive.org/web/20110628195409/https://www.arin.net/resources/request/ipv4_depletion.html. 28 June 2011. dead.
49. Web site: ARIN IPv4 Countdown Plan. ARIN. 3 February 2011. 16 June 2014. 25 June 2014. https://web.archive.org/web/20140625120144/https://www.arin.net/resources/request/ipv4_countdown.html. live.
50. Web site: AFRINIC . AFRINIC Enters IPv4 Exhaustion Phase 1 . 2022-09-02 . www.afrinic.net . en-gb.
51. News: 2020-01-13 . AFRINIC enters IPv4 Exhaustion Phase 2 . en-gb . 2022-09-02.
52. Web site: RIPE NCC. The RIPE NCC has run out of IPv4 Addresses. https://web.archive.org/web/20200402212112/https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses. 2 April 2020. November 25, 2019. July 20, 2022.
53. Web site: APNIC – Policies for IPv4 address space management in the Asia Pacific region. APNIC. 2 December 2011. dead. https://web.archive.org/web/20111118105210/http://www.apnic.net/policy/add-manage-policy#9.4. 18 November 2011.
54. Web site: APNIC – Policies for IPv4 address space management in the Asia Pacific region. APNIC. 2 December 2011. dead. https://web.archive.org/web/20111118105210/http://www.apnic.net/policy/add-manage-policy#9.10. 18 November 2011.
55. Web site: APNIC – IPv4 exhaustion details. APNIC. 3 February 2011. 2 December 2011. 2 December 2011. https://web.archive.org/web/20111202073042/http://www.apnic.net/community/ipv4-exhaustion/ipv4-exhaustion-details. live.
56. Web site: IPv4 exhaustion details. APNIC. 2 February 2011. 15 December 2010. https://web.archive.org/web/20101215042000/http://www.apnic.net/community/ipv4-exhaustion/ipv4-exhaustion-details. live.
57. Web site: No more addresses: Asia-Pacific region IPv4 well runs dry. Ars Technica . 15 April 2011. 16 April 2011. 22 August 2011. https://web.archive.org/web/20110822141932/http://arstechnica.com/tech-policy/news/2011/04/no-more-addresses-asia-pacific-region-ipv4-well-runs-dry.ars. live.
58. Web site: prop-095-v003: Inter-RIR IPv4 address transfer proposal. Tomohiro Fujisaki. 24 February 2011. 9 November 2011. dead. https://web.archive.org/web/20120325193800/http://www.apnic.net/__data/assets/text_file/0017/31607/prop-095-v003.txt. 25 March 2012.
59. Web site: Draft Policy ARIN-2011-1: ARIN Inter-RIR Transfers. 14 October 2011. 9 November 2011. https://web.archive.org/web/20120406113325/https://www.arin.net/policy/proposals/2011_1.html. 6 April 2012. dead.
60. Web site: APNIC Registered IPV4 Brokers. dead. https://web.archive.org/web/20150911183251/https://www.apnic.net/services/become-a-member/manage-your-membership/transfer-resources/transfer-facilitators. 11 September 2015.
61. Web site: Exec: No shortage of Net addresses. https://web.archive.org/web/20050405150445/http://news.zdnet.com/2100-1009_22-1020653.html. June 24, 2003. April 5, 2005. July 20, 2022. John. Lui. ZDNet News.
62. ARIN Board Advises Internet Community on Migration to IPv6. ARIN. 21 May 2007. 1 July 2007. 15 October 2008. https://web.archive.org/web/20081015131752/http://www.arin.net/announcements/2007/20070521.html. live.
63. LACNIC announces the imminent depletion of the IPv4 addresses. LACNIC. 21 June 2007. 1 July 2007. dead. https://archive.today/20120629193807/http://lacnic.net/en/anuncios/2007_agotamiento_ipv4.html. 29 June 2012. dmy-all.
64. JPNIC releases statement on IPv4 consumption. APNIC. 26 June 2007. 1 July 2007. dead. https://web.archive.org/web/20120403160948/http://www.apnic.net/publications/news/2007/jpnic-ipv4. 3 April 2012. dmy-all.
65. About IPv4 address exhaustion in Internet Registries. JPNIC. 19 June 2007. ja. 1 July 2007. 7 October 2007. https://web.archive.org/web/20071007120338/http://www.nic.ad.jp/ja/ip/ipv4pool/ipv4pool-JPNIC-070619.pdf. live.
66. Web site: RIPE 55 – Meeting Report. RIPE NCC. 26 October 2007. 2 February 2011. 4 September 2011. https://web.archive.org/web/20110904204619/http://www.ripe.net/ripe/meetings/ripe-meetings/ripe-55. live.
67. Web site: Notice of Internet Protocol version 4 (IPv4) Address Depletion. 3 February 2011. https://web.archive.org/web/20100107095025/https://www.arin.net/knowledge/about_resources/ceo_letter.pdf. 7 January 2010. dead.
68. News: Lauren. White. ARIN and Caribbean Telecommunications Union Host Premier Internet Community Meeting. 25 August 2009. 27 August 2009. "The global Internet community is playing a crucial role in the effort to raise awareness of IPv4 depletion and the plan to deploy IPv6, as only 10.9% of IPv4 address space currently remains.". https://web.archive.org/web/20150430111203/http://www.businesswire.com/portal/site/google/?ndmViewId=news_view&newsId=20090825005958&newsLang=en. 30 April 2015. live.
69. Web site: IPv4 Exhaustion: LACNIC Has Assigned the Last Remaining Address Block. 21 August 2020. www.lacnic.net. 24 September 2020. https://web.archive.org/web/20200924030648/https://www.lacnic.net/4848/2/lacnic/ipv4-exhaustion:-lacnic-has-assigned-the-last-remaining-address-block. live.
70. Web site: Proposed Global Policy for the Allocation of the Remaining IPv4 Address Space. RIPE NCC. 3 March 2008. 10 November 2010. dead. https://web.archive.org/web/20101123213823/http://www.ripe.net/ripe/policies/proposals/2008-03.html. 23 November 2010.
71. Web site: APNIC transfer policy. APNIC. 10 February 2010. 3 February 2011. dead. https://wayback.archive-it.org/all/20150605013929/https://www.apnic.net/policy/resources. 5 June 2015.
72. Web site: ARIN transfer policy. ARIN. 3 February 2011. 13 May 2011. https://web.archive.org/web/20110513234347/https://www.arin.net/resources/transfers/index.html. live.
73. Web site: Ripe FAQ. RIPE. 3 February 2011. 19 August 2011. https://web.archive.org/web/20110819105045/http://www.ripe.net/lir-services/resource-management/faq/faq-ipv6#2. live.
74. Web site: Wilson. Paul. Michaelson, George. Huston, Geoff. Redesignation of 240/4 from "Future Use" to "Limited Use for Large Private Internets" (expired draft). 29 September 2008 . 5 April 2010. 18 October 2010. https://web.archive.org/web/20101018052708/http://tools.ietf.org/html/draft-wilson-class-e-02. live.
75. Reclassifying 240/4 as usable unicast address space (expired draft). IETF. 24 March 2008. V. Fuller. E. Lear. D. Meyer. 10 November 2010. 20 October 2009. https://web.archive.org/web/20091020013805/http://tools.ietf.org/html/draft-fuller-240space-02. live.
76. Web site: Hain. Tony. A Pragmatic Report on IPv4 Address Space Consumption. 14 November 2007. 6 August 2011. https://web.archive.org/web/20110806165335/http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_8-3/ipv4.html. dead.
77. Web site: Microsoft. Address Classes. 14 November 2007. 15 September 2008. https://web.archive.org/web/20080915040055/http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnbb_tcp_zrnh.mspx?mfr=true. live.
78. Web site: van Beijnum. Iljitsch. IPv4 Address Consumption. 14 November 2007. 10 September 2011. https://web.archive.org/web/20110910155253/http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_10-3/103_addr-cons.html. dead.
79. Web site: Cisco Systems. TCP/IP Overview. 14 November 2007. dead. https://archive.today/20110817230702/http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwhubs/starvwug/83428.htm. 17 August 2011.
80. Web site: Marsan. Carolyn. Stanford move rekinds 'Net address debate. https://web.archive.org/web/20150210092606/http://www.computerworld.com.au/article/89028/stanford_move_rekindles_net_address_debate. dead. 10 February 2015. Computerworld. 22 January 2000. 29 June 2010.
81. Web site: ARIN Recognizes Interop for Returning IPv4 Address Space. ARIN. 20 October 2010. 3 February 2011. 3 June 2011. https://web.archive.org/web/20110603233616/https://www.arin.net/announcements/2010/20101020.html. live.
82. News: Pssst! Rare IPv4 Addresses For Sale! Get Them While You Can!. Phil Lodico. 15 September 2011. Forbes. 1 September 2017. 5 May 2017. https://web.archive.org/web/20170505131745/https://www.forbes.com/sites/ciocentral/2011/09/15/pssst-rare-ipv4-addresses-for-sale-get-them-while-you-can. live.
83. Web site: dead . The State of the Internet: IPv4 Won't Die. https://web.archive.org/web/20130617064125/http://www.technologyreview.com/view/424831/the-state-of-the-internet-ipv4-wont-die/. Kristina. Bjoran. 27 July 2011. 17 June 2013.
84. Web site: IPv6: Unstoppable Force Meets Immovable Object. Steve Wexler. 18 October 2011. 5 December 2011. https://web.archive.org/web/20120120091942/http://www.networkcomputing.com/ipv6-tech-center/231900971. 20 January 2012. dead.
85. Web site: IPv6 will change network attack surface, albeit slowly: Huston. David Braue. 20 October 2011. 5 December 2011. 22 November 2011. https://web.archive.org/web/20111122235125/http://www.cso.com.au/article/404785/ipv6_will_change_network_attack_surface_albeit_slowly_huston. live.
86. Web site: IPv6 Will Cause Some Security Headaches. Elizabeth Harrin. 22 September 2011. 5 December 2011. 28 November 2011. https://web.archive.org/web/20111128144112/http://www.esecurityplanet.com/network-security/ipv6-will-cause-some-security-headaches.html. live.
87. Web site: Mueller. Milton. It's official: Legacy IPv4 address holders own their number blocks. 22 September 2012. Internet governance Project. 22 February 2013. 4 April 2013. https://web.archive.org/web/20130404144758/http://www.internetgovernance.org/2012/09/22/its-official-legacy-ipv4-address-block-holders-own-their-number-blocks. live.
88. Web site: Andrew. Dul. Legacy IPv4 Address standing with USG. 22 February 2013. 31 May 2013. https://web.archive.org/web/20130531065939/http://www.ipaddressnews.com/2013/02/04/192. live.
89. Web site: Strickling. Lawrence. United States Government's Internet Protocol Numbering Principles. USG/NTIA. 22 February 2013. 21 February 2013. https://web.archive.org/web/20130221072853/http://www.ntia.doc.gov/blog/2012/united-states-government-s-internet-protocol-numbering-principles. live.
90. News: Microsoft Spends $7.5M on 666K Nortel IPv4 Addresses. Chloe Albanesius. PCMag. 25 March 2011. 1 September 2017. 11 July 2017. https://web.archive.org/web/20170711144509/http://www.pcmag.com/article2/0,2817,2382616,00.asp. live.
91. Web site: Microsoft spends $7.5 million on IP addresses. Kevin Murphy. Domain Incite. 24 March 2011. 24 March 2011. 27 August 2011. https://web.archive.org/web/20110827140035/http://domainincite.com/microsoft-spends-7-5-million-on-ip-addresses. live.
92. Web site: Resource Transfers: Returning Unneeded IPv4 Address Space. ARIN. 1 February 2011. 13 May 2011. https://web.archive.org/web/20110513234347/https://www.arin.net/resources/transfers/index.html. live.
93. Web site: IPv4 address transfers must meet policy, ARIN chief says. Jaikumar Vijayan. 25 March 2011. 26 March 2011. 19 January 2012. https://web.archive.org/web/20120119203306/http://www.computerworld.com/s/article/9215091/IPv4_address_transfers_must_meet_policy_ARIN_chief_says. live.
94. Web site: Why IPv4 is Here to Stay, Part 2: Show Me the Money. Ramuglia. Gabriel. 16 February 2015. The Web Host Industry Review. 27 February 2015. 20 February 2015. https://web.archive.org/web/20150220142655/http://www.thewhir.com/blog/ipv4-stay-part-2-show-money. dead.
95. RFC 6333 - Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
96. Bush. Randy. R . Bush . The Address plus Port (A+P) Approach to the IPv4 Address Shortage. tools.ietf.org. August 2011. 10.17487/RFC6346 . en. 12 January 2021. 3 December 2020. https://web.archive.org/web/20201203075044/https://tools.ietf.org/html/rfc6346. live.