RFC 3056: Connection of IPv6 Domains via IPv4 Clouds

This memo specifies an optional interim mechanism for IPv6 sites to communicate with each other over the IPv4 network without explicit tunnel setup, and for…

Read RFC 3056 on the RFC Editor

Outgoing relationships (13 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Informative reference — RFC 791: Internet Protocol
Informative reference — RFC 1918: Address Allocation for Private Internets
Informative reference — RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
Informative reference — RFC 2373: IP Version 6 Addressing Architecture
Informative reference — RFC 2462: IPv6 Stateless Address Autoconfiguration
Informative reference — RFC 2529: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
Informative reference — RFC 2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
Informative reference — RFC 2893: Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 2374: An IPv6 Aggregatable Global Unicast Address Format
Informative reference — RFC 2283: Multiprotocol Extensions for BGP-4
Informative reference — RFC 2553: Basic Socket Interface Extensions for IPv6

Incoming relationships (46 related RFCs)

Normatively referenced by — RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
Normatively referenced by — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Normatively referenced by — RFC 4942: IPv6 Transition/Co-existence Security Considerations
Normatively referenced by — RFC 6343: Advisory Guidelines for 6to4 Deployment
Normatively referenced by — RFC 3964: Security Considerations for 6to4
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 5569: IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
Normatively referenced by — RFC 7421: Analysis of the 64-bit Boundary in IPv6 Addressing
Normatively referenced by — RFC 6732: 6to4 Provider Managed Tunnels
Normatively referenced by — RFC 3904: Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks
Normatively referenced by — RFC 5158: 6to4 Reverse DNS Delegation Specification
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 7123: Security Implications of IPv6 on IPv4 Networks
Normatively referenced by — RFC 7526: Deprecating the Anycast Prefix for 6to4 Relay Routers
Informatively referenced by — RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
Informatively referenced by — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Informatively referenced by — RFC 6269: Issues with IP Address Sharing
Informatively referenced by — RFC 4191: Default Router Preferences and More-Specific Routes
Informatively referenced by — RFC 6830: The Locator/ID Separation Protocol (LISP)
Informatively referenced by — RFC 4389: Neighbor Discovery Proxies (ND Proxy)
Informatively referenced by — RFC 6169: Security Concerns with IP Tunneling
Informatively referenced by — RFC 3068: An Anycast Prefix for 6to4 Relay Routers
Informatively referenced by — RFC 5971: GIST: General Internet Signalling Transport
Informatively referenced by — RFC 6890: Special-Purpose IP Address Registries
Informatively referenced by — RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
Informatively referenced by — RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
Informatively referenced by — RFC 4903: Multi-Link Subnet Issues
Informatively referenced by — RFC 6177: IPv6 Address Assignment to End Sites
Informatively referenced by — RFC 9300: The Locator/ID Separation Protocol (LISP)
Informatively referenced by — RFC 6104: Rogue IPv6 Router Advertisement Problem Statement
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 4029: Scenarios and Analysis for Introducing IPv6 into ISP Networks
Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informatively referenced by — RFC 3178: IPv6 Multihoming Support at Site Exit Routers
Informatively referenced by — RFC 4891: Using IPsec to Secure IPv6-in-IPv4 Tunnels
Informatively referenced by — RFC 6180: Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
Informatively referenced by — RFC 7094: Architectural Considerations of IP Anycast
Informatively referenced by — RFC 6751: Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)
Informatively referenced by — RFC 6964: Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
Informatively referenced by — RFC 7059: A Comparison of IPv6-over-IPv4 Tunnel Mechanisms
Informatively referenced by — RFC 7954: Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
Informatively referenced by — RFC 4214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
Informatively referenced by — RFC 6654: Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)
Informatively referenced by — RFC 6782: Wireline Incremental IPv6
Informatively referenced by — RFC 6948: Some Measurements on World IPv6 Day from an End-User Perspective