Re: Issue 3 - two tags (wasRE:I-DACTION:draft-rosenberg-sip-target-uri-delivery-01.txt

Dean Willis <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <[email protected]>
Christer Holmberg wrote:
> Hi, 
> 
>> The point is that the registered contact could be an AOR of another
> user.
> 
> Ok, now I understand. Yes, that is an interesting case, eventhough I
> guess it's really not the correct usage of the registration procedure.
> 

Any contact could be an AOR, not a final destination, in that any UA 
could also decide to become a proxy and send the call somewhere else. 
Such a determination might be made on a call-by-call basis.

In such case, two possibilities apply:

1) the transformation is a reroute, in that the identity of the target 
is not being changed, just the location at which that target is being 
sought.


2) The transformation is a retarget, in that the identity of the target 
is being sought after the transformation is different than the identity 
being sought before the transformation.

Of course, it is possible for a proxy making such a transformation to 
not know the identity of the target. In such a case, it is impossible 
for the proxy to inform the UAC of the transformation and thereby avoid 
an unanticipated respondent scenario. This is the world we live in for 
ALL proxy operations today, and it has its drawbacks.

--
Dean

_______________________________________________
Sip mailing list  https://www.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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.