Hi, Another comment:
For ua-loose-route you indicate that is is upward-compatible for intermediate proxies/routing. Maybe I missunderstand what you are trying to say, but one of the main issues (in my opinion) with the ua-loose-route mechanism is that it DOES need to know whether the next hop supports it or not. Regards, Christer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 25. maaliskuuta 2008 18:29 To: sip@ietf.org Subject: [Sip] Comparison of retargeting proposals I've put together a comparison chart of the varous retargeting proposals: ua-loose-route target-uri History-Info URI- (updated) param. Upward-compatible N Y Y Y with RFC 3263? Upward-compatible depends Y Y Y for UA? Upward-compatible for Y Y Y Y intermediate proxies? Complexity low low high low Upward-compatible for Y Y Y N intermediate routing? Multiple targets? N N Y N The proposals are: ua-loose-route - draft-rosenberg-sip-ua-loose-route-02 target-uri - draft-holmberg-sip-target-uri-delivery-01 History-Info - History-Info (RFC 4244), with additional parameters as needed URI-param. - a URI-parameter like the 'target' proposed in RFC 4458 The criteria are: Upward-compatible with RFC 3263? If a message has no Route headers, is its destination to be determined from the request-URI host-port as in RFC 3263? Upward-compatible for UA? Is the proposal compatible with UAs that use RFC 3263 to examine the request-URI to determine if they are the destination of the request. Complexity Multiple targets? Does the mechanism display more than the latest retargeted URI? Dale _______________________________________________ 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 _______________________________________________ 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
