Browse Prior Art Database

Deprecating the Anycast Prefix for 6to4 Relay Routers (RFC7526)

IP.com Disclosure Number: IPCOM000241670D
Original Publication Date: 2015-May-01
Included in the Prior Art Database: 2015-May-21
Document File: 20 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

O. Troan: AUTHOR [+3]

Abstract

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].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 13% of the total text.

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

 ...