Re: AW: [Sipping-tispan] Requirements 02e

RFC 3261 has in Section 8.2.6.2 procedures for dealing with the To 
header in responses. Essentially, it is required to keep the same URI 
and the tag if present (if not present, the UAS must create a new one).

However, I didn't find any procedures indicated whether a UAS can add a 
new parameter to the To header in a response. And if that was possible, 
will it be correctly used by the UAC for displaying purposes?

/Miguel

Jesske, R wrote:

> In principle I have nothing against such an approach.
> But what is in the case of diverting the communication.
> So that the to header is different from the P-Asserted-Identity and the identity in the to header belongs not to the user where the communication was sent to originally?
> 
> Roland
> 
> 
>>-----Ursprüngliche Nachricht-----
>>Von: Bemmel, Jeroen van (Jeroen) [mailto:jbemmel@lucent.com] 
>>Gesendet: Freitag, 23. September 2005 12:34
>>An: Jesske, Roland; pkyzivat@cisco.com; Miguel.An.Garcia@nokia.com
>>Cc: sipping-tispan@ietf.org
>>Betreff: RE: [Sipping-tispan] Requirements 02e
>>
>>
>>
>>>So we want the have the same within SIP. In forward direction 
>>>we have the From header and the P-Asserted-Identity. But in 
>>>Backward direction the equivalent to the From header is missing.
>>>
>>>So we need such an identity header for the backward direction 
>>>setup from the callee.
>>>
>>>Roland
>>
>>What if the callee would simply add a parameter to the To 
>>header? Something like
>>To: 
>><sip:callee@provider.com>;tag=25425741;identity=user@altprovider.com
>>
>>Jeroen
> 
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.an.garcia@openlaboratory.net
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan