Ben,
...
My point is that a squishy discussion of what a log client might do isn't
appropriate for a standard. If one cannot be precise in describing how each
element of a system is supposed to work, then readers have no confidence
that
there is a consistent, comprehensive system design. Different readers can
come away with different notions of how the system works, which leads to
confusion.
We do describe in considerable detail how each type of client works in
that section - but we cannot document every possible use of the APIs
the I-D defines. Hence we point out that there are other things you
might choose to do, as a user of the API. If you'd prefer a different
way to make that point, happy to consider it.
I don't think it is necessary to define how every client might use these
APIs. I think that a good spec for each CT element would describe what
functions the client MUST/SHOULD perform, and how to use the APIs to
achieve those functions. Examples are good, but they are never a substitute
for well-written specs.
Steve
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
