Tom,
I would still very much apprecaite a statement of why you (and I
don't see any one else) insist that the enums must be specified as
being mandatory or conditionally mandatory. At this point I am not
even being argumentative. But I see no more reason to make these
values mandatory than to make certain emulations mandatory, or
certain paper handling mandatory, or any number of other enums in the
printer MIB mandatory. All it has done is produce vast discussion of
what state should be at what compliance level, and concepts of the
agent fabricating states that are inperceptable by the equipment or
by a user. Please Tom, what is the reason for assigning compliance
levels to the state values?
Bill Wagner, Osicom/DPI
So conformance requirements in a MIB specification are ONLY on the agent as
measured through SNMP operations by a management application.
For the completed state, its the agent, not the device that will usually
retain the data for the row for each completed job. But if 'completed'
were only conditionally mandatory, then the agent doesn't have to add
anything extra to what the device already has. So if the device doesn't keep
job information after the job finishes processing, the agent wouldn't
have to either, IF the 'completed' state were conditionally mandatory.
So lets be clear that conformance requirements are for the agent, not
the device (printer or server).