[LAC-TF] BCP 196, RFC 7526 on Deprecating the Anycast Prefix for 6to4 Relay Routers (fwd)
Azael Fernandez Alcantara
afaza at unam.mx
Wed May 20 16:14:19 BRT 2015
Finalmente salio este RFC, les recomiendo leerlo y disminuir o sustituir
el uso de 6to4 con anycast.
Mensaje enviado sin acentos
---------- Forwarded message ----------
Date: Wed, 20 May 2015 10:41:21 -0500
From: rfc-editor at rfc-editor.org
Reply-To: ietf at ietf.org
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
Cc: drafts-update-ref at iana.org, v6ops at ietf.org, rfc-editor at rfc-editor.org
Subject: BCP 196,
RFC 7526 on Deprecating the Anycast Prefix for 6to4 Relay Routers
A new Request for Comments is now available in online RFC libraries.
Title: Deprecating the Anycast Prefix for
6to4 Relay Routers
Author: O. Troan, B. Carpenter, Ed.
Status: Best Current Practice
Date: May 2015
Mailbox: ot at cisco.com,
brian.e.carpenter at gmail.com
Obsoletes: RFC 3068, RFC 6732
See Also: BCP 196
I-D Tag: draft-ietf-v6ops-6to4-to-historic-11.txt
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.
This document is a product of the IPv6 Operations Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
Association Management Solutions, LLC
More information about the LACTF