Re: [Nea] IETF67 NEA WG Meeting summary

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

> > disagree.  one possible output of a requirements discussion is
> > that there is no way to meet the requirements - that the solution
> > space for the requirements is the null set.
>
> Well, from a pedantic perspective this is certainly true.
>
> However, this is the IETF.  "E" is for "Engineering".  Engineering is
> about producing useful solutions to problems.  It is clear to me that
> NEA is addressing a valid problem. 

"the problem" is valid.  whether NEA is a valid solution is a different 
question.

of course, the NEA WG isn't chartered to solve "the problem", it's 
chartered to develop requirements for one possible kind of solution to 
"the problem".

(IIRC, the first step in the engineering process is stating the problem. 
so maybe we should start there before even discussing requirements?)

> I think that attempting to "rig" the requirements so as to admit no feasible solution is effectively an
> attempt to subvert the WG chartering decision, and to be obstructive.

I'd agree, if anyone were doing that.

Keith


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