> From: Ronald Bonica <rbonica(_at_)juniper(_dot_)net>
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and
> convert their status to HISTORIC.
I think we should only mark things as HISTORIC as a recognition of _what has
already happened_ out in the world, not as an attempt to _make something
happen_.
If we want to tell people to stop using a protocol, we should be direct and
produce a document that says 'this protocol should always be off by default',
or 'stop using this protocol', or 'remove this protocol from your products', or
whatever.
> While it clarifies the meaning of "HISTORIC" in this particular case, it
> does not set a precedent for any future case.
In other words, this document is doing something with "HISTORIC" that isn't the
normal, this is a special case. I think this is a bad idea.
Noel
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf