[Ietf-calsify] Re: additional IANA considerations
alexey.melnikov at isode.com
Thu Jun 21 09:15:15 PDT 2007
Eliot Lear wrote:
> Alexey Melnikov wrote:
>> I think all templates need to have a Usage field, which contains one
>> of the following: limited, global, obsolete.
> Sounds like you're mixing semantics. Do you mean "status"? I think
> that's important too.
SASL registry uses "Usage", which is one of "limited", "common" or
"obsolete". "obsolete" is something that shouldn't be used. "common" is
something that is applicable to various use cases. "limited" is
something known to be somewhat restricted/broken, but not sufficiently
bad in order to be marked "obsolete".
So what do you mean by "status"?
>>> X.X.X Registration Template for New Components
>>> A component is defined by completing the following template.
>>> To: iana at iana.org
>>> Subject: Registration of new iCalendar component XXX
>>> Component Name:
>>> Format Definition:
> You don't need the "To: " line.
This is more of a convention used by many IANA templates.
More information about the Ietf-calsify