RE: [Sip] Vocabulary and problem statement for Request-URI, retargeting, and SIP routing (long, but read it!)

"Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com> Thu, 17 January 2008 23:40 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFeLo-0001iF-Dv; Thu, 17 Jan 2008 18:40:48 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFeLm-0001i5-MA for sip-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 18:40:46 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFeLm-0001hw-As for sip@ietf.org; Thu, 17 Jan 2008 18:40:46 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFeLl-0000s3-VH for sip@ietf.org; Thu, 17 Jan 2008 18:40:46 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 17 Jan 2008 18:40:46 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m0HNejkn002882; Thu, 17 Jan 2008 18:40:45 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0HNeaua027362; Thu, 17 Jan 2008 23:40:41 GMT
Received: from xmb-rtp-215.amer.cisco.com ([64.102.31.124]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 Jan 2008 18:40:36 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Vocabulary and problem statement for Request-URI, retargeting, and SIP routing (long, but read it!)
Date: Thu, 17 Jan 2008 18:40:35 -0500
Message-ID: <5C5630E45267B642894988A97570D3220D2841@xmb-rtp-215.amer.cisco.com>
In-Reply-To: <478FE5D7.7010707@softarmor.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Vocabulary and problem statement for Request-URI, retargeting, and SIP routing (long, but read it!)
Thread-Index: AchZYH4EWVmzcgsbStWWTRQJKTwF/gAAWJsQ
From: "Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com>
To: "Dean Willis" <dean.willis@softarmor.com>, "Hadriel Kaplan" <HKaplan@acmepacket.com>
X-OriginalArrivalTime: 17 Jan 2008 23:40:36.0123 (UTC) FILETIME=[5BC2F6B0:01C85962]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2087; t=1200613245; x=1201477245; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sanjsinh@cisco.com; z=From:=20=22Sanjay=20Sinha=20(sanjsinh)=22=20<sanjsinh@cisc o.com> |Subject:=20RE=3A=20[Sip]=20=09Vocabulary=20and=20problem=2 0statement=20for=20Request-URI,retargeting,=20and=20SIP=20ro uting=20(long,=20but=20read=20it!) |Sender:=20 |To:=20=22Dean=20Willis=22=20<dean.willis@softarmor.com>,=0 A=20=20=20=20=20=20=20=20=22Hadriel=20Kaplan=22=20<HKaplan@a cmepacket.com>; bh=ys5ezeF5sYQTTSVAD/rX5TE5VEPeC3nlFFMTiob9I8w=; b=c7fjQD6+myUdoYkRU+r1uCR3x8Xsu4C2/GqzbnsCuG7gMiJysT9KQ6ygVb LYbD8zWLedX3+NWOZGAm0T9iamP6ftX4Vqr6/NzQYa/VrNJ5FxFc3hX9rlqO 3h6Sq5BIqP;
Authentication-Results: rtp-dkim-2; header.From=sanjsinh@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: IETF SIP List <sip@ietf.org>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Inline ...

>-----Original Message-----
>From: Dean Willis [mailto:dean.willis@softarmor.com] 
>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 
>sip-implementors@cs.columbia.edu for questions on current sip 
>Use sipping@ietf.org 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 sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip