Re: [Sipping-tispan] Requirements -02h

Paul Kyzivat <pkyzivat@cisco.com> Mon, 03 October 2005 12:44 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMPgB-00019j-2U; Mon, 03 Oct 2005 08:44:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMPg9-00019d-N8 for sipping-tispan@megatron.ietf.org; Mon, 03 Oct 2005 08:44:25 -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 IAA26059 for <sipping-tispan@ietf.org>; Mon, 3 Oct 2005 08:44:24 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMPob-000664-43 for sipping-tispan@ietf.org; Mon, 03 Oct 2005 08:53:11 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 03 Oct 2005 05:44:14 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,168,1125903600"; d="scan'208"; a="12153421:sNHT21587128"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j93ChWRN029510; Mon, 3 Oct 2005 08:44:11 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 3 Oct 2005 08:44:10 -0400
Received: from [10.86.242.143] ([10.86.242.143]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 3 Oct 2005 08:44:09 -0400
Message-ID: <43412798.2030500@cisco.com>
Date: Mon, 03 Oct 2005 08:44:08 -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> <433D5467.8040102@cisco.com> <43411F55.9060500@nokia.com>
In-Reply-To: <43411F55.9060500@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Oct 2005 12:44:09.0647 (UTC) FILETIME=[2640ABF0:01C5C818]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
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 Paul:
> 
> I am aware that this version does not contain a comprehensive list of 
> requirements. I don't know how to deal with this, honestly speaking, it 
> seems to be a lot of work to list all the requirements when we can 
> foresee they can be easily implemented with SIP without further extensions.

Before a sip solution can be specified, the requirements must, 
explicitly or implicitly, be interpretted in the context of the sip 
operating environment. Doing this implicitly is to guarantee 
disagreement about the validity of the chosen solution. I don't deny 
that it is work. But it seems to be work that must be done in any case, 
though it otherwise might not be done in IETF. It makes sense to me that 
this work at least be shared with the IETF. Doing that interpretation is 
really work that TISPAN must ultimately do, though people here are 
probably willing to express opinions. Naively, I am inclined to hope 
that this work has already been done, but we just haven't yet seen it.

	Paul

> Need to think a plan.
> 
> /Miguel
> 
> Paul Kyzivat wrote:
> 
>>
>>
>> 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