[v6ops] BCP 196, RFC 7526 on Deprecating the Anycast Prefix for 6to4 Relay Routers

rfc-editor@rfc-editor.org Wed, 20 May 2015 15:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A899B1A88CF; Wed, 20 May 2015 08:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvxDSO55CxAi; Wed, 20 May 2015 08:43:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id F36FA1A88C9; Wed, 20 May 2015 08:43:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E8D5B180207; Wed, 20 May 2015 08:41:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150520154121.E8D5B180207@rfc-editor.org>
Date: Wed, 20 May 2015 08:41:21 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/iR6i3gQNPQfp_cuZMhseQSw5Rbg>
Cc: drafts-update-ref@iana.org, v6ops@ietf.org, rfc-editor@rfc-editor.org
Subject: [v6ops] BCP 196, RFC 7526 on Deprecating the Anycast Prefix for 6to4 Relay Routers
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2015 15:43:07 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 196        
        RFC 7526

        Title:      Deprecating the Anycast Prefix for 
                    6to4 Relay Routers 
        Author:     O. Troan, B. Carpenter, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       May 2015
        Mailbox:    ot@cisco.com, 
                    brian.e.carpenter@gmail.com
        Pages:      10
        Characters: 20894
        Obsoletes:  RFC 3068, RFC 6732
        See Also:   BCP 196

        I-D Tag:    draft-ietf-v6ops-6to4-to-historic-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7526

        DOI:        http://dx.doi.org/10.17487/RFC7526

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC