1. draft-ietf-eman-energy-aware-mib-01 Energy-Aware Networks and Devices MIB draft-ietf-eman-energy-aware-mib-01 Benoit Claise, John Parello

2. draft-ietf-eman-energy-aware-mib-01 Addresses Charter Item #3 “Energy-aware Networks and Devices MIB document The EMAN WG will develop a MIB module for monitoring energy-aware networks and devices. The module will address devices identification, context information, and potential relationship between reporting devices, remote devices, and monitoring probes.”

3. draft-ietf-eman-energy-aware-mib-01 UML of Items Addresses: Identification, Context, Relationship from Charter New Items: Clarification of Child Specific Attributes Added more identifiers

4. draft-ietf-eman-energy-aware-mib-01 Changes in the Draft Added identification objects and reference links which –clear up references to other mibs –Add alternate keys for NMS linking –Identify persistent objects Enumerated data specific to parent or child Renamed capabilities to ProxyAbilities for clarity and to be inline with the framework

5. draft-ietf-eman-energy-aware-mib-01 Open Issues Identified in Draft 1.Length and format of PowerMonitorId. The pmPowerMonitorID should be a unique id that identifies the pmMonitor in Universe. Since you can have multiple pmMonitors per device (i.e. interface) this can’t be just a UUID using RFC 4122 Should a certificate scheme like x.509 be used for uniqueness but is that undue expense? Should use encodingg scheme like UUID:offset within the same device? Feedback: Possibly use entPhysicalUris 2. Do we want separate tables, as depicted in figure 1, as opposed to a single pmTable? Proposed: Keep it as is. 3. Should the pmMgmtMacAddress, pmMgmtAddress,pmMgmtAddressType, and pmMgmtDNSName also be implemented for Power Monitor Parent? Feedback: can be deduced via entity mib if implemented

6. draft-ietf-eman-energy-aware-mib-01 Next Items To DO Include Feedback from Printer WG’s MIB Include Feedback from ODVA Energy Aware SIF