idnits 2.17.1 draft-ietf-hubmib-power-ethernet-mib-01.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 26 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 27 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 62 instances of too long lines in the document, the longest one being 41 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 406 has weird spacing: '...MUST be used ...' == Line 442 has weird spacing: '...hat the devic...' == Line 783 has weird spacing: '...ck) and the v...' == Line 855 has weird spacing: '...e power in...' == (3 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 (20 November 2001) is 8183 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 1192, but not defined ** Obsolete undefined reference: RFC 2274 (Obsoleted by RFC 2574) == Missing Reference: 'RFC2275' is mentioned on line 1193, but not defined ** Obsolete undefined reference: RFC 2275 (Obsoleted by RFC 2575) == Unused Reference: 'RFC2119' is defined on line 1131, 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 20 November 2001 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 (2001). 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 23 54 9 Intellectual Property 24 55 10 Security Considerations 25 56 11 Authors Addresses 25 57 A Full Copyright Statement 26 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 expected 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 7. Definitions 289 POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN 291 IMPORTS 292 MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,NOTIFICATION-TYPE 293 FROM SNMPv2-SMI 294 dot3 295 FROM EtherLike-MIB 296 TruthValue 297 FROM SNMPv2-TC 298 MODULE-COMPLIANCE, OBJECT-GROUP ,NOTIFICATION-GROUP 299 FROM SNMPv2-CONF; 301 powerEthernetMIB MODULE-IDENTITY 302 LAST-UPDATED "200111200000Z" -- November 20, 2001 303 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 304 Working Group" 305 CONTACT-INFO 306 " 308 Chair: Dan Romascanu 309 Avaya Inc. 310 Tel: +972-3-645-8414 311 Email: dromasca@avaya.com 313 Editor: Avi Berger 314 PowerDsine Inc. 315 Tel: +972-9-7755100 Ext 307 316 Fax: +972-9-7755120 317 E-mail: avib@PowerDsine.com 318 " 320 DESCRIPTION 321 "The MIB module for managing Powered Devices (PD) or 322 Power Source Equipment (PSE) working according to the IEEE 323 802.af Power Ethernet (DTE Power via MDI) standard. 325 The following terms are used throughout this 326 MIB module. For complete formal definitions, 327 the IEEE 802.3 standards should be consulted 328 wherever possible: 330 Group - A recommended, but optional, entity 331 defined by the IEEE 802.3 management standard, 332 in order to support a modular numbering scheme. 333 The classical example allows an implementor to 334 represent field-replaceable units as groups of 335 ports, with the port numbering matching the 336 modular hardware implementation. 338 Port - This entity identifies the port within the group 339 for which this entry contains information.The numbering 340 scheme for ports is implementation specific. 342 ::= { dot3 20 } 344 pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } 345 pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } 346 pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 3 } 348 -- PSE Objects 350 pethPsePortTable OBJECT-TYPE 351 SYNTAX SEQUENCE OF PethPsePortEntry 352 MAX-ACCESS not-accessible 353 STATUS current 354 DESCRIPTION 355 "A table of objects that display and control the power 356 characteristics power Ethernet ports on a Power Source 357 Entity (PSE) device. This group will be implemented in 358 managed power Ethernet switches and mid-span devices." 359 ::= { pethObjects 1 } 361 pethPsePortEntry OBJECT-TYPE 362 SYNTAX PethPsePortEntry 363 MAX-ACCESS not-accessible 364 STATUS current 365 DESCRIPTION 366 "A set of objects that display and control the power 367 characteristics of a power Ethernet PSE port." 368 INDEX { pethPsePortGroupIndex , pethPsePortIndex } 369 ::= { pethPsePortTable 1 } 371 PethPsePortEntry ::= SEQUENCE { 372 pethPsePortGroupIndex 373 INTEGER, 374 pethPsePortIndex 375 INTEGER, 376 pethPsePortAdminEnable 377 INTEGER, 378 pethPsePortPowerPairsControlAbility 379 TruthValue, 380 pethPsePortPowerPairs 381 INTEGER, 382 pethPsePortPowerDetectionControl 383 INTEGER, 384 pethPsePortDetectionStatus 385 INTEGER, 386 pethPsePortPowerPriority 387 INTEGER, 388 pethPsePortCurrentStatus 389 INTEGER, 390 pethPsePortCurrentStatusClear 391 INTEGER, 392 pethPsePortType 393 INTEGER, 394 pethPsePortPowerClassifications 395 INTEGER 396 } 398 pethPsePortGroupIndex OBJECT-TYPE 399 SYNTAX INTEGER (1..2147483647) 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "This variable uniquely identifies the group 404 containing the port to which power Ethernet PSE is connected. 405 Group means (box in the stack, module in a rack) and the value 1 406 MUST be used for non-modular devices " 407 ::= { pethPsePortEntry 1 } 409 pethPsePortIndex OBJECT-TYPE 410 SYNTAX INTEGER(1..2147483647) 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "This variable uniquely identifies the power Ethernet PSE 415 port within group pethPseGroupIndex to which the 416 power Ethernet PSE entry is connected." 417 ::= { pethPsePortEntry 2 } 419 pethPsePortAdminEnable OBJECT-TYPE 420 SYNTAX INTEGER { 421 enable(1), 422 disable(2) 423 } 425 MAX-ACCESS read-write 426 STATUS current 427 DESCRIPTION 428 "Enables power supply on this port. 429 Setting this object at a value enable(1) enables power 430 and detection mechanism for this port. 431 Setting this object at a value disable(2) disables power 432 for this port." 433 ::= { pethPsePortEntry 3 } 435 pethPsePortPowerPairsControlAbility OBJECT-TYPE 436 SYNTAX TruthValue 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "Describes the capability of controlling the power pairs 441 functionality to switch pins for sourcing power. 442 The value true indicate that the device has the capability 443 to control the power pairs" 444 ::= { pethPsePortEntry 4 } 446 pethPsePortPowerPairs OBJECT-TYPE 447 SYNTAX INTEGER { 448 signal(1), 449 spare(2) 450 } 451 MAX-ACCESS read-write 452 STATUS current 453 DESCRIPTION 454 "Describes or controls the pairs in use. If the value of 455 pethPsePortPowerPairsControl is true, this object is 456 writable. 457 A value of signal(1) menas that the signal pairs 458 only are in use. 459 A value of spare(2) means that the spare pairs 460 only are in use." 461 ::= { pethPsePortEntry 5 } 463 pethPsePortPowerDetectionControl OBJECT-TYPE 464 SYNTAX INTEGER { 465 auto(1), 466 test(2) 467 } 468 MAX-ACCESS read-write 469 STATUS current 470 DESCRIPTION 471 "Controls the power detection mechanism of the port. 472 Setting the value auto(1) enables the power detection 473 mechanism of the port. 474 Setting the value test(2) puts the port in a 475 testmode: force continuous discovery without applying 476 power regardless of whether PD detected." 477 ::= { pethPsePortEntry 6 } 479 pethPsePortDetectionStatus OBJECT-TYPE 480 SYNTAX INTEGER { 481 disabled(1), 482 searching(2), 483 detected(3), 484 deliveringPower(4), 485 fault(5), 486 invalidPD(6), 487 test(7), 488 denyLowPriority(8) 489 } 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "Describes the operational status of the port PD detection. 494 A value of disabled(1) indicates that the PD Detection function has 495 been disabled. 496 A value of searching(2) indicates that the PD Detection function is 497 enabled and is searching for a valid PD. 498 A value of detected(3)indicates that the PD Detection function has 499 detected a valid PD but the PSE is not supplying power. 500 A value of deliveringPower(4) indicates that the port 501 executed the detection algorithm, found a PD connection 502 and is currently delivering power. 503 A value of fault(5) indicates that a fault was detected 504 on the port , faults detected are vendor-specific. 505 A value of invalidPD(6)indicates that the PD Detection function has 506 detected a invalid PD. 507 A value of test(7)indicates that the PD Detection function has been 508 placed in test mode. 509 A value of denyLowPriority(8) indicates that the port was 510 disabled by the power management system, in order to keep 511 active higher priority ports. 512 " 513 ::= { pethPsePortEntry 7 } 515 pethPsePortPowerPriority OBJECT-TYPE 516 SYNTAX INTEGER { 517 critical(1), 518 high(2), 519 low(3) 521 } 522 MAX-ACCESS read-write 523 STATUS current 524 DESCRIPTION 525 "This object controls the priority of the port from the point 526 of view of a power management algorithm. The priority that 527 is set by this variable could be used by a control mechanism 528 that prevents over current situations by disconnecting first 529 ports with lower power priority. Ports that connect devices 530 critical to the operation of the network - like the E911 531 telephones ports - should be set to higher priority." 532 ::= { pethPsePortEntry 8 } 534 pethPsePortCurrentStatus OBJECT-TYPE 535 SYNTAX INTEGER { 536 ok(1), 537 underCurrent(2), 538 overCurrent(3), 539 both(4) 540 } 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "Describes a current port status related to the power generation 545 The value ok(1) indicates neither an undercurrent or an overcurrent 546 condition was detected since the attribute was last cleared. 547 The value underCurrent(2) indicates that the port current 548 is below the minimal value since the attribute was last cleared. 549 The value overCurrent(3) indicates that the port current 550 exceeds the maximal value since the attribute was last cleared. 551 The value both(4) indicates that both underCurrent and overCurrent 552 since the attribute was last cleared. 553 This attribute is cleared through the pethPsePortCurrentStatusClear 554 action. 556 An undercurrent condition is detected when the current drawn from 557 the PSE at the MDI is less than 558 Off-mode current 2 for a duration greater than Under load time 559 limit. 560 An overcurrent condition is detected when the current drawn from the 561 PSE at the MDI is greater than the overload current limit 562 for a duration greater that Overload time limit. 563 The values Overload current limit, Overload time 564 limit, Off-mode current 2 and Under load time limit are specified in 565 Table 33-5. If a Clause 22 MII or Clause 35 GMII is present, then 566 this will map to the Under Current and Over Current bits 567 specified in 33.6.1.2.2 and 33.6.1.2.3.;" 569 REFERENCE "[IEEE DRAFT STANDARD FOR DTE POWER VIA MDI P802.3af/D1.2]" 570 ::= { pethPsePortEntry 10 } 572 pethPsePortCurrentStatusClear OBJECT-TYPE 573 SYNTAX INTEGER { 574 clear(1), 575 off(2) 576 } 577 MAX-ACCESS read-write 578 STATUS current 579 DESCRIPTION 580 "Setting the value of this object to clear(1) clears the value 581 of the pethPsePortStatus and enable the agent to update the 582 pethPsePortStatus. 583 Read operation this value will be off(2)." 584 ::= { pethPsePortEntry 11 } 586 pethPsePortType OBJECT-TYPE 587 SYNTAX INTEGER { 588 other(1), 589 telephone(2), 590 webcam(3), 591 wireless(4) 592 } 593 MAX-ACCESS read-write 594 STATUS current 595 DESCRIPTION 596 "A manager will set the value of this variable to a value 597 that indicates the type of the device that is connected 598 to theport. This value can be the result of the mapping 599 the address of the station connected to the port and of 600 the value of the pethPdPortType of the respective PD port." 601 ::= { pethPsePortEntry 12 } 603 pethPsePortPowerClassifications OBJECT-TYPE 604 SYNTAX INTEGER { 605 class0(1), 606 class1(2), 607 class2(3), 608 class3(4), 609 class4(5), 610 class5(6) 611 } 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "Classification is a way to tag different terminals on the 616 Power over LAN network according to their power consumption. 618 Devices such as IP telephones, WLAN access points and others, 619 will be classified according to their power requirements. 620 A read-only value that indicates the PD Class of a detected PD as 621 specified in IEEE Draft P802.3af/D2.1 Supplement to IEEE Std.802.3 622 November 14 2001 cclause 33.2.5 and 33.2.6. 624 The value is only valid while a valid PD is being detected as indicated 625 by the attribute pethPsePortDetectionStatus reporting the enumeration 626 (detected) or (deliveringPower). 627 " 628 ::= { pethPsePortEntry 13 } 630 -- PD Port table 632 pethPdPortTable OBJECT-TYPE 633 SYNTAX SEQUENCE OF PethPdPortEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "A table of objects that display and control the power 638 characteristics power Ethernet ports on a Powered 639 Device(PD) device. This group will be implemented in 640 managed powered and mid-span devices." 641 ::= { pethObjects 2 } 643 pethPdPortEntry OBJECT-TYPE 644 SYNTAX PethPdPortEntry 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "A set of objects that display and control the power 649 characteristics of a Powered Device port." 650 INDEX { pethPdPortIndex } 651 ::= { pethPdPortTable 1 } 653 PethPdPortEntry ::= SEQUENCE { 654 pethPdPortIndex 655 INTEGER, 656 pethPdPortPowerPairs 657 INTEGER, 658 pethPdPortDetectionStatus 659 INTEGER, 660 pethPdPortType 661 INTEGER 662 } 664 pethPdPortIndex OBJECT-TYPE 665 SYNTAX INTEGER (0..65535) 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "An index value that uniquely identifies an 670 interface to a PD device. The 671 interface identified by a particular value of 672 this index is the same interface as identified 673 by the same value of ifIndex. The mapping 674 between the ifIndex values and the numbering of 675 the port on the device is an implementation 676 issue." 677 ::= { pethPdPortEntry 1 } 679 pethPdPortPowerPairs OBJECT-TYPE 680 SYNTAX INTEGER { 681 signal(1), 682 spare(2), 683 both(3) 684 } 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "Describes the pairs in use by the PD to derive power. 689 A value of signal(1) indicates that only PD Pinout Mode A is 690 supported by the PD. 691 A value of spare(2) indicates that only PD Pinout Mode B is 692 supported by the PD. 693 A value of both(3) means indicates that both PD Pinout Mode A and PD 694 Pinout Mode B are supported by the PD." 695 ::= { pethPdPortEntry 2 } 697 pethPdPortDetectionStatus OBJECT-TYPE 698 SYNTAX INTEGER { 699 off(1), 700 receivingPower(2) 701 } 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "Describes the operational status of the port detection. 706 The value off(1) indicates that the PD is drawing a current less 707 than I 708 Port as specified in IEEE Draft P802.3af/D2.1 Supplement to IEEE 709 Std.802.3 November 14 2001 Table 33-10. 710 The value receivingPower(2) indicates that the PD is drawing a 711 current greater I Port as specified in 712 IEEE Draft P802.3af/D2.1 Supplement to 713 IEEE Std.802.3 November 14 2001 Table 33-10. 715 " 716 ::= { pethPdPortEntry 3 } 718 pethPdPortType OBJECT-TYPE 719 SYNTAX INTEGER { 720 other(1), 721 telephone(2), 722 webcam(3), 723 wireless(4) 724 } 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The type of the device. A management application may read 729 the value of this variable and use it for setting the 730 corresponding value of pethPsePortType of the port that 731 connects the device." 732 ::= { pethPdPortEntry 4 } 734 -- Main PSE Objects 736 pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } 738 pethMainPseTable OBJECT-TYPE 739 SYNTAX SEQUENCE OF PethMainPseEntry 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "A table of objects that display and control the Main power 744 on a PSE device. Example internet switch midspan device can 745 control an Internet port and the Main Power supply unit's." 746 ::= { pethMainPseObjects 1 } 748 pethMainPseEntry OBJECT-TYPE 749 SYNTAX PethMainPseEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "A set of objects that display and control the Main power 754 of a PSE. " 755 INDEX { pethMainPseGroupIndex } 756 ::= { pethMainPseTable 1 } 758 PethMainPseEntry ::= SEQUENCE { 759 pethMainPseGroupIndex 760 INTEGER, 761 pethMainPsePower 762 Integer32, 763 pethMainPseOperStatus 764 INTEGER, 765 pethMainPseConsumptionPower 766 Gauge32, 767 pethMainPseBackupPresent 768 INTEGER, 769 pethMainPseBackupActivated 770 TruthValue, 771 pethMainPseUsageThreshold 772 INTEGER, 773 pethMainPseMaximumDcPower 774 INTEGER 775 } 776 pethMainPseGroupIndex OBJECT-TYPE 777 SYNTAX INTEGER (0..65535) 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "This variable uniquely identifies the group to which 782 power Ethernet PSE is connected.Group means (box in the stack, 783 module in a rack) and the value 1 MUST be used for non-modular 784 devices " 785 ::= { pethMainPseEntry 1 } 787 pethMainPsePower OBJECT-TYPE 788 SYNTAX Integer32 (0..65535) 789 UNITS "Watts" 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "The nominal power of the PSE expressed in Watts." 794 ::= { pethMainPseEntry 2 } 796 pethMainPseOperStatus OBJECT-TYPE 797 SYNTAX INTEGER { 798 on(1), 799 off(2), 800 faulty(3) 801 } 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The operational status of the main PSE." 806 ::= { pethMainPseEntry 3 } 808 pethMainPseConsumptionPower OBJECT-TYPE 809 SYNTAX Gauge32 810 UNITS "Watts" 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "Measured usage power expressed in Watts." 815 ::= { pethMainPseEntry 4 } 817 pethMainPseBackupPresent OBJECT-TYPE 818 SYNTAX INTEGER { 819 present(1), 820 notPresent(2), 821 faulty(3) 822 } 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "reflects the presence of a backup PSE ." 827 ::= { pethMainPseEntry 5 } 829 pethMainPseBackupActivated OBJECT-TYPE 830 SYNTAX TruthValue 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "Reflects the activation status of the backup PSE . 835 The value true Backup is activated." 836 ::= { pethMainPseEntry 6 } 838 pethMainPseUsageThreshold OBJECT-TYPE 839 SYNTAX INTEGER (1..99) 840 UNITS "%" 841 MAX-ACCESS read-write 842 STATUS current 843 DESCRIPTION 844 "The usage threshold expressed in percens for 845 comparing the measured power and initiating 846 an alarm if the threshold is exceeded." 847 ::= { pethMainPseEntry 7 } 849 pethMainPseMaximumDcPower OBJECT-TYPE 850 SYNTAX INTEGER 851 UNITS "Watts" 852 MAX-ACCESS read-write 853 STATUS current 854 DESCRIPTION 855 "Describes the maximum available power in 856 Watt to be supplied by the DC backup source to this 857 device." 858 ::= { pethMainPseEntry 8 } 860 -- Traps Control Objects 862 pethTrapsControl OBJECT IDENTIFIER ::= { pethObjects 4 } 864 pethTrapsControlTable OBJECT-TYPE 865 SYNTAX SEQUENCE OF PethTrapsControlEntry 866 MAX-ACCESS not-accessible 867 STATUS current 868 DESCRIPTION 869 "A table of objects that display and control the Traps 870 on a PSE device." 871 ::= { pethTrapsControl 1 } 873 pethTrapsControlEntry OBJECT-TYPE 874 SYNTAX PethTrapsControlEntry 875 MAX-ACCESS not-accessible 876 STATUS current 877 DESCRIPTION 878 "A set of objects that control the Trap events." 879 INDEX { pethTrapsControlGroupIndex } 880 ::= { pethTrapsControlTable 1 } 882 PethTrapsControlEntry ::= SEQUENCE { 883 pethTrapsControlGroupIndex 884 INTEGER, 885 pethTrapsControlEnable 886 INTEGER 887 } 888 pethTrapsControlGroupIndex OBJECT-TYPE 889 SYNTAX INTEGER (0..65535) 890 MAX-ACCESS not-accessible 891 STATUS current 892 DESCRIPTION 893 "This variable uniquely identifies the group. Group means 894 box in the stack, module in a rack and it is recommended 895 that the value 1 MUST be used for non-modular devices " 896 ::= { pethTrapsControlEntry 1 } 898 pethTrapsControlEnable OBJECT-TYPE 899 SYNTAX INTEGER 900 { 901 enable(1), 902 disable(2) 903 } 904 MAX-ACCESS read-write 905 STATUS current 906 DESCRIPTION 907 "Enable Traps from Agent" 908 ::= { pethTrapsControlEntry 2 } 910 -- 911 -- Notifications Section 912 -- 913 -- 915 pethPsePortOnOffTrap NOTIFICATION-TYPE 916 OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionStatus } 917 STATUS current 918 DESCRIPTION " This trap indicate if Pse Port is delivering or not power to the PD." 919 ::= { pethNotifications 1 } 921 pethPsePortCurrentStatusTrap NOTIFICATION-TYPE 922 OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortCurrentStatus } 923 STATUS current 924 DESCRIPTION 925 "This trap indicate Port Change Status and it will be 926 sent on every status change." 927 ::= { pethNotifications 2 } 929 pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE 930 OBJECTS { pethPsePortGroupIndex,pethMainPseBackupActivated } 931 STATUS current 932 DESCRIPTION 933 "This trap indicate BackUp is Activated or BackUp 934 is released." 935 ::= { pethNotifications 3 } 937 pethMainPowerUsageOnTrap NOTIFICATION-TYPE 938 OBJECTS { pethPsePortGroupIndex } 939 STATUS current 940 DESCRIPTION 941 "This trap indicate PSE Threshold usage indication is on , 942 the useage power is above the treshold." 943 ::= { pethNotifications 4 } 945 pethMainPowerUsageOffTrap NOTIFICATION-TYPE 946 OBJECTS { pethPsePortGroupIndex } 947 STATUS current 948 DESCRIPTION 949 "This trap indicate PSE Threshold usage indication off , 950 the useage power is below the treshold.." 951 ::= { pethNotifications 5 } 952 pethPsePortTrapGroup NOTIFICATION-GROUP 953 NOTIFICATIONS { pethPsePortOnOffTrap, pethPsePortCurrentStatusTrap} 954 STATUS current 955 DESCRIPTION 956 "Pse trap indications" 957 ::= { pethNotifications 6 } 959 pethMainPowerTrapGroup NOTIFICATION-GROUP 960 NOTIFICATIONS { pethMainPseBackUpActivatedTrap, pethMainPowerUsageOnTrap,pethMainPowerUsageOffTrap} 961 STATUS current 962 DESCRIPTION "Pse trap indications" 963 ::= { pethNotifications 7 } 965 -- 966 -- Conformance Section 967 -- 968 pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } 969 pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } 971 pethCompliance MODULE-COMPLIANCE 972 STATUS current 973 DESCRIPTION 974 "Describes the requirements for conformance to the 975 Power Ethernet MIB." 976 MODULE -- this module 977 GROUP pethPsePortGroup 978 DESCRIPTION 979 "The pethPsePortGroup is mandatory for systems which 980 implement PSE ports." 981 GROUP pethPdPortGroup 982 DESCRIPTION 983 "The pethPdPortGroup is mandatory for systems which 984 implement PD Ports." 985 GROUP pethMainPseGroup 986 DESCRIPTION 987 "The pethMainPseGroup is mandatory for systems which 988 implement main power supply within a PSE Device." 989 GROUP pethTrapsControlGroup 990 DESCRIPTION 991 "The pethTrapsControlGroup is mandatory for systems which 992 implement PSE ports." 994 ::= { pethCompliances 1 } 996 pethPseCompliance MODULE-COMPLIANCE 997 STATUS current 998 DESCRIPTION 999 "Describes the requirements for conformance to the PSE and MidSpan." 1000 MODULE -- this module 1001 MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethTrapsControlGroup} 1002 ::= { pethCompliances 2 } 1004 pethPdCompliance MODULE-COMPLIANCE 1005 STATUS current 1006 DESCRIPTION 1007 "Describes the requirements for conformance to the PSE 1008 and MidSpan." 1009 MODULE -- this module 1010 MANDATORY-GROUPS {pethPdPortGroup} 1011 ::= { pethCompliances 3 } 1013 pethPsePortGroup OBJECT-GROUP 1014 OBJECTS { 1015 pethPsePortGroupIndex, 1016 pethPsePortIndex, 1017 pethPsePortAdminEnable, 1018 pethPsePortPowerPairsControlAbility, 1019 pethPsePortPowerPairs, 1020 pethPsePortDetectionStatus, 1021 pethPsePortPowerPriority, 1022 pethPsePortCurrentStatus, 1023 pethPsePortCurrentStatusClear, 1024 pethPsePortType, 1025 pethPsePortPowerClassifications 1026 } 1027 STATUS current 1028 DESCRIPTION 1029 "PSE Port Objects." 1030 ::= { pethGroups 1 } 1032 pethPdPortGroup OBJECT-GROUP 1033 OBJECTS { 1034 pethPdPortPowerPairs, 1035 pethPdPortDetectionStatus, 1036 pethPdPortType 1037 } 1038 STATUS current 1039 DESCRIPTION 1040 "PD Port Objects." 1041 ::= { pethGroups 2 } 1043 pethMainPseGroup OBJECT-GROUP 1044 OBJECTS { 1045 pethMainPsePower, 1046 pethMainPseOperStatus, 1047 pethMainPseConsumptionPower, 1048 pethMainPseBackupPresent, 1049 pethMainPseBackupActivated, 1050 pethMainPseUsageThreshold, 1051 pethMainPseMaximumDcPower 1052 } 1053 STATUS current 1054 DESCRIPTION 1055 "Main PSE Objects. " 1056 ::= { pethGroups 3 } 1058 pethTrapsControlGroup OBJECT-GROUP 1059 OBJECTS { 1060 pethTrapsControlEnable 1061 } 1062 STATUS current 1063 DESCRIPTION 1064 "Trap Control Objects. " 1065 ::= { pethGroups 4 } 1066 END 1068 8. References 1070 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1071 for Describing SNMP Management Frameworks", RFC 2571, April 1072 1999. 1074 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1075 of Management Information for TCP/IP-based Internets", STD 1076 16, RFC 1155, May 1990. 1078 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1079 16, RFC 1212, March 1991. 1081 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1082 SNMP", RFC 1215, March 1991. 1084 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1085 Rose, M., and S. Waldbusser, "Structure of Management 1086 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1087 1999. 1089 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1090 Rose, M., and S. Waldbusser, "Textual Conventions for 1091 SMIv2", STD 58, RFC 2579, April 1999. 1093 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1094 Rose, M., and S. Waldbusser, "Conformance Statements for 1095 SMIv2", STD 58, RFC 2580, April 1999. 1097 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1098 Network Management Protocol", STD 15, RFC 1157, May 1990. 1100 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1101 "Introduction to Community-based SNMPv2", RFC 1901, January 1102 1996. 1104 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1105 "Transport Mappings for Version 2 of the Simple Network 1106 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1108 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1109 Processing and Dispatching for the Simple Network Management 1110 Protocol (SNMP)", RFC 2572, April 1999. 1112 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1113 (USM) for version 3 of the Simple Network Management 1114 Protocol (SNMPv3)", RFC 2574, April 1999. 1116 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1117 "Protocol Operations for Version 2 of the Simple Network 1118 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1120 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1121 RFC 2573, April 1999. 1123 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1124 Access Control Model (VACM) for the Simple Network 1125 Management Protocol (SNMP)", RFC 2575, April 1999. 1127 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1128 "Introduction to Version 3 of the Internet-standard Network 1129 Management Framework", RFC 2570, April 1999. 1131 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1132 Requirement Levels", BCP 14, RFC 2119, March 1997. 1134 [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects 1135 for the Ethernet-like Interface Types", RFC 2665, August 1999. 1137 [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE) 1138 Power via Media Dependent Interface (MDI)", Draft D2.1, 1139 November 2001. 1141 [PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", 1142 Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, 1143 February 2001. 1145 9.Intellectual Property 1147 The IETF takes no position regarding the validity or scope of any 1148 intellectual property or other rights that might be claimed to 1149 pertain to the implementation or use of the technology described in 1150 this document or the extent to which any license under such rights 1151 might or might not be available; neither does it represent that it 1152 has made any effort to identify any such rights. Information on the 1153 IETF's procedures with respect to rights in standards-track and 1154 standards-related documentation can be found in BCP-11. Copies of 1155 claims of rights made available for publication and any assurances of 1156 licenses to be made available, or the result of an attempt made to 1157 obtain a general license or permission for the use of such 1158 proprietary rights by implementors or users of this specification can 1159 be obtained from the IETF Secretariat. 1161 The IETF invites any interested party to bring to its attention any 1162 copyrights, patents or patent applications, or other proprietary 1163 rights which may cover technology that may be required to practice 1164 this standard. Please address the information to the IETF Executive 1165 Director. 1167 10. Security Considerations 1169 There are a number of management objects defined in this MIB 1170 that have a MAX-ACCESS clause of read-write and/or read-create. 1171 Such objects may be considered sensitive or vulnerable in some 1172 network environments. The support for SET operations in a 1173 non-secure environment without proper protection can have a 1174 negative effect on network operations. 1176 There are a number of managed objects in this MIB that may 1177 contain sensitive information. These are: 1179 It is thus important to control even GET access to these objects 1180 and possibly to even encrypt the values of these object when 1181 sending them over the network via SNMP. Not all versions of 1182 SNMP provide features for such a secure environment. 1184 SNMPv1 by itself is not a secure environment. Even if the 1185 network itself is secure (for example by using IPSec), even then, 1186 there is no control as to who on the secure network is allowed 1187 to access and GET/SET (read/change/create/delete) the objects in 1188 this MIB. 1190 It is RECOMMENDED that the implementers consider the security 1191 features as provided by the SNMPv3 framework. Specifically, the 1192 use of the User-based Security Model [RFC2274] and the 1193 View-based Access Control Model [RFC2275] is RECOMMENDED. 1195 It is then a customer/user responsibility to ensure that the SNMP 1196 entity giving access to an instance of this MIB, is properly 1197 configured to give access to the objects only to those 1198 principals (users) that have legitimate rights to indeed GET or 1199 SET (change/create/delete) them. 1201 11. Authors Addresses 1203 Avi Berger 1204 PowerDsine Inc. 1205 1, Hanagar St., P.O. Box 7220 1206 Hod Hasharon 45421, 1207 Israel 1208 Tel: +972-9-7755100 Ext 307 1209 Fax: +972-9-7755120 1210 E-mail: avib@PowerDsine.com 1212 Dan Romascanu 1213 Avaya Inc. 1214 Atidim Technology Park, Bldg. #3 1215 Tel Aviv, 61131 1216 Israel 1217 Tel: +972-3-645-8414 1218 Email: dromasca@avaya.com 1220 A. Full Copyright Statement 1222 This document and translations of it may be copied and furnished to 1223 others, and derivative works that comment on or otherwise explain it 1224 or assist in its implementation may be prepared, copied, published 1225 and distributed, in whole or in part, without restriction of any 1226 kind, provided that the above copyright notice and this paragraph are 1227 included on all such copies and derivative works. However, this 1228 document itself may not be modified in any way, such as by removing 1229 the copyright notice or references to the Internet Society or other 1230 Internet organizations, except as needed for the purpose of 1231 developing Internet standards in which case the procedures for 1232 copyrights defined in the Internet Standards process must be 1233 followed, or as required to translate it into languages other than 1234 English. 1236 The limited permissions granted above are perpetual and will not be 1237 revoked by the Internet Society or its successors or assigns. 1239 This document and the information contained herein is provided on an 1240 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1241 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1242 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1243 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1244 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.