Re: [v6tc] v6tc - is there life

["Soininen Jonne (Nokia-NET/Helsinki)" <[e-mail]>]

Hello,

in the interest of time, I would propose that a *simple* goals document
is written that comprises the requirements from all three requirements
documents. This is then used as a guideline when designing the protocol.
Also I'm a bit afraid if we start elaborated requirements/analysis/gap
analysis/etc. this project will take number of years or we don't even wg
started as we cannot show that we really need this new protocol.

Basically, I propose that we combine the current requirements to a
single document that the authors of the current document do together -
in fairly short time. Parallel to that people would submit their
protocol proposals as Internet-Drafts.

Then we just do a quick analysis on the mailing list of the protocols
vs. the requirements and choose the one that seems to be the best fit as
a *baseline* document.

After that it's just work, which is of course easy... ;)

Cheers,

Jonne.
 
On Tue, 2004-11-16 at 22:33, ext 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?
-- 
Jonne Soininen
Nokia

Tel: [phone]
E-mail: [e-mail]

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