idnits 2.17.1 draft-tychon-eman-applicability-statement-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 15, 2011) is 4576 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'DASH' is defined on line 1241, but no explicit reference was found in the text == Unused Reference: 'ENERGY' is defined on line 1249, but no explicit reference was found in the text == Unused Reference: 'SGRID' is defined on line 1285, but no explicit reference was found in the text == Unused Reference: 'ASHRAE' is defined on line 1289, but no explicit reference was found in the text == Unused Reference: 'PAP17' is defined on line 1292, but no explicit reference was found in the text == Unused Reference: 'IEC62301' is defined on line 1318, but no explicit reference was found in the text == Outdated reference: A later version (-05) exists of draft-tychon-eman-applicability-statement-04 == Outdated reference: A later version (-14) exists of draft-ietf-eman-requirements-04 -- No information found for draft-ietf-eman-monitoring-mib - is the name correct? == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-02 == Outdated reference: A later version (-20) exists of draft-ietf-eman-battery-mib-02 Summary: 0 errors (**), 0 flaws (~~), 13 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Energy Management Working Group E. Tychon 3 Internet Draft Cisco Systems Inc. 4 Intended status: Informational B. Schoening 5 Expires: April 14, 2012 Independent Consultant 6 Mouli Chandramouli 7 Cisco Systems Inc. 8 Bruce Nordman 9 Lawrence Berkeley National Laboratory 10 October 15, 2011 12 Energy Management (EMAN) Applicability Statement 13 draft-tychon-eman-applicability-statement-04 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance 18 with the provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet 21 Engineering Task Force (IETF), its areas, and its working 22 groups. Note that other groups may also distribute working 23 documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as "work 29 in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html 37 This Internet-Draft will expire on April 14, 2012. 39 Copyright Notice 41 Copyright (c) 2011 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with 49 respect to this document. Code Components extracted from this 50 document must include Simplified BSD License text as described 51 in Section 4.e of the Trust Legal Provisions and are provided 52 without warranty as described in the Simplified BSD License. 54 Abstract 56 The objective of Energy Management (EMAN) is to provide an 57 energy management framework for networked devices. This document 58 presents the applicability of the EMAN framework for a variety 59 of scenarios. This document lists use cases and target devices 60 that can potentially implement the EMAN framework and associated 61 SNMP MIB modules. These use cases are useful for identifying 62 monitoring requirements that need to be considered. Further, we 63 describe the relationship of the EMAN framework to relevant 64 other energy monitoring standards and architectures. 66 Table of Contents 68 1. Introduction .............................................3 69 1.1. Energy Management Overview ............................4 70 1.2. Energy Measurement ....................................5 71 1.3. Energy Management .....................................5 72 1.4. EMAN Framework Application ............................6 73 1.5. EMAN WG Document Overview .............................6 74 2. Scenarios and Target Devices ..............................7 75 2.1. Network Infrastructure Devices ........................7 76 2.2. Devices Powered and Connected to a Network Device .....8 77 2.3. Devices Connected to a Network ........................9 78 2.4. Power Meters ..........................................9 79 2.5. Mid-level Managers ...................................10 80 2.6. Gateways to Building Systems .........................11 81 2.7. Home Energy Gateways .................................12 82 2.8. Data Center Devices ..................................13 83 2.9. Energy Storage Devices ...............................14 84 2.10. Ganged Outlets on a PDU Multiple Power Sources.......15 85 2.11. Industrial Automation Networks ......................15 86 2.12. Printers ............................................16 87 2.13. Off Grid Devices ....................................17 88 2.14. Demand/Response .....................................18 89 3. Use Case Patterns ........................................18 90 3.1. Metering .............................................18 91 3.2. Metering and Control .................................18 92 3.3. Power Supply, Metering and Control....................19 93 3.4. Multiple power sources ...............................19 94 4. Relationship of EMAN to other Standards ..................19 95 4.1. Data Model and Reporting .............................19 96 4.1.1. IEC CIM..........................................19 97 4.1.2. DMTF...............................................20 98 4.1.3. ODVA...............................................21 99 4.1.4. Ecma SDC...........................................22 100 4.1.5. Printers: IEEE-ISTO Printer Working Group (PWG) ...22 101 4.1.6. ASHRAE FACILITY SMART GRID INFORMATION MODEL.......23 102 4.1.7. ZigBee.............................................23 103 4.2. Measurement ..........................................24 104 4.2.1. ANSI C12...........................................24 105 4.2.2. IEC62301...........................................24 106 4.3. Other ................................................25 107 4.3.1. ISO................................................25 108 4.3.2. Energy Star........................................25 109 4.3.3. Smart Grid.........................................26 110 5. Limitations ..............................................27 111 6. Security Considerations ..................................27 112 7. IANA Considerations ......................................27 113 8. Acknowledgements .........................................27 114 9. Open Issues ..............................................27 115 10. References ..............................................28 116 10.1. Normative References ................................28 117 10.2. Informative References ..............................28 119 1. Introduction 121 The focus of the Energy Management (EMAN) framework is energy 122 monitoring and management of devices. The scope of devices 123 considered are network equipment and its components, and 124 EMAN framework enables monitoring i.e.; heterogeneous devices 125 to report their energy consumption, and secondly, if 126 permissible, enables control policies for energy savings. 127 There are multiple scenarios where this is desirable, 128 particularly considering the increased importance of limiting 129 consumption of finite energy resources and reducing 130 operational expenses. 132 The EMAN framework describes how energy information can be 133 retrieved from IP-enabled devices using Simple Network 134 Management Protocol (SNMP), specifically, Management Information 135 Base (MIBs) for SNMP. 137 This document describes typical applications of the EMAN 138 framework, as well as its opportunities and limitations. Other 139 standards that are similar to EMAN but address different domains 140 are described. This document contains references to those other 141 standards and describes how they relate to the EMAN framework. 143 1.1. Energy Management Overview 145 First, a brief introduction to the definitions of Energy and 146 Power are presented. A draft on terminology has been submitted 147 so that to reach a consensus on the definitions of commonly used 148 terms in the EMAN WG. While energy is available in many forms, 149 EMAN addresses only the electrical energy consumed by devices 150 connected to a network. 152 Energy is the capacity to perform work. Electrical energy is 153 typically expressed in kilowatt-hour units (kWh) or other 154 multiples of watt-hours (Wh). One kilowatt-hour is the 155 electrical energy used by a 1 kilowatt device for one hour. 156 Power is the rate of electrical energy flow. In other words, 157 power = energy / time. Power is often measured in watts. 158 Billing is based on electrical energy (measured in kWh) supplied 159 by the utility. 161 Towards the goal of increasing the energy efficiency in networks 162 and buildings, a first step is to enable devices to report their 163 energy usage over time. The EMAN framework addresses this 164 problem with an information model for an energy-using device: 165 identity, context, power measurement and power measurement 166 attributes. 168 The EMAN WG framework defines SNMP MIB modules based on the 169 information model. By implementing the SNMP MIB modules, any IP 170 network device can report its energy consumption according to 171 the information model. In that context, it is important to 172 distinguish devices that can report their own energy usage from 173 devices that can also collect and aggregate energy usage of 174 subtended devices. 176 The list of target devices and scenarios considered for Energy 177 Management are presented in Section 2 with detailed examples. 179 1.2. Energy Measurement 181 More and more devices are able to measure and report their own 182 energy consumption. Smart power strips and some Power over 183 Ethernet switches can meter consumption of connected devices. 184 However, when managed and reported through proprietary means, 185 this information is minimally useful at the enterprise level. 187 The primary goal of the EMAN MIBs is to enable reporting and 188 management within a standard framework that is applicable to a 189 wide variety of end devices, meters, and proxies. This enables 190 a management system to know who's consuming what, when, and how 191 at any time by leveraging existing networks, across various 192 equipment, in a unified and consistent manner. 194 Given that a device can consume energy and/or provide energy to 195 other devices, there are three types of meters for energy 196 measurement: energy input to a device, energy supplied to other 197 devices, and net (resultant) energy consumed (the difference 198 between energy input and provided). 200 1.3. Energy Management 202 Beyond energy monitoring, the EMAN framework provides mechanisms 203 for control. 205 There are many cases where reducing energy consumption of 206 devices is desirable, such as when the device utilization is low 207 or when the electricity is expensive or in short supply. 209 In some cases, control requires considering the context. For 210 instance, in a building: all phones would not usually be turned 211 off to keep some still available in case of emergency; office 212 cooling is usually not turned off totally during non-work hours, 213 but the comfort level is reduced; and so on. 215 Power control requires flexibility and support for different 216 polices and mechanisms: from centralized management with a 217 network management station, to autonomous management by 218 individual devices, and alignment with dynamic demand-response 219 mechanisms. 221 The EMAN framework can be used as a tool for the demand/response 222 scenario where in response to time-of-day fluctuation of energy 223 costs or possible energy shortages, it is possible to respond 224 and reduce the energy consumption for the network devices. 226 1.4. EMAN Framework Application 228 A Network Management System (NMS) is the entity that requests 229 information from compatible devices using SNMP protocol. It may 230 be a system which also implements other network management 231 functions, e.g. security management, identity management and so 232 on), or one that only deals exclusively with energy in which 233 case it is called EMS Energy Management System. It may be 234 limited to monitoring energy use, or it may also implement 235 control functions. In a typical application of the EMAN 236 framework, management software collects energy information for 237 devices in the network. 239 Energy Management can be implemented by extending existing SNMP 240 support to the EMAN specific MIBs. SNMP provides an industry 241 proven and well-known mechanism to discover, secure, measure, 242 and control SNMP-enabled end devices. The EMAN framework 243 provides an information and data model to unify access to a 244 large range of devices. The scope of the target devices and the 245 network scenarios considered for energy management are listed in 246 Section 2. 248 1.5. EMAN WG Document Overview 250 The EMAN working group charter calls for producing a series of 251 Internet standard drafts in the area of energy management. The 252 following drafts are currently under discussion in the working 253 group. 255 Applicability Statement [EMAN-AS] This draft presents the 256 use cases and scenarios for energy monitoring. In addition, 257 other relevant energy standards and architectures are listed. 259 Requirements [EMAN-REQ] This draft presents the requirements 260 of Energy Monitoring and the scope of the devices considered. 262 Framework [EMAN-FRAMEWORK] This draft defines the 263 terminology and explains the different concepts associated 264 with energy monitoring; these are used in the MIB modules. 266 Energy-Aware MIB [EMAN-AWARE-MIB] This draft proposes a MIB 267 module that characterizes a device's identity and context. 269 Monitoring MIB [EMAN-MONITORING-MIB] This draft defines a 270 MIB module for monitoring the power and energy consumption of 271 a device. In addition, the MIB module contains an optional 272 module for power quality metrics. 274 Battery MIB [EMAN-BATTERY-MIB] This draft contains a MIB 275 module for monitoring characteristics of an internal battery. 277 2. Scenarios and Target Devices 279 In this section a selection of scenarios for energy management 280 are presented. The fundamental objective of the use cases is to 281 list important network scenarios that the EMAN framework should 282 solve. These use cases then drive the requirements for the EMAN 283 framework. 285 Each scenario lists target devices for which the energy 286 management framework can be applied, as well as how the 287 reported-on devices are powered, and how the reporting is 288 accomplished. While there may be some overlap between some of 289 the use cases, the use cases serve as illustrative network 290 scenarios EMAN framework should solve. 292 2.1. Network Infrastructure Devices 294 This scenario covers network devices and their components. 295 Power management of network devices is considered as a 296 fundamental requirement of energy management of networks. 298 It can be important to monitor the power state and energy 299 consumption of these devices at a granularity level finer than 300 just the entire device. For these devices, the chassis draws 301 power from one or more sources and feeds all its internal 302 components. It is highly desirable to have monitoring available 303 for individual components, such as line cards, processors, and 304 hard drives as well as peripherals like USB devices. 306 As an illustrative example, consider a switch with the following 307 grouping of sub-entities for which energy monitoring could be 308 useful. 310 . physical view: chassis (or stack), line cards, service 311 modules of the switch 312 . component view: CPU, ASICs, fans, power supply, ports 313 (single port and port groups), storage and memory 314 . logical view: system, data-plane, control-plane, etc. 316 The essential properties of this use case are: 318 . Target devices: Network devices such as routers, switches 319 and their components. 320 . How powered: Typically by a PDU on a rack or from a wall 321 outlet. The components of a device are powered by the 322 device chassis. 323 . Reporting: Direct power measurement can be performed at a 324 device level. Components can report their power 325 consumption directly or the chassis/device that can report 326 on behalf of some components. 328 2.2. Devices Powered and Connected to a Network Device 330 This scenario covers Power over Ethernet (PoE) devices. A PoE 331 Power Sourcing Equipment (PSE) device (e.g. a PoE switch) 332 provides power to a Powered Device (PD) (e.g. a desktop phone). 333 For each port, the PSE can control the power supply (switching 334 it on and off) and monitor actual power provided. PoE devices 335 obtain network connectivity as well as the power supply for the 336 device over a single connection so the PSE can determine which 337 device to allocate each port's power to. 339 PoE ports on a switch are commonly connected to IP phones, 340 wireless access points, and IP cameras. The switch powers 341 itself, as well as supplies power to downstream PoE ports. 342 Monitoring the power consumption of the switch and the power 343 consumption of the PoE end-points is a simple use case of this 344 scenario. 346 The essential properties of this use case are: 348 . Target devices: Power over Ethernet devices such as IP 349 Phones, Wireless Access Points, and IP cameras. 350 . How powered: PoE devices are connected to the switch port 351 which supplies power to those devices. 352 . Reporting: PoE device power consumption is often measured 353 and reported at the switch (PSE) port which supplies power 354 for the PoE device. 356 In this case, the PoE devices do not need to directly support 357 the EMAN framework, only the Power Sourcing Equipment (PSE) 358 does. 360 2.3. Devices Connected to a Network 362 The use case covers devices that receive power from a source but 363 have an independent network connection from another network 364 device. In contrast to the PoE devices, the class of devices 365 have a network connection from a device, but the power supply is 366 from another source. There are several examples. 368 In continuation to the previous example is a switch port that 369 has both a PoE connection powering an IP Phone, and a PC has a 370 daisy-chain connection to the IP Phone for network connectivity. 371 The PC has a network connection from the switch, but draws power 372 from the wall outlet, in contrast to the IP phone draws power 373 from the switch. 375 It is also possible to consider a simple example of PC which has 376 a network connection but draws power from the wall outlet or 377 PDU. 379 The PC in this case, is an non-PoE device, can report power 380 usage by itself, for instance through the EMAN framework. 382 The essential properties of this use case are: 384 . Target devices: A broad set of devices that have a network 385 connection, but receive power supply from the wall outlet. 386 . How powered: These devices receive power supply from the 387 wall outlet or a PDU. 388 . Reporting: There are two models: devices that can measure 389 and report the power consumption directly via the EMAN 390 framework, and those that communicate it to the network 391 device (switch) and the switch can report the device's 392 power consumption via the EMAN framework. 394 2.4. Power Meters 396 This use case covers devices that can measure or report the 397 power consumption of devices externally. Examples are PDUs and 398 smart meters. 400 Some devices are not equipped with instrumentation to measure 401 their own power and accumulated energy consumption. External 402 meters can be used to measure the power consumption of such 403 devices. 405 Three types of external metering are relevant to EMAN: PDUs, 406 standalone meters, and utility meters. External meters can 407 measure these properties for a single device or for a set of 408 devices. 410 Power Distribution Unit (PDUs) in a rack have inbuilt meters for 411 each socket and the PDUs can measure the power supplied to each 412 device in an equipment rack. The PDUs have remote management 413 functionality which can be used to measure and possibly control 414 the power supply of each outlet. 416 Standalone meters can be placed anywhere in a power distribution 417 tree, and can measure the power consumption. 418 Utility meters monitor and report accumulated power consumption 419 of the entire building. There can be sub-meters to measure the 420 power consumption of a portion of the building. 422 The essential properties of this use case are: 424 . Target devices: PDUs and Smart Meters. 426 . How powered: From traditional mains power but as passed 427 through a PDU or meter. 429 . Reporting: The PDUs reports power consumption of downstream 430 devices. There is commonly only one device downstream of each 431 outlet, but there could be many. There can be external meters 432 in between the power supply and device and the meters can 433 report the power consumption of the device. 435 2.5. Mid-level Managers 437 This use case covers aggregation of energy management data at 438 "mid-level managers" that can provide energy management 439 functions for themselves as well as associated devices. 441 A switch can provide energy management functions for all devices 442 connected to its ports, whether or not these devices are powered 443 by the switch or whether the switch provides immediate network 444 connectivity to the devices; such a switch is a mid-level 445 manager, offering aggregation of power consumption data for 446 devices it does not supply power to them. Devices report their 447 EMAN data to the switch and the switch aggregates the data for 448 these data. 450 The essential properties of this use case are summarized as 451 follows: 453 . Target devices: network devices which can perform 454 aggregation; commonly a switch or a proxy 455 . How powered: Mid-level managers can be are commonly 456 powered by a PDU or from a wall outlet but there is no 457 limitation. 458 . Reporting: The middle-manager aggregates the energy data 459 and reports that data to a NMS or higher mid-level manager. 461 2.6. Gateways to Building Systems 463 This use case describes energy management of buildings. 464 Building Management Systems (BMS) have been in place for many 465 years using legacy protocols not based on IP. In these 466 buildings, a gateway can provide an interface between IP and 467 legacy building automation protocols. The gateway can provide 468 an interface between the EMAN framework and relevant building 469 management protocols. 471 Due to the potential energy savings, energy management of 472 buildings has received significant attention. There are gateway 473 network elements to manage the multiple components of a building 474 energy management system such as Heating, Ventilation, and Air 475 Conditioning (HVAC), lighting, electrical, fire and emergency 476 systems, elevators, etc. The gateway device uses legacy building 477 protocols to communicate with those devices, collects their 478 energy usage, and reports the results. 480 The gateway performs protocol conversion between many facility 481 management devices. The gateway communicates via RS-232/RS-485 482 interfaces, Ethernet interfaces, and protocols specific to 483 building management such as BACNET, MODBUS, or Zigbee. 485 The essential properties of this use case are summarized as 486 follows: 488 Due to the potential energy savings, energy management of 489 buildings has received significant attention. There are gateway 490 network elements to manage the multiple components of a building 491 energy management system such as Heating, Ventilation, and Air 492 Conditioning (HVAC), lighting, electrical, fire and other 493 emergency systems, and elevators. The gateway uses legacy 494 building protocols to communicate with those devices, collects 495 their energy data, and reports it via the EMAN framework. 497 The gateway performs protocol conversion for many facility 498 management devices, often communicating via RS-232/RS-485, 499 Ethernet, and protocols specific to building management such as 500 BACNET, MODBUS, and/or Zigbee. 502 The essential properties of this use case are : 504 . Target devices: Building energy management devices - HVAC 505 systems, lighting, electrical, fire and emergency systems. 506 There are meters for each of the sub-systems and the energy 507 data is communicated to the proxy using legacy protocols. 509 . How powered: Any method, including directly from mains 510 power or via a UPS. 511 . Reporting: The gateway collects energy consumption of non- 512 IP systems and communicates the data via the EMAN 513 framework. 515 2.7. Home Energy Gateways 517 This use case describes the scenario of energy management of a 518 home. The home energy gateway is another example of a proxy that 519 interfaces to the electrical appliances and other devices in a 520 home and also has an interface to the utility. This gateway can 521 monitor and manage the appliances (refrigerator, 522 heating/cooling, washing machine etc.) possibly using one of 523 the many protocols (ZigBee Smart Energy,...) that are being 524 developed for the home area network products and considered 525 in standards organizations. 527 In its simplest form, metering can be performed at home. Beyond 528 the metering, it is also possible implement energy saving 529 policies based on energy pricing from the utility grid. From an 530 EMAN point of view, the information model that been investigated 531 can be applied to the protocols under consideration for energy 532 monitoring of a home. 534 The essential properties of this use case are: 536 . Target devices: Home energy gateway and Smart meters in a 537 home. 538 . How powered: Any method. 539 . Reporting: Home energy gateway can collect power 540 consumption of device in a home and possibly report the 541 metering reading to the utility. 543 Beyond the canonical setting of a home drawing power from the 544 utility, it is also possible to envision an energy neutral 545 situation wherein the buildings/homes that can produce and 546 consume energy without importing energy from the utility grid. 547 There are many energy production technologies such as solar 548 panels, wind turbines, or micro generators. This use case 549 illustrates the concept of self-contained energy generation and 550 consumption and possibly the aggregation of the energy use of 551 homes. 553 2.8. Data Center Devices 555 This use case describes energy management of a Data Center 556 network. 558 Energy efficiency of data centers has become a fundamental 559 challenge of data center operation, as datacenters are big 560 energy consumers and their infrastructure is expensive. The 561 equipment generates heat, and heat needs to be evacuated though 562 a HVAC system. 564 A typical data center network consists of a hierarchy of network 565 devices. At the bottom are servers mounted on a rack; these are 566 connected to the top-of-the-rack switches; these are connected 567 to aggregation switches; those in turn connected to core 568 switches. Power consumption of all network elements and the 569 servers in the Data center should be measured. In addition, 570 there are also network storage devices. Energy management can be 571 implemented on different aggregation levels, such as network 572 level, Power Distribution Unit (PDU) level, and server level. 574 The Data center network contains UPS to provide back-up power 575 for the network devices in the event in the event of power 576 outages. Thus from a Data center energy management point of 577 view, in addition, to monitoring the energy usage of network 578 devices, it is also important to monitor the remaining capacity 579 of the UPS. 581 In addition to monitoring the power consumption, at a data 582 center level, additional metrics such as power quality, power 583 characteristics can be important metrics. The dynamic variations 584 in the input power supply from the grid referred to as power 585 quality is one metric. Secondly, how the devices use the power 586 can be referred to as power characteristics and it is also 587 useful to monitor these metrics. 589 The essential properties of this use case are: 591 . Target devices: All network devices in a data center, such 592 as network equipment, servers, and storage devices. 593 . How powered: Any method but commonly by a PDUs in racks. 594 . Reporting: Devices may report on their own behalf, or for 595 other connected devices as described in other use cases. 597 2.9. Energy Storage Devices 599 There are two types of devices with batteries: those whose 600 primary function is to provide power to another device (e.g. a 601 UPS), and those with a different primary function, but have a 602 battery as a component as an alternate internal power source 603 (e.g. a notebook). EMAN covers both types of products in this 604 use case. 606 Some devices have an internal battery as a back-up or 607 alternative source of power to mains power. When the connection 608 to the power supply of the device is disconnected, the device 609 can run on the internal battery. As batteries have a finite 610 capacity and lifetime, means for reporting the actual charge, 611 age, and state of a battery are required. 613 The battery scenario can be generalized to energy storage 614 device, UPS that can provide backup power for many devices 615 contained in data centers for a finite period of time. Energy 616 monitoring of such energy storage devices is vital from a data 617 center network operations point of view. The UPS MIB provides a 618 framework for monitoring the remaining capacity of the UPS 620 There are also battery systems for mobile towers particularly 621 for use in remote locations. It is important to monitor the 622 remaining battery life and raise an alarm when the battery life 623 is below a threshold. 625 The essential properties of this use case are: 627 . Target devices: Devices that have an internal battery such 628 as notebook PC and other mobile devices. 629 . How powered: From internal batteries or mains power. 630 . Reporting: The device reports on its internal battery. 632 2.10. Ganged Outlets on a PDU Multiple Power Sources 634 This use case describes the scenario of multiple power sources 635 of a devices and logical groupings of devices in a PDU. 637 Some PDUs allow physical entities like outlets to be "ganged" 638 together as a logical entity to simplify management. 639 This is particularly useful for servers with multiple power 640 supplies, where each power supply is connected to a different 641 physical outlet. Other implementations allow "gangs" to be 642 created based on common ownership of outlets, such as business 643 units, load shed priority, or other non-physical relationships. 645 Current implementations allow for an "M-to-N" mapping between 646 outlet "gangs" and physical outlets, as with this example: 648 . Outlet 1 - physical entity 649 . Outlet 2 - physical entity 650 . Outlet 3 - physical entity 651 . Outlet 4 - physical entity 652 . Outlet Gang A - virtual entity 653 . Outlet Gang B - virtual entity 655 o Gang A -> Outlets 1, 2 and 3 656 o Gang B -> Outlets 3 and 4 658 Note the allowed overlap on Outlet 3, which belongs to both 659 "gangs." 661 Each "Outlet Gang" entity reports the aggregated data from the 662 individual outlet entities that comprise it and enables a single 663 point of control for all the individual outlet entities. 665 2.11. Industrial Automation Networks 667 Energy consumption statistics in the industrial sector are 668 staggering. The industrial sector alone consumes about half of 669 the world's total delivered energy, making it the largest end- 670 use sector. Thus, the need for optimization of energy usage in 671 this sector is natural. 673 Industrial facilities consume energy in process loads, and in 674 non-process loads. 676 The essential properties of this use case are: 678 . Target devices: Devices used in industrial automation 679 . How powered: Any method. 680 . Reporting: Currently, CIP protocol is currently used for 681 reporting energy for these devices 683 2.12. Printers 685 This use case describes the scenario of energy monitoring and 686 management of Printer devices. 688 Printers in this use case stand in for all imaging equipment, 689 also including multi-function devices (MFDs), copiers, scanners, 690 fax machines, and mailing machines. Energy use of printers has 691 been an industry concern for several decades, and they usually 692 have sophisticated power management with a variety of low-power 693 modes, particularly for managing energy-intensive thermo- 694 mechanical components. Printers also have long made extensive 695 use of SNMP for end-user system interaction and for management 696 generally, and cross-vendor management systems are available 697 today to manage fleets of printers in enterprises. Power 698 consumption during active modes can vary widely, with high peak 699 levels. 701 Printers today can expose detailed power state information, 702 distinct from operational state information, with some printers 703 reporting transition states between stable long-term states. 704 Many also support active setting of power states, and setting of 705 policies such as delay times when no activity will cause 706 automatic transition to a lower power mode. Other features 707 include reporting on components of imaging equipment, counters 708 for state transitions, and typical power levels by state, 709 scheduling, and events/alarms. 711 Some large printers also have a "Digital Front End" which is a 712 computer that performs functions on behalf of the physical 713 imaging system. These will typically have their own presence on 714 the network and are sometimes separately powered. 716 There are some unique characteristics of Printers from the point 717 of view energy monitoring. While the printer is not use, there 718 are timer based low power states (sleep, stand-by), which 719 consume very little power. On the other hand, while the printer 720 is printing or copying the cylinder needs to be heated so that 721 power consumption is quite high but only for a short period of 722 time (duration of the print job). Given this work load, periodic 723 polling of energy consumption would not suffice. 725 Target Devices: All imaging equipment. 727 How Powered: Typically via mains AC from a wall outlet 729 Reporting: Devices report for themselves 731 2.13. Off Grid Devices 733 This use case concerns self-contained devices that use energy 734 but are not connected to an infrastructure power delivery grid. 735 These devices typically scavenge energy from environmental 736 sources such as solar energy or wind power. The device 737 generally contains a closely coupled combination of 739 . power scavenging or generation component(s) 740 . power storage component(s) (e.g., battery) 741 . power consuming component(s) 743 With scavenged power, the energy input is often dependent on the 744 random variations of the weather. These devices therefore 745 require energy management both for internal control and remote 746 reporting of their state. In order to optimize the performance 747 of these devices and minimize the costs of the generation and 748 storage components, it is desirable to vary the activity level, 749 and, hopefully, the energy requirements of the consuming 750 components in order to make best use of the available stored and 751 instantaneously generated energy. With appropriate energy 752 management, the overall device can be optimized to deliver an 753 appropriate level of service without over provisioning the 754 generation and storage components. 756 In many cases these devices are expected to operate 757 autonomously, as continuous communications for the purposes of 758 remote control is either impossible or would result in excessive 759 power consumption. Non continuous polling requires the ability 760 to store and access later the information collected while the 761 communication was not possible. 763 Target Devices: Remote network devices (mobile network) that 764 consume and produce energy 766 How Powered: Can be battery powered or using natural energy 767 sources 768 Reporting: Devices report their power usage but only 769 occasionally. 771 2.14. Demand/Response 773 Demand/Response from the utility or grid is a common theme that 774 spans across some of the use cases. In some situations, in 775 response to time-of-day fluctuation of energy costs or sudden 776 energy shortages due power outages, it may be important to 777 respond and reduce the energy consumption of the network. 779 From EMAN use case perspective, the demand/response scenario can 780 apply to a Data Center or a Building or a residential home. As a 781 first step, it may be important to monitor the energy 782 consumption in real-time of a Data center or a building or home 783 which is already discussed in the previous use cases. Then based 784 on the potential energy shortfall, the Energy Management System 785 (EMS) could formulate a suitable response, i.e., the EMS could 786 shut down some selected devices that may be considered 787 discretionary or uniformly reduce the power supplied to all 788 devices. For multi-site data centers it may be possible to 789 formulate policies such as follow-the-moon type of approach, by 790 scheduling the mobility of VMs across Data centers in different 791 geographical locations. 793 3. Use Case Patterns 795 The use cases presented above can be abstracted to the following 796 broad patterns. 798 3.1. Metering 800 - entities which have capability for internal metering 801 - entities which are metered by an external device 803 3.2. Metering and Control 805 - entities that do not supply power, but can perform only power 806 metering for other devices 808 - entities that do not supply power, can perform both metering 809 and control for other devices 810 3.3. Power Supply, Metering and Control 812 - entities that supply power for other devices but do not 813 perform power metering for those devices 815 - entities that supply power for other devices and also perform 816 power metering 818 - entities supply power for other devices and also perform power 819 metering and control for other devices 821 3.4. Multiple power sources 823 - entities that have multiple power sources and metering and 824 control is performed by one source 826 - entities that have multiple power sources and metering is 827 performed by one source and control another source 829 4. Relationship of EMAN to other Standards 831 EMAN as a framework is tied to other standards and efforts that 832 deal with energy. Existing standards are leveraged when 833 possible. EMAN helps enable adjacent technologies such as Smart 834 Grid. 836 The standards most relevant and applicable to EMAN are listed 837 below with a brief description of their objectives, the current 838 state and how that standard can be applied to EMAN. 840 4.1. Data Model and Reporting 842 4.1.1. IEC - CIM 844 The International Electrotechnical Commission (IEC) has 845 developed a broad set of standards for power management. Among 846 these, the most applicable to EMAN is IEC 61850, a standard for 847 the design of electric utility automation. The abstract data 848 model defined in 61850 is built upon and extends the Common 849 Information Model (CIM). The complete 61850 CIM model includes 850 over a hundred object classes and is widely used by utilities 851 worldwide. 853 This set of standards was originally conceived to automate 854 control of a substation (facilities which transfer electricity 855 from the transmission to the distribution system). While the 856 original domain of 61850 is substation automation, the extensive 857 data model has been widely used in other domains, including 858 Energy Management Systems (EMS). 860 IEC TC57 WG19 is an ongoing working group to harmonize the CIM 861 data model and 61850 standards. 863 Concepts from IEC Standards have been reused in the EMAN WG 864 drafts. In particular, AC Power Quality measurements have been 865 reused from IEC 61850-7-4. The concept of Accuracy Classes for 866 measurement of power and energy has been reused IEC 62053-21 and 867 IEC 62053-22. 869 4.1.2. DMTF 871 The Distributed Management Task Force (DMTF)[DMTF] has 872 standardized management solutions for managing servers and PCs, 873 including power-state configuration and management of elements 874 in a heterogeneous environment. These specifications provide 875 physical, logical and virtual system management requirements for 876 power-state control. 878 The EMAN standard references the DMTF Power Profile and Power 879 State Series. 881 4.1.2.1. Common Information Model Profiles 883 The DMTF uses CIM-based (Common Information Model) 'Profiles' to 884 represent and manage power utilization and configuration of 885 managed elements (note that this is not the 61850 CIM). Key 886 profiles for energy management are 'Power Supply' (DSP 1015), 887 'Power State' (DSP 1027) and 'Power Utilization Management' (DSP 888 1085). These profiles define monitoring and configuration of a 889 Power Managed Element's static and dynamic power saving modes, 890 power allocation limits and power states, among other features. 892 Reduced power modes can be established as static or dynamic. 893 Static modes are fixed policies that limit power use or 894 utilization. Dynamic power saving modes rely upon internal 895 feedback to control power consumption. 897 Power states are eight named operational and non operational 898 levels. These are On, Sleep-Light, Sleep-Deep, Hibernate, Off- 899 Soft, and Off-Hard. Power change capabilities provide 900 immediate, timed interval, and graceful transitions between on, 901 off, and reset power states. Table 3 of the Power State Profile 902 defines the correspondence between the ACPI and DMTF power state 903 models, although it is not necessary for a managed element to 904 support ACPI. Optionally, a TransitingToPowerState property can 905 represent power state transitions in progress. 907 4.1.2.2. DASH 909 DMTF DASH (DSP0232) (Desktop And Mobile Architecture for System 910 Hardware) addresses managing heterogeneous desktop and mobile 911 systems (including power) via in-band and out-of-band 912 communications. DASH provides management and control of managed 913 elements like power, CPU, etc. using the DMTF's WS-Management 914 web services and CIM data model. 916 Both in service and out-of-service systems can be managed with 917 the DASH specification in a fully secured remote environment. 918 Full power lifecycle management is possible using out-of-band 919 management. 921 4.1.3. ODVA 923 The Open DeviceNet Vendors Association (ODVA) is an association 924 for industrial automation companies and defines the Common 925 Industrial Protocol (CIP). Within ODVA, there is a special 926 interest group focused on energy. 928 There are many similar concepts between the ODVA and EMAN 929 frameworks towards monitoring and management of energy aware 930 devices. In particular, one of the concepts being considered 931 different energy meters based on if the device consumes 932 electricity or produces electricity or a passive device. 934 The Open DeviceNet Vendors Association (ODVA) is developing an 935 energy management framework for the industrial sector. There 936 are synergies between the ODVA and EMAN approaches to energy 937 management. 939 ODVA defines a three-part approach towards energy management: 940 awareness of energy usage, consuming energy more efficiently, 941 and exchanging energy with the utility or others. Energy 942 monitoring and management promote efficient consumption and 943 enable automating actions that reduce energy consumption. 945 The foundation of the approach is the information and 946 communication model for entities. An entity is a network- 947 connected, energy-aware device that has the ability to either 948 measure or derive its energy usage based on its native 949 consumption or generation of energy, or report a nominal or 950 static energy value. 952 4.1.4. Ecma SDC 954 The Ecma International committee on Smart Data Centre (TC38-TG2 955 SDC [Ecma-SDC]) is in the process of defining semantics for 956 management of entities in a data center such as servers, 957 storage, and network equipment. It covers energy as one of many 958 functional resources or attributes of systems for monitoring and 959 control. It only defines messages and properties, and does not 960 reference any specific protocol. Its goal is to enable 961 interoperability of such protocols as SNMP, BACNET, and HTTP by 962 ensuring a common semantic model across them. Four power states 963 are defined, Off, Sleep, Idle and Active. The standard does not 964 include actual power measurements in kW or kWh. 966 The 14th draft of SDC process was published in March 2011 and 967 the development of the standard is still underway. When used 968 with EMAN, the SDC standard will provide a thin abstraction on 969 top of the more detailed data model available in EMAN. 971 4.1.5. Printers: IEEE-ISTO Printer Working Group (PWG) 973 The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB 974 modules for printer management and has recently defined a "PWG 975 Power Management Model for Imaging Systems v1.0" [PWG5106.4] and 976 a companion SNMP binding in the "PWG Imaging System Power MIB 977 v1.0" [PWG5106.5]. This PWG model and MIB are harmonized with 978 the DMTF CIM Infrastructure [DSP0004] and DMTF CIM Power State 979 Management Profile [DSP1027] for power states and alerts. 981 The PWG would like its MIBs to be harmonized as closely as 982 possible with those from EMAN. The PWG covers many topics in 983 greater detail than EMAN, as well as some that are specific to 984 imaging equipment. The PWG also provides for vendor-specific 985 extension states (i.e., beyond the standard DMTF CIM states.) 987 4.1.6. ASHRAE FACILITY SMART GRID INFORMATION MODEL 989 In the U.S., there is an extensive effort to coordinate and 990 develop standards related to the "Smart Grid". The Smart Grid 991 Interoperability Panel, coordinated by the government's National 992 Institute of Standards and Technology, identified the need for a 993 building side information model (as a counterpart to utility 994 models) and specified this in Priority Action Plan (PAP) 17. 995 This was designated to be a joint effort by American Society of 996 Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) 997 and National Electrical Manufacturers Association (NEMA), both 998 ANSI approved SDO's. The result is to be an information model, 999 not a device level monitoring protocol. 1001 The ASHRAE effort addresses data used only within a building as 1002 well as data that may be shared with the grid, particularly as 1003 it relates to coordinating future demand levels with the needs 1004 of the grid. The model is intended to be applied to any 1005 building type, both residential and commercial. It is expected 1006 that existing protocols will be adapted to comply with the new 1007 information model, as would any new protocols. 1009 There are four basic types of entities in the model: generators, 1010 loads, meters, and energy managers. 1012 The metering part of this model overlaps with the EMAN framework 1013 to a large degree, though there are features unique to each. 1014 The load part speaks to control capabilities well beyond what 1015 EMAN covers. Details of generation and of the energy management 1016 function are outside of EMAN scope. 1018 A public review draft of the ASHRAE standard is expected soon, 1019 and at that point detailed comparison of the two models can be 1020 made. There are no apparent major conflicts between the two 1021 approaches, but there are likely areas where some harmonization 1022 is possible, and regardless, a description of the 1023 correspondences would be helpful to create. 1025 4.1.7. ZigBee 1027 The Zigbee Smart Energy 2.0 effort [ZIGBEE] focuses on wireless 1028 communication to appliances and lighting. It is intended to 1029 enable building energy management and enable direct load control 1030 by utilities. 1032 ZigBee protocols are intended for use in embedded applications 1033 requiring low data rates and low power consumption. ZigBee 1034 defines a general-purpose, inexpensive, self-organizing mesh 1035 network that can be used for industrial control, embedded 1036 sensing, medical data collection, smoke and intruder warning, 1037 building automation, home automation, etc. 1039 Zigbee is currently not an ANSI recognized SDO. 1041 The EMAN framework addresses the needs of IP-enabled networks 1042 through the usage of SNMP, while Zigbee looks for completely 1043 integrated and inexpensive mesh solution. 1045 4.2. Measurement 1047 4.2.1. ANSI C12 1049 The American National Standards Institute (ANSI) has defined a 1050 collection of power meter standards under ANSI C12. The primary 1051 standards include communication protocols (C12.18, 21 and 22), 1052 data and schema definitions (C12.19), and measurement accuracy 1053 (C12.20). European equivalent standards are provided by IEC 1054 62053-22.ANSI C12.20 defines accuracy classes for watt-hour 1055 meters. 1057 All of these standards are oriented toward the meter itself, and 1058 are therefore very specific and used by electricity distributors 1059 and producers. 1061 The EMAN standard references ANSI C12 accuracy classes. 1063 4.2.2. IEC62301 1065 IEC 62301, "Household electrical appliances Measurement of 1066 standby power", specifies a power level measurement procedure. 1067 While nominally for appliances and low-power modes, many aspects 1068 of it apply to other device types and modes and it is commonly 1069 referenced in test procedures for energy using products. 1071 While the standard is intended for laboratory measurements of 1072 devices in controlled conditions, many aspects of it are 1073 informative to those implementing measurement in products that 1074 ultimately report via EMAN. 1076 4.3. Other 1078 4.3.1. ISO 1080 The ISO [ISO] is developing an energy management standard, ISO 1081 50001, to complement ISO 9001 for quality management, and ISO 1082 14001 for environment management. The intent of the framework is 1083 to facilitate the creation of energy management programs for 1084 industrial, commercial and other entities. The standard defines 1085 a process for energy management at an organization level. It 1086 does not define the way in which devices report energy and 1087 consume energy. 1089 EMAN is complementary to ISO 9001. 1091 ISO 50001 is based on the common elements found in all of ISO's 1092 management system standards, assuring a high level of 1093 compatibility with ISO 9001 (quality management) and ISO 14001 1094 (environmental management). ISO 50001 benefits includes: 1096 o Integrating energy efficiency into management practices and 1097 throughout the supply chain 1098 o Energy management best practices and good energy management 1099 behaviors 1100 o benchmarking, measuring, documenting, and reporting energy 1101 intensity improvements and their projected impact on 1102 reductions in greenhouse gas (GHG) emissions 1103 o Evaluating and prioritizing the implementation of new energy- 1104 efficient technologies 1106 ISO 50001 has been developed by ISO project committee ISO/PC 1107 242, Energy management. 1109 4.3.2. Energy Star 1111 The US Environmental Protection Agency (EPA) and US Department 1112 of Energy (DOE) jointly sponsor the Energy Star program [ESTAR]. 1113 The program promotes the development of energy efficient 1114 products and practices. 1116 To qualify as Energy Star, products must meet specific energy 1117 efficiency targets. The Energy Star program also provides 1118 planning tools and technical documentation to encourage more 1119 energy efficient building design. Energy Star is a program; it 1120 is not a protocol or standard. 1122 For businesses and data centers, Energy Star offers technical 1123 support to help companies establish energy conservation 1124 practices. Energy Star provides best practices for measuring 1125 current energy performance, goal setting, and tracking 1126 improvement. The Energy Star tools offered include a rating 1127 system for building performance and comparative benchmarks. 1129 There is no immediate link between EMAN and Energy Star, one 1130 being a protocol and the other a set of recommendations to 1131 develop energy efficient products. However, Energy Star could 1132 include EMAN standards in specifications for future products, 1133 either as required or rewarded with some benefit. 1135 4.3.3. Smart Grid 1137 The Smart Grid standards efforts underway in the United States 1138 are overseen by the US National Institute of Standards and 1139 Technology [NIST]. NIST is responsible for coordinating a 1140 public-private partnership with key energy and consumer 1141 stakeholders in order to facilitate the development of smart 1142 grid standards. The NIST smart grid standards activities are 1143 monitored and facilitated by the SGIP (Smart Grid 1144 Interoperability Panel). This group has working groups for 1145 specific topics including homes, commercial buildings, and 1146 industrial facilities as they relate to the grid. 1148 When a working group detects a standard or technology gap, the 1149 team seeks approval from the SGIP for the creation of a Priority 1150 Action Plan (PAP), a private-public partnership to close the 1151 gap. There are currently 17 PAPs. PAP 17 is discussed in 1152 section 4.1.6. 1154 PAP 10 addresses "Standard Energy Usage Information". 1155 Smart Grid standards will provide distributed intelligence in 1156 the network and allow enhanced load shedding. For example, 1157 pricing signals will enable selective shutdown of non critical 1158 activities during peak-load pricing periods. These actions can 1159 be effected through both centralized and distributed management 1160 controls. 1162 There is an obvious functional link between Smart Grid and EMAN 1163 in the form of demand response, even if the EMAN framework does 1164 not take any specific step toward Smart Grid communication. 1166 5. Limitations 1168 EMAN Framework shall address the needs of energy monitoring in 1169 terms of measurement and, considers limited control capabilities 1170 of energy monitoring of networks. 1172 EMAN does not create a new protocol stack, but rather defines a 1173 data and information model useful for measuring and reporting 1174 energy and other metrics over SNMP. 1176 The EMAN framework does not address questions regarding 1177 SmartGrid, electricity producers, and distributors even if there 1178 is obvious link between them. 1180 6. Security Considerations 1182 EMAN shall use SNMP protocol for energy monitoring and thus has 1183 the functionality of SNMP's security capabilities. SNMPv3 1184 [RFC3411] provides important security features such as 1185 confidentiality, integrity, and authentication. 1187 7. IANA Considerations 1189 This memo includes no request to IANA. 1191 8. Acknowledgements 1193 The authors would like to thank Jeff Wheeler, Benoit Claise, 1194 Juergen Quittek, Chris Verges, John Parello, and Matt Laherty, 1195 for their valuable contributions. 1197 The authors would like to thank Georgios Karagiannis for use 1198 case involving energy neutral homes, Elwyn Davies for off-grid 1199 electricity systems, and Kerry Lynn for the comment on the 1200 Demand/Response scenario. 1202 9. Open Issues 1204 OPEN ISSUE 1: Relevant IEC standards for application for EMAN 1205 Applicability Statement document can provide guidance on the 1206 issue of what is appropriate standard used by EMAN 1208 IEC 61850-7-4 has been extensively used in EMAN WG documents. 1209 The other IEC documents referred for possible use are IEC 1210 61000-4-30, IEC 62053-21 and IEC 62301. 1212 There is feedback that IEC 61850-7-4 applies only to sub- 1213 stations ? 1215 OPEN ISSUE 2: Should review ASHRAE SPC 201P standard when it is 1216 released for public review 1218 . Need to review ASHRAE information model and the use cases 1219 and how it relates to EMAN 1221 OPEN ISSUE 3: Review ALL requirements to ensure that they can be 1222 traced to a use case 1223 . Missing is an use case for power quality 1225 OPEN ISSUE 4: Question for the WG: Should we have unique use 1226 cases that introduce specific requirements ? or can there be 1227 some overlap between some use cases ? 1229 Any use cases out of scope scenarios ? 1231 10. References 1233 10.1. Normative References 1235 [RFC3411] An Architecture for Describing Simple Network 1236 Management Protocol (SNMP) Management Frameworks, RFC 1237 3411, December 2002. 1239 10.2. Informative References 1241 [DASH] "Desktop and mobile Architecture for System Hardware", 1242 http://www.dmtf.org/standards/mgmt/dash/ 1244 [NIST] http://www.nist.gov/smartgrid/ 1246 [Ecma-SDC] Ecma TC38 / SDC Task Group, "Smart Data Centre 1247 Resource Monitoring and Control (DRAFT)", March 2011. 1249 [ENERGY] http://en.wikipedia.org/wiki/Kilowatt_hour 1251 [EMAN-AS] Tychon, E., B. Schoening , MouliChandramouli, Bruce 1252 Nordman, "Energy Management (EMAN) Applicability 1253 Statement", draft-tychon-eman-applicability-statement- 1254 04.txt, work in progress, October 2011. 1256 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 1257 M. Chandramouli, "Requirements for Energy Management ", 1258 draft-ietf-eman-requirements-04 (work in progress),July 1259 2011. 1261 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 1262 Quittek, J. and B. Claise "Energy and Power Monitoring 1263 MIB ", draft-ietf-eman-monitoring-mib-00,August 2011. 1265 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 1266 energy-aware-mib-02", work in progress, July 2011. 1268 [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. 1269 Quittek, "Energy Management Framework", draft-ietf- 1270 eman-framework-02 ,July 2011. 1272 [EMAN-BATTERY-MIB] Quittek, J., Winter, R., and T. Dietz, 1273 "Definition of Managed Objects for Battery Monitoring" 1274 draft-ietf-eman-battery-mib-02.txt, July 2011. 1276 [DMTF] "Power State Management ProfileDMTFDSP1027 Version 2.0" 1277 December2009. 1278 http://www.dmtf.org/sites/default/files/standards/docum 1279 ents/DSP1027_2.0.0.pdf 1281 [ESTAR] http://www.energystar.gov/ 1283 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1434 1285 [SGRID] http://collaborate.nist.gov/twiki- 1286 sggrid/bin/view/SmartGrid/SGIPWorkingGroupsAndCommittee 1287 s 1289 [ASHRAE] http://collaborate.nist.gov/twiki- 1290 sggrid/bin/view/SmartGrid/PAP17Information 1292 [PAP17] http://collaborate.nist.gov/twiki- 1293 sggrid/bin/view/SmartGrid/PAP17FacilitySmartGridInforma 1294 tionStandard 1296 [ZIGBEE] http://www.zigbee.org/ 1298 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1337 1300 [DSP0004] DMTF Common Information Model (CIM) Infrastructure, 1301 DSP0004, May 2009. 1302 http://www.dmtf.org/standards/published_documents/DSP00 1303 04_2.5.0.pdf 1305 [DSP1027] DMTF Power State Management Profile, DSP1027, December 1306 2009. 1307 http://www.dmtf.org/standards/published_documents/DSP10 1308 27_2.0.0.pdf 1310 [PWG5106.4] IEEE-ISTO PWG Power Management Model for Imaging 1311 Systems v1.0, PWG Candidate Standard 5106.4-2011, 1312 February 2011. ftp://ftp.pwg.org/pub/pwg/candidates/cs- 1313 wimspower10-20110214-5106.4.mib 1315 [PWG5106.5] IEEE-ISTO PWG Imaging System Power MIB v1.0, PWG 1316 Candidate Standard 5106.5-2011, February 2011. 1318 [IEC62301] International Electrotechnical Commission, "IEC 62301 1319 Household electrical appliances Measurement of 1320 standby power", Edition 2.0, 2011. 1322 Authors' Addresses 1324 Emmanuel Tychon 1325 Cisco Systems, Inc. 1326 De Keleetlaan, 6A 1327 B1831 Diegem 1328 Belgium 1329 Email: etychon@cisco.com 1331 Brad Schoening 1332 44 Rivers Edge Drive 1333 Little Silver, NJ 07739 1334 USA 1335 Email: brad@bradschoening.com 1337 Mouli Chandramouli 1338 Cisco Systems, Inc. 1339 Sarjapur Outer Ring Road 1340 Bangalore, 1341 India 1342 Phone: +91 80 4426 3947 1343 Email: moulchan@cisco.com 1345 Bruce Nordman 1346 Lawrence Berkeley National Laboratory 1347 1 Cyclotron Road, 90-4000 1348 Berkeley 94720-8136 1349 USA 1351 Phone: +1 510 486 7089 1352 Email: bnordman@lbl.gov