> -----Original Message----- > From: Dale Worley [mailto:[email protected]] > Sent: Wednesday, March 25, 2009 12:13 AM > > (I'm envisioning a world in which the UAC's end may be involved in > complex service provisioning in which there may be more than one transit > network and more than one element that provides complex call routing. > Though a transit network should be able to hide its internal structure, > the UAC has the right to know what element the transit network delivered > the request to, since that is what the UAC is paying the transit network > to do.)
IMO the UAC has no right to know any such thing. It has no rights - it's not a human. The calling human has a right to know the far-end called human it got delivered to. But they don't care nor have a right to know the *host* element it got delivered to, or host elements it forked to but did not succeed at, etc. It's none of their business, frankly. And if we're thinking the far-end terminating Enterprise or provider will want to tell some originating Enterprise or provider what's going on inside their network, well... once again we all live in different worlds. :) -hadriel _______________________________________________ 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
