Protocol Action: An Anycast Prefix for 6to4 Relay Routers to Historic

The IESG <iesg-secretary@ietf.org> Mon, 09 March 2015 19:10 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4789A1A90BE; Mon, 9 Mar 2015 12:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 v6G49-ZGbSll; Mon, 9 Mar 2015 12:10:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78C4C1A9176; Mon, 9 Mar 2015 12:10:07 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Protocol Action: An Anycast Prefix for 6to4 Relay Routers to Historic
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150309191007.2376.13444.idtracker@ietfa.amsl.com>
Date: Mon, 09 Mar 2015 12:10:07 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/EoB_d48_ZW6e_b2URGZiIhx3VB4>
Cc: v6ops@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2015 19:10:11 -0000

The IESG has approved changing the status of the following document:
- An Anycast Prefix for 6to4 Relay Routers
  (rfc3068) to Historic

This protocol action is documented at:
http://datatracker.ietf.org/doc/status-change-rfc-3068-anycast-prefix-for-6to4-to-historic/

A URL of the affected document is:
http://datatracker.ietf.org/doc/rfc3068/

Status Change Details:

RFC Status Change :  RFC 3068 An Anycast Prefix for 6to4 Relay 
Routers and RFC 6732 Provider managed tunnels to historic

RFC 3068 introduces a "6to4 anycast address" in order to simplify
the configuration of 6to4 routers.  It also defines how this address
will be used by 6to4 relay routers, how the corresponding "6to4
anycast prefix" will be advertised in the IGP and in the EGP.  The
memo documents the reservation by IANA (Internet Assigned Numbers
Authority) of the "6to4 relay anycast prefix."

draft-ietf-v6ops-6to4-to-historic-11.txt requests that RFC 3068, 
"An Anycast Prefix for 6to4 Relay Routers", be made obsolete and 
moved  to historic status. It does so because the mechanism is 
considered unsuitable for  widespread deployment and use in the 
Internet. further recommendations are made for the operations of 
existing 6to4 anycast services.

draft-ietf-v6ops-6to4-to-historic-11 obsoletes RFC 6732 "6to4 Provider 
Managed Tunnels".  It recommends that future products should not support 
6to4 anycast and that existing deployments should be reviewed.

Personnel 

   Joel Jaeggli is the responsible Area Director.