Re: [sipcore] consensus call: draft-roach-sipcore-priority-00: IANA registration template needed?

[Paul Kyzivat <[e-mail]>]

On 11/29/12 2:33 AM, Christer Holmberg wrote:
> Hi Paul,
>
>> We are in the process of adopting draft-roach-sipcore-priority-00 as a wg document. We already ran a WGLC on it in anticipation of the adoption.
>>
>> One issue raised during the WGLC was whether the document should include some sort of IANA registration template. Christer proposed this, and Keith opposed it.
>>
>> Christer failed to specify what he wanted to see in this template. The existing document specifies what the registry should contain: A "priority" name and a document
>> reference. "IETF Review" is required for adding new values, which ensures that there will be an RFC to reference.
>> So presumably the template would include at least these two values.
>>
>> Please indicate if you think the draft is ok as-is, or should be revised to include a registration template.
>>
>> If you favor a template, please indicate what you think it should contain.
>
> What do you mean by "Christer failed to specify"?
>
> 13th November I DID send text proposal to the list for the registration template. It contained Description, Reference and Contact. See copy at the end of this reply.

Oh, sorry. I must have looked at the wrong message.

> However, 15th November I indicated on the list that, if nobody else think a template is needed, I'll step down :)
>
> The important thing is that it is clear to a person who want to register a value WHAT information to provide, and WHERE to send it.

What's necessary is to supply the info that is in the IANA registry. As 
currently proposed, that is only the name of the value and a reference 
to the RFC that defines it.

There is no need to send it anywhere, because it calls for IETF Review, 
which requires an RFC, and the IETF RFC process deals with IANA 
considerations.

It is really hard to write an RFC that defines a new Priority value 
without specifying the name of that value. I think people will remember 
to do this even without a template. :-)

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
> -------------------
>
> x. Priority Header Field Value Registration Template
>
>     Registration requests for Priority header field values
>     requires submitting an Internet-Draft to the IESG.
>
>     | Instructions are preceded by '|'.  All fields are mandatory.
>
>     Priority header field value:
>
>     Description:
>
>     | The description should be no longer than 4 lines. More
>     | detailed information can be provided in the specification
>     | that defines the header field value.
>
>     Priority header field value specification reference:
>
>     | The reference to the speicification the defines the
>     | header field value.
>
>     Contact:
>
>     | Name(s) & email address(es) of person(s) to
>     | contact for further information."
>
> -------------------
>
>