idnits 2.17.1 draft-ietf-eman-applicability-statement-11.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 28 longer pages, the longest (page 1) being 62 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 51 instances of too long lines in the document, the longest one being 5 characters in excess of 72. == 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 (May 12, 2015) is 3266 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC761' is mentioned on line 182, but not defined ** Obsolete undefined reference: RFC 761 (Obsoleted by RFC 793, RFC 7805) == Missing Reference: 'RFC7460' is mentioned on line 1119, but not defined == Missing Reference: 'RFC7461' is mentioned on line 1119, but not defined == Unused Reference: 'EMAN-MONITORING-MIB' is defined on line 1175, but no explicit reference was found in the text == Unused Reference: 'EMAN-AWARE-MIB' is defined on line 1180, but no explicit reference was found in the text -- No information found for draft-ietf-eman-monitoring-mib - is the name correct? == Outdated reference: A later version (-20) exists of draft-ietf-eman-battery-mib-17 Summary: 2 errors (**), 0 flaws (~~), 9 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Energy Management Working Group Brad Schoening 3 Internet Draft Independent Consultant 4 Intended status: Informational Mouli Chandramouli 5 Expires: November 12, 2015 Cisco Systems Inc. 6 Bruce Nordman 7 Lawrence Berkeley National Laboratory 8 May 12, 2015 10 Energy Management (EMAN) Applicability Statement 11 draft-ietf-eman-applicability-statement-11 13 Abstract 15 The objective of Energy Management (EMAN) is to provide an 16 energy management framework for networked devices. This 17 document presents the applicability of the EMAN information 18 model in a variety of scenarios with cases and target devices. 19 These use cases are useful for identifying requirements for the 20 framework and MIBs. Further, we describe the relationship of 21 the EMAN framework to relevant other energy monitoring standards 22 and architectures. 24 Status of This Memo 26 This Internet-Draft is submitted to IETF in full conformance 27 with the provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet 30 Engineering Task Force (IETF), its areas, and its working 31 groups. Note that other groups may also distribute working 32 documents as Internet-Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six 35 months and may be updated, replaced, or obsoleted by other 36 documents at any time. It is inappropriate to use Internet- 37 Drafts as reference material or to cite them other than as "work 38 in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html 46 This Internet-Draft will expire on November 12, 2015. 48 Copyright Notice 50 Copyright (c) 2015 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described 60 in Section 4.e of the Trust Legal Provisions and are provided 61 without warranty as described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction ................................................. 3 66 1.1. Energy Management Overview ............................... 4 67 1.2. EMAN Document Overview ................................... 4 68 1.3. Energy Measurement ....................................... 5 69 1.4. Energy Management ........................................ 5 70 1.5. EMAN Framework Application ............................... 6 71 2. Scenarios and Target Devices ................................. 6 72 2.1. Network Infrastructure Energy Objects .................... 6 73 2.2. Devices Powered and Connected by a Network Device ........ 7 74 2.3. Devices Connected to a Network ........................... 8 75 2.4. Power Meters ............................................. 9 76 2.5. Mid-level Managers ...................................... 10 77 2.6. Non-residential Building System Gateways ................ 11 78 2.7. Home Energy Gateways .................................... 11 79 2.8. Data Center Devices ..................................... 12 80 2.9. Energy Storage Devices .................................. 13 81 2.10. Industrial Automation Networks ......................... 14 82 2.11. Printers ............................................... 14 83 2.12. Demand Response ........................................ 15 84 3. Use Case Patterns ........................................... 16 85 3.1. Metering ................................................ 16 86 3.2. Metering and Control .................................... 16 87 3.3. Power Supply, Metering and Control ...................... 16 88 3.4. Multiple Power Sources .................................. 16 89 4. Relationship of EMAN to Other Standards ..................... 16 90 4.1. Data Model and Reporting ................................ 17 91 4.1.1. IEC - CIM........................................ 17 92 4.1.2. DMTF............................................. 17 93 4.1.3. ODVA............................................. 18 94 4.1.4. Ecma SDC......................................... 19 95 4.1.5. PWG.............................................. 19 96 4.1.6. ASHRAE........................................... 20 97 4.1.7. ANSI/CEA......................................... 21 98 4.1.8. ZigBee........................................... 21 99 4.2. Measurement ............................................. 22 100 4.2.1. ANSI C12......................................... 22 101 4.2.2. IEC 62301........................................ 22 102 4.3. Other ................................................... 22 103 4.3.1. ISO.............................................. 22 104 4.3.2. Energy Star...................................... 23 105 4.3.3. Smart Grid....................................... 24 106 5. Limitations ................................................. 24 107 6. Security Considerations ..................................... 25 108 7. IANA Considerations ......................................... 25 109 8. Acknowledgements ............................................ 25 110 9. References .................................................. 25 111 9.1. Normative References .................................... 25 112 9.2. Informative References .................................. 25 114 1. Introduction 116 The focus of the Energy Management (EMAN) framework is energy 117 monitoring and management of energy objects [RFC7326]. The 118 scope of devices considered are network equipment and their 119 components, and devices connected directly or indirectly to 120 the network. The EMAN framework enables monitoring of 121 heterogeneous devices to report their energy consumption and, 122 if permissible, control. There are multiple scenarios where 123 this is desirable, particularly considering the increased 124 importance of limiting consumption of finite energy resources 125 and reducing operational expenses. 127 The EMAN framework [RFC7326] describes how energy information 128 can be retrieved from IP-enabled devices using Simple Network 129 Management Protocol (SNMP), specifically, Management Information 130 Base (MIBs) for SNMP. 132 This document describes typical applications of the EMAN 133 framework, as well as its opportunities and limitations. It 134 also reviews other standards that are similar in part to EMAN 135 but address different domains, describing how those other 136 standards relate to the EMAN framework. 138 The rest of the document is organized as follows. Section 2 139 contains a list of use cases or network scenarios that EMAN 140 addresses. Section 3 contains an abstraction of the use case 141 scenarios to distinct patterns. Section 4 deals with other 142 standards related and applicable to EMAN. 144 1.1. Energy Management Overview 146 EMAN addresses the electrical energy consumed by devices 147 connected to a network. A first step to increase the energy 148 efficiency in networks and the devices attached to the network 149 is to enable energy objects to report their energy usage over 150 time. The EMAN framework addresses this problem with an 151 information model for electrical equipment: energy object 152 identification, energy object context, power measurement, and 153 power characteristics. 155 The EMAN framework defines SNMP MIB modules based on the 156 information model. By implementing these SNMP MIB modules, an 157 energy object can report its energy consumption according to the 158 information model. Based on the information model, the MIB 159 drafts specify SNMP MIB modules, but it is equally possible to 160 use other mechanisms such as YANG module, NETCONF, etc. 162 In that context, it is important to distinguish energy objects 163 that can only report their own energy usage from devices that 164 can also collect and aggregate energy usage of other energy 165 objects. 167 1.2. EMAN Document Overview 169 The EMAN work consists of the following Standard Track and 170 Informational documents in the area of energy management. 172 Applicability Statement (this document) 174 Requirements [EMAN-REQ]: This document presents requirements 175 of energy management and the scope of the devices considered. 177 Framework [RFC7326]: This document defines a framework for 178 providing energy management for devices within or connected to 179 communication networks, and lists the definitions for the 180 common terms used in these documents. 182 Energy Object Context MIB [RFC761]: This document defines a MIB 183 module that characterizes a device's identity, context and 184 relationships to other entities. 186 Monitoring and Control MIB [RFC7460]: This document defines a MIB 187 module for monitoring the power and energy consumption of a device. 189 The MIB module contains an optional module for metrics 190 metrics associated with power characteristics. 192 Battery MIB [EMAN-BATTERY-MIB]: This document defines a MIB 193 module for monitoring characteristics of an internal battery. 195 1.3. Energy Measurement 197 It is increasingly common for today's smart devices to measure 198 and report their own energy consumption. Intelligent power 199 strips and some Power over Ethernet (PoE) switches can meter 200 consumption of connected devices. However, when managed and 201 reported through proprietary means, this information is 202 difficult to view at the enterprise level. 204 The primary goal of the EMAN information model is to enable 205 reporting and management within a standard framework that is 206 applicable to a wide variety of end devices, meters, and 207 proxies. This enables a management system to know who's 208 consuming what, when, and how by leveraging existing networks, 209 across various equipment, in a unified and consistent manner. 211 Because energy objects may both consume energy and provide 212 energy to other devices, there are three types of energy 213 measurement: energy input to a device, energy supplied to other 214 devices, and net (resultant) energy consumed (the difference 215 between energy input and supplied). 217 1.4. Energy Management 219 The EMAN framework provides mechanisms for energy control in 220 addition to passive monitoring. There are many cases where 221 active energy control of devices is desirable, such during low 222 device utilization or peak electrical price periods. 224 Energy control can be as simple as controlling on/off states. In 225 many cases, however, energy control requires understanding the 226 energy object context. For instance, in commercial building 227 during non-business hours, some phones must remain available in 228 case of emergency and office cooling is not usually turned off 229 completely, but the comfort level is reduced. 231 Energy object control therefore requires flexibility and support 232 for different polices and mechanisms: from centralized 233 management by an energy management system, to autonomous control 234 by individual devices, and alignment with dynamic demand 235 response mechanisms. 237 The EMAN framework power states can be used in demand response 238 scenarios. In response to time-of-day fluctuation of energy 239 costs or grid power shortages, network devices can respond and 240 reduce their energy consumption. 242 1.5. EMAN Framework Application 244 A Network Management System (NMS) is an entity that requests 245 information from compatible devices, typically using the SNMP 246 protocol. An NMS may implement many network management 247 functions, such as security or identity management. An NMS that 248 deals exclusively with energy is called an Energy Management 249 System (EnMS). It may be limited to monitoring energy use, or 250 it may also implement control functions. An EnMS collects 251 energy information for devices in the network. 253 Energy management can be implemented by extending existing SNMP 254 support with EMAN specific MIBs. SNMP provides an industry- 255 proven and well-known mechanism to discover, secure, measure, 256 and control SNMP-enabled end devices. The EMAN framework 257 provides an information and data model to unify access to a 258 large range of devices. 260 2. Scenarios and Target Devices 262 This section presents energy management scenarios that the EMAN 263 framework should solve. Each scenario lists target devices for 264 which the energy management framework can be applied, how the 265 reported-on devices are powered, and how the reporting or 266 control is accomplished. While there is some overlap between 267 some of the use cases, the use cases illustrate network 268 scenarios that the EMAN framework supports. 270 2.1. Network Infrastructure Energy Objects 272 This scenario covers the key use case of network devices and 273 their components. For a device aware of one or more components, 274 our information model supports monitoring and control at the 275 component level. Typically, the chassis draws power from one or 276 more sources and feeds its internal components. It is highly 277 desirable to have monitoring available for individual 278 components, such as line cards, processors, disk drives and 279 peripherals such as USB devices. 281 As an illustrative example, consider a switch with the following 282 grouping of sub-entities for which energy management could be 283 useful. 285 . Physical view: chassis (or stack), line cards, and service 286 modules of the switch. 287 . Component view: CPU, ASICs, fans, power supply, ports 288 (single port and port groups), storage, and memory. 290 The ENTITY-MIB [RFC6933] provides a containment model for 291 uniquely identifying the physical sub-components of network 292 devices. The containment information identifies whether one 293 Energy Object belongs to another Energy Object (e.g. a line-card 294 Energy Object contained in a chassis Energy Object). The 295 mapping table entPhysicalContainsTable has an index 296 entPhysicalChildIndex and the table entPhysicalTable has a MIB 297 object entPhysicalContainedIn which points to the containing 298 entity. 300 The essential properties of this use case are: 302 . Target devices: network devices such as routers and 303 switches as well as their components. 304 . How powered: typically by a Power Distribution Unit (PDU) 305 on a rack or from a wall outlet. The components of a 306 device are powered by the device chassis. 307 . Reporting: direct power measurement can be performed at a 308 device level. Components can report their power 309 consumption directly or the chassis/device can report on 310 behalf of some components. 312 2.2. Devices Powered and Connected by a Network Device 314 This scenario covers Power Sourcing Equipment (PSE) devices. A 315 PSE device (e.g. a PoE switch) provides power to a Powered 316 Device (PD) (e.g. a desktop phone) over a medium such as USB or 317 Ethernet [RFC3621]. For each port, the PSE can control the 318 power supply (switching it on and off) and usually meter actual 319 power provided. PDs obtain network connectivity as well as 320 power over a single connection so the PSE can determine which 321 device is associated with each port. 323 PoE ports on a switch are commonly connected to devices such as 324 IP phones, wireless access points, and IP cameras. The switch 325 needs power for its internal use and to supply power to PoE 326 ports. Monitoring the power consumption of the switch 327 (supplying device) and the power consumption of the PoE end- 328 points (consuming devices) is a simple use case of this 329 scenario. 331 This scenario illustrates the relationships between entities. 332 The PoE IP phone is powered by the switch. If there are many IP 333 phones connected to the same switch, the power consumption of 334 all the IP phones can be aggregated by the switch. 336 The essential properties of this use case are: 338 . Target devices: Power over Ethernet devices such as IP 339 phones, wireless access points, and IP cameras. 340 . How powered: PoE devices are connected to the switch port 341 which supplies power to those devices. 342 . Reporting: PoE device power consumption is measured and 343 reported by the switch (PSE) which supplies power. In 344 addition, some edge devices can support the EMAN framework. 346 This use case can be divided into two subcases: 348 a) The end-point device supports the EMAN framework, in which 349 case this device is an EMAN Energy Object by itself, with 350 its own UUID. The device is responsible for its own power 351 reporting and control. See the related scenario "Devices 352 Connected to a Network" below. 354 b) The end-point device does not have EMAN capabilities, and 355 the power measurement may not be able to be performed 356 independently, and is therefore only performed by the 357 supplying device. This scenario is similar to the "Mid- 358 level Manager" below. 360 In subcase (a) note that two power usage reporting mechanisms 361 for the same device are available: one performed by the PD 362 itself and one performed by the PSE. Device specific 363 implementations will dictate which one to use. 365 2.3. Devices Connected to a Network 367 This use case covers the metering relationship between an energy 368 object and the parent energy object to which it is connected, 369 while receiving power from a different source. 371 An example is a PC which has a network connection to a switch, 372 but draws power from a wall outlet. In this case, the PC can 373 report power usage by itself, ideally through the EMAN 374 framework. 376 The wall outlet to which the PC is plugged in can be unmetered 377 or metered, for example, by a Smart PDU. 379 a) If metered, the PC has a powered-by relationship to the Smart 380 PDU, and the Smart PDU acts as a "Mid-Level Manager". 382 b) If unmetered, or operating on batteries, the PC will report 383 its own energy usage as any other Energy Object to the switch, 384 and the switch may possibly provide aggregation. 386 These two cases are not mutually exclusive. 388 In terms of relationships between entities, the PC has a 389 powered-by relationship to the PDU and if the power consumption 390 of the PC is metered by the PDU, then there is a metered-by 391 relation between the PC and the PDU. 393 The essential properties of this use case are: 395 . Target devices: energy objects that have a network 396 connection, but receive power supply from another source. 397 . How powered: end-point devices (e.g. PCs) receive power 398 supply from the wall outlet (unmetered), a PDU (metered), 399 or can be powered autonomously (batteries). 400 . Reporting: devices can either measure and report the power 401 consumption directly via the EMAN framework, communicate it 402 to the network device (switch) and the switch can report 403 the device's power consumption via the EMAN framework, or 404 power can be reported by the PDU. 406 2.4. Power Meters 408 Some electrical devices are not equipped with instrumentation to 409 measure their own power and accumulated energy consumption. 410 External meters can be used to measure the power consumption of 411 such electrical devices as well as collections of devices. 413 Three types of external metering are relevant to EMAN: PDUs, 414 standalone meters, and utility meters. External meters can 415 measure consumption of a single device or a set of devices. 417 Power Distribution Units (PDUs) can have built-in meters for 418 each socket and can measure the power supplied to each device in 419 an equipment rack. PDUs typically have remote management 420 capabilities which can report and possibly control the power 421 supply of each outlet. 423 Standalone meters can be placed anywhere in a power distribution 424 tree and may measure all or part of the total. Utility meters 425 monitor and report accumulated power consumption of the entire 426 building. There can be sub-meters to measure the power 427 consumption of a portion of the building. 429 The essential properties of this use case are: 431 . Target devices: PDUs and meters. 432 . How powered: from traditional mains power but supplied 433 through a PDU or meter. 434 . Reporting: PDUs report power consumption of downstream 435 devices, usually a single device per outlet. Meters may 436 report for one or more devices and may require knowledge of 437 the topology to associate meters with metered devices. 439 Meters have metered-by relationships with devices, and may have 440 aggregation relationship between the meters and the devices for 441 which power consumption is accumulated and reported by the 442 meter. 444 2.5. Mid-level Managers 446 This use case covers aggregation of energy management data at 447 "mid-level managers" that can provide energy management 448 functions for themselves and associated devices. 450 A switch can provide energy management functions for all devices 451 connected to its ports, whether or not these devices are powered 452 by the switch or whether the switch provides immediate network 453 connectivity to the devices. Such a switch is a mid-level 454 manager, offering aggregation of power consumption data for 455 other devices. Devices report their EMAN data to the switch and 456 the switch aggregates the data for further reporting. 458 The essential properties of this use case: 460 . Target devices: devices which can perform aggregation; 461 commonly a switch or a proxy. 462 . How powered: mid-level managers are commonly powered by a 463 PDU or from a wall outlet but can be powered by any method. 464 . Reporting: the mid-level manager aggregates the energy data 465 and reports that data to an EnMS or higher mid-level 466 manager. 468 2.6. Non-residential Building System Gateways 470 This use case describes energy management of non-residential 471 buildings. Building Management Systems (BMS) have been in place 472 for many years using legacy protocols not based on IP. In these 473 buildings, a gateway can provide a proxy function between IP 474 networks and legacy building automation protocols. The gateway 475 provides an interface between the EMAN framework and relevant 476 building management protocols. 478 Due to the potential energy savings, energy management of 479 buildings has received significant attention. There are gateway 480 network elements to manage the multiple components of a building 481 energy management system such as Heating, Ventilation, and Air 482 Conditioning (HVAC), lighting, electrical, fire and emergency 483 systems, elevators, etc. The gateway device uses legacy 484 building protocols to communicate with those devices, collects 485 their energy usage, and reports the results. 487 The gateway performs protocol conversion and communicates via 488 RS-232/RS-485 interfaces, Ethernet interfaces, and protocols 489 specific to building management such as BACNET [ASHRAE], MODBUS 490 [MODBUS], or ZigBee [ZIGBEE]. 492 The essential properties of this use case are: 494 . Target devices: building energy management devices - HVAC 495 systems, lighting, electrical, fire and emergency systems. 496 . How powered: any method. 497 . Reporting: the gateway collects energy consumption of non- 498 IP systems and communicates the data via the EMAN 499 framework. 501 2.7. Home Energy Gateways 503 This use case describes the scenario of energy management of a 504 home. The home energy gateway is another example of a proxy 505 that interfaces with electrical appliances and other devices in 506 a home. This gateway can monitor and manage electrical 507 equipment (e.g. refrigerator, heating/cooling, or washing 508 machine) using one of the many protocols that are being 509 developed for residential devices. 511 Beyond simply metering, it's possible to implement energy saving 512 policies based on time of day, occupancy, or energy pricing from 513 the utility grid. The EMAN information model can be applied to 514 energy management of a home. 516 The essential properties of this use case are: 518 . Target devices: home energy gateway and smart meters in a 519 home. 520 . How powered: any method. 521 . Reporting: home energy gateway can collect power 522 consumption of device in a home and possibly report the 523 metering reading to the utility. 525 2.8. Data Center Devices 527 This use case describes energy management of a data center. 528 Energy efficiency of data centers has become a fundamental 529 challenge of data center operation, as data centers are big 530 energy consumers and have expensive infrastructure. The 531 equipment generates heat, and heat needs to be evacuated through 532 an HVAC system. 534 A typical data center network consists of a hierarchy of 535 electrical energy objects. At the bottom of the network 536 hierarchy are servers mounted on a rack; these are connected to 537 top-of-the-rack switches, which in turn are connected to 538 aggregation switches, and then to core switches. Power 539 consumption of all network elements, servers, and storage 540 devices in the data center should be measured. Energy 541 management can be implemented on different aggregation levels, 542 i.e., at the network level, Power Distribution Unit (PDU) level, 543 and/or server level. 545 Beyond the network devices, storage devices, and servers, data 546 centers contain UPSs to provide back-up power for the facility 547 in the event of a power outage. A UPS can provide backup power 548 for many devices in a data center for a finite period of time. 549 Energy monitoring of energy storage capacity is vital from a 550 data center network operations point of view. Presently, the 551 UPS MIB can be useful in monitoring the battery capacity, the 552 input load to the UPS, and the output load from the UPS. 553 Currently, there is no link between the UPS MIB and the ENTITY 554 MIB. 556 In addition to monitoring the power consumption of a data 557 center, additional power characteristics should be monitored. 558 Some of these are dynamic variations in the input power supply 559 from the grid referred to as power quality metrics. It can also 560 be useful to monitor how efficiently the devices utilize power. 562 Nameplate capacity of the data center can be estimated from the 563 nameplate ratings (the worst case possible power draw) of IT 564 equipment at a site. 566 The essential properties of this use case are: 568 . Target devices: IT devices in a data center, such as 569 network equipment, servers, and storage devices, as well as 570 power and cooling infrastructure. 571 . How powered: any method, but commonly by one or more PDUs. 572 . Reporting: devices may report on their own behalf, or for 573 other connected devices as described in other use cases. 575 2.9. Energy Storage Devices 577 Energy storage devices can have two different roles: one type 578 whose primary function is to provide power to another device 579 (e.g. a UPS), and one type with a different primary function, 580 but having energy storage as a component (e.g. a notebook). 581 This use case covers both. 583 The energy storage can be a conventional battery, or any other 584 means to store electricity such as a hydrogen cell. 586 An internal battery can be a back-up or an alternative source of 587 power to mains power. As batteries have a finite capacity and 588 lifetime, means for reporting the actual charge, age, and state 589 of a battery are required. An internal battery can be viewed as 590 a component of a device and so be contained within the device 591 from an ENTITY-MIB perspective. 593 Battery systems are often used in remote locations such as 594 mobile telecom towers. For continuous operation, it is 595 important to monitor the remaining battery life and raise an 596 alarm when this falls below a threshold. 598 The essential properties of this use case are: 600 . Target devices: devices that have an internal battery or 601 external storage. 602 . How powered: from batteries or other storage devices. 603 . Reporting: the device reports on its power delivered and 604 state. 606 2.10. Industrial Automation Networks 608 Energy consumption statistics in the industrial sector are 609 staggering. The industrial sector alone consumes about half of 610 the world's total delivered energy, and is a significant user of 611 electricity. Thus, the need for optimization of energy usage in 612 this sector is natural. 614 Industrial facilities consume energy in process loads and non- 615 process loads. 617 The essential properties of this use case are: 619 . Target devices: devices used in an industrial sector. 620 . How powered: any method. 621 . Reporting: the CIP protocol is commonly used for reporting 622 energy for these devices. 624 2.11. Printers 626 This use case describes the scenario of energy monitoring and 627 management of printers. Printers in this use case stand in for 628 all imaging equipment, including multi-function devices (MFDs), 629 scanners, fax machines, and mailing machines. 631 Energy use of printers has been a longstanding industry concern 632 and sophisticated power management is common. Printers often 633 use a variety of low-power modes, particularly for managing 634 energy-intensive thermo-mechanical components. Printers also 635 have long made extensive use of SNMP for end-user system 636 interaction and for management generally, with cross-vendor 637 management systems able to manage fleets of printers in 638 enterprises. Power consumption during active modes can vary 639 widely, with high peak usage levels. 641 Printers can expose detailed power state information, distinct 642 from operational state information, with some printers reporting 643 transition states between stable long-term states. Many also 644 support active setting of power states and policies such as 645 delay times, when inactivity automatically transitions the 646 device to a lower power mode. Other features include reporting 647 on components, counters for state transitions, typical power 648 levels by state, scheduling, and events/alarms. 650 Some large printers also have a "Digital Front End," which is a 651 computer that performs functions on behalf of the physical 652 imaging system. These typically have their own presence on the 653 network and are sometimes separately powered. 655 There are some unique characteristics of printers from the point 656 of view energy management. While the printer is not in use, 657 there are timer-based low power states, which consume little 658 power. On the other hand, while the printer is printing or 659 copying, the cylinder is heated so that power consumption is 660 quite high but only for a short period of time. Given this work 661 load, periodic polling of power levels alone would not suffice. 663 The essential properties of this use case are: 665 . Target devices: all imaging equipment. 666 . How powered: typically AC from a wall outlet. 667 . Reporting: devices report for themselves. 669 2.12. Demand Response 671 The theme of demand response from a utility grid spans across 672 several use cases. In some situations, in response to time-of- 673 day fluctuation of energy costs or sudden energy shortages due 674 power outages, it may be important to respond and reduce the 675 energy consumption of the network. 677 From the EMAN use case perspective, the demand response scenario 678 can apply to a data center, building or home. Real-time energy 679 monitoring is usually a prerequisite, so that during a potential 680 energy shortfall the EnMS can provide an active response. The 681 EnMS could shut down selected devices that are considered lower 682 priority or uniformly reduce the power supplied to a class of 683 devices. For multi-site data centers it may be possible to 684 formulate policies such as follow-the-sun type of approach, by 685 scheduling the mobility of VMs across data centers in different 686 geographical locations. 688 The essential properties of this use case are: 690 . Target devices: any device. 691 . How powered: traditional mains AC power. 692 . Reporting: real-time. 693 . Control: demand response based upon policy or priority. 695 3. Use Case Patterns 697 The use cases presented above can be abstracted to the following 698 broad patterns for energy objects. 700 3.1. Metering 702 - Energy objects which have capability for internal metering 703 - Energy objects which are metered by an external device 705 3.2. Metering and Control 707 - Energy objects that do not supply power, but can perform power 708 metering for other devices 710 - Energy objects that do not supply power, but can perform both 711 metering and control for other devices 713 3.3. Power Supply, Metering and Control 715 - Energy objects that supply power for other devices but do not 716 perform power metering for those devices 718 - Energy objects that supply power for other devices and also 719 perform power metering 721 - Energy objects that supply power for other devices and also 722 perform power metering and control for other devices 724 3.4. Multiple Power Sources 726 - Energy objects that have multiple power sources, with metering 727 and control performed by the same power source 729 - Energy objects that have multiple power sources supplying 730 power to the device with metering performed by one or more 731 sources and control performed by another source 733 4. Relationship of EMAN to Other Standards 735 The EMAN framework is tied to other standards and efforts that 736 address energy monitoring and control. EMAN leverages existing 737 standards when possible, and it helps enable adjacent 738 technologies such as Smart Grid. 740 The standards most relevant and applicable to EMAN are listed 741 below with a brief description of their objectives, the current 742 state, and how that standard relates to EMAN. 744 4.1. Data Model and Reporting 746 4.1.1. IEC - CIM 748 The International Electrotechnical Commission (IEC) has 749 developed a broad set of standards for power management. Among 750 these, the most applicable to EMAN is IEC 61850, a standard for 751 the design of electric utility automation. The abstract data 752 model defined in 61850 is built upon and extends the Common 753 Information Model (CIM). The complete 61850 CIM model includes 754 over a hundred object classes and is widely used by utilities 755 worldwide. 757 This set of standards were originally conceived to automate 758 control of a substation (a facility which transfer electricity 759 from the transmission to the distribution system). However, the 760 extensive data model has been widely used in other domains, 761 including Energy Management Systems (EnMS). 763 IEC TC57 WG19 is an ongoing working group with the objective to 764 harmonize the CIM data model and 61850 standards. 766 Several concepts from IEC Standards have been reused in the EMAN 767 drafts. In particular, AC Power Quality measurements have been 768 reused from IEC 61850-7-4. The concept of Accuracy Classes for 769 measurement of power and energy has been adapted from ANSI 770 C12.20 and IEC standards 62053-21 and 62053-22. 772 4.1.2. DMTF 774 The Distributed Management Task Force (DMTF) has defined a Power 775 State Management profile [DMTF DSP1027] for managing computer 776 systems using the DMTF's Common Information Model (CIM). These 777 specifications provide physical, logical, and virtual system 778 management requirements for power-state control services. The 779 DMTF standard does not include energy monitoring. 781 The Power State Management profile is used to describe and 782 manage the Power State of computer systems. This includes 783 controlling the Power State of an entity for entering sleep 784 mode, awakening, and rebooting. The EMAN framework references 785 the DMTF Power Profile and Power State Set. 787 4.1.2.1. Common Information Model Profiles 789 The DMTF uses CIM-based (Common Information Model) 'Profiles' to 790 represent and manage power utilization and configuration of 791 managed elements (note that this is not the 61850 CIM). Key 792 profiles for energy management are 'Power Supply' (DSP 1015), 793 'Power State' (DSP 1027), and 'Power Utilization Management' 794 (DSP 1085). These profiles define many features for the 795 monitoring and configuration of a Power Managed Element's static 796 and dynamic power saving modes, power allocation limits, and 797 power states. 799 Reduced power modes can be established as static or dynamic. 800 Static modes are fixed policies that limit power use or 801 utilization. Dynamic power saving modes rely upon internal 802 feedback to control power consumption. 804 Power states are eight named operational and non operational 805 levels. These are On, Sleep-Light, Sleep-Deep, Hibernate, Off- 806 Soft, and Off-Hard. Power change capabilities provide 807 immediate, timed interval, and graceful transitions between on, 808 off, and reset power states. Table 3 of the Power State Profile 809 defines the correspondence between the Advanced Configuration 810 and Power Interface [ACPI] and DMTF power state models, although 811 it is not necessary for a managed element to support ACPI. 812 Optionally, a TransitioningToPowerState property can represent 813 power state transitions in progress. 815 4.1.2.2. DASH 817 DMTF DASH [DASH] (Desktop And Mobile Architecture for System 818 Hardware) addresses managing heterogeneous desktop and mobile 819 systems (including power) via in-band and out-of-band 820 communications. DASH uses the DMTF's WS-Management web services 821 and CIM data model to manage and control resources such as 822 power, CPU, etc. 824 Both in-service and out-of-service systems can be managed with 825 the DASH specification in a fully secured remote environment. 826 Full power lifecycle management is possible using out-of-band 827 management. 829 4.1.3. ODVA 831 The Open DeviceNet Vendors Association (ODVA) is an association 832 for industrial automation companies that defines the Common 833 Industrial Protocol (CIP). Within ODVA, there is a special 834 interest group focused on energy and standardization and inter- 835 operability of energy-aware devices. 837 The ODVA is developing an energy management framework for the 838 industrial sector. There are synergies and similar concepts 839 between the ODVA and EMAN approaches to energy monitoring and 840 management. 842 ODVA defines a three-part approach towards energy management: 843 awareness of energy usage, energy efficiently, and the exchange 844 of energy with a utility or others. Energy monitoring and 845 management promote efficient consumption and enable automating 846 actions that reduce energy consumption. 848 The foundation of the approach is the information and 849 communication model for entities. An entity is a network- 850 connected, energy-aware device that has the ability to either 851 measure or derive its energy usage based on its native 852 consumption or generation of energy, or report a nominal or 853 static energy value. 855 4.1.4. Ecma SDC 857 The Ecma International standard on Smart Data Centre [Ecma-SDC] 858 defines semantics for management of entities in a data center 859 such as servers, storage, and network equipment. It covers 860 energy as one of many functional resources or attributes of 861 systems for monitoring and control. It only defines messages 862 and properties, and does not reference any specific protocol. 863 Its goal is to enable interoperability of such protocols as 864 SNMP, BACNET, and HTTP by ensuring a common semantic model 865 across them. Four power states are defined, Off, Sleep, Idle, 866 and Active. The standard does not include actual energy or 867 power measurements. 869 When used with EMAN, the SDC standard will provide a thin 870 abstraction on top of the more detailed data model available in 871 EMAN. 873 4.1.5. PWG 875 The IEEE-ISTO Printer Working Group (PWG) defines open standards 876 for printer related protocols, for the benefit of printer 877 manufacturers and related software vendors. The Printer WG 878 covers power monitoring and management of network printers and 879 imaging systems in the PWG Power Management Model for Imaging 880 Systems [PWG5106.4]. Clearly, these devices are within the 881 scope of energy management since they receive power and are 882 attached to the network. In addition, there is ample scope of 883 power management since printers and imaging systems are not used 884 that often. 886 The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB 887 modules for printer management and in particular a "PWG Power 888 Management Model for Imaging Systems v1.0" [PWG5106.4] and a 889 companion SNMP binding in the "PWG Imaging System Power MIB 890 v1.0" [PWG5106.5]. This PWG model and MIB are harmonized with 891 the DMTF CIM Infrastructure [DMTF DSP0004] and DMTF CIM Power 892 State Management Profile [DMTF DSP1027] for power states and 893 alerts. 895 These MIB modules can be useful for monitoring the power and 896 Power State of printers. The EMAN framework takes into account 897 the standards defined in the Printer Working Group. The PWG may 898 harmonize its MIBs with those from EMAN. The PWG covers many 899 topics in greater detail than EMAN, including those specific to 900 imaging equipment. The PWG also provides for vendor-specific 901 extension states (beyond the standard DMTF CIM states). 903 The IETF Printer MIB RFC3805 [RFC3805] has been standardized, 904 but, this MIB module does not address power management. 906 4.1.6. ASHRAE 908 In the U.S., there is an extensive effort to coordinate and 909 develop standards related to the "Smart Grid". The Smart Grid 910 Interoperability Panel, coordinated by the government's National 911 Institute of Standards and Technology, identified the need for a 912 building side information model (as a counterpart to utility 913 models) and specified this in Priority Action Plan (PAP) 17. 914 This was designated to be a joint effort by the American Society 915 of Heating, Refrigerating and Air-Conditioning Engineers 916 (ASHRAE) and the National Electrical Manufacturers Association 917 (NEMA), both ANSI approved SDO's. The result is to be an 918 information model, not a protocol. 920 The ASHRAE effort addresses data used only within a building as 921 well as data that may be shared with the grid, particularly as 922 it relates to coordinating future demand levels with the needs 923 of the grid. The model is intended to be applied to any 924 building type, both residential and commercial. It is expected 925 that existing protocols will be adapted to comply with the new 926 information model, as would new protocols. 928 There are four basic types of entities in the model: generators, 929 loads, meters, and energy managers. The metering part of the 930 model overlaps to a large degree with the EMAN framework, though 931 there are features unique to each. The load part speaks to 932 control capabilities well beyond what EMAN covers. Details of 933 generation and of the energy management function are outside of 934 EMAN scope. 936 A public review draft of the ASHRAE standard was released in 937 July, 2012. There are no apparent major conflicts between the 938 two approaches, but there are areas where some harmonization is 939 possible. 941 4.1.7. ANSI/CEA 943 The Consumer Electronics Association (CEA) has approved 944 ANSI/CEA-2047 [ANSICEA] as a standard data model for Energy 945 Usage Information. The primary purpose is to enable home 946 appliances and electronics to communicate energy usage 947 information over a wide range of technologies with pluggable 948 modules that contain the physical layer electronics. The 949 standard can be used by devices operating on any home network 950 including Wi-Fi, Ethernet, ZigBee, Z-Wave, and Bluetooth. The 951 Introduction to ANSI/CEA-2047 states that "this standard 952 provides an information model for other groups to develop 953 implementations specific to their network, protocol and 954 needs". It covers device identification, current power level, 955 cumulative energy consumption, and provides for reporting time- 956 series data. 958 4.1.8. ZigBee 960 The ZigBee Smart Energy Profile 2.0 (SEP) effort [ZIGBEE] 961 focuses on IP-based wireless communication to appliances and 962 lighting. It is intended to enable internal building energy 963 management and provide for bi-directional communication with the 964 power grid. 966 ZigBee protocols are intended for use in embedded applications 967 with low data rates and low power consumption. ZigBee defines a 968 general-purpose, inexpensive, self-organizing mesh network that 969 can be used for industrial control, embedded sensing, medical 970 data collection, smoke and intruder warning, building 971 automation, home automation, etc. 973 ZigBee is currently not an ANSI recognized SDO. 975 The EMAN framework addresses the needs of IP-enabled networks 976 through the usage of SNMP, while ZigBee provides for completely 977 integrated and inexpensive mesh solutions. 979 4.2. Measurement 981 4.2.1. ANSI C12 983 The American National Standards Institute (ANSI) has defined a 984 collection of power meter standards under ANSI C12. The primary 985 standards include communication protocols (C12.18, 21 and 22), 986 data and schema definitions (C12.19), and measurement accuracy 987 (C12.20). European equivalent standards are provided by IEC 988 62053-22 990 These very specific standards are oriented to the meter itself, 991 and are used by electricity distributors and producers. 993 The EMAN standard references ANSI C12.20 accuracy classes. 995 4.2.2. IEC 62301 997 IEC 62301, "Household electrical appliances Measurement of 998 standby power", [IEC62301] specifies a power level measurement 999 procedure. While nominally for appliances and low-power modes, 1000 its concepts apply to other device types and modes and it is 1001 commonly referenced in test procedures for energy using 1002 products. 1004 While the standard is intended for laboratory measurements of 1005 devices in controlled conditions, aspects of it are informative 1006 to those implementing measurement in products that ultimately 1007 report via EMAN. 1009 4.3. Other 1011 4.3.1. ISO 1013 The International Organization for Standardization (ISO) [ISO] 1014 is developing an energy management standard, ISO 50001, to 1015 complement ISO 9001 for quality management, and ISO 14001 for 1016 environmental management. The intent is to facilitate the 1017 creation of energy management programs for industrial, 1018 commercial, and other entities. The standard defines a process 1019 for energy management at an organizational level. It does not 1020 define the way in which devices report energy and consume 1021 energy. 1023 ISO 50001 is based on the common elements found in all of ISO's 1024 management system standards, assuring a high level of 1025 compatibility with ISO 9001 and ISO 14001. ISO 50001 benefits 1026 include: 1028 o Integrating energy efficiency into management practices and 1029 throughout the supply chain. 1030 o Energy management best practices and good energy management 1031 behaviors. 1032 o Benchmarking, measuring, documenting, and reporting energy 1033 intensity improvements and their projected impact on 1034 reductions in greenhouse gas (GHG) emissions. 1035 o Evaluating and prioritizing the implementation of new energy- 1036 efficient technologies. 1038 ISO 50001 has been developed by ISO project committee ISO PC 1039 242, Energy management. EMAN is complementary to ISO 9001. 1041 4.3.2. Energy Star 1043 The U.S. Environmental Protection Agency (EPA) and U.S. 1044 Department of Energy (DOE) jointly sponsor the Energy Star 1045 program [ESTAR]. The program promotes the development of energy 1046 efficient products and practices. 1048 To qualify as Energy Star, products must meet specific energy 1049 efficiency targets. The Energy Star program also provides 1050 planning tools and technical documentation to encourage more 1051 energy efficient building design. Energy Star is a program; it 1052 is not a protocol or standard. 1054 For businesses and data centers, Energy Star offers technical 1055 support to help companies establish energy conservation 1056 practices. Energy Star provides best practices for measuring 1057 current energy performance, goal setting, and tracking 1058 improvement. The Energy Star tools offered include a rating 1059 system for building performance and comparative benchmarks. 1061 There is no immediate link between EMAN and Energy Star, one 1062 being a protocol and the other a set of recommendations to 1063 develop energy efficient products. However, Energy Star could 1064 include EMAN standards in specifications for future products, 1065 either as required or rewarded with some benefit. 1067 4.3.3. Smart Grid 1069 The Smart Grid standards efforts underway in the United States 1070 are overseen by the U.S. National Institute of Standards and 1071 Technology [NIST]. NIST is responsible for coordinating a 1072 public-private partnership with key energy and consumer 1073 stakeholders in order to facilitate the development of Smart 1074 Grid standards. These activities are monitored and facilitated 1075 by the SGIP (Smart Grid Interoperability Panel). This group has 1076 working groups for specific topics including homes, commercial 1077 buildings, and industrial facilities as they relate to the grid. 1078 A stated goal of the group is to harmonize any new standard with 1079 the IEC CIM and IEC 61850. 1081 When a working group detects a standard or technology gap, the 1082 team seeks approval from the SGIP for the creation of a Priority 1083 Action Plan (PAP), a private-public partnership to close the 1084 gap. PAP 17 is discussed in section 4.1.6. 1086 PAP 10 addresses "Standard Energy Usage Information". Smart 1087 Grid standards will provide distributed intelligence in the 1088 network and allow enhanced load shedding. For example, pricing 1089 signals will enable selective shutdown of non-critical 1090 activities during peak price periods. Actions can be effected 1091 through both centralized and distributed management controls. 1093 There is an obvious functional link between Smart Grid and EMAN 1094 in the form of demand response, even though the EMAN framework 1095 itself does not address any coordination with the grid. As EMAN 1096 enables control, it can be used by an EnMS to accomplish demand 1097 response through translation of a signal from an outside entity. 1099 5. Limitations 1101 EMAN addresses the needs of energy monitoring in terms of 1102 measurement and considers limited control capabilities of energy 1103 monitoring of networks. 1105 EMAN does not create a new protocol stack, but rather defines a 1106 data and information model useful for measuring and reporting 1107 energy and other metrics over SNMP. 1109 EMAN does not address questions regarding Smart Grid, 1110 electricity producers, and distributors. 1112 6. Security Considerations 1114 EMAN uses the SNMP protocol and thus has the functionality of 1115 SNMP's security capabilities. SNMPv3 [RFC3411] provides 1116 important security features such as confidentiality, integrity, 1117 and authentication. 1119 [RFC7460] section 10 and [RFC7461] section 6 mention that power 1120 monitoring and management MIBs may have certain privacy 1121 implications. These privacy implications are beyond the scope 1122 of this document. There may be additional privacy 1123 considerations specific to each use case; this document has not 1124 attempted to analyze these. 1126 7. IANA Considerations 1128 This memo includes no request to IANA. 1130 8. Acknowledgements 1132 Firstly, the authors thank Emmanuel Tychon for taking the lead 1133 for the initial draft and his substantial contributions to it. 1134 The authors also thank Jeff Wheeler, Benoit Claise, Juergen 1135 Quittek, Chris Verges, John Parello, and Matt Laherty for their 1136 valuable contributions. The authors also thank Kerry Lynn for 1137 the use case involving demand response. 1139 9. References 1141 9.1. Normative References 1143 [RFC3411] An Architecture for Describing Simple Network 1144 Management Protocol (SNMP) Management Frameworks, RFC 1145 3411, December 2002. 1147 [RFC3621] Power Ethernet MIB, RFC 3621, December 2003. 1149 9.2. Informative References 1151 [ACPI] "Advanced Configuration and Power Interface 1152 Specification", http://www.acpi.info/spec30b.htm 1154 [DASH] "Desktop and mobile Architecture for System Hardware", 1155 http://www.dmtf.org/standards/mgmt/dash/ 1157 [DMTF DSP0004] DMTF Common Information Model (CIM) 1158 Infrastructure, DSP0004, May 2009. 1159 http://www.dmtf.org/standards/published_documents/DSP00 1160 04_2.5.0.pdf. 1162 [DMTF DSP1027] DMTF Power State Management Profile, DSP1027, 1163 December 2009. 1164 http://www.dmtf.org/standards/published_documents/DSP10 1165 27_2.0.0.pdf. 1167 [Ecma-SDC] Ecma-400, "Smart Data Centre Resource Monitoring and 1168 nd 1169 Control (2 Edition)", June 2013. 1171 [EMAN-REQ] Quittek, J., Chandramouli, M. Winter, R., Dietz, T., 1172 Claise, B., and Chandramouli, M. "Requirements for 1173 Energy Management ", RFC 6988, September 2013. 1175 [EMAN-MONITORING-MIB] Chandramouli, M., Schoening, B., Dietz, 1176 T., Quittek, J. and Claise, B. "Energy and Power 1177 Monitoring MIB ", draft-ietf-eman-monitoring-mib-13, 1178 May 2015. 1180 [EMAN-AWARE-MIB] Parello, J., Claise, B. and Chandramouli, M. 1181 "draft-ietf-eman-energy-aware-mib-16", work in 1182 progress, July 2014. 1184 [RFC7326] Claise, B., Parello, J., Schoening, B., Quittek, J. 1185 "Energy Management Framework", RFC7326, September 2014. 1187 [EMAN-BATTERY-MIB] Quittek, J., Winter, R., and T. Dietz, 1188 "Definition of Managed Objects for Battery Monitoring" 1189 draft-ietf-eman-battery-mib-17.txt, December 2014. 1191 [ESTAR] http://www.energystar.gov/ 1193 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1434 1195 [ASHRAE] http://collaborate.nist.gov/twiki- 1196 sggrid/bin/view/SmartGrid/PAP17Information 1198 [ZIGBEE] http://www.zigBee.org/ 1200 [ANSICEA] ANSI/CEA-2047, Consumer Electronics - Energy Usage 1201 Information (CE-EUI), 2013. 1203 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1337 1205 [PWG5106.4]IEEE-ISTO PWG Power Management Model for Imaging 1206 Systems v1.0, PWG Candidate Standard 5106.4-2011, 1207 February 2011.ftp://ftp.pwg.org/pub/pwg/candidates/cs- 1208 wimspower10-20110214-5106.4.mib 1210 [PWG5106.5] IEEE-ISTO PWG Imaging System Power MIB v1.0, PWG 1211 Candidate Standard 5106.5-2011, February 2011. 1213 [IEC62301] International Electrotechnical Commission, "IEC 62301 1214 Household electrical appliances Measurement of standby 1215 power", Edition 2.0, 2011. 1217 [MODBUS] Modbus-IDA, "MODBUS Application Protocol Specification 1218 V1.1b", December 2006. 1220 [NIST] http://www.nist.gov/smartgrid/ 1222 [RFC3805] Bergman, R., Lewis, H., and McDonald, I. "Printer MIB 1223 v2", RFC 3805, June 2004. 1225 [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and 1226 Chandramouli, M., "Entity MIB v4", RFC 6933, May 2013. 1228 Authors' Addresses 1230 Brad Schoening 1231 44 Rivers Edge Drive 1232 Little Silver, NJ 07739 1233 USA 1235 Phone: +1 917 304 7190 1236 Email: brad.schoening@verizon.net 1238 Mouli Chandramouli 1239 Cisco Systems, Inc. 1240 Sarjapur Outer Ring Road 1241 Bangalore 560103 1242 India 1244 Phone: +91 80 4429 2409 1245 Email: moulchan@cisco.com 1247 Bruce Nordman 1248 Lawrence Berkeley National Laboratory 1249 1 Cyclotron Road, 90-4000 1250 Berkeley 94720-8136 1251 USA 1253 Phone: +1 510 486 7089 1254 Email: bnordman@lbl.gov