[Nea] Re: use of a design team to develop requirements

[Keith Moore <moore at cs.utk.edu>]

-------- Original Message --------

> > > > > > "Keith" == Keith Moore <moore at cs.utk.edu> writes:
>
>     Keith> Stephen & Susan, I really have to question the use of a
>     Keith> design team to develop requirements for the NEA WG.  A lot
>     Keith> of the strength of the IETF process has traditionally been
>     Keith> from its inclusiveness.  Experience suggests that this is
>     Keith> most beneficial in two areas - one is determining
>     Keith> requirements and design considerations (the more people who
>     Keith> have input into these, the more chances there are to spot
>     Keith> important considerations that might otherwise have been
>     Keith> overlooked) and another is in reviewing documents (the more
>     Keith> reviewers, the greater the chance that a flaw in the
>     Keith> document is discovered).
>
> Keith, speaking only to the correctness of process: it is absolutely
> clear to me that a WG can choose to use a design team to solve any
> problem before them. 

strictly speaking, it may be allowed by our process, though I think of 
this as an omission or ambiguity in our process documents.  I don't 
think our process was intended to allow handpicked design teams to 
develop requirements.

I also think that is is contrary to good engineering practice and common 
sense to try to define requirements of a solution before the problem 
itself is well understood.  the chairs and the design team may believe 
that they understand the problem well, but they haven't bothered to get 
much input from the larger group before starting to draft requirements.

Keith


_______________________________________________
Nea mailing list
Nea at ietf.org
https://www1.ietf.org/mailman/listinfo/nea