Deprecating the Anycast Prefix for 6to4 Relay Routers
RFC 7526
| Document | Type |
RFC - Best Current Practice
(May 2015; No errata)
Also known as BCP 196
|
|
|---|---|---|---|
| Last updated | 2015-05-20 | ||
| Replaces | draft-troan-v6ops-6to4-to-historic | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Fred Baker | ||
| Shepherd write-up | Show (last changed 2015-01-30) | ||
| IESG | IESG state | RFC 7526 (Best Current Practice) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Joel Jaeggli | ||
| IESG note | The document shepherd is Fred Baker (fred@cisco.com). | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) O. Troan
Request for Comments: 7526 Cisco
BCP: 196 B. Carpenter, Ed.
Obsoletes: 3068, 6732 Univ. of Auckland
Category: Best Current Practice May 2015
ISSN: 2070-1721
Deprecating the Anycast Prefix for 6to4 Relay Routers
Abstract
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.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7526.
Troan & Carpenter Best Current Practice [Page 1]
RFC 7526 Deprecating 6to4 Anycast May 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Related Work . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. 6to4 Operational Problems . . . . . . . . . . . . . . . . . . 4
4. Deprecation . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Implementation Recommendations . . . . . . . . . . . . . . . 5
6. Operational Recommendations . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
Troan & Carpenter Best Current Practice [Page 2]
RFC 7526 Deprecating 6to4 Anycast May 2015
1. Introduction
The original form of the 6to4 transition mechanism [RFC3056] relies
on unicast addressing. However, its extension specified in "An
Anycast Prefix for 6to4 Relay Routers" [RFC3068] has been shown to
have severe practical problems when used in the Internet. This
document requests that RFCs 3068 and 6732 be moved to Historic
status, as defined in Section 4.2.4 of [RFC2026]. It complements the
deployment guidelines in [RFC6343].
6to4 was designed to help transition the Internet from IPv4 to IPv6.
It has been a good mechanism for experimenting with IPv6, but because
of the high failure rates seen with anycast 6to4 [HUSTON], end users
may end up disabling IPv6 on hosts; this has resulted in some content
providers being reluctant to make content available over IPv6 in the
past.
[RFC6343] analyzes the known operational issues in detail and
describes a set of suggestions to improve 6to4 reliability, given the
widespread presence of hosts and customer premises equipment that
support it. The advice to disable 6to4 by default has been widely
adopted in recent operating systems, and the failure modes have been
widely hidden from users by many browsers adopting the "Happy
Eyeballs" approach [RFC6555].
Show full document text