Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature

[Christer Holmberg <[e-mail]>]

Hi, 

>>I am not sure what the difference between a feature and a 
>>service is...
> 
>Then it's a good thing RFC 5897 provides guidance on that front:
> 
>"The best way to avoid this problem is to use feature tags 
>that can be matched to well-defined signaling features -- media 
>types, required SIP extensions, and so on.  In particular, 
>the golden rule is that the granularity of feature tags must be 
>equivalent to the granularity of individual features that can be 
>signaled in SIP."

I am not sure how much the text really clarifies.

But, assuming it does, it probably works for pure SIP features, associated with a single dialog. For example, I think the forking capability indicator I suggested fits fine into that.

But, the features in the draft are more complex than that, and may include multiple dialogs etc.

Having said that, if you think there is a better way of solving the use-cases in the draft, I am willing to hear about it.

Regards,

Christer