1. Is this intended as read-only?
The intro suggests that it is for controlling as well. (1.1 Scope). I dont
see how this can work.
2. Doesnt the generic 'attributes' section merely punt the standardization
issue?
SNMP already has methods for passing general attributes around (its called
OIDs and MIBS). We are now inventing another method. The whole purpose of a
MIB is to define the attribute set.
What this really shows is that MIBs are too chunky and cannot be extended
easily enough - so the group has ending up defining a way of adding 'TBD'
3. Why have standard names for punching styles?
Why not just explicitly state the hole sizes, shapes and placement? Are
these 'well-known' values - where is Latvian9punch and Morrocan21Hole? :-)
4. I like the way that it slides gracefully into the printer MIB model.
(section 3)
99. (personal peeve) The word 'insure' is used where you mean 'ensure'.