IETF Logo Mail Archive

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

"Francois Audet" <audet@nortel.com> Fri, 11 January 2008 19: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 1JDPpH-00032g-03; Fri, 11 Jan 2008 14:45:59 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JDPpG-00032b-FV for sip-confirm+ok@megatron.ietf.org; Fri, 11 Jan 2008 14:45:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDPpG-00032T-59 for sip@ietf.org; Fri, 11 Jan 2008 14:45:58 -0500
Received: from zcars04e.nortel.com ([47.129.242.56]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDPpF-0001RU-PE for sip@ietf.org; Fri, 11 Jan 2008 14:45:58 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id m0BJgFK01241; Fri, 11 Jan 2008 19:42:15 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Date: Fri, 11 Jan 2008 13:45:54 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF1428F846@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF04051C9D@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Thread-Index: AchUZtW5bDMRNv3qRbeBDq53RksY6wAC6fXwAAREC3AAAN5tsAAAvlqg
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>
From: Francois Audet <audet@nortel.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: sip@ietf.org, "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens.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

 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Friday, January 11, 2008 11:33
> To: Audet, Francois (SC100:3055)
> Cc: sip@ietf.org; Elwell, John; Paul Kyzivat; DRAGE,Keith (Keith)
> Subject: RE: [Sip] RE: Delivering request-URI and parameters 
> to UAS via proxy
>
> >The Target seems identical to the To header field.
> 
> I don't think they are identical. Jonathan's draft describes 
> the issues with using the To header.

Well, your description of "Target" in your draft is indentical to
the description of the "To" header.

What Jonathan describes as limitations of "To" is that it doesn't
reflect any "retargeting".

I think what you meant by Target was more the "Current" target as opposed
to the Initiatl Target.

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


_______________________________________________
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