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

Jeroen van Bemmel <jbemmel@zonnet.nl> Fri, 18 January 2008 07:45 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 1JFluP-0005do-JW; Fri, 18 Jan 2008 02:45:01 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFluO-0005Zc-5F for sip-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 02:45:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFluA-0005Vq-VY for sip@ietf.org; Fri, 18 Jan 2008 02:44:46 -0500
Received: from smtp3.versatel.nl ([62.58.50.90]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFlu9-0000ZV-EC for sip@ietf.org; Fri, 18 Jan 2008 02:44:46 -0500
Received: (qmail 32164 invoked by uid 0); 18 Jan 2008 07:44:16 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO [192.168.1.6]) ([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>) by smtp3.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 18 Jan 2008 07:44:16 -0000
Message-ID: <479058E4.2050902@zonnet.nl>
Date: Fri, 18 Jan 2008 08:44:36 +0100
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Vocabulary and problem statement for Request-URI, retargeting, and SIP routing (long, but read it!)
References: <5D1A7985295922448D5550C94DE2918001AC02E9@DEEXC1U01.de.lucent.com> <1ECE0EB50388174790F9694F77522CCF1434B83B@zrc2hxm0.corp.nortel.com> A <CA9998CD4A020D418654FCDEF4E707DF040D69C7@esealmw113.eemea.ericsson.se> <0D5F89FAC29E2C41B98A6A762007F5D0549D3F@GBNTHT12009MSX.gb002.siemens.net> <1ECE0EB50388174790F9694F77522CCF1438F1B0@zrc2hxm0.corp.nortel.com> <478CEFB4.6070002@zonnet.nl> <CA9998CD4A020D418654FCDEF4E707DF0413D587@esealmw113.eemea.ericsson.se> <"0D5F89FA C29E2C41B98A6A762007F5D0593C68"@GBNTHT12009MSX.gb002.siemen! s .net> A <CA9998CD4A0 20D418654FCDEF4E707DF04173CB8@esealmw113.eemea.ericsson.se> <0D5F89FAC29E2C41B98A6A762007F5D0593CFF@GBNTHT12009MSX.gb002.siemens.net> A <CA9998CD4A020D418654FCDEF4E707DF041743D6@esealmw113.eemea.ericsson.se> <0D5F89FAC29E2C41B98A6A762007F5D0593E13@GBNTHT12009MSX.gb002.siemens.net> <CA9998CD4A020D418654FCDEF4E707DF041C939B@esealmw113.eemea.ericsson.se> <C8D63C78-437F-430E-950C-2E63C69E3CEF@softarmor.com>
In-Reply-To: <C8D63C78-437F-430E-950C-2E63C69E3CEF@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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

Dean,

Regarding
>  
>
> We also have a related operation:
>
> 4) Request redirection, which informs an upstream node about a new 
> identity to target instead of the original.
>
Redirection does not always imply a new identity, it could be an 
alternative Contact for the same identity. The thing is that we cannot 
easily distinguish between these, since both use the same response code 
(302). So it can be either rerouting or retargeting. For the problem at 
hand this makes no difference though, in any case the request URI is 
replaced.

BTW what happened to the 'opaque' parameter solution that was part of a 
GRUU draft some versions ago? A special URI parameter that survives 
rerouting/retargeting would avoid introducing yet another identity 
header, and also detection-of-support issues.

Regards,
Jeroen



_______________________________________________
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