Re: [Sipping-tispan] Requirements -02h

Paul Kyzivat <pkyzivat@cisco.com> Fri, 30 September 2005 15:06 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELMT3-0007qK-Sh; Fri, 30 Sep 2005 11:06:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELMT3-0007qF-0W for sipping-tispan@megatron.ietf.org; Fri, 30 Sep 2005 11:06:33 -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 LAA15976 for <sipping-tispan@ietf.org>; Fri, 30 Sep 2005 11:06:31 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELMas-0007z6-Vx for sipping-tispan@ietf.org; Fri, 30 Sep 2005 11:14:42 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 30 Sep 2005 08:06:21 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8UF5V5I020663; Fri, 30 Sep 2005 08:06:18 -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); Fri, 30 Sep 2005 11:06:16 -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); Fri, 30 Sep 2005 11:06:16 -0400
Message-ID: <433D5467.8040102@cisco.com>
Date: Fri, 30 Sep 2005 11:06:15 -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 -02h
References: <433D0C9B.8070804@nokia.com>
In-Reply-To: <433D0C9B.8070804@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Sep 2005 15:06:16.0398 (UTC) FILETIME=[815A5EE0:01C5C5D0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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:
> ok, so here it goes with a new iteration:

> Changes:
> - Clarification that we don't list every single requirement that we have.

As I noted elsewhere, I am finding this to be a problem. The 
reinterpretation of the requirements relative to SIP rather than ISDN is 
not entirely straightforward, expecially to those of us who aren't 
familiar with ISDN.

As a result, much of the sip community here cannot properly participate 
in evaluating the proposed changes.

Also, the requirements for changes presume not only the interpretation 
of the feature, but also the contemplated implementation. I don't find a 
request for a new sip feature meaningful without being presented with 
the use case where it will be used.

	Paul

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