RFC 6346: The Address plus Port (A+P) Approach to the IPv4 Address Shortage

We are facing the exhaustion of the IANA IPv4 free IP address pool. Unfortunately, IPv6 is not yet deployed widely enough to fully replace IPv4, and it is…

Read RFC 6346 on the RFC Editor

Incoming relationships (13 related RFCs)

Normatively referenced by — RFC 7599: Mapping of Address and Port using Translation (MAP-T)
Normatively referenced by — RFC 9313: Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
Informatively referenced by — RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
Informatively referenced by — RFC 8900: IP Fragmentation Considered Fragile
Informatively referenced by — RFC 7596: Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
Informatively referenced by — RFC 7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
Informatively referenced by — RFC 6967: Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments
Informatively referenced by — RFC 7269: NAT64 Deployment Options and Experience
Informatively referenced by — RFC 7618: Dynamic Allocation of Shared IPv4 Addresses
Informatively referenced by — RFC 7620: Scenarios with Host Identification Complications
Informatively referenced by — RFC 8992: Autonomic IPv6 Edge Prefix Management in Large-Scale Networks
Informatively referenced by — RFC 7600: IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)
Informatively referenced by — RFC 7974: An Experimental TCP Option for Host Identification