Last Call: RFC 3068 An Anycast Prefix for 6to4 Relay Routers and RFC 6732 Provider Managed Tunnels to Historic
The IESG <iesg-secretary@ietf.org> Fri, 06 February 2015 23:29 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 CB32F1A88CF for <ietf-announce@ietfa.amsl.com>; Fri, 6 Feb 2015 15:29:43 -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 w0ECsj3l_h36 for <ietf-announce@ietfa.amsl.com>; Fri, 6 Feb 2015 15:29:42 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4B31A87E3 for <ietf-announce@ietf.org>; Fri, 6 Feb 2015 15:29:42 -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>
Subject: Last Call: RFC 3068 An Anycast Prefix for 6to4 Relay Routers and RFC 6732 Provider Managed Tunnels to Historic
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20150206232942.29561.29982.idtracker@ietfa.amsl.com>
Date: Fri, 06 Feb 2015 15:29:42 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/0AAx0fZKGIXojEwAPmhQjFs5YGc>
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: Fri, 06 Feb 2015 23:29:44 -0000
The IESG has received a request from the v6ops WG to make the following
status changes:
- RFC6732 from Informational to Historic
(6to4 Provider Managed Tunnels)
- RFC3068 from Proposed Standard to Historic
(An Anycast Prefix for 6to4 Relay Routers)
The supporting document for this request can be found here:
http://datatracker.ietf.org/doc/status-change-rfc-3068-anycast-prefix-for-6to4-to-historic/
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.
The document proposing the action, currently in last call as a BCP is available via
http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/
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-20. 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.
The affected documents can be obtained via
http://datatracker.ietf.org/doc/rfc6732/
http://datatracker.ietf.org/doc/rfc3068/
IESG discussion of this request can be tracked via
http://datatracker.ietf.org/doc/status-change-rfc-3068-anycast-prefix-for-6to4-to-historic/ballot/