Network Working Group M. Teraoka, Ed.
Internet-Draft Y. Miyata
Intended status: Informational Yokogawa Electric Corp.
Expires: April 21, 2010 H. Kodaka
Y. Kodama
Alaxala Networks Corp.
October 18, 2009
Power Consumption MIB for IP forwarding devices
draft-teraoka-powerconsumption-mib-00
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 April 21, 2010.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines
objects for monitoring power consumption with IP network element that
has a function of dynamic performance control.
Teraoka, et al. Expires April 21, 2010 [Page 1]
Internet-Draft Power Consumption MIB October 2009
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. The module constitution of the network device . . . . . . 4
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. The General Group . . . . . . . . . . . . . . . . . . . . 5
5.2. The pconModuleData Group . . . . . . . . . . . . . . . . . 5
5.3. The pconPowerCon Group . . . . . . . . . . . . . . . . . . 6
5.4. The pconTraffic Group . . . . . . . . . . . . . . . . . . 6
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7
6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 7
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Normative References . . . . . . . . . . . . . . . . . . . 17
11.2. Informative References . . . . . . . . . . . . . . . . . . 18
Teraoka, et al. Expires April 21, 2010 [Page 2]
Internet-Draft Power Consumption MIB October 2009
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines
objects for monitoring power consumption with IP network element that
has a function of dynamic performance control. The router with a
dynamic performance control lowers the operation clock frequency when
the amount of traffic decreases and suppresses a surplus performance.
As a result, power consumption is decreased. The amount of traffic
is forecast according to the schedule of day of the week
specification. This MIB is used to know the situation of power
consumption, traffic and the state of the engine.
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 purpose of this MIB is to provide monitoring power consumption
and traffic information.
The Power Consumption MIB module (POWER-CONSUMPTION-MIB) is designed
to:
o Provide property information about rated power consumption and
traffic on network device.
o Support querying of the module constitution of the network device.
Teraoka, et al. Expires April 21, 2010 [Page 3]
Internet-Draft Power Consumption MIB October 2009
o Support monitoring of modules' measured power consumption
information.
o Support monitoring of modules' measured traffic information.
4.1. The module constitution of the network device
In order to understand the current power consumption of the entire
router, you can accomplish with a simple configuration of MIB
objects. But if you try to reduce the power consumption of the
router, you need to get more detailed information.
This MIB assumes that the router is composed of control plane,
forwarding plane and network interface. It thinks about these three
pieces as an element to control the electric power. Individual
information is collected from these modules, and the operational
condition of each module is understood. The judgment whether an
appropriate setting can be achieved becomes possible by knowing
operation information, and it is possible to reflect it in the policy
decision in the future. As a result, the engine control of three
modules achieves reduction of the consumption electricity.
5. Structure of the MIB Module
This section presents the structure of the POWER CONSUMPTION MIB
module. The objects are arranged into the following groups:
o pconObjects - defines the objects forming the basis for the POWER
CONSUMPTION MIB. These objects are divided up by function into
the following groups:
* General Group - This group contains the objects which describe
power consumption and transfer capacity to network device.
* Module Information Group - Contains information describing the
details of the module.
* Power Consumption Group - Contains information describing the
power consumption.
* Traffic Group - Contains information describing the traffic.
o pconConformance - defines minimal and full conformance of
implementations to this POWER CONSUMPTION MIB.
Teraoka, et al. Expires April 21, 2010 [Page 4]
Internet-Draft Power Consumption MIB October 2009
5.1. The General Group
The General group reports general information. This group is used to
monitor rated power consumption and the transfer performance of the
network device.
--pconObjects(1)
|
+-- Gauge32 pconMaxPowerConsumption(1)
+-- Gauge32 pconMaxTransferCapacity(2)
+-- Counter64 pconTotalTransferCapacity(3)
+-- Counter64 pconTransferCapacityMargin(4)
o Maximum Power Consumption - Maximum amount of power consumed by
the entire network device
o Maximum Transfer Capacity - Maximum transfer capacity of the
entire network device
o Total Transfer Capacity - Based on the current engine status,
total Transfer capacity of the entire network device
o Transfer Capacity Margin - Based on the current engine status,
margin of transfer capacity
5.2. The pconModuleData Group
The pconModuleData Subtree reports module information. The module
assumes control plane, forwarding plane, network interface and entire
network device.
--pconObjects(1)
|
+--pconModuleData(5) [pconModuleIndex]
|
+-- Integer32 pconModuleIndex(1)
+-- DisplayString pconModuleDescr(2)
+-- INTEGER pconModuleType(3)
+-- INTEGER pconModuleStatus(4)
+-- INTEGER pconModuleMode(5)
o Module Description - The textual description of this
PconModuleEntry.
o Module Type - The module type of this PconModuleEntry.
o Module Status - The module status of this PconModuleEntry.
Teraoka, et al. Expires April 21, 2010 [Page 5]
Internet-Draft Power Consumption MIB October 2009
o Module Mode - The module mode of this PconModuleEntry.
5.3. The pconPowerCon Group
The pconPowerCon Subtree reports power consumption information.
--pconObjects(1)
|
+--pconPowerCon(6) [pconModuleIndex]
|
+-- Counter64 pconPowerConPowerConsumption(1)
+-- Counter64 pconPowerConPowerMeter(2)
o Power Consumption - Power consumption of the module, accumulation
value. If the value of 'pconModuleType' object is 'all', it
describes total power consumption of the entire network device.
In other case, this means to power consumption to each module.
o Power Meter - Power meter of the module, instantaneous value. If
the value of 'pconModuleType' object is 'all', it describes total
power meter of the entire network device. In other case, this
means to power meter to each module.
5.4. The pconTraffic Group
The pconTraffic Subtree reports traffic information.
--pconObjects(1)
|
+--pconTraffic(7) [pconModuleIndex]
|
+-- Counter64 pconTrafficInOctets(1)
+-- Counter64 pconTrafficOutOctets(2)
+-- Counter64 pconTrafficInPkts(3)
+-- Counter64 pconTrafficOutPkts(4)
+-- Counter64 pconTrafficDiscPkts(5)
o In Octets - Total Number of Octets that received on this module
o Out Octets - Total Number of Octets transmitted out from this
module
o In Packets - Total Number of Packets that received on this module
o Out Packets - Total Number of Packets transmitted out from this
module
Teraoka, et al. Expires April 21, 2010 [Page 6]
Internet-Draft Power Consumption MIB October 2009
o Discarded Packets - Total Number of Discarded Packets on this
module
6. Relationship to Other MIB Modules
6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The POWER CONSUMPTION MIB
does not duplicate those objects.
6.2. MIB modules required for IMPORTS
The POWER CONSUMPTION MIB module requires following MIB modules for
IMPORTS:
o SNMPv2-SMI defined in [RFC2578]
7. Definitions
POWER-CONSUMPTION-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Gauge32, Counter64,
Integer32
FROM SNMPv2-SMI
DisplayString
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF;
pconMIB MODULE-IDENTITY
LAST-UPDATED "200910150000Z" -- 15 Oct 2009
ORGANIZATION "Operations and Management Area Working Group"
CONTACT-INFO "
Minoru Teraoka
Yokogawa Electric Corp.
2-9-32 Nakacho
Musashino-shi, Tokyo 180-8750
Japan
Phone: +81 422 52 6413
Fax: +81 422 52 6426
EMail: minoru.teraoka@jp.yokogawa.com
Yuuji Miyata
Yokogawa Electric Corp.
Teraoka, et al. Expires April 21, 2010 [Page 7]
Internet-Draft Power Consumption MIB October 2009
2-9-32 Nakacho
Musashino-shi, Tokyo 180-8750
Japan
Phone: +81 422 52 6413
Fax: +81 422 52 6426
EMail: yuuji.miyata@jp.yokogawa.com
Hideo Kodaka
Alaxala Networks Corp.
Shin-Kawasaki Mitsui Bldg.
890 Saiwai-ku Kashimada
Kawasaki, Kanagawa 212-0058
Japan
Phone: +81 44 549 1646
Fax: +81 44 549 1736
EMail: hideo.kodaka@alaxala.com
Yasuhiro Kodama
Alaxala Networks Corp.
Shin-Kawasaki Mitsui Bldg.
890 Saiwai-ku Kashimada
Kawasaki, Kanagawa 212-0058
Japan
Phone: +81 44 549 1346
Fax: +81 44 549 1434
EMail: yasuhiro.kodama@alaxala.com"
DESCRIPTION "
The MIB module for management of reducing the power
consumption for network device which can be useful for
dynamic power management."
REVISION "200910150000Z" -- 15 Oct 2009
DESCRIPTION "Initial version."
::= { mib-2 xxx }
-- Top level components of this MIB
pconObjects OBJECT IDENTIFIER
::= { pconMIB 1 }
pconConformance OBJECT IDENTIFIER
::= { pconMIB 2 }
-- pconCharacteristicData
pconMaxPowerConsumption OBJECT-TYPE
SYNTAX Gauge32
UNITS "Wh"
MAX-ACCESS read-only
Teraoka, et al. Expires April 21, 2010 [Page 8]
Internet-Draft Power Consumption MIB October 2009
STATUS current
DESCRIPTION
"maximum power consumption."
::= { pconObjects 1 }
pconMaxTransferCapacity OBJECT-TYPE
SYNTAX Gauge32
UNITS "Kbps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"maximum transfer capacity."
::= { pconObjects 2 }
pconTotalTransferCapacity OBJECT-TYPE
SYNTAX Gauge32
UNITS "Kbps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"total transfer capacity."
::= { pconObjects 3 }
pconTransferCapacityMargin OBJECT-TYPE
SYNTAX Gauge32
UNITS "Kbps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"margin of transfer capacity."
::= { pconObjects 4 }
-- pconModuleData
pconModuleData OBJECT IDENTIFIER
::= { pconObjects 5 }
pconModuleTable OBJECT-TYPE
SYNTAX SEQUENCE OF PconModuleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The module information table."
::= { pconModuleData 1 }
pconModuleEntry OBJECT-TYPE
SYNTAX PconModuleEntry
MAX-ACCESS not-accessible
Teraoka, et al. Expires April 21, 2010 [Page 9]
Internet-Draft Power Consumption MIB October 2009
STATUS current
DESCRIPTION
"The module information entry."
INDEX {
pconModuleIndex
}
::= {pconModuleTable 1 }
PconModuleEntry ::= SEQUENCE {
pconModuleIndex Integer32,
pconModuleDescr DisplayString,
pconModuleType INTEGER,
pconModuleStatus INTEGER,
pconModuleMode INTEGER
}
pconModuleIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value for each module contained by the network device.
The value for each module must remain constant at
least from one re-initialization of the agent to the
next re-initialization."
::= { pconModuleEntry 1 }
pconModuleDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The textual description of this module."
::= { pconModuleEntry 2 }
pconModuleType OBJECT-TYPE
SYNTAX INTEGER {
other (1),
all (2),
controlPlane (3),
forwardingPlane (4),
networkInterface (5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the type of module.
Teraoka, et al. Expires April 21, 2010 [Page 10]
Internet-Draft Power Consumption MIB October 2009
A value of 'controlPlane' indicates that the module is
control plane in network device.
If this value is 'controlPlane' then an entry exists in
the pconPowerConTable which corresponds to this network
device.
A value of 'forwardingPlane' indicates that the module is
forwarding plane in network device.
If this value is 'forwardingPlane' then an entry exists in
the pconPowerConTable and pconTrafficTable which
corresponds to this network device.
A value of 'networkInterface' indicates that the module is
network interface in network device.
If this value is 'networkInterface' then an entry exists in
the pconPowerConTable and pconTrafficTable which
A value of 'all' indicates that the module is entire
network device.
If this value is 'all' then entry exists in the
pconPowerConTable and pconTrafficTable which
A value of 'other' means that this module is unable to
report module type."
::= { pconModuleEntry 3 }
pconModuleStatus OBJECT-TYPE
SYNTAX INTEGER {
other (1),
hotStandby (2),
coldStandby (3),
providingService (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The module status of this PconModuleEntry.
A value of 'hotStandby' means the module is not
providing service, but it will be immediately able to
act when its mode would be changed.
A value of 'coldStandy' means that the module will not
be immediately able to act, and will require some
initialization activity.
A value of 'providingService' means the module is
providing service.
A value of 'other' means that this module is unable
to report module status."
::= { pconModuleEntry 4 }
pconModuleMode OBJECT-TYPE
SYNTAX INTEGER {
Teraoka, et al. Expires April 21, 2010 [Page 11]
Internet-Draft Power Consumption MIB October 2009
other (1),
fullPower (2),
powerSaving (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The module mode of this PconModuleEntry.
A value of 'fullPower' means the module operates by the
maximum performance.
A value of 'powerSaving' means that the operation of this
module saves the performance.
A value of 'other' means that this module is unable
to report module mode."
::= { pconModuleEntry 5 }
-- pconPowerCon
pconPowerCon OBJECT IDENTIFIER
::= { pconObjects 6 }
pconPowerConTable OBJECT-TYPE
SYNTAX SEQUENCE OF PconPowerConEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The power consumption information table."
::= { pconPowerCon 1 }
pconPowerConEntry OBJECT-TYPE
SYNTAX PconPowerConEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The power consumption information entry.
The pconModuleIndex in the index represents
the entry in the pconModuleTable that corresponds to the
pconPowerConEntry."
INDEX {
pconModuleIndex
}
::= {pconPowerConTable 1 }
PconPowerConEntry ::= SEQUENCE {
pconPowerConPowerConsumption Counter64,
pconPowerConPowerMeter Gauge32
}
Teraoka, et al. Expires April 21, 2010 [Page 12]
Internet-Draft Power Consumption MIB October 2009
pconPowerConPowerConsumption OBJECT-TYPE
SYNTAX Counter64
UNITS "Wh"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"power consumption of module."
::= { pconPowerConEntry 1 }
pconPowerConPowerMeter OBJECT-TYPE
SYNTAX Gauge32
UNITS "W"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"power meter of module."
::= { pconPowerConEntry 2 }
-- pconTraffic
pconTraffic OBJECT IDENTIFIER
::= { pconObjects 7 }
pconTrafficTable OBJECT-TYPE
SYNTAX SEQUENCE OF PconTrafficEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Traffic information table."
::= { pconTraffic 1 }
pconTrafficEntry OBJECT-TYPE
SYNTAX PconTrafficEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Traffic information entry.
The pconModuleIndex in the index represents
the entry in the pconModuleTable that corresponds to the
pconTrafficEntry."
INDEX {
pconModuleIndex
}
::= {pconTrafficTable 1 }
PconTrafficEntry ::= SEQUENCE {
pconTrafficInOctets Counter64,
pconTrafficOutOctets Counter64,
Teraoka, et al. Expires April 21, 2010 [Page 13]
Internet-Draft Power Consumption MIB October 2009
pconTrafficInPkts Counter64,
pconTrafficOutPkts Counter64,
pconTrafficDiscPkts Counter64
}
pconTrafficInOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets that received on this module."
::= { pconTrafficEntry 1 }
pconTrafficOutOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets transmitted out from this
module."
::= { pconTrafficEntry 2 }
pconTrafficInPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets that received on this
module."
::= { pconTrafficEntry 3 }
pconTrafficOutPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets transmitted out from this
module."
::= { pconTrafficEntry 4 }
pconTrafficDiscPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
Teraoka, et al. Expires April 21, 2010 [Page 14]
Internet-Draft Power Consumption MIB October 2009
STATUS current
DESCRIPTION
"The total number of discarded packets on this module."
::= { pconTrafficEntry 5 }
-- Conformance Information
pconCompliances OBJECT IDENTIFIER
::= { pconConformance 1 }
pconGroups OBJECT IDENTIFIER
::= { pconConformance 2 }
-- Compliance statements
pconCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for network device
supporting POWER-CONSUMPTION-MIB."
MODULE -- this module
MANDATORY-GROUPS {
pconGeneralGroup,
pconModuleGroup,
pconPowerConGroup,
pconTrafficGroup
}
::= { pconCompliances 1 }
pconGeneralGroup OBJECT-GROUP
OBJECTS {
pconMaxPowerConsumption,
pconMaxTransferCapacity,
pconTotalTransferCapacity,
pconTransferCapacityMargin
}
STATUS current
DESCRIPTION "A collection of objects providing data information
of the network device."
::= { pconGroups 1 }
pconModuleGroup OBJECT-GROUP
OBJECTS {
pconModuleDescr,
pconModuleType,
pconModuleStatus,
pconModuleMode
}
STATUS current
Teraoka, et al. Expires April 21, 2010 [Page 15]
Internet-Draft Power Consumption MIB October 2009
DESCRIPTION "A collection of objects providing module data
information of the network device."
::= { pconGroups 2 }
pconPowerConGroup OBJECT-GROUP
OBJECTS {
pconPowerConPowerConsumption,
pconPowerConPowerMeter
}
STATUS current
DESCRIPTION "A collection of objects providing information of the
power consumption in the network device."
::= { pconGroups 3 }
pconTrafficGroup OBJECT-GROUP
OBJECTS {
pconTrafficInOctets,
pconTrafficOutOctets,
pconTrafficInPkts,
pconTrafficOutPkts,
pconTrafficDiscPkts
}
STATUS current
DESCRIPTION "A collection of objects providing information of the
traffic in the network device."
::= { pconGroups 4 }
END
8. Security Considerations
There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (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
Teraoka, et al. Expires April 21, 2010 [Page 16]
Internet-Draft Power Consumption MIB October 2009
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 indeed GET or SET (change/create/delete) them.
9. IANA Considerations
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pconMIB { mib-2 XXX }
10. Acknowledgements
The authors wish to thank Tomoyuki Iijima, Yoshifumi Atarashi.
11. References
11.1. Normative References
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
[RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB
Documents", BCP 111, RFC 4181, September 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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",
Teraoka, et al. Expires April 21, 2010 [Page 17]
Internet-Draft Power Consumption MIB October 2009
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
11.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
Minoru Teraoka (editor)
Yokogawa Electric Corp.
2-9-32 Nakacho
Musashino-shi, Tokyo 180-8750
Japan
Phone: +81-422-52-6413
Fax: +81-422-52-6426
EMail: minoru.teraoka@jp.yokogawa.com
Yuuji Miyata
Yokogawa Electric Corp.
2-9-32 Nakacho
Musashino-shi, Tokyo 180-8750
Japan
Phone: +81-422-52-6413
Fax: +81-422-52-6426
EMail: yuuji.miyata@jp.yokogawa.com
Hideo Kodaka
Alaxala Networks Corp.
Shin-Kawasaki Mitsui Bldg.
890 Saiwai-ku Kashimada
Kawasaki, Kanagawa 212-0058
Japan
Phone: +81-44-549-1646
Fax: +81-44-549-1736
EMail: hideo.kodaka@alaxala.com
Teraoka, et al. Expires April 21, 2010 [Page 18]
Internet-Draft Power Consumption MIB October 2009
Yasuhiro Kodama
Alaxala Networks Corp.
Shin-Kawasaki Mitsui Bldg.
890 Saiwai-ku Kashimada
Kawasaki, Kanagawa 212-0058
Japan
Phone: +81-44-549-1346
Fax: +81-44-549-1434
EMail: yasuhiro.kodama@alaxala.com
Teraoka, et al. Expires April 21, 2010 [Page 19]