Re: [Sip] draft-ietf-sip-callee-caps-03 methods question

[Jonathan Rosenberg <jdrosen at dynamicsoft.com>]

inline.

Juha Heinanen wrote:

> Jonathan Rosenberg writes:
>
>  > Sorry for the long delay in replying, Juha. 
>
> no problem.
>
>  >     When there
>  >     exists a feature tag that describes a capability that can also be
>  >     represented with a SIP header field, a UA MUST use the header field
>  >     to describe the capability. A UA receiving a message that contains
>  >     both the header field and the feature tag MUST use the header field,
>  >     and not the feature tag.
>
> i'm not sure if the above makes sense at least in methods vs. allow
> case.  since an invite, for example, can contain many contacts each with
> different set of supported methods, a single allow header cannot be used
> to describe the situation.

[assuming s/invite/register]

True. In that case, the callee caps params are what you want. We will 
see if perhaps a clarification can be added before the document is 
published as an RFC.

-Jonathan R.



--
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen at dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip