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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 17 January 2008 21:12 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 1JFc2O-0005N0-Ds; Thu, 17 Jan 2008 16:12:36 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFc2M-0005Mq-Jw for sip-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 16:12:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFc2M-0005Mi-91 for sip@ietf.org; Thu, 17 Jan 2008 16:12:34 -0500
Received: from host6.216.41.24.conversent.net ([216.41.24.6] helo=etmail.acmepacket.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFc2L-0005lr-TF for sip@ietf.org; Thu, 17 Jan 2008 16:12:34 -0500
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.240.5; Thu, 17 Jan 2008 16:12:30 -0500
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Thu, 17 Jan 2008 16:12:29 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Dean Willis <dean.willis@softarmor.com>, IETF SIP List <sip@ietf.org>
Date: Thu, 17 Jan 2008 16:10:05 -0500
Subject: RE: [Sip] Vocabulary and problem statement for Request-URI, retargeting, and SIP routing (long, but read it!)
Thread-Topic: [Sip] Vocabulary and problem statement for Request-URI, retargeting, and SIP routing (long, but read it!)
Thread-Index: AchZPU+/dzx0k6eGS1WWuhtw80L2kAADrUvg
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC306E4ED4501@mail.acmepacket.com>
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> <"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>
In-Reply-To: <C8D63C78-437F-430E-950C-2E63C69E3CEF@softarmor.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc:
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: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Thursday, January 17, 2008 2:13 PM
>
> Call for clarity on exactly which problems we're solving with UA-
> Loose-Routing, target, CPID, etc. Proposed: target identity, end-to-
> end parameters.

Not exactly.  I believe the idea in the UALR draft is to get the target identity/params created by the nearest re-targeting event relative to the UAS, where those created by the UAC is the default such event (and thus the logical "farthest").  In other words, what you say is true, except if the request got retargeted, the identity and params will be those of the new target, and thus not end-to-end and not always what the UAC sent.  Right?

For example, given the following, where "RTRG" means Re-Targeting, "RRT" means Re-Routing, "RT" means Routing, and the single letters represent connections:

                    RRT
                   +---+
                   |R1 |
                B /+---+\ C
            RT   /       \  RT
           +---+/         \+---+
           |P1 |           |P1 |
        A /+---+           +---+\ D
         /                       \
   +---+/                         \+---+
   |UAC|                           |UAS|
   +---+                           +---+

UA-Loose-routing wants the req-uri seen on connection "A" I think.
To header gives you A.
PCPID gives you B.
Hist-Info gives you A,B,C.


But in the re-targeting scenario such as:
                    RTRG                    RRT
                   +---+                   +---+
                   |R1 |                   |R2 |
                B /+---+\ C             E /+---+\ F
            RT   /       \  RT      RT   /       \  RT
           +---+/         \+---+ D +---+/         \+---+
           |P1 |           |P2 +---+P3 |           |P4 |
        A /+---+           +---+   +---+           +---+\ G
         /                                               \
   +---+/                                                 \+---+
   |UAC|                                                   |UAS|
   +---+                                                   +---+

UA-Loose-routing wants the req-uri seen on connection "C" I think.
To header gives you A.
PCPID gives you E.
Hist-Info gives you A,B,C,D,E,F.

-hadriel



_______________________________________________
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