Re: [v6tc] v6tc - is there life

"Soininen Jonne (Nokia-NET/Helsinki)" <jonne.soininen@nokia.com> Thu, 18 November 2004 19:03 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22104; Thu, 18 Nov 2004 14:03:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUrbQ-0000eL-I3; Thu, 18 Nov 2004 14:05:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUrIF-0000kd-5d; Thu, 18 Nov 2004 13:46:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUrAs-0006AQ-0A for v6tc@megatron.ietf.org; Thu, 18 Nov 2004 13:38:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19973 for <v6tc@ietf.org>; Thu, 18 Nov 2004 13:38:28 -0500 (EST)
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUrDW-0008Tp-Lo for v6tc@ietf.org; Thu, 18 Nov 2004 13:41:16 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAIIcNv04913; Thu, 18 Nov 2004 20:38:24 +0200 (EET)
X-Scanned: Thu, 18 Nov 2004 20:38:11 +0200 Nokia Message Protector V1.3.31 2004060815 - RELEASE
Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iAIIcBsW007159; Thu, 18 Nov 2004 20:38:11 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks004.ntc.nokia.com 00drY7MX; Thu, 18 Nov 2004 20:38:09 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAIIc9S20494; Thu, 18 Nov 2004 20:38:09 +0200 (EET)
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Thu, 18 Nov 2004 20:38:07 +0200
Received: from esebe054.NOE.Nokia.com ([172.21.143.44]) by esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Thu, 18 Nov 2004 20:38:06 +0200
Received: ESEBE054.noe.nokia.com 172.21.143.44 from 172.21.155.64 172.21.155.64 via HTTP with MS-WebStorage 6.0.6249
Received: from essrv103nok15564.ntc.nokia.com by ESEBE054.noe.nokia.com; 18 Nov 2004 20:38:07 +0200
Subject: Re: [v6tc] v6tc - is there life
From: "Soininen Jonne (Nokia-NET/Helsinki)" <jonne.soininen@nokia.com>
To: ext Alain Durand <Alain.Durand@Sun.COM>
In-Reply-To: <E937BBD2-398C-11D9-B9DD-00039376A6AA@sun.com>
References: <C26BB8276599A44B85D52F9CE41035E1050B986B@esealnt944.al.sw.ericsson.se> <E937BBD2-398C-11D9-B9DD-00039376A6AA@sun.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1100803086.4434.55.camel@essrv103nok15564.ntc.nokia.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6
Date: Thu, 18 Nov 2004 20:38:07 +0200
X-OriginalArrivalTime: 18 Nov 2004 18:38:06.0813 (UTC) FILETIME=[BED0C8D0:01C4CD9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: v6tc@ietf.org
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit

Hi,

I agree with Alain. Let's not use normative text and have "goals"
instead of requirements. The documents should be guiding of nature - not
stating hard requirements.

Cheers,

Jonne.

On Thu, 2004-11-18 at 20:08, ext Alain Durand wrote:
> On Nov 18, 2004, at 12:44 AM, Karen E. Nielsen (AH/LMD) wrote:
> > Another issue. I have some problems with SHOULD and MAY requirements.
> > I would much rather stick with must-only requirements, perhaps with 
> > the addition
> > that a certain feature (requirement) possibly could be profited from 
> > in this and that
> > deployment scenario. I do not see the point in having SHOULD 
> > requirements and in general
> > I do not see the point in using the words MUST, SHOULD and MAY in a 
> > requirement document.
> 
> Karen,
> 
> I remember Brian Carpenter strongly advising us to use the term goal 
> instead
> of requirements and remove the uppercase normative language.
> 
> I makes sense to focus on what is really needed. However, if there are 
> "really nice to have" things,
> it might make sense to mention them as such.
> 
> 	- Alain.
> 
> 
> _______________________________________________
> v6tc mailing list
> v6tc@ietf.org
> https://www1.ietf.org/mailman/listinfo/v6tc
-- 
Jonne Soininen
Nokia

Tel: +358 40 527 46 34
E-mail: jonne.soininen@nokia.com

_______________________________________________
v6tc mailing list
v6tc@ietf.org
https://www1.ietf.org/mailman/listinfo/v6tc