[mailto:v6ops-bounces(_at_)ietf(_dot_)org] On Behalf Of TJ
Sent: Tuesday, June 07, 2011 7:33 AM
To: Tim Chown
Cc: v6ops(_at_)ietf(_dot_)org WG; ietf(_at_)ietf(_dot_)org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
(Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic
status) to Informational RFC
It's time to remove the stabilisers on the IPv6 bicycle.
I agree, but get me native everywhere before taking away one connection
mechanism that does work.
This takes nothing away. It's not as if the day that this draft gets published
as an RFC, 6to4 stops working. IETF has moved other protocols to historical
status before they were out of heavy use, with the expectation that it would
take some time for the alternatives to be deployed and existing implementations
to be retired. This is specifically why we resisted the idea of putting in a
shutdown schedule or other flag day where the 6to4 prefixes get null-routed,
because it's likely to be different in each network and application.
"In order to limit the impact of end-users, it is
recommended that operators retain their existing 6to4 relay routers
and follow the recommendations found in
[I-D.ietf-v6ops-6to4-advisory]. When traffic levels diminish, these
routers can be decommissioned."
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail and
Ietf mailing list