RFC 3068 An Anycast Prefix for 6to4 Relay Routers and RFC 6732 Provider Managed Tunnels to Historic
status-change-rfc-3068-anycast-prefix-for-6to4-to-historic-01

The following approval message was sent
From: The IESG
To: IETF-Announce
Cc: RFC Editor , v6ops@ietf.org
Subject: Protocol Action: An Anycast Prefix for 6to4 Relay Routers to Historic

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.

The following approval message was sent
From: The IESG
To: IETF-Announce
Cc: RFC Editor , v6ops@ietf.org
Subject: Document Action: 6to4 Provider Managed Tunnels to Historic

The IESG has approved changing the status of the following document:
- 6to4 Provider Managed Tunnels
  (rfc6732) to Historic

This document 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/rfc6732/

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.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call: RFC 3068 An Anycast Prefix for 6to4 Relay Routers and RFC 6732 Provider Managed Tunnels to Historic


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/