Tom, thanks for getting the v0.82 draft out. Here are my comments on the PDF
version.
1. deviceAlertCode (6) needs pointer to SNMP alert table - See pg. 36.
When the device is a printer, the alert code SHALL be the printer alert code.
This is the current definition. But, this is not very effective when
genericAlertCodes are used. An index into the
alert table would provide more information (rather than just JAM, you'd know
jam in Input 3, for
example). Maybe this is too much info for job monitoring? But it's just as
easy for the agent.
2. deviceAlertCode (6) is may be multivalued - See pg. 36.
More than one alert may be in effect. Do we need to clarify that this attribute
can be multi row?
3. What happened to serverAssignedJobNumber (2x) - See pg. 37
We used to have serverAssignedJobNumber, with syntax integer. I think we
combined
this with serverAssignedJobName (22) and dropped it, but in so doing, it is not
listed as
Octets (only). What about the original concern that (OS/2 and perhaps other)
some os's
use an integer not a text string. Are we saying the integer must be converted
to text?
4. Persistence of serverAssignedJobName - See pgs. 36, 37
Two other attributes (jobOwner and jobName) mandate "long" persistence. If you
read the
note under serverAssignedJobName, it leads in with the same reasoning, but
stops short of
requiring "long" persistence. Which persistence value is serverAssignedJobName
intended
to follow?
(Aside... this leads to another whole question about persistence of tables vs.
persistence
of specific attributes or objects and whether or not the 3 objects above should
just be added
to the job state table. Separate topic but probably needs further discussion).
5. jobProcessAfterDateAndTime (51) - Octets vs Integer - See pg. 40-41
Shouldn't this be Octets, not Integer?
6. Eliminate "timeSince" Attributes - See pg. 47
This is too much work for the agent and is contrary to SNMP in that sysUpTime
should do
the trick. I don't mind using a JmTimeStampTC rather than sysUpTime so much,
but the
NMS, not the agent, should calculate the times since. I believe time can be
synchronized
by allowing jobSubmissionToDeviceTime to be multivalued - one DateAndTime
passed
in on submission and one jmTimeStampTC stamped by the printer.
7. IMPLIED/IMPLICIT - See pg. 61
The note reads "an IMPLICIT statement is NOT provided in the following INDEX
clause, since it
was not an SMIv2 feature. Therefore, the extra ASN.1 tag SHALL be included in
the varbind
in the SNMP request and the response."
First, we think the terminology is IMPLIED, not IMPLICIT. Also, we think the
IMPLIED statement
SHOULD (SHALL?;-) be included because it saves a byte on each varbind. If you
left this
out because it is not part of v1 (as stated) I think there are other examples
(like DateAndTime)
where you are using v2 constructs.
8. "Requested Attribute" defaults
For requested attributes like copies, toner, quality etc. what if the requested
value is not passed
in? Should the agent use the device default?
9. Misc editorial
We noticed, in the text version, jobHoldUnitl is in the TOC twice.
In the text and PDF versions jobHold is missing.
>>> Harry Lewis <<<