metasystema.org
CurrentBEST CURRENT PRACTICEIETF streamBCP196

RFC 7526: Deprecating the Anycast Prefix for 6to4 Relay Routers

In plain English — editorial summary, not part of the RFC

Experience with the 6to4 transition mechanism defined in RFC 3056 ("Connection of IPv6 Domains via IPv4 Clouds") has shown that the mechanism is unsuitable for widespread deployment and use in the Internet when used in its anycast mode. Therefore, this document requests that RFC 3068 ("An Anycast Prefix for 6to4 Relay Routers") and RFC 6732 ("6to4 Provider Managed Tunnels") be made obsolete and moved to Historic status. It recommends that future products should not support 6to4 anycast and that existing deployments should be reviewed. This complements the guidelines in RFC 6343.

Document record

Document ID
RFC7526
Published
May 2015
Authors
O. Troan; B. Carpenter
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
10
Also known as
BCP196
Obsoletes:
RFC 3068, RFC 6732

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 3068 (2001)
  2. RFC 6732 (2012)
  3. RFC 7526 (2015)

Read the full history of Deprecating the Anycast Prefix for 6to4 Relay Routers →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/7526-deprecating-the-anycast-prefix-for-6to4-relay-routers