Skip to main content

RFC Status Change : RFC 3068 An Anycast Prefix for 6to4 Relay Routers and and RFC 6732 Provider managed tunnels to historic
status-change-rfc-3068-anycast-prefix-for-6to4-to-historic-00

The information below is for an old version of the document.
Document Proposed status change RFC Status Change : RFC 3068 An Anycast Prefix for 6to4 Relay Routers and and RFC 6732 Provider managed tunnels to historic Snapshot
Last updated 2015-02-05
Moves to Historic RFC3068, RFC6732
State AD Review
IESG Telechat date (None)
Responsible AD Joel Jaeggli
Send notices to v6ops@ietf.org

status-change-rfc-3068-anycast-prefix-for-6to4-to-historic-00
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.