Re: [Sip] Question on RFC3840/3841

hi
That is my understanding as well. But if that is the case then it should 
apply to Contact header as well
when describing Capabilities using Feature parameters in Contact Header.
But i'm not sure if it applies the same way. I had posted this question long 
ago but didnt get any comments on it.

regards
Mahesh

----- Original Message ----- 
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <sip@ietf.org>
Cc: "Paul Kyzivat" <pkyzivat@cisco.com>
Sent: Wednesday, January 09, 2008 3:54 PM
Subject: [Sip] Question on RFC3840/3841

Hi,

Chapter 9 of RFC3840 says:

"There are additional constraints on the usage of feature-param that
cannot be represented in a BNF. There MUST only be one instance of any
feature tag in feature-param."

Chapter 10 of RFC3840 says:

"Furthermore, there can only be one instance of any feature tag in
feature-param."

So, this means that the following is NOT allowed:

Accept-Contact: *;myTag,myTag

However, since an Accept-Contact header can contain multiple ac-values,
each with its own sets of ac-parameters (including feature-params), the
following should be allowed:

Accept-Contact: *;myTag, *;myTag

...or:

Accept-Contact: *;myTag
Accept-Contact: *;myTag

Correct?

Regards,

Christer

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

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