Re: [Sip] Delivering request-URI and parameters to UAS via proxy - new version of the draft-holmberg-sip-target-uri-delivery draft

Enrico Marocco <enrico.marocco@telecomitalia.it> Wed, 16 January 2008 17:41 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 1JFCGa-0002aY-Ag; Wed, 16 Jan 2008 12:41:32 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFCGX-0002aC-Vf for sip-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 12:41:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFCGX-0002a4-LL for sip@ietf.org; Wed, 16 Jan 2008 12:41:29 -0500
Received: from maild.telecomitalia.it ([156.54.233.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFCGV-0005K9-UX for sip@ietf.org; Wed, 16 Jan 2008 12:41:29 -0500
Received: from ptpxch009ba020.idc.cww.telecomitalia.it ([156.54.240.52]) by maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 18:41:26 +0100
Received: from ptpxch006ba020.idc.cww.telecomitalia.it ([156.54.240.45]) by ptpxch009ba020.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 18:41:26 +0100
Received: from [10.229.8.45] ([10.229.8.45]) by ptpxch006ba020.idc.cww.telecomitalia.it over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 18:41:25 +0100
Message-ID: <478E4256.7020306@telecomitalia.it>
Date: Wed, 16 Jan 2008 18:43:50 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Delivering request-URI and parameters to UAS via proxy - new version of the draft-holmberg-sip-target-uri-delivery draft
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><1ECE0EB50388174790F9694F77522CCF1438F1B0@zrc2hxm0.corp.nortel.com><478CEFB4.6070002@zonnet.nl> <CA9998CD4A020D418654FCDEF4E707DF0413D587@esealmw113.eemea.ericsson.se> <CA9998CD4A020D418654FCDEF4E707DF0413D6C2@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0413D6C2@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 16 Jan 2008 17:41:25.0138 (UTC) FILETIME=[03F5DF20:01C85867]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: 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>
Content-Type: multipart/mixed; boundary="===============1385929724=="
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
> We've uploaded a new version (-01) of the Target draft.
> 
> We've tried to make things more clear. I've also removed all text about
> P-Called-Party-ID, except from one chapter where we try to explain the
> semantical difference between Target and P-CPI.

Thanks Christer, the new version is pretty clear about the difference
between Target and P-Called-Party-ID.  However, other than the semantic
difference, I'd also add that the Target header could be used in a
cross-domain registration case, when the registered contact for a
specific URI is an AOR itself targeting a different domain.  As far as I
know, such a case is uncommon in current SIP deployments, but it could
appear more frequently with P2PSIP overlays, e.g. when peers with
limited connectivity make themselves globally reachable using P2P URIs
(maybe temporary ones).

-- 
Ciao,
Enrico
_______________________________________________
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