Re: Policy to register media feature tags

Responses inline...

/Hans Erik

Paul Kyzivat wrote:
> On one side were those who wanted capabilities and preferences to be 
> stated in terms of feature tags that are well known and orthogonal. On 
> the other side were those who prefer to associate arbitrary names to 
> collections of features and then negotiate on the basis of the names 
> of those collections.
>
> Using the latter approach its possible that interoperation will fail 
> because the parties don't share a common name for a collection of 
> features even though they both possess the necessary features to 
> interoperate.
That is a feature. This interoperability "problem" only occurs when the 
originating party includes the header field parameters "require" and 
"explicit" in the Accept-Contact header field containing the feature 
tag. In this case the failure of the call when not all of the receiving  
UA's support  the feature is intended!
> I don't have a problem with independent groups defining new feature 
> tags, as long as they are primitive and orthogonal to existing ones. 
> But I do have a problem with defining feature tags that identify 
> collections of features, especially when the mapping from the 
> identifier to the collection of features is not public.
Well who is going to determine what can be called a feature and what not.
I also like to see where this principle is documented to apply to the 
global tree.
>
> The bottom line is that I think this sort of thing needs to be 
> thrashed out within the sip community. So I think the RFC process is 
> the right process.
I think that bending the rules because some SIP people don't like on how 
other organisations are applying SIP in their solutions will alieanate 
those SIP users from that same SIP community. So I seriously hope we 
will not go down that path.

/Hans Erik
_______________________________________________
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