Inline ... >-----Original Message----- >From: Dean Willis [mailto:[EMAIL PROTECTED] >Sent: Thursday, January 17, 2008 6:34 PM >To: Hadriel Kaplan >Cc: IETF SIP List >Subject: Re: [Sip] Vocabulary and problem statement for >Request-URI,retargeting, and SIP routing (long, but read it!) > >Hadriel Kaplan wrote: >> >>> We also have a related operation: >>> >>> 4) Request redirection, which informs an upstream node about a new >>> identity to target instead of the original. >> >> >> This is described from the aspect of the downstream node sending the >> 3xx, right? Vs. what it is for the upstream node recursing on the >> 3xx? (which has no idea if it's performing (2) or (3) when this >> occurs, but I guess could be added to the 3xx contact as a >param such >> as described in JR's draft) > >right. > >> So if a proxy is doing "redirection" it is sending a 3xx, > >Right. > >> whereas the >> upstream proxy or UAC getting that 3xx is not doing redirection, but >> in fact "recursing". >> > >The upstream node is just generating a new request. It really >doesn't know where that request is going, except that the new >request URI was obtained during an attempt to reach the old >one. Not sure what you mean here? The next request-uri is taken from Contact of the redirect response. So it knows where the request is going.
> We'd actually have more information from a REFER request. How is the Refer-To header different that Contacts in redirect response? Sanjay > >We've already seen all sorts of hideous problems related to an >upstream proxy recursing on a 3xx. My take is that we should >never do this in a proxy. > >-- >Dean > > >_______________________________________________ >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 > _______________________________________________ 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
