[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] [IPR]

Versions: (draft-parello-eman-energy-aware-mib) 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 RFC 7461

     Network Working Group                                 J. Parello
     Internet-Draft                                         B. Claise
     Intended Status: Standards Track             Cisco Systems, Inc.
     Expires: April 30, 2012                         October 31, 2011
     
     
     
                    Energy-aware Networks and Devices MIB
                     draft-ietf-eman-energy-aware-mib-03
     
     
     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 September, 2011.
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     Copyright Notice
     
        Copyright (c) 2011 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
        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 Simplified BSD License.
     
     
     Abstract
     
        This document defines a subset of a Management Information Base
        (MIB) for energy management of devices.  The module addresses
        device identification, context information, and the
        relationships between reporting devices, remote devices, and
        monitoring devices.
     
     Conventions used in this document
     
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
        "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
        RECOMMENDED", "MAY", and "OPTIONAL" in this document are to
        be interpreted as described in RFC 2119 [RFC2119].
     
     
     
     Table of Contents
     
        1. Introduction............................................3
           1.1. Energy Management Document Overview................3
        2. The Internet-Standard Management Framework..............4
        3. Requirements and Use Cases..............................4
        4. Terminology.............................................5
        5. Architecture Concepts Applied to the MIB Module.........5
           5.1 Energy Object Identification........................7
           5.2 Energy Object Context...............................8
           5.3 Links to Other Identifiers..........................9
           5.4 Child: Energy Object Relationships..................9
           5.5 Parent: Energy Object Relationships................11
           5.6 Energy Object Identity Persistence.................11
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 2]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        6. Structure of the MIB...................................12
        7. MIB Definitions........................................13
        8. Security Considerations................................29
        9. IANA Considerations....................................30
        10. References............................................30
           10.1. Normative References.............................30
           10.2. Informative References...........................31
        11. Acknowledgments.......................................32
     
     
     
     
     
     1. Introduction
     
        The EMAN standards provides network administrators with a
        specification for Energy Management. This document defines a
        subset of a Management Information Base (MIB) for use with
        network management protocols for Energy monitoring of Electrical
        Equipments (for example network devices and devices attached to
        the network.)
     
        This focus of this MIB module is on monitoring Energy Objects as
        defined in [EMAN-FMWK].  The module addresses Energy Object
        Identification, Energy Object Context, and Energy Object
        Relationships.
     
        Devices and their sub-components are characterized by the power-
        related attributes of a physical entity present in the ENTITY
        MIB [RFC4133].
     
     
     1.1. Energy Management Document Overview
     
        This document specifies the Energy-Aware Networks and Devices
        MIB.  This document is based on the Energy Management Framework
        [EMAN-FMWK] and meets the requirements specified in the Energy
        Management requirements [EMAN-REQ].
     
        The Power and Energy Monitoring MIB [EMAN-MON-MIB] contains the
        Energy Objects for monitoring of Power States, along with the
        Power and Energy consumption of Electrical Objects.  Power State
        monitoring includes: retrieving Power States, Power State
        properties, current Power State, Power State transitions, and
        Power State statistics.  This MIB module provides the detailed
        properties of the Power, Energy, along with optional
        characteristics.
     
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 3]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
        EDITOR'S NOTE: Replace characteristics with consensus term when
        defined. This is electrical qualities or characteristics.
     
        The applicability statement document [EMAN-AS] provides the list
        of use cases, cross-reference between existing standards and the
        EMAN standard, and shows how the EMAN framework relates to other
        frameworks.
     
     
     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 MIB modules that are compliant with
        SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58,
        RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
     
     3. Requirements and Use Cases
     
        Requirements for power and energy monitoring for networking
        devices are specified in [EMAN-REQ].  The requirements in [EMAN-
        REQ] include communications network devices, such as switches,
        routers, and various connected endpoints and Electrical
        Equipments.
     
        The use cases for this MIB are specified in the EMAN
        applicability statement document [EMAN-AS].
     
        EDITOR'S NOTE: say a few words about the use cases when we will
        have a stable version of the EMAN applicability statement
        document.
     
        Accordingly, the scope of the MIB module in this document is in
        accordance to the requirements specified in [EMAN-REQ] and the
        use cases in [EMAN-AS].
     
     
     
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 4]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     4. Terminology
     
        The definitions of basic terms like Energy Management, Energy
        Monitoring, Power, Energy, Energy Object, Energy Object Parent,
        Energy Object Child, Energy Management Domain, Power State,
        Power State Set, Energy Object Relationships, Aggregation
        Relationship, Power Source Relationship, Proxy Relationship,
        Dependency Relationship, Nameplate Power can be found in the
        temporary draft[EMAN-TERMINOLOGY].
     
        EDITOR'S NOTE: all terms will be copied over from the final
        version of the [EMAN-TERMINOLOGY] draft.
     
     
     5. Architecture Concepts Applied to the MIB Module
     
        This section describes the basic concepts specified in the
        Energy Management Architecture [EMAN-FMWK], with specific
        information related to the MIB module specified in this document
     
        The following diagram shows the relationship of the identifying
        information.
     
     
               +--------------------------+
               |  EO Context Information  |
               | ------------------------ |
               |  eoRoleDescription       |
               |  eoKeywords              |
               |  eoImportance            |
               |  eoPowerCategory         |
               +--------------------------+
                      |
                      |
                      v
                 +--------------------------------+
                 |  EO Identification             |
                 |_------------------------------ |
              |->| entPhysIndex (*)               |
              |  | entPhysicalName (*)            |
              |  | entPhysicalUris (*)  (EO UUID) |
              |  | eoDomainName                   |
              |  | eoMgmtMacAddress               |
              |  | eoMgmtAddress                  |
              |  | eoMgmtAddressType              |
              |  | eoMgmtDNSName                  |
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 5]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
              |  +--------------------------------+
              |
              |
     
              |  +------------------------------+
              |--|   Links to other Identifiers |
              |  | ---------------------------- |
              |  |  eoEthPortIndex (**)         |
              |  |  eoEthPortGrpIndex (**)      |
              |  |  eoLldpPortNumber (***)      |
              |  |  eoAlternateKey              |
              |  +------------------------------+
              |
              |
              |  +-------------------------------------------+
              |--|   EO Child Relationships (optional)       |
              |  | ----------------------------------------- |
              |  |  eoMeteredBy (Parent(s) UUID list)        |
              |  |  eoPoweredBy (Parent(s) UUID list         |
              |  |  eoDependentOf (Parent(s) UUID list)      |
              |  |  eoAggregatedBy (Parent(s) UUID list      |
              |  |  eoProxyBy (Parent(s) UUID list)          |
              |  |  eoParentProxyAbilities (Parent abilities)|
              |  +-------------------------------------------+
              |
              |
              |  +-----------------------------------------+
              |--|   EO Parent Relationships (optional)    |
                 | --------------------------------------- |
                 |  eoChildrenList (Child(ren) UUID list)  |
                 +-----------------------------------------+
     
     
     
              +-----------------------------------------+
              |         EO Identity Persistence         |
              | --------------------------------------- |
              |  eoTablePersistence (boolean)           |
              +-----------------------------------------+
     
     
     
          (*)    Compliance From the ENTITY MIB [RFC4133]
          (**)   Link with the Power over Ethernet MIB [RFC3621]
          (***)  Link with LLDP MIBs [LLDP-MIB] [LLDP-MED-MIB]
     
     
                         Figure 1: MIB Objects Grouping
     
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 6]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
        As displayed in figure 1, there are six different logical groups
        of MIB objects in the ENERGY-AWARE-MIB module:
     
        1) The Energy Object Identification. See Section 5.1 "Energy
           Object Identification"
        2) The Context Information. See Section 5.2 "Energy Object
           Context"
        3) The links to other MIB modules. See Section 5.3 "Links to
           other Identifiers"
        4) The Energy Object Child Relationships specific information.
           See Section 5.4 "Child: Energy Objects Relationship."
        5) The Energy Object Parent Relationships specific information.
           See Section 5.5 "Parent: Energy Objects Relationship."
        6) The Energy Object Identity Persistence. See Section 5.6
           "Energy Object Identity Persistence"
     
     
     5.1 Energy Object Identification
     
        Refer to the "Energy Object Information" section in [EMAN-FMWK]
        for background information about Energy Objects.
     
        Every Energy Object MUST support the unique index,
        entPhysicalIndex, from the ENTITY MIB [RFC4133], which is used
        as index for the primary Energy Object information in the
        ENERGY-AWARE-MIB module eoTable table.
     
        The ENERGY-AWARE-MIB MIB module, specified in this document
        requires the implementation of some managed objects in the
        ENTITY MIB [RFC4133].
     
        Other ENTITY MIB managed objects MAY be implemented.
     
        Every Energy Object MUST have a printable name. Energy Objects
        MUST implement the entPhysicalName object specified in the
        ENTITY-MIB, which must contain the Energy Object name.
     
        By the [RFC4133] definition, the entPhysicalUris contains a
        white space separated list of  Uniform Resource Identifier
        (s)(URIs).  For the ENERGY-AWARE-MIB compliance, every Energy
        Object instance MUST implement the entPhysicalUris from the
        ENTITY MIB [RFC4133].  The entPhysicalUris MUST contain the
        Energy Object UUID, according to [RFC4122].
     
        As displayed in [RFC4122], the following is an example of the
        string representation of a UUID as a URN: urn:uuid:f81d4fae-
        7dec-11d0-a765-00a0c91e6bf6.
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 7]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        Other ENTITY MIB managed objects, next to entPhysicalIndex,
        entPhysicalName, and entPhysicalUris, MAY be implemented.
     
        When a Energy Object Parent acts as a Power Aggregator or a
        Power Proxy, the Energy Object Parent and its Energy Object
        Child/Children MUST be members of the same Energy Management
        Domain, specified by the eoDomainName MIB Object.
     
        Each Energy Object MUST belong to a single Energy Management
        Domain or in other words, a Energy Object cannot belong to more
        than one Energy Management Domain.  Refer to the "Energy
        Management Domain" section in [EMAN-FMWK] for background
        information.  The eoDomainName, which is an element of the
        eoTable, is a read-write MIB object.  The Energy Management
        Domain should map 1-1 with a metered or sub-metered portion of
        the site.  The Energy Management Domain MUST be configured on
        the Energy Object Parent.  The Energy Object Children MAY
        inherit their domain parameters from the Energy Object Parent or
        the Energy Management Domain MAY be configured directly in a
        Energy Object Child.
     
        The eoMgmtMacAddress, eoMgmtAddress, eoMgmtAddressType, and
        eoMgmtDNSName MIB objects SHOULD be implemented for Energy
        Object Children, and MAY be implemented for Energy Object
        Parents.
     
     
     
     5.2 Energy Object Context
     
        Refer to the "Energy Object Context" section in [EMAN-FMWK] for
        background information.
     
        A Energy Object can provide a eoImportance value in the range of
        1..100 to help differentiate the use or relative value of the
        device.  The importance range is from 1 (least important) to 100
        (most important).  The default importance value is 1.
     
        A Energy Object can provide a set of eoKeywords.  These keywords
        are a list of tags that can be used for grouping and summary
        reporting within or between Energy Management Domains.
     
        Additionally, a Energy Object can provide a eoRoleDescription
        string that indicates the purpose the Energy Object serves in
        the network or for the site/business.
     
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 8]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
     5.3 Links to Other Identifiers
     
        While the entPhysicalIndex is the primary index for all MIB
        objects in the ENERGY-AWARE-MIB module, the Energy Management
        Systems (EnMS) must be able to make the link with the
        identifier(s) in other supported MIB modules.
     
        The Energy Object eoethPortIndex and eoethPortGrpIndex MUST
        contain the values of pethPsePortIndex and pethPsePortGroupIndex
        from the Power over Ethernet MIB [RFC3621], if the Power over
        Ethernet MIB is supported by the Energy Object SNMP agent.
     
        The Energy Object eoLldpPortNumber MUST contain the
        lldpLocPortNum from the LLDP MIB [LLDP-MIB], if the LLDP-MED MIB
        is supported on the Energy Object SNMP agent.
     
        The intent behind the links to the other MIB module
        identifier(s) is to correlate the instances in the different MIB
        modules.  This will allow the ENERGY-AWARE-MIB to reference
        other MIB modules in cases where the Power over Ethernet and the
        LLDP MIB modules are supported by the SNMP agent.  Some use
        cases may not implement any of these two MIB modules for the
        Energy Objects.  However, in situation where any of these two
        MIB modules is implemented, the EnMS must be able to correlate
        the instances in the different MIB modules.
     
        The eoAlternateKey alternate key object specifies a manufacturer
        defined string that can be used to identify the Energy Object.
        Since EnMS may need to correlate objects across management
        systems, this alternate key is provided to facilitate such a
        link.  This optional value is intended as a foreign key or
        alternate identifier for a manufacturer or EnMS to use to
        correlate the unique Energy Object Id in other systems or
        namespaces. If an alternate key is not available or is not
        applicable then NULL should be returned.
     
     
     5.4 Child: Energy Object Relationships
     
        Refer to the "Energy Object Parent and Child" section in [EMAN-
        FMWK] for background information.
     
        In order to link the Energy Object Child and the Energy Object
        Parent, multiple objects are introduced in the MIB module.
        Depending on the Energy Object Relationship type, the following
        objects are appropriate:
     
     
     
     <Parello, Claise>       Expires April 30, 2012            [Page 9]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
         Metering Relationship         ->   eoMeteredBy
     
         Power Source Relationship     ->   eoPoweredBy
     
         Dependency Relationship       ->   eoDependentOf
     
         Aggregation Relationship      ->   eoAggregatedBy
     
          Proxy Relationship            ->   eoProxyBy,
                                        ->   eoParentProxyAbilities
     
        Each object contains the list of Energy Object Parent UUIDs for
        the specific Energy Object Relationship type.  The UUIDs MUST
        comply to the RFC 4122 specifications.  The object contains URIs
        and, therefore, the syntax of this object must conform to RFC
        3986 [RFC3986], section 2.  Multiple URIs may be present and are
        separated by white space characters.  Leading and trailing white
        space characters are ignored.
     
        For example, if an Energy Object Child is powered by two power
        sources, eoPoweredBy would contain the two power sources UUIDs,
        separated by a space: "urn:uuid:f81d4fae-7dec-11d0-a765-
        00a0c91e6bf6 urn:uuid:abcdec11-7abc-23e1-b876-00a0c91e6bf8".
     
        The eoParentProxyAbilities object is specific to the Proxy
        Relationship.  This object describes the capabilities of the
        Energy Object Parent for the Energy Object Child represented by
        the entPhysicalIndex. The possible capabilities are: report,
        configuration, and/or wakeonlan.  This object only applies to an
        Energy Object Child.
     
        If the Energy Object is not an Energy Object Child, or if the
        Energy Object doesn't have a Energy Object Relationship, the
        eoMeteredBy, eoPoweredBy, eoDependentOf, eoAggregatedBy,
        eoProxyBy, and eoParentProxyAbilities objects are not
        instantiated.  A zero length octet string MAY also be returned
        in this case.
     
        The Energy Object Child can indicate that it wants its Energy
        Object Parent to proxy capabilities such as, energy reporting,
        power state configurations, non physical wake capabilities (such
        as Wake-on-LAN)), or any combination of capabilities.  These
        capabilities are indicated in the eoParentProxyAbilities object.
        In the case of Energy Object Parent, the eoParentProxyAbilities
        MUST be set to "none" (0).
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 10]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        Since the communication between the Energy Object Parent and
        Energy Object Child may not be via SNMP (as defined in EMAN-
        FMWK), a Energy Object Child can have additional MIB objects
        that can be used for easier identification by the EnMS. The
        optional objects eoMgmtMacAddress, eoMgmtAddressType
        eoMgmtDNSName can be used to help identify the relationship
        between the child and other NMS objects.  These objects can be
        used as an alternate key to help link the Energy Object with
        other keyed information that may be stored within the EnMS(s).
     
        The eoMeteredBy, eoPoweredBy, eoDependentOf, eoAggregatedBy,
        eoProxyBy, and eoParentProxyAbilities implementations are
        optional.
     
     
     
     5.5 Parent: Energy Object Relationships
     
        When the Energy Object is an Energy Object Parent, the
        eoChildrenList object represents the list of Energy Object
        Child(ren) UUIDs.  This UUID list will help in the network
        discovery of Energy Objects, using the Energy Object Parent as
        entry points.
     
        eoChildrenList has the same format as the eoMeteredBy,
        eoPoweredBy, eoDependentOf, eoAggregatedBy, and eoProxyBy. The
        UUIDs MUST comply to the RFC 4122 specifications.  The UUIDs
        MUST comply to the RFC 4122 specifications.  The eoChildrenList
        object contains URIs and, therefore, the syntax of this object
        must conform to RFC 3986 [RFC3986], section 2.  Multiple URIs
        may be present and are separated by white space characters.
        Leading and trailing white space characters are ignored.
     
        If the Energy Object is not an Energy Object Parent, the
        eoChildrenList objects is not instantiated.  A zero length octet
        string MAY also be returned in this case.
     
        The eoChildrenList implementation is optional.
     
     
     
     5.6 Energy Object Identity Persistence
     
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 11]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        In some situations, the Energy Object identity information
        should be persistent even after a device reload.  For example,
        in a static setup where a switch monitors a series of connected
        PoE phones, there is a clear benefit for the EnMS if the Energy
        Object Identification and all associated information persist, as
        it saves a network discovery.  However, in other situations,
        such as a wireless access point monitoring the mobile user PCs,
        there is not much advantage to persist the Energy Object
        Information.  Therefore, a specific MIB object, the
        eoTablePersistence, enables and disables the persistence
        globally for all Energy Objects information in the ENERGY-AWARE-
        MIB module.
     
     
     6. Structure of the MIB
     
        The primary MIB object in this MIB module is the energyAwareMIB
        Object.  The eoTable table of energyAwareMIB Object describes an
        entity in the network that is a Energy Object according the
        [EMAN-FMWK].
     
        +--  rwn TruthValue      eoTablePersistence(1)
        +- eoTable(2)
           |
           +- eoEntry(1) [entPhysicalIndex]
           |  |
           |  +-- r-n PhysicalIndexOrZero          eoPhysicalEntity(1)
           |  +-- r-n PethPsePortIndexOrZero       eoEthPortIndex(2)
           |  +-- r-n PethPsePortGroupIndexOrZero  eoEthPortGrpIndex(3)
           |  +-- r-n LldpPortNumberOrZero         eoLldpPortNumber(4)
           |  +-- rwn SnmpAdminString              eoDomainName(5)
           |  +-- rwn SnmpAdminString              eoRoleDescription(6)
           |  +-- rwn MacAddress                   eoMgmtMacAddress(7)
           |  +-- r-n eoMgmtAddressType            eoMgmtAddressType(8)
           |  +-- r-n InetAddress                  eoMgmtAddress(9)
           |  +-- r-n SnmpAdminString              eoMgmtDNSName(10)
           |  +-- rwn SnmpAdminString              eoAlternateKey(11)
           |  +-- rwn EnergyObjectKeywordList      eoKeywords(12)
           |  +-- rwn Integer32                    eoImportance(13)
           |  +-- r-n INTEGER                      eoPowerCategory(14)
           |  +-- r-n OCTET STRING                 eoMeteredBy(15)
           |  +-- r-n OCTET STRING                 eoPoweredBy(16)
           |  +-- r-n OCTET STRING                 eoDependentOf(17)
           |  +-- r-n OCTET STRING                 eoAggregatedBy(18)
           |  +-- r-n OCTET STRING                 eoAggregatedBy(19)
           |  +-- r-n BITS                    eoParentProxyAbilities(20)
           |  +-- r-n OCTET STRING                 eoChildrenList(21)
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 12]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
     7. MIB Definitions
     
     
        -- ************************************************************
        --
        --
        -- This MIB is used for describing the identity and the
        -- context information of Energy Objects in network
        --
        --
        -- *************************************************************
     
        ENERGY-AWARE-MIB DEFINITIONS ::= BEGIN
     
        IMPORTS
            MODULE-IDENTITY,
            OBJECT-TYPE,
            mib-2,
            Integer32
                FROM SNMPv2-SMI
            TEXTUAL-CONVENTION, MacAddress, TruthValue
                FROM SNMPv2-TC
            MODULE-COMPLIANCE,
            OBJECT-GROUP
                FROM SNMPv2-CONF
            SnmpAdminString
                FROM SNMP-FRAMEWORK-MIB
            InetAddressType, InetAddress
               FROM INET-ADDRESS-MIB
            PhysicalIndexOrZero
               FROM ENTITY-MIB;
     
        energyAwareMIB MODULE-IDENTITY
            LAST-UPDATED    "201103050000Z"
            ORGANIZATION    "IETF EMAN Working Group"
            CONTACT-INFO
               "WG Charter:
                http://datatracker.ietf.org/wg/eman/charter/
     
               Mailing Lists:
                General Discussion: eman@ietf.org
                To Subscribe: https://www.ietf.org/mailman/listinfo/eman
                Archive: http://www.ietf.org/mail-archive/web/eman
     
               Editors:
                  John Parello
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 13]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
                  Cisco Systems, Inc.
                  3550 Cisco Way
                  San Jose, California 95134
                  US
                  Phone: +1 408 525 2339
                  Email: jparello@cisco.com
     
                  Benoit Claise
                  Cisco Systems, Inc.
                  De Kleetlaan 6a b1
                  Degem 1831
                  Belgium
                  Phone:  +32 2 704 5622
                  Email: bclaise@cisco.com"
     
            DESCRIPTION
               "This MIB is used for describing the identity and the
               context information of Energy Objects"
            REVISION
                "201103050000Z"
            DESCRIPTION
               "Initial version, published as RFC XXXX."
     
     
           ::= { mib-2 xxxxx }
     
        energyAwareMIBNotifs OBJECT IDENTIFIER
            ::= { energyAwareMIB 0 }
     
        energyAwareMIBObjects OBJECT IDENTIFIER
            ::= { energyAwareMIB 2 }
     
        energyAwareMIBConform  OBJECT IDENTIFIER
            ::= { energyAwareMIB 3 }
     
     
        -- Textual Conventions
     
     
        PethPsePortIndexOrZero ::= TEXTUAL-CONVENTION
        DISPLAY-HINT "d"
           STATUS            current
           DESCRIPTION
               "This textual convention is an extension of the
               pethPsePortIndex convention, which defines a greater than
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 14]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
               zero value used to identify a power Ethernet PSE port.
               This extension permits the additional value of zero.  The
               semantics of the value zero are object-specific and must,
               therefore, be defined as part of the description of any
               object that uses this syntax.  Examples of the usage of
               this extension are situations where none or all physical
               entities need to be referenced."
           SYNTAX Integer32 (0..2147483647)
     
        PethPsePortGroupIndexOrZero::= TEXTUAL-CONVENTION
        DISPLAY-HINT "d"
           STATUS            current
           DESCRIPTION
               "This textual convention is an extension of the
               pethPsePortGroupIndex convention, which defines a greater
               than zero value used to identify group containing the
               port to which a power Ethernet PSE is connected.  This
               extension permits the additional value of zero.  The
               semantics of the value zero are object-specific and must,
               therefore, be defined as part of the description of any
               object that uses this syntax.  Examples of the usage of
               this extension are situations where none or all physical
               entities need to be referenced."
           SYNTAX Integer32 (0..2147483647)
     
       LldpPortNumberOrZero ::= TEXTUAL-CONVENTION
            DISPLAY-HINT "d"
            STATUS     current
            DESCRIPTION
               "This textual convention is an extension of the
               LldpPortNumber convention specified in the LLDP MIB,
               which defines a greater than zero value used to uniquely
               identify each port contained in the chassis (that is
               known to the LLDP agent) by a port number.  This
               extension permits the additional value of zero. The
               semantics of the value zero are object-specific and must,
               therefore, be defined as part of the description of any
               object that uses this syntax.  Examples of the usage of
               this extension are situations where none or all physical
               entities need to be referenced."
          SYNTAX Integer32(0..4096)
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 15]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
       EnergyObjectKeywordList ::= TEXTUAL-CONVENTION
           STATUS          current
           DESCRIPTION
               "A list of keywords that can be used to group Energy
               Objects for reporting or searching. If multiple keywords
               are present, then this string will contain all the
               keywords separated by the ',' character. For example, if
               a Energy Object were to be tagged with the keyword values
               'hospitality' and 'guest', then the keyword list will be
               'hospitality,guest'."
           SYNTAX OCTET STRING (SIZE (0..255))
     
        -- Objects
     
        eoTablePersistence OBJECT-TYPE
            SYNTAX          TruthValue
            MAX-ACCESS      read-write
            STATUS          current
            DESCRIPTION
               "This object enables/disables persistence for
               all entries in the eoTable. A value of True enables the
               persistence, while a value of False disables the
               persistence."
            ::= { energyAwareMIBObjects 1 }
     
     
        eoTable OBJECT-TYPE
            SYNTAX          SEQUENCE OF EoEntry
            MAX-ACCESS      not-accessible
            STATUS          current
            DESCRIPTION
               "This table lists Energy Objects."
            ::= { energyAwareMIBObjects 2 }
     
        eoEntry OBJECT-TYPE
            SYNTAX          EoEntry
            MAX-ACCESS      not-accessible
            STATUS          current
            DESCRIPTION
               "An entry describes the attributes of a Energy Object.
               Whenever a new Energy Object is added or deleted a row in
               the eoTable is added or deleted."
     
            AUGMENTS        { entPhysicalIndex }
            ::= { eoTable 1 }
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 16]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        EoEntry ::= SEQUENCE {
                eoPhysicalEntity            PhysicalIndexOrZero,
                eoEthPortIndex              PethPsePortIndexOrZero,
                eoEthPortGrpIndex           PethPsePortGroupIndexOrZero,
                eoLldpPortNumber            LldpPortNumberOrZero,
                eoDomainName                SnmpAdminString,
                eoRoleDescription           SnmpAdminString,
                eoMgmtMacAddress            MacAddress,
                eoMgmtAddressType           InetAddressType,
                eoMgmtAddress               InetAddress,
                eoMgmtDNSName               SnmpAdminString,
                eoAlternateKey              SnmpAdminString,
                eoKeywords                  EnergyObjectKeywordList,
                eoImportance                Integer32,
                eoPowerCategory             INTEGER,
                eoMeteredBy                 OCTET STRING,
                eoPoweredBy                 OCTET STRING,
                eoDependentOf               OCTET STRING,
                eoAggregatedBy              OCTET STRING,
                eoProxyBy                   OCTET STRING,
                eoParentProxyAbilities      BITS,
                eoChildrenList              OCTET STRING
        }
     
        eoPhysicalEntity OBJECT-TYPE
            SYNTAX          PhysicalIndexOrZero
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
               "This object contains the index of a physical entity in
               the ENTITY MIB [RFC4133].  This physical entity is the
               given observation point.  If such a physical entity
               cannot be specified or is not known then the object is
               zero."
            ::= { eoEntry 1 }
     
        eoEthPortIndex   OBJECT-TYPE
            SYNTAX       PethPsePortIndexOrZero
            MAX-ACCESS   read-only
            STATUS       current
            DESCRIPTION
               "This variable uniquely identifies the power Ethernet
               port to which the attached device is connected [RFC3621].
               If such a power Ethernet port cannot be specified or is
               not known then the object is zero."
            ::= { eoEntry 2 }
     
        eoEthPortGrpIndex   OBJECT-TYPE
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 17]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
            SYNTAX       PethPsePortGroupIndexOrZero
            MAX-ACCESS   read-only
            STATUS       current
            DESCRIPTION
               "This variable uniquely identifies the group containing
               the port to which a power Ethernet PSE is connected
               [RFC3621].  If such a group cannot be specified or is not
               known then the object is zero."
            ::= { eoEntry 3 }
     
        eoLldpPortNumber   OBJECT-TYPE
            SYNTAX       LldpPortNumberOrZero
            MAX-ACCESS   read-only
            STATUS       current
            DESCRIPTION
              "This variable uniquely identifies the port component
              (contained in the local chassis with the LLDP agent) as
              defined by the lldpLocPortNum in the [LLDP-MIB] and
              [LLDP-MED-MIB]. If such a port number cannot be specified
              or is not known then the object is zero."
            ::= { eoEntry 4 }
     
        eoDomainName OBJECT-TYPE
            SYNTAX          SnmpAdminString
            MAX-ACCESS      read-write
            STATUS          current
            DESCRIPTION
               "This object specifies the name of a Energy Management
               Domain for the Energy Object.  This object specifies a
               null string if no Energy Management Domain name is
               configured. The value of eoDomainName must remain
               constant at least from one re-initialization of the
               entity's network management system to the next re-
               initialization."
            ::= { eoEntry 5 }
     
        eoRoleDescription OBJECT-TYPE
            SYNTAX          SnmpAdminString
            MAX-ACCESS      read-write
            STATUS          current
            DESCRIPTION
               "This object specifies an administratively assigned name
               to indicate the purpose an Energy Object serves in the
               network.
     
               For example, we can have a phone deployed to a lobby with
               eoRoleDescription as 'Lobby phone'.
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 18]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
               This object specifies a null string if no role
               description is configured."
            ::= { eoEntry 6 }
     
        eoMgmtMacAddress OBJECT-TYPE
            SYNTAX          MacAddress
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
               "This object specifies a MAC address of the Energy
               Object. This object typically only applies to Energy
               Object Children. This object can be used as an alternate
               key to help link the Energy Object with other keyed
               information that may be stored within the EnMS(s). The
               eoMgmtMacAddress MIB object SHOULD be implemented for
               Energy Object Children, and MAY be implemented for Energy
               Object Parents."
            ::= { eoEntry 7 }
     
        eoMgmtAddressType OBJECT-TYPE
            SYNTAX          InetAddressType
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
              "This object specifies the eoMgmtAddress type, i.e. an
              IPv4 address or an IPv6 address. This object MUST be
              implemented when eoMgmtAddress is populated.  The
              eoMgmtAddressType MIB object SHOULD be implemented for
              Energy Object Children, and MAY be implemented for Energy
              Object Parents."
            ::= { eoEntry 8 }
     
        eoMgmtAddress OBJECT-TYPE
            SYNTAX          InetAddress
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
              "This object specifies the management address as an IPv4
              address or IPv6 address of Energy Object. The IP address
              type, i.e. IPv4 or IPv6, is determined by the
              eoMgmtAddressType value. This object can be used as an
              alternate key to help link the Energy Object with other
              keyed information that may be stored within the EnMS(s).
              The eoMgmtAddress MIB object SHOULD be implemented for
              Energy Object Children, and MAY be implemented for Energy
              Object Parents."
            ::= { eoEntry 9 }
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 19]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        eoMgmtDNSName OBJECT-TYPE
            SYNTAX          SnmpAdminString
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
               "This object specifies the DNS name of the eoMgmtAddress.
               This object can be used as an alternate key to help link
               the Energy Object with other keyed information that may
               be stored within the EnMS(s).  The eoMgmtDNSName MIB
               objects SHOULD be implemented for Energy Object Children,
               and MAY be implemented for Energy Object Parents."
     
            ::= { eoEntry 10 }
     
        eoAlternateKey OBJECT-TYPE
            SYNTAX          SnmpAdminString
            MAX-ACCESS      read-write
            STATUS          current
            DESCRIPTION
               "This object specifies a manufacturer defined string that
               can be used to identify the Energy Object. Since Energy
               Management Systems (EnMS) and Network Management Systems
               (NMS) may need to correlate objects across management
               systems, this alternate key is provided to provide such a
               link. This optional value is intended as a foreign key or
               alternate identifier for a manufacturer or EnMS/NMS to
               use to correlate the unique Energy Object Id in other
               systems or namespaces. If an alternate key is not
               available or is not applicable then NULL should be
               returned."
            ::= { eoEntry 11 }
     
        eoKeywords OBJECT-TYPE
            SYNTAX          EnergyObjectKeywordList
            MAX-ACCESS      read-write
            STATUS          current
            DESCRIPTION
              "This object specifies a list of keywords that can be
              used to group Energy Objects for reporting or searching.
              This object specifies the null string if no keywords have
              been configured. If multiple keywords are present, then
              this string will contain all the keywords separated by
              the ',' character. For example, if a Energy Object were
              to be tagged with the keyword values 'hospitality' and
              'guest', then the keyword list will be
              'hospitality,guest'.
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 20]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
               If write access is implemented and a value is written
               into the instance, the agent must retain the supplied
               value in the eoKeywords instance associated with
               the same physical entity for as long as that entity
               remains instantiated.  This includes instantiations
               across all re-initializations/reboots of the network
               management system."
            ::= { eoEntry 12 }
     
        eoImportance OBJECT-TYPE
            SYNTAX          Integer32 (1..100)
            MAX-ACCESS      read-write
            STATUS          current
            DESCRIPTION
               "This object specifies a ranking of how important the
               Energy Object is (on a scale of 1 to 100) compared with
               other Energy Objects in the same Energy Management
               Domain. The ranking should provide a business or
               operational context for the Energy Object as compared to
               other similar Energy Objects. This ranking could be used
               as input for policy-based network management.
     
     
               Although network managers must establish their own
               ranking, the following is a broad recommendation:
     
               90 to 100 Emergency response
               80 to 90 Executive or business critical
               70 to 79 General or Average
               60 to  69 Staff or support
               40 to  59 Public or guest
               1  to 39 Decorative or hospitality"
            DEFVAL          { 1 }
            ::= { eoEntry 13 }
     
        eoPowerCategory OBJECT-TYPE
            SYNTAX          INTEGER {
                                consumer(0),
                                producer(1),
                                consumer-producer(2),
                                meter(3)
                            }
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
               "This object describes the Energy Object category, which
               indicates the expected behavior or physical property of
               the Energy Object, based on its design. A Energy Object
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 21]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
               can be a consumer(0), producer(1) or consumer-producer
               (2) or meter (3).
     
               There are devices with a dual mode - consuming energy and
               producing of energy and those are identified as consumer-
               producer.
     
               In some cases, a meter is required to measure the power
               consumption. In such a case, this meter Energy Object
               category is meter(3). "
            ::= { eoEntry 14 }
     
        eoMeteredBy OBJECT-TYPE
            SYNTAX      OCTET STRING
            MAX-ACCESS  read-only
            STATUS      current
            DESCRIPTION
              "When this Energy Object is an Energy Object Child, this
              object represents the list of Energy Object Parent
              Universally Unique Identifiers (UUIDs) for the Metering
              Relationship.
     
              The UUIDs must comply to the RFC 4122 specifications.
     
              The object contains URIs and, therefore, the syntax of
              this object must conform to RFC 3986, section 2.
     
              Multiple URIs may be present and are separated by white
              space characters.  Leading and trailing white space
              characters are ignored.
     
              If this Energy Object is not an Energy Object Child, or
              if the Energy Object doesn't have a Metering
              Relationship, the object is not instantiated.  A zero
              length octet string may also be returned in this case."
            REFERENCE
              "RFC 3986, Uniform Resource Identifiers (URI): Generic
              Syntax, section 2, August 1998.
              RFC 4122, Uniform Resource Identifier (UUID) URN
              Namespace, July 2005."
            ::= { eoEntry 15 }
     
        eoPoweredBy OBJECT-TYPE
            SYNTAX      OCTET STRING
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 22]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
            MAX-ACCESS  read-only
            STATUS      current
            DESCRIPTION
              "When this Energy Object is an Energy Object Child, this
              object represents the list of Energy Object Parent
              Universally Unique Identifiers (UUIDs) for the Power
              Source Relationship.
     
              The UUIDs must comply to the RFC 4122 specifications.
     
              The object contains URIs and, therefore, the syntax of
              this object must conform to RFC 3986, section 2.
     
              Multiple URIs may be present and are separated by white
              space characters.  Leading and trailing white space
              characters are ignored.
     
              If this Energy Object is not an Energy Object Child, or
              if the Energy Object doesn't have a Power Source
              Relationship, the object is not instantiated.  A zero
              length octet string may also be returned in this case."
            REFERENCE
              "RFC 3986, Uniform Resource Identifiers (URI): Generic
              Syntax, section 2, August 1998.
              RFC 4122, Uniform Resource Identifier (UUID) URN
              Namespace, July 2005."
            ::= { eoEntry 16 }
     
        eoDependentOf OBJECT-TYPE
            SYNTAX      OCTET STRING
            MAX-ACCESS  read-only
            STATUS      current
            DESCRIPTION
              "When this Energy Object is an Energy Object Child, this
              object represents the list of Energy Object Parent
              Universally Unique Identifiers (UUIDs) for the Dependency
              Relationship.
     
              The UUIDs must comply to the RFC 4122 specifications.
     
              The object contains URIs and, therefore, the syntax of
              this object must conform to RFC 3986, section 2.
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 23]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
              Multiple URIs may be present and are separated by white
              space characters.  Leading and trailing white space
              characters are ignored.
     
              If this Energy Object is not an Energy Object Child, or
              if the Energy Object doesn't have a Dependency
              Relationship, the object is not instantiated.  A zero
              length octet string may also be returned in this case."
            REFERENCE
              "RFC 3986, Uniform Resource Identifiers (URI): Generic
              Syntax, section 2, August 1998.
              RFC 4122, Uniform Resource Identifier (UUID) URN
              Namespace, July 2005."
            ::= { eoEntry 17 }
     
        eoAggregatedBy OBJECT-TYPE
            SYNTAX      OCTET STRING
            MAX-ACCESS  read-only
            STATUS      current
            DESCRIPTION
              "When this Energy Object is an Energy Object Child, this
              object represents the list of Energy Object Parent
              Universally Unique Identifiers (UUIDs) for the
              Aggregation Relationship.
     
              The UUIDs must comply to the RFC 4122 specifications.
     
              The object contains URIs and, therefore, the syntax of
              this object must conform to RFC 3986, section 2.
     
              Multiple URIs may be present and are separated by white
              space characters.  Leading and trailing white space
              characters are ignored.
     
              If this Energy Object is not an Energy Object Child, or
              if the Energy Object doesn't have a Aggregation
              Relationship, the object is not instantiated.  A zero
              length octet string may also be returned in this case."
            REFERENCE
              "RFC 3986, Uniform Resource Identifiers (URI): Generic
              Syntax, section 2, August 1998.
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 24]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
              RFC 4122, Uniform Resource Identifier (UUID) URN
              Namespace, July 2005."
            ::= { eoEntry 18 }
     
        eoProxyBy OBJECT-TYPE
            SYNTAX      OCTET STRING
            MAX-ACCESS  read-only
            STATUS      current
            DESCRIPTION
              "When this Energy Object is an Energy Object Child, this
              object represents the list of Energy Object Parent
              Universally Unique Identifiers (UUIDs) for the Proxy
              Relationship.
     
              The UUIDs must comply to the RFC 4122 specifications.
     
              The object contains URIs and, therefore, the syntax of
              this object must conform to RFC 3986, section 2.
     
              Multiple URIs may be present and are separated by white
              space characters.  Leading and trailing white space
              characters are ignored.
     
              If this Energy Object is not an Energy Object Child, or
              if the Energy Object doesn't have a Proxy Relationship,
              the object is not instantiated.  A zero length octet
              string may also be returned in this case."
            REFERENCE
              "RFC 3986, Uniform Resource Identifiers (URI): Generic
              Syntax, section 2, August 1998.
              RFC 4122, Uniform Resource Identifier (UUID) URN
              Namespace, July 2005."
            ::= { eoEntry 19 }
     
        eoParentProxyAbilities OBJECT-TYPE
            SYNTAX          BITS {
                                none(0),
                                report(1),
                                configuration(2),
                                wakeonlan(3)
                            }
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 25]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
               "This object describes the capabilities of the Energy
               Object Parent for the Energy Object Child represented by
               the entPhysicalIndex. This object only applies to a
               Energy Object Child.
               None (0) MUST be used when the Energy Object represented
               by the entPhysicalIndex is a Energy Object Parent, and no
               other bit can be set.
               Report(1) indicates that the Energy Object Parent reports
               the usage for the Energy Object Child represented by the
               entPhysicalIndex.
               Configuration(2) indicates that the Energy Object Parent
               can configure the Power Level for the Energy Object Child
               Child represented by the entPhysicalIndex.
               Wakeonlan(3) indicates that the Energy Object Parent can
               wake up the Energy Object Child, Child represented by the
               entPhysicalIndex, whatever the mechanism."
            ::= { eoEntry 20 }
     
     
        eoChildrenList  OBJECT-TYPE
            SYNTAX      OCTET STRING
            MAX-ACCESS  read-only
            STATUS      current
            DESCRIPTION
              "When this Energy Object is an Energy Object Parent, this
              object represents the list of Energy Object Children
              Universally Unique Identifiers (UUIDs).
     
              The UUIDs must comply to the RFC 4122 specifications.
     
              The object contains URIs and, therefore, the syntax of
              this object must conform to RFC 3986, section 2.
     
              Multiple URIs may be present and are separated by white
              space characters.  Leading and trailing white space
              characters are ignored.
     
              If this Energy Object is not an Energy Object Parent, the
              object is not instantiated.  A zero length octet string
              may also be returned in this case."
            REFERENCE
              "RFC 3986, Uniform Resource Identifiers (URI): Generic
              Syntax, section 2, August 1998.
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 26]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
              RFC 4122, Uniform Resource Identifier (UUID) URN
              Namespace, July 2005."
            ::= { eoEntry 21 }
     
     
        -- Conformance
     
        energyAwareMIBCompliances  OBJECT IDENTIFIER
            ::= { energyAwareMIBObjects 3 }
     
        energyAwareMIBGroups  OBJECT IDENTIFIER
            ::= { energyAwareMIBObjects 4 }
     
     
        energyAwareMIBFullCompliance MODULE-COMPLIANCE
            STATUS          current
            DESCRIPTION
                "When this MIB is implemented with support for
                read-create, then such an implementation can
                claim full compliance. Such devices can then
                be both monitored and configured with this MIB."
            MODULE          -- this module
            MANDATORY-GROUPS {
                        energyAwareMIBTableGroup
                            }
     
            ::= { energyAwareMIBCompliances 1 }
     
        energyAwareMIBReadOnlyCompliance MODULE-COMPLIANCE
            STATUS          current
            DESCRIPTION
                "When this MIB is implemented without support for
                read-create (i.e. in read-only mode), then such an
                implementation can claim read-only compliance.  Such a
                device can then be monitored but cannot be configured
                with this MIB."
            MODULE          -- this module
            MANDATORY-GROUPS {
                         energyAwareMIBTableGroup
                            }
     
            OBJECT          eoTablePersistence
            MIN-ACCESS      read-only
            DESCRIPTION
                "Write access is not required."
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 27]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
            OBJECT          eoDomainName
            MIN-ACCESS      read-only
            DESCRIPTION
                "Write access is not required."
     
            OBJECT          eoRoleDescription
            MIN-ACCESS      read-only
            DESCRIPTION
                "Write access is not required."
     
            OBJECT          eoKeywords
            MIN-ACCESS      read-only
            DESCRIPTION
            "Write access is not required."
     
            OBJECT          eoImportance
            MIN-ACCESS      read-only
            DESCRIPTION
                "Write access is not required."
     
        ::= { energyAwareMIBCompliances 2 }
     
        -- Units of Conformance
     
        energyAwareMIBTableGroup OBJECT-GROUP
            OBJECTS         {
                                eoTablePersistence,
                                eoPhysicalEntity,
                                eoEthPortIndex,
                                eoEthPortGrpIndex,
                                eoLldpPortNumber,
                                eoDomainName,
                                eoRoleDescription,
                                eoMgmtMacAddress,
                                eoMgmtAddressType,
                                eoMgmtAddress,
                                eoMgmtDNSName,
                                eoAlternateKey,
                                eoKeywords,
                                eoImportance,
                                eoPowerCategory,
                                eoMeteredBy,
                                eoPoweredBy,
                                eoDependentOf,
                                eoAggregatedBy,
                                eoProxyBy,
                                eoParentProxyAbilities,
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 28]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
                                eoChildrenList
                            }
            STATUS          current
            DESCRIPTION
                "This group contains the collection of all the objects
                related to the EnergyObject."
            ::= { energyAwareMIBGroups 1 }
     
     
        END
     
     
     8. Security Considerations
     
        Some of the readable objects in these MIB modules (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.
     
        There are a number of management objects defined in these MIB
        modules 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.  The following are the
        tables and objects and their sensitivity/vulnerability:
     
          . Unauthorized changes to the eoDomainName, entPhysicalName,
             eoRoleDescription, eoKeywords, and/or eoImportance MAY
             disrupt power and energy collection, and therefore any
             predefined policies defined in the network.
     
     
        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 secure control over who on the secure
        network is allowed to access and GET/SET
        (read/change/create/delete) the objects in these MIB modules.
     
     
     
        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).
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 29]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        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 these MIB modules is properly configured to give
        access to the objects only to those principals (users) that have
        legitimate rights to 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
          ----------                         -----------------------
          energyAwareMIB                     { mib-2 xxx }
     
        Additions to this MIB module are subject to Expert Review
        [RFC5226], i.e., review by one of a group of experts designated
        by an IETF Area Director.  The group of experts MUST check the
        requested MIB objects for completeness and accuracy of the
        description.  Requests for MIB objects that duplicate the
        functionality of existing objects SHOULD be declined.  The
        smallest available OID SHOULD be assigned to a new MIB objects.
        The specification of new MIB objects SHOULD follow the structure
        specified in Section 6 and MUST be published using a well-
        established and persistent publication medium.
     
     
     10. References
     
     10.1. Normative References
     
     
        [RFC2119] S. Bradner, 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",
                STD 58, RFC 2579, April 1999.
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 30]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
        [RFC2580]  McCloghrie, K., Perkins, D., and J. Schoenwaelder,
                "Conformance Statements for SMIv2", STD 58, RFC 2580,
                April 1999.
     
        [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB",
                RFC3621, December 2003.
     
        [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,
                "Uniform Resource Identifier (URI): Generic Syntax",
                RFC 3986, January 2005
     
        [RFC4122]  Leach, P., Mealling, M., and R. Salz, "A Universally
                Unique IDentifier (UUID) URN Namespace ", RFC 4122,
                July 2005.
     
        [RFC4133]  Bierman, A. and K. McCloghrie, "Entity MIB (Version
                3)", RFC 4133, August 2005.
     
        [LLDP-MIB] IEEE 802.1AB-2005, "Management Information Base
                module for LLDP configuration, statistics, local system
                data and remote systems data components", May 2005.
     
        [LLDP-MED-MIB]  ANSI/TIA-1057, "The LLDP Management Information
                Base extension module for TIA-TR41.4 media endpoint
                discovery information", July 2005.
     
        [EMAN-MON-MIB] M. Chandramouli, Schoening, B., Quittek, J.,
                Dietz, T., and B. Claise  "Power and Energy Monitoring
                MIB", draft-ietf-eman-energy-monitoring-mib-01, October
                2011.
     
     10.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.
     
        [RFC5226]  Narten, T. Alverstrand, H., A. and K. McCloghrie,
                "Guidelines for Writing an IANA Considerations Section
                in RFCs ", BCP 26, RFC 5226, May 2008.
     
        [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and
                M. Chandramouli, " Requirements for Energy Management",
                draft-ietf-eman-requirements-04, work in progress, July
                2011.
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 31]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
        [EMAN-FMWK] Claise, B., Parello, J., Schoening, B., and J.
                Quittek, "Energy Management Framework", draft-ietf-
                eman-framework-03, work in progress, October 2011.
     
        [EMAN-AS] Tychon, E., Schoening, B., Chandramouli, M, and B.
                Nordman, "Energy Management (EMAN) Applicability
                Statement", draft-tychon-eman-applicability-statement-
                05.txt, work in progress, October 2011.
     
        [EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology",
                draft-parello-eman-definitions-03, work in progress,
                October 2011
     
     
     
     11. Acknowledgments
     
        The authors would like to thank Juergen Quittek, Brad Schoening,
        Mouli Chandramouli, Juergen Schoenwaelder for their help, and
        Michael Brown for improving the text dramatically.
     
     
     
      Authors' Addresses
     
      Benoit Claise
      Cisco Systems, Inc.
      De Kleetlaan 6a b1
      Diegem 1813
      BE
     
      Phone: +32 2 704 5622
      Email: bclaise@cisco.com
     
     
      John Parello
      Cisco Systems, Inc.
      3550 Cisco Way
      San Jose, California 95134
      US
     
      Phone: +1 408 525 2339
      Email: jparello@cisco.com
     
     
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 32]


     Internet-Draft <Energy-aware Networks and Devices MIB> Oct 2011
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     <Parello, Claise>       Expires April 30, 2012           [Page 33]
     

Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/