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

Jonathan Rosenberg <jdrosen@cisco.com> Wed, 05 December 2007 22:02 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 1J02KI-00087V-7R; Wed, 05 Dec 2007 17:02:42 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J02KG-00087G-JN for sip-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 17:02:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J02KG-000875-9F for sip@ietf.org; Wed, 05 Dec 2007 17:02:40 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J02KF-00009f-MG for sip@ietf.org; Wed, 05 Dec 2007 17:02:40 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 05 Dec 2007 14:02:39 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id lB5M2dq6002256; Wed, 5 Dec 2007 14:02:39 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id lB5M2c1f024572; Wed, 5 Dec 2007 22:02:38 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 14:02:38 -0800
Received: from [10.21.94.113] ([10.21.94.113]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 14:02:38 -0800
Message-ID: <47572024.9000901@cisco.com>
Date: Wed, 05 Dec 2007 17:03:16 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: VS: [Sip] Delivering request-URI and parameters to UAS via proxy
References: <5D1A7985295922448D5550C94DE29180019B7E52@DEEXC1U01.de.lucent.com> <CA9998CD4A020D418654FCDEF4E707DFEE08CD@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DFEE08CD@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Dec 2007 22:02:38.0605 (UTC) FILETIME=[8CB9A3D0:01C8378A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2643; t=1196892159; x=1197756159; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Re=3A=20VS=3A=20[Sip]=20Delivering=20request-URI=20and=20para meters=20to=20UAS=20via=20proxy |Sender:=20; bh=AvzhtGuB1/BL+qg8mK3710nRrktpxPbGX5+Z0a7p6ao=; b=pYsxqRlftTXr3cQgPfiu3pR4JRzAqEpelBdmf4x97Ir5Rrw9Uz8t68ppi32amKSqiWozbr82 bB5sKvOqldT9E0NxovOkDUDDJj4jNKZQoqY5/ge5Vu0ACy3RhdfvJUO2;
Authentication-Results: sj-dkim-3; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: sip@ietf.org, "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.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


Christer Holmberg wrote:
> 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).

For when a proxy is talking to a registered UA, yes.

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

That is not the intent.

The idea is, any proxy that is translating a request-URI, is doing so 
based on some kind of mapping table. There are many ways that this 
mapping table can get into the proxy:

1. dynamically through register
2. provisioned
3. through an enum query
etc.

If we take provisioning as an example (i.e., someone enters phone number 
routing rules via prefix matching rules), when those rules are 
provisioned, they would include a flag which says whether the 
destination is loose-route compliant. If they are loose route compliant, 
the proxy uses a Route header, else it uses r-uri translation as is 
currently done.

> 
> 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?

As above, no.

> 
> 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?

Yes.

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

Hopefully the above paragraph answers your question.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com


_______________________________________________
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