Hi Francois, >I think what you meant by Target was more the "Current" >target as opposed to the Initiatl Target.
Yes. >And if that's the case, then I don't see why it is different >from P-Called-ID (although I might be missing something with >what the P-Called_ID is supposed to be). In the draft we try to explain the difference. But, we are working on the text to make it more clear. The P-CPI is inserted when the R-URI is rewritten by the Contact address of the UAS. RFC3455 calls that operation "retargeting", but we don't think that is the definition for retarget used in the ua-loose-route draft, which says: "When a home proxy receives a request and accesses a location service, the resulting contact(s) obtained from the location service are considered the last hop in the route towards the entity addressed by the Request-URI. Since that target, almost by definition, can claim the identity of the URI prior to translation, the operation is one of routing and not retargeting." So, if we follow the definitions in the ua-loose-route draft, P-CPI would be inserted due to a reroute - not retarget. But, no matter whether we call it retarget or reroute, the point is that the P-CPI is inserted when the R-URI is rewritten with the Contact address of the UAS. The scope of Target is wider than that, and can be used in any retargeting situation. Regards, Christer _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
