Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7526
Discuss this RFC: Send questions or comments to the mailing listv6ops@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7526
Experience with the 6to4 transition mechanism defined in RFC 3056("Connection of IPv6 Domains via IPv4 Clouds") has shown that themechanism is unsuitable for widespread deployment and use in theInternet when used in its anycast mode. Therefore, this documentrequests that RFC 3068 ("An Anycast Prefix for 6to4 Relay Routers")and RFC 6732 ("6to4 Provider Managed Tunnels") be made obsolete andmoved to Historic status. It recommends that future products shouldnot support 6to4 anycast and that existing deployments should bereviewed. This complements the guidelines in RFC 6343.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.