RFC 6127: IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios

When IPv6 was designed, it was expected that the transition from IPv4 to IPv6 would occur more smoothly and expeditiously than experience has revealed. The…

Read RFC 6127 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 1918: Address Allocation for Private Internets
Normative reference — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Informative reference — RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
Informative reference — RFC 6052: IPv6 Addressing of IPv4/IPv6 Translators
Informative reference — RFC 6147: DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
Informative reference — RFC 6145: IP/ICMP Translation Algorithm
Informative reference — RFC 6144: Framework for IPv4/IPv6 Translation
Informative reference — RFC 6169: Security Concerns with IP Tunneling
Informative reference — RFC 4925: Softwire Problem Statement
Informative reference — RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
Informative reference — RFC 2766: Network Address Translation - Protocol Translation (NAT-PT)

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 6180: Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
Informatively referenced by — RFC 6619: Scalable Operation of Address Translators with Per-Interface Bindings