Re: [Sipping-tispan] Re: TIP/TIR requirements

Miguel Garcia <Miguel.An.Garcia@nokia.com> Wed, 07 September 2005 18:21 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED4Xm-0006Jx-Q1; Wed, 07 Sep 2005 14:21:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED4Xl-0006Jp-9D for sipping-tispan@megatron.ietf.org; Wed, 07 Sep 2005 14:21:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07522 for <sipping-tispan@ietf.org>; Wed, 7 Sep 2005 14:21:08 -0400 (EDT)
Received: from mgw-ext04.nokia.com ([131.228.20.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED4ay-0006Hh-U4 for sipping-tispan@ietf.org; Wed, 07 Sep 2005 14:24:29 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j87IJe1L007167; Wed, 7 Sep 2005 21:19:43 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Sep 2005 21:21:06 +0300
Received: from [127.0.0.1] ([10.162.19.205]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 7 Sep 2005 21:21:05 +0300
Message-ID: <431F2F91.9060804@nokia.com>
Date: Wed, 07 Sep 2005 21:21:05 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping-tispan] Re: TIP/TIR requirements
References: <072C5B76F7CEAB488172C6F64B30B5E38A38B9@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E38A38B9@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Sep 2005 18:21:05.0825 (UTC) FILETIME=[E94B2110:01C5B3D8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: 7bit
Cc: sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

I am certainly not the expert in supplementary services in the PSTN, but 
  I have been told that this identity is never asserted by the network, 
so the callee can put there whatever he wants.

During the discussions of solutions we looked at headers like Reply-To, 
and In-Reply-To, but their semantics are well defined and do not match 
the requirements.

/Miguel

Michael Hammer (mhammer) wrote:

> If this is not an asserted identity, then what good is it?
> 
> I thought that the CLIP and COLP were complementary and identical in
> type.  But, perhaps that is a subtlety I missed.
> 
> Mike
> 
> 
> 
>>-----Original Message-----
>>From: sipping-tispan-bounces@ietf.org 
>>[mailto:sipping-tispan-bounces@ietf.org] On Behalf Of Miguel Garcia
>>Sent: Wednesday, September 07, 2005 4:03 AM
>>To: Schmidt, Christian
>>Cc: sipping-tispan@ietf.org; Alexeitsev, D
>>Subject: [Sipping-tispan] Re: TIP/TIR requirements
>>
>>Inline discussion.
>>
>>Schmidt, Christian wrote:
>>
>>
>>>Some comments / questions concerning the TIP/TIR requirements:
>>>
>>>- What happens, when the caller is in PSTN and the callee 
>>
>>provides a 
>>
>>>SIP URI as identity? Will it be translated at the gateway 
>>
>>to a E.164 number?
>>
>>I don't know what people want to do in this scenario, but in 
>>my opinion the responsibility lies in the calee, so if the 
>>callee offers only a SIP URI, and not both a SIP URI and TEL 
>>URL, then the network shouldn't be doing this type of 
>>translations. Remember that this is not an asserted identity, 
>>so this should be end-to-end information
>>
>>
>>>- TIP-1: type error: calle > callee
>>
>>Fixed.
>>
>>
>>>- How to handle identity restriction from PSTN/ISDN side? Sould the 
>>>gateway delete both identity information and restriction 
>>
>>information 
>>
>>>in this case?
>>
>>If we build on the trust model, and if we consider that the 
>>PSTN Gateway trusts the IMS network, then I would say no, 
>>delete at the trusted/not-trusted boundary.
>>
>>
>>
>>>EQ-TIP-4: If identity information and restriction indication is 
>>>included in a message, the gateway may not transfer the 
>>
>>identity information.
>>
>>Is this a proposal for a new requirement? What is the actual 
>>requirement here? This looks like a clarification.
>>
>>/Miguel
>>
>>>
>>>Regards,
>>>Christian
>>>
>>
>>-- 
>>Miguel A. Garcia           tel:+358-50-4804586
>>sip:miguel.an.garcia@openlaboratory.net
>>Nokia Research Center      Helsinki, Finland
>>
>>
>>_______________________________________________
>>Sipping-tispan mailing list
>>Sipping-tispan@ietf.org
>>https://www1.ietf.org/mailman/listinfo/sipping-tispan
> 
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.an.garcia@openlaboratory.net
Nokia Research Center      Helsinki, Finland


_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan