[Ietf-calsify] Re: additional IANA considerations

Alexey Melnikov alexey.melnikov at isode.com
Thu Jun 21 06:53:38 PDT 2007


Hi Bernard,
Some questions/comments about the proposed templates below:

Bernard Desruisseaux wrote:

>>> Also, I think we should consider having 4 templates:
>>>
>>> - Registration of New Components
>>> - Registration of New Properties
>>> - Registration of New Parameters
>>> - Registration of New Values
>>>
>>> What do you think?
>>
>>
>> I think there needs to be a substantial difference in the templates 
>> to justify four of them.  Do you think there is?
>
>
> Here's what I have in mind.  A total of 5 templates.
>
>   - Registration Template for New Components
>   - Registration Template for New Properties
>   - Registration Template for New Parameters
>   - Registration Template for New Value Data Types
>   - Registration Template for New Values

I think all templates need to have a Usage field, which contains one of 
the following: limited, global, obsolete.

> 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:
>
>         Purpose:
>
>         Format Definition:
>
>         Description:

How is Purpose different from Description?

What is Format Definition? Is it supposed to be ABNF or RFC reference?

>         Example:
>
> X.X.X  Registration Template for New Properties
>
>     A property is defined by completing the following template.
>
>         To: iana at iana.org
>
>         Subject: Registration of new iCalendar property XXX
>
>         Property name:
>
>         Purpose:
>
>         Value type(s):
>
>         Property parameter(s):
>
>         Conformance:

And this is an RFC reference? Why have you omitted this from the 
previous template?

>         Description:
>
>         Format definition:
>
>         Example(s):




More information about the Ietf-calsify mailing list