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

[Sam Hartman <hartmans-ietf at mit.edu>]

>>>>> "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.  However, for sponsored design teams, it's also
clear to me that decision is subject to WG consensus like all other WG
decisinos.  Discussing the formation of the team at the meeting and
then on the list seems to meet the requirement of confirming WG
consensus for that decision.

Obviously, ad-hoc design teams formed by participants and not given
support by the chair can be formed for any problem without the
approval of the WG.  That too is a critical part of the IETF process.



Again, I'm speaking to process issues, not to whether it is right to
form a design team in this case.  Also, as you well know, this is
Russ's group not mine; my opinion here holds no more weight than your
own.


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