OPSAWG WG S. Sasidharan Internet-Draft KP. Bhat Expires: August 2, 2010 S. Shreekantaiah Infosys Technologies Ltd. January 29, 2010 MIB for Energy, Efficiency, Throughput and Carbon Emission draft-sreek-powerconsumption-mib-01.txt Abstract This document defines a portion of Management Information Base (MIB) for the Energy consumption, Throughput, Efficiency and Carbon emission in a Network Element. Energy,Throughput and Efficiency are required to calculate the carbon emission of the network element. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 2, 2010. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Sasidharan, et al. Expires August 2, 2010 [Page 1] Internet-Draft Power Consuption MIB January 2010 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Relation to Entity-MIB(RFC 4133) . . . . . . . . . . . . . . . 3 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Sasidharan, et al. Expires August 2, 2010 [Page 2] Internet-Draft Power Consuption MIB January 2010 1. Introduction The carbon emission for a device is calculated as a function of Energy Consumed (Power in Watts) and efficiency (which is dependent on throughput). Mathematically the carbon emission is directly proportional to Energy Consumption Rate (ECR). Again, depending on the utilization of the device, meaning fully utilized, half or idle the ECR will change. For all practical purpose, the carbon emission from a device is calculated considering how much percentage of time the device has been utilized full, half and idle. This document suggests MIb structures for all the parameters required for calculating the carbon emission of a device successfully. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410[RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 4. Overview The global MIB variables defined are for the system as a whole and a table of MIBs are being defined for the indpendent devices within the system. The table is meant for the systems whose independent module energy consumption and throughput can be measured. 5. Relation to Entity-MIB(RFC 4133) The MIB defined in this memo is defined as a part of EntityMIB and Sasidharan, et al. Expires August 2, 2010 [Page 3] Internet-Draft Power Consuption MIB January 2010 implementation of EntityMIB is mandatory for using this MIB. 6. Definitions POWERCONSUMPTION-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, mib-2 FROM SNMPv2-SMI DisplayString FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB entityMIB, entPhysicalIndex FROM ENTITY-MIB; powerConsumptionMib MODULE-IDENTITY LAST-UPDATED "201001050000Z" ORGANIZATION "PowerConsumption Mib Working Group" CONTACT-INFO "Sreekanth Sasidharan, Sahana Shreekantaiah, KrishnaPrasad Bhat E-Mail: sreekanthss@infosys.com, sahana_s@infosys.com, krishnap_bhat@infosys.com" DESCRIPTION "This MIB describes Energy consumption, Throughput, Efficiency and Carbon emission." -- RFC Ed.: replace yyyy with actual RFC number & remove this note REVISION "201001050000Z" -- 05 January 2010 DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy with actual RFC number & remove this note ::= { entityMIB 4 } -- -- Top-level structure -- powerConsumptionNotifications OBJECT IDENTIFIER ::= { powerConsumptionMib 0 } powerConsumptionObjects OBJECT IDENTIFIER ::= { powerConsumptionMib 1 } Sasidharan, et al. Expires August 2, 2010 [Page 4] Internet-Draft Power Consuption MIB January 2010 -- -- Conformance Information -- powerConsumptionConformance OBJECT IDENTIFIER ::= { powerConsumptionMib 2 } powerConsumptionCompliances OBJECT IDENTIFIER ::= { powerConsumptionConformance 1 } powerConsumptionGroups OBJECT IDENTIFIER ::= { powerConsumptionConformance 2 } -- -- The power consumption Table -- powerConsumptionTable OBJECT-TYPE SYNTAX SEQUENCE OF PowerConsumptionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Measuring the Carbon footprint of devices" ::= {powerConsumptionObjects 1} powerConsumptionEntry OBJECT-TYPE SYNTAX PowerConsumptionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "For any instance in the entityMIB for which entPhysicalContainedIn is 0, then row in this table is mandatory" INDEX {entPhysicalIndex} ::= { powerConsumptionTable 1} PowerConsumptionEntry ::= SEQUENCE { powerEnergyConsumptionFull OCTET STRING, powerThroughputFull OCTET STRING, powerEffeciencyFull OCTET STRING, powerEnergyConsumptionHalf OCTET STRING, powerThroughputHalf OCTET STRING, powerEffeciencyHalf OCTET STRING, powerEnergyConsumptionIdle OCTET STRING, powerThroughputIdle OCTET STRING, powerEffeciencyIdle OCTET STRING, powerLoad OCTET STRING, powerCo2Emission OCTET STRING, powerEffeciencyPercentageFull OCTET STRING, powerEffeciencyPercentageHalf OCTET STRING, powerEffeciencyPercentageIdle OCTET STRING } Sasidharan, et al. Expires August 2, 2010 [Page 5] Internet-Draft Power Consuption MIB January 2010 powerEnergyConsumptionFull OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Energy Consumption measured in watts when resource is running at full capacity (Full throughput)" ::= {powerConsumptionEntry 1} powerThroughputFull OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Throughput measured in Gbps when the resource is running at full capacity" ::= {powerConsumptionEntry 2} powerEffeciencyFull OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "It is a function of EnergyConsumption and Throughput( or utilization) when resource is running at full capacity" ::= {powerConsumptionEntry 3} powerEnergyConsumptionHalf OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Energy Consumption measured in watts when resource is running at full capacity (Full throughput)" ::= {powerConsumptionEntry 4} powerThroughputHalf OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Throughput measured in Gbps when the resource is running at half capacity" ::= {powerConsumptionEntry 5} powerEffeciencyHalf OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "It is a function of EnergyConsumption and Sasidharan, et al. Expires August 2, 2010 [Page 6] Internet-Draft Power Consuption MIB January 2010 Throughput( or utilization) when resource is running at half capacity" ::= {powerConsumptionEntry 6} powerEnergyConsumptionIdle OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Energy Consumption measured in watts when the resource is idle" ::= {powerConsumptionEntry 7} powerThroughputIdle OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Throughput measured in Gbps when the resource is idle" ::= {powerConsumptionEntry 8} powerEffeciencyIdle OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "It is a function of EnergyConsumption and Throughput( or utilization) when resource is idle" ::= {powerConsumptionEntry 9} powerLoad OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Load is the total power consumption which is measured as a function of load and throughput" ::= {powerConsumptionEntry 10} powerCo2Emission OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..16)) MAX-ACCESS read-only STATUS current DESCRIPTION "The total Co2 emission is calculated as a function of total effeciency and load" ::= {powerConsumptionEntry 11} powerEffeciencyPercentageFull OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..8)) Sasidharan, et al. Expires August 2, 2010 [Page 7] Internet-Draft Power Consuption MIB January 2010 MAX-ACCESS read-write STATUS current DESCRIPTION "Percentage of the equipment running on full load" ::= {powerConsumptionEntry 12} powerEffeciencyPercentageHalf OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..8)) MAX-ACCESS read-write STATUS current DESCRIPTION "Percentage of the equipment running on half load" ::= {powerConsumptionEntry 13} powerEffeciencyPercentageIdle OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..8)) MAX-ACCESS read-write STATUS current DESCRIPTION "Percentage of the equipment being idle" ::= {powerConsumptionEntry 14} -- -- Compliance Statements -- powerConsumptionCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for network elements that implement methods to calculate Carbon Emission" MODULE -- this module MANDATORY-GROUPS {powerConsumptionGroup } ::= { powerConsumptionCompliances 1 } -- -- Units of Conformance -- powerConsumptionGroup OBJECT-GROUP OBJECTS { powerEnergyConsumptionFull, powerThroughputFull, powerEffeciencyFull, powerEnergyConsumptionHalf, powerThroughputHalf, powerEffeciencyHalf, powerEnergyConsumptionIdle, Sasidharan, et al. Expires August 2, 2010 [Page 8] Internet-Draft Power Consuption MIB January 2010 powerThroughputIdle, powerEffeciencyIdle, powerLoad, powerCo2Emission, powerEffeciencyPercentageFull, powerEffeciencyPercentageHalf, powerEffeciencyPercentageIdle } STATUS current DESCRIPTION "Collection of objects for finding the power consumption by individual modules in a network element. Example can be a router or line card in a router" ::= { powerConsumptionGroups 2 } END 7. Security Considerations There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the objects and their sensitivity/ vulnerability: o powerEffeciencyPercentageFull, powerEffeciencyPercentageHalf, powerEffeciencyPercentageIdle - Changing these values will impact the calculation of carbon footprint of the individual resource in the device. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. In this MIB module, possible effects that can be induced by GET and/or NOTIFY operations include: SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), there is still no control over whom on the secure network is allowed Sasidharan, et al. Expires August 2, 2010 [Page 9] Internet-Draft Power Consuption MIB January 2010 to access (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to access (read/change/create/delete) them. 8. Acknowledgments Authors would like to acknowledge Mr. Bharat Joshi for the guidence in creating the RFC draft. 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005. Sasidharan, et al. Expires August 2, 2010 [Page 10] Internet-Draft Power Consuption MIB January 2010 9.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. Authors' Addresses Sreekanth Sasidharan Infosys Technologies Ltd. 44 Electronics City, Hosur Road Bangalore 560 100 India Email: sreekanthss@infosys.com URI: http://www.infosys.com/ Krishna Prasad Bhat Infosys Technologies Ltd. 44 Electronics City, Hosur Road Bangalore 560 100 India Email: KrishnaP_Bhat@infosys.com URI: http://www.infosys.com/ Sahana Shreekantaiah Infosys Technologies Ltd. 44 Electronics City, Hosur Road Bangalore 560 100 India Email: Sahana_S@infosys.com URI: http://www.infosys.com/ Sasidharan, et al. Expires August 2, 2010 [Page 11]