Re: [sipcore] Feature-Caps: Feature indications in 18x and 200

[Christer Holmberg <[e-mail]>]

Hi, 

>> If an entity receives different values in responses 
>> associated with the same dialog, an error case has occured 
>>(as the sender should not send different values for the same dialog).
>> 
>> So, we can either say that the first response with 
>> Feature-Caps is taken as definitive, or we can say that the 
>> Feature-Caps in 2xx is taken as definitive, because for a 
>> given dialog they should always be the same.
> 
> Right, so I agree with Keith that the 2xx should win.

So, I have done some additions (<addition>) to the suggested text:

	"An entity can include the same Feature-Caps 
	header field value in multiple responses (18x/2xx) 
	for the same INVITE/re-INVITE transaction, but for a
	given dialog the entity MUST use the same Feature-Caps 
	header field value (if included) in all responses for 
	the same transaction. In addition, if an entity includes 
	a Feature-Caps header field in a 18x response, for the 
	given dialog it MUST include the header field in all
	subsequent 18x responses, and the 2xx response, for the 
	same transaction. <addition> If an entity, for a given dialog,
      receives different Feature-Caps header field values in
	responses to the same transaction (this would not happen in
	normal operations), it MUST use the latest header field 
	values as the valid one.</addition>"

Regards,

Christer