Why IPv4 Still Dominates and How IPv6 Can Solve the Address Crisis

IPv4 vs IPv6 Fundamentals

IPv4 is defined in RFC 791 (1981) and uses 32‑bit addresses, giving a total of about 4.3 billion addresses (≈3.7 billion usable). Addresses are written in dotted‑decimal notation, e.g., 192.168.1.1. The IPv4 header length varies from 20 to 60 bytes because optional fields can be present.

IPv6 is defined in RFC 2460 (1998) and formally standardised in 2017. It uses 128‑bit addresses, providing roughly 3.4 × 10^38 unique identifiers. Addresses are expressed in hexadecimal with "::" compression, e.g., 2001:db8::1. The IPv6 header has a fixed size of 40 bytes, which simplifies processing in routers.

Key Comparative Metrics

Address space: IPv4 ~4.3 billion vs IPv6 ~3.4 × 10^38.

Header size: IPv4 20‑60 bytes (variable) vs IPv6 40 bytes (fixed).

NAT requirement: IPv4 typically needs NAT/CGNAT; IPv6 provides native end‑to‑end connectivity.

Automatic configuration: IPv4 relies on stateful DHCP; IPv6 prefers stateless SLAAC with optional DHCPv6.

Security: IPsec is optional in IPv4 but mandatory in IPv6.

Global traffic share (2026): IPv4 ≈53 % vs IPv6 ≈47 % (Google measurement).

IPv4 Exhaustion and NAT/CGNAT Mitigation

The IPv4 address pool was exhausted in 2011. IANA allocated the final /8 blocks to regional registries, which subsequently depleted. China’s CNISP exhausted its pool in 2019. To keep the Internet operational, operators deployed Network Address Translation (NAT) and Carrier‑Grade NAT (CGNAT), allowing thousands of customers to share a single public IPv4 address.

By 2026 the secondary‑market price for a single IPv4 address rose to US $50‑80, because buying IPv4 + CGNAT remains cheaper than a full IPv6 migration.

Drawbacks of NAT/CGNAT

Breaks true end‑to‑end connectivity (affects P2P, VoIP, gaming, IoT).

Introduces additional latency of roughly 5‑20 ms due to double translation.

Port exhaustion can cause connection failures.

Complicates traffic tracing and forensic analysis.

Root Causes of Continued IPv4 Dominance

Legacy equipment: Billions of routers, firewalls, servers, printers, and industrial devices support only IPv4.

Dual‑stack complexity: Running IPv4 and IPv6 simultaneously doubles routing tables, ACLs, and monitoring overhead.

Migration cost: A medium‑size data centre may require several hundred thousand USD (or HKD) to transition fully to IPv6.

Skill gap: Many network engineers lack experience with IPv6 SLAAC, Neighbor Discovery, and related protocols.

Content provider bias: Numerous web services remain IPv4‑only, discouraging end‑user adoption.

Performance misconceptions: Modern ASICs forward IPv6 packets faster than IPv4, contrary to some beliefs.

Short‑term cost mindset: Purchasing IPv4 addresses and applying CGNAT appears cheaper in the near term.

Why IPv6 Is Essential

Abundant address space: Enables assigning tens of thousands of unique addresses per server, critical for AI clusters, IoT, and edge devices.

Native end‑to‑end connectivity: Supports P2P, WebRTC, remote desktop, and other latency‑sensitive applications without translation.

Simplified provisioning: SLAAC + Router Advertisements provide plug‑and‑play addressing; DHCPv6 can be used for additional parameters.

Built‑in security: IPsec is mandatory, facilitating encrypted traffic by default.

Future‑proofing: 5G/6G, edge computing, digital twins, and massive IoT deployments rely on IPv6 scalability.

Projected Trends

Global traffic is expected to shift toward IPv6 dominance within the next few years, while IPv4 address market prices will continue to rise.