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

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

> I agree with this as well, and I am sure other "design team" members
> also agree. Infact, we have already had lots of discussions on the
> mailing lists on the requirements and that's driving a lot of what we
> are putting in the draft. Also I don't believe the intent of a small
> design team was to exclude mailing lists discussions & participation.
>
> I look towards the chairs for advice on the specifics of this
> process...my personal thoughts would be sharing weekly design team
> meeting summary, send out an early rev of the draft for feedback, etc.

my belief is that the "design team" should not be drafting any 
requirements text in advance of list discussion.  instead, they should 
try to write up goals and requirements based on the discussion on the 
list, with an eye to what kind of language might reach consensus.

something else they might try to do is to come up with topics for 
discussion - e.g. name some categories for requirements that should be 
discussed, or mention tradeoffs and ask the list what's an appropriate 
compromise for each.

Keith

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