Hi,
I've just posted a Stable draft of the PWG Imaging System Power MIB:
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspowermib10-20100922.mib
- full ASN.1 source with compliance statements, defaults, references, etc.
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspowermib10-20100922.pdf / doc
- full MS Word document with all sections completed
This draft addresses all the comments from the Samsung prototypes and the
August PWG F2F.
This document is technically aligned with PWG Power Management Model.
Cheers,
- Ira
-------------------
***Changes made to create 22 September 2010 version (Stable Draft)*
Editorial – Changed document status to Stable, per August PWG F2F
Technical – Added new section 1.4 Power State Transition Notifications to
specify the RECOMMENDED support for new powPowerV2Trap defined in
the Power MIB, per August PWG F2F
Technical – Revised powGeneralNaturalLanguage to change to “read-only”,
per August PWG F2F
Technical – Added powGeneralMaxCounterRecords, powGeneralMaxMeterRecords
(oversights in previous draft), per August PWG F2F
Technical – Added powGeneralCanRequestPowerStates (comma-delimited
list of all supported stable and transitional power states), per August PWG
F2F
Technical – Revised powMonitorPowerState and powLogPowerState to clarify
that “on” and “offSoft” MUST be supported and “standby”, “suspend”, and
“hibernate”
SHOULD be supported, per August PWG F2F
Technical – Revised powMonitorPowerState and powLogPowerState to clarify
that standard states (e.g., “standby”) MUST be supported whenever vendor
extensions (e.g., “standbyVendor1”) are supported, per August PWG F2F
Technical – Revised powMonitorComponentType and powLogComponentType to
clarify that “system” MUST be supported and “scanner” and “marker”
(subunits)
SHOULD be supported, if the components are present, per August PWG F2F
Technical – Revised powLogPowerState to clarify that only state transitions
for the
same component are allowed, per August PWG F2F
Technical – Added powSupportPowerPeakWatts (distinct from
powSupportPowerActiveWatts), per August PWG F2F
Technical – Revised powSupportTable, powSupportPowerState,
powTransitionTable,
powTransitionStartPowerState, and powTransitionEndPowerState to clarify that
values MUST only be stable power states, per August PWG F2F
Technical – Revised powEventName to correct MAX-ACCESS to “read-create”, per
compiler error
Technical – Revised MODULE-COMPLIANCE macro to add GROUP macros for
powCounterTable and powMeterTable objects (oversights in previous draft),
per
August PWG F2F
Technical – Revised MODULE-COMPLIANCE macro to add OBJECT macros with
MIN-ACCESS or “read-only” for all powTimeoutTable, powCalendarTable, and
powEventTable columnar objects and OBJECT macros with SYNTAX restrictions
for
other objects as needed, per August PWG F2F
Technical – Added new powPowerV2Trap and powPowerTrapGroup to support
notifications when IETF Printer MIB v2 is not present (e.g., a stand-alone
Scanner or
Fax device), per August PWG F2F
--
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/20100922/c5757eac/attachment-0001.html>