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

"Christer Holmberg" <christer.holmberg@ericsson.com> Tue, 04 December 2007 18:01 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 1Izc59-0001Ur-TI; Tue, 04 Dec 2007 13:01:19 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Izc58-0001Uf-8V for sip-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 13:01:18 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izc57-0001UT-T9 for sip@ietf.org; Tue, 04 Dec 2007 13:01:17 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Izc57-0008JN-6H for sip@ietf.org; Tue, 04 Dec 2007 13:01:17 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 5C59621CD0; Tue, 4 Dec 2007 18:58:26 +0100 (CET)
X-AuditID: c1b4fb3c-aff97bb0000030cf-83-47559542296e
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 3DCDB21CBD; Tue, 4 Dec 2007 18:58:26 +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, 4 Dec 2007 18:58:26 +0100
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: VS: [Sip] Delivering request-URI and parameters to UAS via proxy
Date: Tue, 4 Dec 2007 18:58:25 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DFEE08CD@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Delivering request-URI and parameters to UAS via proxy
Thread-Index: Acg2ih6i4UTKPgVSQf2WFbiy3Qsq9wAAR3+U
References: <5D1A7985295922448D5550C94DE29180019B7E52@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, <sip@ietf.org>
X-OriginalArrivalTime: 04 Dec 2007 17:58:26.0114 (UTC) FILETIME=[44BF3220:01C8369F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
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

Hi,
 
In order to think about documenting "alternative solutions", I have a question for clarifications regarding the scope of the problem we are trying to solve.
 
The MECHANISM part of the draft says that a UA supporting the mechanism would indicate it to the registrar, and the registrar would only use the mechanism in case the UA has indicated support for it (that is also shown in the example in the draft). It has also been claimed that this would be backward compatible with an MGC which uses the R-URI to map to ISUP Called Party number, because the MGC does not register so the mechanism would not be used towards it. 
 
My question is: does this mean that the only entity allowed to use this mechanism is the registrar, since the mechanism is used based on whether the UA supports it or not? 
 
When reading the USE-CASE part of the draft, I would say that the answer is "no". Because, as I understand the text, there could be non-registrar entities in the path, which today normally would re-write the R-URI, but would now instead use this mechanism. Is my understanding correct?
 
If so, my next question is: these non-registrar entities have no clue about whether the terminating UA supports the mechanism or not, or whether the call will be routed towards an MGC. So, what happens if the request is routed towards an UA that has not indicated support, or towards an MGC? The MGC may not be able to map the R-URI.
 
Regards,
 
Christer
 
 

________________________________

Lähettäjä: DRAGE, Keith (Keith) [mailto:drage@alcatel-lucent.com]
Lähetetty: ti 4.12.2007 16:27
Vastaanottaja: sip@ietf.org
Aihe: [Sip] Delivering request-URI and parameters to UAS via proxy



(As WG chair)

We have a couple of milestones that we generated as a result of
discussion of

http://www.ietf.org/internet-drafts/draft-rosenberg-sip-ua-loose-route-0
1.txt

Dec 2007    Delivering request-URI and parameters to UAS via proxy to
WGLC 
Feb 2008    Delivering request-URI and parameters to UAS via proxy to
IESG (PS) 

This work is currently stalled and the editor needs input.

The document contains various example scenarios where a solution is
required, for which there appears to be no dispute that a solution is
needed.

The document proposes one solution to resolve these example scenarios,
but this solution is not gaining consensus. At least one other solution
has been talked about, but there is no documentation on the table.

This mail is to identify a deadline for other solutions to the example
scenarios to be documented as internet drafts, showing how the solution
works for those scenarios. This deadline is:

        January 11th 2008

It is appropriate fo these documents to identify any other scenarios
where such a solution is appropriate. Any other input is also welcome in
identifying other scenarios.

If we have no such internet-drafts by this deadline, we will proceed
with completing the solution we have.


Regards

Keith



_______________________________________________
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




_______________________________________________
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