draft-ietf-eman-energy-monitoring-mib-06.txt   draft-ietf-eman-energy-monitoring-mib-07.txt 
Network Working Group M. Chandramouli Network Working Group M. Chandramouli
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening Intended Status: Standards Track B. Schoening
Expires: February 15, 2014 Independent Consultant Expires: April 21, 2014 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
B. Claise B. Claise
Cisco Systems, Inc. Cisco Systems, Inc.
July 15, 2013 October 21, 2013
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-06 draft-ietf-eman-energy-monitoring-mib-07
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance This Internet-Draft is submitted to IETF in full conformance
with the provisions of BCP 78 and BCP 79. with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed The list of Internet-Draft Shadow Directories can be accessed
at http://www.ietf.org/shadow.html at http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 2014. This Internet-Draft will expire on April 2014.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED"
"MAY", and "OPTIONAL" in this document are to be interpreted as "MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119]. described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction............................................. 3 1. Introduction.............................................. 3
2. The Internet-Standard Management Framework............... 4 2. The Internet-Standard Management Framework................ 4
3. Use Cases................................................ 4 3. Use Cases................................................. 4
4. Terminology.............................................. 5 4. Terminology............................................... 5
5. Architecture Concepts Applied to the MIB Module.......... 6 5. Architecture Concepts Applied to the MIB Module........... 6
5.1. Energy Object Information............................. 13 5.1. Energy Object Information.............................. 13
5.2. Power State........................................... 14 5.2. Power State............................................ 14
5.2.1. Power State Set................................14 5.2.1. Power State Set................................ 15
5.3. Energy Object Usage Information....................... 15 5.3. Energy Object Usage Information........................ 15
5.4. Optional Power Usage Attributes....................... 16 5.4. Optional Power Usage Attributes........................ 16
5.5. Optional Energy Measurement........................... 17 5.5. Optional Energy Measurement............................ 17
5.6. Fault Management...................................... 21 5.6. Fault Management....................................... 21
6. Discovery............................................... 21 6. Discovery................................................ 21
7. Link with the other IETF MIBs........................... 22 7. Link with the other IETF MIBs............................ 22
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..22 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB...22
7.2. Link with the ENTITY-STATE MIB......................23 7.2. Link with the ENTITY-STATE MIB.......................23
7.3. Link with the POWER-OVER-ETHERNET MIB...............24 7.3. Link with the POWER-OVER-ETHERNET MIB................24
7.4. Link with the UPS MIB...............................24 7.4. Link with the UPS MIB................................25
7.5. Link with the LLDP and LLDP-MED MIBs................25 7.5. Link with the LLDP and LLDP-MED MIBs.................26
8. Implementation Scenario................................. 26 8. Implementation Scenario.................................. 26
9. Structure of the MIB.................................... 28 9. Structure of the MIB..................................... 29
10. MIB Definitions........................................ 29 10. MIB Definitions......................................... 30
11. Implementation Status.................................. 70 11. Implementation Status................................... 70
12. Security Considerations................................ 70 11.1. SNMP Research......................................... 71
13. IANA Considerations.................................... 71 11.2. Cisco Systems......................................... 71
13.1. IANA Considerations for the MIB Modules.............. 71 12. Security Considerations................................. 72
13.2. IANA Registration of new Power State Set............. 72 13. IANA Considerations..................................... 73
13.2.1. IANA Registration of the IEEE1621 Power State Set..72 13.1. IANA Considerations for the MIB Modules............... 73
13.2.2. IANA Registration of the DMTF Power State Set......72 13.2. IANA Registration of new Power State Set.............. 73
13.2.3. IANA Registration of the EMAN Power State Set.....73 13.2.1. IANA Registration of the IEEE1621 Power State Set..74
13.2.2. IANA Registration of the DMTF Power State Set......74
13.2.3. IANA Registration of the EMAN Power State Set......74
13.3. Updating the Registration of Existing Power State 13.3. Updating the Registration of Existing Power State
Sets....................................................... 73 Sets........................................................ 74
12. Contributors........................................... 73 12. Contributors............................................ 75
13. Acknowledgment......................................... 74 13. Acknowledgment.......................................... 75
14. Open Issues............................................ 74 14. Open Issues............................................. 75
15. References............................................. 74 15. References.............................................. 76
15.2. Normative References...............................74 15.2. Normative References............................... 76
15.3. Informative References.............................75 15.3. Informative References............................. 76
1. Introduction 1. Introduction
This document defines a subset of the Management Information This document defines a subset of the Management Information
Base (MIB) for use in energy management of devices within or Base (MIB) for use in energy management of devices within or
connected to communication networks. The MIB modules in this connected to communication networks. The MIB modules in this
document are designed to provide a model for energy management, document are designed to provide a model for energy management,
which includes monitoring for power state and energy consumption which includes monitoring for power state and energy consumption
of networked elements. This MIB takes into account the Energy of networked elements. This MIB takes into account the Energy
Management Framework [EMAN-FMWK], which in turn, is based on the Management Framework [EMAN-FMWK], which in turn, is based on the
skipping to change at page 4, line 20 skipping to change at page 4, line 22
dependent attached devices, such as a switch with PoE endpoints dependent attached devices, such as a switch with PoE endpoints
or a power distribution unit with attached endpoints. or a power distribution unit with attached endpoints.
Devices and their sub-components can be modeled using the Devices and their sub-components can be modeled using the
containment tree of the ENTITY-MIB [RFC6933]. In addition, containment tree of the ENTITY-MIB [RFC6933]. In addition,
ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] provides a framework ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] provides a framework
for modeling the relationship between Energy Objects. It is for modeling the relationship between Energy Objects. It is
conceivable to have implementations of ENERGY-AWARE-MIB and conceivable to have implementations of ENERGY-AWARE-MIB and
ENERGY-OBJECT-MIB for modeling the relationships between Energy ENERGY-OBJECT-MIB for modeling the relationships between Energy
Objects and also monitoring the Energy consumption. In some Objects and also monitoring the Energy consumption. In some
stuations, it is possible to have implementation of ENERGY- situations, it is possible to have implementation of ENERGY-
OBJECT-MIB along with the requirement of Module Compliance of OBJECT-MIB along with the requirement of Module Compliance of
ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance
should be supported which requires 3 MIB objects should be supported which requires 3 MIB objects
(entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be (entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be
implemented. implemented.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the
current Internet-Standard Management Framework, please refer to current Internet-Standard Management Framework, please refer to
skipping to change at page 8, line 46 skipping to change at page 8, line 50
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersSampleRate (7) | eoEnergyParametersSampleRate (7)
| +-- r-n RowStatus eoEnergyParametersStatus (8) | +-- r-n RowStatus eoEnergyParametersStatus (8)
| |
+eoEnergyTable(5) +eoEnergyTable(5)
+---eoEnergyEntry(1) [ eoEnergyParametersIndex, +---eoEnergyEntry(1) [ eoEnergyParametersIndex,
eoEnergyCollectionStartTime] eoEnergyCollectionStartTime]
| |
| +-- r-n TimeTicks eoEnergyCollectionStartTime (1) | +-- r-n TimeTicks eoEnergyCollectionStartTime (1)
| +-- r-n Integer32 eoEnergyConsumed (2) | +-- r-n Integer32 eoEnergyConsumed (2)
| +-- r-n Integer32 eoEnergyProduced (3) | +-- r-n Integer32 eoEnergyProvided (3)
| +-- r-n Integer32 eoEnergyNet (4) | +-- r-n Integer32 eoEnergyStored (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoEnergyUnitMultiplier (5) | eoEnergyUnitMultiplier (5)
| +-- r-n Integer32 eoEnergyAccuracy(6) | +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyMaxConsumed (7) | +-- r-n Integer32 eoEnergyMaxConsumed (7)
| +-- r-n Integer32 eoEnergyMaxProduced (8) | +-- r-n Integer32 eoEnergyMaxProduced (8)
| +-- r-n TimeTicks | +-- r-n TimeTicks
| eoEnergyDiscontinuityTime(9) | eoEnergyDiscontinuityTime(9)
The powerAttributesMIB consists of four tables. The powerAttributesMIB consists of four tables.
eoACPwrAttributesTable is indexed by entPhysicalIndex. eoACPwrAttributesTable is indexed by entPhysicalIndex.
skipping to change at page 12, line 4 skipping to change at page 12, line 8
| eoEnergyParametersIndex | | eoEnergyParametersIndex |
| eoEnergyParametersIntervalLength | | eoEnergyParametersIntervalLength |
| eoEnergyParametersIntervalNumber | | eoEnergyParametersIntervalNumber |
| eoEnergyParametersIntervalMode | | eoEnergyParametersIntervalMode |
| eoEnergyParametersIntervalWindow | | eoEnergyParametersIntervalWindow |
| eoEnergyParametersSampleRate | | eoEnergyParametersSampleRate |
| eoEnergyParametersStatus | | eoEnergyParametersStatus |
+----------------------------------+ +----------------------------------+
| |
V V
+----------------------------------+ +----------------------------------+
| Energy Table | | Energy Table |
| -------------------------------- | | -------------------------------- |
| eoEnergyCollectionStartTime | | eoEnergyCollectionStartTime |
| eoEnergyConsumed | | eoEnergyConsumed |
| eoEnergyProduced | | eoEnergyProvided |
| eoEnergyNet | | eoEnergyStored |
| eoEnergyUnitMultiplier | | eoEnergyUnitMultiplier |
| eoEnergyAccuracy | | eoEnergyAccuracy |
| eoEnergyMaxConsumed | | eoEnergyMaxConsumed |
| eoEnergyMaxProduced | | eoEnergyMaxProduced |
| eoDiscontinuityTime | | eoDiscontinuityTime |
+----------------------------------+ +----------------------------------+
+-----------------------+ +-----------------------+
|---> | Energy Object ID (*) | |---> | Energy Object ID (*) |
| | --------------------- | | | --------------------- |
skipping to change at page 13, line 22 skipping to change at page 13, line 26
| +------------------------------------------------+ | +------------------------------------------------+
|---- | AC Input DEL Configuration | |---- | AC Input DEL Configuration |
| | ---------------------------------------------- | | | ---------------------------------------------- |
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage | | | eoACPwrAttributesDelPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage | | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdCurrent | | | eoACPwrAttributesDelThdCurrent |
| +------------------------------------------------+ | +------------------------------------------------+
| |
| +----------------------------------------------+ | +----------------------------------------------+
|---- | AC Input WYE Configuration | |---- | AC Input WYE Configuration |
| -------------------------------------------- | | ---------------------------------------------|
| eoACPwrAttributesWyePhaseToNeutralVoltage | | eoACPwrAttributesWyePhaseToNeutralVoltage |
| eoACPwrAttributesWyePhaseCurrent | | eoACPwrAttributesWyePhaseCurrent |
| eoACPwrAttributesWyeThdPhaseToNeutralVoltage | | eoACPwrAttributesWyeThdPhaseToNeutralVoltage |
+----------------------------------------------+ +----------------------------------------------+
Figure 2: UML diagram for the powerAttributesMIB Figure 2: UML diagram for the powerAttributesMIB
(*) Compliance with the ENERGY-AWARE-MIB (*) Compliance with the ENERGY-AWARE-MIB
5.1. Energy Object Information 5.1. Energy Object Information
skipping to change at page 19, line 38 skipping to change at page 19, line 44
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. eoEnergyParametersIntervalLength is ignored.
The eoEnergyParametersStatus is used to start and stop energy The eoEnergyParametersStatus is used to start and stop energy
usage logging. The status of this variable is "active" when usage logging. The status of this variable is "active" when
all the objects in eoEnergyParametersTable are appropriate which all the objects in eoEnergyParametersTable are appropriate which
in turn indicates if eoEnergyTable entries exist or not. in turn indicates if eoEnergyTable entries exist or not.
The eoEnergyTable consists of energy measurements in The eoEnergyTable consists of energy measurements in
eoEnergyConsumed, eoEnergyProduced and eoEnergyNet, the units of eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units
the measured energy eoEnergyUnitMultiplier, and the maximum of the measured energy eoEnergyUnitMultiplier, and the maximum
observed energy within a window eoEnergyMaxConsumed, observed energy within a window eoEnergyMaxConsumed,
eoEnergyMaxProduced. eoEnergyMaxProduced.
Measurements of the total energy consumed by an Energy Object Measurements of the total energy consumed by an Energy Object
may suffer from interruptions in the continuous measurement of may suffer from interruptions in the continuous measurement of
energy consumption. In order to indicate such interruptions, energy consumption. In order to indicate such interruptions,
the object eoEnergyDiscontinuityTime is provided for indicating the object eoEnergyDiscontinuityTime is provided for indicating
the time of the last interruption of total energy measurement. the time of the last interruption of total energy measurement.
eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418]
when the device was reset. when the device was reset.
skipping to change at page 30, line 22 skipping to change at page 30, line 35
TimeStamp, TruthValue TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
entPhysicalIndex, PhysicalIndex entPhysicalIndex, PhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
energyObjectMib MODULE-IDENTITY energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201306300000Z" -- 30 June 2013 LAST-UPDATED "2013102120000Z" -- 21 October2013
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
skipping to change at page 31, line 50 skipping to change at page 32, line 18
from the ENERGY-AWARE-MIB. As a requirement from the ENERGY-AWARE-MIB. As a requirement
[EMAN-AWARE-MIB] should be implemented. [EMAN-AWARE-MIB] should be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"201306300000Z" -- 30 June 2013 "2013102120000Z" -- 21 October2013
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
::= { mib-2 xxx } ::= { mib-2 xxx }
energyObjectMibNotifs OBJECT IDENTIFIER energyObjectMibNotifs OBJECT IDENTIFIER
::= { energyObjectMib 0 } ::= { energyObjectMib 0 }
energyObjectMibObjects OBJECT IDENTIFIER energyObjectMibObjects OBJECT IDENTIFIER
skipping to change at page 37, line 50 skipping to change at page 38, line 20
IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3.
ANSI C12.20 class 0.2, 0.5" ANSI C12.20 class 0.2, 0.5"
::= { eoPowerEntry 4 } ::= { eoPowerEntry 4 }
eoPowerMeasurementCaliber OBJECT-TYPE eoPowerMeasurementCaliber OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unavailable(1) , unavailable(1) ,
unknown(2), unknown(2),
actual(3) , actual(3) ,
estimated(4), estimated(4),
presumed(5) } static(5) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies how the usage value reported by "This object specifies how the usage value reported by
eoPower was obtained: eoPower was obtained:
- unavailable(1): Indicates that the usage is not - unavailable(1): Indicates that the usage is not
available. In such a case, the eoPower value must be 0 available. In such a case, the eoPower value must be 0
for devices that can not measure or report power this for devices that can not measure or report power this
option can be used. option can be used.
skipping to change at page 38, line 35 skipping to change at page 39, line 5
(4) or estimated (3) but is the measured consumption (4) or estimated (3) but is the measured consumption
rate. rate.
- estimated(4): Indicates that the usage was not - estimated(4): Indicates that the usage was not
determined by physical measurement. The value is a determined by physical measurement. The value is a
derivation based upon the device type, state, and/or derivation based upon the device type, state, and/or
current utilization using some algorithm or heuristic. It current utilization using some algorithm or heuristic. It
is presumed that the entity's state and current is presumed that the entity's state and current
configuration were used to compute the value. configuration were used to compute the value.
- presumed(5): Indicates that the usage was not - static(5): Indicates that the usage was not determined
determined by physical measurement, algorithm or by physical measurement, algorithm or derivation. The
derivation. The usage was reported based upon external usage was reported based upon external tables,
tables, specifications, and/or model information. For specifications, and/or model information. For example, a
example, a PC Model X draws 200W, while a PC Model Y PC Model X draws 200W, while a PC Model Y draws 210W"
draws 210W"
::= { eoPowerEntry 5 } ::= { eoPowerEntry 5 }
eoPowerCurrentType OBJECT-TYPE eoPowerCurrentType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ac(1), ac(1),
dc(2), dc(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 45, line 20 skipping to change at page 45, line 38
SYNTAX INTEGER { SYNTAX INTEGER {
period(1), period(1),
sliding(2), sliding(2),
total(3) total(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A control object to define the mode of interval calculation "A control object to define the mode of interval calculation
for the computation of the average eoEnergyConsumed or for the computation of the average eoEnergyConsumed or
eoEnergyProduced measurement in the eoEnergyTable table. eoEnergyProvided measurement in the eoEnergyTable table.
A mode of period(1) specifies non-overlapping periodic A mode of period(1) specifies non-overlapping periodic
measurements. measurements.
A mode of sliding(2) specifies overlapping sliding windows A mode of sliding(2) specifies overlapping sliding windows
where the interval between the start of one interval and where the interval between the start of one interval and
the next is defined in eoEnergyParametersIntervalWindow. the next is defined in eoEnergyParametersIntervalWindow.
A mode of total(3) specifies non-periodic measurement. In A mode of total(3) specifies non-periodic measurement. In
this mode only one interval is used as this is a this mode only one interval is used as this is a
skipping to change at page 45, line 44 skipping to change at page 46, line 13
::= { eoEnergyParametersEntry 5 } ::= { eoEnergyParametersEntry 5 }
eoEnergyParametersIntervalWindow OBJECT-TYPE eoEnergyParametersIntervalWindow OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the duration window between the starting "The length of the duration window between the starting
time of one sliding window and the next starting time in time of one sliding window and the next starting time in
hundredth of seconds, in order to compute the average of hundredth of seconds, in order to compute the average of
eoEnergyConsumed, eoEnergyProduced measurements in the eoEnergyConsumed, eoEnergyProvided measurements in the
eoEnergyTable table. This is valid only when the eoEnergyTable table. This is valid only when the
eoEnergyParametersIntervalMode is sliding(2). The eoEnergyParametersIntervalMode is sliding(2). The
eoEnergyParametersIntervalWindow value should be a multiple eoEnergyParametersIntervalWindow value should be a multiple
of eoEnergyParametersSampleRate." of eoEnergyParametersSampleRate."
::= { eoEnergyParametersEntry 6 } ::= { eoEnergyParametersEntry 6 }
eoEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sampling rate, in milliseconds, at which the Energy "The sampling rate, in milliseconds, at which the Energy
Object should poll power usage in order to compute the Object should poll power usage in order to compute the
average eoEnergyConsumed, eoEnergyProduced measurements average eoEnergyConsumed, eoEnergyProvided measurements
in the table eoEnergyTable. The Energy Object should in the table eoEnergyTable. The Energy Object should
initially set this sampling rate to a reasonable value, initially set this sampling rate to a reasonable value,
i.e., a compromise between intervals that will provide i.e., a compromise between intervals that will provide
good accuracy by not being too long, but not so short good accuracy by not being too long, but not so short
that they affect the Energy Object performance by that they affect the Energy Object performance by
requesting continuous polling. If the sampling rate is requesting continuous polling. If the sampling rate is
unknown, the value 0 is reported. The sampling rate unknown, the value 0 is reported. The sampling rate
should be selected so that should be selected so that
eoEnergyParametersIntervalWindow is a multiple of eoEnergyParametersIntervalWindow is a multiple of
eoEnergyParametersSampleRate." eoEnergyParametersSampleRate."
skipping to change at page 47, line 18 skipping to change at page 47, line 34
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describing energy measurements." "An entry describing energy measurements."
INDEX { eoEnergyParametersIndex, INDEX { eoEnergyParametersIndex,
eoEnergyCollectionStartTime } eoEnergyCollectionStartTime }
::= { eoEnergyTable 1 } ::= { eoEnergyTable 1 }
EoEnergyEntry ::= SEQUENCE { EoEnergyEntry ::= SEQUENCE {
eoEnergyCollectionStartTime TimeTicks, eoEnergyCollectionStartTime TimeTicks,
eoEnergyConsumed Integer32, eoEnergyConsumed Integer32,
eoEnergyProduced Integer32, eoEnergyProvided Integer32,
eoEnergyNet Integer32, eoEnergyStored Integer32,
eoEnergyUnitMultiplier UnitMultiplier, eoEnergyUnitMultiplier UnitMultiplier,
eoEnergyAccuracy Integer32, eoEnergyAccuracy Integer32,
eoEnergyMaxConsumed Integer32, eoEnergyMaxConsumed Integer32,
eoEnergyMaxProduced Integer32, eoEnergyMaxProduced Integer32,
eoEnergyDiscontinuityTime TimeStamp eoEnergyDiscontinuityTime TimeStamp
} }
eoEnergyCollectionStartTime OBJECT-TYPE eoEnergyCollectionStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
UNITS "hundredths of seconds" UNITS "hundredths of seconds"
skipping to change at page 48, line 5 skipping to change at page 48, line 24
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy consumed in units of watt- "This object indicates the energy consumed in units of watt-
hours for the Energy Object over the defined interval. hours for the Energy Object over the defined interval.
This value is specified in the common billing units of watt- This value is specified in the common billing units of watt-
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 2 } ::= { eoEnergyEntry 2 }
eoEnergyProduced OBJECT-TYPE eoEnergyProvided OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy produced in units of watt- "This object indicates the energy produced in units of watt-
hours for the Energy Object over the defined interval. hours for the Energy Object over the defined interval.
This value is specified in the common billing units of watt- This value is specified in the common billing units of watt-
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 3 } ::= { eoEnergyEntry 3 }
eoEnergyNet OBJECT-TYPE eoEnergyStored OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the resultant of the energy consumed and "This object indicates the resultant of the energy consumed and
energy produced for an energy object in units of watt-hours for energy produced for an energy object in units of watt-hours for
the Energy Object over the defined interval. This value is the Energy Object over the defined interval. This value is
specified in the common billing units of watt-hours specified in the common billing units of watt-hours
with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 4 } ::= { eoEnergyEntry 4 }
eoEnergyUnitMultiplier OBJECT-TYPE eoEnergyUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the magnitude of watt-hours for the "This object is the magnitude of watt-hours for the
energy field in eoEnergyConsumed, eoEnergyProduced, energy field in eoEnergyConsumed, eoEnergyProvided,
eoEnergyNet, eoEnergyMaxConsumed, and eoEnergyMaxProduced eoEnergyStored, eoEnergyMaxConsumed, and
." eoEnergyMaxProduced ."
::= { eoEnergyEntry 5 } ::= { eoEnergyEntry 5 }
eoEnergyAccuracy OBJECT-TYPE eoEnergyAccuracy OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a percentage value, in 100ths of a "This object indicates a percentage value, in 100ths of a
percent, representing the presumed accuracy of Energy usage percent, representing the presumed accuracy of Energy usage
reporting. eoEnergyAccuracy is applicable to all Energy reporting. eoEnergyAccuracy is applicable to all Energy
measurements in the eoEnergyTable. measurements in the eoEnergyTable.
For example: 1010 means the reported usage is accurate to +/- For example: 1010 means the reported usage is accurate to +/-
10.1 percent. 10.1 percent.
This value is zero if the accuracy is unknown." This value is zero if the accuracy is unknown."
::= { eoEnergyEntry 6 } ::= { eoEnergyEntry 6 }
skipping to change at page 50, line 5 skipping to change at page 50, line 22
eoEnergyDiscontinuityTime OBJECT-TYPE eoEnergyDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime [RFC3418] on the most recent "The value of sysUpTime [RFC3418] on the most recent
occasion at which any one or more of this entity's energy occasion at which any one or more of this entity's energy
counters in this table suffered a discontinuity: counters in this table suffered a discontinuity:
eoEnergyConsumed, eoEnergyProduced or eoEnergyNet. If no eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If
such discontinuities have occurred since the last re- no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
::= { eoEnergyEntry 9 } ::= { eoEnergyEntry 9 }
-- Notifications -- Notifications
eoPowerEnableStatusNotification OBJECT-TYPE eoPowerEnableStatusNotification OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 54, line 4 skipping to change at page 54, line 19
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the configuration of the Energy Table." related to the configuration of the Energy Table."
::= { energyObjectMibGroups 3 } ::= { energyObjectMibGroups 3 }
energyObjectMibEnergyTableGroup OBJECT-GROUP energyObjectMibEnergyTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object -- Note that object
-- eoEnergyCollectionStartTime is not -- eoEnergyCollectionStartTime is not
-- included since it is not-accessible -- included since it is not-accessible
eoEnergyConsumed, eoEnergyConsumed,
eoEnergyProduced, eoEnergyProvided,
eoEnergyNet, eoEnergyStored,
eoEnergyUnitMultiplier, eoEnergyUnitMultiplier,
eoEnergyAccuracy, eoEnergyAccuracy,
eoEnergyMaxConsumed, eoEnergyMaxConsumed,
eoEnergyMaxProduced, eoEnergyMaxProduced,
eoEnergyDiscontinuityTime eoEnergyDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Table." related to the Energy Table."
skipping to change at page 55, line 36 skipping to change at page 56, line 7
FROM SNMPv2-CONF FROM SNMPv2-CONF
UnitMultiplier UnitMultiplier
FROM ENERGY-OBJECT-MIB FROM ENERGY-OBJECT-MIB
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
entPhysicalIndex entPhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
powerAttributesMIB MODULE-IDENTITY powerAttributesMIB MODULE-IDENTITY
LAST-UPDATED "201306300000Z" -- 30 June 2013 LAST-UPDATED "2013102120000Z" -- 21 October 2013
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
skipping to change at page 57, line 19 skipping to change at page 57, line 36
[EMAN-AWARE-MIB] should be implemented. [EMAN-AWARE-MIB] should be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"201306300000Z" -- 30 June 2013 "2013102120000Z" -- 21 October 2013
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { mib-2 yyy }
powerAttributesMIBConform OBJECT IDENTIFIER powerAttributesMIBConform OBJECT IDENTIFIER
::= { powerAttributesMIB 0 } ::= { powerAttributesMIB 0 }
powerAttributesMIBObjects OBJECT IDENTIFIER powerAttributesMIBObjects OBJECT IDENTIFIER
skipping to change at page 69, line 40 skipping to change at page 70, line 8
DESCRIPTION DESCRIPTION
"This group contains the collection of all 3-phase power "This group contains the collection of all 3-phase power
attributes objects related to the Power State." attributes objects related to the Power State."
::= { powerAttributesMIBGroups 3 } ::= { powerAttributesMIBGroups 3 }
powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
eoACPwrAttributesDelPhaseToNextPhaseVoltage, eoACPwrAttributesDelPhaseToNextPhaseVoltage ,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage, eoACPwrAttributesDelThdPhaseToNextPhaseVoltage,
eoACPwrAttributesDelThdCurrent eoACPwrAttributesDelThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all power "This group contains the collection of all power
characteristic attributes of a phase in a DEL 3-phase characteristic attributes of a phase in a DEL 3-phase
power system." power system."
::= { powerAttributesMIBGroups 4 } ::= { powerAttributesMIBGroups 4 }
powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
eoACPwrAttributesWyePhaseToNeutralVoltage, eoACPwrAttributesWyePhaseToNeutralVoltage,
eoACPwrAttributesWyePhaseCurrent, eoACPwrAttributesWyePhaseCurrent,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage eoACPwrAttributesWyeThdPhaseToNeutralVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all WYE "This group contains the collection of all WYE
configuration phase-to-neutral power attributes configuration phase-to-neutral power attributes
measurements." measurements."
::= { powerAttributesMIBGroups 5 } ::= { powerAttributesMIBGroups 5 }
END END
11. Implementation Status 11. Implementation Status
[RFC Editor: before publication please remove this section and [Note to RFC Editor: Please remove this section and the
the reference to [I-D.sheffer-running-code], along the offered reference to [RFC6982] before publication.]
experiment of which this section exists to assist document This section records the status of known implementations of the
reviewers.] EMAN-Monitoring MIB at the time of posting of this Internet-
Draft, and is based on a proposal described in [RFC6982].
At the time of this writing the mandatory tables of the MIB The description of implementations in this section is intended
module eoPowerTable.and eoPowerStateTable have been implemented to assist the IETF in its decision processes in progressing
as a standalone prototype for monitoring the energy consumption drafts to RFCs.
of routers and switches. Network Management support for querying
MIB objects is under development. 11.1. SNMP Research
Organization: SNMP Research, Inc.
Maturity: Prototype based upon early drafts of the MIBs.
We anticipate updating it to more recent
documents as development schedules allow.
Coverage: Code was generated to implement all MIB objects
in ENTITY-MIB (Version 4),
ENERGY-OBJECT-CONTEXT-MIB,
ENERGY-OBJECT-MIB,
POWER-CHARACTERISTICS-MIB,
and BATTERY-MIB.
Implementation experience: The documents are implementable.
Comments: Technical comments about the
ENERGY-OBJECT-CONTEXT-MIB,
ENERGY-OBJECT-MIB, and
BATTERY-MIB
were submitted to the EMAN Working Group
E-mail list.
Licensing: Proprietary, royalty licensing
Contact: Alan Luchuk, luchuk at snmp.com
URL: http://www.snmp.com/
11.2. Cisco Systems
Organization: Cisco Systems, Inc.
Maturity: Prototype based upon early version drafts of
the MIBs. We anticipate updating the MIB
modules as when the drafts are updated.
Coverage: Code was generated to implement all MIB objects
in the ENTITY-MIB (Version 4), and
ENERGY-OBJECT-MIB.
Implementation experience: The MIB modules are implemented
on Cisco router platforms to measure and report
router energy measurements. The documents are
implementable.
Licensing: Proprietary
URL: http://www.cisco.com
12. Security Considerations 12. Security Considerations
Some of the readable objects in these MIB modules (i.e., objects Some of the readable objects in these MIB modules (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is sensitive or vulnerable in some network environments. It is
thus important to control even GET and/or NOTIFY access to these thus important to control even GET and/or NOTIFY access to these
objects and possibly to even encrypt the values of these objects objects and possibly to even encrypt the values of these objects
when sending them over the network via SNMP. when sending them over the network via SNMP.
skipping to change at page 72, line 7 skipping to change at page 73, line 30
13. IANA Considerations 13. IANA Considerations
13.1. IANA Considerations for the MIB Modules 13.1. IANA Considerations for the MIB Modules
The MIB modules in this document uses the following IANA- The MIB modules in this document uses the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
energyObjectMib { mib-2 xxx } energyObjectMib { mib-2 xxx }
powerAttributesMIB { mib-2 yyy } powerAttributesMIB { mib-2 yyy }
Additions to the MIB modules are subject to Expert Review Additions to the MIB modules are subject to Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested MIB objects for completeness and accuracy of the requested MIB objects for completeness and accuracy of the
description. Requests for MIB objects that duplicate the description. Requests for MIB objects that duplicate the
functionality of existing objects SHOULD be declined. The functionality of existing objects SHOULD be declined. The
smallest available OIDs SHOULD be assigned to the new MIB smallest available OIDs SHOULD be assigned to the new MIB
objects. The specification of new MIB objects SHOULD follow the objects. The specification of new MIB objects SHOULD follow the
skipping to change at page 74, line 18 skipping to change at page 76, line 4
The authors would like to thank Shamita Pisal for her prototype The authors would like to thank Shamita Pisal for her prototype
of this MIB module, and her valuable feedback. The authors of this MIB module, and her valuable feedback. The authors
would like to Michael Brown for improving the text dramatically. would like to Michael Brown for improving the text dramatically.
We would like to thank Juergen Schoenwalder for proposing the We would like to thank Juergen Schoenwalder for proposing the
design of the Textual Convention for IANAPowerStateSet and Ira design of the Textual Convention for IANAPowerStateSet and Ira
McDonald for his feedback. Thanks for the many comments on the McDonald for his feedback. Thanks for the many comments on the
design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki.
14. Open Issues 14. Open Issues
OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are
covered. Nominal Voltage to be reported as a range ? covered.
OPEN ISSUE 2 IANA Registered Power State Sets deferred to [EMAN-
FMWK]
15. References 15. References
15.2. Normative References 15.2. Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate [RFC2119] S. Bradner, Key words for use in RFCs to Indicate
Requirement Levels, BCP 14, RFC 2119, March 1997. Requirement Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
skipping to change at page 76, line 7 skipping to change at page 77, line 31
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268, November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie,
"Guidelines for Writing an IANA Considerations Section "Guidelines for Writing an IANA Considerations Section
in RFCs ", BCP 26, RFC 5226, May 2008. in RFCs ", BCP 26, RFC 5226, May 2008.
[EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and
M. Chandramouli, " Requirements for Energy Management", M. Chandramouli, " Requirements for Energy Management",
draft-ietf-eman-requirements-14, May 2013. RFC 6988, September 2013.
[EMAN-FMWK] Claise, B., Parello, J., Schoening, B., Quittek, J. [EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek,
and Nordman, B, "Energy Management Framework", draft- J., "Energy Management Framework", draft-ietf-eman-
ietf-eman-framework-08, July 2013. framework-11, October 2013.
[EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T.,
Quittek, J. and B. Claise "Energy and Power Monitoring Quittek, J. and B. Claise "Energy and Power Monitoring
MIB ", draft-ietf-eman-energy-monitoring-mib-05, April MIB ", draft-ietf-eman-energy-monitoring-mib-06, July
2013. 2013.
[EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B. [EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B.
"Energy Management (EMAN) Applicability Statement", "Energy Management (EMAN) Applicability Statement",
draft-ietf-eman-applicability-statement-03, April 2013. draft-ietf-eman-applicability-statement-04, October
2013.
[RFC6933] A. Bierman, D. Romascanu, J. Quittek and M. [RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
Chandramouli " Entity MIB (Version 4)", RFC 6933, May Chandramouli " Entity MIB (Version 4)", RFC 6933, May
2013. 2013.
[ACPI] "Advanced Configuration and Power Interface [ACPI] "Advanced Configuration and Power Interface
Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3
0b.pdf 0b.pdf
[DMTF] "Power State Management Profile DMTF DSP1027 Version [DMTF] "Power State Management Profile DMTF DSP1027 Version
skipping to change at page 77, line 7 skipping to change at page 78, line 35
[IEC.62053-21] International Electrotechnical Commission, [IEC.62053-21] International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 1 and 2)", 2003. (classes 1 and 2)", 2003.
[IEC.62053-22]International Electrotechnical Commission, [IEC.62053-22]International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 0,2 S and 0,5 S)", 2003. (classes 0,2 S and 0,5 S)", 2003.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of
Running Code: The Implementation Status Section", RFC
6982, July 2013.
Authors' Addresses Authors' Addresses
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
IN IN
Phone: +91 80 4429 2409 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
 End of changes. 41 change blocks. 
104 lines changed or deleted 154 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/