IETF Logo Mail Archive

Re: [v6tc] v6tc - is there life

Alain Durand <Alain.Durand@Sun.COM> Thu, 18 November 2004 18:28 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 NAA19236; Thu, 18 Nov 2004 13:28:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUr3Y-0008H4-Cs; Thu, 18 Nov 2004 13:30:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqst-0002mE-9b; Thu, 18 Nov 2004 13:19:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqiV-0008EO-IL for v6tc@megatron.ietf.org; Thu, 18 Nov 2004 13:09:11 -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 NAA17798 for <v6tc@ietf.org>; Thu, 18 Nov 2004 13:09:08 -0500 (EST)
Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqkz-0007pV-T8 for v6tc@ietf.org; Thu, 18 Nov 2004 13:11:57 -0500
Received: from esunmail ([129.147.156.34]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id iAII8xun027727 for <v6tc@ietf.org>; Thu, 18 Nov 2004 11:08:59 -0700 (MST)
Received: from xpa-fe2 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0I7D00ELBZQYJN@edgemail1.Central.Sun.COM> for v6tc@ietf.org; Thu, 18 Nov 2004 11:08:59 -0700 (MST)
Received: from [192.168.1.2] ([66.93.39.75]) by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTPSA id <0I7D00AJHZQXJR@mail.sun.net> for v6tc@ietf.org; Thu, 18 Nov 2004 11:08:58 -0700 (MST)
Date: Thu, 18 Nov 2004 10:08:55 -0800
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: [v6tc] v6tc - is there life
In-reply-to: <C26BB8276599A44B85D52F9CE41035E1050B986B@esealnt944.al.sw.ericsson.se>
To: "Karen E. Nielsen (AH/LMD)" <karen.e.nielsen@ericsson.com>
Message-id: <E937BBD2-398C-11D9-B9DD-00039376A6AA@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
References: <C26BB8276599A44B85D52F9CE41035E1050B986B@esealnt944.al.sw.ericsson.se>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7BIT

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

v2.8.7 | Report a Bug | By Email