Difference Between IPv4 vs IPv6 and Internet Governance

In February 2011, the Internet Assigned Numbers Authority (IANA) made a quiet announcement that had enormous implications: it had officially exhausted the global pool of unallocated IPv4 addresses. The last blocks had been distributed to the five Regional Internet Registries. There were no more to give out.

To understand why this matters — and why the internet still functions despite it — you need to understand the difference between IPv4 and IPv6, how those two addressing systems are governed, and why the transition between them is one of the most consequential and slowest-moving processes in the history of internet governance.

This is not just a technical story. It is a governance story. The decisions about how IP addresses are allocated, who gets to claim them, how the transition to IPv6 is managed, and who bears the cost of that transition are decisions that affect internet access, digital inclusion, and the distribution of power on the internet for decades to come.

📌  The Bottom Line:  IPv4 gives the internet approximately 4.3 billion unique addresses — not enough for the modern world. IPv6 gives it 340 undecillion addresses — effectively unlimited. The shift from one to the other is being managed by IANA, five Regional Internet Registries, and the internet governance community through a complex, multi-decade transition that is still very much in progress.

What Is an IP Address, and Why Do We Need Two Systems?

An IP address is the numerical identifier assigned to every device that connects to the internet. It is how the network knows where to send your email, your web page request, your video stream. Without a unique IP address, your device has no way to be found or to reach anything else on the internet.

IPv4 — Internet Protocol version 4 — was the first widely deployed version of this system. Defined by the IETF in RFC 791 in 1981, it uses 32-bit addresses, which means it can theoretically produce about 4.3 billion unique addresses. At the time, that seemed like more than enough. The internet was a research network with a few thousand users, not a global infrastructure serving billions of people and billions of devices.

IPv6 — Internet Protocol version 6 — was designed in the 1990s specifically because it was clear that IPv4 would eventually run out. IPv6 uses 128-bit addresses, producing approximately 340 undecillion unique addresses — a number so large that it is essentially unlimited by any practical measure. Every square centimeter of the Earth’s surface could be assigned billions of IPv6 addresses and there would still be room to spare.

The reason we have two systems running simultaneously — rather than having simply switched from one to the other — is governance. Transitioning the global internet’s addressing infrastructure is not a technical operation that someone flips a switch to complete. It requires coordination across hundreds of thousands of networks, policy changes at national and regional levels, investment by ISPs and network operators, and sustained political will from the internet governance community. That coordination has been underway for decades, and it is still not finished.

IPv4 vs IPv6 Internet Governance: How the Two Systems Are Managed Differently?

From a pure technical standpoint, IPv4 and IPv6 work on similar principles — they both route data packets across networks using numerical addresses. But from a governance standpoint, the two systems present very different challenges and require very different policy approaches.

IPv4 Governance: Managing Scarcity

IPv4 governance today is almost entirely about scarcity management. IANA exhausted its unallocated IPv4 pool in 2011. The five RIRs — ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC — subsequently exhausted their own free pools at different points, with APNIC running out first in 2011, RIPE NCC in 2012, ARIN in 2015, and LACNIC and AFRINIC reaching critical thresholds more recently.

What this means in practice is that the IPv4 address space is now managed as a finite resource under rationing and reclamation policies. Each RIR has developed its own policies — through open, multistakeholder community processes — for how to handle waiting lists, legacy address space, transfers between organizations, and the return of addresses from organizations that no longer need them.

A secondary market for IPv4 addresses has also developed, where organizations sell unused blocks of IPv4 space to others that need it. ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC all have different policies governing whether and how such transfers are permitted within their regions, and whether cross-regional transfers are allowed. These transfer policies have become some of the most actively debated policy questions in the RIR community, because they raise fundamental questions about whether IPv4 addresses are a public resource to be allocated in the public interest or private property to be traded on the market.

IPv6 Governance: Managing a New Abundance — and New Inequalities

IPv6 governance faces a different set of challenges. Because the address space is effectively unlimited, the governance question is not how to ration scarcity but how to ensure that IPv6 deployment happens equitably, that the transition is managed in a way that does not leave developing nations and smaller network operators behind, and that the policies governing IPv6 allocation serve the public interest of a truly global internet.

IANA allocates large blocks of IPv6 address space to the five RIRs, which then develop their own allocation policies for distributing IPv6 to ISPs and organizations. The allocation policies for IPv6 have generally been more generous than those for IPv4, reflecting the abundance of address space available. But deployment is a different question from allocation — an organization can hold an IPv6 allocation while its network still operates entirely on IPv4.

One of the most significant governance challenges for IPv6 is the digital divide it risks creating. Larger, wealthier network operators in developed economies have had the resources to deploy IPv6 infrastructure and train staff to manage it. Smaller ISPs and network operators in developing regions have often lacked the capital, technical capacity, or regulatory incentives to prioritize IPv6 deployment. The result is uneven IPv6 adoption globally — and an internet where the organizations best positioned to serve the next billion users may be the least prepared for the addressing infrastructure those users will need.

The RIRs and IANA: Governing the Global Address Space

The governance of both IPv4 and IPv6 flows through the same institutional hierarchy: IANA at the top, the five Regional Internet Registries in the middle, and ISPs and organizations at the bottom. But the way this hierarchy functions has evolved significantly as the IPv4 scarcity problem has intensified and as IPv6 deployment has gradually expanded.

IANA’s role in IP address governance is to maintain the authoritative records of global address allocations and to coordinate allocations to the RIRs based on demonstrated need and established policy. For IPv4, IANA’s function is now largely archival — it maintains the record of what blocks were allocated to which RIR, but there is no free pool left to allocate from. For IPv6, IANA continues to make allocations to the RIRs as they demonstrate need, though the scale of the IPv6 space makes these allocations less urgent than IPv4 allocations were.

Each of the five RIRs — APNIC (Asia Pacific), ARIN (North America), RIPE NCC (Europe, Middle East, Central Asia), LACNIC (Latin America and Caribbean), and AFRINIC (Africa) — develops its own address policies through open, bottom-up, community-driven processes. Any member of the internet community can propose a policy change, which is then debated in public forums and mailing lists before being adopted or rejected by the RIR’s community. This decentralized, open policy development model is one of the most distinctive features of internet governance and is often cited as a model of effective multistakeholder governance.

IPv4 vs IPv6: A Governance and Technical Comparison

Feature	IPv4	IPv6
Address format	32-bit — e.g. 192.168.1.1	128-bit — e.g. 2001:0db8:85a3::8a2e:0370:7334
Total addresses	~4.3 billion	~340 undecillion (3.4 x 10^38)
IANA pool status	Exhausted — February 2011	Active — ongoing allocations to RIRs
Governance challenge	Scarcity management, transfer policy	Deployment equity, transition policy, adoption incentives
Security features	Security optional (IPsec add-on)	Security built-in (IPsec mandatory in original spec)
NAT use	Common — masks multiple devices behind one IP	Not needed — every device can have unique global address
RIR allocation status	Very limited; waiting lists in most regions	Abundant; RIRs allocating generously
Global deployment (2026)	~98% of internet traffic — still dominant	~40-45% of internet traffic — growing steadily
Key governance bodies	IANA, 5 RIRs, NRO, IETF	Same — plus national regulators pushing deployment mandates
Policy debate focus	Transfer markets, legacy address space	IPv6-only networks, transition mechanisms, digital divide

Who Is Governing the IPv4-to-IPv6 Transition?

The transition from IPv4 to IPv6 does not have a single governing authority, a single deadline, or a single responsible party. It is governed — like most aspects of the internet — through a distributed, multistakeholder system in which different organizations play complementary roles.

IANA: The Coordinator at the Top IANA maintains the authoritative records of global address allocations for both IPv4 and IPv6. While the IPv4 free pool is exhausted, IANA continues to coordinate IPv6 allocations to the RIRs and maintains the global number resource registry that underpins the entire IP addressing system. IANA’s coordination role ensures that the address spaces of the five RIRs do not overlap and that the global routing system remains coherent.

The Five RIRs: Policy Makers and Allocators APNIC, ARIN, RIPE NCC, LACNIC, and AFRINIC are where most of the active governance of both IPv4 and IPv6 happens in practice. Their open policy processes determine who gets addresses, under what conditions, at what cost, and with what accountability obligations. The Number Resource Organization (NRO), which brings together all five RIRs, coordinates on cross-regional issues and represents the RIR community in global internet governance forums including ICANN and the IGF.

The IETF: Standards That Enable Transition The IETF (Internet Engineering Task Force) defines the technical standards that make IPv6 work and that govern how networks can operate both IPv4 and IPv6 simultaneously (dual-stack) or convert between them (translation mechanisms). IETF working groups have developed dozens of RFCs governing different aspects of IPv6 operation and the transition from IPv4, including standards for NAT64 (translation between IPv6 and IPv4 networks), 464XLAT (enabling IPv4 applications to work on IPv6-only networks), and various other transition mechanisms.

National Governments and Regulators: The Emerging Force Increasingly, national governments and telecommunications regulators have become active players in IPv6 governance. India’s Department of Telecommunications issued a directive requiring ISPs to deploy IPv6. The US Office of Management and Budget has set IPv6 deployment targets for federal agencies. The European Commission has published recommendations on IPv6 adoption for member states. This growing regulatory dimension of IPv6 governance reflects governments’ recognition that the transition to IPv6 is not just a technical matter for the internet community — it has implications for national digital infrastructure, economic competitiveness, and digital inclusion.

IGF and ISOC: The Broader Governance Conversation The Internet Governance Forum (IGF) has hosted discussions on IPv6 transition and the governance implications of IPv4 scarcity for over a decade. The Internet Society (ISOC) has been one of the most active advocates for IPv6 deployment, publishing measurement data on global adoption rates, advocating for policy changes that incentivize deployment, and running World IPv6 Launch events that coordinated major ISPs and content providers to enable IPv6 on a global scale. ISOC’s Pulse platform tracks real-time IPv6 deployment statistics by region and provider.

IPv4 Scarcity, IPv6 Adoption, and the Digital Divide

The governance of IPv4 and IPv6 is not neutral with respect to global equity. The depletion of the IPv4 free pool has had very different effects in different parts of the world, and the pace of IPv6 adoption has not been uniform.

Countries and organizations that obtained large IPv4 allocations early — particularly in North America and Europe, where the internet first developed commercially — hold address resources that are now worth significant money on the secondary market. Organizations in regions where the internet developed later, particularly in Africa and parts of Asia, received far smaller allocations before the pool ran out. This historical inequity in IPv4 allocation is one of the persistent governance grievances in the RIR community, and it has shaped debates about how the remaining IPv4 space should be managed.

The IPv6 transition offers an opportunity to reset some of these historical inequities — IPv6 address space is abundant enough that every organization in every country can receive a generous allocation, without the scarcity dynamics that characterized IPv4. But converting that opportunity into reality requires investment in network infrastructure, training, and regulatory frameworks that make IPv6 deployment economically rational for ISPs in developing markets. Without deliberate governance attention to this dimension, the IPv6 era risks replicating the connectivity gaps of the IPv4 era rather than resolving them.

IPv4 vs IPv6 and Internet Governance: Key Facts

Fact	Detail
IPv4 designed	1981 — RFC 791, Internet Engineering Task Force
IPv6 designed	1998 — RFC 2460, IETF; updated RFC 8200 (2017)
IANA IPv4 pool exhausted	February 2011 — last /8 blocks allocated to RIRs
First RIR to exhaust IPv4	APNIC — April 2011
Global IPv6 traffic (2026)	Approximately 40-45% of internet traffic (APNIC measurement data)
IPv6 enabled countries	India leads deployment; US federal mandate from OMB; EU recommendations in place
NRO function	Number Resource Organization — coordinates the 5 RIRs on cross-regional issues
IPv4 transfer markets	Active in ARIN, RIPE NCC, APNIC regions — policy-governed transfers between organizations
World IPv6 Launch	June 6, 2012 — ISOC-coordinated event enabling IPv6 on major ISPs and websites globally
ISOC Pulse	Free real-time IPv6 deployment tracking by country and provider at pulse.internetsociety.org

Frequently Asked Questions

Q1: Why hasn’t the world simply switched from IPv4 to IPv6 already?

The short answer is that switching the internet’s addressing infrastructure is enormously complex and expensive. Every router, server, operating system, and application that handles IP traffic needs to support IPv6, and billions of pieces of equipment worldwide were built for IPv4. Operators face a chicken-and-egg problem: content providers are reluctant to invest in IPv6 until users have IPv6 access, and ISPs are reluctant to deploy IPv6 until content is available over it. This coordination problem, combined with the cost of transition and the short-term viability of workarounds like NAT (Network Address Translation), has slowed the transition for decades despite its technical necessity.

Q2: What is NAT, and does it solve the IPv4 address shortage?

NAT — Network Address Translation — is a technique that allows many devices to share a single public IPv4 address by mapping their private IP addresses to a single public one. Your home router almost certainly uses NAT: all your devices have private IP addresses, but they share one public IPv4 address when communicating with the internet. NAT has effectively extended the life of the IPv4 address space by decades, but it introduces complications: it breaks end-to-end connectivity (some applications cannot work properly through NAT), it adds complexity to networks, and it creates a layer of obscurity that can complicate security monitoring. NAT is a workaround, not a solution — and from a governance perspective, it does not solve the fundamental issue that IPv4 addresses are running out.

Q3: How do IANA and the RIRs govern IP address allocation differently?

IANA sits at the top of the allocation hierarchy and allocates large blocks (typically /8 blocks for IPv4 and even larger for IPv6) to the five Regional Internet Registries. IANA’s policies are developed through coordination between IANA, the RIRs, and the global community, particularly through the Number Resource Organization (NRO). The RIRs then develop their own, more detailed policies for allocating smaller blocks to ISPs and organizations within their regions — and these policies are developed through each RIR’s own open, community-driven policy process. So IANA sets the framework at the top level, but most of the day-to-day governance of address allocation happens within the five RIR communities.

Q4: What are IPv4 transfer markets, and are they controversial?

IPv4 transfer markets have developed as a result of address exhaustion — organizations that hold unused IPv4 address blocks can sell or transfer them to organizations that need them. All five RIRs have developed policies governing these transfers, though the details vary significantly. The controversy centers on several issues: whether treating address blocks as tradeable commodities is consistent with the original principle that IP addresses are a public resource allocated in the public interest; whether transfer markets advantage wealthy organizations and countries over less-resourced ones; and whether they reduce the incentive for organizations to deploy IPv6. The governance debates around IPv4 transfer markets are among the most active in the RIR community today.

Q5: What is the governance role of the IETF in IPv4 and IPv6?

The IETF (Internet Engineering Task Force) is the standards body responsible for the technical specifications of both IPv4 and IPv6. While IANA and the RIRs govern who gets IP addresses and under what conditions, the IETF governs how IP addressing works technically — defining the protocols, the packet formats, the routing mechanisms, and the transition tools that make IPv4 and IPv6 function. IETF working groups have developed the key transition mechanisms (dual-stack, NAT64, 464XLAT) and continue to work on improving IPv6 features and operability. The IETF’s work and the RIR policy processes are complementary but distinct governance functions.

Q6: How does IPv6 deployment relate to the digital divide?

The digital divide has a direct IPv6 dimension. Organizations in developed markets that received generous IPv4 allocations before exhaustion have been able to delay IPv6 deployment by stretching their existing IPv4 space. Organizations in developing regions, which received smaller IPv4 allocations, face greater pressure to deploy IPv6 but often lack the capital and technical capacity to do so quickly. If IPv6 deployment proceeds faster in wealthy regions than in developing ones, new internet services designed for IPv6-native environments could be harder to access from developing regions, potentially worsening existing connectivity gaps. Addressing this dimension of the IPv4-to-IPv6 transition is increasingly recognized as an internet governance responsibility, not just a technical one.

Q7: What role do national governments play in IPv6 governance?

National governments have become increasingly active in IPv6 governance, particularly through telecommunications regulation and public procurement. Several governments have issued mandates or targets for IPv6 deployment: India’s DoT has required ISPs to deploy IPv6, the US government has set targets for federal agency IPv6 readiness, and the EU has published recommendations for member states. Public procurement policies that require government IT systems to support IPv6 can create significant market incentives for broader deployment. In internet governance forums like the IGF, the role of government mandates versus market-driven IPv6 deployment is an active policy debate.

Q8: How can I follow IPv6 deployment progress and internet governance discussions around it?

Several resources track IPv6 deployment in near-real time. APNIC’s blog (blog.apnic.net) publishes regular measurement data and analysis. ISOC’s Pulse platform (pulse.internetsociety.org) tracks IPv6 adoption by country and ISP. The RIPE NCC, ARIN, LACNIC, and AFRINIC all publish statistics on address allocation and IPv6 deployment within their regions. For governance discussions, each RIR’s public mailing lists and policy forums are open to community participation, and the IGF hosts sessions on IP addressing governance each year. IG Insight at iginsight.org is a great starting point for understanding the governance context before engaging with the technical communities directly.

The Internet’s Address Infrastructure Is Being Rebuilt. The Decisions Being Made Now Will Shape It for Decades. IPv4 exhaustion, IPv6 deployment, transfer market policy, digital divide implications — the governance of IP addresses is not a niche technical debate. It is a question about who gets to be fully present on the internet, under what conditions, and at what cost. These decisions are made in open community forums where your participation is both welcome and needed. Explore more and get involved: Keep Learning at IG Insight Track global IPv6 deployment at pulse.internetsociety.org — free, real-time data Read APNIC Blog at blog.apnic.net for technical and policy analysis on IP addressing Participate in your regional RIR’s policy process — APNIC, ARIN, RIPE NCC, LACNIC, AFRINIC Attend a free RIR community meeting — all five RIRs hold open meetings with remote access Read more on IG Insight: What Is IANA? | What Are RIRs? | How Internet Governance Works Follow IG Insight at iginsight.org for plain-language updates on internet governance The internet’s infrastructure is governed by communities that are open to new voices. IG Insight is your entry point.