IPv4 & IPv6 Dual-Stack Protocol Architecture
In-depth technical analysis of the global Internet protocol transition. Learn how operating systems negotiate dual-stack routing, prevent IPv6 black holes, and manage address scopes.
Quick Answer
IPv4 and IPv6 operate as parallel, independent network layer protocols. A dual-stack client maintains both an IPv4 and IPv6 socket. Happy Eyeballs (RFC 8305) ensures that if an ISP has broken or unoptimized IPv6 routing, the browser falls back to IPv4 within 250ms without dropping the user's connection.
- IPv4 address exhaustion made Carrier-Grade NAT (CGNAT 100.64.0.0/10) standard for home ISPs.
- IPv6 eliminates NAT, restoring the original end-to-end connectivity principle of the Internet.
- SLAAC (Stateless Address Autoconfiguration) allows devices to generate their own IP from a network prefix.
Address Scope and Type Classification
Understanding the standard prefixes and designated scopes of IPv4 and IPv6.
| Scope / Function | IPv4 Definition | IPv6 Equivalent | Routability |
|---|---|---|---|
| Loopback | 127.0.0.1/8 | ::1/128 | Internal device only (Never reaches wire) |
| Private / Internal | RFC 1918 (10.0.0.0/8, 192.168.0.0/16) | ULA fc00::/7 (Unique Local) | LAN only (Filtered at WAN border) |
| Link-Local Auto | 169.254.0.0/16 (APIPA) | fe80::/10 (Mandatory on all v6 interfaces) | Single broadcast segment (Zero routing) |
| Carrier-Grade NAT | 100.64.0.0/10 (RFC 6598) | Not applicable (Public v6 is abundant) | ISP internal transport network |
| Global Public Unicast | Public pool (e.g. 1.1.1.1) | 2000::/3 (All public routable IPv6) | Globally routed across all Tier-1 transit |
Dual-Stack Diagnostics & Fallback Decision Tree
[ Check Native IPv6 Support ]
|
+---------------+---------------+
| |
[ Test Succeeds ] [ Test Fails ]
| |
Dual-Stack Active +---------+---------+
| | |
Happy Eyeballs Races [ Router Disabled ] [ ISP Unsupported ]
| | |
Optimal Route Selected Enable SLAAC/DHCPv6 Request /64 Prefix
Frequently Asked Questions
Why does my device have multiple IPv6 addresses?
Under RFC 4941 (Privacy Extensions for SLAAC), modern operating systems generate both a stable global IPv6 address (for inbound connections) and temporary randomized IPv6 addresses that rotate daily for outbound web browsing. This prevents long-term hardware fingerprinting via your network interface card MAC address.
What is Happy Eyeballs (RFC 8305)?
Happy Eyeballs is an algorithm implemented in web browsers and operating systems that races dual-stack connection attempts. When a user requests a domain, the browser queries both A (IPv4) and AAAA (IPv6) records. It starts an IPv6 connection first, and if no SYN-ACK handshake is received within roughly 250 milliseconds, it immediately falls back to IPv4, preventing broken IPv6 networks from freezing the user experience.
Does IPv6 make my internet connection faster?
In many real-world scenarios, yes. Native IPv6 routes bypass Carrier-Grade NAT (CGNAT) gateway middleboxes, reducing round-trip latency by 5ms to 20ms and eliminating packet loss caused by stateful translation table exhaustion.
Data & Technical Sources
- IETF RFC 8200 — Internet Protocol, Version 6 (IPv6) Specification (Standard 86)
- IETF RFC 8305 — Happy Eyeballs Version 2: Better Connectivity Using Concurrency
- IETF RFC 4941 — Privacy Extensions for SLAAC in IPv6