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

Paul Kyzivat <pkyzivat@cisco.com> Mon, 28 January 2008 20:45 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 1JJarZ-00050E-Hz; Mon, 28 Jan 2008 15:45:53 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JJarX-000509-U2 for sip-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 15:45:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJarX-0004zz-KB for sip@ietf.org; Mon, 28 Jan 2008 15:45:51 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJarW-0003Qp-Ov for sip@ietf.org; Mon, 28 Jan 2008 15:45:51 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 28 Jan 2008 15:45:51 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m0SKjo0V031204; Mon, 28 Jan 2008 15:45:50 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0SKjNJb019057; Mon, 28 Jan 2008 20:45:50 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jan 2008 15:45:41 -0500
Received: from [161.44.174.133] ([161.44.174.133]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jan 2008 15:45:40 -0500
Message-ID: <479E3EF9.1080109@cisco.com>
Date: Mon, 28 Jan 2008 15:45:45 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: youssef.chadli@orange-ftgroup.com
Subject: Re: [Sip] Delivering request-URI and parameters to UAS via proxy
References: <2AF8FF7D89242541B12E7A47F6ECB4BE06990C59@ftrdmel3>
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE06990C59@ftrdmel3>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 28 Jan 2008 20:45:40.0580 (UTC) FILETIME=[BE797240:01C861EE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5018; t=1201553150; x=1202417150; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20Delivering=20request-URI=20and= 20parameters=20to=20UAS=20via=20proxy |Sender:=20 |To:=20youssef.chadli@orange-ftgroup.com; bh=qNkEVJv0he1skCMXINeWgSkAECs9FDD2/5O5TbAqiYw=; b=vx6n4tVg2osd7kIvkq5gZTjReoKBprSFlv/hl6JtFSuxjgx51W21SbiSHS Cv44BFQ6D/85KPPhq9YHzidT5fq6vhn/zDtPnvOm9fNEVe/BTu++EYeygEfw CQ8yHy9K31;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: sip@ietf.org, 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

These cases can all be handled by having intermediate entity use a 
unique user part, together with its own domain name, to construct a 
contact address for each terminal UA that it is registering. Then when 
it receives an incoming request to one of these uris it can simply 
translate it, using the user part as a key to its own local mappings.

We don't need anything new to solve these cases.

	Paul

youssef.chadli@orange-ftgroup.com wrote:
>  
> There are other cases similar to what is described in section  2.1 Unknown Aliases of J. Rosenberg draft that should be taken into account. 
> 
> Those cases are where the customer side is composed of several SIP terminals that access the network through an intermediate entity which registers their associated aliases with its contact address. Thus, such client side is seen from the network as a single client having several aliases (aggregated endpoints). Moreover, such client side may be a mini private network composed of several entities. In these configurations, the intermediate entity is in charge of routeing incoming calls inside the client domain and may need to behave as a SIP proxy for incoming SIP messages.  
> 
> As examples of such configuration:
> - Corporate networks: in that case the PBX register all the served individual user identities with its contact address and routes incoming calls toward the individual called users.
> - Home networks: the Home Gateway may need to register on behalf of all the served terminals.  The Home Gateway is in charge of routeing incoming calls toward the individual called users. 
> 
> J. Rosenberg draft seems give a good solution to take into account these configurations.
>    
> Best regards,
> 
> Youssef
> 
> 
>> -----Message d'origine-----
>> De : DRAGE, Keith (Keith) [mailto:drage@alcatel-lucent.com] 
>> Envoyé : lundi 14 janvier 2008 17:58
>> À : sip@ietf.org
>> Objet : [Sip] Delivering request-URI and parameters to UAS via proxy
>>
>> (As WG chair)
>>
>> In fulfilment of our charter items of
>>
>> 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)
>>
>> We now have a couple of proposals on the table for solving 
>> the problem.
>>
>> The original draft from Jonathan and which led to the 
>> creation of the charter items by the WG is unfortunately 
>> expired, but is at:
>>
>> http://tools.ietf.org/id/draft-rosenberg-sip-ua-loose-route-01.txt
>>
>> The alternative document from Christer, etc is at:
>>
>> http://www.ietf.org/internet-drafts/draft-holmberg-sip-target-
>> uri-delive
>> ry-00.txt
>>
>> We obviously need to make a decision between the two 
>> approaches so please attempt to address the following 
>> specific points via the mailing
>> list:
>>
>> 1)	Problem cases: These are summarised in section 4.4 of
>> draft-rosenberg-sip-ua-loose-route-01 and from my read of the 
>> other draft, I don't believe that this draft adds any others. 
>> If you believe there are other cases that should be covered 
>> by the solution, then please identify them. If there is 
>> support on any new problem cases, I would encourage the 
>> authors of both drafts to add text concerning these problem cases.
>>
>> 2)	Clarifications: If for any reason you don't understand either
>> draft, or believe that there are technical issues that are 
>> not represented in the current draft, please post your 
>> questions / comments to the list. I would encourage authors 
>> of both drafts to revise as frequently as appropriate to 
>> reflect the current state of discussion.
>>
>> 3)	Support for either position. If you wish to indicate support for
>> either position please do so, but please accompany this is 
>> technical reasoning as to why you have this position, as that 
>> will help other members of the WG form a position.
>>
>> I would encourage as much list discussion as possible before 
>> Philadelphia. I suspect we will need to have a discussion at 
>> the face-to-face meeting in Philadephia, but list discussion 
>> is essential prior to that. If we can solve this positions on 
>> list, then well and good, and even better (that is how we are 
>> meant to make decisions).
>>
>> 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
> 


_______________________________________________
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