IETF Logo Mail Archive

Re: [v6tc] v6tc - is there life

Pekka Savola <pekkas@netcore.fi> Tue, 16 November 2004 20:38 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 PAA10512; Tue, 16 Nov 2004 15:38:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUA7z-0007PF-0s; Tue, 16 Nov 2004 15:40:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUA53-0000S3-AQ; Tue, 16 Nov 2004 15:37:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUA1d-0007Do-Is for v6tc@megatron.ietf.org; Tue, 16 Nov 2004 15:34:05 -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 PAA10054 for <v6tc@ietf.org>; Tue, 16 Nov 2004 15:34:04 -0500 (EST)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUA3r-0007Jg-2N for v6tc@ietf.org; Tue, 16 Nov 2004 15:36:26 -0500
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id iAGKXJ123809; Tue, 16 Nov 2004 22:33:21 +0200
Date: Tue, 16 Nov 2004 22:33:19 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [v6tc] v6tc - is there life
In-Reply-To: <20041116192132.GN4961@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.61.0411162232140.23785@netcore.fi>
References: <1100605147.10092.23.camel@essrv103nok15564.ntc.nokia.com> <5DFA372B-37FC-11D9-96B1-00039376A6AA@sun.com> <20041116192132.GN4961@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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: 2409bba43e9c8d580670fda8b695204a

On Tue, 16 Nov 2004, Tim Chown wrote:
> I think the single doc should be split into
>
> Intro
> Assumptions
> Requirements (all)
> Scenarios (including 3gpp)
>
> with the Scenarios stating which requirements are applicable, and whether
> the requirements are may/should/must.
>
> We shouldn't repeat the "confusion" of scattering requirements in the
> scenarios text.

What would you feel about putting the scenario-specific justifications 
inside the requirements, so that the requirements would be better 
grounded in the reality?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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

v2.8.7 | Report a Bug | By Email