idnits 2.17.1 draft-ietf-eman-applicability-statement-10.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 29 longer pages, the longest (page 1) being 62 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 11, 2015) is 3333 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- 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: 0 errors (**), 0 flaws (~~), 4 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: Standards Track Mouli Chandramouli 5 Expires: July 11, 2015 Cisco Systems Inc. 6 Bruce Nordman 7 Lawrence Berkeley National Laboratory 8 February 11, 2015 10 Energy Management (EMAN) Applicability Statement 11 draft-ietf-eman-applicability-statement-10 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 July 11, 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. Off-Grid Devices .................................. 15 84 2.13. Demand Response ................................... 16 85 2.14. Power Capping ..................................... 16 86 3. Use Case Patterns ...................................... 17 87 3.1. Metering ........................................... 17 88 3.2. Metering and Control ............................... 17 89 3.3. Power Supply, Metering and Control ................. 17 90 3.4. Multiple Power Sources ............................. 17 91 4. Relationship of EMAN to Other Standards ................ 18 92 4.1. Data Model and Reporting ........................... 18 93 4.1.1. IEC - CIM................................... 18 94 4.1.2. DMTF........................................ 18 95 4.1.3. ODVA........................................ 20 96 4.1.4. Ecma SDC.................................... 20 97 4.1.5. PWG......................................... 21 98 4.1.6. ASHRAE...................................... 21 99 4.1.7. ANSI/CEA.................................... 22 100 4.1.8. ZigBee...................................... 22 101 4.2. Measurement ........................................ 23 102 4.2.1. ANSI C12.................................... 23 103 4.2.2. IEC 62301................................... 23 104 4.3. Other .............................................. 24 105 4.3.1. ISO......................................... 24 106 4.3.2. Energy Star................................. 24 107 4.3.3. Smart Grid.................................. 25 108 5. Limitations ............................................ 26 109 6. Security Considerations ................................ 26 110 7. IANA Considerations .................................... 26 111 8. Acknowledgements ....................................... 26 112 9. References ............................................. 26 113 9.1. Normative References ............................... 26 114 9.2. Informative References ............................. 27 116 1. Introduction 118 The focus of the Energy Management (EMAN) framework is energy 119 monitoring and management of energy objects [RFC7326]. The 120 scope of devices considered are network equipment and their 121 components, and devices connected directly or indirectly to 122 the network. The EMAN framework enables monitoring of 123 heterogeneous devices to report their energy consumption and, 124 if permissible, control. There are multiple scenarios where 125 this is desirable, particularly considering the increased 126 importance of limiting consumption of finite energy resources 127 and reducing operational expenses. 129 The EMAN framework [RFC7326] describes how energy information 130 can be retrieved from IP-enabled devices using Simple Network 131 Management Protocol (SNMP), specifically, Management Information 132 Base (MIBs) for SNMP. 134 This document describes typical applications of the EMAN 135 framework, as well as its opportunities and limitations. It 136 also reviews other standards that are similar in part to EMAN 137 but address different domains, describing how those other 138 standards relate to the EMAN framework. 140 The rest of the document is organized as follows. Section 2 141 contains a list of use cases or network scenarios that EMAN 142 addresses. Section 3 contains an abstraction of the use case 143 scenarios to distinct patterns. Section 4 deals with other 144 standards related and applicable to EMAN. 146 1.1. Energy Management Overview 148 EMAN addresses the electrical energy consumed by devices 149 connected to a network. A first step to increase the energy 150 efficiency in networks and the devices attached to the network 151 is to enable energy objects to report their energy usage over 152 time. The EMAN framework addresses this problem with an 153 information model for electrical equipment: energy object 154 identification, energy object context, power measurement, and 155 power characteristics. 157 The EMAN framework defines SNMP MIB modules based on the 158 information model. By implementing these SNMP MIB modules, an 159 energy object can report its energy consumption according to the 160 information model. Based on the information model, the MIB 161 drafts specify SNMP MIB modules, but it is equally possible to 162 use other mechanisms such as YANG module, NETCONF, etc. 164 In that context, it is important to distinguish energy objects 165 that can only report their own energy usage from devices that 166 can also collect and aggregate energy usage of other energy 167 objects. 169 1.2. EMAN Document Overview 171 The EMAN work consists of the following Standard Track and 172 Informational documents in the area of energy management. 174 Applicability Statement (this document) 176 Requirements [EMAN-REQ]: This document presents requirements 177 of energy management and the scope of the devices considered. 179 Framework [RFC7326]: This document defines a framework for 180 providing energy management for devices within or connected to 181 communication networks, and lists the definitions for the 182 common terms used in these documents. 184 Energy-Aware MIB [EMAN-AWARE-MIB]: This document defines a MIB 185 module that characterizes a device's identity, context and 186 relationships to other entities. 188 Monitoring MIB [EMAN-MONITORING-MIB]: This document defines a 189 MIB module for monitoring the power and energy consumption of 190 a device. The MIB module contains an optional module for 191 metrics associated with power characteristics. 193 Battery MIB [EMAN-BATTERY-MIB]: This document defines a MIB 194 module for monitoring characteristics of an internal battery. 196 1.3. Energy Measurement 198 It is increasingly common for today's smart devices to measure 199 and report their own energy consumption. Intelligent power 200 strips and some Power over Ethernet (PoE) switches can meter 201 consumption of connected devices. However, when managed and 202 reported through proprietary means, this information is 203 difficult to view at the enterprise level. 205 The primary goal of the EMAN information model is to enable 206 reporting and management within a standard framework that is 207 applicable to a wide variety of end devices, meters, and 208 proxies. This enables a management system to know who's 209 consuming what, when, and how by leveraging existing networks, 210 across various equipment, in a unified and consistent manner. 212 Because energy objects may both consume energy and provide 213 energy to other devices, there are three types of energy 214 measurement: energy input to a device, energy supplied to other 215 devices, and net (resultant) energy consumed (the difference 216 between energy input and supplied). 218 1.4. Energy Management 220 The EMAN framework provides mechanisms for energy control in 221 addition to passive monitoring. There are many cases where 222 active energy control of devices is desirable, such during low 223 device utilization or peak electrical price periods. 225 Energy control can be as simple as controlling on/off states. In 226 many cases, however, energy control requires understanding the 227 energy object context. For instance, in commercial building 228 during non-business hours, some phones must remain available in 229 case of emergency and office cooling is not usually turned off 230 completely, but the comfort level is reduced. 232 Energy object control therefore requires flexibility and support 233 for different polices and mechanisms: from centralized 234 management by an energy management system, to autonomous control 235 by individual devices, and alignment with dynamic demand 236 response mechanisms. 238 The EMAN framework power states can be used in demand response 239 scenarios. In response to time-of-day fluctuation of energy 240 costs or grid power shortages, network devices can respond and 241 reduce their energy consumption. 243 1.5. EMAN Framework Application 245 A Network Management System (NMS) is an entity that requests 246 information from compatible devices, typically using the SNMP 247 protocol. An NMS may implement many network management 248 functions, such as security or identity management. An NMS that 249 deals exclusively with energy is called an Energy Management 250 System (EnMS). It may be limited to monitoring energy use, or 251 it may also implement control functions. An EnMS collects 252 energy information for devices in the network. 254 Energy management can be implemented by extending existing SNMP 255 support with EMAN specific MIBs. SNMP provides an industry- 256 proven and well-known mechanism to discover, secure, measure, 257 and control SNMP-enabled end devices. The EMAN framework 258 provides an information and data model to unify access to a 259 large range of devices. 261 2. Scenarios and Target Devices 263 This section presents energy management scenarios that the EMAN 264 framework should solve. Each scenario lists target devices for 265 which the energy management framework can be applied, how the 266 reported-on devices are powered, and how the reporting or 267 control is accomplished. While there is some overlap between 268 some of the use cases, the use cases illustrate network 269 scenarios that the EMAN framework supports. 271 2.1. Network Infrastructure Energy Objects 273 This scenario covers the key use case of network devices and 274 their components. For a device aware of one or more components, 275 our information model supports monitoring and control at the 276 component level. Typically, the chassis draws power from one or 277 more sources and feeds its internal components. It is highly 278 desirable to have monitoring available for individual 279 components, such as line cards, processors, disk drives and 280 peripherals such as USB devices. 282 As an illustrative example, consider a switch with the following 283 grouping of sub-entities for which energy management could be 284 useful. 286 . Physical view: chassis (or stack), line cards, and service 287 modules of the switch. 288 . Component view: CPU, ASICs, fans, power supply, ports 289 (single port and port groups), storage, and memory. 291 The ENTITY-MIB [RFC6933] provides a containment model for 292 uniquely identifying the physical sub-components of network 293 devices. The containment information identifies whether one 294 Energy Object belongs to another Energy Object (e.g. a line-card 295 Energy Object contained in a chassis Energy Object). The 296 mapping table entPhysicalContainsTable has an index 297 entPhysicalChildIndex and the table entPhysicalTable has a MIB 298 object entPhysicalContainedIn which points to the containing 299 entity. 301 The essential properties of this use case are: 303 . Target devices: network devices such as routers and 304 switches as well as their components. 305 . How powered: typically by a Power Distribution Unit (PDU) 306 on a rack or from a wall outlet. The components of a 307 device are powered by the device chassis. 308 . Reporting: direct power measurement can be performed at a 309 device level. Components can report their power 310 consumption directly or the chassis/device can report on 311 behalf of some components. 313 2.2. Devices Powered and Connected by a Network Device 315 This scenario covers Power Sourcing Equipment (PSE) devices. A 316 PSE device (e.g. a PoE switch) provides power to a Powered 317 Device (PD) (e.g. a desktop phone) over a medium such as USB or 318 Ethernet [RFC3621]. For each port, the PSE can control the 319 power supply (switching it on and off) and usually meter actual 320 power provided. PDs obtain network connectivity as well as 321 power over a single connection so the PSE can determine which 322 device is associated with each port. 324 PoE ports on a switch are commonly connected to devices such as 325 IP phones, wireless access points, and IP cameras. The switch 326 needs power for its internal use and to supply power to PoE 327 ports. Monitoring the power consumption of the switch 328 (supplying device) and the power consumption of the PoE end- 329 points (consuming devices) is a simple use case of this 330 scenario. 332 This scenario illustrates the relationships between entities. 333 The PoE IP phone is powered by the switch. If there are many IP 334 phones connected to the same switch, the power consumption of 335 all the IP phones can be aggregated by the switch. 337 The essential properties of this use case are: 339 . Target devices: Power over Ethernet devices such as IP 340 phones, wireless access points, and IP cameras. 341 . How powered: PoE devices are connected to the switch port 342 which supplies power to those devices. 343 . Reporting: PoE device power consumption is measured and 344 reported by the switch (PSE) which supplies power. In 345 addition, some edge devices can support the EMAN framework. 347 This use case can be divided into two subcases: 349 a) The end-point device supports the EMAN framework, in which 350 case this device is an EMAN Energy Object by itself, with 351 its own UUID. The device is responsible for its own power 352 reporting and control. See the related scenario "Devices 353 Connected to a Network" below. 355 b) The end-point device does not have EMAN capabilities, and 356 the power measurement may not be able to be performed 357 independently, and is therefore only performed by the 358 supplying device. This scenario is similar to the "Mid- 359 level Manager" below. 361 In subcase (a) note that two power usage reporting mechanisms 362 for the same device are available: one performed by the PD 363 itself and one performed by the PSE. Device specific 364 implementations will dictate which one to use. 366 2.3. Devices Connected to a Network 368 This use case covers the metering relationship between an energy 369 object and the parent energy object to which it is connected, 370 while receiving power from a different source. 372 An example is a PC which has a network connection to a switch, 373 but draws power from a wall outlet. In this case, the PC can 374 report power usage by itself, ideally through the EMAN 375 framework. 377 The wall outlet to which the PC is plugged in can be unmetered 378 or metered, for example, by a Smart PDU. 380 a) If metered, the PC has a powered-by relationship to the Smart 381 PDU, and the Smart PDU acts as a "Mid-Level Manager". 383 b) If unmetered, or operating on batteries, the PC will report 384 its own energy usage as any other Energy Object to the switch, 385 and the switch may possibly provide aggregation. 387 These two cases are not mutually exclusive. 389 In terms of relationships between entities, the PC has a 390 powered-by relationship to the PDU and if the power consumption 391 of the PC is metered by the PDU, then there is a metered-by 392 relation between the PC and the PDU. 394 The essential properties of this use case are: 396 . Target devices: energy objects that have a network 397 connection, but receive power supply from another source. 398 . How powered: end-point devices (e.g. PCs) receive power 399 supply from the wall outlet (unmetered), a PDU (metered), 400 or can be powered autonomously (batteries). 401 . Reporting: devices can either measure and report the power 402 consumption directly via the EMAN framework, communicate it 403 to the network device (switch) and the switch can report 404 the device's power consumption via the EMAN framework, or 405 power can be reported by the PDU. 407 2.4. Power Meters 409 Some electrical devices are not equipped with instrumentation to 410 measure their own power and accumulated energy consumption. 411 External meters can be used to measure the power consumption of 412 such electrical devices as well as collections of devices. 414 Three types of external metering are relevant to EMAN: PDUs, 415 standalone meters, and utility meters. External meters can 416 measure consumption of a single device or a set of devices. 418 Power Distribution Units (PDUs) can have built-in meters for 419 each socket and can measure the power supplied to each device in 420 an equipment rack. PDUs typically have remote management 421 capabilities which can report and possibly control the power 422 supply of each outlet. 424 Standalone meters can be placed anywhere in a power distribution 425 tree and may measure all or part of the total. Utility meters 426 monitor and report accumulated power consumption of the entire 427 building. There can be sub-meters to measure the power 428 consumption of a portion of the building. 430 The essential properties of this use case are: 432 . Target devices: PDUs and meters. 433 . How powered: from traditional mains power but supplied 434 through a PDU or meter. 435 . Reporting: PDUs report power consumption of downstream 436 devices, usually a single device per outlet. Meters may 437 report for one or more devices and may require knowledge of 438 the topology to associate meters with metered devices. 440 Meters have metered-by relationships with devices, and may have 441 aggregation relationship between the meters and the devices for 442 which power consumption is accumulated and reported by the 443 meter. 445 2.5. Mid-level Managers 447 This use case covers aggregation of energy management data at 448 "mid-level managers" that can provide energy management 449 functions for themselves and associated devices. 451 A switch can provide energy management functions for all devices 452 connected to its ports, whether or not these devices are powered 453 by the switch or whether the switch provides immediate network 454 connectivity to the devices. Such a switch is a mid-level 455 manager, offering aggregation of power consumption data for 456 other devices. Devices report their EMAN data to the switch and 457 the switch aggregates the data for further reporting. 459 The essential properties of this use case: 461 . Target devices: devices which can perform aggregation; 462 commonly a switch or a proxy. 463 . How powered: mid-level managers are commonly powered by a 464 PDU or from a wall outlet but can be powered by any method. 466 . Reporting: the mid-level manager aggregates the energy data 467 and reports that data to an EnMS or higher mid-level 468 manager. 470 2.6. Non-residential Building System Gateways 472 This use case describes energy management of non-residential 473 buildings. Building Management Systems (BMS) have been in place 474 for many years using legacy protocols not based on IP. In these 475 buildings, a gateway can provide a proxy function between IP 476 networks and legacy building automation protocols. The gateway 477 provides an interface between the EMAN framework and relevant 478 building management protocols. 480 Due to the potential energy savings, energy management of 481 buildings has received significant attention. There are gateway 482 network elements to manage the multiple components of a building 483 energy management system such as Heating, Ventilation, and Air 484 Conditioning (HVAC), lighting, electrical, fire and emergency 485 systems, elevators, etc. The gateway device uses legacy 486 building protocols to communicate with those devices, collects 487 their energy usage, and reports the results. 489 The gateway performs protocol conversion and communicates via 490 RS-232/RS-485 interfaces, Ethernet interfaces, and protocols 491 specific to building management such as BACNET [ASHRAE], MODBUS 492 [MODBUS], or ZigBee [ZIGBEE]. 494 The essential properties of this use case are: 496 . Target devices: building energy management devices - HVAC 497 systems, lighting, electrical, fire and emergency systems. 498 . How powered: any method. 499 . Reporting: the gateway collects energy consumption of non- 500 IP systems and communicates the data via the EMAN 501 framework. 503 2.7. Home Energy Gateways 505 This use case describes the scenario of energy management of a 506 home. The home energy gateway is another example of a proxy 507 that interfaces with electrical appliances and other devices in 508 a home. This gateway can monitor and manage electrical 509 equipment (e.g. refrigerator, heating/cooling, or washing 510 machine) using one of the many protocols that are being 511 developed for residential devices. 513 Beyond simply metering, it's possible to implement energy saving 514 policies based on time of day, occupancy, or energy pricing from 515 the utility grid. The EMAN information model can be applied to 516 energy management of a home. 518 The essential properties of this use case are: 520 . Target devices: home energy gateway and smart meters in a 521 home. 522 . How powered: any method. 523 . Reporting: home energy gateway can collect power 524 consumption of device in a home and possibly report the 525 metering reading to the utility. 527 While the common case is of a home drawing all power from the 528 utility, some buildings/homes can produce and consume energy 529 with reduced or net-zero energy from the utility grid. There 530 are many energy production technologies such as solar panels, 531 wind turbines, or micro generators. This use case illustrates 532 the concept of self-contained energy generation, consumption, 533 and possibly the aggregation of the energy use of homes. 535 2.8. Data Center Devices 537 This use case describes energy management of a data center. 538 Energy efficiency of data centers has become a fundamental 539 challenge of data center operation, as data centers are big 540 energy consumers and have expensive infrastructure. The 541 equipment generates heat, and heat needs to be evacuated through 542 an HVAC system. 544 A typical data center network consists of a hierarchy of 545 electrical energy objects. At the bottom of the network 546 hierarchy are servers mounted on a rack; these are connected to 547 top-of-the-rack switches, which in turn are connected to 548 aggregation switches, and then to core switches. Power 549 consumption of all network elements, servers, and storage 550 devices in the data center should be measured. Energy 551 management can be implemented on different aggregation levels, 552 i.e., at the network level, Power Distribution Unit (PDU) level, 553 and/or server level. 555 Beyond the network devices, storage devices, and servers, data 556 centers contain UPSs to provide back-up power for the facility 557 in the event of a power outage. A UPS can provide backup power 558 for many devices in a data center for a finite period of time. 559 Energy monitoring of energy storage capacity is vital from a 560 data center network operations point of view. Presently, the 561 UPS MIB can be useful in monitoring the battery capacity, the 562 input load to the UPS, and the output load from the UPS. 563 Currently, there is no link between the UPS MIB and the ENTITY 564 MIB. 566 In addition to monitoring the power consumption of a data 567 center, additional power characteristics should be monitored. 568 Some of these are dynamic variations in the input power supply 569 from the grid referred to as power quality metrics. It can also 570 be useful to monitor how efficiently the devices utilize power. 572 Nameplate capacity of the data center can be estimated from the 573 nameplate ratings (the worst case possible power draw) of IT 574 equipment at a site. 576 The essential properties of this use case are: 578 . Target devices: IT devices in a data center, such as 579 network equipment, servers, and storage devices, as well as 580 power and cooling infrastructure. 581 . How powered: any method, but commonly by one or more PDUs. 582 . Reporting: devices may report on their own behalf, or for 583 other connected devices as described in other use cases. 585 2.9. Energy Storage Devices 587 Energy storage devices can have two different roles: one type 588 whose primary function is to provide power to another device 589 (e.g. a UPS), and one type with a different primary function, 590 but having energy storage as a component (e.g. a notebook). 591 This use case covers both. 593 The energy storage can be a conventional battery, or any other 594 means to store electricity such as a hydrogen cell. 596 An internal battery can be a back-up or an alternative source of 597 power to mains power. As batteries have a finite capacity and 598 lifetime, means for reporting the actual charge, age, and state 599 of a battery are required. An internal battery can be viewed as 600 a component of a device and so be contained within the device 601 from an ENTITY-MIB perspective. 603 Battery systems are often used in remote locations such as 604 mobile telecom towers. For continuous operation, it is 605 important to monitor the remaining battery life and raise an 606 alarm when this falls below a threshold. 608 The essential properties of this use case are: 610 . Target devices: devices that have an internal battery or 611 external storage. 612 . How powered: from batteries or other storage devices. 613 . Reporting: the device reports on its power delivered and 614 state. 616 2.10. Industrial Automation Networks 618 Energy consumption statistics in the industrial sector are 619 staggering. The industrial sector alone consumes about half of 620 the world's total delivered energy, and is a significant user of 621 electricity. Thus, the need for optimization of energy usage in 622 this sector is natural. 624 Industrial facilities consume energy in process loads and non- 625 process loads. 627 The essential properties of this use case are: 629 . Target devices: devices used in an industrial sector. 630 . How powered: any method. 631 . Reporting: the CIP protocol is commonly used for reporting 632 energy for these devices. 634 2.11. Printers 636 This use case describes the scenario of energy monitoring and 637 management of printers. Printers in this use case stand in for 638 all imaging equipment, including multi-function devices (MFDs), 639 scanners, fax machines, and mailing machines. 641 Energy use of printers has been a longstanding industry concern 642 and sophisticated power management is common. Printers often 643 use a variety of low-power modes, particularly for managing 644 energy-intensive thermo-mechanical components. Printers also 645 have long made extensive use of SNMP for end-user system 646 interaction and for management generally, with cross-vendor 647 management systems able to manage fleets of printers in 648 enterprises. Power consumption during active modes can vary 649 widely, with high peak usage levels. 651 Printers can expose detailed power state information, distinct 652 from operational state information, with some printers reporting 653 transition states between stable long-term states. Many also 654 support active setting of power states and policies such as 655 delay times, when inactivity automatically transitions the 656 device to a lower power mode. Other features include reporting 657 on components, counters for state transitions, typical power 658 levels by state, scheduling, and events/alarms. 660 Some large printers also have a "Digital Front End," which is a 661 computer that performs functions on behalf of the physical 662 imaging system. These typically have their own presence on the 663 network and are sometimes separately powered. 665 There are some unique characteristics of printers from the point 666 of view energy management. While the printer is not in use, 667 there are timer-based low power states, which consume little 668 power. On the other hand, while the printer is printing or 669 copying, the cylinder is heated so that power consumption is 670 quite high but only for a short period of time. Given this work 671 load, periodic polling of power levels alone would not suffice. 673 The essential properties of this use case are: 675 . Target devices: all imaging equipment. 676 . How powered: typically AC from a wall outlet. 677 . Reporting: devices report for themselves. 679 2.12. Off-Grid Devices 681 This use case concerns self-contained devices that use energy 682 but are not connected to an infrastructure power delivery grid. 683 These devices typically produce energy from sources such as 684 solar energy, wind power, or fuel cells. The device generally 685 contains a closely coupled combination of 687 . power generation component(s) 688 . power storage component(s) (e.g., battery) 689 . power consuming component(s) 691 With renewable power, the energy input is often affected by 692 variations in weather. These devices therefore require energy 693 management both for internal control and remote reporting of 694 their state. 696 In many cases these devices are expected to operate 697 autonomously, as continuous communications for the purposes of 698 remote control is not available. Non-continuous polling 699 requires the ability to store and access later the information 700 acquired while off-line. 702 The essential properties of this use case are: 704 . Target devices: remote area devices that produce and 705 consume energy. 706 . How powered: site energy sources. 707 . Reporting: devices report their power usage, but not 708 necessarily continuously. 710 2.13. Demand Response 712 The theme of demand response from a utility grid spans across 713 several use cases. In some situations, in response to time-of- 714 day fluctuation of energy costs or sudden energy shortages due 715 power outages, it may be important to respond and reduce the 716 energy consumption of the network. 718 From the EMAN use case perspective, the demand response scenario 719 can apply to a data center, building or home. Real-time energy 720 monitoring is usually a prerequisite, so that during a potential 721 energy shortfall the EnMS can provide an active response. The 722 EnMS could shut down selected devices that are considered lower 723 priority or uniformly reduce the power supplied to a class of 724 devices. For multi-site data centers it may be possible to 725 formulate policies such as follow-the-sun type of approach, by 726 scheduling the mobility of VMs across data centers in different 727 geographical locations. 729 The essential properties of this use case are: 731 . Target devices: any device. 732 . How powered: traditional mains AC power. 733 . Reporting: real-time. 734 . Control: demand response based upon policy or priority. 736 2.14. Power Capping 738 The purpose of power-capping is to run a server without 739 exceeding a power usage threshold, and thereby, to remain under 740 the critical available power threshold. This method can be 741 useful for power limited data centers. Based on workload 742 measurements, a device can choose the optimal power state in 743 terms of performance and power consumption. When the server 744 operates at less than the power supply capacity, the server can 745 operate at full speed. When the power requirements exceed the 746 power supply, the server operates in a reduced power mode so 747 that its power consumption matches the available power budget. 749 The essential properties of this use case are: 751 Target devices: IT devices in a data center. 752 How powered: traditional mains AC power. 753 Reporting: real-time. 754 Control: autonomous power capping by the device. 756 3. Use Case Patterns 758 The use cases presented above can be abstracted to the following 759 broad patterns for energy objects. 761 3.1. Metering 763 - Energy objects which have capability for internal metering 764 - Energy objects which are metered by an external device 766 3.2. Metering and Control 768 - Energy objects that do not supply power, but can perform power 769 metering for other devices 771 - Energy objects that do not supply power, but can perform both 772 metering and control for other devices 774 3.3. Power Supply, Metering and Control 776 - Energy objects that supply power for other devices but do not 777 perform power metering for those devices 779 - Energy objects that supply power for other devices and also 780 perform power metering 782 - Energy objects that supply power for other devices and also 783 perform power metering and control for other devices 785 3.4. Multiple Power Sources 787 - Energy objects that have multiple power sources, with metering 788 and control performed by the same power source 789 - Energy objects that have multiple power sources supplying 790 power to the device with metering performed by one or more 791 sources and control performed by another source 793 4. Relationship of EMAN to Other Standards 795 The EMAN framework is tied to other standards and efforts that 796 address energy monitoring and control. EMAN leverages existing 797 standards when possible, and it helps enable adjacent 798 technologies such as Smart Grid. 800 The standards most relevant and applicable to EMAN are listed 801 below with a brief description of their objectives, the current 802 state, and how that standard relates to EMAN. 804 4.1. Data Model and Reporting 806 4.1.1. IEC - CIM 808 The International Electrotechnical Commission (IEC) has 809 developed a broad set of standards for power management. Among 810 these, the most applicable to EMAN is IEC 61850, a standard for 811 the design of electric utility automation. The abstract data 812 model defined in 61850 is built upon and extends the Common 813 Information Model (CIM). The complete 61850 CIM model includes 814 over a hundred object classes and is widely used by utilities 815 worldwide. 817 This set of standards were originally conceived to automate 818 control of a substation (a facility which transfer electricity 819 from the transmission to the distribution system). However, the 820 extensive data model has been widely used in other domains, 821 including Energy Management Systems (EnMS). 823 IEC TC57 WG19 is an ongoing working group with the objective to 824 harmonize the CIM data model and 61850 standards. 826 Several concepts from IEC Standards have been reused in the EMAN 827 drafts. In particular, AC Power Quality measurements have been 828 reused from IEC 61850-7-4. The concept of Accuracy Classes for 829 measurement of power and energy has been adapted from ANSI 830 C12.20 and IEC standards 62053-21 and 62053-22. 832 4.1.2. DMTF 834 The Distributed Management Task Force (DMTF) has defined a Power 835 State Management profile [DMTF DSP1027] for managing computer 836 systems using the DMTF's Common Information Model (CIM). These 837 specifications provide physical, logical, and virtual system 838 management requirements for power-state control services. The 839 DMTF standard does not include energy monitoring. 841 The Power State Management profile is used to describe and 842 manage the Power State of computer systems. This includes 843 controlling the Power State of an entity for entering sleep 844 mode, awakening, and rebooting. The EMAN framework references 845 the DMTF Power Profile and Power State Set. 847 4.1.2.1. Common Information Model Profiles 849 The DMTF uses CIM-based (Common Information Model) 'Profiles' to 850 represent and manage power utilization and configuration of 851 managed elements (note that this is not the 61850 CIM). Key 852 profiles for energy management are 'Power Supply' (DSP 1015), 853 'Power State' (DSP 1027), and 'Power Utilization Management' 854 (DSP 1085). These profiles define many features for the 855 monitoring and configuration of a Power Managed Element's static 856 and dynamic power saving modes, power allocation limits, and 857 power states. 859 Reduced power modes can be established as static or dynamic. 860 Static modes are fixed policies that limit power use or 861 utilization. Dynamic power saving modes rely upon internal 862 feedback to control power consumption. 864 Power states are eight named operational and non operational 865 levels. These are On, Sleep-Light, Sleep-Deep, Hibernate, Off- 866 Soft, and Off-Hard. Power change capabilities provide 867 immediate, timed interval, and graceful transitions between on, 868 off, and reset power states. Table 3 of the Power State Profile 869 defines the correspondence between the Advanced Configuration 870 and Power Interface [ACPI] and DMTF power state models, although 871 it is not necessary for a managed element to support ACPI. 872 Optionally, a TransitioningToPowerState property can represent 873 power state transitions in progress. 875 4.1.2.2. DASH 877 DMTF DASH [DASH] (Desktop And Mobile Architecture for System 878 Hardware) addresses managing heterogeneous desktop and mobile 879 systems (including power) via in-band and out-of-band 880 communications. DASH uses the DMTF's WS-Management web services 881 and CIM data model to manage and control resources such as 882 power, CPU, etc. 884 Both in-service and out-of-service systems can be managed with 885 the DASH specification in a fully secured remote environment. 886 Full power lifecycle management is possible using out-of-band 887 management. 889 4.1.3. ODVA 891 The Open DeviceNet Vendors Association (ODVA) is an association 892 for industrial automation companies that defines the Common 893 Industrial Protocol (CIP). Within ODVA, there is a special 894 interest group focused on energy and standardization and inter- 895 operability of energy-aware devices. 897 The ODVA is developing an energy management framework for the 898 industrial sector. There are synergies and similar concepts 899 between the ODVA and EMAN approaches to energy monitoring and 900 management. 902 ODVA defines a three-part approach towards energy management: 903 awareness of energy usage, energy efficiently, and the exchange 904 of energy with a utility or others. Energy monitoring and 905 management promote efficient consumption and enable automating 906 actions that reduce energy consumption. 908 The foundation of the approach is the information and 909 communication model for entities. An entity is a network- 910 connected, energy-aware device that has the ability to either 911 measure or derive its energy usage based on its native 912 consumption or generation of energy, or report a nominal or 913 static energy value. 915 4.1.4. Ecma SDC 917 The Ecma International standard on Smart Data Centre [Ecma-SDC] 918 defines semantics for management of entities in a data center 919 such as servers, storage, and network equipment. It covers 920 energy as one of many functional resources or attributes of 921 systems for monitoring and control. It only defines messages 922 and properties, and does not reference any specific protocol. 923 Its goal is to enable interoperability of such protocols as 924 SNMP, BACNET, and HTTP by ensuring a common semantic model 925 across them. Four power states are defined, Off, Sleep, Idle, 926 and Active. The standard does not include actual energy or 927 power measurements. 929 When used with EMAN, the SDC standard will provide a thin 930 abstraction on top of the more detailed data model available in 931 EMAN. 933 4.1.5. PWG 935 The IEEE-ISTO Printer Working Group (PWG) defines open standards 936 for printer related protocols, for the benefit of printer 937 manufacturers and related software vendors. The Printer WG 938 covers power monitoring and management of network printers and 939 imaging systems in the PWG Power Management Model for Imaging 940 Systems [PWG5106.4]. Clearly, these devices are within the 941 scope of energy management since they receive power and are 942 attached to the network. In addition, there is ample scope of 943 power management since printers and imaging systems are not used 944 that often. 946 The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB 947 modules for printer management and in particular a "PWG Power 948 Management Model for Imaging Systems v1.0" [PWG5106.4] and a 949 companion SNMP binding in the "PWG Imaging System Power MIB 950 v1.0" [PWG5106.5]. This PWG model and MIB are harmonized with 951 the DMTF CIM Infrastructure [DMTF DSP0004] and DMTF CIM Power 952 State Management Profile [DMTF DSP1027] for power states and 953 alerts. 955 These MIB modules can be useful for monitoring the power and 956 Power State of printers. The EMAN framework takes into account 957 the standards defined in the Printer Working Group. The PWG may 958 harmonize its MIBs with those from EMAN. The PWG covers many 959 topics in greater detail than EMAN, including those specific to 960 imaging equipment. The PWG also provides for vendor-specific 961 extension states (beyond the standard DMTF CIM states). 963 The IETF Printer MIB RFC3805 [RFC3805] has been standardized, 964 but, this MIB module does not address power management. 966 4.1.6. ASHRAE 968 In the U.S., there is an extensive effort to coordinate and 969 develop standards related to the "Smart Grid". The Smart Grid 970 Interoperability Panel, coordinated by the government's National 971 Institute of Standards and Technology, identified the need for a 972 building side information model (as a counterpart to utility 973 models) and specified this in Priority Action Plan (PAP) 17. 974 This was designated to be a joint effort by the American Society 975 of Heating, Refrigerating and Air-Conditioning Engineers 976 (ASHRAE) and the National Electrical Manufacturers Association 977 (NEMA), both ANSI approved SDO's. The result is to be an 978 information model, not a protocol. 980 The ASHRAE effort addresses data used only within a building as 981 well as data that may be shared with the grid, particularly as 982 it relates to coordinating future demand levels with the needs 983 of the grid. The model is intended to be applied to any 984 building type, both residential and commercial. It is expected 985 that existing protocols will be adapted to comply with the new 986 information model, as would new protocols. 988 There are four basic types of entities in the model: generators, 989 loads, meters, and energy managers. The metering part of the 990 model overlaps to a large degree with the EMAN framework, though 991 there are features unique to each. The load part speaks to 992 control capabilities well beyond what EMAN covers. Details of 993 generation and of the energy management function are outside of 994 EMAN scope. 996 A public review draft of the ASHRAE standard was released in 997 July, 2012. There are no apparent major conflicts between the 998 two approaches, but there are areas where some harmonization is 999 possible. 1001 4.1.7. ANSI/CEA 1003 The Consumer Electronics Association (CEA) has approved 1004 ANSI/CEA-2047 [ANSICEA] as a standard data model for Energy 1005 Usage Information. The primary purpose is to enable home 1006 appliances and electronics to communicate energy usage 1007 information over a wide range of technologies with pluggable 1008 modules that contain the physical layer electronics. The 1009 standard can be used by devices operating on any home network 1010 including Wi-Fi, Ethernet, ZigBee, Z-Wave, and Bluetooth. The 1011 Introduction to ANSI/CEA-2047 states that "this standard 1012 provides an information model for other groups to develop 1013 implementations specific to their network, protocol and 1014 needs". It covers device identification, current power level, 1015 cumulative energy consumption, and provides for reporting time- 1016 series data. 1018 4.1.8. ZigBee 1020 The ZigBee Smart Energy Profile 2.0 (SEP) effort [ZIGBEE] 1021 focuses on IP-based wireless communication to appliances and 1022 lighting. It is intended to enable internal building energy 1023 management and provide for bi-directional communication with the 1024 power grid. 1026 ZigBee protocols are intended for use in embedded applications 1027 with low data rates and low power consumption. ZigBee defines a 1028 general-purpose, inexpensive, self-organizing mesh network that 1029 can be used for industrial control, embedded sensing, medical 1030 data collection, smoke and intruder warning, building 1031 automation, home automation, etc. 1033 ZigBee is currently not an ANSI recognized SDO. 1035 The EMAN framework addresses the needs of IP-enabled networks 1036 through the usage of SNMP, while ZigBee provides for completely 1037 integrated and inexpensive mesh solutions. 1039 4.2. Measurement 1041 4.2.1. ANSI C12 1043 The American National Standards Institute (ANSI) has defined a 1044 collection of power meter standards under ANSI C12. The primary 1045 standards include communication protocols (C12.18, 21 and 22), 1046 data and schema definitions (C12.19), and measurement accuracy 1047 (C12.20). European equivalent standards are provided by IEC 1048 62053-22 1050 These very specific standards are oriented to the meter itself, 1051 and are used by electricity distributors and producers. 1053 The EMAN standard references ANSI C12.20 accuracy classes. 1055 4.2.2. IEC 62301 1057 IEC 62301, "Household electrical appliances Measurement of 1058 standby power", [IEC62301] specifies a power level measurement 1059 procedure. While nominally for appliances and low-power modes, 1060 its concepts apply to other device types and modes and it is 1061 commonly referenced in test procedures for energy using 1062 products. 1064 While the standard is intended for laboratory measurements of 1065 devices in controlled conditions, aspects of it are informative 1066 to those implementing measurement in products that ultimately 1067 report via EMAN. 1069 4.3. Other 1071 4.3.1. ISO 1073 The International Organization for Standardization (ISO) [ISO] 1074 is developing an energy management standard, ISO 50001, to 1075 complement ISO 9001 for quality management, and ISO 14001 for 1076 environmental management. The intent is to facilitate the 1077 creation of energy management programs for industrial, 1078 commercial, and other entities. The standard defines a process 1079 for energy management at an organizational level. It does not 1080 define the way in which devices report energy and consume 1081 energy. 1083 ISO 50001 is based on the common elements found in all of ISO's 1084 management system standards, assuring a high level of 1085 compatibility with ISO 9001 and ISO 14001. ISO 50001 benefits 1086 include: 1088 o Integrating energy efficiency into management practices and 1089 throughout the supply chain. 1090 o Energy management best practices and good energy management 1091 behaviors. 1092 o Benchmarking, measuring, documenting, and reporting energy 1093 intensity improvements and their projected impact on 1094 reductions in greenhouse gas (GHG) emissions. 1095 o Evaluating and prioritizing the implementation of new energy- 1096 efficient technologies. 1098 ISO 50001 has been developed by ISO project committee ISO PC 1099 242, Energy management. EMAN is complementary to ISO 9001. 1101 4.3.2. Energy Star 1103 The U.S. Environmental Protection Agency (EPA) and U.S. 1104 Department of Energy (DOE) jointly sponsor the Energy Star 1105 program [ESTAR]. The program promotes the development of energy 1106 efficient products and practices. 1108 To qualify as Energy Star, products must meet specific energy 1109 efficiency targets. The Energy Star program also provides 1110 planning tools and technical documentation to encourage more 1111 energy efficient building design. Energy Star is a program; it 1112 is not a protocol or standard. 1114 For businesses and data centers, Energy Star offers technical 1115 support to help companies establish energy conservation 1116 practices. Energy Star provides best practices for measuring 1117 current energy performance, goal setting, and tracking 1118 improvement. The Energy Star tools offered include a rating 1119 system for building performance and comparative benchmarks. 1121 There is no immediate link between EMAN and Energy Star, one 1122 being a protocol and the other a set of recommendations to 1123 develop energy efficient products. However, Energy Star could 1124 include EMAN standards in specifications for future products, 1125 either as required or rewarded with some benefit. 1127 4.3.3. Smart Grid 1129 The Smart Grid standards efforts underway in the United States 1130 are overseen by the U.S. National Institute of Standards and 1131 Technology [NIST]. NIST is responsible for coordinating a 1132 public-private partnership with key energy and consumer 1133 stakeholders in order to facilitate the development of Smart 1134 Grid standards. These activities are monitored and facilitated 1135 by the SGIP (Smart Grid Interoperability Panel). This group has 1136 working groups for specific topics including homes, commercial 1137 buildings, and industrial facilities as they relate to the grid. 1138 A stated goal of the group is to harmonize any new standard with 1139 the IEC CIM and IEC 61850. 1141 When a working group detects a standard or technology gap, the 1142 team seeks approval from the SGIP for the creation of a Priority 1143 Action Plan (PAP), a private-public partnership to close the 1144 gap. PAP 17 is discussed in section 4.1.6. 1146 PAP 10 addresses "Standard Energy Usage Information". Smart 1147 Grid standards will provide distributed intelligence in the 1148 network and allow enhanced load shedding. For example, pricing 1149 signals will enable selective shutdown of non-critical 1150 activities during peak price periods. Actions can be effected 1151 through both centralized and distributed management controls. 1153 There is an obvious functional link between Smart Grid and EMAN 1154 in the form of demand response, even though the EMAN framework 1155 itself does not address any coordination with the grid. As EMAN 1156 enables control, it can be used by an EnMS to accomplish demand 1157 response through translation of a signal from an outside entity. 1159 5. Limitations 1161 EMAN addresses the needs of energy monitoring in terms of 1162 measurement and considers limited control capabilities of energy 1163 monitoring of networks. 1165 EMAN does not create a new protocol stack, but rather defines a 1166 data and information model useful for measuring and reporting 1167 energy and other metrics over SNMP. 1169 EMAN does not address questions regarding Smart Grid, 1170 electricity producers, and distributors. 1172 6. Security Considerations 1174 EMAN uses the SNMP protocol and thus has the functionality of 1175 SNMP's security capabilities. SNMPv3 [RFC3411] provides 1176 important security features such as confidentiality, integrity, 1177 and authentication. 1179 7. IANA Considerations 1181 This memo includes no request to IANA. 1183 8. Acknowledgements 1185 Firstly, the authors thank Emmanuel Tychon for taking the lead 1186 for the initial draft and his substantial contributions to it. 1187 The authors also thank Jeff Wheeler, Benoit Claise, Juergen 1188 Quittek, Chris Verges, John Parello, and Matt Laherty for their 1189 valuable contributions. The authors thank Georgios Karagiannis 1190 for use case involving energy neutral homes, Elwyn Davies for 1191 off-grid electricity systems, and Kerry Lynn for demand 1192 response. 1194 9. References 1196 9.1. Normative References 1198 [RFC3411] An Architecture for Describing Simple Network 1199 Management Protocol (SNMP) Management Frameworks, RFC 1200 3411, December 2002. 1202 [RFC3621] Power Ethernet MIB, RFC 3621, December 2003. 1204 9.2. Informative References 1206 [ACPI] "Advanced Configuration and Power Interface 1207 Specification", http://www.acpi.info/spec30b.htm 1209 [DASH] "Desktop and mobile Architecture for System Hardware", 1210 http://www.dmtf.org/standards/mgmt/dash/ 1212 [DMTF DSP0004] DMTF Common Information Model (CIM) 1213 Infrastructure, DSP0004, May 2009. 1214 http://www.dmtf.org/standards/published_documents/DSP00 1215 04_2.5.0.pdf. 1217 [DMTF DSP1027] DMTF Power State Management Profile, DSP1027, 1218 December 2009. 1219 http://www.dmtf.org/standards/published_documents/DSP10 1220 27_2.0.0.pdf. 1222 [Ecma-SDC] Ecma-400, "Smart Data Centre Resource Monitoring and 1223 Control (2 Edition)", June 2013. 1225 [EMAN-REQ] Quittek, J., Chandramouli, M. Winter, R., Dietz, T., 1226 Claise, B., and Chandramouli, M. "Requirements for 1227 Energy Management ", RFC 6988, September 2013. 1229 [EMAN-MONITORING-MIB] Chandramouli, M., Schoening, B., Dietz, 1230 T., Quittek, J. and Claise, B. "Energy and Power 1231 Monitoring MIB ", draft-ietf-eman-monitoring-mib-13, 1232 May 2015. 1234 [EMAN-AWARE-MIB] Parello, J., Claise, B. and Chandramouli, M. 1235 "draft-ietf-eman-energy-aware-mib-16", work in 1236 progress, July 2014. 1238 [RFC7326] Claise, B., Parello, J., Schoening, B., Quittek, J. 1239 "Energy Management Framework", RFC7326, September 2014. 1241 [EMAN-BATTERY-MIB] Quittek, J., Winter, R., and T. Dietz, 1242 "Definition of Managed Objects for Battery Monitoring" 1243 draft-ietf-eman-battery-mib-17.txt, December 2014. 1245 [ESTAR] http://www.energystar.gov/ 1247 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1434 1249 [ASHRAE] http://collaborate.nist.gov/twiki- 1250 sggrid/bin/view/SmartGrid/PAP17Information 1252 [ZIGBEE] http://www.zigBee.org/ 1254 [ANSICEA] ANSI/CEA-2047, Consumer Electronics - Energy Usage 1255 Information (CE-EUI), 2013. 1257 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1337 1259 [PWG5106.4]IEEE-ISTO PWG Power Management Model for Imaging 1260 Systems v1.0, PWG Candidate Standard 5106.4-2011, 1261 February 2011.ftp://ftp.pwg.org/pub/pwg/candidates/cs- 1262 wimspower10-20110214-5106.4.mib 1264 [PWG5106.5] IEEE-ISTO PWG Imaging System Power MIB v1.0, PWG 1265 Candidate Standard 5106.5-2011, February 2011. 1267 [IEC62301] International Electrotechnical Commission, "IEC 62301 1268 Household electrical appliances Measurement of standby 1269 power", Edition 2.0, 2011. 1271 [MODBUS] Modbus-IDA, "MODBUS Application Protocol Specification 1272 V1.1b", December 2006. 1274 [NIST] http://www.nist.gov/smartgrid/ 1276 [RFC3805] Bergman, R., Lewis, H., and McDonald, I. "Printer MIB 1277 v2", RFC 3805, June 2004. 1279 [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and 1280 Chandramouli, M., "Entity MIB v4", RFC 6933, May 2013. 1282 Authors' Addresses 1284 Brad Schoening 1285 44 Rivers Edge Drive 1286 Little Silver, NJ 07739 1287 USA 1289 Phone: +1 917 304 7190 1290 Email: brad.schoening@verizon.net 1292 Mouli Chandramouli 1293 Cisco Systems, Inc. 1294 Sarjapur Outer Ring Road 1295 Bangalore 560103 1296 India 1298 Phone: +91 80 4429 2409 1299 Email: moulchan@cisco.com 1301 Bruce Nordman 1302 Lawrence Berkeley National Laboratory 1303 1 Cyclotron Road, 90-4000 1304 Berkeley 94720-8136 1305 USA 1307 Phone: +1 510 486 7089 1308 Email: bnordman@lbl.gov