Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature-03 (featuring the Feature-Caps header field)

[Paul Kyzivat <[e-mail]>]

[trimming]

On 11/1/11 4:45 PM, Christer Holmberg wrote:

>>> And, as you also indicated, we can specify what information a feature tag specification, and its associated IANA registration, needs to contain.
>>
>> If we use feature tags, unless we require use of the "sip" tree, or
>> define a new tree, I don't think we can specify what the specification
>> includes, since the registration is defined by RFC 2506.
>
> What is it then that is missing today? For example, alll the currently IANA registered g.3gpp feature tags DO contain a specification reference.

We can't easily (without ammending 2506) change what is required to 
register a feature tag. The document references are optional, and there 
is no required content for referenced documents.

I think its probably possible to craft the normative requirements for a 
new usage of feature-tags (i.e. in Feature-Caps) to restrict usage to 
feature tags that have a referenced document with some specific content.

What that wouldn't do is normatively prohibit the use of those new 
feature tags in other places, such as called out in 3840/3841. To do 
that we would have to revise 3840/3841.

	Thanks,
	Paul