Yes, that sounds OK.
-----Original Message-----
From: owner-ipp at pwg.org [mailto:owner-ipp at pwg.org]On Behalf Of Hastings,
Tom N
Sent: 11 May 1999 06:13
To: anthony.porter at computer.org
Cc: 'ipp'
Subject: RE: IPP> MOD - REVISITED Issue 17 - Client display of absolute
date and time for job attributes
Our intent was not to invalidate implementations. Also it seems that we
need to clarify the difference between the Printer object software and the
device(s).
So we propose the following clarification to allow your Printer object
implementation (in the PC) to continue without having to reset the time.
However, for those implementations where the MIB-II sysUpTime is reset on
power up or the Printer MIB, such implementation MAY want to reset the
"printer-up-time" attribute.
So how does this sound:
If the Printer object software ceases running, and restarts without knowing
the last value for "printer-up-time", the implementation MUST reset this
value to 1. However, if the device or devices that the Printer object is
representing are restarted or power cycled, the Printer object MAY continue
counting this value or MAY reset this value to 1 depending on
implementation. If this value is reset and the implementation has
persistent jobs and the Event Time Job Description Attributes are
represented using the 'integer' form (instead of the 'dateTime' form), they
MUST be reset according to Section 4.3.12.