[EMAIL PROTECTED] wrote:
From: Jonathan Rosenberg <[EMAIL PROTECTED]>
THe mechanism basically changes the way proxies handle requests. Instead
of rewriting the request URI for out-of-dialog requests, they'll push a
route header and leave the r-uri alone. This allows the original R-URI
and any parameters it contains to get delivered to the UAS.
Unfortunately, I have to say that I dislike this mechanism intensely,
as it changes the whole philosophy of how SIP messages are routed.
Well, right now, it happens two ways. So I view it as trying to make it
consistent.
On a more practical level, it only deals with one level of address
mapping, and it's not usable by a UA that doesn't implement the change
-- whereas I would expect that the optimal mechanism is one that
tweaks the behavior of the proxy doing the mapping, and requires no
change from any other system.
If the purpose of this is to communicate the targeted URI from the
terminating proxy to the UA, I don't see how any mechanism can work
unless it is supported by that proxy and that UA. Any of the mechanisms
mentioned or discussed (P-Called-Party-ID, To, History-Info) have this
property.
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza
Cisco Fellow Parsippany, NJ 07054-2711
Cisco Systems
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.cisco.com
_______________________________________________
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
