RE: [v6tc] v6tc - is there life

["Karen E. Nielsen (AH/LMD)" <[e-mail]>]

I think that it is important to have scenario specific sections where the
finer points of the various requirements vis-à-vis the individual deployment scenario,
can be addressed in a coherent manner -
otherwise I am afraid that we loose the big picture, deployment wise.

We could under each requirement in the general requirements section
list the applicability of the requirement in the various scenarios -
like "applicable for Scenario x, Section ?.?, Scenario y etc."

As such I generally agree with the outline proposed by Pekka.

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.

BR, Karen

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]On Behalf Of
> Kurt Erik Lindqvist
> Sent: Wednesday, November 17, 2004 11:28 AM
> To: Pekka Savola
> Cc: [e-mail]
> Subject: Re: [v6tc] v6tc - is there life
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> On 2004-11-16, at 21.33, Pekka Savola wrote:
> 
> > 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?
> >
> 
> I like Tim's approach above. I think that would give a easy 
> to read and 
> clear document.
> 
> - - kurtis -
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.1
> 
> iQA/AwUBQZsnqKarNKXTPFCVEQLfHACglcgohp1XjqLaOUu3g9k6zwjPFCsAn1gs
> AGNzz7gknfsuz4Rzz/ffsLEK
> =8u0f
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> v6tc mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/v6tc
> 

_______________________________________________
v6tc mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/v6tc