idnits 2.17.1 draft-ietf-eman-applicability-statement-09.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 (December 27, 2014) is 3402 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- 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: Informational Mouli Chandramouli 5 Expires: June 27, 2015 Cisco Systems Inc. 6 Bruce Nordman 7 Lawrence Berkeley National Laboratory 8 December 27, 2014 10 Energy Management (EMAN) Applicability Statement 11 draft-ietf-eman-applicability-statement-09 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 June 27, 2015. 48 Copyright Notice 50 Copyright (c) 2014 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 its 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. This document describes how 138 those other 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 to EMAN 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 have 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 provided). 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 as when the 223 device utilization is low or during peak electrical price 224 periods. 226 Energy control can be as simple as controlling on/off states. 227 But, in many cases, energy control requires understanding the 228 energy object context. For instance, in commercial building 229 during non-business hours, some phones must remain available in 230 case of emergency and office cooling is not usually turned off 231 completely, but the comfort level is reduced. 233 Energy object control therefore requires flexibility and support 234 for different polices and mechanisms: from centralized 235 management by an energy management system, to autonomous control 236 by individual devices, and alignment with dynamic demand- 237 response mechanisms. 239 The EMAN framework power states can be used in demand response 240 scenarios. In response to time-of-day fluctuation of energy 241 costs or grid power shortages, network devices can respond and 242 reduce their energy consumption. 244 1.5. EMAN Framework Application 246 A Network Management System (NMS) is an entity that requests 247 information from compatible devices, typically using the SNMP 248 protocol. An NMS may implement many network management 249 functions, such as security or identity management. An NMS that 250 deals exclusively with energy is called an Energy Management 251 System (EnMS). It may be limited to monitoring energy use, or 252 it may also implement control functions. An EnMS collects 253 energy information for devices in the network. 255 Energy management can be implemented by extending existing SNMP 256 support to the EMAN specific MIBs. SNMP provides an industry 257 proven and well-known mechanism to discover, secure, measure, 258 and control SNMP-enabled end devices. The EMAN framework 259 provides an information and data model to unify access to a 260 large range of devices. 262 2. Scenarios and Target Devices 264 This section presents energy management scenarios that the EMAN 265 framework should solve. Each scenario lists target devices for 266 which the energy management framework can be applied, how the 267 reported-on devices are powered, and how the reporting or 268 control is accomplished. While there is some overlap between 269 some of the use cases, the use cases illustrate network 270 scenarios that the EMAN framework supports. 272 2.1. Network Infrastructure Energy Objects 274 This scenario covers the key use case of network devices and 275 their components. For a device aware of one or more components, 276 our information model supports monitoring and control at the 277 component level. Typically, the chassis draws power from one or 278 more sources and feeds its internal components. It is highly 279 desirable to have monitoring available for individual 280 components, such as line cards, processors, and disk drives as 281 well as peripherals such as USB devices. 283 As an illustrative example, consider a switch with the following 284 grouping of sub-entities for which energy management could be 285 useful. 287 . physical view: chassis (or stack), line cards, and service 288 modules of the switch. 289 . component view: CPU, ASICs, fans, power supply, ports 290 (single port and port groups), storage and memory. 292 The ENTITY-MIB [RFC6933] provides a containment model for 293 uniquely identifying the physical sub-components of network 294 devices. The containment information identifies if one Energy 295 Object belongs to another Energy Object (e.g. a line-card Energy 296 Object contained in a chassis Energy Object). The table 297 entPhysicalContainsTable has an index entPhysicalChildIndex and 298 the MIB object entPhysicalContainedIn which points to the 299 containing 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 that can report 311 on 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 sub cases: 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, like in scenario "Devices Connected to a 352 Network" below. The device is responsible for its own power 353 reporting and control. 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 so is only performed by the supplying 358 device. This scenario is similar to the "Mid-level Manager" 359 below. 361 In sub case (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 it is connected to, while 370 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 the PC is plugged in can be metered for example 378 by a Smart PDU, or unmetered. 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 running on batteries - the PC will report 384 its own energy usage as any other Energy Object to the switch, 385 and the switch can possibly provide aggregation. 387 These two cases are not mutually exclusive. 389 In terms of relationships between entities, the PC has a powered 390 by relationship to the PDU and if the power consumption of the 391 PC is metered by the PDU then there is a metered by relation 392 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 Unit (PDUs) can have inbuilt meters for each 419 socket and so can measure the power supplied to each device in 420 an equipment rack. PDUs typically have remote management 421 functionality 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 so may measure all or part of the total. Utility 426 meters monitor and report accumulated power consumption of the 427 entire 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 metering relationships with devices, and possibly 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. 465 . Reporting: the mid-level manager aggregates the energy data 466 and reports that data to a EnMS or higher mid-level 467 manager. 469 2.6. Non-residential Building System Gateways 471 This use case describes energy management of non-residential 472 buildings. Building Management Systems (BMS) have been in place 473 for many years using legacy protocols not based on IP. In these 474 buildings, a gateway can provide a proxy function between IP 475 networks and legacy building automation protocols. The gateway 476 provides an interface between the EMAN framework and relevant 477 building management protocols. 479 Due to the potential energy savings, energy management of 480 buildings has received significant attention. There are gateway 481 network elements to manage the multiple components of a building 482 energy management system such as Heating, Ventilation, and Air 483 Conditioning (HVAC), lighting, electrical, fire and emergency 484 systems, elevators, etc. The gateway device uses legacy 485 building protocols to communicate with those devices, collects 486 their energy usage, and reports the results. 488 The gateway performs protocol conversion and communicates via 489 RS-232/RS-485 interfaces, Ethernet interfaces, and protocols 490 specific to building management such as BACNET [ASHRAE], MODBUS 491 [MODBUS], or ZigBee [ZIGBEE]. 493 The essential properties of this use case are: 495 . Target devices: building energy management devices - HVAC 496 systems, lighting, electrical, fire and emergency systems. 497 . How powered: any method. 498 . Reporting: the gateway collects energy consumption of non- 499 IP systems and communicates the data via the EMAN 500 framework. 502 2.7. Home Energy Gateways 504 This use case describes the scenario of energy management of a 505 home. The home energy gateway is another example of a proxy 506 that interfaces to electrical appliances and other devices in a 507 home. This gateway can monitor and manage electrical equipment 508 (e.g. refrigerator, heating/cooling, or washing machine) using 509 one of the many protocols that are being developed for 510 residential devices. 512 Beyond simply metering, it's possible to implement energy saving 513 policies based on time of day, occupancy, or energy pricing from 514 the utility grid. The EMAN information model can be applied to 515 energy management of a home. 517 The essential properties of this use case are: 519 . Target devices: home energy gateway and smart meters in a 520 home. 521 . How powered: any method. 522 . Reporting: home energy gateway can collect power 523 consumption of device in a home and possibly report the 524 metering reading to the utility. 526 While the common case is of a home drawing all power from the 527 utility, some buildings/homes can produce and consume energy 528 with reduced or zero net importing energy from the utility grid. 529 There are many energy production technologies such as solar 530 panels, wind turbines, or micro generators. This use case 531 illustrates the concept of self-contained energy generation, 532 consumption and possibly the aggregation of the energy use of 533 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 though 542 a 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 at the network level, Power Distribution Unit (PDU) level, and 553 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 in the event of a power outage. A UPS can provide 558 backup power for many devices in a data center for a finite 559 period of time. Energy monitoring of energy storage capacity is 560 vital from a data center network operations point of view. 562 Presently, the UPS MIB can be useful in monitoring the battery 563 capacity, the input load to the UPS and the output load from the 564 UPS. Currently, there is no link between the UPS MIB and the 565 ENTITY MIB. 567 In addition to monitoring the power consumption of a data 568 center, additional power characteristic should be monitored. 569 Some of these are dynamic variations in the input power supply 570 from the grid referred to as power quality metrics. It can also 571 be useful to monitor how efficiently the devices utilize power. 573 Nameplate capacity of the data center can be estimated from the 574 nameplate ratings (the worst case possible power draw) of IT 575 equipment at a site. 577 The essential properties of this use case are: 579 . Target devices: IT devices in a data center, such as 580 network equipment, servers, and storage devices, as well as 581 power and cooling infrastructure. 582 . How powered: any method but commonly by one or more PDUs. 583 . Reporting: devices may report on their own behalf, or for 584 other connected devices as described in other use cases. 586 2.9. Energy Storage Devices 588 There are two types of devices with energy storage: those whose 589 primary function is to provide power to another device (e.g. a 590 UPS), and those with a different primary function, but which 591 have energy storage as a component (e.g. a notebook). This use 592 case covers both. 594 The energy storage can be a conventional battery, or any other 595 means to store electricity such as a hydrogen cell. 597 An internal battery can be a back-up or an alternative source of 598 power to mains power. As batteries have a finite capacity and 599 lifetime, means for reporting the actual charge, age, and state 600 of a battery are required. An internal battery can be viewed as 601 a component of a device and so be contained within the device 602 from an ENTITY-MIB perspective. 604 Battery systems are used in mobile telecom towers including for 605 use in remote locations. It is important to monitor the 606 remaining battery life and raise an alarm when this falls below 607 a threshold. 609 The essential properties of this use case are: 611 . Target devices: devices that have an internal battery or 612 external storage. 613 . How powered: from batteries or other storage devices. 614 . Reporting: the device reports on its power delivered and 615 state. 617 2.10. Industrial Automation Networks 619 Energy consumption statistics in the industrial sector are 620 staggering. The industrial sector alone consumes about half of 621 the world's total delivered energy, and is a significant user of 622 electricity. Thus, the need for optimization of energy usage in 623 this sector is natural. 625 Industrial facilities consume energy in process loads, and in 626 non-process loads. 628 The essential properties of this use case are: 630 . Target devices: devices used in an industrial sector. 631 . How powered: any method. 632 . Reporting: currently, CIP protocol is currently used for 633 reporting energy for these devices. 635 2.11. Printers 637 This use case describes the scenario of energy monitoring and 638 management of printers. Printers in this use case stand in for 639 all imaging equipment, also including multi-function devices 640 (MFDs), scanners, fax machines, and mailing machines. 642 Energy use of printers has been an industry concern for several 643 decades, and they usually have sophisticated power management 644 with a variety of low-power modes, particularly for managing 645 energy-intensive thermo-mechanical components. Printers also 646 have long made extensive use of SNMP for end-user system 647 interaction and for management generally, and cross-vendor 648 management systems manage fleets of printers in enterprises. 649 Power consumption during active modes can vary widely, with high 650 peak levels. 652 Printers can expose detailed power state information, distinct 653 from operational state information, with some printers reporting 654 transition states between stable long-term states. Many also 655 support active setting of power states, and setting of policies 656 such as delay times when no activity will cause automatic 657 transition to a lower power mode. Other features include 658 reporting on components, counters for state transitions, typical 659 power levels by state, scheduling, and events/alarms. 661 Some large printers also have a "Digital Front End" which is a 662 computer that performs functions on behalf of the physical 663 imaging system. These typically have their own presence on the 664 network and are sometimes separately powered. 666 There are some unique characteristics of printers from the point 667 of view energy management. While the printer is not in use, 668 there are timer based low power states, which consume little 669 power. On the other hand, while the printer is printing or 670 copying the cylinder needs to be heated so that power 671 consumption is quite high but only for a short period of time. 672 Given this work load, periodic polling of power levels alone 673 would not suffice. 675 The essential properties of this use case are: 677 . Target devices: all imaging equipment. 678 . How powered: typically AC from a wall outlet. 679 . Reporting: devices report for themselves. 681 2.12. Off-Grid Devices 683 This use case concerns self-contained devices that use energy 684 but are not connected to an infrastructure power delivery grid. 685 These devices typically produce energy from sources such as 686 solar energy, wind power, or fuel cells. The device generally 687 contains a closely coupled combination of 689 . power generation component(s) 690 . power storage component(s) (e.g., battery) 691 . power consuming component(s) 693 With renewable power, the energy input is often affected by 694 variations in weather. These devices therefore require energy 695 management both for internal control and remote reporting of 696 their state. 698 In many cases these devices are expected to operate 699 autonomously, as continuous communications for the purposes of 700 remote control is not available. Non continuous polling 701 requires the ability to store and access later the information 702 acquired while off-line. 704 The essential properties of this use case are: 706 Target Devices: remote area devices that produce and consume 707 energy. 708 How Powered: site energy sources. 709 Reporting: devices report their power usage, but not 710 necessarily continuously. 712 2.13. Demand Response 714 The theme of demand response from a utility grid spans across 715 several use cases. In some situations, in response to time-of- 716 day fluctuation of energy costs or sudden energy shortages due 717 power outages, it may be important to respond and reduce the 718 energy consumption of the network. 720 From the EMAN use case perspective, the demand response scenario 721 can apply to a data center, building or home. Real-time energy 722 monitoring is usually a pre-requisite. Then based on the 723 potential energy shortfall, the EnMS could formulate a suitable 724 response. The EnMS could shut down selected devices that are 725 considered lower priority or uniformly reduce the power supplied 726 to a class of devices. For multi-site data centers it may be 727 possible to formulate policies such as follow-the-sun type of 728 approach, by scheduling the mobility of VMs across data centers 729 in different geographical locations. 731 The essential properties of this use case are: 733 Target Devices: any device. 734 How Powered: traditional mains AC power. 735 Control: demand response based upon policy or priority. 737 2.14. Power Capping 739 The purpose of power-capping is to run a server without 740 exceeding a power usage threshold to remain under the critical 741 available power threshold; it can be useful for power limited 742 data centers. Based on workload measurements, a device can 743 choose the optimal power state in terms of performance and power 744 consumption. When the server operates at less than the power 745 supply capacity, it runs at full speed. When the power 746 requirements would be greater than the power supply, it runs in 747 a reduced power mode so that its power consumption matches the 748 available power. 750 The essential properties of this use case are: 752 Target Devices: IT devices in a data center. 753 How Powered: traditional mains AC power. 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 and metering 788 and control are performed by the same power source 790 - energy objects that have multiple power sources supplying 791 power to the device and metering is performed by one or more 792 sources and control is performed by another source 794 4. Relationship of EMAN to other Standards 796 The EMAN framework is tied to other standards and efforts that 797 deal with energy. EMAN leverages existing standards when 798 possible, and it helps enable adjacent technologies such as 799 Smart Grid. 801 The standards most relevant and applicable to EMAN are listed 802 below with a brief description of their objectives, the current 803 state and how that standard relates to EMAN. 805 4.1. Data Model and Reporting 807 4.1.1. IEC - CIM 809 The International Electrotechnical Commission (IEC) has 810 developed a broad set of standards for power management. Among 811 these, the most applicable to EMAN is IEC 61850, a standard for 812 the design of electric utility automation. The abstract data 813 model defined in 61850 is built upon and extends the Common 814 Information Model (CIM). The complete 61850 CIM model includes 815 over a hundred object classes and is widely used by utilities 816 worldwide. 818 This set of standards was originally conceived to automate 819 control of a substation (facilities which transfer electricity 820 from the transmission to the distribution system). However, the 821 extensive data model has been widely used in other domains, 822 including Energy Management Systems (EnMS). 824 IEC TC57 WG19 is an ongoing working group to harmonize the CIM 825 data model and 61850 standards. 827 Several concepts from IEC Standards have been reused in the EMAN 828 drafts. In particular, AC Power Quality measurements have been 829 reused from IEC 61850-7-4. The concept of Accuracy Classes for 830 measure of power and energy has been adapted from ANSI C12.20 831 and IEC standards 62053-21 and 62053-22. 833 4.1.2. DMTF 835 The Distributed Management Task Force (DMTF) has defined a Power 836 State Management profile [DMTF DSP1027] for managing computer 837 systems using the DMTF's Common Information Model (CIM). These 838 specifications provide physical, logical, and virtual system 839 management requirements for power-state control services. The 840 DMTF standard does not include energy monitoring. 842 The Power State Management profile is used to describe and 843 manage the Power State of computer systems. This includes 844 controlling the Power State of an entity for entering sleep 845 mode, re-awaking, and rebooting. The EMAN framework references 846 the DMTF Power Profile and Power State Set. 848 4.1.2.1. Common Information Model Profiles 850 The DMTF uses CIM-based (Common Information Model) 'Profiles' to 851 represent and manage power utilization and configuration of 852 managed elements (note that this is not the 61850 CIM). Key 853 profiles for energy management are 'Power Supply' (DSP 1015), 854 'Power State' (DSP 1027) and 'Power Utilization Management' (DSP 855 1085). These profiles define many features for monitoring and 856 configuration of a Power Managed Element's static and dynamic 857 power saving modes, power allocation limits and 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 TransitingToPowerState 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 provides management and control of managed 881 elements like power, CPU, etc. using the DMTF's WS-Management 882 web services and CIM data model. 884 Both in-service and out-of-service systems can be managed with 885 the DASH specification in a fully secured remote environment. 887 Full power lifecycle management is possible using out-of-band 888 management. 890 4.1.3. ODVA 892 The Open DeviceNet Vendors Association (ODVA) is an association 893 for industrial automation companies and defines the Common 894 Industrial Protocol (CIP). Within ODVA, there is a special 895 interest group focused on energy and standardization and inter- 896 operability of energy-aware devices. 898 The ODVA is developing an energy management framework for the 899 industrial sector. There are synergies and similar concepts 900 between the ODVA and EMAN approaches to energy monitoring and 901 management. 903 ODVA defines a three-part approach towards energy management: 904 awareness of energy usage, consuming energy more efficiently, 905 and exchanging energy with the utility or others. Energy 906 monitoring and management promote efficient consumption and 907 enable automating actions that reduce energy consumption. 909 The foundation of the approach is the information and 910 communication model for entities. An entity is a network- 911 connected, energy-aware device that has the ability to either 912 measure or derive its energy usage based on its native 913 consumption or generation of energy, or report a nominal or 914 static energy value. 916 4.1.4. Ecma SDC 918 The Ecma International standard on Smart Data Centre [Ecma-SDC] 919 defines semantics for management of entities in a data center 920 such as servers, storage, and network equipment. It covers 921 energy as one of many functional resources or attributes of 922 systems for monitoring and control. It only defines messages 923 and properties, and does not reference any specific protocol. 924 Its goal is to enable interoperability of such protocols as 925 SNMP, BACNET, and HTTP by ensuring a common semantic model 926 across them. Four power states are defined, Off, Sleep, Idle, 927 and Active. The standard does not include actual energy or 928 power measurements. 930 When used with EMAN, the SDC standard will provide a thin 931 abstraction on top of the more detailed data model available in 932 EMAN. 934 4.1.5. PWG 936 The IEEE-ISTO Printer Working Group (PWG) defines open standards 937 for printer related protocols, for the benefit of printer 938 manufacturers and related software vendors. The Printer WG 939 covers power monitoring and management of network printers and 940 imaging systems in the PWG Power Management Model for Imaging 941 Systems [PWG5106.4]. Clearly, these devices are within the 942 scope of energy management since these devices receive power and 943 are attached to the network. In addition, there is ample scope 944 of power management since printers and imaging systems are not 945 used that often. 947 The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB 948 modules for printer management and in particular a "PWG Power 949 Management Model for Imaging Systems v1.0" [PWG5106.4] and a 950 companion SNMP binding in the "PWG Imaging System Power MIB 951 v1.0" [PWG5106.5]. This PWG model and MIB are harmonized with 952 the DMTF CIM Infrastructure [DMTF DSP0004] and DMTF CIM Power 953 State Management Profile [DMTF DSP1027] for power states and 954 alerts. 956 These MIB modules can be useful for monitoring the power and 957 Power State of printers. The EMAN framework takes into account 958 the standards defined in the Printer working group. The PWG may 959 harmonize its MIBs with those from EMAN. The PWG covers many 960 topics in greater detail than EMAN, as well as some that are 961 specific to imaging equipment. The PWG also provides for 962 vendor-specific extension states (beyond the standard DMTF CIM 963 states). 965 The IETF Printer MIB RFC3805 [RFC3805] has been standardized, 966 however, this MIB module does not address power management. 968 4.1.6. ASHRAE 970 In the U.S., there is an extensive effort to coordinate and 971 develop standards related to the "Smart Grid". The Smart Grid 972 Interoperability Panel, coordinated by the government's National 973 Institute of Standards and Technology, identified the need for a 974 building side information model (as a counterpart to utility 975 models) and specified this in Priority Action Plan (PAP) 17. 976 This was designated to be a joint effort by the American Society 977 of Heating, Refrigerating and Air-Conditioning Engineers 978 (ASHRAE) and the National Electrical Manufacturers Association 979 (NEMA), both ANSI approved SDO's. The result is to be an 980 information model, not a protocol. 982 The ASHRAE effort addresses data used only within a building as 983 well as data that may be shared with the grid, particularly as 984 it relates to coordinating future demand levels with the needs 985 of the grid. The model is intended to be applied to any 986 building type, both residential and commercial. It is expected 987 that existing protocols will be adapted to comply with the new 988 information model, as would new protocols. 990 There are four basic types of entities in the model: generators, 991 loads, meters, and energy managers. The metering part of the 992 model overlaps with the EMAN framework to a large degree, though 993 there are features unique to each. The load part speaks to 994 control capabilities well beyond what EMAN covers. Details of 995 generation and of the energy management function are outside of 996 EMAN scope. 998 A public review draft of the ASHRAE standard was released in 999 July, 2012. There are no apparent major conflicts between the 1000 two approaches, but there are areas where some harmonization is 1001 possible. 1003 4.1.7. ANSI/CEA 1005 The Consumer Electronics Association (CEA) has approved 1006 ANSI/CEA-2047 [ANSICEA] as a standard data model for Energy 1007 Usage Information. The primary purpose is to enable home 1008 appliances and electronics to communicate energy usage 1009 information over a wide range of technologies with pluggable 1010 modules that contain the physical layer electronics. The 1011 standard can be used by devices operating on any home network 1012 including Wi-Fi, Ethernet, ZigBee, Z-Wave, Bluetooth, and 1013 others. The Introduction to ANSI/CEA-2047 states that "This 1014 standard provides an information model for other groups to 1015 develop implementations specific to their network, protocol and 1016 needs". It covers device identification, current power level, 1017 cumulative energy consumption, and provides for reporting time- 1018 series data. 1020 4.1.8. ZigBee 1022 The ZigBee Smart Energy Profile 2.0 (SEP) effort [ZIGBEE] 1023 focuses on IP-based wireless communication to appliances and 1024 lighting. It is intended to enable internal building energy 1025 management and provide for bi-directional communication with the 1026 power grid. 1028 ZigBee protocols are intended for use in embedded applications 1029 with low data rates and low power consumption. ZigBee defines a 1030 general-purpose, inexpensive, self-organizing mesh network that 1031 can be used for industrial control, embedded sensing, medical 1032 data collection, smoke and intruder warning, building 1033 automation, home automation, etc. 1035 ZigBee is currently not an ANSI recognized SDO. 1037 The EMAN framework addresses the needs of IP-enabled networks 1038 through the usage of SNMP, while ZigBee looks for completely 1039 integrated and inexpensive mesh solution. 1041 4.2. Measurement 1043 4.2.1. ANSI C12 1045 The American National Standards Institute (ANSI) has defined a 1046 collection of power meter standards under ANSI C12. The primary 1047 standards include communication protocols (C12.18, 21 and 22), 1048 data and schema definitions (C12.19), and measurement accuracy 1049 (C12.20). European equivalent standards are provided by IEC 1050 62053-22 1052 These standards are oriented to the meter itself, are very 1053 specific, and used by electricity distributors and producers. 1055 The EMAN standard references ANSI C12.20 accuracy classes. 1057 4.2.2. IEC 62301 1059 IEC 62301, "Household electrical appliances Measurement of 1060 standby power", [IEC62301] specifies a power level measurement 1061 procedure. While nominally for appliances and low-power modes, 1062 many aspects of it apply to other device types and modes and it 1063 is commonly referenced in test procedures for energy using 1064 products. 1066 While the standard is intended for laboratory measurements of 1067 devices in controlled conditions, many aspects of it are 1068 informative to those implementing measurement in products that 1069 ultimately report via EMAN. 1071 4.3. Other 1073 4.3.1. ISO 1075 The International Organization for Standardization (ISO) [ISO] 1076 is developing an energy management standard, ISO 50001, to 1077 complement ISO 9001 for quality management, and ISO 14001 for 1078 environmental management. The intent is to facilitate the 1079 creation of energy management programs for industrial, 1080 commercial, and other entities. The standard defines a process 1081 for energy management at an organization level. It does not 1082 define the way in which devices report energy and consume 1083 energy. 1085 ISO 50001 is based on the common elements found in all of ISO's 1086 management system standards, assuring a high level of 1087 compatibility with ISO 9001 and ISO 14001. ISO 50001 benefits 1088 include: 1090 o Integrating energy efficiency into management practices and 1091 throughout the supply chain 1092 o Energy management best practices and good energy management 1093 behaviors 1094 o Benchmarking, measuring, documenting, and reporting energy 1095 intensity improvements and their projected impact on 1096 reductions in greenhouse gas (GHG) emissions 1097 o Evaluating and prioritizing the implementation of new energy- 1098 efficient technologies 1100 ISO 50001 has been developed by ISO project committee ISO PC 1101 242, Energy management. EMAN is complementary to ISO 9001. 1103 4.3.2. Energy Star 1105 The U.S. Environmental Protection Agency (EPA) and U.S. 1106 Department of Energy (DOE) jointly sponsor the Energy Star 1107 program [ESTAR]. The program promotes the development of energy 1108 efficient products and practices. 1110 To qualify as Energy Star, products must meet specific energy 1111 efficiency targets. The Energy Star program also provides 1112 planning tools and technical documentation to encourage more 1113 energy efficient building design. Energy Star is a program; it 1114 is not a protocol or standard. 1116 For businesses and data centers, Energy Star offers technical 1117 support to help companies establish energy conservation 1118 practices. Energy Star provides best practices for measuring 1119 current energy performance, goal setting, and tracking 1120 improvement. The Energy Star tools offered include a rating 1121 system for building performance and comparative benchmarks. 1123 There is no immediate link between EMAN and Energy Star, one 1124 being a protocol and the other a set of recommendations to 1125 develop energy efficient products. However, Energy Star could 1126 include EMAN standards in specifications for future products, 1127 either as required or rewarded with some benefit. 1129 4.3.3. Smart Grid 1131 The Smart Grid standards efforts underway in the United States 1132 are overseen by the U.S. National Institute of Standards and 1133 Technology [NIST]. NIST is responsible for coordinating a 1134 public-private partnership with key energy and consumer 1135 stakeholders in order to facilitate the development of smart 1136 grid standards. These activities are monitored and facilitated 1137 by the SGIP (Smart Grid Interoperability Panel). This group has 1138 working groups for specific topics including homes, commercial 1139 buildings, and industrial facilities as they relate to the grid. 1140 A stated goal of the group is to harmonize any new standard with 1141 the IEC CIM and IEC 61850. 1143 When a working group detects a standard or technology gap, the 1144 team seeks approval from the SGIP for the creation of a Priority 1145 Action Plan (PAP), a private-public partnership to close the 1146 gap. PAP 17 is discussed in section 4.1.6. 1148 PAP 10 addresses "Standard Energy Usage Information". Smart 1149 Grid standards will provide distributed intelligence in the 1150 network and allow enhanced load shedding. For example, pricing 1151 signals will enable selective shutdown of non critical 1152 activities during peak price periods. Both centralized and 1153 distributed management controls. 1155 There is an obvious functional link between Smart Grid and EMAN 1156 in the form of demand response, even though the EMAN framework 1157 itself does not address any coordination with the grid. As EMAN 1158 enables control, it can be used by an EnMS to accomplish demand 1159 response through translation of a signal from an outside entity. 1161 5. Limitations 1163 EMAN addresses the needs of energy monitoring in terms of 1164 measurement and, considers limited control capabilities of 1165 energy monitoring of networks. 1167 EMAN does not create a new protocol stack, but rather defines a 1168 data and information model useful for measuring and reporting 1169 energy and other metrics over SNMP. 1171 EMAN does not address questions regarding Smart Grid, 1172 electricity producers, and distributors. 1174 6. Security Considerations 1176 EMAN uses the SNMP protocol and thus has the functionality of 1177 SNMP's security capabilities. SNMPv3 [RFC3411] provides 1178 important security features such as confidentiality, integrity, 1179 and authentication. 1181 7. IANA Considerations 1183 This memo includes no request to IANA. 1185 8. Acknowledgements 1187 Firstly, the authors thank Emmanuel Tychon for taking the lead 1188 for this draft and his substantial contributions to it. The 1189 authors thank Jeff Wheeler, Benoit Claise, Juergen Quittek, 1190 Chris Verges, John Parello, and Matt Laherty, for their valuable 1191 contributions. The authors thank Georgios Karagiannis for use 1192 case involving energy neutral homes, Elwyn Davies for off-grid 1193 electricity systems, and Kerry Lynn for demand response. 1195 9. References 1197 9.1. Normative References 1199 [RFC3411] An Architecture for Describing Simple Network 1200 Management Protocol (SNMP) Management Frameworks, RFC 1201 3411, December 2002. 1203 [RFC3621] Power Ethernet MIB, RFC 3621, December 2003. 1205 9.2. Informative References 1207 [ACPI] "Advanced Configuration and Power Interface 1208 Specification", http://www.acpi.info/spec30b.htm 1210 [DASH] "Desktop and mobile Architecture for System Hardware", 1211 http://www.dmtf.org/standards/mgmt/dash/ 1213 [DMTF DSP0004] DMTF Common Information Model (CIM) 1214 Infrastructure, DSP0004, May 2009. 1215 http://www.dmtf.org/standards/published_documents/DSP00 1216 04_2.5.0.pdf 1218 [DMTF DSP1027] DMTF Power State Management Profile, DSP1027, 1219 December 2009. 1220 http://www.dmtf.org/standards/published_documents/DSP10 1221 27_2.0.0.pdf 1223 [Ecma-SDC] Ecma-400, "Smart Data Centre Resource Monitoring and 1224 Control (2 Edition)", June 2013. 1226 [EMAN-REQ] Quittek, J., Chandramouli, M. Winter, R., Dietz, T., 1227 Claise, B., and M. Chandramouli, "Requirements for 1228 Energy Management ", RFC 6988, September 2013. 1230 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 1231 Quittek, J. and B. Claise "Energy and Power Monitoring 1232 MIB ", draft-ietf-eman-monitoring-mib-13, May 2015. 1234 [EMAN-AWARE-MIB] J. Parello, B. Claise and Mouli Chandramouli, 1235 "draft-ietf-eman-energy-aware-mib-16", work in 1236 progress, July 2014. 1238 [RFC7326] Claise, B., Parello, J., Schoening, B., J. Quittek, 1239 "Energy Management Framework", RFC7326, September 2014 1240 . 1242 [EMAN-BATTERY-MIB] Quittek, J., Winter, R., and T. Dietz, 1243 "Definition of Managed Objects for Battery Monitoring" 1244 draft-ietf-eman-battery-mib-17.txt, December 2014. 1246 [ESTAR] http://www.energystar.gov/ 1248 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1434 1250 [ASHRAE] http://collaborate.nist.gov/twiki- 1251 sggrid/bin/view/SmartGrid/PAP17Information 1253 [ZIGBEE] http://www.zigBee.org/ 1255 [ANSICEA] ANSI/CEA-2047, Consumer Electronics - Energy Usage 1256 Information (CE-EUI), 2013. 1258 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1337 1260 [PWG5106.4]IEEE-ISTO PWG Power Management Model for Imaging 1261 Systems v1.0, PWG Candidate Standard 5106.4-2011, 1262 February 2011.ftp://ftp.pwg.org/pub/pwg/candidates/cs- 1263 wimspower10-20110214-5106.4.mib 1265 [PWG5106.5] IEEE-ISTO PWG Imaging System Power MIB v1.0, PWG 1266 Candidate Standard 5106.5-2011, February 2011. 1268 [IEC62301] International Electrotechnical Commission, "IEC 62301 1269 Household electrical appliances Measurement of standby 1270 power", Edition 2.0, 2011. 1272 [MODBUS] Modbus-IDA, "MODBUS Application Protocol Specification 1273 V1.1b", December 2006. 1275 [NIST] http://www.nist.gov/smartgrid/ 1277 [RFC3805] Bergman, R., Lewis, H., and I. McDonald, "Printer MIB 1278 v2", RFC 3805, June 2004. 1280 [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M. 1281 Chandramouli, "Entity MIB v4", RFC 6933, May 2013. 1283 Authors' Addresses 1285 Brad Schoening 1286 44 Rivers Edge Drive 1287 Little Silver, NJ 07739 1288 USA 1290 Phone: +1 917 304 7190 1291 Email: brad.schoening@verizon.net 1293 Mouli Chandramouli 1294 Cisco Systems, Inc. 1295 Sarjapur Outer Ring Road 1296 Bangalore 560103 1297 India 1299 Phone: +91 80 4429 2409 1300 Email: moulchan@cisco.com 1302 Bruce Nordman 1303 Lawrence Berkeley National Laboratory 1304 1 Cyclotron Road, 90-4000 1305 Berkeley 94720-8136 1306 USA 1308 Phone: +1 510 486 7089 1309 Email: bnordman@lbl.gov