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

"Christer Holmberg" <christer.holmberg@ericsson.com> Tue, 15 January 2008 12:49 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 1JElEI-0001Js-LI; Tue, 15 Jan 2008 07:49:22 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JElEH-0001I3-Ks for sip-confirm+ok@megatron.ietf.org; Tue, 15 Jan 2008 07:49:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JElEH-0001Hv-9s for sip@ietf.org; Tue, 15 Jan 2008 07:49:21 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JElEG-0001HQ-MW for sip@ietf.org; Tue, 15 Jan 2008 07:49:21 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id D66842079D; Tue, 15 Jan 2008 13:49:19 +0100 (CET)
X-AuditID: c1b4fb3e-af6a0bb00000459d-27-478cabcf3fea
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A6A0F201C3; Tue, 15 Jan 2008 13:49:19 +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 13:49:19 +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 13:49:18 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0410E90F@esealmw113.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0593A46@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Thread-Index: AchUZtW5bDMRNv3qRbeBDq53RksY6wAC6fXwAAREC3AAAN5tsAAAvlqgAIQb/vAAHhqlMAAKS5DAAAacccAAAIe2AAAE3pIAAADKqtA=
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> A <CA9998CD4A020D418654FCDEF4E707DF040D69C7@esealmw113.eemea.ericsson.se> <0D5F89FAC29E2C41B98A6A762007F5D0549D3F@GBNTHT12009MSX.gb002.siemens.net> A <CA9998CD4A020D418654FCDEF4E707DF0410E399@esealmw113.eemea.ericsson.se> <0D5F89FAC29E2C41B98A6A762007F5D0593A46@GBNTHT12009MSX.gb002.siemens.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>, "Francois Audet" <audet@nortel.com>
X-OriginalArrivalTime: 15 Jan 2008 12:49:19.0513 (UTC) FILETIME=[0B75F890:01C85775]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sip@ietf.org, 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 John, 

>>Target, if present, always represents the current target. A receiving 
>>entity that receives a request without a Target header has to assume 
>>that the Request-URI represents the current target. When no Target 
>>header is available on the request then the Target is inserted when a 
>>reroute is performed.
>> 
>>P-CPI is ONLY used to maintain the R-URI which is rewritten by the 
>>contact of the UAS. I.e. by the home proxy which is usually 
>>at the end of a chain of proxies.
>> 
>>When both Target and P-CPI are used: Target always represents the 
>>current target. P-CPI always represents the AOR received by the home 
>>proxy which may in some cases be the same as the current target but it

>>may also be the last route (not equal to the current target) taken to 
>>deliver the request.
>>
>[JRE] I think I am getting there. So the target could be some 
>sort of call centre group, for example, and P-CPI could be 
>the AoR of the selected member of that group. Correct?

Correct.

>I am a little concerned about using the term "AoR" in the 
>definition of these AoRs. What about a request targeted at a 
>GRUU? I would imagine the Target and P-CPI would both contain 
>the GRUU, which is not an AoR.

Good point. I guess we could simply say URI. We'll fix that in the next
version of the document.

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