Re: [Sipping-tispan] requirements -02f

Paul Kyzivat <pkyzivat@cisco.com> Fri, 23 September 2005 03:00 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIdnL-0006p0-TG; Thu, 22 Sep 2005 23:00:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIdnJ-0006oh-MB for sipping-tispan@megatron.ietf.org; Thu, 22 Sep 2005 23:00:14 -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 XAA01578 for <sipping-tispan@ietf.org>; Thu, 22 Sep 2005 23:00:11 -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 1EIdte-0007kR-8G for sipping-tispan@ietf.org; Thu, 22 Sep 2005 23:06:48 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 22 Sep 2005 20:00:01 -0700
X-IronPort-AV: i="3.97,139,1125903600"; d="scan'208"; a="344696241:sNHT34477166"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8N2xjKK006893; Thu, 22 Sep 2005 19:59:54 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 22 Sep 2005 19:59:41 -0700
Received: from [10.89.16.54] ([10.89.16.54]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 22 Sep 2005 19:59:32 -0700
Message-ID: <43336F9B.8090404@cisco.com>
Date: Thu, 22 Sep 2005 22:59:39 -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 -02f
References: <43328BD5.40500@nokia.com>
In-Reply-To: <43328BD5.40500@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Sep 2005 02:59:32.0861 (UTC) FILETIME=[D2BA62D0:01C5BFEA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: "'sipping-tispan@ietf.org'" <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


Miguel Garcia wrote:
> Hi:
> 
> I have added one more requirement, CDIV, to our draft.

>    REQ-CDIV-1: It must be possible that the caller is informed that a
>                communication is being diverted.

I can't understand what this is requiring. The fact that it must be 
possible to inform the caller does not say that the caller will in fact 
be informed. Is the decision about whether the caller is informed to be 
made by the caller or the callee, or somebody else?

>    REQ-CDIV-2: It must be possible for the diverting user to express his
>                privacy requirements with respect his identity.

Again, just because the user expressed requirements does not endure they 
will be honored. What is the real requirement?

>    REQ-CDIV-3: The reason of the redirection must be available to both
>                the caller and callee.

Is there a clear distinction between a redirection and a simple 
forwarding? Is there a list of the possible reasons? What if none of the 
possible reasons is applicable? What if the reason for forwarding is not 
known?

>    REQ-CDIV-4: The history of the communication must be available to
>                both the caller and callee.

Are you talking about History-Info? "history of the communication" could 
mean many things, including a complete log of all the media that were 
exchanged.

	Paul

P.S. It is getting increasingly frustrating to figure out why we must 
include a buggy whip holder in the design for our new car, and what the 
car must do when whipped in various ways.

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