Hi,
I've just posted a Prototype draft of the PWG Power Management Model:
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower10-20091022.pdf / doc
- clean copy
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower10-20091022-rev.pdf / doc
- redlines
Based on this draft, Pete will be updating the XML Schema for PWG SM/2.0
and I will be writing the Initial draft of the PWG Power Management MIB.
Comments?
Cheers,
- Ira
--------------------------------------------------------------------------------------
Changes made to create 22 October 2009 version (Prototype Draft)
Editorial – Changed document status to Prototype, per October PWG F2F
Technical – Global – Added Default Value clauses to all elements (except
key elements), per Nancy Chen at October PWG F2F
Technical – Added ISSUE for power state change notifications to Section 3.3
Design Requirements
Technical – Renamed Section 4 from PWG Semantic Model Extensions to
Relationship to PWG Semantic Model and changed all uppercase imperatives
(MUST, etc.) to lowercase (will, etc.), per October PWG F2F
Technical – Added new Section 5.1 Power General group (with Max…Records)
and Section 5.4.1 Examples of Power General Group, per Pete Zehler at October
PWG F2F
Technical – Deleted MonitorID (redundant) from Power Monitor group, per October
PWG F2F
Technical – Added CanUseInterfaces (comma-delimited list of InterfaceID/ifIndex
values) to Power Support group, per Jerry Thrasher at October PWG F2F
Technical – Deleted RequestID (redundant) from Power Request group, per
October PWG F2F
Editorial – Renamed CalendarIsOnetime to CalendarRunOnce, for clarity
Technical – Added new paragraph to Section 11 Security Considerations, stating
that systems that support secure and privileged (Operator or
Administrator ONLY)
admin operations MUST implement any supported power state/policy change
operations as secure and privileged, per October PWG F2F
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.