RFC 3056: Connection of IPv6 Domains via IPv4 Clouds
In plain English — editorial summary, not part of the RFC
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 them to communicate with native IPv6 domains via relay routers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3056
- Published
- February 2001
- Authors
- B. Carpenter; K. Moore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2765Stateless IP/ICMP Translation Algorithm (SIIT)Obsoleted
February 2000
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 2766Network Address Translation - Protocol Translation (NAT-PT)Obsoleted
February 2000
- RFC 25466Bone Routing PracticeObsoleted
March 1999
- RFC 3574Transition Scenarios for 3GPP NetworksCurrent
August 2003
- RFC 2365Administratively Scoped IP MulticastCurrent
July 1998
- RFC 6250Evolution of the IP ModelCurrent
May 2011
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?