idnits 2.17.1 draft-tychon-eman-applicability-statement-05.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 3 longer pages, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' scope of devices considered are network equipment and its' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 6. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 7. IANA Considerations' ) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 31, 2011) is 4560 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? 'EMAN-DEF' on line 1330 looks like a reference -- Missing reference section? 'EMAN-AS' on line 1305 looks like a reference -- Missing reference section? 'EMAN-REQ' on line 1310 looks like a reference -- Missing reference section? 'EMAN-FRAMEWORK' on line 1322 looks like a reference -- Missing reference section? 'EMAN-AWARE-MIB' on line 1319 looks like a reference -- Missing reference section? 'EMAN-MONITORING-MIB' on line 1315 looks like a reference -- Missing reference section? 'EMAN-BATTERY-MIB' on line 1326 looks like a reference -- Missing reference section? 'DMTF' on line 1333 looks like a reference -- Missing reference section? 'Ecma-SDC' on line 1300 looks like a reference -- Missing reference section? 'DSP0004' on line 1357 looks like a reference -- Missing reference section? 'DSP1027' on line 1362 looks like a reference -- Missing reference section? 'ZIGBEE' on line 1353 looks like a reference -- Missing reference section? 'ISO' on line 1355 looks like a reference -- Missing reference section? 'ESTAR' on line 1338 looks like a reference -- Missing reference section? 'NIST' on line 1298 looks like a reference -- Missing reference section? 'RFC3411' on line 1289 looks like a reference -- Missing reference section? 'DASH' on line 1295 looks like a reference -- Missing reference section? 'ENERGY' on line 1303 looks like a reference -- Missing reference section? 'SGRID' on line 1342 looks like a reference -- Missing reference section? 'ASHRAE' on line 1346 looks like a reference -- Missing reference section? 'PAP17' on line 1349 looks like a reference -- Missing reference section? 'IEC62301' on line 1375 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 23 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 31, 2012 Independent Consultant 6 Mouli Chandramouli 7 Cisco Systems Inc. 8 Bruce Nordman 9 Lawrence Berkeley National Laboratory 10 October 31, 2011 12 Energy Management (EMAN) Applicability Statement 13 draft-tychon-eman-applicability-statement-05 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 31, 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 energy 57 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 70 ..............................4 71 1.2. Energy Measurement 72 ......................................5 73 1.3. Energy Management 74 .......................................5 75 1.4. EMAN Framework Application 76 ..............................6 77 1.5. EMAN WG Document Overview 78 ...............................6 79 2. Scenarios and Target Devices 80 ................................7 81 2.1. Network Infrastructure Energy Objects 82 ...................7 83 2.2. Devices Powered and Connected to a Network Device 84 .......8 85 2.3. Devices Connected to a Network 86 ..........................9 87 2.4. Power Meters 88 ............................................9 89 2.5. Mid-level Managers 90 .....................................10 91 2.6. Gateways to Building Systems 92 ...........................11 93 2.7. Home Energy Gateways 94 ...................................12 95 2.8. Data Center Devices 96 ....................................13 97 2.10. Ganged Outlets on a PDU Multiple Power Sources ........14 98 2.11. Industrial Automation Networks 99 ......................15 100 2.12. Printers 101 ...................................15 102 2.13. Off-Grid Devices 103 ......................................17 104 2.14. Demand/Response 105 .....................................17 106 2.15. Power Capping 107 ........................................18 108 3. Use Case Patterns 109 ..........................................18 110 3.1. Metering 111 ...............................................18 112 3.2. Metering and Control 113 ...................................19 114 3.3. Power Supply, Metering and Control 115 .....................19 116 3.4. Multiple power sources 117 .................................19 118 4. Relationship of EMAN to other Standards 119 ....................19 120 4.1. Data Model and Reporting 121 ...............................20 122 4.1.1. IEC - CIM. ......................................20 123 4.1.2. DMTF ............................................20 124 4.1.3. ODVA ............................................21 125 4.1.4. Ecma SDC ........................................22 126 4.1.5. IEEE-ISTO Printer Working Group (PWG) ...........22 127 4.1.6. ASHRAE ..........................................23 128 4.1.7. ZigBee ..........................................24 129 4.2. Measurement 130 ............................................24 131 4.2.1. ANSI C12 ........................................24 132 4.2.2. IEC62301 ........................................24 133 4.3. Other 134 ..................................................25 135 4.3.1. ISO .............................................25 136 4.3.2. EnergyStar ......................................26 137 4.3.3. SmartGrid .......................................26 138 5. Limitations 139 ................................................27 140 6. Security Considerations 141 ....................................27 142 7. IANA Considerations 143 ........................................27 144 8. Acknowledgements 145 ...........................................27 146 9. Open Issues 147 ...............................................28 148 10. References 149 ................................................28 150 10.1. Normative References 151 ..................................28 152 10.2. Informative References 153 ................................29 155 1. Introduction 157 The focus of the Energy Management (EMAN) framework is energy 158 monitoring and management of energy objects [EMAN-DEF]. The 159 scope of devices considered are network equipment and its 160 the network. The EMAN framework enables monitoring i.e.; 161 heterogeneous devices to report their energy consumption, and 162 secondly, if permissible, enables control policies for energy 163 savings. There are multiple scenarios where this is 164 desirable, particularly considering the increased importance 165 of limiting consumption of finite energy resources and 166 reducing operational expenses. 168 The EMAN framework describes how energy information can be 169 retrieved from IP-enabled devices using Simple Network 170 Management Protocol (SNMP), specifically, Management Information 171 Base (MIBs) for SNMP. 173 This document describes typical applications of the EMAN 174 framework, as well as its opportunities and limitations. Other 175 standards that are similar to EMAN but address different domains 176 are described. This document contains references to those other 177 standards and describes how they relate to the EMAN framework. 179 1.1. Energy Management Overview 181 First, a brief introduction to the definitions of Energy and 182 Power are presented. A draft on terminology has been submitted 183 so that to reach a consensus on the definitions of commonly used 184 terms in the EMAN WG. While energy is available in many forms, 185 EMAN addresses only the electrical energy consumed by devices 186 connected to a network. 188 Energy is the capacity to perform work. Electrical energy is 189 typically expressed in kilowatt-hour units (kWh) or other 190 multiples of watt-hours (Wh). One kilowatt-hour is the 191 electrical energy used by a 1 kilowatt device for one hour. 192 Power is the rate of electrical energy flow. In other words, 193 power = energy / time. Power is often measured in watts. Billing 194 is based on electrical energy (measured in kWh) supplied by the 195 utility. 197 Towards the goal of increasing the energy efficiency in networks 198 and buildings, a first step is to enable energy objects to 199 report their energy usage over time. The EMAN framework 200 addresses this problem with an information model for some 201 electrical equipment: energy object identification, energy 202 object context, power measurement and power measurement 203 attributes. 205 The EMAN WG framework defines SNMP MIB modules based on the 206 information model. By implementing the SNMP MIB modules, any 207 energy object can report its energy consumption according to the 208 information model. In that context, it is important to 209 distinguish energy objects that can report their own energy 210 usage from parent devices that can also collect and aggregate 211 energy usage of children energy objects. 213 The list of target devices and scenarios considered for Energy 214 Management are presented in Section 2 with detailed examples. 216 1.2. Energy Measurement 218 More and more devices are able to measure and report their own 219 energy consumption. Smart power strips and some Power over 220 Ethernet (PoE) switches can meter consumption of connected 221 devices. However, when managed and reported through proprietary 222 means, this information is minimally useful at the enterprise 223 level. 225 The primary goal of the EMAN MIBs is to enable reporting and 226 management within a standard framework that is applicable to a 227 wide variety of end devices, meters, and proxies. This enables a 228 management system to know who's consuming what, when, and how at 229 any time by leveraging existing networks, across various 230 equipment, in a unified and consistent manner. 232 Given that an energy object can consume energy and/or provide 233 energy to other devices, there are three types of meters for 234 energy measurement: energy input to a device, energy supplied to 235 other devices, and net (resultant) energy consumed (the 236 difference between energy input and provided). 238 1.3. Energy Management 240 Beyond energy monitoring, the EMAN framework provides mechanisms 241 for energy control. 243 There are many cases where reducing energy consumption of 244 devices is desirable, such as when the device utilization islow 245 or when the electricity is expensive or in short supply. 247 In some cases, energy control requires considering the energy 248 object context. For instance, in a building: all phones would 249 not usually be turned off to keep some still available in case 250 of emergency; office cooling is usually not turned off totally 251 during non-work hours, but the comfort level is reduced; and so 252 on. 254 Energy object control requires flexibility and support for 255 different polices and mechanisms: from centralized management 256 with a network management station, to autonomous management by 257 individual devices, and alignment with dynamic demand-response 258 mechanisms. 260 The EMAN framework can be used as a tool for the demand/response 261 scenario where in response to time-of-day fluctuation of energy 262 costs or possible energy shortages, it is possible to respond 263 and reduce the energy consumption for the network devices, 264 effectively changing its power state. 266 1.4. EMAN Framework Application 268 A Network Management System (NMS) is the entity that requests 269 information from compatible devices using SNMP protocol. It may 270 be a system which also implements other network management 271 functions, e.g. security management, identity management and so 272 on), or one that only deals exclusively with energy in which 273 case it is called EnMS, Energy Management System. It may be 274 limited to monitoring energy use, or it may also implement 275 control functions. In a typical application of the EMAN 276 framework, management software collects energy information for 277 devices in the network. 279 Energy management can be implemented by extending existing SNMP 280 support to the EMAN specific MIBs. SNMP provides an industry 281 proven and well-known mechanism to discover, secure, measure, 282 and control SNMP-enabled end devices. The EMAN framework 283 provides an information and data model to unify access to a 284 large range of devices. The scope of the target devices and the 285 network scenarios considered for energy management are listed in 286 Section 2. 288 1.5. EMAN WG Document Overview 290 The EMAN working group charter calls for producing a series of 291 Internet standard drafts in the area of energy management. The 292 following drafts are currently under discussion in the working 293 group. 295 Applicability Statement [EMAN-AS] This draft presents the use 296 cases and scenarios for energy monitoring. In addition, other 297 relevant energy standards and architectures are listed. 299 Requirements [EMAN-REQ] This draft presents the requirements 300 of Energy Monitoring and the scope of the devices considered. 302 Framework [EMAN-FRAMEWORK] This draft defines the terminology 303 and explains the different concepts associated with energy 304 monitoring; these are used in the MIB modules. 306 Energy-Aware MIB [EMAN-AWARE-MIB] This draft proposes a MIB 307 module that characterizes a device's identity and context. 309 Monitoring MIB [EMAN-MONITORING-MIB] This draft defines a MIB 310 module for monitoring the power and energy consumption of a 311 device. In addition, the MIB module contains an optional 312 module for power quality metrics. 314 Battery MIB [EMAN-BATTERY-MIB] This draft contains a MIB 315 module for monitoring characteristics of an internal battery. 317 Energy Management Terminology [EMAN-DEF] This draft lists the 318 definitions and terms used in the Energy Management Working 319 Group. 321 2. Scenarios and Target Devices 323 In this section a selection of scenarios for energy management 324 are presented. The fundamental objective of the use cases is to 325 list important network scenarios that the EMAN framework should 326 solve. These use cases then drive the requirements for the EMAN 327 framework. 329 Each scenario lists target devices for which the energy 330 management framework can be applied, as well as how the 331 reported-on devices are powered, and how the reporting is 332 accomplished. While there may be some overlap between some of 333 the use cases, the use cases serve as illustrative network 334 scenarios EMAN framework should solve. 336 2.1. Network Infrastructure Energy Objects 338 This scenario covers network devices and their components. Power 339 management of energy objects is considered as a fundamental 340 requirement of energy management of networks. 342 It can be important to monitor the power state and energy 343 consumption of these energy objects at a granularity level finer 344 than just the entire device. For these devices, the chassis 345 draws power from one or more sources and feeds all its internal 346 components. It is highly desirable to have monitoring available 347 for individual components, such as line cards, processors, and 348 hard drives as well as peripherals like USB devices. 350 As an illustrative example, consider a switch with the following 351 grouping of sub-entities for which energy monitoring could be 352 useful. 354 . physical view: chassis (or stack), line cards, service 355 modules of the switch 356 . component view: CPU, ASICs, fans, power supply, ports 357 (single port and port groups), storage and memory 358 . logical view: system, data-plane, control-plane, etc. 360 The essential properties of this use case are: 362 . Target devices: Network devices such as routers, switches 363 and their components. 364 . How powered: Typically by a PDU on a rack or from a wall 365 outlet. The components of a device are powered by the 366 device chassis. 367 . Reporting: Direct power measurement can be performed at a 368 device level. Components can report their power consumption 369 directly or the chassis/device that can report on behalf of 370 some components. 372 2.2. Devices Powered and Connected to a Network Device 374 This scenario covers Power over Ethernet (PoE) devices. A PoE 375 Power Sourcing Equipment (PSE) device (e.g. a PoE switch) 376 provides power to a Powered Device (PD) (e.g. a desktop phone). 377 For each port, the PSE can control the power supply (switching 378 it on and off) and monitor actual power provided. PoE devices 379 obtain network connectivity as well as the power supply for the 380 device over a single connection so the PSE can determine which 381 device to allocate each port's power to. 383 PoE ports on a switch are commonly connected to IP phones, 384 wireless access points, and IP cameras. The switch powers 385 itself, as well as supplies power to downstream PoE ports. 386 Monitoring the power consumption of the switch (Energy Object 387 Parent) and the power consumption of the PoE end-points(Energy 388 Object Children) is a simple use case of this scenario. 390 The essential properties of this use case are: 392 . Target devices: Power over Ethernet devices such as IP 393 Phones, Wireless Access Points, and IP cameras. 394 . How powered: PoE devices are connected to the switch port 395 which supplies power to those devices. 396 . Reporting: PoE device power consumption is often measured 397 and reported at the switch (PSE) port which supplies power 398 for the PoE device. 400 In this case, the PoE devices do not need to directly support 401 the EMAN framework, only the Power Sourcing Equipment (PSE) 402 does. 404 2.3. Devices Connected to a Network 406 The use case covers the metering relationship between an energy 407 object receiving power from a source such as a power brick, and 408 have an independent network connection to a parent energy object 409 such as a switch. 411 In continuation to the previous example is a switch port that 412 has both a PoE connection powering an IP Phone, and a PC has a 413 daisy-chain connection to the IP Phone for network connectivity. 414 The PC has a network connection from the switch, but draws power 415 from the wall outlet, in contrast to the IP phone draws power 416 from the switch. 418 It is also possible to consider a simple example of PC which has 419 a network connection but draws power from the wall outlet or 420 PDU. 422 The PC in this case, is an non-PoE device, can report power 423 usage by itself, for instance through the EMAN framework. 425 The essential properties of this use case are: 427 . Target devices: Abroad set of energy objects that have a 428 network connection, but receive power supply from the wall 429 outlet. 430 . How powered: These devices receive power supply from the 431 wall outlet or a PDU. 432 . Reporting: There are two models: devices that can measure 433 and report the power consumption directly via the EMAN 434 framework, and those that communicate it to the network 435 device (switch) and the switch can report the device's 436 power consumption via the EMAN framework. 438 2.4. Power Meters 440 Some electrical devices are not equipped with instrumentation to 441 measure their own power and accumulated energy consumption. 442 External meters can be used to measure the power consumption of 443 such electrical devices. 445 This use case covers the proxy relationship of energy objects 446 able to measure or report the power consumption of external 447 electrical devices, not natively connected to the network. 448 Examples of such metering devices are smart PDUs and smart 449 meters. 451 Three types of external metering are relevant to EMAN: PDUs, 452 standalone meters, and utility meters. External meters can 453 measure these properties for a single device or for a set of 454 devices. 456 Power Distribution Unit (PDUs) in a rack have inbuilt meters for 457 each socket and the PDUs can measure the power supplied to each 458 device in an equipment rack. The PDUs have remote management 459 functionality which can be used to measure and possibly control 460 the power supply of each outlet. 462 Standalone meters can be placed anywhere in a power distribution 463 tree, and can measure the power consumption. 464 Utility meters monitor and report accumulated power consumption 465 of the entire building. There can be sub-meters to measure the 466 power consumption of a portion of the building. 468 The essential properties of this use case are: 470 . Target devices: PDUs and Smart Meters. 471 . How powered: From traditional mains power but as passed 472 through a PDU or meter. 473 . Reporting: The PDUs reports power consumption of 474 downstream devices. There is commonly only one device 475 downstream of each outlet, but there could be many. There 476 can be external meters in between the power supply and 477 device and the meters can report the power consumption of 478 the device. 480 2.5. Mid-level Managers 482 This use case covers aggregation of energy management data at 483 "mid-level managers" that can provide energy management 484 functions for themselves as well as associated devices. 486 A switch can provide energy management functions for all devices 487 connected to its ports, whether or not these devices are powered 488 by the switch or whether the switch provides immediate network 489 connectivity to the devices; such a switch is a mid-level 490 manager, offering aggregation of power consumption data for 491 devices it does not supply power to them. Devices report their 492 EMAN data to the switch and the switch aggregates the data for 493 these data. 495 The essential properties of this use case are summarized as 496 follows: 498 . Target devices: network devices which can perform 499 aggregation; commonly a switch or a proxy 500 . How powered: Mid-level managers can be are commonly 501 powered by a PDU or from a wall outlet but there is no 502 limitation. 503 . Reporting: The middle-manager aggregates the energy data 504 and reports that data to a NMS or higher mid-level manager. 506 2.6. Gateways to Building Systems 508 This use case describes energy management of buildings. Building 509 Management Systems (BMS) have been in place for many years using 510 legacy protocols not based on IP. In these buildings, a gateway 511 can provide a proxy relationship between IP and legacy building 512 automation protocols. The gateway can provide an interface 513 between the EMAN framework and relevant building management 514 protocols. 516 Due to the potential energy savings, energy management of 517 buildings has received significant attention. There are gateway 518 network elements to manage the multiple components ofa building 519 energy management system such as Heating, Ventilation, and Air 520 Conditioning (HVAC), lighting, electrical, fire and emergency 521 systems, elevators, etc. The gateway device uses legacy building 522 protocols to communicate with those devices, collects their 523 energy usage, and reports the results. 525 The gateway performs protocol conversion between many facility 526 management devices. The gateway communicates via RS-232/RS-485 527 interfaces, Ethernet interfaces, and protocols specific to 528 building management such as BACNET, MODBUS, or Zigbee. 530 The essential properties of this use case are : 532 . Target devices: Building energy management devices - HVAC 533 systems, lighting, electrical, fire and emergency systems. 534 There are meters for each of the sub-systems and the energy 535 data is communicated to the proxy using legacy protocols. 536 . How powered: Any method, including directly from mains 537 power or via a UPS. 539 . Reporting: The gateway collects energy consumption of non- 540 IP systems and communicates the data via the EMAN 541 framework. 543 2.7. Home Energy Gateways 545 This use case describes the scenario of energy management of a 546 home. The home energy gateway is another example of a proxy that 547 interfaces to the electrical appliances and other devices in a 548 home and also has an interface to the utility. This gateway can 549 monitor and manage electrical equipment (refrigerator, 550 heating/cooling, washing machine etc.) possibly using one of the 551 many protocols (ZigBee, Smart Energy, ...) that are being 552 developed for the home area network products and considered in 553 standards organizations. 555 In its simplest form, metering can be performed at home. Beyond 556 the metering, it is also possible implement energy saving 557 policies based on energy pricing from the utility grid. From an 558 EMAN point of view, the information model that been investigated 559 can be applied to the protocols under consideration for energy 560 monitoring of a home. 562 The essential properties of this use case are: 564 . Target devices: Home energy gateway and Smart meters in a 565 home. 566 . How powered: Any method. 567 . Reporting: Home energy gateway can collect power 568 consumption of device in a home and possibly report the 569 metering reading to the utility. 571 Beyond the canonical setting of a home drawing power from the 572 utility, it is also possible to envision an energy neutral 573 situation wherein the buildings/homes that can produce and 574 consume energy without importing energy from the utility grid. 575 There are many energy production technologies such as solar 576 panels, wind turbines, or micro generators. This use case 577 illustrates the concept of self-contained energy generation and 578 consumption and possibly the aggregation of the energy use of 579 homes. 581 2.8. Data Center Devices 583 This use case describes energy management of a Data Center 584 network. 586 Energy efficiency of data centers has become a fundamental 587 challenge of data center operation, as datacenters are big 588 energy consumers and their infrastructure is expensive. The 589 equipment generates heat, and heat needs to be evacuated though 590 a HVAC system. 592 A typical data center network consists of a hierarchy of 593 electrical energy objects. At the bottom are servers mounted on 594 a rack; these are connected to the top-of-the-rack switches; 595 these are connected to aggregation switches; those in turn 596 connected to core switches. Power consumption of all network 597 elements and the servers in the Data center should be measured. 598 In addition, there are also network storage devices. Energy 599 management can be implemented on different aggregation levels, 600 such as network level, Power Distribution Unit (PDU) level, and 601 server level. 603 The Data center network contains UPS to provide back-up power 604 for the network devices in the event in the event of power 605 outages. Thus from a Data center energy management point of 606 view, in addition, to monitoring the energy usage of network 607 devices, it is also important to monitor the remaining capacity 608 of the UPS. 610 In addition to monitoring the power consumption, at a data 611 center level, additional metrics such as power quality, power 612 characteristics can be important metrics. The dynamic variations 613 in the input power supply from the grid referred to as power 614 quality is one metric. Secondly, how the devices use the power 615 can be referred to as power characteristics and it is also 616 useful to monitor these metrics. Lastly, the power plate set 617 will make it possible to know an aggregate of the potential 618 worst-case power usage and compare it to the budgeted power in 619 the data center. 621 The essential properties of this use case are: 623 . Target devices: All network devices in a data center, such 624 as network equipment, servers, and storage devices. 625 . How powered: Any method but commonly by a PDUs in racks. 626 . Reporting: Devices may report on their own behalf, or for 627 other connected devices as described in other use cases. 629 2.9. Energy Storage Devices 631 There are two types of devices with energy storage: those whose 632 primary function is to provide power to another device (e.g. a 633 UPS), and those with a different primary function, but have an 634 energy storage as a component as an alternate internal power 635 source (e.g. a notebook). EMAN covers both types of products in 636 this use case. 638 The energy storage can be a battery, or any other means to store 639 electricity such as a hydrogen cell. 641 Some devices have an internal battery as a back-up or 642 alternative source of power to mains power. When the connection 643 to the power supply of the device is disconnected, the device 644 can run on the internal battery. As batteries have a finite 645 capacity and lifetime, means for reporting the actual charge, 646 age, and state of a battery are required. 648 UPS can provide backup power for many devices in a data centers 649 for a finite period of time. Energy monitoring of such energy 650 storage devices is vital from a data center network operations 651 point of view. The UPS MIB provides a framework for monitoring 652 the remaining capacity of the UPS. 654 There are also battery systems for mobile towers particularly 655 for use in remote locations. It is important to monitor the 656 remaining battery life and raise an alarm when the battery life 657 is below a threshold. 659 The essential properties of this use case are: 661 . Target devices: Devices that have an internal battery such 662 as notebook PC and other mobile devices. 663 . How powered: From internal batteries or mains power. 664 . Reporting: The device reports on its internal battery. 666 2.10. Ganged Outlets on a PDU Multiple Power Sources 668 This use case describes the scenario of multiple power sources 669 of a devices and logical groupings of devices in a PDU. 671 Some PDUs allow physical entities like outlets to be "ganged" 672 together as a logical entity to simplify management. 674 This is particularly useful for servers with multiple power 675 supplies, where each power supply is connected to a different 676 physical outlet. Other implementations allow "gangs" to be 677 created based on common ownership of outlets, such as business 678 units, load shed priority, or other non-physical relationships. 680 Current implementations allow for an "M-to-N" mapping between 681 outlet "gangs" and physical outlets, as with this example: 683 . Outlet 1 - physical entity 684 . Outlet 2 - physical entity 685 . Outlet 3 - physical entity 686 . Outlet 4 - physical entity 687 . Outlet Gang A - virtual entity 688 . Outlet Gang B - virtual entity 690 o Gang A -> Outlets 1, 2 and 3 691 o Gang B -> Outlets 3 and 4 693 Note the allowed overlap on Outlet 3, which belongs to both 694 "gangs." 696 Each "Outlet Gang" entity reports the aggregated data from the 697 individual outlet entities that comprise it and enables a single 698 point of control for all the individual outlet entities. 700 2.11. Industrial Automation Networks 702 Energy consumption statistics in the industrial sector are 703 staggering. The industrial sector alone consumes about half of 704 the world's total delivered energy, making it the largest end- 705 use sector. Thus, the need for optimization of energy usage in 706 this sector is natural. 707 Industrial facilities consume energy in process loads, and in 708 non-process loads. 709 The essential properties of this use case are: 711 . Target devices: Devices used in industrial automation 712 . How powered: Any method. 713 . Reporting: Currently, CIP protocol is currently used for 714 reporting energy for these devices 716 2.12. Printers 718 This use case describes the scenario of energy monitoring and 719 management of Printer devices. 721 Printers in this use case stand in for all imaging equipment, 722 also including multi-function devices (MFDs), copiers, scanners, 723 fax machines, and mailing machines. Energy use of printers has 724 been an industry concern for several decades, and they usually 725 have sophisticated power management with a variety of low-power 726 modes, particularly for managing energy-intensive thermo- 727 mechanical components. Printers also have long made extensive 728 use of SNMP for end-user system interaction and for management 729 generally, and cross-vendor management systems are available 730 today to manage fleets of printers in enterprises. Power 731 consumption during active modes can vary widely, with high peak 732 levels. 734 Printers today can expose detailed power state information, 735 distinct from operational state information, with some printers 736 reporting transition states between stable long-term states. 737 Many also support active setting of power states, and setting of 738 policies such as delay times when no activity will cause 739 automatic transition to a lower power mode. Other features 740 include reporting on components of imaging equipment, counters 741 for state transitions, and typical power levels by state, 742 scheduling, and events/alarms. 744 Some large printers also have a "Digital Front End" which is a 745 computer that performs functions on behalf of the physical 746 imaging system. These will typically have their own presence on 747 the network and are sometimes separately powered. 749 There are some unique characteristics of Printers from the point 750 of view energy monitoring. While the printer is not in use, 751 there are timer based low power states (sleep, stand-by), which 752 consume very little power. On the other hand, while the printer 753 is printing or copying the cylinder needs to be heated so that 754 power consumption is quite high but only for a short period of 755 time (duration of the print job). Given this work load, periodic 756 polling of energy consumption would not suffice. 758 Target Devices: All imaging equipment. 760 How Powered: Typically via mains AC from a wall outlet 762 Reporting: Devices report for themselves 764 2.13. Off-Grid Devices 766 This use case concerns self-contained devices that use energy 767 but are not connected to an infrastructure power delivery grid. 768 These devices typically scavenge energy from environmental 769 sources such as solar energy or wind power. The device generally 770 contains a closely coupled combination of 772 . power scavenging or generation component(s) 773 . power storage component(s) (e.g., battery) 774 . power consuming component(s) 776 With scavenged power, the energy input is often dependent on the 777 random variations of the weather. These devices therefore 778 require energy management both for internal control and remote 779 reporting of their state. In order to optimize the performance 780 of these devices and minimize the costs of the generation and 781 storage components, it is desirable to vary the activity level, 782 and, hopefully, the energy requirements of the consuming 783 components in order to make best use of the available stored and 784 instantaneously generated energy. With appropriate energy 785 management, the overall device can be optimized to deliver an 786 appropriate level of service without over provisioning the 787 generation and storage components. 789 In many cases these devices are expected to operate 790 autonomously, as continuous communications for the purposes of 791 remote control is either impossible or would result in excessive 792 power consumption. Non continuous polling requires the ability 793 to store and access later the information collected while the 794 communication was not possible. 796 Target Devices: Remote network devices (mobile network) that 797 consume and produce energy 799 How Powered: Can be battery powered or using natural energy 800 sources 802 Reporting: Devices report their power usage but only 803 occasionally. 805 2.14. Demand/Response 807 Demand/Response from the utility or grid is a common theme that 808 spans across some of the use cases. In some situations, in 809 response to time-of-day fluctuation of energy costs or sudden 810 energy shortages due power outages, it may be important to 811 respond and reduce the energy consumption of the network. 812 From EMAN use case perspective, the demand/response scenario can 813 apply to a Data Center or a Building or a residential home. As a 814 first step, it may be important to monitor the energy 815 consumption in real-time of a Data center or a building or home 816 which is already discussed in the previous use cases. Then based 817 on the potential energy shortfall, the Energy Management System 818 (EMS) could formulate a suitable response, i.e., the EMS could 819 shut down some selected devices that may be considered 820 discretionary or uniformly reduce the power supplied to all 821 devices. For multi-site data centers it may be possible to 822 formulate policies such as follow-the-moon type of approach, by 823 scheduling the mobility of VMs across Data centers in different 824 geographical locations. 826 2.15. Power Capping 828 Power capping is a technique to limit the total power 829 consumption of a server. This technique can be useful for power 830 limited data centers. Based on workload measurements, the server 831 can choose the optimal power state of the server in terms of 832 performance and power consumption. When the server operates at 833 less than the power supply capacity, it runs at full speed. When 834 the server power would be greater than the power supply 835 capacity, it runs at a slower speed so that its power 836 consumption matches the available power supply capacity. This 837 gives vendors the option to use smaller, cost-effective power 838 supplies that allow real world workloads to run at nominal 839 frequency. 841 3. Use Case Patterns 843 The use cases presented above can be abstracted to the following 844 broad patterns. 846 3.1. Metering 848 -energy objects which have capability for internal metering 849 - electrical devices which are metered by an external device 851 3.2. Metering and Control 853 - entities objects that do not supply power, butcan perform only 854 power metering for other devices 856 - entities objects that do not supply power, can perform both 857 metering and control for other devices 859 3.3. Power Supply, Metering and Control 861 - entities devices that supply power for other devices but do 862 not perform power metering for those devices 864 - entities that supply power for other devices and also perform 865 power metering 867 - entities supply power for other devices and also perform power 868 metering and control for other devices 870 3.4. Multiple power sources 872 - entities that have multiple power sources and metering and 873 control is performed by one source 875 - entities that have multiple power sources and metering is 876 performed by one source and control another source 878 4. Relationship of EMAN to other Standards 880 EMAN as a framework is tied to other standards and efforts that 881 deal with energy. Existing standards are leveraged when 882 possible. EMAN helps enable adjacent technologies such as Smart 883 Grid. 885 The standards most relevant and applicable to EMAN are listed 886 below with a brief description of their objectives, the current 887 state and how that standard can be applied to EMAN. 889 4.1. Data Model and Reporting 891 4.1.1. IEC - CIM 893 The International Electro-technical Commission (IEC) has 894 developed a broad set of standards for power management. Among 895 these, the most applicable to EMAN is IEC 61850,a standard for 896 the design of electric utility automation. The abstract data 897 model defined in 61850 is built upon and extends the Common 898 Information Model (CIM). The complete 61850 CIM model includes 899 over a hundred object classes and is widely used by utilities 900 worldwide. 902 This set of standards was originally conceived to automate 903 control of a substation (facilities which transfer electricity 904 from the transmission to the distribution system). While the 905 original domain of 61850 is substation automation, the extensive 906 data model has been widely used in other domains, including 907 Energy Management Systems (EMS). 909 IEC TC57 WG19 is an ongoing working group to harmonize the CIM 910 data model and 61850 standards. 912 Concepts from IEC Standards have been reused in the EMAN WG 913 drafts. In particular, AC Power Quality measurements have been 914 reused from IEC 61850-7-4. The concept of Accuracy Classes for 915 measurement of power and energy has been reused IEC 62053-21 and 916 IEC 62053-22. 918 4.1.2. DMTF 920 The Distributed Management Task Force (DMTF)[DMTF] has 921 standardized management solutions for managing servers and PCs, 922 including power-state configuration and management of elements 923 in a heterogeneous environment. These specifications provide 924 physical, logical and virtual system management requirements for 925 power-state control. 927 The EMAN standard references the DMTF Power Profile and Power 928 State Series. 930 4.1.2.1. Common Information Model Profiles 932 The DMTF uses CIM-based (Common Information Model) 'Profiles' to 933 represent and manage power utilization and configuration of 934 managed elements (note that this is not the 61850 CIM). Key 935 profiles for energy management are 'Power Supply' (DSP 1015), 936 'Power State' (DSP 1027) and 'Power Utilization Management' (DSP 937 1085).These profiles define monitoring and configuration of a 938 Power Managed Element's static and dynamic power saving modes, 939 power allocation limits and power states, among other features. 941 Reduced power modes can be established as static or dynamic. 942 Static modes are fixed policies that limit power use or 943 utilization. Dynamic power saving modes rely upon internal 944 feedback to control power consumption. 946 Power states are eight named operational and non operational 947 levels. These are On, Sleep-Light, Sleep-Deep, Hibernate, Off- 948 Soft, and Off-Hard. Power change capabilities provide 949 immediate, timed interval, and graceful transitions between on, 950 off, and reset power states. Table 3 of the Power State Profile 951 defines the correspondence between the ACPI and DMTF power state 952 models, although it is not necessary for a managed element to 953 support ACPI. Optionally, a TransitingToPowerState property can 954 represent power state transitions in progress. 956 4.1.2.2. DASH 958 DMTF DASH (DSP0232) (Desktop And Mobile Architecture for System 959 Hardware) addresses managing heterogeneous desktop and mobile 960 systems (including power) via in-band and out-of-band 961 communications. DASH provides management and control of managed 962 elements like power, CPU, etc. using the DMTF's WS-Management 963 web services and CIM data model. 965 Both in service and out-of-service systems can be managed with 966 the DASH specification in a fully secured remote environment. 967 Full power lifecycle management is possible using out-of-band 968 management. 970 4.1.3. ODVA 972 The Open DeviceNet Vendors Association (ODVA) is an association 973 for industrial automation companies and defines the Common 974 Industrial Protocol (CIP). Within ODVA, there is a special 975 interest group focused on energy. 977 There are many similar concepts between the ODVA and EMAN 978 frameworks towards monitoring and management of energy aware 979 devices. In particular, one of the concepts being considered 980 different energy meters based on if the device consumes 981 electricity or produces electricity or a passive device. 983 The Open DeviceNet Vendors Association (ODVA) is developing an 984 energy management framework for the industrial sector. There 985 are synergies between the ODVA and EMAN approaches to energy 986 management. 988 ODVA defines a three-part approach towards energy management: 989 awareness of energy usage, consuming energy more efficiently, 990 and exchanging energy with the utility or others. Energy 991 monitoring and management promote efficient consumption and 992 enable automating actions that reduce energy consumption. 994 The foundation of the approach is the information and 995 communication model for entities. An entity is a network- 996 connected, energy-aware device that has the ability to either 997 measure or derive its energy usage based on its native 998 consumption or generation of energy, or report a nominal or 999 static energy value. 1001 4.1.4. Ecma SDC 1003 The Ecma International committee on Smart Data Centre (TC38-TG2 1004 SDC [Ecma-SDC]) is in the process of defining semantics for 1005 management of entities in a data center such as servers, 1006 storage, and network equipment. It covers energy as one of many 1007 functional resources or attributes of systems for monitoring and 1008 control. It only defines messages and properties, and does not 1009 reference any specific protocol. Its goal is to enable 1010 interoperability of such protocols as SNMP, BACNET, and HTTP by 1011 ensuring a common semantic model across them. Four power states 1012 are defined, Off, Sleep, Idle and Active. The standard does not 1013 include actual power measurements in kWor kWh. 1015 The 14th draft of SDC process was published in March 2011 and 1016 the development of the standard is still underway. When used 1017 with EMAN, the SDC standard will provide a thin abstraction on 1018 top of the more detailed data model available in EMAN. 1020 4.1.5. IEEE-ISTO Printer Working Group (PWG) 1022 The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB 1023 modules for printer management and has recently defined a "PWG 1024 Power Management Model for Imaging Systems v1.0" [PWG5106.4] and 1025 a companion SNMP binding in the "PWG Imaging System Power MIB 1026 v1.0" [PWG5106.5]. This PWG model and MIB are harmonized with 1027 the DMTF CIM Infrastructure [DSP0004] and DMTF CIM Power State 1028 Management Profile [DSP1027] for power states and alerts. 1030 The PWG would like its MIBs to be harmonized as closely as 1031 possible with those from EMAN. The PWG covers many topics in 1032 greater detail than EMAN, as well as some that are specific to 1033 imaging equipment. The PWG also provides for vendor-specific 1034 extension states (i.e., beyond the standard DMTF CIM states.) 1036 4.1.6. ASHRAE 1038 In the U.S., there is an extensive effort to coordinate and 1039 develop standards related to the "Smart Grid". The Smart Grid 1040 Interoperability Panel, coordinated by the government's National 1041 Institute of Standards and Technology, identified the need for a 1042 building side information model (as a counterpart to utility 1043 models) and specified this in Priority Action Plan (PAP) 17. 1044 This was designated to be a joint effort by American Society of 1045 Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) 1046 and National Electrical Manufacturers Association (NEMA), both 1047 ANSI approved SDO's. The result is to be an information model, 1048 not a device level monitoring protocol. 1050 The ASHRAE effort addresses data used only within a building as 1051 well as data that may be shared with the grid, particularly as 1052 it relates to coordinating future demand levels with the needs 1053 of the grid. The model is intended to be applied to any 1054 building type, both residential and commercial. It is expected 1055 that existing protocols will be adapted to comply with the new 1056 information model, as would any new protocols. 1058 There are four basic types of entities in the model: generators, 1059 loads, meters, and energy managers. 1061 The metering part of this model overlaps with the EMAN framework 1062 to a large degree, though there are features unique to each. 1063 The load part speaks to control capabilities well beyond what 1064 EMAN covers. Details of generation and of the energy management 1065 function are outside of EMAN scope. 1067 A public review draft of the ASHRAE standard is expected soon, 1068 and at that point detailed comparison of the two models can be 1069 made. There are no apparent major conflicts between the two 1070 approaches, but there are likely areas where some harmonization 1071 is possible, and regardless, a description of the 1072 correspondences would be helpful to create. 1074 4.1.7. ZigBee 1076 The Zigbee Smart Energy 2.0 effort[ZIGBEE] focuses on wireless 1077 communication to appliances and lighting. It is intended to 1078 enable building energy management and enable direct load control 1079 by utilities. 1081 ZigBee protocols are intended for use in embedded applications 1082 requiring low data rates and low power consumption. ZigBee 1083 defines a general-purpose, inexpensive, self-organizing mesh 1084 network that can be used for industrial control, embedded 1085 sensing, medical data collection, smoke and intruder warning, 1086 building automation, home automation, etc. 1088 Zigbee is currently not an ANSI recognized SDO. 1090 The EMAN framework addresses the needs of IP-enabled networks 1091 through the usage of SNMP, while Zigbee looks for completely 1092 integrated and inexpensive mesh solution. 1094 4.2. Measurement 1096 4.2.1. ANSI C12 1098 The American National Standards Institute (ANSI) has defined a 1099 collection of power meter standards under ANSI C12. The primary 1100 standards include communication protocols (C12.18, 21 and 22), 1101 data and schema definitions (C12.19), and measurement accuracy 1102 (C12.20). European equivalent standards are provided by IEC 1103 62053-22.ANSI C12.20 defines accuracy classes for watt-hour 1104 meters. 1106 All of these standards are oriented toward the meter itself, and 1107 are therefore very specific and used by electricity distributors 1108 and producers. 1110 The EMAN standard references ANSI C12 accuracy classes. 1112 4.2.2. IEC62301 1114 IEC 62301, "Household electrical appliances Measurement of 1115 standby power", specifies a power level measurement procedure. 1117 While nominally for appliances and low-power modes, many aspects 1118 of it apply to other device types and modes and it is commonly 1119 referenced in test procedures for energy using products. 1121 While the standard is intended for laboratory measurements of 1122 devices in controlled conditions, many aspects of it are 1123 informative to those implementing measurement in products that 1124 ultimately report via EMAN. 1126 4.3. Other 1128 4.3.1. ISO 1130 The ISO [ISO] is developing an energy management standard, ISO 1131 50001, to complement ISO 9001 for quality management, and ISO 1132 14001 for environment management. The intent of the framework is 1133 to facilitate the creation of energy management programs for 1134 industrial, commercial and other entities. The standard defines 1135 a process for energy management at an organization level. It 1136 does not define the way in which devices report energy and 1137 consume energy. 1139 EMAN is complementary to ISO 9001. 1141 ISO 50001 is based on the common elements found in all of ISO's 1142 management system standards, assuring a high level of 1143 compatibility with ISO 9001 (quality management) and ISO 14001 1144 (environmental management). ISO 50001 benefits includes: 1146 o Integrating energy efficiency into management practices and 1147 throughout the supply chain 1148 o Energy management best practices and good energy management 1149 behaviors 1150 o benchmarking, measuring, documenting, and reporting energy 1151 intensity improvements and their projected impact on 1152 reductions in greenhouse gas (GHG) emissions 1153 o Evaluating and prioritizing the implementation of new energy- 1154 efficient technologies 1156 ISO 50001 has been developed by ISO project committee ISO/PC 1157 242, Energy management. 1159 4.3.2. EnergyStar 1161 The US Environmental Protection Agency (EPA) and US Department 1162 of Energy (DOE) jointly sponsor the Energy Star program [ESTAR]. 1163 The program promotes the development of energy efficient 1164 products and practices. 1166 To qualify as Energy Star, products must meet specific energy 1167 efficiency targets. The Energy Star program also provides 1168 planning tools and technical documentation to encourage more 1169 energy efficient building design. Energy Star is a program; it 1170 is not a protocol or standard. 1172 For businesses and data centers, Energy Star offers technical 1173 support to help companies establish energy conservation 1174 practices. Energy Star provides best practices for measuring 1175 current energy performance, goal setting, and tracking 1176 improvement. The Energy Star tools offered include a rating 1177 system for building performance and comparative benchmarks. 1179 There is no immediate link between EMAN and EnergyStar, one 1180 being a protocol and the other a set of recommendations to 1181 develop energy efficient products. However, Energy Star could 1182 include EMAN standards in specifications for future products, 1183 either as required or rewarded with some benefit. 1185 4.3.3. SmartGrid 1187 The Smart Grid standards efforts underway in the United States 1188 are overseen by the US National Institute of Standards and 1189 Technology [NIST].NIST is responsible for coordinating a public- 1190 private partnership with key energy and consumer stakeholders in 1191 order to facilitate the development of smart grid standards. The 1192 NIST smart grid standards activities are monitored and 1193 facilitated by the SGIP (Smart Grid Interoperability Panel). 1194 This group has working groups for specific topics including 1195 homes, commercial buildings, and industrial facilities as they 1196 relate to the grid. 1198 When a working group detects a standard or technology gap, the 1199 team seeks approval from the SGIP for the creation of a Priority 1200 Action Plan (PAP), a private-public partnership to close the 1201 gap. There are currently 17 PAPs. PAP 17 is discussed in 1202 section 4.1.6. 1204 PAP 10 addresses "Standard Energy Usage Information". 1206 Smart Grid standards will provide distributed intelligence in 1207 the network and allow enhanced load shedding. For example, 1208 pricing signals will enable selective shutdown of non critical 1209 activities during peak-load pricing periods. These actions can 1210 be effected through both centralized and distributed management 1211 controls. 1213 There is an obvious functional link between SmartGrid and EMAN 1214 in the form of demand response, even if the EMAN framework does 1215 not take any specific step toward SmartGrid communication. 1217 5. Limitations 1219 EMAN Framework shall address the needs of energy monitoring in 1220 terms of measurement and, considers limited control capabilities 1221 of energy monitoring of networks. 1223 EMAN does not create a new protocol stack, but rather defines a 1224 data and information model useful for measuring and reporting 1225 energy and other metrics over SNMP. 1227 The EMAN framework does not address questions regarding 1228 SmartGrid, electricity producers, and distributors even if there 1229 is obvious link between them. 1231 6. Security Considerations 1233 EMAN shall use SNMP protocol for energy monitoring and thus has 1234 the functionality of SNMP's security capabilities. SNMPv3 1235 [RFC3411] provides important security features such as 1236 confidentiality, integrity, and authentication. 1238 7. IANA Considerations 1240 This memo includes no request to IANA. 1242 8. Acknowledgements 1244 The authors would like to thank Jeff Wheeler, Benoit Claise, 1245 Juergen Quittek, Chris Verges, John Parello, and Matt Laherty, 1246 for their valuable contributions. 1248 The authors would like to thank Georgios Karagiannis for use 1249 case involving energy neutral homes, Elwyn Davies for off-grid 1250 electricity systems, and Kerry Lynn for the comment on the 1251 Demand/Response scenario. 1253 9. Open Issues 1255 "EDITOR NOTE: use the latest definition from draft-parello-eman- 1256 definitions" 1258 OPEN ISSUE 1: Relevant IEC standards for application for EMAN 1259 Applicability Statement document can provide guidance on the 1260 issue of what is appropriate standard used by EMAN 1262 IEC 61850-7-4 has been extensively used in EMAN WG documents. 1263 The other IEC documents referred for possible use are IEC 1264 61000-4-30, IEC 62053-21 and IEC 62301. 1266 There is feedback that IEC 61850-7-4 applies only to sub- 1267 stations ? 1269 OPEN ISSUE 2: Should review ASHRAE SPC 201P standard when it is 1270 released for public review 1272 . Need to review ASHRAE information model and the use cases 1273 and how it relates to EMAN 1275 OPEN ISSUE 3: Review ALL requirements to ensure that they can be 1276 traced to a use case 1277 . Missing is an use case for power quality 1279 OPEN ISSUE 4: Question for the WG. Should we have unique use 1280 cases that introduce specific requirements ? or can there be 1281 some overlap between use cases ? 1283 Any use cases out of scope scenarios ? 1285 10. References 1287 10.1. Normative References 1289 [RFC3411] An Architecture for Describing Simple Network 1290 Management Protocol (SNMP) Management Frameworks, RFC 1291 3411, December 2002. 1293 10.2. Informative References 1295 [DASH] "Desktop and mobile Architecture for System Hardware", 1296 http://www.dmtf.org/standards/mgmt/dash/ 1298 [NIST] http://www.nist.gov/smartgrid/ 1300 [Ecma-SDC] Ecma TC38 / SDC Task Group, "Smart Data Centre 1301 Resource Monitoring and Control (DRAFT)", March 2011. 1303 [ENERGY] http://en.wikipedia.org/wiki/Kilowatt_hour 1305 [EMAN-AS] Tychon, E., B. Schoening,MouliChandramouli, Bruce 1306 Nordman, "Energy Management (EMAN) Applicability 1307 Statement", draft-tychon-eman-applicability-statement- 1308 04.txt, work in progress, October 2011. 1310 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 1311 M. Chandramouli, "Requirements for Energy Management ", 1312 draft-ietf-eman-requirements-04 (work in progress),July 1313 2011. 1315 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 1316 Quittek, J. and B. Claise "Energy and Power Monitoring 1317 MIB ", draft-ietf-eman-monitoring-mib-00,August 2011. 1319 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 1320 energy-aware-mib-02", work in progress, July 2011. 1322 [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. 1323 Quittek, "Energy Management Framework", draft-ietf- 1324 eman-framework-02 ,July 2011. 1326 [EMAN-BATTERY-MIB] Quittek, J., Winter, R., and T. Dietz, 1327 "Definition of Managed Objects for Battery Monitoring" 1328 draft-ietf-eman-battery-mib-02.txt, July 2011. 1330 [EMAN-DEF] J. Parello"Energy Management Terminology", draft- 1331 parello-eman-definitions-03 1333 [DMTF] "Power State Management ProfileDMTFDSP1027 Version 2.0" 1334 December2009. 1335 http://www.dmtf.org/sites/default/files/standards/docum 1336 ents/DSP1027_2.0.0.pdf 1338 [ESTAR] http://www.energystar.gov/ 1340 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1434 1342 [SGRID] http://collaborate.nist.gov/twiki- 1343 sggrid/bin/view/SmartGrid/SGIPWorkingGroupsAndCommittee 1344 s 1346 [ASHRAE] http://collaborate.nist.gov/twiki- 1347 sggrid/bin/view/SmartGrid/PAP17Information 1349 [PAP17] http://collaborate.nist.gov/twiki- 1350 sggrid/bin/view/SmartGrid/PAP17FacilitySmartGridInforma 1351 tionStandard 1353 [ZIGBEE] http://www.zigbee.org/ 1355 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1337 1357 [DSP0004] DMTF Common Information Model (CIM) Infrastructure, 1358 DSP0004, May 2009. 1359 http://www.dmtf.org/standards/published_documents/DSP00 1360 04_2.5.0.pdf 1362 [DSP1027] DMTF Power State Management Profile, DSP1027, December 1363 2009. 1364 http://www.dmtf.org/standards/published_documents/DSP10 1365 27_2.0.0.pdf 1367 [PWG5106.4]IEEE-ISTO PWG Power Management Model for Imaging 1368 Systems v1.0, PWG Candidate Standard 5106.4-2011, 1369 February 2011.ftp://ftp.pwg.org/pub/pwg/candidates/cs- 1370 wimspower10-20110214-5106.4.mib 1372 [PWG5106.5] IEEE-ISTO PWG Imaging System Power MIB v1.0, PWG 1373 Candidate Standard 5106.5-2011, February 2011. 1375 [IEC62301] International Electrotechnical Commission, "IEC 62301 1376 Household electrical appliances Measurement of standby 1377 power", Edition 2.0, 2011. 1379 Authors' Addresses 1381 Emmanuel Tychon 1382 Cisco Systems, Inc. 1383 De Keleetlaan, 6A 1384 B1831 Diegem 1385 Belgium 1386 Email: etychon@cisco.com 1388 Brad Schoening 1389 44 Rivers Edge Drive 1390 Little Silver, NJ 07739 1391 USA 1392 Email:brad@bradschoening.com 1394 MouliChandramouli 1395 Cisco Systems, Inc. 1396 Sarjapur Outer Ring Road 1397 Bangalore, 1398 India 1399 Phone: +91 80 4426 3947 1400 Email: moulchan@cisco.com 1402 Bruce Nordman 1403 Lawrence Berkeley National Laboratory 1404 1 Cyclotron Road, 90-4000 1405 Berkeley 94720-8136 1406 USA 1408 Phone: +1 510 486 7089 1409 Email: bnordman@lbl.gov