[v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-11.txt> (Deprecating Anycast Prefix for 6to4 Relay Routers) to Best Current Practice
The IESG <iesg-secretary@ietf.org> Wed, 04 February 2015 21:55 UTC
Return-Path: <iesg-secretary@ietf.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 5E2181A8997; Wed, 4 Feb 2015 13:55:22 -0800 (PST)
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 pF6pXcxleD_s; Wed, 4 Feb 2015 13:55:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0821D1A888B; Wed, 4 Feb 2015 13:55:21 -0800 (PST)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20150204215521.20810.26259.idtracker@ietfa.amsl.com>
Date: Wed, 04 Feb 2015 13:55:21 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/3LJRS_VJrFmR6zLlhuGuUfSgC14>
Cc: v6ops@ietf.org
Subject: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-11.txt> (Deprecating Anycast Prefix for 6to4 Relay Routers) to Best Current Practice
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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, 04 Feb 2015 21:55:22 -0000
The IESG has received a request from the IPv6 Operations WG (v6ops) to consider the following document: - 'Deprecating Anycast Prefix for 6to4 Relay Routers' <draft-ietf-v6ops-6to4-to-historic-11.txt> as Best Current Practice The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-02-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Experience with the "Connection of IPv6 Domains via IPv4 Clouds (6to4)" IPv6 transition mechanism defined in RFC 3056 has shown that when used in its anycast mode, the mechanism is unsuitable for widespread deployment and use in the Internet. This document therefore requests that RFC 3068, "An Anycast Prefix for 6to4 Relay Routers", be made obsolete and moved to historic status. It also obsoletes RFC 6732 "6to4 Provider Managed Tunnels". It recommends that future products should not support 6to4 anycast and that existing deployments should be reviewed. This complements the guidelines in RFC 6343. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/ No IPR declarations have been submitted directly on this I-D.