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

"Michael Hammer \(mhammer\)" <mhammer@cisco.com> Wed, 07 September 2005 16:23 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED2hk-0000ZB-UY; Wed, 07 Sep 2005 12:23:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED2hj-0000Y6-6e for sipping-tispan@megatron.ietf.org; Wed, 07 Sep 2005 12:23:19 -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 MAA00151 for <sipping-tispan@ietf.org>; Wed, 7 Sep 2005 12:23:16 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED2ku-0002Tj-Rr for sipping-tispan@ietf.org; Wed, 07 Sep 2005 12:26:38 -0400
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by sj-iport-1.cisco.com with ESMTP; 07 Sep 2005 09:23:06 -0700
X-IronPort-AV: i="3.96,176,1122879600"; d="scan'208"; a="658649682:sNHT32342216"
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j87GMegs029304; Thu, 8 Sep 2005 00:23:03 +0800 (CST)
Received: from xbh-rtp-201.amer.cisco.com ([64.102.31.12]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 8 Sep 2005 00:22:52 +0800
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Sep 2005 12:22:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping-tispan] Re: TIP/TIR requirements
Date: Wed, 7 Sep 2005 12:22:28 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E38A38B9@xmb-rtp-20b.amer.cisco.com>
Thread-Topic: [Sipping-tispan] Re: TIP/TIR requirements
Thread-Index: AcWzg69FJas1JNTAQjypd4dsKKMevgARFpjQ
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, "Schmidt, Christian" <christian-schmidt@siemens.com>
X-OriginalArrivalTime: 07 Sep 2005 16:22:29.0297 (UTC) FILETIME=[57832210:01C5B3C8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: quoted-printable
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

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
> 

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