[Isms] DISCUSS and COMMENT: draft-ietf-isms-transport-security-model

[Adrian Farrel <[e-mail]>]

Discuss:
I am not a MIB expert, but when I see counters I wonder about wraps
and discontinuities. These seem not to be covered in this document
and I would like to hear from a MIB expert that this is OK.

Comment:
Section 1.2
Helpful if s/STD62/STD62 [RFC3411]/

Section 1.5
You seem to fluctuate in your usage of RFC 2119 language.
In bullet 3, I suggest s/may not/might not/

Section 2.3.1
Notwithstanding the requirement to read the reference material, please
expand ASI on first use.

Section 3.1.2
"REQUIRES" is not in the RFC 2119 lexicon.

Section 3.1.3
"and other MIB modules" is a bit vague.

Section 3.1.3
   IANA maintains a registry for transport domains and the corresponding
   prefix.
Would be helpful to include a pointer (perhaps by registry name, or by
defining RFC) to this registry. 

Section 7
Useful if FROM clauses can give a comment that shows the RFC that 
defines the module from which the import is taken.
For example
FROM SNMPv2-SMI  -- RFC 2578