On Jun 23, 2008, at 12:48 PM, Paul Kyzivat wrote:
How about this?
Define the new INFO usage framework, for new uses of INFO, along the
lines proposed by Hadriel and others. As part of that, establish a
registry or registries.
Incorporate into that a grandfather clause. If your usage of INFO
predated some specified date then it will be permitted to be
registered, but not standardized. Presumably the registration would
have to be based on Content-Type, since AFAIK that is all that
really works for existing usages. The registry for these
grandfathered usages would have to point to *some* specification of
the usage. It could be be an individual informational RFC, or a
document by some other SDO. (What else would make sense?)
Existing *standard* usages of INFO (the few there are) would also
fall under this grandfather clause. In that case there is an RFC to
refer to.
*New* usages, after the specified date, would be ineligible for
registration under the grandfather clause. They would be required to
use the new formal usage mechanism.
That works for me. It's quite rational, given where we find ourselves,
and fits with the goal of "reducing further damage."
(Damn, I'm allowing myself to be sucked into this again.)
I'm so sorry ;-).
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
