RE: [Sip] RE: Delivering request-URI and parameters to UAS via proxy

"Christer Holmberg" <christer.holmberg@ericsson.com> Tue, 15 January 2008 08:48 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 1JEhT7-0006rg-Dh; Tue, 15 Jan 2008 03:48:25 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JEhT5-0006rb-F1 for sip-confirm+ok@megatron.ietf.org; Tue, 15 Jan 2008 03:48:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JEhSy-0006pr-OP for sip@ietf.org; Tue, 15 Jan 2008 03:48:16 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JEhSw-00084K-VF for sip@ietf.org; Tue, 15 Jan 2008 03:48:16 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id C68EA213F8; Tue, 15 Jan 2008 09:48:11 +0100 (CET)
X-AuditID: c1b4fb3e-ae69ebb00000459d-5f-478c734b8377
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 988C1211F4; Tue, 15 Jan 2008 09:48:11 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Jan 2008 09:48:11 +0100
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] RE: Delivering request-URI and parameters to UAS via proxy
Date: Tue, 15 Jan 2008 09:48:10 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF040D69C7@esealmw113.eemea.ericsson.se>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1434B83B@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Thread-Index: AchUZtW5bDMRNv3qRbeBDq53RksY6wAC6fXwAAREC3AAAN5tsAAAvlqgAIQb/vAAHhqlMAAKS5DA
References: <5D1A7985295922448D5550C94DE2918001AC02E9@DEEXC1U01.de.lucent.com><CA9998CD4A020D418654FCDEF4E707DF040266B1@esealmw113.eemea.ericsson.se><47878B1E.3010303@cisco.com><0D5F89FAC29E2C41B98A6A762007F5D0549A47@GBNTHT12009MSX.gb002.siemens.net><1ECE0EB50388174790F9694F77522CCF1428F69B@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF04051C9D@esealmw113.eemea.ericsson.se> <1ECE0EB50388174790F9694F77522CCF1428F846@zrc2hxm0.corp.nortel.com> <CA9998CD4A020D418654FCDEF4E707DF040960B7@esealmw113.eemea.ericsson.se> <1ECE0EB50388174790F9694F77522CCF1434B83B@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>
X-OriginalArrivalTime: 15 Jan 2008 08:48:11.0344 (UTC) FILETIME=[5BC29500:01C85753]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: sip@ietf.org, "Elwell, John" <john.elwell@siemens.com>, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.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

Hi, 

P-CPI could probably be useful in some cases, in addition to Loose
Route/Target. And, as the draft says, P-CPI will still have to be used
in IMS, because there are procedures defined for it.

However, again, the purpose of the draft was to provide an alternative
to the Loose Route alternative, and that alternative is Target only. 

I am working on an updated version of the draft to make that more clear.

Regards,

Christer





>Hum. I guess then P-Called-ID would then be useful with 
>Loose-route as well (although now I'm thinking that 
>History-Info covers it).
> 
>I think explaining all that in great and precise details, 
>with a concrete example would be very useful.
> 
>And then we could compare P-Target with Loose-route. 





> 
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> > Sent: Monday, January 14, 2008 03:56
> > To: Audet, Francois (SC100:3055)
> > Cc: sip@ietf.org; DRAGE, Keith (Keith); Paul Kyzivat; Elwell, John
> > Subject: RE: [Sip] RE: Delivering request-URI and parameters to UAS 
> > via proxy
> > 
> > 
> > Hi Francois,
> > 
> > >I think what you meant by Target was more the "Current" 
> > >target as opposed to the Initiatl Target.
> > 
> > Yes.
> >  
> > >And if that's the case, then I don't see why it is different from 
> > >P-Called-ID (although I might be missing something with what the 
> > >P-Called_ID is supposed to be).
> > 
> > In the draft we try to explain the difference. But, we are 
> working on 
> > the text to make it more clear.
> > 
> > The P-CPI is inserted when the R-URI is rewritten by the Contact 
> > address of the UAS. RFC3455 calls that operation 
> "retargeting", but we 
> > don't think that is the definition for retarget used in the 
> > ua-loose-route draft, which says:
> > 
> > "When a home proxy receives a request and accesses a 
> location service, 
> > the resulting contact(s) obtained from the location service are 
> > considered the last hop in the route towards the entity 
> addressed by 
> > the Request-URI.  Since that target, almost by definition, 
> can claim 
> > the identity of the URI prior to translation, the operation 
> is one of 
> > routing and not retargeting."
> > 
> > So, if we follow the definitions in the ua-loose-route draft, P-CPI 
> > would be inserted due to a reroute - not retarget.
> > 
> > But, no matter whether we call it retarget or reroute, the point is 
> > that the P-CPI is inserted when the R-URI is rewritten with the 
> > Contact address of the UAS. The scope of Target is wider than that, 
> > and can be used in any retargeting situation.
> > 
> > Regards,
> > 
> > Christer
> > 
> > 
> 


_______________________________________________
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