Hi,
I've just posted a Stable draft of the PWG Power Management Model, ready
for WIMS WG last call:
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower10-20100926.pdf / doc
- clean copy with line numbers
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower10-20100926-rev.pdf / doc
- redlines with line numbers
This draft addresses all the comments from the WIMS WG review last week.
This document is technically aligned with PWG Imaging System Power MIB.
Comments?
Cheers,
- Ira
-----------------------
***Changes made to create 26 September 2010 version (Stable Draft)*
Editorial – Kept document status at Stable
Editorial – Revised section 1.4 to change “RECOMMENDED” to “recommended”,
per WIMS WG review
Editorial – Revised section 3.3 Design Requirements to put “should” in the
first
sentence and to add a requirement for future extensibility to add automatic
device-written policies (explaining that this use case was deemed too
complex for
this first version), per WIMS WG review
Technical – Revised section 5.1.2 MaxLogRecords to change default to 20 (but
keep
minimum at 10), to accommodate logging for Subunits (e.g., Scanner and
Marker),
per MPSA feedback
Technical – Revised section 5.3.2 PowerState (in Power Log group) to reduce
MUST
to SHOULD for successive entries for the same component with different
states (i.e., a
power transition) and added a warning to implementers about the problem of
lost
functionality due to system heartbeat events filling up the Power Log, per
WIMS WG
review
Technical – Revised sections 5.7 (power state notifications) and sections
8.1 and 8.2
(conformance) to explicitly add a SHOULD for the PWG Imaging System Power
MIB,
for completeness
Technical – Revised section 7.2.3 StartPowerState (in Power Timeout group)
to add
“stable” qualifier, per WIMS WG review
Technical – Revised sections 8.1 and 8.2 (conformance) to add “if these
components
are present” for Scanner and Marker recommendations, per WIMG WG review
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/wims/attachments/20100926/dd021849/attachment-0001.html>