The tag is used only by the UAs to indicate support for changed from/to
URIs, but for proxies which do not support changed from and To-URI this
new RFCs says there are no provisions and says as below
"This document makes no provision for proxies that are unable to
tolerate a change of URI, since changing the URI has been expected for a
considerable time."
So let us say we wanted to pass end to end updated connected identity
and both the UA indicated support for that, but if in the network we
have a proxy which does not support changing from/to URIs ( because of
backward compatibility to rfc-2543 ). The information would fail to be
passed end to end even though both UAs indicated support for so.
So I was trying to re-inforce the point that going forward probably we
have to loosen up our compliancy rules w.r.t to backward compatibility
with RFC-2543 to be able to provide newer functionalities as described
in the newer RFCs etc ...
Best Regards,
Indresh
________________________________
From: ext Roman Shpount [mailto:[email protected]]
Sent: Friday, February 19, 2010 5:09 PM
To: Singh, Indresh (NSN - US/Boca Raton)
Cc: Paul Kyzivat; [email protected]
Subject: Re: [Sip-implementors] Query - are *header* parameters
(other thantag) of From and To part of dialog state?
I think the key here that end point suppose to indicate that it
supports changing To and From headers in the middle of the dialog. If
such capability is not indicated, changing headers is not allowed.
____________________________
Roman Shpount www.telurix.com <http://www.telurix.com/>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
