Telechat Review of draft-ietf-nmop-terminology-19
review-ietf-nmop-terminology-19-artart-telechat-bray-2025-06-30-00

Once again, gripes from this non-networking specialist may be irrelevant if the
language would be clear touch a specialist.

I do have one problem with this document, the lack of examples. I mentioned
this before and Adrian's reply was "I am usually a fan of examples, but in this
case I'm cautious. The risk is that the examples are taken to be limiting."  I
take his point but still disagree. Yes, it's hard to come up with quality
examples, but I believe the work is worthwhile. First, there is risk that
difficulty in offering examples might be a symptom of insufficient specificity
in the normative text. Second, and speaking for myself, I know that when I'm
having trouble understanding technical text the first thing I do is go looking
for examples.

3.1 "The terms may be viewed as a cascaded sequence of processes” - Hmm, terms
aren’t usually processes?

3.1 "Network monitoring - This is the process of keeping a continuous record of
functions related to a network topology.”  This sentence is hard to parse. Do
you mean something like “the functioning (or behavior?) of a running network”.
"Topology" doesn't seem quite the right word.

3.2 “Event”. Can an Event be anything other than the observation of a change? 
Troubled by the notion of anything that changes in a “negligible” delta-t.
Examples would help here.

I really don’t understand the difference between Condition and State, and
memory shortage being included in both definitions isn’t helping.

Occurrence, typo, missing verb: “That is, Occurrences, themselves a recursive
concept”