idnits 2.17.1 draft-ietf-eman-energy-aware-mib-16.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 226 has weird spacing: '...xOrZero eoEth...' == Line 486 has weird spacing: '... if the power...' == Line 950 has weird spacing: '... of the entit...' -- The document date (July 4, 2014) is 3583 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MED-MIB' == Outdated reference: A later version (-13) exists of draft-ietf-eman-energy-monitoring-mib-10 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-11) exists of draft-ietf-eman-applicability-statement-06 -- Obsolete informational reference (is this intentional?): RFC 6982 (Obsoleted by RFC 7942) Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Parello 3 Internet-Draft B. Claise 4 Intended Status: Standards Track Mouli Chandramouli 5 Expires: January 4, 2014 Cisco Systems, Inc. 6 July 4, 2014 8 Energy Object Context MIB 9 draft-ietf-eman-energy-aware-mib-16 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance 14 with the provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet 17 Engineering Task Force (IETF), its areas, and its working 18 groups. Note that other groups may also distribute working 19 documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other 23 documents at any time. It is inappropriate to use Internet- 24 Drafts as reference material or to cite them other than as "work 25 in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 This Internet-Draft will expire on January 4, 2014. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with 45 respect to this document. Code Components extracted from this 46 document must include Simplified BSD License text as described 47 in Section 4.e of the Trust Legal Provisions and are provided 48 without warranty as described in the Simplified BSD License. 50 Abstract 52 This document defines a subset of a Management Information Base 53 (MIB) for energy management of devices. The module addresses 54 device identification, context information, and the energy 55 relationships between devices. 57 Conventions used in this document 59 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 60 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT 61 RECOMMENDED", "MAY", and "OPTIONAL" in this document are to 62 be interpreted as described in RFC 2119 [RFC2119]. 64 Table of Contents 66 1. Introduction............................................. 3 67 1.1. Energy Management Document Overview..................3 68 2. The Internet-Standard Management Framework............... 4 69 3. Terminology.............................................. 4 70 4. Architecture Concepts Applied to the MIB Module.......... 5 71 4.1 Energy Object Identification..........................8 72 4.2 Energy Object Context.................................9 73 4.3 Links to Other Identifiers...........................10 74 4.4 Energy Object Relationships..........................11 75 4.5 Energy Object Identity Persistence...................12 76 5. MIB Definitions......................................... 12 77 6. Implementation Status................................... 28 78 6.1 SNMP Research.......................................... 29 79 6.2 Python................................................. 29 80 7. Security Considerations................................. 29 81 8. IANA Considerations..................................... 30 82 9. Acknowledgement......................................... 31 83 10. References............................................. 32 84 10.1. Normative References...............................32 85 10.2. Informative References.............................33 87 1. Introduction 89 The EMAN standards provide a specification for Energy 90 Management. This document defines a subset of a Management 91 Information Base (MIB) for use with network management protocols 92 for Energy monitoring of network devices and devices attached to 93 the network and possibly extending to devices in the industrial 94 automation setting with a network interface. 96 The focus of the MIB module specified in this document is on the 97 identification of Energy Objects and reporting the context and 98 relationships of Energy Objects as defined in [EMAN-FMWK]. The 99 module addresses Energy Object identification, Energy Object 100 context, and Energy Object relationships. 102 1.1. Energy Management Document Overview 104 This document specifies the Energy Object Context (ENERGY- 105 OBJECT-CONTEXT-MIB) and IANA Energy Relationship (IANA-ENERGY- 106 RELATION-MIB) modules. The Energy Object Context MIB module 107 specifies MIB objects for identification of Energy Objects, and 108 reporting context and relationship of an Energy Object. The IANA 109 Energy Relationship MIB module specifies the first version of 110 the IANA-maintained definitions of relationships between Energy 111 Objects. 113 Firstly, to illustrate the importance of energy monitoring in 114 networks and secondly to list some of the important areas to be 115 addressed by the Energy Management Framework, several use cases 116 and network scenarios are presented in the EMAN applicability 117 statement document [EMAN-AS]. In addition, for each scenario, 118 the target devices for energy management, and how those devices 119 powered and metered are also presented. To address the network 120 scenarios, requirements for power and energy monitoring for 121 networking devices are specified in [RFC6988]. Based on the 122 requirements [RFC6988], the [EMAN-FMWK] presents a solution 123 approach. 125 Accordingly, the scope of the MIB modules in this document is in 126 accordance to the requirements specified in [RFC6988] and the 127 concepts from [EMAN-FMWK]. 129 This document is based on the Energy Management Framework [EMAN- 130 FMWK] and meets the requirements on identification of Energy 131 Objects and their context and relationships as specified in the 132 Energy Management requirements [RFC6988]. 134 A second MIB module meeting the EMAN requirements [RFC6988] the 135 Power and Energy Monitoring MIB [EMAN-MON-MIB], monitors the 136 Energy Objects for Power States, for the Power and Energy 137 consumption. Power State monitoring includes: retrieving Power 138 States, Power State properties, current Power State, Power State 139 transitions, and Power State statistics. In addition, this MIB 140 module provides the Power Characteristics properties of the 141 Power and Energy, along with optional characteristics. 143 The applicability statement document [EMAN-AS] provides the list 144 of use cases, and describes the common aspects of between 145 existing Energy standards and the EMAN standard, and shows how 146 the EMAN framework relates to other frameworks. 148 2. The Internet-Standard Management Framework 150 For a detailed overview of the documents that describe the 151 current Internet-Standard Management Framework, please refer to 152 section 7 of RFC 3410 [RFC3410]. 154 Managed objects are accessed via a virtual information store, 155 termed the Management Information Base or MIB. MIB objects are 156 generally accessed through the Simple Network Management 157 Protocol (SNMP). Objects in the MIB are defined using the 158 mechanisms defined in the Structure of Management Information 159 (SMI). This memo specifies MIB modules that are compliant with 160 SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 161 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 163 3. Terminology 165 Please refer to [EMAN-FMWK] for the definitions of the following 166 terminology used in this draft. 168 Energy Management 169 Energy Management System (EnMS) 170 Energy Monitoring 171 Energy Control 172 electrical equipment 173 non-electrical equipment (mechanical equipment) 174 device 175 component 176 power inlet 177 power outlet 178 energy 179 power 180 demand 181 provide energy 182 receive energy 183 meter (energy meter) 184 battery 185 Power Interface 186 Nameplate Power 187 Power Attributes 188 Power Quality 189 Power State 190 Power State Set 192 4. Architecture Concepts Applied to the MIB Module 194 This section describes the basic concepts specified in the 195 Energy Management Architecture [EMAN-FMWK], with specific 196 information related to the MIB modules specified in this 197 document. 199 The Energy Object Context (ENERGY-OBJECT-CONTEXT-MIB) MIB module 200 in this document specifies MIB objects for identification of 201 Energy Objects, and reporting context and relationship of an 202 Energy Object. The managed objects are contained in two tables 203 eoTable and eoRelationTable. 205 The first table eoTable focuses on the link to the other MIB 206 modules, on identification and context of the Energy Object. The 207 second table eoRelationTable specifies the relationships between 208 Energy Objects. This is a simplified representation of 209 relationship between Energy Objects. 211 A "smidump-style" tree presentation of the MIB modules contained 212 in the draft is presented. The meaning of the three symbols in 213 is a compressed representation of the object's MAX-ACCESS clause 214 which may have the following values: 216 "not-accessible"->"---" 217 "accessible-for-notify"->"--n" 218 "read-only"->"r-n" 219 "read-write"->"rwn" 221 +- eoTable(1) 222 | 223 +- eoEntry(1) [entPhysicalIndex] 224 | 225 +-- r-n PethPsePortIndexOrZero eoEthPortIndex(1) 226 +-- r-n PethPsePortGroupIndexOrZero eoEthPortGrpIndex(2) 227 +-- r-n LldpPortNumberOrZero eoLldpPortNumber(3) 228 +-- rwn MacAddress eoMgmtMacAddress(4) 229 +-- r-n InetAddressType eoMgmtAddressType(5) 230 +-- r-n InetAddress eoMgmtAddress(6) 231 +-- r-n OCTET STRING eoMgmtDNSName(7) 232 +-- rwn SnmpAdminString eoDomainName(8) 233 +-- rwn SnmpAdminString eoRoleDescription(9) 234 +-- rwn EnergyObjectKeywordList eoKeywords(10) 235 +-- rwn Integer32 eoImportance(11) 236 +-- r-n INTEGER eoPowerCategory(12) 237 +-- rwn SnmpAdminString eoAlternateKey(13) 238 +-- r-n INTEGER eoPowerInterfaceType(14) 240 +- eoRelationTable(2) 241 | 242 +- eoRelationEntry(1) [entPhysicalIndex, eoRelationIndex] 243 | 244 +-- --n Integer32 eoRelationIndex(1) 245 +-- rwn UUIDorZero eoRelationID(2) 246 +-- rwn IANAEnergyRelationship eoRelationship(3) 247 +-- rwn RowStatus eoRelationStatus(4) 248 +-- rwn StorageType eoRelationStorageType(5) 250 The following UML diagram illustrates the relationship of the 251 MIB objects in the eoTable, eoRelationTable and ENTITY-MIB. The 252 MIB objects describe the identity, context and relationship of 253 an Energy Object. The UML diagram furthermore contains objects 254 from the ENTITY-MIB [RFC6933]. 256 +--------------------------+ 257 | EO Context Information | 258 | ------------------------ | 259 | eoRoleDescription | 260 | eoKeywords | 261 | eoImportance | 262 | eoPowerCategory | 263 | eoPowerInterfaceType | 264 | eoDomainName | 265 +--------------------------+ 266 ^ 267 | 268 | 269 +------------------------------+ 270 |--- | EO Identification | 271 | | ---------------------------- | 272 | | entPhysicalIndex (*) | 273 | | entPhysicalName (*) | 274 | | entPhysicalUUID (*) | 275 | | entPhysicalClass (*) | 276 | -------------------------------- 277 | 278 | +------------------------------+ 279 |---> | Link to other identifiers | 280 | |------------------------------| 281 | | eoEthPortIndex (**) | 282 | | eoEthPortGrpIndex (**) | 283 | | eoLldpPortNumber (***) | 284 | | | 285 | | eoMgmtMacAddress (optional) | 286 | | eoMgmtAddressType (optional) | 287 | | eoMgmtAddress (optional) | 288 | | eoMgmtDNSName (optional) | 289 | | eoAlternateKey | 290 | +------------------------------+ 291 | 292 | +------------------------------+ 293 |---> | EO Relationship | 294 | ---------------------------- | 295 | eoRelationIndex | 296 | eoRelationID | 297 | eoRelationship | 298 | eoRelationStatus | 299 | eoRelationStorageType | 300 +------------------------------+ 302 (*) Compliance with entity4CRCompliance ENTITY MIB[RFC6933] 303 (**) Link with the Power over Ethernet MIB [RFC3621] 304 (***) Link with LLDP MIBs [LLDP-MIB] [LLDP-MED-MIB] 306 Figure 1: MIB Objects Grouping 308 As displayed in figure 1, the MIB objects can be classified in 309 different logical grouping of MIB objects. 311 1) The Energy Object Identification. See Section 5.1 "Energy 312 Object Identification". Devices and their sub-components are 313 characterized by the power-related attributes of a physical 314 entity present in the ENTITY MIB [RFC6933]. 315 2) The Context Information. See Section 5.2 "Energy Object 316 Context" 317 3) The links to other MIB modules. See Section 5.3 "Links to 318 other Identifiers" 319 4) The Energy Object Relationships specific information. See 320 Section 5.4 321 5) The Energy Object Identity Persistence. See Section 5.5 322 "Energy Object Identity Persistence" 324 4.1 Energy Object Identification 326 Refer to the "Energy Object Information" section in [EMAN-FMWK] 327 for background information about Energy Objects. 329 Every Energy Object MUST implement the unique index, 330 entPhysicalIndex, entPhysicalName, entPhysicalClass, and 331 entPhysicalUUID from the ENTITY MIB [RFC6933]. Module Compliance 332 with respect to entity4CRCompliance of ENTITY-MIB MUST be 333 supported which require a limited number of objects supported 334 (entPhysicalIndex, entPhysicalName, entPhysicalClass, and 335 entPhysicalUUID). entPhysicalIndex is used as index for the 336 Energy Object in the ENERGY-OBJECT-CONTEXT-MIB module. 337 Every Energy Object MUST have a printable name assigned to it. 338 Energy Objects MUST implement the entPhysicalName object 339 specified in the ENTITY-MIB [RFC6933], which must contain the 340 Energy Object name. 342 For the ENERGY-OBJECT-CONTEXT-MIB compliance, every Energy 343 Object instance MUST implement the entPhysicalUUID from the 344 ENTITY MIB [RFC6933]. 346 As displayed in [RFC4122], the following is an example of the 347 string representation of a UUID as a URN: urn:uuid:f81d4fae- 348 7dec-11d0-a765-00a0c91e6bf6. 350 For example, to understand the relationship between Energy 351 Object Components and Energy Objects, the ENTITY-MIB physical 352 containment tree [RFC6933] MUST be implemented. 354 A second example deals with one of the ENTITY-MIB extensions: if 355 the Energy Object temperature is required, the managed objects 356 from the ENTITY-SENSOR-MIB [RFC3433] should be supported. 358 Each Energy Object MUST belong to a single Energy Management 359 Domain or in other words, an Energy Object cannot belong to more 360 than one Energy Management Domain. Refer to the "Energy 361 Management Domain" section in [EMAN-FMWK] for background 362 information. The eoDomainName, which is an element of the 363 eoTable, is a read-write MIB object. The Energy Management 364 Domain should map 1-1 with a metered or sub-metered portion of 365 the network. The Energy Management Domain MUST be configured on 366 the Energy Object. The Energy Object MAY inherit the some of the 367 domain parameters (possibly domain name, some of the context 368 information such as role or keywords, importance) from the 369 Energy Object or the Energy Management Domain MAY be configured 370 directly in an Energy Object. 372 When an Energy Object acts as a Power Aggregator, the Energy 373 Objects for which Power should be aggregated MUST be members of 374 the same Energy Management Domain, specified by the eoDomainName 375 MIB Object. 377 4.2 Energy Object Context 379 Refer to the "Energy Object Context" section in [EMAN-FMWK] for 380 background information. 382 An Energy Object must provide a value for eoImportance in the 383 range of 1...100 to help differentiate the use or relative value 384 of the device. The importance range is from 1 (least important) 385 to 100 (most important). The default importance value is 1. 387 An Energy Object can provide a set of eoKeywords. These keywords 388 are a list of tags that can be used for grouping and summary 389 reporting within or between Energy Management Domains. 391 An Energy Object can have Power Interfaces and those interfaces 392 can be classified as Power Inlet, Power Outlet or both. 394 An Energy Object can be classified based on the physical 395 properties of the Energy Object. That Energy Object can be 396 classified as consuming power or supplying power to other 397 devices or that Energy Object can perform both of those 398 functions and finally, an Energy Object can be a passive meter. 400 Additionally, an Energy Object can provide an eoRoleDescription 401 string that indicates the purpose the Energy Object serves in 402 the network. 404 4.3 Links to Other Identifiers 406 While the entPhysicalIndex is the primary index for all MIB 407 objects in the ENERGY-OBJECT-CONTEXT-MIB module, the Energy 408 Management Systems (EnMS) must be able to make the link with the 409 identifier(s) in other supported MIB modules. 411 If the Energy Object is a Power over Ethernet (PoE) port, and if 412 the Power over Ethernet MIB [RFC3621] is supported by the SNMP 413 agent managing the Energy Object, then the Energy Object 414 eoethPortIndex and eoethPortGrpIndex MUST contain the 415 corresponding values of pethPsePortIndex and 416 pethPsePortGroupIndex [RFC3621]. 418 If the LLDP-MED MIB [LLDP-MIB] is supported by the Energy Object 419 SNMP agent, then the Energy Object eoLldpPortNumber MUST contain 420 the corresponding lldpLocPortNum from the LLDP MIB. 422 The intent behind the links to the other MIB module 423 identifier(s) is to correlate the instances in the different MIB 424 modules. This will allow the ENERGY-OBJECT-CONTEXT-MIB module to 425 reference other MIB modules in cases where the Power over 426 Ethernet and the LLDP MIB modules are supported by the SNMP 427 agent. Some use cases may not implement any of these two MIB 428 modules for the Energy Objects. However, in situation where any 429 of these two MIB modules are implemented, the EnMS must be able 430 to correlate the instances in the different MIB modules. 432 The eoAlternateKey object specifies an alternate key string that 433 can be used to identify the Energy Object. Since an EnMS may 434 need to correlate objects across management systems, this 435 alternate key is provided to facilitate such a link. This 436 optional value is intended as a foreign key or alternate 437 identifier for a manufacturer or EnMS to use to correlate the 438 unique Energy Object Id in other systems or namespaces. If an 439 alternate key is not available or is not applicable then the 440 value is the zero-length string. 442 An Energy Object can have additional MIB objects that can be 443 used for easier identification by the EnMS. The optional objects 444 eoMgmtMacAddress, eoMgmtAddressType eoMgmtDNSName can be used to 445 help identify the relationship between the Energy Objects and 446 other NMS objects. These objects can be used as an alternate 447 key to help link the Energy Object with other keyed information 448 that may be stored within the EnMS(s). For the optional objects 449 that may not be included in some vendor implementations, the 450 expected behavior when those objects are polled is a response 451 noSuchInstance. 453 4.4 Energy Object Relationships 455 Refer to the "Energy Object Relationships" section in [EMAN- 456 FMWK] for the definition and background information.In order to 457 link two Energy Objects a separate table (eoRelationTable) has 458 been introduced in this MIB module. 460 Each Energy object can have one or more Energy Object 461 relationships with other Energy Objects. The relationship 462 between Energy Objects are specified in eoRelationTable. The 463 relationship between the Energy Objects is specified with the 464 entPhysicalIndex of the Energy Object and the UUID of the remote 465 Energy Object. The UUID MUST comply to the RFC 4122 466 specifications. It is important to note that it is possible 467 that an Energy Object may not have an Energy Object relationship 468 with other Energy Objects. 470 The following relationships between Energy objects have been 471 considered in the eoRelationTable. 473 Metering Relationship -> meteredBy / metering 475 Power Source Relationship -> poweredBy / powering 477 Aggregation Relationship -> aggregatedBy / aggregating 479 An Energy Object B has "meteredBy" relationship with Energy 480 Object A, if the energy consumption of Energy Object B is 481 measured by Energy Object A. Equivalently, it is possible to 482 indicate that Energy Object A has "metering" relationship with 483 Energy Object B. 485 An Energy Object B has "poweredBy" relationship with Energy 486 Object A, if the power source of Energy Object B Energy Object 487 A. Equivalently, it is possible to indicate that Energy Object A 488 has "powering" relationship with Energy Object B. 490 An Energy Object B has "aggregatedBy" relationship with Energy 491 Object A, if Energy Object A is an aggregation point for energy 492 usage of Energy Object B. Equivalently, it is possible to 493 indicate that Energy Object A has "aggregating" relationship 494 with Energy Object B. 496 The IANA Energy Relationship MIB module in Section 6 below 497 specifies the first version of the IANA-maintained definitions 498 of relationships. This way, for Energy Relationships, new 499 textual conventions can be specified, without updating the 500 primary Energy Object Context MIB module. 502 4.5 Energy Object Identity Persistence 504 In some situations, the Energy Object identity information 505 should be persistent even after a device reload. For example, in 506 a static setup where a switch monitors a series of connected PoE 507 phones, there is a clear benefit for the EnMS if the Energy 508 Object Identification and all associated information persist, as 509 it saves a network discovery. However, in other situations, 510 such as a wireless access point monitoring the mobile user PCs, 511 there is not much advantage to persist the Energy Object 512 Information. The identity information of an Energy Object 513 should be persisted and there is value in the writable MIB 514 objects persisted. 516 5. MIB Definitions 518 -- ************************************************************ 519 -- 520 -- 521 -- This MIB is used for describing the identity and the 522 -- context information of Energy Objects in network 523 -- 524 -- 525 -- ************************************************************* 527 ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN 529 IMPORTS 530 MODULE-IDENTITY, 531 OBJECT-TYPE, 532 mib-2, Integer32 533 FROM SNMPv2-SMI -- RFC2578 534 TEXTUAL-CONVENTION, MacAddress, TruthValue, 535 RowStatus, StorageType 536 FROM SNMPv2-TC -- RFC2579 537 MODULE-COMPLIANCE, OBJECT-GROUP 538 FROM SNMPv2-CONF -- RFC2580 539 SnmpAdminString 540 FROM SNMP-FRAMEWORK-MIB -- RFC3411 541 InetAddressType, InetAddress 542 FROM INET-ADDRESS-MIB -- RFC3291 543 entPhysicalIndex 544 FROM ENTITY-MIB -- RFC6933 545 UUIDorZero 546 FROM UUID-TC-MIB -- RFC6933 547 IANAEnergyRelationship 548 FROM IANA-ENERGY-RELATION-MIB; 550 energyObjectContextMIB MODULE-IDENTITY 551 LAST-UPDATED "201406110000Z" 553 ORGANIZATION "IETF EMAN Working Group" 554 CONTACT-INFO 555 "WG Charter: 556 http://datatracker.ietf.org/wg/eman/charter/ 558 Mailing Lists: 559 General Discussion: eman@ietf.org 560 To Subscribe: https://www.ietf.org/mailman/listinfo/eman 561 Archive: http://www.ietf.org/mail-archive/web/eman 563 Editors: 564 John Parello 565 Cisco Systems, Inc. 566 3550 Cisco Way 567 San Jose, California 95134 568 US 569 Phone: +1 408 525 2339 570 Email: jparello@cisco.com 572 Benoit Claise 573 Cisco Systems, Inc. 574 De Kleetlaan 6a b1 575 Degem 1831 576 Belgium 577 Phone: +32 2 704 5622 578 Email: bclaise@cisco.com 580 Mouli Chandramouli 581 Cisco Systems, Inc. 582 Sarjapur Outer Ring Road 583 Bangalore 560103 584 IN 585 Phone: +91 80 4429 2409 586 Email: moulchan@cisco.com" 588 DESCRIPTION 589 "This MIB is used for describing the identity and the 590 context information of Energy Objects" 591 REVISION 592 "201406110000Z" 593 DESCRIPTION 594 "Initial version, published as RFC YYYY." 596 ::= { mib-2 xxx1 } 598 -- RFC Editor, please replace xxx1 with the IANA allocation 599 -- for this MIB module and YYYY with the number of the 600 -- approved RFC 602 energyObjectContextMIBNotifs OBJECT IDENTIFIER 603 ::= { energyObjectContextMIB 0 } 605 energyObjectContextMIBObjects OBJECT IDENTIFIER 606 ::= { energyObjectContextMIB 1 } 608 energyObjectContextMIBConform OBJECT IDENTIFIER 609 ::= { energyObjectContextMIB 2 } 611 -- Textual Conventions 613 PethPsePortIndexOrZero ::= TEXTUAL-CONVENTION 614 DISPLAY-HINT "d" 615 STATUS current 616 DESCRIPTION 617 "This textual convention is an extension of the 618 pethPsePortIndex convention, which defines a greater than 619 zero value used to identify a power Ethernet PSE port. 621 This extension permits the additional value of zero. The 622 semantics of the value zero are object-specific and must, 623 therefore, be defined as part of the description of any 624 object that uses this syntax. Examples of the usage of 625 this extension are situations where none or all physical 626 entities need to be referenced." 627 SYNTAX Integer32 (0..2147483647) 629 PethPsePortGroupIndexOrZero ::= TEXTUAL-CONVENTION 630 DISPLAY-HINT "d" 631 STATUS current 632 DESCRIPTION 633 "This textual convention is an extension of the 634 pethPsePortGroupIndex convention from the Power Over 635 Ethernet MIB RFC 3621, which defines a greater than zero 636 value used to identify group containing the port to which 637 a power Ethernet PSE is connected. This extension 638 permits the additional value of zero. The semantics of 639 the value zero are object-specific and must, therefore, 640 be defined as part of the description of any object that 641 uses this syntax. Examples of the usage of this 642 extension are situations where none or all physical 643 entities need to be referenced." 644 SYNTAX Integer32 (0..2147483647) 646 LldpPortNumberOrZero ::= TEXTUAL-CONVENTION 647 DISPLAY-HINT "d" 648 STATUS current 649 DESCRIPTION 650 "This textual convention is an extension of the 651 LldpPortNumber convention specified in the LLDP MIB, 652 which defines a greater than zero value used to uniquely 653 identify each port contained in the chassis (that is 654 known to the LLDP agent) by a port number. This 655 extension permits the additional value of zero. The 656 semantics of the value zero are object-specific and must, 657 therefore, be defined as part of the description of any 658 object that uses this syntax. Examples of the usage of 659 this extension are situations where none or all physical 660 entities need to be referenced." 661 SYNTAX Integer32(0..4096) 663 EnergyObjectKeywordList ::= TEXTUAL-CONVENTION 664 STATUS current 665 DESCRIPTION 666 "A list of keywords that can be used to group Energy 667 Objects for reporting or searching. If multiple keywords 668 are present, then this string will contain all the 669 keywords separated by the ',' character. All alphanumeric 670 characters and symbols (other than a comma), such as #, 671 (, $, !, and &, are allowed. White spaces before and 672 after the commas are ignored, as well as within a keyword 673 itself. 675 For example, if an Energy Object were to be tagged with 676 the keyword values 'hospitality' and 'guest', then the 677 keyword list will be 'hospitality,guest'." 678 SYNTAX OCTET STRING (SIZE (0..2048)) 680 -- Objects 682 eoTable OBJECT-TYPE 683 SYNTAX SEQUENCE OF EoEntry 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "This table lists Energy Objects." 688 ::= { energyObjectContextMIBObjects 1 } 690 eoEntry OBJECT-TYPE 691 SYNTAX EoEntry 692 MAX-ACCESS not-accessible 693 STATUS current 694 DESCRIPTION 695 "An entry describes the attributes of an Energy Object. 696 Whenever a new Energy Object is added or an existing 697 Energy Object is deleted, a row in the eoTable is added 698 or deleted." 700 INDEX {entPhysicalIndex } 701 ::= { eoTable 1 } 703 EoEntry ::= SEQUENCE { 704 eoEthPortIndex PethPsePortIndexOrZero, 705 eoEthPortGrpIndex PethPsePortGroupIndexOrZero, 706 eoLldpPortNumber LldpPortNumberOrZero, 707 eoMgmtMacAddress MacAddress, 708 eoMgmtAddressType InetAddressType, 709 eoMgmtAddress InetAddress, 710 eoMgmtDNSName OCTET STRING, 711 eoDomainName SnmpAdminString, 712 eoRoleDescription SnmpAdminString, 713 eoKeywords EnergyObjectKeywordList, 714 eoImportance Integer32, 715 eoPowerCategory INTEGER, 716 eoAlternateKey SnmpAdminString, 717 eoPowerInterfaceType INTEGER 718 } 720 eoEthPortIndex OBJECT-TYPE 721 SYNTAX PethPsePortIndexOrZero 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "This variable uniquely identifies the power Ethernet 726 port to which a Power over Enternet device is connected . 727 If the Power over Ethernet MIB RFC 3621 is supported by 728 the SNMP agent managing the Energy Object, then the 729 Energy Object eoethPortIndex MUST contain the 730 corresponding value of pethPsePortIndex. f such a power 731 Ethernet port cannot be specified or is not known then 732 the object is zero." 733 REFERENCE "RFC 3621 " 734 DEFVAL { 0 } 736 ::= { eoEntry 1 } 738 eoEthPortGrpIndex OBJECT-TYPE 739 SYNTAX PethPsePortGroupIndexOrZero 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "This variable uniquely identifies the group containing 744 the port to which a power over Ethernet device PSE is 745 connected [RFC3621]. If the Power over Ethernet MIB RFC 746 3621 is supported by the SNMP agent managing the Energy 747 Object, then the Energy Object eoEthPortGrpIndex MUST 748 contain the corresponding value of eoethPortGrpIndex. If 749 such a power Ethernet port cannot be specified or is not 750 known then the object is zero." 751 REFERENCE "RFC 3621" 752 DEFVAL { 0 } 754 ::= { eoEntry 2 } 756 eoLldpPortNumber OBJECT-TYPE 757 SYNTAX LldpPortNumberOrZero 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "This variable uniquely identifies the port component 762 (contained in the local chassis with the LLDP agent) as 763 defined by the lldpLocPortNum in the [LLDP-MIB] and 764 [LLDP-MED-MIB]. If the [LLDP-MIB] is supported by the 765 SNMP agent managing the Energy Object, then the Energy 766 Object eoLldpPortNumber MUST contain the corresponding 767 value of lldpLocPortNum from the [LLDP-MIB]. If such a 768 port number cannot be specified or is not known then the 769 object is zero." 770 REFERENCE "LLDP MIB, IEEE 802.1AB-2005, 771 LLDP-MED-MIB, ANSI/TIA-1057" 772 DEFVAL { 0 } 774 ::= { eoEntry 3 } 776 eoMgmtMacAddress OBJECT-TYPE 777 SYNTAX MacAddress 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "This object specifies a MAC address of the Energy 782 Object." 783 ::= { eoEntry 4 } 785 eoMgmtAddressType OBJECT-TYPE 786 SYNTAX InetAddressType 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "This object specifies the eoMgmtAddress type, i.e. an 791 IPv4 address or an IPv6 address. This object MUST be 792 populated when eoMgmtAddress is populated." 793 ::= { eoEntry 5 } 795 eoMgmtAddress OBJECT-TYPE 796 SYNTAX InetAddress 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "This object specifies the management address as an IPv4 801 address or IPv6 address of Energy Object. The IP address 802 type, i.e. IPv4 or IPv6, is determined by the 803 eoMgmtAddressType value. This object can be used as an 804 alternate key to help link the Energy Object with other 805 keyed information that may be stored within the EnMS(s)." 806 ::= { eoEntry 6 } 808 eoMgmtDNSName OBJECT-TYPE 809 SYNTAX OCTET STRING 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "This object specifies a DNS name of the eoMgmtAddress. 814 This object can be used as an alternate key to help link 815 the Energy Object with other keyed information that may 816 be stored within the EnMS(s). A DNS Name must always be a 817 fully qualified name. This MIB uses the same encoding as 818 the DNS protocol." 819 REFERENCE 820 "RFC-1034 section 3.1." 821 ::= { eoEntry 7 } 823 eoDomainName OBJECT-TYPE 824 SYNTAX SnmpAdminString 825 MAX-ACCESS read-write 826 STATUS current 827 DESCRIPTION 828 "This object specifies the name of an Energy Management 829 Domain for the Energy Object. By default, this object 830 should be an empty string. The value of eoDomainName must 831 remain constant at least from one re-initialization of 832 the entity local management system to the next re- 833 initialization." 834 ::= { eoEntry 8 } 836 eoRoleDescription OBJECT-TYPE 837 SYNTAX SnmpAdminString 838 MAX-ACCESS read-write 839 STATUS current 840 DESCRIPTION 841 "This object specifies an administratively assigned name 842 to indicate the purpose an Energy Object serves in the 843 network. 845 For example, we can have a phone deployed to a lobby with 846 eoRoleDescription as 'Lobby phone'. 848 This object specifies that the value is the zero-length 849 string value if no role description is configured. 850 The value of eoRoleDescription must remain constant at 851 least from one re-initialization of the entity local 852 management system to the next re-initialization. " 853 ::= { eoEntry 9 } 855 eoKeywords OBJECT-TYPE 856 SYNTAX EnergyObjectKeywordList 857 MAX-ACCESS read-write 858 STATUS current 859 DESCRIPTION 860 "This object specifies a list of keywords that can be 861 used to group Energy Objects for reporting or searching. 862 The value is the zero-length string if no keywords have 863 been configured. If multiple keywords are present, then 864 this string will contain all the keywords separated by 865 the ',' character. For example, if an Energy Object were 866 to be tagged with the keyword values 'hospitality' and 867 'guest', then the keyword list will be 868 'hospitality,guest'. 870 If write access is implemented and a value is written 871 into the instance, the agent must retain the supplied 872 value in the eoKeywords instance associated with 873 the same physical entity for as long as that entity 874 remains instantiated. This includes instantiations 875 across all re-initializations/reboots of the local 876 management agent. " 877 ::= { eoEntry 10 } 879 eoImportance OBJECT-TYPE 880 SYNTAX Integer32 (1..100) 881 MAX-ACCESS read-write 882 STATUS current 883 DESCRIPTION 884 "This object specifies a ranking of how important the 885 Energy Object is (on a scale of 1 to 100) compared with 886 other Energy Objects in the same Energy Management 887 Domain. The ranking should provide a business or 888 operational context for the Energy Object as compared to 889 other similar Energy Objects. This ranking could be used 890 as input for policy-based network management. 892 Although network managers must establish their own 893 ranking, the following is a broad recommendation: 895 90 to 100 Emergency response 896 80 to 90 Executive or business critical 897 70 to 79 General or Average 898 60 to 69 Staff or support 899 40 to 59 Public or guest 900 1 to 39 Decorative or hospitality 902 The value of eoImportance must remain constant at least 903 from one re-initialization of the Energy Object local 904 management system to the next re-initialization. " 905 DEFVAL { 1 } 906 ::= { eoEntry 11 } 908 eoPowerCategory OBJECT-TYPE 909 SYNTAX INTEGER { 910 consumer(0), 911 producer(1), 912 meter(2), 913 distributor(3), 914 store(4) 915 } 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 "This object describes the Energy Object category, which 920 indicates the expected behavior or physical property of 921 the Energy Object, based on its design. An Energy Object 922 can be a consumer(0), producer(1), meter(2), 923 distributor(3) or store(4). 925 In some cases, a meter is required to measure the power 926 consumption. In such a case, this meter Energy Object 927 category is meter(2). If a device is distributing 928 electric Energy, the category of the Energy Object is 929 distributor (3). If a device is storing electric Energy, 930 the category of the device can be store (4). " 931 ::= { eoEntry 12 } 933 eoAlternateKey OBJECT-TYPE 934 SYNTAX SnmpAdminString 935 MAX-ACCESS read-write 936 STATUS current 937 DESCRIPTION 938 "The eoAlternateKey object specifies an alternate key 939 string that can be used to identify the Energy Object. 940 Since Energy Management Systems (EnMS) and Network 941 Management Systems (NMS) may need to correlate objects 942 across management systems, this alternate key is provided 943 to provide such a link. This optional value is intended 944 as a foreign key or alternate identifier for a 945 manufacturer or EnMS/NMS to use to correlate the unique 946 Energy Object Id in other systems or namespaces. If an 947 alternate key is not available or is not applicable then 948 the value is the zero-length string. 949 The value of eoAlternateKey must remain constant at 950 least from one re-initialization of the entity local 951 management system to the next re-initialization. " 952 ::= { eoEntry 13 } 954 eoPowerInterfaceType OBJECT-TYPE 955 SYNTAX INTEGER { 956 inlet(0), 957 outlet(1), 958 both(2) 959 } 960 MAX-ACCESS read-only 961 STATUS current 962 DESCRIPTION 963 "This object describes the Power Interface for an Energy 964 Object. A Power Interface is an interface at which a 965 Energy Object is connected to a power transmission 966 medium, at which it can in turn receive power, provide 967 power, or both. A Power Interface type can be an inlet(0) 968 or outlet(1) or both(2), respectively." 969 ::= { eoEntry 14 } 971 eoRelationTable OBJECT-TYPE 972 SYNTAX SEQUENCE OF EoRelationEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "This table describes the relationships between Energy 977 Objects." 978 ::= { energyObjectContextMIBObjects 2 } 980 eoRelationEntry OBJECT-TYPE 981 SYNTAX EoRelationEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "An entry in this table specifies the Energy relationship 986 between Energy objects. Energy relations between two 987 Energy objects are defined in the EMAN-FMWK." 988 REFERENCE 989 "EMAN-FMWK, Energy Management Framework, RFC abcs, 990 Jan 2014" 991 INDEX { entPhysicalIndex, eoRelationIndex } 992 ::= { eoRelationTable 1 } 994 EoRelationEntry ::= SEQUENCE { 995 eoRelationIndex Integer32, 996 eoRelationID UUIDorZero, 997 eoRelationship IANAEnergyRelationship, 998 eoRelationStatus RowStatus, 999 eoRelationStorageType StorageType 1000 } 1002 eoRelationIndex OBJECT-TYPE 1003 SYNTAX Integer32 (0..2147483647) 1004 MAX-ACCESS not-accessible 1005 STATUS current 1006 DESCRIPTION 1007 "This object is an arbitrary index to identify the Energy 1008 Object related to another Energy Object" 1009 ::= { eoRelationEntry 1 } 1011 eoRelationID OBJECT-TYPE 1012 SYNTAX UUIDorZero 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "This object specifies the Universally Unique Identifier 1017 (UUID) of the peer (other) Energy Object. The UUID must 1018 comply the specifications of UUID in UUID-TC-MIB. 1020 If UUID of the energy object is unknown or non-existent, 1021 the eoRelationID will be set to a zero-length string 1022 instead. It is preferable that the value of 1023 entPhysicalUUID from ENTITY-MIB is used for values for 1024 this object." 1026 REFERENCE 1027 "RFC 6933, Entity MIB - version 4, May 2013 " 1028 ::= { eoRelationEntry 2 } 1030 eoRelationship OBJECT-TYPE 1031 SYNTAX IANAEnergyRelationship 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "This object describes the relations between Energy 1036 objects. For each Energy object, the relations between 1037 the other Energy objects are specified using the bitmap." 1038 ::= { eoRelationEntry 3 } 1040 eoRelationStatus OBJECT-TYPE 1041 SYNTAX RowStatus 1042 MAX-ACCESS read-create 1043 STATUS current 1044 DESCRIPTION 1045 "The status controls and reflects the creation and 1046 activation status of a row in this table to specify energy 1047 relationship between Energy objects. 1049 An entry status may not be active(1) unless all objects in 1050 the entry have the appropriate values. 1051 No attempt to modify a row columnar object instance value 1052 in the eoRelationTable should be issued while the value of 1053 eoRelationStatus is active(1). The data can be destroyed by 1054 setting up the eoRelationStatus to destroy(2)." 1056 ::= { eoRelationEntry 4 } 1058 eoRelationStorageType OBJECT-TYPE 1059 SYNTAX StorageType 1060 MAX-ACCESS read-create 1061 STATUS current 1062 DESCRIPTION 1063 "This variable indicates the storage type for this row." 1064 DEFVAL { nonVolatile } 1065 ::= {eoRelationEntry 5 } 1067 -- Conformance 1069 energyObjectContextMIBCompliances OBJECT IDENTIFIER 1070 ::= { energyObjectContextMIBConform 1 } 1072 energyObjectContextMIBGroups OBJECT IDENTIFIER 1073 ::= { energyObjectContextMIBConform 2 } 1075 energyObjectContextMIBFullCompliance MODULE-COMPLIANCE 1076 STATUS current 1077 DESCRIPTION 1078 "When this MIB is implemented with support for 1079 read-write, then such an implementation can 1080 claim full compliance. Such devices can then 1081 be both monitored and configured with this MIB. 1082 Module Compliance of ENTITY-MIB with respect to 1083 entity4CRCompliance MUST be supported." 1085 MODULE -- this module 1086 MANDATORY-GROUPS { 1087 energyObjectContextMIBTableGroup, 1088 energyObjectRelationTableGroup 1089 } 1091 GROUP energyObjectOptionalMIBTableGroup 1092 DESCRIPTION 1093 "A compliant implementation does not have to 1094 implement. " 1095 ::= { energyObjectContextMIBCompliances 1 } 1097 energyObjectContextMIBReadOnlyCompliance MODULE-COMPLIANCE 1098 STATUS current 1099 DESCRIPTION 1100 "When this MIB is implemented without support for 1101 read-write (i.e. in read-only mode), then such an 1102 implementation can claim read-only compliance. 1103 Such a device can then be monitored but cannot be 1104 Configured with this MIB. 1105 Module Compliance of ENTITY-MIB with respect to 1106 entity4CRCompliance MUST be supported." 1107 MODULE -- this module 1109 MANDATORY-GROUPS { 1110 energyObjectContextMIBTableGroup, 1111 energyObjectRelationTableGroup 1112 } 1114 GROUP energyObjectOptionalMIBTableGroup 1115 DESCRIPTION 1116 "A compliant implementation does not have to implement 1117 the managed objects in this GROUP. " 1119 ::= { energyObjectContextMIBCompliances 2 } 1121 -- Units of Conformance 1123 energyObjectContextMIBTableGroup OBJECT-GROUP 1124 OBJECTS { 1125 eoDomainName, 1126 eoRoleDescription, 1127 eoAlternateKey, 1128 eoKeywords, 1129 eoImportance, 1130 eoPowerCategory, 1131 eoPowerInterfaceType 1132 } 1133 STATUS current 1134 DESCRIPTION 1135 "This group contains the collection of all the objects 1136 related to the EnergyObject. " 1138 ::= { energyObjectContextMIBGroups 1 } 1140 energyObjectOptionalMIBTableGroup OBJECT-GROUP 1141 OBJECTS { 1142 eoEthPortIndex, 1143 eoEthPortGrpIndex, 1144 eoLldpPortNumber, 1145 eoMgmtMacAddress, 1146 eoMgmtAddressType, 1147 eoMgmtAddress, 1148 eoMgmtDNSName 1149 } 1150 STATUS current 1151 DESCRIPTION 1152 "This group contains the collection of all the objects 1153 related to the Energy Object." 1154 ::= { energyObjectContextMIBGroups 2 } 1156 energyObjectRelationTableGroup OBJECT-GROUP 1157 OBJECTS { 1159 eoRelationID, 1160 eoRelationship, 1161 eoRelationStatus, 1162 eoRelationStorageType 1163 } 1164 STATUS current 1165 DESCRIPTION 1166 "This group contains the collection of all objects 1167 specifying the relationship between Energy Objects." 1168 ::= { energyObjectContextMIBGroups 3 } 1170 END 1171 IANA-ENERGY-RELATION-MIB DEFINITIONS ::= BEGIN 1172 IMPORTS 1173 MODULE-IDENTITY, mib-2 1174 FROM SNMPv2-SMI 1175 TEXTUAL-CONVENTION 1176 FROM SNMPv2-TC; 1178 ianaEnergyRelationMIB MODULE-IDENTITY 1179 LAST-UPDATED "201406110000Z" -- June 11, 2014 1180 ORGANIZATION "IANA" 1181 CONTACT-INFO " 1182 Internet Assigned Numbers Authority 1183 Postal: ICANN 1184 12025 Waterfront Drive Suite 300 1185 Los Angeles, CA 90094 1186 Tel: +1-310-301 5800 1187 EMail: iana&iana.org" 1189 DESCRIPTION 1190 "This MIB module defines a TEXTUAL-CONVENTION that 1191 describes the relationships between Energy Objects. 1193 Copyright (C) The IETF Trust (2013). 1195 The initial version of this MIB module was published in 1196 RFC YYYY; for full legal notices see the RFC itself. 1197 Supplementary information may be available at 1198 http://www.ietf.org/copyrights/ianamib.html" 1200 REVISION "201406110000Z" -- June 11, 2014 1201 DESCRIPTION "Initial version of this MIB as published in 1202 RFC YYYY." 1203 ::= { mib-2 xxx2 } 1205 -- RFC Editor, please replace xxx2 with the IANA allocation 1206 -- for this MIB module and YYYY with the number of the 1207 -- approved RFC 1209 -- Textual Conventions 1211 IANAEnergyRelationship ::= TEXTUAL-CONVENTION 1212 STATUS current 1213 DESCRIPTION 1214 "An enumerated value specifying the type of 1215 relationship between an Energy Object A, on 1216 which the relationship is specified, with the 1217 Energy Object B, identified by the UUID. 1219 The enumeration 'poweredBy' is applicable if the 1220 Energy Object A is poweredBy Energy Object B. 1222 The enumeration 'powering' is applicable if the 1223 Energy Object A is powering Energy Object B. 1225 The enumeration 'meteredBy' is applicable if the 1226 Energy Object A is meteredBy Energy Object B. 1228 The enumeration 'metering' is applicable if the 1229 Energy Object A is metering Energy Object B. 1231 The enumeration 'aggregatedBy' is applicable if the 1232 Energy Object A is aggregatedBy Energy Object B. 1234 The enumeration 'aggregating' is applicable if the 1235 Energy Object A is aggregating Energy Object B." 1237 SYNTAX INTEGER { 1238 poweredBy(1), -- power relationship 1239 powering(2), 1240 meteredBy(3), -- meter relationship 1241 metering(4), 1242 aggregatedBy(5), -- aggregation relationship 1243 aggregating(6) 1244 } 1246 END 1248 6. Implementation Status 1250 [Note to RFC Editor: Please remove this section and the 1251 reference to [RFC6982] before publication.] 1253 This section records the status of known implementations of the 1254 EMAN-Monitoring MIB at the time of posting of this Internet- 1255 Draft, and is based on a proposal described in [RFC6982]. 1257 The description of implementations in this section is intended 1258 to assist the IETF in its decision processes in progressing 1259 drafts to RFCs. 1261 6.1 SNMP Research 1263 Organization: SNMP Research, Inc. 1265 Maturity: Prototype based upon early drafts of the MIBs. 1266 We anticipate updating it to more recent 1267 documents as development schedules allow. 1269 Coverage: Code was generated to implement all MIB objects 1270 in ENTITY-MIB (Version 4), 1271 ENERGY-OBJECT-CONTEXT-MIB, 1272 ENERGY-OBJECT-MIB, 1273 POWER-CHARACTERISTICS-MIB, 1274 and BATTERY-MIB. 1276 Implementation experience: The documents are implementable. 1278 Comments: Technical comments about the 1279 ENERGY-OBJECT-CONTEXT-MIB, 1280 ENERGY-OBJECT-MIB, and 1281 BATTERY-MIB 1282 were submitted to the EMAN Working Group 1283 E-mail list. 1285 Licensing: Proprietary, royalty licensing 1287 Contact: Alan Luchuk, luchuk at snmp.com 1289 URL: http://www.snmp.com/ 1291 6.2 Python 1293 Priyanka Rao has mentioned on the mailing list 1294 (http://www.ietf.org/mail- 1295 archive/web/eman/current/msg02063.html) that she has 1296 a python implementation. 1298 7. Security Considerations 1300 There are a number of management objects defined in this MIB 1301 module with a MAX-ACCESS clause of read-write and/or read- 1302 create. Such objects may be considered sensitive or vulnerable 1303 in some network environments. The support for SET operations in 1304 a non-secure environment without proper protection can have a 1305 negative effect on network operations. These are the tables and 1306 objects and their sensitivity/vulnerability: 1308 . Unauthorized changes to the eoDomainName, entPhysicalName, 1309 eoRoleDescription, eoKeywords, and/or eoImportance MAY 1310 disrupt power and energy collection, and therefore any 1311 predefined policies defined in the network. 1313 SNMP versions prior to SNMPv3 did not include adequate security. 1314 Even if the network itself is secure (for example by using 1315 IPsec), there is no control as to who on the secure network is 1316 allowed to access and GET/SET (read/change/create/delete) the 1317 objects in this MIB module. 1319 Implementations SHOULD provide the security features described 1320 by the SNMPv3 framework (see [RFC3410]), and implementations 1321 claiming compliance to the SNMPv3 standard MUST include full 1322 support for authentication and privacy via the User-based 1323 Security Model (USM) [RFC3414] with the AES cipher algorithm 1324 [RFC3826]. Implementations MAY also provide support for the 1325 Transport Security Model (TSM) [RFC5591] in combination with a 1326 secure transport such as SSH [RFC5592] or TLS/DTLS [RFC6353]. 1328 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1329 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1330 enable cryptographic security. It is then a customer/operator 1331 responsibility to ensure that the SNMP entity giving access to 1332 an instance of this MIB module is properly configured to give 1333 access to the objects only to those principals (users) that have 1334 legitimate rights to indeed GET or SET (change/create/delete) 1335 them. 1337 8. IANA Considerations 1339 The MIB modules in this document use the following IANA-assigned 1340 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1342 Descriptor OBJECT IDENTIFIER value 1344 ---------- ----------------------- 1346 energyObjectContextMIB { mib-2 xxx1 } 1348 Editor's Note (to be removed prior to publication): IANA is 1349 requested to assign a value for "xxx1" under the 'mib-2' subtree 1350 and to record the assignment in the SMI Numbers registry. When 1351 the assignment has been made, the RFC Editor is asked to replace 1352 "xxx1" (here and in the MIB module) with the assigned value and 1353 to remove this note. 1355 This document defines the first version of the IANA-maintained 1356 IANA-ENERGY-RELATION-MIB module, which allows new definitions of 1357 relationships between Energy Objects. 1359 A Specification Required as defined in RFC 5226 [RFC5226], is 1360 REQUIRED for each modification of the energy relationships. 1362 The MIB module in this document uses the following IANA-assigned 1363 OBJECT IDENTIFIER values recorded in the SMI Numbers registry. 1365 Descriptor OBJECT IDENTIFIER value 1367 ---------- ----------------------- 1369 ianaEnergyRelationMIB { mib-2 xxx2 } 1371 Editor's Note (to be removed prior to publication): IANA is 1372 requested to assign a value for "xxx2" under the 'mib-2' subtree 1373 and to record the assignment in the SMI Numbers registry. When 1374 the assignment has been made, the RFC Editor is asked to replace 1375 "xxx2" (here and in the MIB module) with the assigned value and 1376 to remove this note. 1378 9. Acknowledgement 1380 We would like to thank Juergen Quittek and Juergen Schoenwalder 1381 for their suggestions on the new design of eoRelationTable which 1382 was a proposed solution for the open issue on the representation 1383 of Energy Object as a UUIDlist. 1385 Many thanks to Juergen Quittek for many comments on the wording, 1386 text and design of the MIB thus resulting in an improved draft. 1388 Many thanks to Alan Luchuk for the review of the MIB and his 1389 comments. 1391 In addition the authors thank Bill Mielke for his multiple 1392 reviews, Brad Schoening and Juergen Schoenwaelder for their 1393 suggestions and Michael Brown for dramatically improving this 1394 draft. 1396 And finally thanks the EMAN WG chairs: Nevil Brownlee and Tom 1397 Nadeau. 1399 10. References 1401 10.1. Normative References 1403 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 1404 Requirement Levels, BCP 14, RFC 2119, March 1997. 1406 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1407 Schoenwaelder, Ed., "Structure of Management 1408 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1409 1999. 1411 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1412 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1413 STD 58, RFC 2579, April 1999. 1415 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1416 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1417 April 1999. 1419 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 1420 RFC3621, December 2003. 1422 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 1423 Unique IDentifier (UUID) URN Namespace ", RFC 4122, 1424 July 2005. 1426 [RFC6933] Bierman, A. Romascanu,D. Quittek, J. and M. 1427 Chandramouli, "Entity MIB (Version 4)", RFC 6933, May 1428 2013. 1430 [LLDP-MIB] IEEE 802.1AB-2005, "Management Information Base 1431 module for LLDP configuration, statistics, local system 1432 data and remote systems data components", May 2005. 1434 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 1435 Base extension module for TIA-TR41.4 media endpoint 1436 discovery information", July 2005. 1438 [EMAN-MON-MIB] M. Chandramouli, Schoening, B., Quittek, J., 1439 Dietz, T., and B. Claise "Power and Energy Monitoring 1440 MIB", draft-ietf-eman-energy-monitoring-mib-10, June 1441 2014. 1443 10.2. Informative References 1445 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1446 "Introduction and Applicability Statements for Internet 1447 Standard Management Framework", RFC 3410, December 1448 2002. 1450 [RFC3433] Bierman, A., Romascanu, D., and K.C. Norseth, "Entity 1451 Sensor Management Information Base", RFC 3433, December 1452 2002. 1454 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 1455 "Guidelines for Writing an IANA Considerations Section 1456 in RFCs ", BCP 26, RFC 5226, May 2008. 1458 [RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M. 1459 Chandramouli, "Requirements for Energy Management", RFC 1460 6988, September 2013. 1462 [EMAN-FMWK] Claise, B., Parello, J., Schoening, B., and J. 1463 Quittek, "Energy Management Framework", draft-ietf- 1464 eman-framework-19, work in progress, April, 2014. 1466 [EMAN-AS] Schoening, B., Chandramouli, M, and B. Nordman, 1467 "Energy Management (EMAN) Applicability Statement", 1468 draft-ietf-eman-applicability-statement-06.txt, work in 1469 progress, June 2014. 1471 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of 1472 Running Code: The Implementation Status Section", RFC 1473 6982, July 2013. 1475 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 1476 Model (USM) for version 3 of the Simple Network 1477 ManagementProtocol (SNMPv3)", STD 62, RFC 3414, 1478 December 2002. 1480 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 1481 Advanced Encryption Standard (AES) Cipher Algorithm in 1482 the SNMP User-based Security Model", RFC 3826, June 1483 2004. 1485 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security 1486 Model for the Simple Network Management Protocol 1487 (SNMP)", RFC 5591, June 2009. 1489 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1490 Shell Transport Model for the Simple Network Management 1491 Protocol (SNMP)", RFC 5592, June 2009. 1493 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) 1494 Transport Model for the Simple Network Management 1495 Protocol (SNMP)", RFC 6353, July 2011. 1497 Authors' Addresses 1499 Benoit Claise 1500 Cisco Systems, Inc. 1501 De Kleetlaan 6a b1 1502 Diegem 1813 1503 BE 1505 Phone: +32 2 704 5622 1506 Email: bclaise@cisco.com 1508 John Parello 1509 Cisco Systems, Inc. 1510 3550 Cisco Way 1511 San Jose, California 95134 1512 US 1514 Phone: +1 408 525 2339 1515 Email: jparello@cisco.com 1517 Mouli Chandramouli 1518 Cisco Systems, Inc. 1519 Sarjapur Outer Ring Road 1520 Bangalore 560103 1521 IN 1523 Phone: +91 80 4429 2409 1524 Email: moulchan@cisco.com