| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 06 Oct 2025 21:46:06 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=3TFMSFU6tQxhnbjDs2GdDpr_cLEiw.r5X_boniRSHxs-1759787166-1.0.1.1-2xFZZiN5yuqrxHuQVLAx2D86pRKaI6F.hAH9FoQ_c4xN4YVqM_IwMbR4HSYevJ4t0c4BIh5r1CW2DfaOh.P8kB2sMhcbTYFFDgyKJ0vpNQw; path=/; expires=Mon, 06-Oct-25 22:16:06 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98a85978f9966f7a-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 3056 » RFC Editor
Search RFCs
RFC 3056
Connection of IPv6 Domains via IPv4 Clouds, February 2001
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- B. Carpenter
K. Moore - Stream:
- IETF
- Source:
- ngtrans (ops)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3056
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3056
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us