IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@cisco.com> Fri, 18 January 2008 14:57 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 1JFsen-0004Jb-KU; Fri, 18 Jan 2008 09:57:21 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFsem-0004H7-Bg for sip-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 09:57:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFsel-0004F4-W9 for sip@ietf.org; Fri, 18 Jan 2008 09:57:20 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFsek-00012q-IK for sip@ietf.org; Fri, 18 Jan 2008 09:57:19 -0500
X-IronPort-AV: E=Sophos;i="4.25,216,1199682000"; d="scan'208";a="83763570"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 18 Jan 2008 09:57:19 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0IEvICl002194; Fri, 18 Jan 2008 09:57:18 -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 m0IEv0uq018036; Fri, 18 Jan 2008 14:57:17 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 Jan 2008 09:57:05 -0500
Received: from [161.44.174.133] ([161.44.174.133]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 Jan 2008 09:57:05 -0500
Message-ID: <4790BE45.4040804@cisco.com>
Date: Fri, 18 Jan 2008 09:57:09 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
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> <479058E4.2050902@zonnet.nl>
In-Reply-To: <479058E4.2050902@zonnet.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jan 2008 14:57:05.0530 (UTC) FILETIME=[640095A0:01C859E2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=512; t=1200668238; x=1201532238; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20=09Vocabulary=20and=20problem=2 0statement=20for=20Request-URI,=09retargeting,=0A=20and=20SI P=20routing=20(long,=20but=20read=20it!) |Sender:=20 |To:=20Jeroen=20van=20Bemmel=20<jbemmel@zonnet.nl>; bh=AjS8Jrj/DJVKlFGq1CHSz76/aYODdxsDVaB2bJNIR7E=; b=ZvksJmvOMEm05rKD8BWUfhCOn5MnxWilq7wbClm2lFhnCBB9XnRqEL54AP eMj8uy9edq3PXOQ1AiR8XAEGtqOmP3GsA5fuJFNcIye9uMSIrBB3HYYiy+Zv K8ZfDzrd2L;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: IETF SIP List <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
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


Jeroen van Bemmel wrote:

> 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.

It was judged to be a hack and rejected. That was one of the motivations 
for the current proposal, which (at the time) was thought to be cleaner. 
In hindsight maybe it wasn't so much cleaner. :-)

	Paul


_______________________________________________
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

v2.23.0 | Report a Bug | By Email