idnits 2.17.1 draft-ietf-hubmib-power-ethernet-mib-02.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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 49 instances of too long lines in the document, the longest one being 40 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 168 has weird spacing: '...o allow for t...' == Line 305 has weird spacing: '...CESS to read-...' == Line 449 has weird spacing: '...MUST be used ...' == Line 484 has weird spacing: '...hat the devic...' == Line 812 has weird spacing: '...ck) and the v...' == (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 (30 June 2002) is 7964 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 70, but not defined == Missing Reference: 'RFC2274' is mentioned on line 1224, but not defined ** Obsolete undefined reference: RFC 2274 (Obsoleted by RFC 2574) == Missing Reference: 'RFC2275' is mentioned on line 1225, but not defined ** Obsolete undefined reference: RFC 2275 (Obsoleted by RFC 2575) == Unused Reference: 'RFC2119' is defined on line 1163, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** 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' -- Possible downref: Normative reference to a draft: ref. 'PWR-MIB' Summary: 24 errors (**), 0 flaws (~~), 15 warnings (==), 4 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 30 June 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 7 53 8 References 24 54 9 Intellectual Property 26 55 10 Security Considerations 26 56 11 Authors Addresses 27 57 A Full Copyright Statement 27 59 1. Introduction 61 This memo defines a portion of the Management Information Base (MIB) 62 for use with network management protocols in the Internet community. 63 In particular, it defines a set of MIB objects to manage a Power 64 Ethernet (DTE Power via MDI)Powered Device (PD) and/or power Source 65 Equipment (PSE). 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 69 document are to be interpreted as described in [RFC2863]. 71 2. The SNMP Management Framework 73 The SNMP Management Framework presently consists of five major 74 components: 76 o An overall architecture, described in RFC 2571 [RFC2571]. 78 o Mechanisms for describing and naming objects and events for the 79 purpose of management. The first version of this Structure of 80 Management Information (SMI) is called SMIv1 and described in 81 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 82 1215 [RFC1215]. The second version, called SMIv2, is described 83 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 84 STD 58, RFC 2580 [RFC2580]. 86 o Message protocols for transferring management information. The 87 first version of the SNMP message protocol is called SNMPv1 and 88 described in STD 15, RFC 1157 [RFC1157]. A second version of 89 the SNMP message protocol, which is not an Internet standards 90 track protocol, is called SNMPv2c and described in RFC 1901 91 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 92 message protocol is called SNMPv3 and described in RFC 1906 93 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 95 o Protocol operations for accessing management information. The 96 first set of protocol operations and associated PDU formats is 97 described in STD 15, RFC 1157 [RFC1157]. A second set of 98 protocol operations and associated PDU formats is described in 99 RFC 1905 [RFC1905]. 101 o A set of fundamental applications described in RFC 2573 102 [RFC2573] and the view-based access control mechanism described 103 in RFC 2575 [RFC2575]. 105 A more detailed introduction to the current SNMP Management Framework 106 can be found in RFC 2570 [RFC2570]. 108 Managed objects are accessed via a virtual information store, termed 109 the Management Information Base or MIB. Objects in the MIB are 110 defined using the mechanisms defined in the SMI. 112 This memo specifies a MIB module that is compliant to the SMIv2. A 113 MIB conforming to the SMIv1 can be produced through the appropriate 114 translations. The resulting translated MIB must be semantically 115 equivalent, except where objects or events are omitted because no 116 translation is possible (use of Counter64). Some machine readable 117 information in SMIv2 will be converted into textual descriptions in 118 SMIv1 during the translation process. However, this loss of machine 119 readable information is not considered to change the semantics of the 120 MIB. 122 3. Overview 124 The emergence of IP telephony as an application that allows for voice 125 applications to be run over the same infrastructure as data 126 applications led to the emergence of Ethernet IP phones, with similar 127 functions and characteristics as the traditional phones. Powering a 128 phone is one of these functions that are being taken as granted. The 129 IEEE 802.3 Working Group initiated a standard work on this subject, 130 currently known as the IEEE 802.3af work [IEEE-802.3af]. 132 The IEEE 802.3af WG will not define a full management interface, but 133 only the hardware registers that will allow for a management 134 interfaces to be built for a powered Ethernet device. The MIB module 135 defined in this document extends the Ethernet-like Interfaces MIB 136 [RFC2665] with the management objects required for the management of 137 the powered Ethernet devices and ports. 139 The following abbreviations are defined in [IEEE-802.3af] and will be 140 used with the same significance in this document: PSE - Power 141 Sourcing Equipment; PD - Powered Device 143 4. MIB Structure 145 This MIB objects are included in four MIB groups - three of them 146 include MIB tables, and the fourth scalar objects 148 The pethPsePortTable defines the objects used for the configuration 149 and describing the status of ports on a PSE device. Examples of PSE 150 devices are Ethernet switches that support power Ethernet and mid- 151 span boxes. 153 The pethPdPortTable defines the objects used for the configuration 154 and describing the status of ports on a PD device. Examples of PD 155 devices are Ethernet phones. 157 The pethMainPseObjects MIB group defines the management objects for a 158 managed main power source in a PSE device. Ethernet switches are one 159 example of boxes that would support these objects. 161 The pethTrapsControlTable includes objects that control the 162 transmission of traps by the agent to a management application. 164 5. Evolution of the Document, Limitations and Future Work 166 The IEEE 802.3af is at this stage work in progress. The scope of this 167 document is to do the standards work in the IETF in parallel with the 168 IEEE standardization activity, in order to allow for the publication 169 of a standard track document containing an SNMP MIB simultaneously 170 or close to the date of the publication of the IEEE revised standard. 171 It is possible that changes may be brought to the IEEE proposal, and 172 the Ethernet MIB Working Group will work in order to ensure 173 consistency between the two standards proposals. 175 6. Changes Log 177 The following changes were introduced relative to the first proposal 178 for a Power Ethernet MIB [PWR-MIB] 180 a. pethPsePortTable has to index pethPsePortGroupIndex & 181 pethPsePortIndex 183 b. pethPsePortIndex INTEGER instead of InterfaceIndex 185 c. Name change pethPsePortStatus insted of pethPsePortFaultError 187 d. Name change pethPsePortStatusClear instead of 188 pethPsePortFaultErrorClear 190 e. DESCRIPTION update for pethPsePortPowerDetectionStatus test(3) 191 f. DESCRIPTION update pethPsePortDetectionOperStatus off(2) 193 g. Adding to pethPsePortStatus one more item both(4) 195 h. Adding pethMainPseTable with a pethMainPseGroupIndex 197 i. Deletting to objects pethMainPseMaxVoltage & pethMainPseMinVoltage 199 j. Change SYNTAX of pethMainPseUsagePower form INTEGER to Gauge32 201 k. Change SYNTAX of pethMainPseUsageCurrent form INTEGER to Gauge32 203 l. Adding pethMainPseBackupActivated & pethMainPseBackupPresent 205 m. Adding Traps Control Objects 207 n. Adding Notifications Section (5 notifications ) 209 o. Adding pethTrapsControlGroup to Conformance Section 211 p. Adding pethPsePortPowerClassifications to pethPsePortTable Class 212 1-5 214 q. Adding pethPsePortPowerClassifications to pethPsePortGroup 216 r. Change in pethPsePortStatus none(1) to ok(1) 218 s. Change in DESCRIPTION of pethMainPseUsagePower from mW to Watt 220 t. Change pethMainPseUsagePower to pethMainPseConsumptionPower 222 u. Delete of pethMainPseUsageCurrent 224 The following changes were introduced between draft-ietf-hubmib- 225 power-ethernet-mib-00.txt and draft-ietf-hubmib-power-ethernet- 226 mib-01.txt: 228 1. change pethMainPowerUsageTrap to pethMainPowerUsageOnTrap 230 2. add pethMainPowerUsageOffTrap 232 3. change pethMainPowerTrapGroup 234 4. change pethPsePorPowerEnable to pethPsePortAdminEnable 236 5. pethPsePortPowerIdPairsControl to 237 pethPsePortPowerPairsControlAbility 238 6. pethPsePortPowerIdPairs to pethPsePortPowerPairs 240 7. delete both from pethPsePortPowerPairs object 242 8. change pethPsePortPowerDetectionStatus to 243 pethPsePortPowerDetectionControl 245 9. delete from pethPsePortPowerDetectionControl off , and change test 246 to 2 248 10. change pethPsePortDetectionOperStatus to 249 pethPsePortDetectionStatus 251 11. change pethPsePortDetectionStatus to: 252 disabled(1), 253 searching(2), 254 detected(3), 255 deliveringPower(4), 256 fault(5), 257 invalidPD(6), 258 test(7), 259 denyLowPriority(8) 261 12. change description for pethPsePortPowerClassifications 263 13. change pethPsePortStatus to pethPsePortCurrentStatus 265 14. Update description for pethPsePortCurrentStatus 267 15. change pethPsePortStatusClear to pethPsePortCurrentStatusClear 269 16. change pethPdPortDetectionOperStatus to pethPdPortDetectionStatus 271 17. change in description of pethPdPortPowerPairs 273 18. change in pethPdPortDetectionStatus description 275 19. delete pethPdPortPowerClassifications object 277 20. change in pethPsePortGroup 279 21. change in pethPdPortGroup 281 22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus 282 object 284 23. change pethPsePortStatusTrap to pethPsePortCurrentStatusTrap 285 24. change pethPsePortTrapGroup 287 The following changes were introduced between draft-ietf-hubmib- 288 power-ethernet-mib-01.txt and draft-ietf-hubmib-power-ethernet- 289 mib-02.txt: 291 1. change pethMainPsePower SYNTAX Integer32 (0..65535) to (1..65535) 293 2. change pethTrapsControlGroupIndex SYNTAX Integer32 (0..65535) to 294 (1..65535) 296 3. change int pethMainPseBackUpActivatedTrap pethPsePortGroupIndex to 297 pethMainPseGroupIndex 299 4. change int pethMainPowerUsageOnTrap pethPsePortGroupIndex to 300 pethMainPseGroupIndex 302 5. change int pethMainPowerUsageOffTrap pethPsePortGroupIndex to 303 pethMainPseGroupIndex 305 6. change pethMainPseGroupIndex MAX-ACCESS to read-only 307 updates from IEEE Draft P802.3af/D3.1, June 5, 2002 309 7. remove from pethPsePortPowerClassifications class5 311 8. remove from pethPsePortCurrentStatus both(4) and description 313 9. add pethPsePortUnderCurrentCounter object 315 10. add pethPsePortOverCurrentCounter object 317 11. remove pethPsePortCurrentStatusClear object 319 12. change pethPsePortType OID to end with 13 321 13. change pethPsePortPowerClassifications OID to end with 14 323 14. update pethPsePortGroup OBJECT-GROUP 325 15. chage reference to new IEEE Draft 327 16. change pethPdCompliance description. 329 7. Definitions 330 POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN 332 IMPORTS 333 MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,Counter32 ,NOTIFICATION-TYPE 334 FROM SNMPv2-SMI 335 dot3 336 FROM EtherLike-MIB 337 TruthValue 338 FROM SNMPv2-TC 339 MODULE-COMPLIANCE, OBJECT-GROUP ,NOTIFICATION-GROUP 340 FROM SNMPv2-CONF; 342 powerEthernetMIB MODULE-IDENTITY 343 LAST-UPDATED "200206260000Z" -- June 26, 2002 344 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 345 Working Group" 346 CONTACT-INFO 347 " 349 Chair: Dan Romascanu 350 Avaya Inc. 351 Tel: +972-3-645-8414 352 Email: dromasca@avaya.com 354 Editor: Avi Berger 355 PowerDsine Inc. 356 Tel: 972-9-7755100 Ext 307 357 Fax: 972-9-7755120 358 E-mail: avib@PowerDsine.com 359 " 361 DESCRIPTION 362 "The MIB module for for managing Powered Devices (PD) or 363 Power Source Equipment (PSE) working according to the IEEE 364 802.af Powere Ethernet (DTE Power via MDI) standard. 366 The following terms are used throughout this 367 MIB module. For complete formal definitions, 368 the IEEE 802.3 standards should be consulted 369 wherever possible: 371 Group - A recommended, but optional, entity 372 defined by the IEEE 802.3 management standard, 373 in order to support a modular numbering scheme. 374 The classical example allows an implementor to 375 represent field-replaceable units as groups of 376 ports, with the port numbering matching the 377 modular hardware implementation. 379 Port - This entity identifies the port within the group 380 for which this entry contains information.The numbering 381 scheme for ports is implementation specific. 382 " 383 ::= { dot3 20 } 385 pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } 386 pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } 387 pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 3 } 389 -- PSE Objects 391 pethPsePortTable OBJECT-TYPE 392 SYNTAX SEQUENCE OF PethPsePortEntry 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "A table of objects that display and control the power 397 characteristics power Ethernet ports on a Power Source 398 Entity (PSE) device. This group will be implemented in 399 managed power Ethernet switches and mid-span devices." 400 ::= { pethObjects 1 } 402 pethPsePortEntry OBJECT-TYPE 403 SYNTAX PethPsePortEntry 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "A set of objects that display and control the power 408 characteristics of a power Ethernet PSE port." 409 INDEX { pethPsePortGroupIndex , pethPsePortIndex } 410 ::= { pethPsePortTable 1 } 412 PethPsePortEntry ::= SEQUENCE { 413 pethPsePortGroupIndex 414 INTEGER, 415 pethPsePortIndex 416 INTEGER, 417 pethPsePortAdminEnable 418 INTEGER, 419 pethPsePortPowerPairsControlAbility 420 TruthValue, 421 pethPsePortPowerPairs 422 INTEGER, 423 pethPsePortPowerDetectionControl 424 INTEGER, 425 pethPsePortDetectionStatus 426 INTEGER, 427 pethPsePortPowerPriority 428 INTEGER, 429 pethPsePortCurrentStatus 430 INTEGER, 431 pethPsePortUnderCurrentCounter 432 Counter32, 433 pethPsePortOverCurrentCounter 434 Counter32, 435 pethPsePortType 436 INTEGER, 437 pethPsePortPowerClassifications 438 INTEGER 439 } 441 pethPsePortGroupIndex OBJECT-TYPE 442 SYNTAX INTEGER (1..2147483647) 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "This variable uniquely identifies the group 447 containing the port to which power Ethernet PSE is connected. 448 Group means (box in the stack, module in a rack) and the value 1 449 MUST be used for non-modular devices." 450 ::= { pethPsePortEntry 1 } 452 pethPsePortIndex OBJECT-TYPE 453 SYNTAX INTEGER(1..2147483647) 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "This variable uniquely identifies the power Ethernet PSE 458 port within group pethPseGroupIndex to which the 459 power Ethernet PSE entry is connected." 460 ::= { pethPsePortEntry 2 } 462 pethPsePortAdminEnable OBJECT-TYPE 463 SYNTAX INTEGER { 464 enable(1), 465 disable(2) 466 } 467 MAX-ACCESS read-write 468 STATUS current 469 DESCRIPTION 470 "Enables power supply on this port. 471 Setting this object at a value enable(1) enables power 472 and detection mechanism for this port. 473 Setting this object at a value disable(2) disables power 474 for this port." 475 ::= { pethPsePortEntry 3 } 477 pethPsePortPowerPairsControlAbility OBJECT-TYPE 478 SYNTAX TruthValue 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "Describes the capability of controlling the power pairs 483 functionality to switch pins for sourcing power. 484 The value true indicate that the device has the capability 485 to control the power pairs" 486 ::= { pethPsePortEntry 4 } 488 pethPsePortPowerPairs OBJECT-TYPE 489 SYNTAX INTEGER { 490 signal(1), 491 spare(2) 492 } 493 MAX-ACCESS read-write 494 STATUS current 495 DESCRIPTION 496 "Describes or controls the pairs in use. If the value of 497 pethPsePortPowerPairsControl is true, this object is 498 writable. 499 A value of signal(1) menas that the signal pairs 500 only are in use. 501 A value of spare(2) means that the spare pairs 502 only are in use." 503 ::= { pethPsePortEntry 5 } 505 pethPsePortPowerDetectionControl OBJECT-TYPE 506 SYNTAX INTEGER { 507 auto(1), 508 test(2) 509 } 510 MAX-ACCESS read-write 511 STATUS current 512 DESCRIPTION 513 "Controls the power detection mechanism of the port. 514 Setting the value auto(1) enables the power detection 515 mechanism of the port. 516 Setting the value test(2) puts the port in a 517 testmode: force continuous discovery without applying 518 power regardless of whether PD detected." 519 ::= { pethPsePortEntry 6 } 521 pethPsePortDetectionStatus OBJECT-TYPE 522 SYNTAX INTEGER { 523 disabled(1), 524 searching(2), 525 detected(3), 526 deliveringPower(4), 527 fault(5), 528 invalidPD(6), 529 test(7), 530 denyLowPriority(8) 531 } 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "Describes the operational status of the port PD detection. 536 A value of disabled(1) indicates that the PD Detection function 537 has been disabled. 538 A value of searching(2) indicates that the PD Detection function 539 is enabled and is searching for a valid PD. 540 A value of detected(3)indicates that the PD Detection function 541 has detected a valid PD but the PSE is not supplying power. 542 A value of deliveringPower(4) indicates that the port 543 executed the detection algorithm, found a PD connection 544 and is currently delivering power. 545 A value of fault(5) indicates that a fault was detected 546 on the port , faults detected are vendor-specific. 547 A value of invalidPD(6)indicates that the PD Detection function 548 has detected an invalid PD. 549 A value of test(7)indicates that the PD Detection function has 550 been placed in test mode. 551 A value of denyLowPriority(8) indicates that the port was 552 disabled by the power management system, in order to keep 553 active higher priority ports. 554 " 555 ::= { pethPsePortEntry 7 } 557 pethPsePortPowerPriority OBJECT-TYPE 558 SYNTAX INTEGER { 559 critical(1), 560 high(2), 561 low(3) 562 } 563 MAX-ACCESS read-write 564 STATUS current 565 DESCRIPTION 566 "This object controls the priority of the port from the point 567 of view of a power management algorithm. The priority that 568 is set by this variable could be used by a control mechanism 569 that prevents over current situations by disconnecting first 570 ports with lower power priority. Ports that connect devices 571 critical to the operation of the network - like the E911 572 telephones ports - should be set to higher priority." 573 ::= { pethPsePortEntry 8 } 575 pethPsePortCurrentStatus OBJECT-TYPE 576 SYNTAX INTEGER { 577 ok(1), 578 underCurrent(2), 579 overCurrent(3) 580 } 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "Describes a current port status related to the power generation 585 The value ok(1) indicates neither an undercurrent or an 586 overcurrent condition has been 587 detected since the attribute was last cleared. 588 The value underCurrent(2) indicates that the port current 589 is below the minimal value since the attribute was last cleared. 590 The value overCurrent(3) indicates that the port current 591 exceeds the maximal value since the attribute was last cleared. " 593 REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.8 aPSEPowerCurrentStatus]" 594 ::= { pethPsePortEntry 10 } 596 pethPsePortUnderCurrentCounter OBJECT-TYPE 597 SYNTAX Counter32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Counts the number of times that the pethPsePortCurrentStatus 602 attribute changes from any 603 enumeration to the enumeration underCurrent ." 605 REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.9 aPSEUnderCurrentCounter]" 606 ::= { pethPsePortEntry 11 } 608 pethPsePortOverCurrentCounter OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "Counts the number of times that the aPSEPowerCurrentStatus 614 attribute changes from any 615 enumeration to the enumeration overCurrent ." 616 REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.10 aPSEOverCurrentCounter]" 617 ::= { pethPsePortEntry 12 } 619 pethPsePortType OBJECT-TYPE 620 SYNTAX INTEGER { 621 other(1), 622 telephone(2), 623 webcam(3), 624 wireless(4) 625 } 626 MAX-ACCESS read-write 627 STATUS current 628 DESCRIPTION 629 "A manager will set the value of this variable to a value 630 that indicates the type of the device that is connected 631 to theport. This value can be the result of the mapping 632 the address of the station connected to the port and of 633 the value of the pethPdPortType of the respective PD port." 634 ::= { pethPsePortEntry 13 } 636 pethPsePortPowerClassifications OBJECT-TYPE 637 SYNTAX INTEGER { 638 class0(1), 639 class1(2), 640 class2(3), 641 class3(4), 642 class4(5) 643 } 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "Classification is a way to tag different terminals on the 648 Power over LAN network according to their power consumption. 649 Devices such as IP telephones, WLAN access points and others, 650 will be classified according to their power requirements. 652 The value is only valid while a valid PD is being detected 653 as indicated by the attribute 654 pethPsePortDetectionStatus reporting the enumeration 655 (detected) or (deliveringPower). 656 " 657 REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.7 aPSEPowerClassification]" 659 ::= { pethPsePortEntry 14 } 661 -- PD Port table 663 pethPdPortTable OBJECT-TYPE 664 SYNTAX SEQUENCE OF PethPdPortEntry 665 MAX-ACCESS not-accessible 666 STATUS current 667 DESCRIPTION 668 "A table of objects that display and control the power 669 characteristics power Ethernet ports on a Powered 670 Device(PD) device. This group will be implemented in 671 managed powered and mid-span devices." 672 ::= { pethObjects 2 } 674 pethPdPortEntry OBJECT-TYPE 675 SYNTAX PethPdPortEntry 676 MAX-ACCESS not-accessible 677 STATUS current 678 DESCRIPTION 679 "A set of objects that display and control the power 680 characteristics of a Powered Device port." 681 INDEX { pethPdPortIndex } 682 ::= { pethPdPortTable 1 } 684 PethPdPortEntry ::= SEQUENCE { 685 pethPdPortIndex 686 INTEGER, 687 pethPdPortPowerPairs 688 INTEGER, 689 pethPdPortDetectionStatus 690 INTEGER, 691 pethPdPortType 692 INTEGER 693 } 695 pethPdPortIndex OBJECT-TYPE 696 SYNTAX INTEGER (0..65535) 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "An index value that uniquely identifies an 701 interface to a PD device. The 702 interface identified by a particular value of 703 this index is the same interface as identified 704 by the same value of ifIndex. The mapping 705 between the ifIndex values and the numbering of 706 the port on the device is an implementation 707 issue." 708 ::= { pethPdPortEntry 1 } 710 pethPdPortPowerPairs OBJECT-TYPE 711 SYNTAX INTEGER { 712 signal(1), 713 spare(2), 714 both(3) 715 } 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "Describes the pairs in use by the PD to derive power. 720 A value of signal(1) indicates that only PD Pinout Mode A is 721 supported by the PD. 722 A value of spare(2) indicates that only PD Pinout Mode B is 723 supported by the PD. 724 A value of both(3) means indicates that both PD Pinout Mode A 725 and PD Pinout Mode B are supported by the PD." 726 ::= { pethPdPortEntry 2 } 728 pethPdPortDetectionStatus OBJECT-TYPE 729 SYNTAX INTEGER { 730 off(1), 731 receivingPower(2) 732 } 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "Describes the operational status of the port detection. 737 The value off(1) indicates that the PD is drawing a current less 738 than I Port as specified in [IEEE-802.3af] 739 The value receivingPower(2) indicates that the PD is drawing a 740 current greater I Port as specified in [IEEE-802.3af] 741 " 742 REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.2.1.2 aPDPowerStatus]" 743 ::= { pethPdPortEntry 3 } 745 pethPdPortType OBJECT-TYPE 746 SYNTAX INTEGER { 747 other(1), 748 telephone(2), 749 webcam(3), 750 wireless(4) 751 } 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The type of the device. A management application may read 756 the value of this variable and use it for setting the 757 corresponding value of pethPsePortType of the port that 758 connects the device." 759 ::= { pethPdPortEntry 4 } 761 -- Main PSE Objects 763 pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } 765 pethMainPseTable OBJECT-TYPE 766 SYNTAX SEQUENCE OF PethMainPseEntry 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "A table of objects that display and control the Main power 771 on a PSE device. Example internet switch midspan 772 device can control an 773 Ethernet port and the Main Power supply unit's." 774 ::= { pethMainPseObjects 1 } 776 pethMainPseEntry OBJECT-TYPE 777 SYNTAX PethMainPseEntry 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "A set of objects that display and control the Main power 782 of a PSE. " 783 INDEX { pethMainPseGroupIndex } 784 ::= { pethMainPseTable 1 } 786 PethMainPseEntry ::= SEQUENCE { 787 pethMainPseGroupIndex 788 INTEGER, 789 pethMainPsePower 790 Integer32, 791 pethMainPseOperStatus 792 INTEGER, 793 pethMainPseConsumptionPower 794 Gauge32, 795 pethMainPseBackupPresent 796 INTEGER, 797 pethMainPseBackupActivated 798 TruthValue, 799 pethMainPseUsageThreshold 800 INTEGER, 802 pethMainPseMaximumDcPower 803 INTEGER 804 } 805 pethMainPseGroupIndex OBJECT-TYPE 806 SYNTAX INTEGER (0..65535) 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "This variable uniquely identifies the group to which 811 power Ethernet PSE is connected.Group means (box in the stack, 812 module in a rack) and the value 1 MUST be used for 813 non-modular devices " 814 ::= { pethMainPseEntry 1 } 816 pethMainPsePower OBJECT-TYPE 817 SYNTAX Integer32 (1..65535) 818 UNITS "Watts" 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "The nominal power of the PSE expressed in Watts." 823 ::= { pethMainPseEntry 2 } 825 pethMainPseOperStatus OBJECT-TYPE 826 SYNTAX INTEGER { 827 on(1), 828 off(2), 829 faulty(3) 830 } 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "The operational status of the main PSE." 835 ::= { pethMainPseEntry 3 } 837 pethMainPseConsumptionPower OBJECT-TYPE 838 SYNTAX Gauge32 839 UNITS "Watts" 840 MAX-ACCESS read-only 841 STATUS current 842 DESCRIPTION 843 "Measured usage power expressed in Watts." 844 ::= { pethMainPseEntry 4 } 846 pethMainPseBackupPresent OBJECT-TYPE 847 SYNTAX INTEGER { 848 present(1), 849 notPresent(2), 850 faulty(3) 851 } 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "reflects the presence of a backup PSE ." 856 ::= { pethMainPseEntry 5 } 858 pethMainPseBackupActivated OBJECT-TYPE 859 SYNTAX TruthValue 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "Reflects the activation status of the backup PSE . 864 The value true Backup is activated." 865 ::= { pethMainPseEntry 6 } 867 pethMainPseUsageThreshold OBJECT-TYPE 868 SYNTAX INTEGER (1..99) 869 UNITS "%" 870 MAX-ACCESS read-write 871 STATUS current 872 DESCRIPTION 873 "The usage threshold expressed in percens for 874 comparing the measured power and initiating 875 an alarm if the threshold is exceeded." 876 ::= { pethMainPseEntry 7 } 878 pethMainPseMaximumDcPower OBJECT-TYPE 879 SYNTAX INTEGER 880 UNITS "Watts" 881 MAX-ACCESS read-write 882 STATUS current 883 DESCRIPTION 884 "describes the maximum available power in 885 Watt to be supplied by the DC backup source to this 886 device." 887 ::= { pethMainPseEntry 8 } 889 -- Traps Control Objects 891 pethTrapsControl OBJECT IDENTIFIER ::= { pethObjects 4 } 893 pethTrapsControlTable OBJECT-TYPE 894 SYNTAX SEQUENCE OF PethTrapsControlEntry 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "A table of objects that display and control the Traps 899 on a PSE device." 900 ::= { pethTrapsControl 1 } 902 pethTrapsControlEntry OBJECT-TYPE 903 SYNTAX PethTrapsControlEntry 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 "A set of objects that control the Trap events." 908 INDEX { pethTrapsControlGroupIndex } 909 ::= { pethTrapsControlTable 1 } 911 PethTrapsControlEntry ::= SEQUENCE { 912 pethTrapsControlGroupIndex 913 INTEGER, 914 pethTrapsControlEnable 915 INTEGER 916 } 917 pethTrapsControlGroupIndex OBJECT-TYPE 918 SYNTAX INTEGER (1..65535) 919 MAX-ACCESS not-accessible 920 STATUS current 921 DESCRIPTION 922 "This variable uniquely identifies the group.Group means 923 (box in the stack, module in a rack) and recommend 924 that the value 1 MUST be used for non-modular devices " 925 ::= { pethTrapsControlEntry 1 } 927 pethTrapsControlEnable OBJECT-TYPE 928 SYNTAX INTEGER 929 { 930 enable(1), 931 disable(2) 932 } 933 MAX-ACCESS read-write 934 STATUS current 935 DESCRIPTION 936 "Enable Traps from Agent" 937 ::= { pethTrapsControlEntry 2 } 939 -- 940 -- Notifications Section 941 -- 942 -- 944 pethPsePortOnOffTrap NOTIFICATION-TYPE 945 OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionStatus } 946 STATUS current 947 DESCRIPTION " This trap indicate if Pse Port is delivering 948 or not power to the PD." 949 ::= { pethNotifications 1 } 951 pethPsePortCurrentStatusTrap NOTIFICATION-TYPE 952 OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortCurrentStatus } 953 STATUS current 954 DESCRIPTION 955 " This trap indicate Port Change Status and 956 it will be sent on every status change." 957 ::= { pethNotifications 2 } 959 pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE 960 OBJECTS { pethMainPseGroupIndex,pethMainPseBackupActivated } 961 STATUS current 962 DESCRIPTION 963 " This trap indicate BackUp is Activated or 964 BackUp is released." 965 ::= { pethNotifications 3 } 967 pethMainPowerUsageOnTrap NOTIFICATION-TYPE 968 OBJECTS { pethMainPseGroupIndex } 969 STATUS current 970 DESCRIPTION 971 " This trap indicate PSE Threshold usage indication is on, 972 the usage power is above the threshold." 973 ::= { pethNotifications 4 } 975 pethMainPowerUsageOffTrap NOTIFICATION-TYPE 976 OBJECTS { pethMainPseGroupIndex } 977 STATUS current 978 DESCRIPTION 979 " This trap indicate PSE Threshold usage indication off, 980 the usage power is below the threshold.." 981 ::= { pethNotifications 5 } 983 pethPsePortTrapGroup NOTIFICATION-GROUP 984 NOTIFICATIONS { pethPsePortOnOffTrap, pethPsePortCurrentStatusTrap} 985 STATUS current 986 DESCRIPTION "Pse trap indications" 987 ::= { pethNotifications 6 } 989 pethMainPowerTrapGroup NOTIFICATION-GROUP 990 NOTIFICATIONS { pethMainPseBackUpActivatedTrap, pethMainPowerUsageOnTrap,pethMainPowerUsageOffTrap} 991 STATUS current 992 DESCRIPTION "Pse trap indications" 993 ::= { pethNotifications 7 } 995 -- 996 -- Conformance Section 997 -- 998 pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } 999 pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } 1001 pethCompliance MODULE-COMPLIANCE 1002 STATUS current 1003 DESCRIPTION 1004 "Describes the requirements for conformance to the 1005 Power Ethernet MIB." 1006 MODULE -- this module 1007 GROUP pethPsePortGroup 1008 DESCRIPTION 1009 "The pethPsePortGroup is mandatory for systems which 1010 implement PSE ports." 1011 GROUP pethPdPortGroup 1012 DESCRIPTION 1013 "The pethPdPortGroup is mandatory for systems which 1014 implement PD Ports." 1015 GROUP pethMainPseGroup 1016 DESCRIPTION 1017 "The pethMainPseGroup is mandatory for systems which 1018 implement main power supply within a PSE Device." 1019 GROUP pethTrapsControlGroup 1020 DESCRIPTION 1021 "The pethTrapsControlGroup is mandatory for systems which 1022 implement PSE ports." 1023 ::= { pethCompliances 1 } 1025 pethPseCompliance MODULE-COMPLIANCE 1026 STATUS current 1027 DESCRIPTION 1028 "Describes the requirements for conformance to the PSE 1029 and MID-Span." 1030 MODULE -- this module 1031 MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethTrapsControlGroup} 1032 ::= { pethCompliances 2 } 1034 pethPdCompliance MODULE-COMPLIANCE 1035 STATUS current 1036 DESCRIPTION 1037 "Describes the requirements for conformance to the PD." 1038 MODULE -- this module 1039 MANDATORY-GROUPS {pethPdPortGroup} 1040 ::= { pethCompliances 3} 1042 pethPsePortGroup OBJECT-GROUP 1043 OBJECTS { 1044 pethPsePortGroupIndex, 1045 pethPsePortIndex, 1046 pethPsePortAdminEnable, 1047 pethPsePortPowerPairsControlAbility, 1048 pethPsePortPowerPairs, 1049 pethPsePortDetectionStatus, 1050 pethPsePortPowerPriority, 1051 pethPsePortCurrentStatus, 1052 pethPsePortUnderCurrentCounter, 1053 pethPsePortOverCurrentCounter, 1054 pethPsePortType, 1055 pethPsePortPowerClassifications 1056 } 1057 STATUS current 1058 DESCRIPTION 1059 "PSE Port Objects." 1060 ::= { pethGroups 1 } 1062 pethPdPortGroup OBJECT-GROUP 1063 OBJECTS { 1064 pethPdPortPowerPairs, 1065 pethPdPortDetectionStatus, 1066 pethPdPortType 1067 } 1068 STATUS current 1069 DESCRIPTION 1070 "PD Port Objects." 1071 ::= { pethGroups 2 } 1073 pethMainPseGroup OBJECT-GROUP 1074 OBJECTS { 1075 pethMainPsePower, 1076 pethMainPseOperStatus, 1077 pethMainPseConsumptionPower, 1078 pethMainPseBackupPresent, 1079 pethMainPseBackupActivated, 1080 pethMainPseUsageThreshold, 1081 pethMainPseMaximumDcPower 1083 } 1084 STATUS current 1085 DESCRIPTION 1086 "Main PSE Objects. " 1087 ::= { pethGroups 3 } 1089 pethTrapsControlGroup OBJECT-GROUP 1090 OBJECTS { 1091 pethTrapsControlEnable 1092 } 1093 STATUS current 1094 DESCRIPTION 1095 "Trap Control Objects. " 1096 ::= { pethGroups 4 } 1098 END 1100 8. References 1102 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1103 for Describing SNMP Management Frameworks", RFC 2571, April 1104 1999. 1106 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1107 of Management Information for TCP/IP-based Internets", STD 1108 16, RFC 1155, May 1990. 1110 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1111 16, RFC 1212, March 1991. 1113 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1114 SNMP", RFC 1215, March 1991. 1116 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1117 Rose, M., and S. Waldbusser, "Structure of Management 1118 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1119 1999. 1121 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1122 Rose, M., and S. Waldbusser, "Textual Conventions for 1123 SMIv2", STD 58, RFC 2579, April 1999. 1125 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1126 Rose, M., and S. Waldbusser, "Conformance Statements for 1127 SMIv2", STD 58, RFC 2580, April 1999. 1129 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1130 Network Management Protocol", STD 15, RFC 1157, May 1990. 1132 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1133 "Introduction to Community-based SNMPv2", RFC 1901, January 1134 1996. 1136 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1137 "Transport Mappings for Version 2 of the Simple Network 1138 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1140 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1141 Processing and Dispatching for the Simple Network Management 1142 Protocol (SNMP)", RFC 2572, April 1999. 1144 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1145 (USM) for version 3 of the Simple Network Management 1146 Protocol (SNMPv3)", RFC 2574, April 1999. 1148 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1149 "Protocol Operations for Version 2 of the Simple Network 1150 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1152 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1153 RFC 2573, April 1999. 1155 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1156 Access Control Model (VACM) for the Simple Network 1157 Management Protocol (SNMP)", RFC 2575, April 1999. 1159 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1160 "Introduction to Version 3 of the Internet-standard Network 1161 Management Framework", RFC 2570, April 1999. 1163 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1164 Requirement Levels", BCP 14, RFC 2119, March 1997. 1166 [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects 1167 for the Ethernet-like Interface Types", RFC 2665, August 1999. 1169 [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE) 1170 Power via Media Dependent Interface (MDI)", Draft D3.1, 1171 November 2001. 1173 [PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", 1174 Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, 1175 June 2002. 1177 9.Intellectual Property 1179 The IETF takes no position regarding the validity or scope of any 1180 intellectual property or other rights that might be claimed to 1181 pertain to the implementation or use of the technology described in 1182 this document or the extent to which any license under such rights 1183 might or might not be available; neither does it represent that it 1184 has made any effort to identify any such rights. Information on the 1185 IETF's procedures with respect to rights in standards-track and 1186 standards-related documentation can be found in BCP-11. Copies of 1187 claims of rights made available for publication and any assurances of 1188 licenses to be made available, or the result of an attempt made to 1189 obtain a general license or permission for the use of such 1190 proprietary rights by implementors or users of this specification can 1191 be obtained from the IETF Secretariat. 1193 The IETF invites any interested party to bring to its attention any 1194 copyrights, patents or patent applications, or other proprietary 1195 rights which may cover technology that may be required to practice 1196 this standard. Please address the information to the IETF Executive 1197 Director. 1199 10. Security Considerations 1201 There are a number of management objects defined in this MIB 1202 that have a MAX-ACCESS clause of read-write and/or read-create. 1203 Such objects may be considered sensitive or vulnerable in some 1204 network environments. The support for SET operations in a 1205 non-secure environment without proper protection can have a 1206 negative effect on network operations. 1208 There are a number of managed objects in this MIB that may 1209 contain sensitive information. These are: 1211 It is thus important to control even GET access to these objects 1212 and possibly to even encrypt the values of these object when 1213 sending them over the network via SNMP. Not all versions of 1214 SNMP provide features for such a secure environment. 1216 SNMPv1 by itself is not a secure environment. Even if the 1217 network itself is secure (for example by using IPSec), even then, 1218 there is no control as to who on the secure network is allowed 1219 to access and GET/SET (read/change/create/delete) the objects in 1220 this MIB. 1222 It is RECOMMENDED that the implementers consider the security 1223 features as provided by the SNMPv3 framework. Specifically, the 1224 use of the User-based Security Model [RFC2274] and the 1225 View-based Access Control Model [RFC2275] is RECOMMENDED. 1227 It is then a customer/user responsibility to ensure that the SNMP 1228 entity giving access to an instance of this MIB, is properly 1229 configured to give access to the objects only to those 1230 principals (users) that have legitimate rights to indeed GET or 1231 SET (change/create/delete) them. 1233 11. Authors Addresses 1235 Avi Berger 1236 PowerDsine Inc. 1237 1, Hanagar St., P.O. Box 7220 1238 Hod Hasharon 45421, 1239 Israel 1240 Tel: +972-9-7755100 Ext 307 1241 Fax: +972-9-7755120 1242 E-mail: avib@PowerDsine.com 1244 Dan Romascanu 1245 Avaya Inc. 1246 Atidim Technology Park, Bldg. #3 1247 Tel Aviv, 61131 1248 Israel 1249 Tel: +972-3-645-8414 1250 Email: dromasca@avaya.com 1252 A. Full Copyright Statement 1254 This document and translations of it may be copied and furnished to 1255 others, and derivative works that comment on or otherwise explain it 1256 or assist in its implementation may be prepared, copied, published 1257 and distributed, in whole or in part, without restriction of any 1258 kind, provided that the above copyright notice and this paragraph are 1259 included on all such copies and derivative works. However, this 1260 document itself may not be modified in any way, such as by removing 1261 the copyright notice or references to the Internet Society or other 1262 Internet organizations, except as needed for the purpose of 1263 developing Internet standards in which case the procedures for 1264 copyrights defined in the Internet Standards process must be 1265 followed, or as required to translate it into languages other than 1266 English. 1268 The limited permissions granted above are perpetual and will not be 1269 revoked by the Internet Society or its successors or assigns. 1271 This document and the information contained herein is provided on an 1272 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1273 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1274 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1275 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1276 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.