[WIMS] REVISED: PWG Power Management Model (22 April 2010)

[Ira McDonald]

Hi,

WRONG change log in previous copy


[For review next Monday 26 April during WIMS WG teleconference]

I've just posted another Prototype draft of the PWG Power Management Model:

 ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower10-20100422.pdf / doc
 - clean copy with line numbers

 ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower10-20100422-rev.pdf / doc
 - redlines with line numbers

This draft addresses all the open issues from the April PWG F2F.

This draft is technically aligned with the Power MIB.

Comments?

Cheers,
- Ira
--------------------------
Changes made to create 22 April 2010 version (Prototype Draft)

Editorial – Kept document status as Prototype

Editorial – Global – Replaced “flea power” with “limited auxiliary power,
e.g., console lights”, per Bill Wagner

Editorial – Renamed section 2.4.2 to DMTF CIM Stable Power States,
per Bill Wagner

Technical – Added section 2.4.3 DMTF CIM Transitional Power States,
per Bill Wagner

Technical – Added section 2.4.4 DMTF CIM Out-of-band Power States,
per Bill Wagner

Technical – Revised section 2.5.1 and section 8.1 (conformance) to clarify
that the specified relationships between operational state and power state
are RECOMMENDED best practice, per Bill Wagner

Technical – Revised section 4.6 and section 8.1 (conformance) to clarify that,
if implemented, the icKeyTable, icServiceTable, and icSubunitTable in the
already RECOMMENDED PWG ISC MIB MUST be persistent across reboots
(which is important for correlating operational states with power states), per
Bill Wagner

Technical – Revised sections 5.2.1 and 5.3.2 (PowerState) to clarify that
intermediate power states (e.g., OffSoft before On during a ResetSoft power
operation) SHOULD NOT be reported, for consistency, per Bill Wagner

Technical – Revised section 9.1 to change “MUST” to “will” for PWG SM/2.0
mappings, per WIMS WG

Technical – Renamed “OffGraceful” to “OffSoftGraceful” and “Reset” to
“ResetSoft” and “ResetGraceful” to “ResetSoftGraceful” in Table 2 in
section 9.1,
for clarity and consistency

Technical – Revised some ACPI state transitions in Table 2 in section 9.1, for
clarity and consistency

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.