RFC 6180: Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment

The Internet continues to grow beyond the capabilities of IPv4. An expansion in the address space is clearly required. With its increase in the number of…

Read RFC 6180 on the RFC Editor

Outgoing relationships (35 related RFCs)

Normative reference — RFC 4301: Security Architecture for the Internet Protocol
Normative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Normative reference — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Normative reference — RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
Normative reference — RFC 3484: Default Address Selection for Internet Protocol version 6 (IPv6)
Normative reference — RFC 5555: Mobile IPv6 Support for Dual Stack Hosts and Routers
Normative reference — RFC 5565: Softwire Mesh Framework
Normative reference — RFC 5454: Dual-Stack Mobile IPv4
Informative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Informative reference — RFC 3056: Connection of IPv6 Domains via IPv4 Clouds
Informative reference — RFC 1981: Path MTU Discovery for IP version 6
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 5844: IPv4 Support for Proxy Mobile IPv6
Informative reference — RFC 5969: IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
Informative reference — RFC 6144: Framework for IPv4/IPv6 Translation
Informative reference — RFC 6169: Security Concerns with IP Tunneling
Informative reference — RFC 2993: Architectural Implications of NAT
Informative reference — RFC 4798: Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)
Informative reference — RFC 5218: What Makes for a Successful Protocol?
Informative reference — RFC 4038: Application Aspects of IPv6 Transition
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)
Informative reference — RFC 3053: IPv6 Tunnel Broker
Informative reference — RFC 3314: Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards
Informative reference — RFC 4057: IPv6 Enterprise Network Scenarios
Informative reference — RFC 4029: Scenarios and Analysis for Introducing IPv6 into ISP Networks
Informative reference — RFC 4215: Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks
Informative reference — RFC 4852: IPv6 Enterprise Network Analysis - IP Layer 3 Focus
Informative reference — RFC 6036: Emerging Service Provider Scenarios for IPv6 Deployment
Informative reference — RFC 3574: Transition Scenarios for 3GPP Networks
Informative reference — RFC 5181: IPv6 Deployment Scenarios in 802.16 Networks
Informative reference — RFC 5211: An Internet Transition Plan
Informative reference — RFC 6127: IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios

Incoming relationships (3 related RFCs)

Normatively referenced by — RFC 9313: Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
Normatively referenced by — RFC 9386: IPv6 Deployment Status
Normatively referenced by — RFC 6782: Wireline Incremental IPv6