Is this something we should do here or in IOTOPS?I think it would be cool to develop at least something of a requirements doc. And there are some tools out there, even at the EAP level. But They don't all fit together well.
Eliot On 05.07.21 16:20, Carolin Baumgartner wrote:
On 7/3/21 1:57 PM, Alan DeKok wrote:I agree and out of experience everything that leaves just a little bit room of interpretation ("you can do it this way or that way") ends up in misinterpretions or gaps and causes good ideas to fail.On Jul 3, 2021, at 7:47 AM, Eliot Lear <l...@lear.ch> wrote:I don't think Tim could be blamed for holding the view that there is a separation between specifications and how they are used. There's good and bad to the practice. The good is that the spec can be used in ways that the creators didn't intend, and thus perahsp there are fewer unnecessary constraints.People don't even understand how to use the specs as intended. We're essentially telling people "EAP methods are applicable in these situations, but good luck actually trying to get them deployed, you're on your own".On the other hand, not having a theory of operation section, as we do have in a good number of our specs, leads to people really not understanding when they are applicable, and perhaps more importantly, when they are not._______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
