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

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 18 January 2008 15:17 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 1JFsyk-0001eO-Ln; Fri, 18 Jan 2008 10:17:58 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFsyj-0001eD-4M for sip-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 10:17:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFsyi-0001e5-Qr for sip@ietf.org; Fri, 18 Jan 2008 10:17:56 -0500
Received: from host6.216.41.24.conversent.net ([216.41.24.6] helo=etmail.acmepacket.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFsyi-0001Re-Fa for sip@ietf.org; Fri, 18 Jan 2008 10:17:56 -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; Fri, 18 Jan 2008 10:17:52 -0500
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Fri, 18 Jan 2008 10:17:51 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Elwell, John" <john.elwell@siemens.com>, Dean Willis <dean.willis@softarmor.com>, IETF SIP List <sip@ietf.org>
Date: Fri, 18 Jan 2008 10:15:00 -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+/dzx0k6eGS1WWuhtw80L2kAADrUvgABZyvrAADtRW8A==
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC306E4ED497B@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> A <"CA9998CD4A0 20D418654FCDEF4E707DF04173CB8"@esealmw113.eemea.ericsson.se> <"0 D5F89FAC29E2 C41B98A6A762007F5D0593CFF"@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> <E6C2E8958BA59A4FB960963D475F7AC306E4ED4501@mail.acmepacket.com> <0D5F89FAC29E2C41B98A6A762007F5D0594068@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0594068@GBNTHT12009MSX.gb002.siemens.net>
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.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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

Hey John,
Inline...

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]
> Sent: Friday, January 18, 2008 2:48 AM
> >
> > 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.
> [JRE] According to Dean's definition of RT, it does not change the
> Request-URI (only the Route header field presumably, or maybe not even
> that).
> So C, D and E are the same. Also A and B are the same, and F and G are
> the same.
> So I think:
> - UA-Loose-routing gives you C/D/E
> - To gives you A/B
> - PCPID gives you C/D/E
> - Target gives you C/D/E
> - Hist-info gives you A/B, C/D/E and F/G.

Yes, I agree that is the *theory*.  :)
I drew it that way though so we could argue about what the UAS/UALR-draft _wants_ to happen vs. what _will_ happen if P2 or P3 are not purely RT's and didn't support a new draft. (Since it seemed the conversation was going that way previously on this list, for example when Christer pointed out the difference between Target and PCPID)

For example, I think there is more than just a syntax difference between Christer's sip-target-uri-delivery draft (STUD?) and Jonathan's UALR approach.  Though I have no idea which one is better.

-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