RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers

This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. Two mechanisms are specified, dual stack and…

Read RFC 4213 on the RFC Editor

Outgoing relationships (25 related RFCs)

Obsoletes, Informative reference — RFC 2893: Transition Mechanisms for IPv6 Hosts and Routers
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Normative reference — RFC 791: Internet Protocol
Normative reference — RFC 1191: Path MTU discovery
Normative reference — RFC 1981: Path MTU Discovery for IP version 6
Normative reference — RFC 2463: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
Informative reference — RFC 2401: Security Architecture for the Internet Protocol
Informative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Informative reference — RFC 1812: Requirements for IP Version 4 Routers
Informative reference — RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
Informative reference — RFC 2827: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
Informative reference — RFC 3056: Connection of IPv6 Domains via IPv4 Clouds
Informative reference — RFC 2462: IPv6 Stateless Address Autoconfiguration
Informative reference — RFC 3704: Ingress Filtering for Multihomed Networks
Informative reference — RFC 3484: Default Address Selection for Internet Protocol version 6 (IPv6)
Informative reference — RFC 3513: Internet Protocol Version 6 (IPv6) Addressing Architecture
Informative reference — RFC 2983: Differentiated Services and Tunnels
Informative reference — RFC 2890: Key and Sequence Number Extensions to GRE
Informative reference — RFC 3493: Basic Socket Interface Extensions for IPv6
Informative reference — RFC 3596: DNS Extensions to Support IP Version 6
Informative reference — RFC 3232: Assigned Numbers: RFC 1700 is Replaced by an On-line Database
Informative reference — RFC 2923: TCP Problems with Path MTU Discovery
Informative reference — RFC 1435: IESG Advice from Experience with Path MTU Discovery
Informative reference — RFC 4087: IP Tunnel MIB

Incoming relationships (35 related RFCs)

Normatively referenced by — RFC 5844: IPv4 Support for Proxy Mobile IPv6
Normatively referenced by — RFC 5214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
Normatively referenced by — RFC 4459: MTU and Fragmentation Issues with In-the-Network Tunneling
Normatively referenced by — RFC 6434: IPv6 Node Requirements
Normatively referenced by — RFC 5512: The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 4925: Softwire Problem Statement
Normatively referenced by — RFC 6324: Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations
Normatively referenced by — RFC 7421: Analysis of the 64-bit Boundary in IPv6 Addressing
Normatively referenced by — RFC 4891: Using IPsec to Secure IPv6-in-IPv4 Tunnels
Normatively referenced by — RFC 6180: Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
Normatively referenced by — RFC 5211: An Internet Transition Plan
Normatively referenced by — RFC 5454: Dual-Stack Mobile IPv4
Normatively referenced by — RFC 6127: IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios
Normatively referenced by — RFC 6214: Adaptation of RFC 1149 for IPv6
Normatively referenced by — RFC 6219: The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition
Normatively referenced by — RFC 6586: Experiences from an IPv6-Only Network
Normatively referenced by — RFC 5579: Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Interfaces
Normatively referenced by — RFC 6589: Considerations for Transitioning Content to IPv6
Normatively referenced by — RFC 6964: Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
Normatively referenced by — RFC 9386: IPv6 Deployment Status
Informatively referenced by — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Informatively referenced by — RFC 5971: GIST: General Internet Signalling Transport
Informatively referenced by — RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
Informatively referenced by — RFC 6343: Advisory Guidelines for 6to4 Deployment
Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
Informatively referenced by — RFC 5320: The Subnetwork Encapsulation and Adaptation Layer (SEAL)
Informatively referenced by — RFC 5975: QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)
Informatively referenced by — RFC 6619: Scalable Operation of Address Translators with Per-Interface Bindings
Informatively referenced by — RFC 7094: Architectural Considerations of IP Anycast
Informatively referenced by — RFC 7381: Enterprise IPv6 Deployment Guidelines
Informatively referenced by — RFC 5720: Routing and Addressing in Networks with Global Enterprise Recursion (RANGER)
Informatively referenced by — RFC 5979: NSIS Operation over IP Tunnels
Informatively referenced by — RFC 7059: A Comparison of IPv6-over-IPv4 Tunnel Mechanisms
Informatively referenced by — RFC 8952: Captive Portal Architecture
Informatively referenced by — RFC 6312: Mobile Networks Considerations for IPv6 Deployment