idnits 2.17.1 draft-ietf-eman-energy-aware-mib-14.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 246 has weird spacing: '...xOrZero eoEt...' == Line 504 has weird spacing: '... if the power...' == Line 966 has weird spacing: '... of the entit...' -- The document date (February 10, 2014) is 3721 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-08 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-15 == Outdated reference: A later version (-11) exists of draft-ietf-eman-applicability-statement-04 -- Obsolete informational reference (is this intentional?): RFC 6982 (Obsoleted by RFC 7942) Summary: 0 errors (**), 0 flaws (~~), 8 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: August 10, 2014 Cisco Systems, Inc. 6 February 10, 2014 8 Energy Object Context MIB 9 draft-ietf-eman-energy-aware-mib-14 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 August 10, 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.......... 6 71 5.1 Energy Object Identification..........................8 72 5.2 Energy Object Context................................10 73 5.3 Links to Other Identifiers...........................10 74 5.4 Energy Object Relationships..........................11 75 5.5 Energy Object Identity Persistence...................12 76 5. MIB Definitions......................................... 13 77 6. Implementation Status................................... 29 78 7. Security Considerations................................. 30 79 8. IANA Considerations..................................... 31 80 9. Acknowledgement......................................... 32 81 10. References............................................. 32 82 10.1. Normative References...............................32 83 10.2. Informative References.............................33 85 1. Introduction 87 The EMAN standards provide a specification for Energy 88 Management. This document defines a subset of a Management 89 Information Base (MIB) for use with network management protocols 90 for Energy monitoring of network devices and devices attached to 91 the network and possibly extending to devices in the industrial 92 automation setting with a network interface. 94 The focus of the MIB module specified in this document is on the 95 identification of Energy Objects and reporting the context and 96 relationships of Energy Objects as defined in [EMAN-FMWK]. The 97 module addresses Energy Object identification, Energy Object 98 context, and Energy Object relationships. 100 1.1. Energy Management Document Overview 102 This document specifies the Energy Object Context (ENERGY- 103 OBJECT-CONTEXT-MIB) and IANA Energy Relationship (IANA-ENERGY- 104 RELATION-MIB) modules. The Energy Object Context MIB module 105 specifies MIB objects for identification of Energy Objects, and 106 reporting context and relationship of an Energy Object. The IANA 107 Energy Relationship MIB module specifies the first version of 108 the IANA-maintained definitions of relationships between Energy 109 Objects. 111 Firstly, to illustrate the importance of energy monitoring in 112 networks and secondly to list some of the important areas to be 113 addressed by the Energy Management Framework, several use cases 114 and network scenarios are presented in the EMAN applicability 115 statement document [EMAN-AS]. In addition, for each scenario, 116 the target devices for energy management, and how those devices 117 powered and metered are also presented. To address the network 118 scenarios, requirements for power and energy monitoring for 119 networking devices are specified in [RFC6988]. Based on the 120 requirements [RFC6988], the [EMAN-FMWK] presents a solution 121 approach. 123 Accordingly, the scope of the MIB modules in this document is in 124 accordance to the requirements specified in [RFC6988] and the 125 concepts from [EMAN-FMWK]. 127 This document is based on the Energy Management Framework [EMAN- 128 FMWK] and meets the requirements on identification of Energy 129 Objects and their context and relationships as specified in the 130 Energy Management requirements [RFC6988]. 132 A second MIB module meeting the EMAN requirements [RFC6988] the 133 Power and Energy Monitoring MIB [EMAN-MON-MIB], monitors the 134 Energy Objects for Power States, for the Power and Energy 135 consumption. Power State monitoring includes: retrieving Power 136 States, Power State properties, current Power State, Power State 137 transitions, and Power State statistics. In addition, this MIB 138 module provides the Power Characteristics properties of the 139 Power and Energy, along with optional characteristics. 141 The applicability statement document [EMAN-AS] provides the list 142 of use cases, and describes the common aspects of between 143 existing Energy standards and the EMAN standard, and shows how 144 the EMAN framework relates to other frameworks. 146 2. The Internet-Standard Management Framework 148 For a detailed overview of the documents that describe the 149 current Internet-Standard Management Framework, please refer to 150 section 7 of RFC 3410 [RFC3410]. 152 Managed objects are accessed via a virtual information store, 153 termed the Management Information Base or MIB. MIB objects are 154 generally accessed through the Simple Network Management 155 Protocol (SNMP). Objects in the MIB are defined using the 156 mechanisms defined in the Structure of Management Information 157 (SMI). This memo specifies MIB modules that are compliant with 158 SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 159 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 161 3. Terminology 163 Please refer to [EMAN-FMWK] for the definitions of the following 164 terminology used in this draft: 166 Energy Management 168 Energy Management System (EnMS) 170 Energy Monitoring 172 Energy Control 174 electrical equipment 176 non-electrical equipment (mechanical equipment) 178 device 180 component 182 power inlet 184 power outlet 186 energy 188 power 190 demand 192 provide energy 194 receive energy 196 meter (energy meter) 198 battery 200 Power Interface 202 Nameplate Power 204 Power Attributes 206 Power Quality 208 Power State 210 Power State Set 212 4. Architecture Concepts Applied to the MIB Module 214 This section describes the basic concepts specified in the 215 Energy Management Architecture [EMAN-FMWK], with specific 216 information related to the MIB modules specified in this 217 document. 219 The Energy Object Context (ENERGY-OBJECT-CONTEXT-MIB) MIB module 220 in this document specifies MIB objects for identification of 221 Energy Objects, and reporting context and relationship of an 222 Energy Object. The managed objects are contained in two tables 223 eoTable and eoRelationTable. 225 The first table eoTable focuses on the link to the other MIB 226 modules, and secondly on identification, context of the Energy 227 Object. The second table eoRelationTable specifies the 228 relationships between Energy Objects. This is a simplified 229 representation of relationship between Energy Objects. 231 A "smidump-style" tree presentation of the MIB modules contained 232 in the draft is presented. The meaning of the three symbols in 233 is a compressed representation of the object's MAX-ACCESS clause 234 which may have the following values: 236 "not-accessible"->"---" 237 "accessible-for-notify"->"--n" 238 "read-only"->"r-n" 239 "read-write"->"rwn" 241 +- eoTable(1) 242 | 243 +- eoEntry(1) [entPhysicalIndex] 244 | 245 +-- r-n PethPsePortIndexOrZero eoEthPortIndex(1) 246 +-- r-n PethPsePortGroupIndexOrZero eoEthPortGrpIndex(2) 247 +-- r-n LldpPortNumberOrZero eoLldpPortNumber(3) 248 +-- rwn MacAddress eoMgmtMacAddress(4) 249 +-- r-n InetAddressType eoMgmtAddressType(5) 250 +-- r-n InetAddress eoMgmtAddress(6) 251 +-- r-n OCTET STRING eoMgmtDNSName(7) 252 +-- rwn SnmpAdminString eoDomainName(8) 253 +-- rwn SnmpAdminString eoRoleDescription(9) 254 +-- rwn EnergyObjectKeywordList eoKeywords(10) 255 +-- rwn Integer32 eoImportance(11) 256 +-- r-n INTEGER eoPowerCategory(12) 257 +-- rwn SnmpAdminString eoAlternateKey(13) 258 +-- r-n INTEGER eoPowerInterfaceType(14) 260 +- eoRelationTable(2) 261 | 262 +- eoRelationEntry(1) [entPhysicalIndex, eoRelationIndex] 263 | 264 +-- --n Integer32 eoRelationIndex(1) 265 +-- rwn UUIDorZero eoRelationID(2) 266 +-- rwn IANAEnergyRelationship eoRelationship(3) 267 +-- rwn RowStatus eoRelationStatus(4) 269 The following UML diagram illustrates the relationship of the 270 MIB objects in the eoTable, eoRelationTable and ENTITY-MIB. The 271 MIB objects describe the identity, context and relationship of 272 an Energy Object. The UML diagram furthermore contains objects 273 from the ENTITY-MIB [RFC6933]. 275 +--------------------------+ 276 | EO Context Information | 277 | ------------------------ | 278 | eoRoleDescription | 279 | eoKeywords | 280 | eoImportance | 281 | eoPowerCategory | 282 | eoPowerInterfaceType | 283 | eoDomainName | 284 +--------------------------+ 285 ^ 286 | 287 | 288 +-----------------------------+ 289 |--- | EO Identification | 290 | | ---------------------------- | 291 | | entPhysicalIndex (*) | 292 | | entPhysicalName (*) | 293 | | entPhysicalUUID (*) | 294 | | entPhysicalClass (*) | 295 | -------------------------------- 296 | 297 | +------------------------------+ 298 |---> | Link to other identifiers | 299 | |------------------------------| 300 | | eoEthPortIndex (**) | 301 | | eoEthPortGrpIndex (**) | 302 | | eoLldpPortNumber (***) | 303 | | | 304 | | eoMgmtMacAddress (optional) | 305 | | eoMgmtAddressType (optional) | 306 | | eoMgmtAddress (optional) | 307 | | eoMgmtDNSName (optional) | 308 | | eoAlternateKey | 309 | +------------------------------+ 310 | 311 | +------------------------------+ 312 |---> | EO Relationship | 313 | ---------------------------- | 314 | eoRelationIndex | 315 | eoRelationID | 316 | eoRelationship | 317 | eoRelationStatus | 318 +------------------------------+ 320 (*) Compliance with entity4CRCompliance ENTITY MIB[RFC6933] 321 (**) Link with the Power over Ethernet MIB [RFC3621] 322 (***) Link with LLDP MIBs [LLDP-MIB] [LLDP-MED-MIB] 324 Figure 1: MIB Objects Grouping 326 As displayed in figure 1, the MIB objects can be classified in 327 different logical grouping of MIB objects. 329 1) The Energy Object Identification. See Section 5.1 "Energy 330 Object Identification". Devices and their sub-components are 331 characterized by the power-related attributes of a physical 332 entity present in the ENTITY MIB [RFC6933]. 333 2) The Context Information. See Section 5.2 "Energy Object 334 Context" 335 3) The links to other MIB modules. See Section 5.3 "Links to 336 other Identifiers" 337 4) The Energy Object Relationships specific information. See 338 Section 5.4 339 5) The Energy Object Identity Persistence. See Section 5.5 340 "Energy Object Identity Persistence" 342 5.1 Energy Object Identification 344 Refer to the "Energy Object Information" section in [EMAN-FMWK] 345 for background information about Energy Objects. 347 Every Energy Object MUST implement the unique index, 348 entPhysicalIndex, entPhysicalName, entPhysicalClass, and 349 entPhysicalUUID from the ENTITY MIB [RFC6933]. Module Compliance 350 with respect to entity4CRCompliance of ENTITY-MIB MUST be 351 supported which require a limited number of objects supported 352 (entPhysicalIndex, entPhysicalName, entPhysicalClass, and 353 entPhysicalUUID). entPhysicalIndex is used as index for the 354 Energy Object in the ENERGY-OBJECT-CONTEXT-MIB module. 355 Every Energy Object MUST have a printable name assigned to it. 356 Energy Objects MUST implement the entPhysicalName object 357 specified in the ENTITY-MIB [RFC6933], which must contain the 358 Energy Object name. 360 For the ENERGY-OBJECT-CONTEXT-MIB compliance, every Energy 361 Object instance MUST implement the entPhysicalUUID from the 362 ENTITY MIB [RFC6933]. 364 As displayed in [RFC4122], the following is an example of the 365 string representation of a UUID as a URN: urn:uuid:f81d4fae- 366 7dec-11d0-a765-00a0c91e6bf6. 368 For example, to understand the relationship between Energy 369 Object Components and Energy Objects, the ENTITY-MIB physical 370 containment tree [RFC6933] MUST be implemented. 372 A second example deals with one of the ENTITY-MIB extensions: if 373 the Energy Object temperature is required, the managed objects 374 from the ENTITY-SENSOR-MIB [RFC3433] should be supported. 376 Each Energy Object MUST belong to a single Energy Management 377 Domain or in other words, an Energy Object cannot belong to more 378 than one Energy Management Domain. Refer to the "Energy 379 Management Domain" section in [EMAN-FMWK] for background 380 information. The eoDomainName, which is an element of the 381 eoTable, is a read-write MIB object. The Energy Management 382 Domain should map 1-1 with a metered or sub-metered portion of 383 the network. The Energy Management Domain MUST be configured on 384 the Energy Object. The Energy Object MAY inherit the some of the 385 domain parameters (possibly domain name, some of the context 386 information such as role or keywords, importance) from the 387 Energy Object or the Energy Management Domain MAY be configured 388 directly in an Energy Object. 390 When an Energy Object acts as a Power Aggregator, the Energy 391 Objects for which Power should be aggregated MUST be members of 392 the same Energy Management Domain, specified by the eoDomainName 393 MIB Object. 395 5.2 Energy Object Context 397 Refer to the "Energy Object Context" section in [EMAN-FMWK] for 398 background information. 400 An Energy Object must provide a value for eoImportance in the 401 range of 1...100 to help differentiate the use or relative value 402 of the device. The importance range is from 1 (least important) 403 to 100 (most important). The default importance value is 1. 405 An Energy Object can provide a set of eoKeywords. These keywords 406 are a list of tags that can be used for grouping and summary 407 reporting within or between Energy Management Domains. 409 An Energy Object can have Power Interfaces and those interfaces 410 can be classified as Power Inlet, Power Outlet or both. 412 An Energy Object can be classified based on the physical 413 properties of the Energy Object. That Energy Object can be 414 classified as consuming power or supplying power to other 415 devices or that Energy Object can perform both of those 416 functions and finally, an Energy Object can be a passive meter. 418 Additionally, an Energy Object can provide an eoRoleDescription 419 string that indicates the purpose the Energy Object serves in 420 the network. 422 5.3 Links to Other Identifiers 424 While the entPhysicalIndex is the primary index for all MIB 425 objects in the ENERGY-OBJECT-CONTEXT-MIB module, the Energy 426 Management Systems (EnMS) must be able to make the link with the 427 identifier(s) in other supported MIB modules. 429 If the Energy Object is a Power over Ethernet (PoE) port, and if 430 the Power over Ethernet MIB [RFC3621] is supported by the SNMP 431 agent managing the Energy Object, then the Energy Object 432 eoethPortIndex and eoethPortGrpIndex MUST contain the 433 corresponding values of pethPsePortIndex and 434 pethPsePortGroupIndex [RFC3621]. 436 If the LLDP-MED MIB [LLDP-MIB] is supported by the Energy Object 437 SNMP agent, then the Energy Object eoLldpPortNumber MUST contain 438 the corresponding lldpLocPortNum from the LLDP MIB. 440 The intent behind the links to the other MIB module 441 identifier(s) is to correlate the instances in the different MIB 442 modules. This will allow the ENERGY-OBJECT-CONTEXT-MIB module to 443 reference other MIB modules in cases where the Power over 444 Ethernet and the LLDP MIB modules are supported by the SNMP 445 agent. Some use cases may not implement any of these two MIB 446 modules for the Energy Objects. However, in situation where any 447 of these two MIB modules are implemented, the EnMS must be able 448 to correlate the instances in the different MIB modules. 450 The eoAlternateKey object specifies an alternate key string that 451 can be used to identify the Energy Object. Since an EnMS may 452 need to correlate objects across management systems, this 453 alternate key is provided to facilitate such a link. This 454 optional value is intended as a foreign key or alternate 455 identifier for a manufacturer or EnMS to use to correlate the 456 unique Energy Object Id in other systems or namespaces. If an 457 alternate key is not available or is not applicable then the 458 value is the zero-length string. 460 An Energy Object can have additional MIB objects that can be 461 used for easier identification by the EnMS. The optional objects 462 eoMgmtMacAddress, eoMgmtAddressType eoMgmtDNSName can be used to 463 help identify the relationship between the Energy Objects and 464 other NMS objects. These objects can be used as an alternate 465 key to help link the Energy Object with other keyed information 466 that may be stored within the EnMS(s). For the optional objects 467 that may not be included in some vendor implementations, the 468 expected behavior when those objects are polled is a response 469 noSuchInstance. 471 5.4 Energy Object Relationships 473 Refer to the "Energy Object Relationships" section in [EMAN- 474 FMWK] for the definition and background information. In order to 475 link two Energy Objects a separate table (eoRelationTable) has 476 been introduced in this MIB module. 478 Each Energy object can have one or more Energy Object 479 relationships with other Energy Objects. The relationship 480 between Energy Objects are specified in eoRelationTable. The 481 relationship between the Energy Objects is specified with the 482 entPhysicalIndex of the Energy Object and the UUID of the remote 483 Energy Object. The UUID MUST comply to the RFC 4122 484 specifications. It is important to note that it is possible 485 that an Energy Object may not have an Energy Object relationship 486 with other Energy Objects. 488 The following relationships between Energy objects have been 489 considered in the eoRelationTable. 491 Metering Relationship -> meteredBy / metering 493 Power Source Relationship -> poweredBy / powering 495 Aggregation Relationship -> aggregatedBy / aggregating 497 An Energy Object B has "meteredBy" relationship with Energy 498 Object A, if the energy consumption of Energy Object B is 499 measured by Energy Object A. Equivalently, it is possible to 500 indicate that Energy Object A has "metering" relationship with 501 Energy Object B. 503 An Energy Object B has "poweredBy" relationship with Energy 504 Object A, if the power source of Energy Object B Energy Object 505 A. Equivalently, it is possible to indicate that Energy Object A 506 has "powering" relationship with Energy Object B. 508 An Energy Object B has "aggregatedBy" relationship with Energy 509 Object A, if Energy Object A is an aggregation point for energy 510 usage of Energy Object B. Equivalently, it is possible to 511 indicate that Energy Object A has "aggregating" relationship 512 with Energy Object B. 514 The IANA Energy Relationship MIB module in Section 6 below 515 specifies the first version of the IANA-maintained definitions 516 of relationships. This way, for Energy Relationships, new 517 textual conventions can be specified, without updating the 518 primary Energy Object Context MIB module. 520 5.5 Energy Object Identity Persistence 522 In some situations, the Energy Object identity information 523 should be persistent even after a device reload. For example, in 524 a static setup where a switch monitors a series of connected PoE 525 phones, there is a clear benefit for the EnMS if the Energy 526 Object Identification and all associated information persist, as 527 it saves a network discovery. However, in other situations, 528 such as a wireless access point monitoring the mobile user PCs, 529 there is not much advantage to persist the Energy Object 530 Information. The identity information of an Energy Object 531 should be persisted and there is value in the writable MIB 532 objects persisted. 534 5. MIB Definitions 536 -- ************************************************************ 537 -- 538 -- 539 -- This MIB is used for describing the identity and the 540 -- context information of Energy Objects in network 541 -- 542 -- 543 -- ************************************************************* 545 ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN 547 IMPORTS 548 MODULE-IDENTITY, 549 OBJECT-TYPE, 550 mib-2, Integer32 551 FROM SNMPv2-SMI -- RFC2578 552 TEXTUAL-CONVENTION, MacAddress, TruthValue, RowStatus 553 FROM SNMPv2-TC -- RFC2579 554 MODULE-COMPLIANCE, OBJECT-GROUP 555 FROM SNMPv2-CONF -- RFC2580 556 SnmpAdminString 557 FROM SNMP-FRAMEWORK-MIB -- RFC3411 558 InetAddressType, InetAddress 559 FROM INET-ADDRESS-MIB -- RFC3291 560 entPhysicalIndex 561 FROM ENTITY-MIB -- RFC6933 562 UUIDorZero 563 FROM UUID-TC-MIB -- RFC6933 564 IANAEnergyRelationship 565 FROM IANA-ENERGY-RELATION-MIB; 567 energyObjectContextMIB MODULE-IDENTITY 568 LAST-UPDATED "201402100000Z" 570 ORGANIZATION "IETF EMAN Working Group" 571 CONTACT-INFO 572 "WG Charter: 573 http://datatracker.ietf.org/wg/eman/charter/ 575 Mailing Lists: 576 General Discussion: eman@ietf.org 577 To Subscribe: https://www.ietf.org/mailman/listinfo/eman 578 Archive: http://www.ietf.org/mail-archive/web/eman 580 Editors: 581 John Parello 582 Cisco Systems, Inc. 583 3550 Cisco Way 584 San Jose, California 95134 585 US 586 Phone: +1 408 525 2339 587 Email: jparello@cisco.com 589 Benoit Claise 590 Cisco Systems, Inc. 591 De Kleetlaan 6a b1 592 Degem 1831 593 Belgium 594 Phone: +32 2 704 5622 595 Email: bclaise@cisco.com 597 Mouli Chandramouli 598 Cisco Systems, Inc. 599 Sarjapur Outer Ring Road 600 Bangalore 560103 601 IN 602 Phone: +91 80 4429 2409 603 Email: moulchan@cisco.com" 605 DESCRIPTION 606 "This MIB is used for describing the identity and the 607 context information of Energy Objects" 608 REVISION 609 "201402100000Z" 610 DESCRIPTION 611 "Initial version, published as RFC YYY." 613 ::= { mib-2 XXX1 } 615 -- RFC Editor, please replace XXX1 with the IANA allocation 616 -- for this MIB module and YYY with the number of the 617 -- approved RFC 619 energyObjectContextMIBNotifs OBJECT IDENTIFIER 620 ::= { energyObjectContextMIB 0 } 622 energyObjectContextMIBObjects OBJECT IDENTIFIER 623 ::= { energyObjectContextMIB 1 } 625 energyObjectContextMIBConform OBJECT IDENTIFIER 626 ::= { energyObjectContextMIB 2 } 628 -- Textual Conventions 630 PethPsePortIndexOrZero ::= TEXTUAL-CONVENTION 631 DISPLAY-HINT "d" 632 STATUS current 633 DESCRIPTION 634 "This textual convention is an extension of the 635 pethPsePortIndex convention, which defines a greater than 636 zero value used to identify a power Ethernet PSE port. 637 This extension permits the additional value of zero. The 638 semantics of the value zero are object-specific and must, 639 therefore, be defined as part of the description of any 640 object that uses this syntax. Examples of the usage of 641 this extension are situations where none or all physical 642 entities need to be referenced." 643 SYNTAX Integer32 (0..2147483647) 645 PethPsePortGroupIndexOrZero ::= TEXTUAL-CONVENTION 646 DISPLAY-HINT "d" 647 STATUS current 648 DESCRIPTION 649 "This textual convention is an extension of the 650 pethPsePortGroupIndex convention from the Power Over 651 Ethernet MIB RFC 3621, which defines a greater than zero 652 value used to identify group containing the port to which 653 a power Ethernet PSE is connected. This extension 654 permits the additional value of zero. The semantics of 655 the value zero are object-specific and must, therefore, 656 be defined as part of the description of any object that 657 uses this syntax. Examples of the usage of this 658 extension are situations where none or all physical 659 entities need to be referenced." 660 SYNTAX Integer32 (0..2147483647) 662 LldpPortNumberOrZero ::= TEXTUAL-CONVENTION 663 DISPLAY-HINT "d" 664 STATUS current 665 DESCRIPTION 666 "This textual convention is an extension of the 667 LldpPortNumber convention specified in the LLDP MIB, 668 which defines a greater than zero value used to uniquely 669 identify each port contained in the chassis (that is 670 known to the LLDP agent) by a port number. This 671 extension permits the additional value of zero. The 672 semantics of the value zero are object-specific and must, 673 therefore, be defined as part of the description of any 674 object that uses this syntax. Examples of the usage of 675 this extension are situations where none or all physical 676 entities need to be referenced." 677 SYNTAX Integer32(0..4096) 679 EnergyObjectKeywordList ::= TEXTUAL-CONVENTION 680 STATUS current 681 DESCRIPTION 682 "A list of keywords that can be used to group Energy 683 Objects for reporting or searching. If multiple keywords 684 are present, then this string will contain all the 685 keywords separated by the ',' character. All alphanumeric 686 characters and symbols (other than a comma), such as #, 687 (, $, !, and &, are allowed. White spaces before and 688 after the commas are ignored, as well as within a keyword 689 itself. 691 For example, if an Energy Object were to be tagged with 692 the keyword values 'hospitality' and 'guest', then the 693 keyword list will be 'hospitality,guest'." 694 SYNTAX OCTET STRING (SIZE (0..2048)) 696 -- Objects 698 eoTable OBJECT-TYPE 699 SYNTAX SEQUENCE OF EoEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "This table lists Energy Objects." 704 ::= { energyObjectContextMIBObjects 1 } 706 eoEntry OBJECT-TYPE 707 SYNTAX EoEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "An entry describes the attributes of an Energy Object. 712 Whenever a new Energy Object is added or an existing 713 Energy Object is deleted, a row in the eoTable is added 714 or deleted." 716 INDEX {entPhysicalIndex } 717 ::= { eoTable 1 } 719 EoEntry ::= SEQUENCE { 720 eoEthPortIndex PethPsePortIndexOrZero, 721 eoEthPortGrpIndex PethPsePortGroupIndexOrZero, 722 eoLldpPortNumber LldpPortNumberOrZero, 723 eoMgmtMacAddress MacAddress, 724 eoMgmtAddressType InetAddressType, 725 eoMgmtAddress InetAddress, 726 eoMgmtDNSName OCTET STRING,, 727 eoDomainName SnmpAdminString, 728 eoRoleDescription SnmpAdminString, 729 eoKeywords EnergyObjectKeywordList, 730 eoImportance Integer32, 731 eoPowerCategory INTEGER, 732 eoAlternateKey SnmpAdminString, 733 eoPowerInterfaceType INTEGER 734 } 736 eoEthPortIndex OBJECT-TYPE 737 SYNTAX PethPsePortIndexOrZero 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "This variable uniquely identifies the power Ethernet 742 port to which a Power over Enternet device is connected . 743 If the Power over Ethernet MIB RFC 3621 is supported by 744 the SNMP agent managing the Energy Object, then the 745 Energy Object eoethPortIndex MUST contain the 746 corresponding value of pethPsePortIndex. f such a power 747 Ethernet port cannot be specified or is not known then 748 the object is zero." 749 REFERENCE "RFC 3621 " 750 DEFVAL { 0 } 752 ::= { eoEntry 1 } 754 eoEthPortGrpIndex OBJECT-TYPE 755 SYNTAX PethPsePortGroupIndexOrZero 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "This variable uniquely identifies the group containing 760 the port to which a power over Ethernet device PSE is 761 connected [RFC3621]. If the Power over Ethernet MIB RFC 762 3621 is supported by the SNMP agent managing the Energy 763 Object, then the Energy Object eoEthPortGrpIndex MUST 764 contain the corresponding value of eoethPortGrpIndex. If 765 such a power Ethernet port cannot be specified or is not 766 known then the object is zero." 767 REFERENCE "RFC 3621" 768 DEFVAL { 0 } 770 ::= { eoEntry 2 } 772 eoLldpPortNumber OBJECT-TYPE 773 SYNTAX LldpPortNumberOrZero 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "This variable uniquely identifies the port component 778 (contained in the local chassis with the LLDP agent) as 779 defined by the lldpLocPortNum in the [LLDP-MIB] and 780 [LLDP-MED-MIB]. If the [LLDP-MIB] is supported by the 781 SNMP agent managing the Energy Object, then the Energy 782 Object eoLldpPortNumber MUST contain the corresponding 783 value of lldpLocPortNum from the [LLDP-MIB]. If such a 784 port number cannot be specified or is not known then the 785 object is zero." 786 REFERENCE "LLDP MIB, IEEE 802.1AB-2005, 787 LLDP-MED-MIB, ANSI/TIA-1057, " 788 DEFVAL { 0 } 790 ::= { eoEntry 3 } 792 eoMgmtMacAddress OBJECT-TYPE 793 SYNTAX MacAddress 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "This object specifies a MAC address of the Energy 798 Object." 799 ::= { eoEntry 4 } 801 eoMgmtAddressType OBJECT-TYPE 802 SYNTAX InetAddressType 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "This object specifies the eoMgmtAddress type, i.e. an 807 IPv4 address or an IPv6 address. This object MUST be 808 populated when eoMgmtAddress is populated." 809 ::= { eoEntry 5 } 811 eoMgmtAddress OBJECT-TYPE 812 SYNTAX InetAddress 813 MAX-ACCESS read-only 814 STATUS current 815 DESCRIPTION 816 "This object specifies the management address as an IPv4 817 address or IPv6 address of Energy Object. The IP address 818 type, i.e. IPv4 or IPv6, is determined by the 819 eoMgmtAddressType value. This object can be used as an 820 alternate key to help link the Energy Object with other 821 keyed information that may be stored within the EnMS(s)." 822 ::= { eoEntry 6 } 824 eoMgmtDNSName OBJECT-TYPE 825 SYNTAX OCTET STRING 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "This object specifies a DNS name of the eoMgmtAddress. 830 This object can be used as an alternate key to help link 831 the Energy Object with other keyed information that may 832 be stored within the EnMS(s). A DNS Name must always be a 833 fully qualified name. This MIB uses the same encoding as 834 the DNS protocol." 835 REFERENCE 836 "RFC-1034 section 3.1." 837 ::= { eoEntry 7 } 839 eoDomainName OBJECT-TYPE 840 SYNTAX SnmpAdminString 841 MAX-ACCESS read-write 842 STATUS current 843 DESCRIPTION 844 "This object specifies the name of an Energy Management 845 Domain for the Energy Object. By default, this object 846 should be an empty string. The value of eoDomainName must 847 remain constant at least from one re-initialization of 848 the entity local management system to the next re- 849 initialization." 850 ::= { eoEntry 8 } 852 eoRoleDescription OBJECT-TYPE 853 SYNTAX SnmpAdminString 854 MAX-ACCESS read-write 855 STATUS current 856 DESCRIPTION 857 "This object specifies an administratively assigned name 858 to indicate the purpose an Energy Object serves in the 859 network. 861 For example, we can have a phone deployed to a lobby with 862 eoRoleDescription as 'Lobby phone'. 864 This object specifies that the value is the zero-length 865 string value if no role description is configured. 866 The value of eoRoleDescription must remain constant at 867 least from one re-initialization of the entity local 868 management system to the next re-initialization. " 869 ::= { eoEntry 9 } 871 eoKeywords OBJECT-TYPE 872 SYNTAX EnergyObjectKeywordList 873 MAX-ACCESS read-write 874 STATUS current 875 DESCRIPTION 876 "This object specifies a list of keywords that can be 877 used to group Energy Objects for reporting or searching. 878 The value is the zero-length string if no keywords have 879 been configured. If multiple keywords are present, then 880 this string will contain all the keywords separated by 881 the ',' character. For example, if an Energy Object were 882 to be tagged with the keyword values 'hospitality' and 883 'guest', then the keyword list will be 884 'hospitality,guest'. 886 If write access is implemented and a value is written 887 into the instance, the agent must retain the supplied 888 value in the eoKeywords instance associated with 889 the same physical entity for as long as that entity 890 remains instantiated. This includes instantiations 891 across all re-initializations/reboots of the local 892 management agent. " 893 ::= { eoEntry 10 } 895 eoImportance OBJECT-TYPE 896 SYNTAX Integer32 (1..100) 897 MAX-ACCESS read-write 898 STATUS current 899 DESCRIPTION 900 "This object specifies a ranking of how important the 901 Energy Object is (on a scale of 1 to 100) compared with 902 other Energy Objects in the same Energy Management 903 Domain. The ranking should provide a business or 904 operational context for the Energy Object as compared to 905 other similar Energy Objects. This ranking could be used 906 as input for policy-based network management. 908 Although network managers must establish their own 909 ranking, the following is a broad recommendation: 911 90 to 100 Emergency response 912 80 to 90 Executive or business critical 913 70 to 79 General or Average 914 60 to 69 Staff or support 915 40 to 59 Public or guest 916 1 to 39 Decorative or hospitality 918 The value of eoImportance must remain constant at least 919 from one re-initialization of the Energy Object local 920 management system to the next re-initialization. " 921 DEFVAL { 1 } 922 ::= { eoEntry 11 } 924 eoPowerCategory OBJECT-TYPE 925 SYNTAX INTEGER { 926 consumer(0), 927 producer(1), 928 meter(2), 929 distributor(3), 930 store(4) 931 } 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "This object describes the Energy Object category, which 936 indicates the expected behavior or physical property of 937 the Energy Object, based on its design. An Energy Object 938 can be a consumer(0), producer(1), meter(2), 939 distributor(3) or store(4). 941 In some cases, a meter is required to measure the power 942 consumption. In such a case, this meter Energy Object 943 category is meter(2). If a device is distributing 944 electric Energy, the category of the Energy Object is 945 distributor (3). If a device is storing electric Energy, 946 the category of the device can be store (4). " 947 ::= { eoEntry 12 } 949 eoAlternateKey OBJECT-TYPE 950 SYNTAX SnmpAdminString 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 "The eoAlternateKey object specifies an alternate key 955 string that can be used to identify the Energy Object. 956 Since Energy Management Systems (EnMS) and Network 957 Management Systems (NMS) may need to correlate objects 958 across management systems, this alternate key is provided 959 to provide such a link. This optional value is intended 960 as a foreign key or alternate identifier for a 961 manufacturer or EnMS/NMS to use to correlate the unique 962 Energy Object Id in other systems or namespaces. If an 963 alternate key is not available or is not applicable then 964 the value is the zero-length string. 965 The value of eoAlternateKey must remain constant at 966 least from one re-initialization of the entity local 967 management system to the next re-initialization. " 968 ::= { eoEntry 13 } 970 eoPowerInterfaceType OBJECT-TYPE 971 SYNTAX INTEGER { 972 inlet(0), 973 outlet(1), 974 both(2) 975 } 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "This object describes the Power Interface for an Energy 980 Object. A Power Interface is an interface at which a 981 Energy Object is connected to a power transmission 982 medium, at which it can in turn receive power, provide 983 power, or both. A Power Interface type can be an inlet(0) 984 or outlet(1) or both(2), respectively." 985 ::= { eoEntry 14 } 987 eoRelationTable OBJECT-TYPE 988 SYNTAX SEQUENCE OF EoRelationEntry 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "This table describes the relationships between Energy 993 Objects." 994 ::= { energyObjectContextMIBObjects 2 } 996 eoRelationEntry OBJECT-TYPE 997 SYNTAX EoRelationEntry 998 MAX-ACCESS not-accessible 999 STATUS current 1000 DESCRIPTION 1001 "An entry in this table specifies the Energy relationship 1002 between Energy objects. Energy relations between two 1003 Energy objects are defined in the EMAN-FMWK." 1004 REFERENCE 1005 "EMAN-FMWK, Energy Management Framework, RFC abcs, 1006 Jan 2014" 1007 INDEX { entPhysicalIndex, eoRelationIndex } 1008 ::= { eoRelationTable 1 } 1010 EoRelationEntry ::= SEQUENCE { 1011 eoRelationIndex Integer32, 1012 eoRelationID UUIDorZero, 1013 eoRelationship IANAEnergyRelationship, 1014 eoRelationStatus RowStatus 1015 } 1017 eoRelationIndex OBJECT-TYPE 1018 SYNTAX Integer32 (0..2147483647) 1019 MAX-ACCESS not-accessible 1020 STATUS current 1021 DESCRIPTION 1022 "This object is an arbitrary index to identify the Energy 1023 Object related to another Energy Object" 1024 ::= { eoRelationEntry 1 } 1026 eoRelationID OBJECT-TYPE 1027 SYNTAX UUIDorZero 1028 MAX-ACCESS read-create 1029 STATUS current 1030 DESCRIPTION 1031 "This object specifies the Universally Unique Identifier 1032 (UUID) of the peer (other) Energy Object. The UUID must 1033 comply the specifications of UUID in UUID-TC-MIB. 1035 If UUID of the energy object is unknown or non-existent, 1036 the eoRelationID will be set to a zero-length string 1037 instead. It is preferable that the value of 1038 entPhysicalUUID from ENTITY-MIB is used for values for 1039 this object." 1041 REFERENCE 1042 "RFC 6933, Entity MIB - version 4, May 2013 " 1043 ::= { eoRelationEntry 2 } 1045 eoRelationship OBJECT-TYPE 1046 SYNTAX IANAEnergyRelationship 1047 MAX-ACCESS read-create 1048 STATUS current 1049 DESCRIPTION 1050 "This object describes the relations between Energy 1051 objects. For each Energy object, the relations between 1052 the other Energy objects are specified using the bitmap." 1053 ::= { eoRelationEntry 3 } 1055 eoRelationStatus OBJECT-TYPE 1056 SYNTAX RowStatus 1057 MAX-ACCESS read-create 1058 STATUS current 1059 DESCRIPTION 1060 "The status controls and reflects the creation and 1061 activation status of a row in this table to specify energy 1062 relationship between Energy objects. 1064 An entry status may not be active(1) unless all objects in 1065 the entry have the appropriate values. 1066 No attempt to modify a row columnar object instance value 1067 in the eoRelationTable should be issued while the value of 1068 eoRelationStatus is active(1). The data can be destroyed by 1069 setting up the eoRelationStatus to destroy(2)." 1071 ::= { eoRelationEntry 4 } 1073 -- Conformance 1075 energyObjectContextMIBCompliances OBJECT IDENTIFIER 1076 ::= { energyObjectContextMIBConform 1 } 1078 energyObjectContextMIBGroups OBJECT IDENTIFIER 1079 ::= { energyObjectContextMIBConform 2 } 1081 energyObjectContextMIBFullCompliance MODULE-COMPLIANCE 1082 STATUS current 1083 DESCRIPTION 1084 "When this MIB is implemented with support for 1085 read-write, then such an implementation can 1086 claim full compliance. Such devices can then 1087 be both monitored and configured with this MIB. 1088 Module Compliance of ENTITY-MIB with respect to 1089 entity4CRCompliance MUST be supported." 1091 MODULE -- this module 1092 MANDATORY-GROUPS { 1093 energyObjectContextMIBTableGroup, 1094 energyObjectRelationTableGroup 1095 } 1097 GROUP energyObjectOptionalMIBTableGroup 1098 DESCRIPTION 1099 "A compliant implementation does not have to 1100 implement. " 1101 ::= { energyObjectContextMIBCompliances 1 } 1103 energyObjectContextMIBReadOnlyCompliance MODULE-COMPLIANCE 1104 STATUS current 1105 DESCRIPTION 1106 "When this MIB is implemented without support for 1107 read-write (i.e. in read-only mode), then such an 1108 implementation can claim read-only compliance. 1109 Such a device can then be monitored but cannot be 1110 Configured with this MIB. 1111 Module Compliance of ENTITY-MIB with respect to 1112 entity4CRCompliance MUST be supported." 1113 MODULE -- this module 1115 MANDATORY-GROUPS { 1116 energyObjectContextMIBTableGroup, 1117 energyObjectRelationTableGroup 1118 } 1120 GROUP energyObjectOptionalMIBTableGroup 1121 DESCRIPTION 1122 "A compliant implementation does not have to implement 1123 the managed objects in this GROUP. " 1125 ::= { energyObjectContextMIBCompliances 2 } 1127 -- Units of Conformance 1129 energyObjectContextMIBTableGroup OBJECT-GROUP 1130 OBJECTS { 1131 eoDomainName, 1132 eoRoleDescription, 1133 eoAlternateKey, 1134 eoKeywords, 1135 eoImportance, 1136 eoPowerCategory, 1137 eoPowerInterfaceType 1138 } 1139 STATUS current 1140 DESCRIPTION 1141 "This group contains the collection of all the objects 1142 related to the EnergyObject. " 1144 ::= { energyObjectContextMIBGroups 1 } 1146 energyObjectOptionalMIBTableGroup OBJECT-GROUP 1147 OBJECTS { 1148 eoEthPortIndex, 1149 eoEthPortGrpIndex, 1150 eoLldpPortNumber, 1151 eoMgmtMacAddress, 1152 eoMgmtAddressType, 1153 eoMgmtAddress, 1154 eoMgmtDNSName 1155 } 1156 STATUS current 1157 DESCRIPTION 1158 "This group contains the collection of all the objects 1159 related to the Energy Object." 1160 ::= { energyObjectContextMIBGroups 2 } 1162 energyObjectRelationTableGroup OBJECT-GROUP 1163 OBJECTS { 1165 eoRelationID, 1166 eoRelationship, 1167 eoRelationStatus 1168 } 1169 STATUS current 1170 DESCRIPTION 1171 "This group contains the collection of all objects 1172 specifying the relationship between Energy Objects." 1173 ::= { energyObjectContextMIBGroups 3 } 1175 END 1177 IANA-ENERGY-RELATION-MIB DEFINITIONS ::= BEGIN 1178 IMPORTS 1179 MODULE-IDENTITY, mib-2 1180 FROM SNMPv2-SMI 1181 TEXTUAL-CONVENTION 1182 FROM SNMPv2-TC; 1184 ianaEnergyRelationMIB MODULE-IDENTITY 1185 LAST-UPDATED "201402100000Z" -- February 10, 2014 1186 ORGANIZATION "IANA" 1187 CONTACT-INFO " 1188 Internet Assigned Numbers Authority 1189 Postal: ICANN 1190 4676 Admiralty Way, Suite 330 1191 Marina del Rey, CA 90292 1192 Tel: +1-310-823-9358 1193 EMail: iana&iana.org" 1195 DESCRIPTION 1196 "This MIB module defines a TEXTUAL-CONVENTION that 1197 describes the relationships between Energy Objects. 1199 Copyright (C) The IETF Trust (2013). 1201 The initial version of this MIB module was published in 1202 RFC YYY; for full legal notices see the RFC itself. 1204 Supplementary information may be available at 1205 http://www.ietf.org/copyrights/ianamib.html" 1207 REVISION "201402100000Z" -- February 10, 2014 1208 DESCRIPTION "Initial version of this MIB as published in 1209 RFC YYY." 1210 ::= { mib-2 XXX2 } 1212 -- RFC Editor, please replace XXX2 with the IANA allocation 1213 -- for this MIB module and YYY with the number of the 1214 -- approved RFC 1216 -- Textual Conventions 1218 IANAEnergyRelationship ::= TEXTUAL-CONVENTION 1219 STATUS current 1220 DESCRIPTION 1221 "An enumerated value specifying the type of 1222 relationship between an Energy Object A, on 1223 which the relationship is specified, with the 1224 Energy Object B, identified by the UUID. 1226 The enumeration 'poweredBy' is applicable if the 1227 Energy Object A is poweredBy Energy Object B. 1229 The enumeration 'powering' is applicable if the 1230 Energy Object A is powering Energy Object B. 1232 The enumeration 'meteredBy' is applicable if the 1233 Energy Object A is meteredBy Energy Object B. 1235 The enumeration 'metering' is applicable if the 1236 Energy Object A is metering Energy Object B. 1238 The enumeration 'aggregatedBy' is applicable if the 1239 Energy Object A is aggregatedBy Energy Object B. 1241 The enumeration 'aggregating' is applicable if the 1242 Energy Object A is aggregating Energy Object B." 1244 SYNTAX INTEGER { 1245 poweredBy(1), -- power relationship 1246 powering(2), 1247 meteredBy(3), -- meter relationship 1248 metering(4), 1249 aggregatedBy(5), -- aggregation relationship 1250 aggregating(6) 1251 } 1253 END 1255 6. Implementation Status 1257 [Note to RFC Editor: Please remove this section and the 1258 reference to [RFC6982] before publication.] 1260 This section records the status of known implementations of the 1261 EMAN-Monitoring MIB at the time of posting of this Internet- 1262 Draft, and is based on a proposal described in [RFC6982]. 1264 The description of implementations in this section is intended 1265 to assist the IETF in its decision processes in progressing 1266 drafts to RFCs. 1268 11.1 SNMP Research 1270 Organization: SNMP Research, Inc. 1272 Maturity: Prototype based upon early drafts of the MIBs. 1273 We anticipate updating it to more recent 1274 documents as development schedules allow. 1276 Coverage: Code was generated to implement all MIB objects 1277 in ENTITY-MIB (Version 4), 1278 ENERGY-OBJECT-CONTEXT-MIB, 1279 ENERGY-OBJECT-MIB, 1280 POWER-CHARACTERISTICS-MIB, 1281 and BATTERY-MIB. 1283 Implementation experience: The documents are implementable. 1285 Comments: Technical comments about the 1286 ENERGY-OBJECT-CONTEXT-MIB, 1287 ENERGY-OBJECT-MIB, and 1288 BATTERY-MIB 1289 were submitted to the EMAN Working Group 1290 E-mail list. 1292 Licensing: Proprietary, royalty licensing 1294 Contact: Alan Luchuk, luchuk at snmp.com 1296 URL: http://www.snmp.com/ 1298 11.2 Python 1300 Priyanka Rao mentioned on the mailing list 1301 (http://www.ietf.org/mail-archive/web/eman/current/msg02063.html) 1302 that she has a python implementation. 1304 7. Security Considerations 1306 Some of the readable objects in these MIB modules (i.e., objects 1307 with a MAX-ACCESS other than not-accessible) may be considered 1308 sensitive or vulnerable in some network environments. It is 1309 thus important to control even GET and/or NOTIFY access to these 1310 objects and possibly to even encrypt the values of these objects 1311 when sending them over the network via SNMP. 1313 There are a number of management objects defined in these MIB 1314 modules with a MAX-ACCESS clause of read-write and/or read- 1315 create. Such objects MAY be considered sensitive or vulnerable 1316 in some network environments. The support for SET operations in 1317 a non-secure environment without proper protection can have a 1318 negative effect on network operations. The following are the 1319 tables and objects and their sensitivity/vulnerability: 1321 . Unauthorized changes to the eoDomainName, entPhysicalName, 1322 eoRoleDescription, eoKeywords, and/or eoImportance MAY 1323 disrupt power and energy collection, and therefore any 1324 predefined policies defined in the network. 1326 SNMP versions prior to SNMPv3 did not include adequate security. 1327 Even if the network itself is secure (for example, by using 1328 IPsec), there is still no secure control over who on the secure 1329 network is allowed to access and GET/SET 1330 (read/change/create/delete) the objects in these MIB modules. 1332 It is RECOMMENDED that implementers consider the security 1333 features as provided by the SNMPv3 framework (see [RFC3410], 1334 section 8), including full support for the SNMPv3 cryptographic 1335 mechanisms (for authentication and privacy). 1337 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1338 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1339 enable cryptographic security. It is then a customer/operator 1340 responsibility to ensure that the SNMP entity giving access to 1341 an instance of these MIB modules is properly configured to give 1342 access to the objects only to those principals (users) that have 1343 legitimate rights to GET or SET (change/create/delete) them. 1345 8. IANA Considerations 1347 The MIB modules in this document use the following IANA-assigned 1348 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1350 Descriptor OBJECT IDENTIFIER value 1352 ---------- ----------------------- 1354 energyAwareMIB { mib-2 XXX1 } 1356 Editor's Note (to be removed prior to publication): IANA is 1357 requested to assign a value for "XXX1" under the 'mib-2' subtree 1358 and to record the assignment in the SMI Numbers registry. When 1359 the assignment has been made, the RFC Editor is asked to replace 1360 "XXX1" (here and in the MIB module) with the assigned value and 1361 to remove this note. 1363 This document defines the first version of the IANA-maintained 1364 IANA-ENERGY-RELATION-MIB module, which allows new definitions of 1365 relationships between Energy Objects. 1367 A Specification Required as defined in RFC 5226 [RFC5226], is 1368 REQUIRED for each modification of the energy relationships. 1370 The MIB module in this document uses the following IANA-assigned 1371 OBJECT IDENTIFIER values recorded in the SMI Numbers registry. 1373 Descriptor OBJECT IDENTIFIER value 1375 ---------- ----------------------- 1377 ianaEnergyRelationMIB { mib-2 XXX2 } 1379 Editor's Note (to be removed prior to publication): IANA is 1380 requested to assign a value for "XXX2" under the 'mib-2' subtree 1381 and to record the assignment in the SMI Numbers registry. When 1382 the assignment has been made, the RFC Editor is asked to replace 1383 "XXX2" (here and in the MIB module) with the assigned value and 1384 to remove this note. 1386 9. Acknowledgement 1388 We would like to thank Juergen Quittek and Juergen Schoenwalder 1389 for their suggestions on the new design of eoRelationTable which 1390 was a proposed solution for the open issue on the representation 1391 of Energy Object as a UUIDlist. 1393 Many thanks to Juergen Quittek for many comments on the wording, 1394 text and design of the MIB thus resulting in an improved draft. 1396 Many thanks to Alan Luchuk for the review of the MIB and his 1397 comments. 1399 In addition the authors thank Bill Mielke for his multiple 1400 reviews, Brad Schoening and Juergen Schoenwaelder for their 1401 suggestions and Michael Brown for dramatically improving this 1402 draft. 1404 And finally thanks the EMAN WG chairs: Nevil Brownlee and Tom 1405 Nadeau. 1407 10. References 1409 10.1. Normative References 1411 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 1412 Requirement Levels, BCP 14, RFC 2119, March 1997. 1414 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1415 Schoenwaelder, Ed., "Structure of Management 1416 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1417 1999. 1419 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1420 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1421 STD 58, RFC 2579, April 1999. 1423 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1424 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1425 April 1999. 1427 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 1428 RFC3621, December 2003. 1430 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 1431 Unique IDentifier (UUID) URN Namespace ", RFC 4122, 1432 July 2005. 1434 [RFC6933] Bierman, A. Romascanu,D. Quittek, J. and M. 1435 Chandramouli, "Entity MIB (Version 4)", RFC 6933, May 1436 2013. 1438 [LLDP-MIB] IEEE 802.1AB-2005, "Management Information Base 1439 module for LLDP configuration, statistics, local system 1440 data and remote systems data components", May 2005. 1442 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 1443 Base extension module for TIA-TR41.4 media endpoint 1444 discovery information", July 2005. 1446 [EMAN-MON-MIB] M. Chandramouli, Schoening, B., Quittek, J., 1447 Dietz, T., and B. Claise "Power and Energy Monitoring 1448 MIB", draft-ietf-eman-energy-monitoring-mib-08, December 1449 2013. 1451 10.2. Informative References 1453 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1454 "Introduction and Applicability Statements for Internet 1455 Standard Management Framework", RFC 3410, December 1456 2002. 1458 [RFC3433] Bierman, A., Romascanu, D., and K.C. Norseth, "Entity 1459 Sensor Management Information Base", RFC 3433, December 1460 2002. 1462 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 1463 "Guidelines for Writing an IANA Considerations Section 1464 in RFCs ", BCP 26, RFC 5226, May 2008. 1466 [RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M. 1467 Chandramouli, "Requirements for Energy Management", RFC 1468 6988, September 2013. 1470 [EMAN-FMWK] Claise, B., Parello, J., Schoening, B., and J. 1471 Quittek, "Energy Management Framework", draft-ietf- 1472 eman-framework-15, work in progress, February 2014. 1474 [EMAN-AS] Schoening, B., Chandramouli, M, and B. Nordman, 1475 "Energy Management (EMAN) Applicability Statement", 1476 draft-ietf-eman-applicability-statement-04.txt, work in 1477 progress, October 2013. 1479 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of 1480 Running Code: The Implementation Status Section", RFC 1481 6982, July 2013. 1483 Authors' Addresses 1485 Benoit Claise 1486 Cisco Systems, Inc. 1487 De Kleetlaan 6a b1 1488 Diegem 1813 1489 BE 1491 Phone: +32 2 704 5622 1492 Email: bclaise@cisco.com 1494 John Parello 1495 Cisco Systems, Inc. 1496 3550 Cisco Way 1497 San Jose, California 95134 1498 US 1500 Phone: +1 408 525 2339 1501 Email: jparello@cisco.com 1503 Mouli Chandramouli 1504 Cisco Systems, Inc. 1505 Sarjapur Outer Ring Road 1506 Bangalore 560103 1507 IN 1509 Phone: +91 80 4429 2409 1510 Email: moulchan@cisco.com