idnits 2.17.1 draft-ietf-hubmib-power-ethernet-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 27 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 28 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 56 instances of too long lines in the document, the longest one being 17 characters in excess of 72. ** The abstract seems to contain references ([RFC2665]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 171 has weird spacing: '...o allow for t...' == Line 308 has weird spacing: '...CESS to read-...' == Line 352 has weird spacing: '... update the d...' == Line 391 has weird spacing: '...tivated objec...' == Line 825 has weird spacing: '...s value ident...' == (2 more instances...) ** The document contains RFC2119-like boilerplate, but doesn't seem to mention RFC 2119. The boilerplate contains a reference [RFC2863], but that reference does not seem to mention RFC 2119 either. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (19 December 2002) is 7798 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) == Missing Reference: 'RFC2863' is mentioned on line 71, but not defined == Missing Reference: 'RFC2274' is mentioned on line 1252, but not defined ** Obsolete undefined reference: RFC 2274 (Obsoleted by RFC 2574) == Missing Reference: 'RFC2275' is mentioned on line 1253, but not defined ** Obsolete undefined reference: RFC 2275 (Obsoleted by RFC 2575) == Unused Reference: 'RFC2119' is defined on line 1160, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2665 (Obsoleted by RFC 3635) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.3af' -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) Summary: 18 errors (**), 0 flaws (~~), 15 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Avi Berger 3 PowerDsine Inc. 4 Dan Romascanu 5 Avaya Inc. 6 19 December 2002 8 Power Ethernet (DTE Power via MDI) MIB 10 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference 23 material or to cite them other than as "work in progress." 25 To view the list Internet-Draft Shadow Directories, see 26 http://www.ietf.org/shadow.html. 28 Copyright Notice 30 Copyright (C) The Internet Society (2002). All Rights Reserved. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 The document proposes an extension to the Ethernet-like Interfaces 37 MIB [RFC2665] with a set of objects for managing a power Ethernet 38 Powered Device (PD) and/or Power Source Equipment (PSE). 40 Distribution of this memo is unlimited. 42 Table of Contents 44 Status of this Memo 1 45 Abstract 1 46 1 Introduction 2 47 2 The SNMP Management Framework 2 48 3 Overview 3 49 4 MIB Structure 4 50 5 Evolution of the Document, Limitations and Future Work 4 51 6 Changes log 4 52 7 Definitions 10 53 8 Normative References 24 54 9 Informative References 25 55 10 Intellectual Property 26 56 11 Security Considerations 27 57 12 Authors Addresses 27 58 A Full Copyright Statement 28 60 1. Introduction 62 This memo defines a portion of the Management Information Base (MIB) 63 for use with network management protocols in the Internet community. 64 In particular, it defines a set of MIB objects to manage a Power 65 Ethernet (DTE Power via MDI)Powered Device (PD) and/or power Source 66 Equipment (PSE). 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 70 document are to be interpreted as described in [RFC2863]. 72 2. The SNMP Management Framework 74 The SNMP Management Framework presently consists of five major 75 components: 77 o An overall architecture, described in RFC 2571 [RFC2571]. 79 o Mechanisms for describing and naming objects and events for the 80 purpose of management. The first version of this Structure of 81 Management Information (SMI) is called SMIv1 and described in 82 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 83 1215 [RFC1215]. The second version, called SMIv2, is described 84 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 85 STD 58, RFC 2580 [RFC2580]. 87 o Message protocols for transferring management information. The 88 first version of the SNMP message protocol is called SNMPv1 and 89 described in STD 15, RFC 1157 [RFC1157]. A second version of 90 the SNMP message protocol, which is not an Internet standards 91 track protocol, is called SNMPv2c and described in RFC 1901 92 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 93 message protocol is called SNMPv3 and described in RFC 1906 94 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 96 o Protocol operations for accessing management information. The 97 first set of protocol operations and associated PDU formats is 98 described in STD 15, RFC 1157 [RFC1157]. A second set of 99 protocol operations and associated PDU formats is described in 100 RFC 1905 [RFC1905]. 102 o A set of fundamental applications described in RFC 2573 103 [RFC2573] and the view-based access control mechanism described 104 in RFC 2575 [RFC2575]. 106 A more detailed introduction to the current SNMP Management Framework 107 can be found in RFC 2570 [RFC2570]. 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. Objects in the MIB are 111 defined using the mechanisms defined in the SMI. 113 This memo specifies a MIB module that is compliant to the SMIv2. A 114 MIB conforming to the SMIv1 can be produced through the appropriate 115 translations. The resulting translated MIB must be semantically 116 equivalent, except where objects or events are omitted because no 117 translation is possible (use of Counter64). Some machine readable 118 information in SMIv2 will be converted into textual descriptions in 119 SMIv1 during the translation process. However, this loss of machine 120 readable information is not considered to change the semantics of the 121 MIB. 123 3. Overview 125 The emergence of IP telephony as an application that allows for voice 126 applications to be run over the same infrastructure as data 127 applications led to the emergence of Ethernet IP phones, with similar 128 functions and characteristics as the traditional phones. Powering a 129 phone is one of these functions that are being taken as granted. The 130 IEEE 802.3 Working Group initiated a standard work on this subject, 131 currently known as the IEEE 802.3af work [IEEE-802.3af]. 133 The IEEE 802.3af WG will not define a full management interface, but 134 only the hardware registers that will allow for a management 135 interfaces to be built for a powered Ethernet device. The MIB module 136 defined in this document extends the Ethernet-like Interfaces MIB 137 [RFC2665] with the management objects required for the management of 138 the powered Ethernet devices and ports. 140 The following abbreviations are defined in [IEEE-802.3af] and will be 141 used with the same significance in this document: 143 PSE - Power Sourcing Equipment; 144 PD - Powered Device 146 4. MIB Structure 148 This MIB objects are included in four MIB groups - three of them 149 include MIB tables, and the fourth scalar objects 151 The pethPsePortTable defines the objects used for the configuration 152 and describing the status of ports on a PSE device. Examples of PSE 153 devices are Ethernet switches that support power Ethernet and mid- 154 span boxes. 156 The pethPdPortTable defines the objects used for the configuration 157 and describing the status of ports on a PD device. Examples of PD 158 devices are Ethernet phones. 160 The pethMainPseObjects MIB group defines the management objects for a 161 managed main power source in a PSE device. Ethernet switches are one 162 example of boxes that would support these objects. 164 The pethTrapsControlTable includes objects that control the 165 transmission of traps by the agent to a management application. 167 5. Evolution of the Document, Limitations and Future Work 169 The IEEE 802.3af is at this stage work in progress. The scope of this 170 document is to do the standards work in the IETF in parallel with the 171 IEEE standardization activity, in order to allow for the publication 172 of a standard track document containing an SNMP MIB simultaneously 173 or close to the date of the publication of the IEEE revised standard. 174 It is possible that changes may be brought to the IEEE proposal, and 175 the Ethernet MIB Working Group will work in order to ensure 176 consistency between the two standards proposals. 178 6. Changes Log 180 The following changes were introduced relative to the first proposal 181 for a Power Ethernet MIB [PWR-MIB] 183 a. pethPsePortTable has to index pethPsePortGroupIndex & 184 pethPsePortIndex 186 b. pethPsePortIndex INTEGER instead of InterfaceIndex 188 c. Name change pethPsePortStatus insted of pethPsePortFaultError 189 d. Name change pethPsePortStatusClear instead of 190 pethPsePortFaultErrorClear 192 e. DESCRIPTION update for pethPsePortPowerDetectionStatus test(3) 194 f. DESCRIPTION update pethPsePortDetectionOperStatus off(2) 196 g. Adding to pethPsePortStatus one more item both(4) 198 h. Adding pethMainPseTable with a pethMainPseGroupIndex 200 i. Deletting to objects pethMainPseMaxVoltage & pethMainPseMinVoltage 202 j. Change SYNTAX of pethMainPseUsagePower form INTEGER to Gauge32 204 k. Change SYNTAX of pethMainPseUsageCurrent form INTEGER to Gauge32 206 l. Adding pethMainPseBackupActivated & pethMainPseBackupPresent 208 m. Adding Traps Control Objects 210 n. Adding Notifications Section (5 notifications ) 212 o. Adding pethTrapsControlGroup to Conformance Section 214 p. Adding pethPsePortPowerClassifications to pethPsePortTable Class 215 1-5 217 q. Adding pethPsePortPowerClassifications to pethPsePortGroup 219 r. Change in pethPsePortStatus none(1) to ok(1) 221 s. Change in DESCRIPTION of pethMainPseUsagePower from mW to Watt 223 t. Change pethMainPseUsagePower to pethMainPseConsumptionPower 225 u. Delete of pethMainPseUsageCurrent 227 The following changes were introduced between draft-ietf-hubmib- 228 power-ethernet-mib-00.txt and draft-ietf-hubmib-power-ethernet- 229 mib-01.txt: 231 1. change pethMainPowerUsageTrap to pethMainPowerUsageOnTrap 233 2. add pethMainPowerUsageOffTrap 235 3. change pethMainPowerTrapGroup 236 4. change pethPsePorPowerEnable to pethPsePortAdminEnable 238 5. pethPsePortPowerIdPairsControl to 239 pethPsePortPowerPairsControlAbility 241 6. pethPsePortPowerIdPairs to pethPsePortPowerPairs 243 7. delete both from pethPsePortPowerPairs object 245 8. change pethPsePortPowerDetectionStatus to 246 pethPsePortPowerDetectionControl 248 9. delete from pethPsePortPowerDetectionControl off , and change test 249 to 2 251 10. change pethPsePortDetectionOperStatus to 252 pethPsePortDetectionStatus 254 11. change pethPsePortDetectionStatus to: 255 disabled(1), 256 searching(2), 257 detected(3), 258 deliveringPower(4), 259 fault(5), 260 invalidPD(6), 261 test(7), 262 denyLowPriority(8) 264 12. change description for pethPsePortPowerClassifications 266 13. change pethPsePortStatus to pethPsePortCurrentStatus 268 14. Update description for pethPsePortCurrentStatus 270 15. change pethPsePortStatusClear to pethPsePortCurrentStatusClear 272 16. change pethPdPortDetectionOperStatus to pethPdPortDetectionStatus 274 17. change in description of pethPdPortPowerPairs 276 18. change in pethPdPortDetectionStatus description 278 19. delete pethPdPortPowerClassifications object 280 20. change in pethPsePortGroup 282 21. change in pethPdPortGroup 283 22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus 284 object 286 23. change pethPsePortStatusTrap to pethPsePortCurrentStatusTrap 288 24. change pethPsePortTrapGroup 290 The following changes were introduced between draft-ietf-hubmib- 291 power-ethernet-mib-01.txt and draft-ietf-hubmib-power-ethernet- 292 mib-02.txt: 294 1. change pethMainPsePower SYNTAX Integer32 (0..65535) to (1..65535) 296 2. change pethTrapsControlGroupIndex SYNTAX Integer32 (0..65535) to 297 (1..65535) 299 3. change int pethMainPseBackUpActivatedTrap pethPsePortGroupIndex to 300 pethMainPseGroupIndex 302 4. change int pethMainPowerUsageOnTrap pethPsePortGroupIndex to 303 pethMainPseGroupIndex 305 5. change int pethMainPowerUsageOffTrap pethPsePortGroupIndex to 306 pethMainPseGroupIndex 308 6. change pethMainPseGroupIndex MAX-ACCESS to read-only 310 updates from IEEE Draft P802.3af/D3.1, June 5, 2002 312 7. remove from pethPsePortPowerClassifications class5 314 8. remove from pethPsePortCurrentStatus both(4) and description 316 9. add pethPsePortUnderCurrentCounter object 318 10. add pethPsePortOverCurrentCounter object 320 11. remove pethPsePortCurrentStatusClear object 322 12. change pethPsePortType OID to end with 13 324 13. change pethPsePortPowerClassifications OID to end with 14 326 14. update pethPsePortGroup OBJECT-GROUP 328 15. chage reference to new IEEE Draft 330 16. change pethPdCompliance description. 332 The following changes were introduced between draft-ietf-hubmib- 333 power-ethernet-mib-02.txt and draft-ietf-hubmib-power-ethernet- 334 mib-03.txt: 336 1. remove pethPsePortGroupIndex and pethPsePortIndex from 337 pethPsePortOnOffTrap and pethPsePortCurrentStatusTrap 339 2. change pethPsePortGroupIndex and pethPsePortIndex MAX-ACCESS to 340 not-accessible 342 3. remove pethMainPseGroupIndex from pethMainPseBackUpActivatedTrap 344 4. replace pethMainPseGroupIndex with pethMainPseConsumptionPower in 345 pethMainPowerUsageOnTrap and pethMainPowerUsageOffTrap 347 5. change pethMainPseGroupIndex MAX-ACCESS to not-accessible 349 6. move pethPsePortTrapGroup NOTIFICATION-GROUP and 350 pethMainPowerTrapGroup NOTIFICATION-GROUP to the Conformance Section 352 7. update the discription of pethPsePortOnOffTrap 354 8. add pethPsePortPowerDetectionControl to pethPsePortGroup 356 9. change reference to IEEE Draft P802.3af/D3.3 October 2002 358 10. delete enumaration pethPsePortDetectionStatus detected(3) and 359 invalidPD(6) 361 11. change pethPsePortCurrentStatus to 362 pethPsePortPowerMaintenanceStatus 364 12 . change pethPsePortUnderCurrentCounter to 365 pethPsePortMPSAbsentCounter 367 13. add pethPdPortAdminEnable object. 369 14. replace Trap with Notification. 371 15. update pethPsePortOnOffNotification description. 373 16. update pethPsePortDetectionStatus description. 375 17. remove pethPdPortPowerPairs object. 377 18. remove pethPdPortDetectionStatus object. 379 19. remove pethPdPortType object. 381 20. change pethPdPortAdminEnable OID. 383 The following changes were introduced between draft-ietf-hubmib- 384 power-ethernet-mib-03.txt and draft-ietf-hubmib-power-ethernet- 385 mib-04.txt: 387 1. remove pethMainPseMaximumDcPower object 389 2. remove pethMainPseBackupPresent object 391 3. remove pethMainPseBackupActivated object. 393 4. remove pethMainPseBackUpActivatedNotification 395 5. change reference from IEEE Draft P802.3af/D3.3, October, 2002 to 396 IEEE Draft P802.3af/D4.0, November, 2002 398 6. DESCRIPTION "Initial version, published as RFC yyyy." 400 7. change the syntax of pethPsePortGroupIndex from INTEGER 401 (1..2147483647) to Integer32 (1..2147483647). 403 8. change the syntax of pethPsePortIndex from INTEGER (1..2147483647) 404 to Integer32 (1..2147483647). 406 9.change the syntax of pethPdPortIndex from INTEGER (0..65535) to 407 InterfaceIndex. 409 10.import InterfaceIndex from IF-MIB. 411 11. change the syntax of pethMainPseGroupIndex from INTEGER 412 (0..65535) to Integer32 (1..2147483647) 414 12. change the syntax of pethMainPseUsageThreshold from INTEGER 415 (1..99) to Integer32 (1..99). 417 13. change the syntax of pethNotificationControlGroupIndex from 418 INTEGER (1..65535) to Integer32 (1..2147483647) 420 14. replace OID: ! pethNotifications OBJECT IDENTIFIER ::= { 421 powerEthernetMIB 0 } ! pethObjects OBJECT IDENTIFIER ::= { 422 powerEthernetMIB 1 } ! pethConformance OBJECT IDENTIFIER ::= { 423 powerEthernetMIB 2 } 425 15. change the discription of the pethPsePortGroup and 426 pethPdPortGroup 428 16. pethMainPsePower changed to Gauge32 429 17. add: REVISION "200212020000Z" -- December 02, 2002 430 DESCRIPTION "Initial version, published as RFC yyyy." 431 18 change the MIB registered from { dot3 20 } ::= { 432 mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned 433 number & remove this notice 435 7. Definitions 437 POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN 439 IMPORTS 440 MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32, 441 Gauge32, Counter32, NOTIFICATION-TYPE 442 FROM SNMPv2-SMI 443 TruthValue 444 FROM SNMPv2-TC 445 InterfaceIndex 446 FROM IF-MIB 447 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 448 FROM SNMPv2-CONF; 450 powerEthernetMIB MODULE-IDENTITY 452 LAST-UPDATED "200212020000Z" -- December 02, 2002 453 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 454 Working Group" 455 CONTACT-INFO 456 " 458 Chair: Dan Romascanu 459 Avaya Inc. 460 Tel: +972-3-645-8414 461 Email: dromasca@avaya.com 463 Editor: Avi Berger 464 PowerDsine Inc. 465 Tel: 972-9-7755100 Ext 307 466 Fax: 972-9-7755120 467 E-mail: avib@PowerDsine.com 468 " 470 DESCRIPTION 471 "The MIB module for for managing Powered Devices (PD) or 472 Power Source Equipment (PSE) working according to the IEEE 473 802.af Powered Ethernet (DTE Power via MDI) standard. 475 The following terms are used throughout this 476 MIB module. For complete formal definitions, 477 the IEEE 802.3 standards should be consulted 478 wherever possible: 480 Group - A recommended, but optional, entity 481 defined by the IEEE 802.3 management standard, 482 in order to support a modular numbering scheme. 483 The classical example allows an implementor to 484 represent field-replaceable units as groups of 485 ports, with the port numbering matching the 486 modular hardware implementation. 488 Port - This entity identifies the port within the group 489 for which this entry contains information. The numbering 490 scheme for ports is implementation specific." 492 REVISION "200212020000Z" -- December 02, 2002 493 DESCRIPTION "Initial version, published as RFC yyyy." 494 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 496 ::= { mib-2 XXX } 497 -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 499 pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } 500 pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } 501 pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } 503 -- PSE Objects 505 pethPsePortTable OBJECT-TYPE 506 SYNTAX SEQUENCE OF PethPsePortEntry 507 MAX-ACCESS not-accessible 508 STATUS current 509 DESCRIPTION 510 "A table of objects that display and control the power 511 characteristics power Ethernet ports on a Power Source 512 Entity (PSE) device. This group will be implemented in 513 managed power Ethernet switches and mid-span devices." 514 ::= { pethObjects 1 } 516 pethPsePortEntry OBJECT-TYPE 517 SYNTAX PethPsePortEntry 518 MAX-ACCESS not-accessible 519 STATUS current 520 DESCRIPTION 521 "A set of objects that display and control the power 522 characteristics of a power Ethernet PSE port." 524 INDEX { pethPsePortGroupIndex , pethPsePortIndex } 525 ::= { pethPsePortTable 1 } 527 PethPsePortEntry ::= SEQUENCE { 528 pethPsePortGroupIndex 529 Integer32, 530 pethPsePortIndex 531 Integer32, 532 pethPsePortAdminEnable 533 INTEGER, 534 pethPsePortPowerPairsControlAbility 535 TruthValue, 536 pethPsePortPowerPairs 537 INTEGER, 538 pethPsePortPowerDetectionControl 539 INTEGER, 540 pethPsePortDetectionStatus 541 INTEGER, 542 pethPsePortPowerPriority 543 INTEGER, 544 pethPsePortPowerMaintenanceStatus 545 INTEGER, 546 pethPsePortMPSAbsentCounter 547 Counter32, 548 pethPsePortOverCurrentCounter 549 Counter32, 550 pethPsePortType 551 INTEGER, 552 pethPsePortPowerClassifications 553 INTEGER 554 } 556 pethPsePortGroupIndex OBJECT-TYPE 557 SYNTAX Integer32 (1..2147483647) 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "This variable uniquely identifies the group 562 containing the port to which a power Ethernet PSE is connected. 563 Group means box in the stack, module in a rack and the value 1 564 MUST be used for non-modular devices . 566 pethPseMidSpanGroupCapacity is the number of Mid-Span PSE 567 groups that can be contained within the Mid-Span PSE." 568 ::= { pethPsePortEntry 1 } 570 pethPsePortIndex OBJECT-TYPE 571 SYNTAX Integer32 (1..2147483647) 572 MAX-ACCESS not-accessible 573 STATUS current 574 DESCRIPTION 575 "This variable uniquely identifies the power Ethernet PSE 576 port within group pethPseGroupIndex to which the 577 power Ethernet PSE entry is connected." 578 ::= { pethPsePortEntry 2 } 580 pethPsePortAdminEnable OBJECT-TYPE 581 SYNTAX INTEGER { 582 enable(1), 583 disable(2) 584 } 585 MAX-ACCESS read-write 586 STATUS current 587 DESCRIPTION 588 "Enables power supply on this port. 589 Setting this object at a value enable(1) enables power 590 and detection mechanism for this port. 591 Setting this object at a value disable(2) disables power 592 for this port." 593 ::= { pethPsePortEntry 3 } 595 pethPsePortPowerPairsControlAbility OBJECT-TYPE 596 SYNTAX TruthValue 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "Describes the capability of controlling the power pairs 601 functionality to switch pins for sourcing power. 602 The value true indicate that the device has the capability 603 to control the power pairs" 604 ::= { pethPsePortEntry 4 } 606 pethPsePortPowerPairs OBJECT-TYPE 607 SYNTAX INTEGER { 608 signal(1), 609 spare(2) 610 } 611 MAX-ACCESS read-write 612 STATUS current 613 DESCRIPTION 614 "Describes or controls the pairs in use. If the value of 615 pethPsePortPowerPairsControl is true, this object is 616 writable. 617 A value of signal(1) means that the signal pairs 618 only are in use. 619 A value of spare(2) means that the spare pairs 620 only are in use." 621 ::= { pethPsePortEntry 5 } 623 pethPsePortPowerDetectionControl OBJECT-TYPE 624 SYNTAX INTEGER { 625 auto(1), 626 test(2) 627 } 628 MAX-ACCESS read-write 629 STATUS current 630 DESCRIPTION 631 "Controls the power detection mechanism of the port. 632 Setting the value auto(1) enables the power detection 633 mechanism of the port. 634 Setting the value test(2) puts the port in a 635 testmode: force continuous discovery without applying 636 power regardless of whether PD detected." 637 ::= { pethPsePortEntry 6 } 639 pethPsePortDetectionStatus OBJECT-TYPE 640 SYNTAX INTEGER { 641 disabled(1), 642 searching(2), 643 deliveringPower(4), 644 fault(5), 645 test(7), 646 denyLowPriority(8) 647 } 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "Describes the operational status of the port PD detection. 652 A value of disabled(1)- indicates that the PSE State diagram is in 653 the state IDLE 654 A value of searching(2)- indicates that the PSE State diagram is in 655 the state DETECTION, CLASSIFICATION, SIGNATURE_INVALID or BACKOFF. 656 A value of deliveringPower(4) - indicates that the PSE State diagram 657 is in the state POWER_UP, POWER_ON or POWER_OFF. 658 A value of fault(5) - indicates that the PSE State diagram is in the 659 state TEST_ERROR or the state IDLE due to the variable error 660 condition. 661 Faults detected are vendor specific. 662 A value of test(7) - indicates that the PSE State diagram is in the 663 state TEST_MODE. 664 A value of denyLowPriority(8) indicates that the port was 665 disabled by the power management system, in order to keep 666 active higher priority ports. 667 " 668 ::= { pethPsePortEntry 7 } 670 pethPsePortPowerPriority OBJECT-TYPE 671 SYNTAX INTEGER { 672 critical(1), 673 high(2), 674 low(3) 675 } 676 MAX-ACCESS read-write 677 STATUS current 678 DESCRIPTION 679 "This object controls the priority of the port from the point 680 of view of a power management algorithm. The priority that 681 is set by this variable could be used by a control mechanism 682 that prevents over current situations by disconnecting first 683 ports with lower power priority. Ports that connect devices 684 critical to the operation of the network - like the E911 685 telephones ports - should be set to higher priority." 686 ::= { pethPsePortEntry 8 } 688 pethPsePortPowerMaintenanceStatus OBJECT-TYPE 689 SYNTAX INTEGER { 690 ok(1), 691 underCurrent(2), 692 mPSAbsent(3) 693 } 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "The value ok(1) indicates the Power Maintenance 698 Signature is present and the overcurrent condition has not been 699 detected. 700 The value overCurrent (2) indicates an overcurrent condition 701 has been detected. 702 The value mPSAbsent(3) indicates that the Power Maintenance 703 Signature is absent." 705 REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, 30.9.1.1.8 706 aPSEPowerMaintenanceStatus]" 707 ::= { pethPsePortEntry 10 } 709 pethPsePortMPSAbsentCounter OBJECT-TYPE 710 SYNTAX Counter32 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "Counts the number of times that the 715 pethPsePortPowerMaintenanceStatus attribute changes from any 716 value to the value mPSAbsent(3)." 717 REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, object 30.9.1.1.9 718 aPSEUnderCurrentCounter]" 719 ::= { pethPsePortEntry 11 } 721 pethPsePortOverCurrentCounter OBJECT-TYPE 722 SYNTAX Counter32 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "Counts the number of times that the aPSEPowerCurrentStatus 727 attribute changes from any value to the value overCurrent(2)." 728 REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, object 30.9.1.1.1 729 aPSEOverCurrentCounter]" 730 ::= { pethPsePortEntry 12 } 732 pethPsePortType OBJECT-TYPE 733 SYNTAX INTEGER { 734 other(1), 735 telephone(2), 736 webcam(3), 737 wireless(4) 738 } 739 MAX-ACCESS read-write 740 STATUS current 741 DESCRIPTION 742 "A manager will set the value of this variable to a value 743 that indicates the type of the device that is connected 744 to theport. This value can be the result of the mapping 745 the address of the station connected to the port and of 746 the value of the pethPdPortType of the respective PD port." 747 ::= { pethPsePortEntry 13 } 749 pethPsePortPowerClassifications OBJECT-TYPE 750 SYNTAX INTEGER { 751 class0(1), 752 class1(2), 753 class2(3), 754 class3(4), 755 class4(5) 756 } 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "Classification is a way to tag different terminals on the 761 Power over LAN network according to their power consumption. 762 Devices such as IP telephones, WLAN access points and others, 763 will be classified according to their power requirements. 765 The value is only valid while a valid PD is being detected as 766 indicated by the attribute pethPsePortDetectionStatus reporting 767 the value or deliveringPower(4)." 768 REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, 769 object 30.9.1.1.7 aPSEPowerClassification]" 770 ::= { pethPsePortEntry 14 } 772 -- PD Port table 774 pethPdPortTable OBJECT-TYPE 775 SYNTAX SEQUENCE OF PethPdPortEntry 776 MAX-ACCESS not-accessible 777 STATUS current 778 DESCRIPTION 779 "A table of objects that display and control the power 780 characteristics power Ethernet ports on a Powered 781 Device(PD) device. This group will be implemented in 782 managed powered and mid-span devices." 783 ::= { pethObjects 2 } 785 pethPdPortEntry OBJECT-TYPE 786 SYNTAX PethPdPortEntry 787 MAX-ACCESS not-accessible 788 STATUS current 789 DESCRIPTION 790 "A set of objects that display and control the power 791 characteristics of a Powered Device port." 792 INDEX { pethPdPortIndex } 793 ::= { pethPdPortTable 1 } 795 PethPdPortEntry ::= SEQUENCE { 796 pethPdPortIndex 797 InterfaceIndex, 798 pethPdPortAdminEnable 799 INTEGER 800 } 802 pethPdPortIndex OBJECT-TYPE 803 SYNTAX InterfaceIndex 804 MAX-ACCESS not-accessible 805 STATUS current 806 DESCRIPTION 807 "An index value that uniquely identifies an 808 interface to a PD device. The 809 interface identified by a particular value of 810 this index is the same interface as identified 811 by the same value of ifIndex. The mapping 812 between the ifIndex values and the numbering of 813 the port on the device is an implementation 814 issue." 815 ::= { pethPdPortEntry 1 } 817 pethPdPortAdminEnable OBJECT-TYPE 818 SYNTAX INTEGER { 819 enable(1), 820 disable(2) 821 } 822 MAX-ACCESS read-write 823 STATUS current 824 DESCRIPTION 825 "This value identifies the operational state of the PD functions. 826 An interface which can provide the PD functions will be enabled 827 to do so when this attribute has the value enable. When this 828 attribute has the value disable the interface will act 829 as it would if it had no PD function." 830 ::= { pethPdPortEntry 2 } 832 -- Main PSE Objects 834 pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } 836 pethMainPseTable OBJECT-TYPE 837 SYNTAX SEQUENCE OF PethMainPseEntry 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "A table of objects that display and control the Main power 842 on a PSE device. Example - an Ethernet switch midspan device can 843 control an Ethnternet port and the Main Power supply unit's." 844 ::= { pethMainPseObjects 1 } 846 pethMainPseEntry OBJECT-TYPE 847 SYNTAX PethMainPseEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "A set of objects that display and control the Main power 852 of a PSE. " 853 INDEX { pethMainPseGroupIndex } 854 ::= { pethMainPseTable 1 } 856 PethMainPseEntry ::= SEQUENCE { 857 pethMainPseGroupIndex 858 Integer32, 859 pethMainPsePower 860 Gauge32 , 861 pethMainPseOperStatus 862 INTEGER, 863 pethMainPseConsumptionPower 864 Gauge32, 865 pethMainPseUsageThreshold 866 Integer32 867 } 868 pethMainPseGroupIndex OBJECT-TYPE 869 SYNTAX Integer32 (1..2147483647) 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "This variable uniquely identifies the group to which 874 power Ethernet PSE is connected.Group means (box in the stack, 875 module in a rack) and the value 1 MUST be used for non-modular 876 devices " 877 ::= { pethMainPseEntry 1 } 879 pethMainPsePower OBJECT-TYPE 880 SYNTAX Gauge32 (1..65535) 881 UNITS "Watts" 882 MAX-ACCESS read-only 883 STATUS current 884 DESCRIPTION 885 "The nominal power of the PSE expressed in Watts." 886 ::= { pethMainPseEntry 2 } 888 pethMainPseOperStatus OBJECT-TYPE 889 SYNTAX INTEGER { 890 on(1), 891 off(2), 892 faulty(3) 893 } 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "The operational status of the main PSE." 898 ::= { pethMainPseEntry 3 } 900 pethMainPseConsumptionPower OBJECT-TYPE 901 SYNTAX Gauge32 902 UNITS "Watts" 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "Measured usage power expressed in Watts." 907 ::= { pethMainPseEntry 4 } 909 pethMainPseUsageThreshold OBJECT-TYPE 910 SYNTAX Integer32 (1..99) 911 UNITS "%" 912 MAX-ACCESS read-write 913 STATUS current 914 DESCRIPTION 915 "The usage threshold expressed in percents for 916 comparing the measured power and initiating 917 an alarm if the threshold is exceeded." 918 ::= { pethMainPseEntry 7 } 920 -- Notification Control Objects 922 pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } 924 pethNotificationControlTable OBJECT-TYPE 925 SYNTAX SEQUENCE OF PethNotificationControlEntry 926 MAX-ACCESS not-accessible 927 STATUS current 928 DESCRIPTION 929 "A table of objects that display and control the Notification 930 on a PSE device." 931 ::= { pethNotificationControl 1 } 933 pethNotificationControlEntry OBJECT-TYPE 934 SYNTAX PethNotificationControlEntry 935 MAX-ACCESS not-accessible 936 STATUS current 937 DESCRIPTION 938 "A set of objects that control the Notification events." 939 INDEX { pethNotificationControlGroupIndex } 940 ::= { pethNotificationControlTable 1 } 942 PethNotificationControlEntry ::= SEQUENCE { 943 pethNotificationControlGroupIndex 944 Integer32, 945 pethNotificationControlEnable 946 INTEGER 947 } 948 pethNotificationControlGroupIndex OBJECT-TYPE 949 SYNTAX Integer32 (1..2147483647) 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "This variable uniquely identifies the group. Group means 954 box in the stack, module in a rack and it is RECOMENDED 955 that the value 1 be used for non-modular devices " 956 ::= { pethNotificationControlEntry 1 } 958 pethNotificationControlEnable OBJECT-TYPE 959 SYNTAX INTEGER 960 { 961 enable(1), 962 disable(2) 963 } 964 MAX-ACCESS read-write 965 STATUS current 966 DESCRIPTION 967 "Enable Notification from Agent" 968 ::= { pethNotificationControlEntry 2 } 970 -- 971 -- Notifications Section 972 -- 973 -- 975 pethPsePortOnOffNotification NOTIFICATION-TYPE 976 OBJECTS { pethPsePortDetectionStatus } 977 STATUS current 978 DESCRIPTION 979 " This Notification indicates if Pse Port is delivering or 980 not power to the PD. This Notification SHOULD be sent on 981 every status change except in the searching mode." 982 ::= { pethNotifications 1 } 984 pethPsePortPowerMaintenanceStatusNotification NOTIFICATION-TYPE 985 OBJECTS { pethPsePortPowerMaintenanceStatus } 986 STATUS current 987 DESCRIPTION 988 " This Notification indicates a Port Change Status and it 989 SHOULD be sent on every status change." 990 ::= { pethNotifications 2 } 992 pethMainPowerUsageOnNotification NOTIFICATION-TYPE 993 OBJECTS { pethMainPseConsumptionPower } 994 STATUS current 995 DESCRIPTION 996 " This Notification indicate PSE Threshold usage indication is 997 on, the usage power is above the threshold." 998 ::= { pethNotifications 4 } 1000 pethMainPowerUsageOffNotification NOTIFICATION-TYPE 1001 OBJECTS { pethMainPseConsumptionPower } 1002 STATUS current 1003 DESCRIPTION 1004 " This Notification indicate PSE Threshold usage indication 1005 off, the usage power is below the threshold." 1006 ::= { pethNotifications 5 } 1008 -- 1009 -- Conformance Section 1010 -- 1011 pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } 1012 pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } 1014 pethCompliance MODULE-COMPLIANCE 1015 STATUS current 1016 DESCRIPTION 1017 "Describes the requirements for conformance to the 1018 Power Ethernet MIB." 1019 MODULE -- this module 1020 GROUP pethPsePortGroup 1021 DESCRIPTION 1022 "The pethPsePortGroup is mandatory for systems which 1023 implement PSE ports." 1024 GROUP pethPdPortGroup 1025 DESCRIPTION 1026 "The pethPdPortGroup is mandatory for systems which 1027 implement PD Ports." 1028 GROUP pethMainPseGroup 1029 DESCRIPTION 1030 "The pethMainPseGroup is mandatory for systems which 1031 implement main power supply within a PSE Device." 1032 GROUP pethNotificationControlGroup 1033 DESCRIPTION 1034 "The pethNotificationControlGroup is mandatory for systems which 1035 implement PSE ports." 1036 ::= { pethCompliances 1 } 1038 pethPseCompliance MODULE-COMPLIANCE 1039 STATUS current 1040 DESCRIPTION 1041 "Describes the requirements for conformance to the PSE and MID- 1042 Span." 1043 MODULE -- this module 1044 MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethNotificationControlGroup} 1045 ::= { pethCompliances 2 } 1047 pethPdCompliance MODULE-COMPLIANCE 1048 STATUS current 1049 DESCRIPTION 1050 "Describes the requirements for conformance to the PD." 1051 MODULE -- this module 1052 MANDATORY-GROUPS {pethPdPortGroup} 1053 ::= { pethCompliances 3} 1055 pethPsePortGroup OBJECT-GROUP 1056 OBJECTS { 1057 pethPsePortAdminEnable, 1058 pethPsePortPowerPairsControlAbility, 1059 pethPsePortPowerDetectionControl, 1060 pethPsePortPowerPairs, 1061 pethPsePortDetectionStatus, 1062 pethPsePortPowerPriority, 1063 pethPsePortPowerMaintenanceStatus , 1064 pethPsePortMPSAbsentCounter, 1065 pethPsePortOverCurrentCounter, 1066 pethPsePortType, 1067 pethPsePortPowerClassifications 1068 } 1069 STATUS current 1070 DESCRIPTION 1071 "The pethPsePortGroup is mandatory for systems which 1072 implement PSE ports." 1073 ::= { pethGroups 1 } 1075 pethPdPortGroup OBJECT-GROUP 1076 OBJECTS { 1077 pethPdPortAdminEnable 1078 } 1079 STATUS current 1080 DESCRIPTION 1081 "The pethPdPortGroup is mandatory for systems which 1082 implement PD Ports." 1083 ::= { pethGroups 2 } 1085 pethMainPseGroup OBJECT-GROUP 1086 OBJECTS { 1087 pethMainPsePower, 1088 pethMainPseOperStatus, 1089 pethMainPseConsumptionPower, 1090 pethMainPseUsageThreshold 1091 } 1092 STATUS current 1093 DESCRIPTION 1094 "Main PSE Objects. " 1095 ::= { pethGroups 3 } 1097 pethNotificationControlGroup OBJECT-GROUP 1098 OBJECTS { 1099 pethNotificationControlEnable 1100 } 1101 STATUS current 1102 DESCRIPTION 1103 "Notification Control Objects. " 1104 ::= { pethGroups 4 } 1106 pethPsePortNotificationGroup NOTIFICATION-GROUP 1107 NOTIFICATIONS { pethPsePortOnOffNotification, 1108 pethPsePortPowerMaintenanceStatusNotification} 1109 STATUS current 1110 DESCRIPTION "Pse Notification indications" 1111 ::= { pethCompliances 4 } 1113 pethMainPowerNotificationGroup NOTIFICATION-GROUP 1114 NOTIFICATIONS { pethMainPowerUsageOnNotification, 1115 pethMainPowerUsageOffNotification} 1116 STATUS current 1117 DESCRIPTION "Pse Notification indications" 1118 ::= { pethCompliances 5 } 1120 END 1122 8. Normative References 1124 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1125 for Describing SNMP Management Frameworks", RFC 2571, April 1126 1999. 1128 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1129 Rose, M., and S. Waldbusser, "Structure of Management 1130 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1131 1999. 1133 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1134 Rose, M., and S. Waldbusser, "Textual Conventions for 1135 SMIv2", STD 58, RFC 2579, April 1999. 1137 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1138 Rose, M., and S. Waldbusser, "Conformance Statements for 1139 SMIv2", STD 58, RFC 2580, April 1999. 1141 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1142 Processing and Dispatching for the Simple Network Management 1143 Protocol (SNMP)", RFC 2572, April 1999. 1145 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1146 (USM) for version 3 of the Simple Network Management 1147 Protocol (SNMPv3)", RFC 2574, April 1999. 1149 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1150 RFC 2573, April 1999. 1152 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1153 Access Control Model (VACM) for the Simple Network 1154 Management Protocol (SNMP)", RFC 2575, April 1999. 1156 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1157 "Introduction to Version 3 of the Internet-standard Network 1158 Management Framework", RFC 2570, April 1999. 1160 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1161 Requirement Levels", BCP 14, RFC 2119, March 1997. 1163 [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects 1164 for the Ethernet-like Interface Types", RFC 2665, August 1999. 1166 [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE) 1167 Power via Media Dependent Interface (MDI)", Draft D4.0, 1168 December 2002. 1170 9. Informative References 1172 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1173 of Management Information for TCP/IP-based Internets", STD 1174 16, RFC 1155, May 1990. 1176 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1177 16, RFC 1212, March 1991. 1179 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1180 SNMP", RFC 1215, March 1991. 1182 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1183 Network Management Protocol", STD 15, RFC 1157, May 1990. 1185 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1186 "Introduction to Community-based SNMPv2", RFC 1901, January 1187 1996. 1189 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1190 "Transport Mappings for Version 2 of the Simple Network 1191 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1193 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1194 "Protocol Operations for Version 2 of the Simple Network 1195 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1197 [PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", 1198 Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, 1199 June 2002. 1201 10.Intellectual Property 1203 The IETF takes no position regarding the validity or scope of any 1204 intellectual property or other rights that might be claimed to 1205 pertain to the implementation or use of the technology described in 1206 this document or the extent to which any license under such rights 1207 might or might not be available; neither does it represent that it 1208 has made any effort to identify any such rights. Information on the 1209 IETF's procedures with respect to rights in standards-track and 1210 standards-related documentation can be found in BCP-11. Copies of 1211 claims of rights made available for publication and any assurances of 1212 licenses to be made available, or the result of an attempt made to 1213 obtain a general license or permission for the use of such 1214 proprietary rights by implementors or users of this specification can 1215 be obtained from the IETF Secretariat. 1217 The IETF invites any interested party to bring to its attention any 1218 copyrights, patents or patent applications, or other proprietary 1219 rights which may cover technology that may be required to practice 1220 this standard. Please address the information to the IETF Executive 1221 Director. 1223 11. Security Considerations 1225 There are a number of management objects defined in this MIB 1226 that have a MAX-ACCESS clause of read-write and/or read-create. 1227 Such objects may be considered sensitive or vulnerable in some 1228 network environments. The support for SET operations in a 1229 non-secure environment without proper protection can have a 1230 negative effect on network operations. 1232 There are a number of managed objects in this MIB that may 1233 contain sensitive information. These are: 1235 pethPsePortPowerPairsControlAbility 1236 pethPsePortPowerPriority 1237 pethPsePortPowerClassifications 1239 It is thus important to control even GET access to these objects 1240 and possibly to even encrypt the values of these object when 1241 sending them over the network via SNMP. Not all versions of 1242 SNMP provide features for such a secure environment. 1244 SNMPv1 by itself is not a secure environment. Even if the 1245 network itself is secure (for example by using IPSec), even then, 1246 there is no control as to who on the secure network is allowed 1247 to access and GET/SET (read/change/create/delete) the objects in 1248 this MIB. 1250 It is RECOMMENDED that the implementers consider the security 1251 features as provided by the SNMPv3 framework. Specifically, the 1252 use of the User-based Security Model [RFC2274] and the 1253 View-based Access Control Model [RFC2275] is RECOMMENDED. 1255 It is then a customer/user responsibility to ensure that the SNMP 1256 entity giving access to an instance of this MIB, is properly 1257 configured to give access to the objects only to those 1258 principals (users) that have legitimate rights to indeed GET or 1259 SET (change/create/delete) them. 1261 12. Authors Addresses 1263 Avi Berger 1264 PowerDsine Inc. 1266 1, Hanagar St., P.O. Box 7220 1267 Hod Hasharon 45421, 1268 Israel 1269 Tel: +972-9-7755100 Ext 307 1270 Fax: +972-9-7755120 1271 E-mail: avib@PowerDsine.com 1273 Dan Romascanu 1274 Avaya Inc. 1275 Atidim Technology Park, Bldg. #3 1276 Tel Aviv, 61131 1277 Israel 1278 Tel: +972-3-645-8414 1279 Email: dromasca@avaya.com 1281 A. Full Copyright Statement 1283 This document and translations of it may be copied and furnished to 1284 others, and derivative works that comment on or otherwise explain it 1285 or assist in its implementation may be prepared, copied, published 1286 and distributed, in whole or in part, without restriction of any 1287 kind, provided that the above copyright notice and this paragraph are 1288 included on all such copies and derivative works. However, this 1289 document itself may not be modified in any way, such as by removing 1290 the copyright notice or references to the Internet Society or other 1291 Internet organizations, except as needed for the purpose of 1292 developing Internet standards in which case the procedures for 1293 copyrights defined in the Internet Standards process must be 1294 followed, or as required to translate it into languages other than 1295 English. 1297 The limited permissions granted above are perpetual and will not be 1298 revoked by the Internet Society or its successors or assigns. 1300 This document and the information contained herein is provided on an 1301 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1302 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1303 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1304 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1305 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.