Re: [Sipping-tispan] Requirements 02e

Paul Kyzivat <pkyzivat@cisco.com> Mon, 26 September 2005 14:56 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJuPQ-0000km-3h; Mon, 26 Sep 2005 10:56:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJuPO-0000jO-Ci for sipping-tispan@megatron.ietf.org; Mon, 26 Sep 2005 10:56:46 -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 KAA02649 for <sipping-tispan@ietf.org>; Mon, 26 Sep 2005 10:56:44 -0400 (EDT)
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 1EJuWR-0007cW-H3 for sipping-tispan@ietf.org; Mon, 26 Sep 2005 11:04:04 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 26 Sep 2005 07:56:35 -0700
X-IronPort-AV: i="3.97,146,1125903600"; d="scan'208"; a="345565456:sNHT95995410"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8QEu9KU002160; Mon, 26 Sep 2005 07:56:31 -0700 (PDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 26 Sep 2005 10:56:24 -0400
Received: from [161.44.79.87] ([161.44.79.87]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 26 Sep 2005 10:56:23 -0400
Message-ID: <43380C17.5030207@cisco.com>
Date: Mon, 26 Sep 2005 10:56:23 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
Subject: Re: [Sipping-tispan] Requirements 02e
References: <000001c5be7e$3326ba60$11b04c0a@china.huawei.com> <43311155.8030102@nokia.com> <43316297.8010007@cisco.com> <43324ACD.8060108@nokia.com> <43330163.2090401@cisco.com> <4333D486.50505@nokia.com>
In-Reply-To: <4333D486.50505@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Sep 2005 14:56:23.0953 (UTC) FILETIME=[76937010:01C5C2AA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: sipping-tispan@ietf.org
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


Miguel Garcia wrote:
> 
> 
> Paul Kyzivat wrote:
> 
>>
>>
>> Miguel Garcia wrote:
>>
>>> That is my understanding. If I recall correctly, the idea is to 
>>> emulate the PBX, where the callee can indicate a direct-to-call 
>>> number (URI).
>>
>>
>>
>> OK, so the callee can indicate it. What happens at the calling end? Is 
>> it displayed instead of the callerid? Is it displayed in addition to 
>> the callerid? Is it retained by the calling UA and used in some 
>> circumstance?
>>
>> This sounds a lot like the SIP Reply-To header, which can be there and 
>> carry information, but which has never had any clear utility, and so 
>> has essentially never been used.
> 
> 
> 
> Actually, when we have been discussion solutions, the Reply-To header 
> came one possibility to look at.
> 
> You say that the Reply-To header has no clear utility, and perhaps, this 
> is an application where it could have a clear utility. I would expect 
> this information to be offered by the UI, perhaps when saving the contact.

That would perhaps be helpful in supporting some *new* services. How 
would it help in a simulation service? Apparently it is simulating some 
existing service that has such an address. What is that service? How is 
this additional information used? Is it additional callerid info?

	Paul

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