idnits 2.17.1 draft-ietf-snmpv3-update-mib-05.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. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 400: '... specified community name) MAY include...' RFC 2119 keyword, line 402: '...k(s). It is strongly RECOMMENDED that...' RFC 2119 keyword, line 421: '... strongly RECOMMENDED that the ...' RFC 2119 keyword, line 553: '...of SNMP entities MAY be capable of gen...' RFC 2119 keyword, line 1184: '...cationFailure description from MUST to...' (2 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1009 has weird spacing: '... The previo...' -- 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 (9 August 2000) is 8660 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) == Unused Reference: 'RFC1213' is defined on line 1087, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 2233 (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFC-TM' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFC-PROTO' Summary: 16 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Editor of this version: 2 Request for Comments: -MIB R. Presuhn 3 STD: XXX BMC Software, Inc. 4 Obsoletes: 1907 Authors of previous version: 5 Category: Standards Track J. Case 6 SNMP Research, Inc. 7 K. McCloghrie 8 Cisco Systems, Inc. 9 M. Rose 10 Dover Beach Consulting, Inc. 11 S. Waldbusser 12 International Network Services 13 9 August 2000 15 Management Information Base 16 for the 17 Simple Network Management Protocol 18 20 Status of this Memo 22 This document is an Internet-Draft and is in full conformance with 23 all provisions of Section 10 of RFC2026. Internet-Drafts are working 24 documents of the Internet Engineering Task Force (IETF), its areas, 25 and its working groups. Note that other groups may also distribute 26 working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html 39 Copyright Notice 41 Copyright (C) The Internet Society (2000). All Rights Reserved. 43 Abstract 45 This document defines managed objects which describe the behavior of 46 an SNMP entity. This document obsoletes RFC 1907, Management 47 Information Base for Version 2 of the Simple Network Management 48 Protocol (SNMPv2). 50 Table of Contents 52 1. The SNMP Management Framework ............................... 3 53 2. Definitions ................................................. 4 54 3. Notice on Intellectual Property ............................. 22 55 4. Acknowledgments ............................................. 23 56 5. Security Considerations ..................................... 24 57 6. References .................................................. 24 58 7. Editor's Address ............................................ 26 59 8. Changes from RFC 1907 ....................................... 26 60 9. Issues ...................................................... 27 61 10. Full Copyright Statement ................................... 29 63 1. The SNMP Management Framework 65 The SNMP Management Framework at the time of this writing consists of 66 five major components: 68 - An overall architecture, described in RFC 2571 [RFC2571]. 70 - Mechanisms for describing and naming objects and events for 71 the purpose of management. The first version of this 72 Structure of Management Information (SMI) is called SMIv1 73 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 74 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 75 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 76 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 78 - Message protocols for transferring management information. 79 The first version of the SNMP message protocol is called 80 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 81 second version of the SNMP message protocol, which is not 82 an Internet standards track protocol, is called SNMPv2c and 83 described in RFC 1901 [RFC1901] and RFC -TM [RFC-TM]. The 84 third version of the message protocol is called SNMPv3 and 85 described in RFC -TM [RFC-TM], RFC 2572 [RFC2572] and RFC 86 2574 [RFC2574]. 88 - Protocol operations for accessing management information. 89 The first set of protocol operations and associated PDU 90 formats is described in STD 15, RFC 1157 [RFC1157]. A 91 second set of protocol operations and associated PDU 92 formats is described in RFC -PROTO [RFC-PROTO]. 94 - A set of fundamental applications described in RFC 2573 95 [RFC2573] and the view-based access control mechanism 96 described in RFC 2575 [RFC2575]. 98 A more detailed introduction to the current SNMP Management Framework 99 can be found in RFC 2570 [RFC2570]. 101 Managed objects are accessed via a virtual information store, termed 102 the Management Information Base or MIB. Objects in the MIB are 103 defined using the mechanisms defined in the SMI. 105 This memo specifies a MIB module that is compliant to the SMIv2. A 106 MIB conforming to the SMIv1 can be produced through the appropriate 107 translations. The resulting translated MIB must be semantically 108 equivalent, except where objects or events are omitted because no 109 translation is possible (use of Counter64). Some machine readable 110 information in SMIv2 will be converted into textual descriptions in 111 SMIv1 during the translation process. However, this loss of machine 112 readable information is not considered to change the semantics of the 113 MIB. 115 It is the purpose of this document to define managed objects which 116 describe the behavior of an SNMP entity, as defined in the SNMP 117 architecture [RFC2571]. 119 2. Definitions 121 SNMPv2-MIB DEFINITIONS ::= BEGIN 123 IMPORTS 124 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 125 TimeTicks, Counter32, snmpModules, mib-2 126 FROM SNMPv2-SMI 127 DisplayString, TestAndIncr, TimeStamp 128 FROM SNMPv2-TC 129 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 130 FROM SNMPv2-CONF; 132 snmpMIB MODULE-IDENTITY 133 LAST-UPDATED "200008092017Z" 134 ORGANIZATION "IETF SNMPv3 Working Group" 135 CONTACT-INFO 136 "WG-EMail: snmpv3@tis.com 137 Subscribe: majordomo@tis.com 138 In message body: subscribe snmpv3 140 Chair: Russ Mundy 141 TIS Labs at Network Associates 142 postal: 3060 Washington Rd 143 Glenwood MD 21738 144 USA 145 EMail: mundy@tislabs.com 146 phone: +1 301 854-6889 148 Editor: Randy Presuhn 149 BMC Software, Inc. 150 postal: 2141 North First Street 151 San Jose, CA 95131 152 USA 153 EMail: randy_presuhn@bmc.com 154 phone: +1 408 546-1006" 155 DESCRIPTION 156 "The MIB module for SNMP entities." 157 REVISION "200008092017Z" 158 DESCRIPTION 159 "This revision of this MIB module was published as 160 ." 161 REVISION "199511090000Z" 162 DESCRIPTION 163 "This revision of this MIB module was published as 164 RFC 1907." 165 REVISION "199304010000Z" 166 DESCRIPTION 167 "The initial revision of this MIB module was published 168 as RFC 1450." 169 ::= { snmpModules 1 } 171 snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 } 173 -- ::= { snmpMIBObjects 1 } this OID is obsolete 174 -- ::= { snmpMIBObjects 2 } this OID is obsolete 175 -- ::= { snmpMIBObjects 3 } this OID is obsolete 177 -- the System group 178 -- 179 -- a collection of objects common to all managed systems. 181 system OBJECT IDENTIFIER ::= { mib-2 1 } 183 sysDescr OBJECT-TYPE 184 SYNTAX DisplayString (SIZE (0..255)) 185 MAX-ACCESS read-only 186 STATUS current 187 DESCRIPTION 188 "A textual description of the entity. This value should 189 include the full name and version identification of 190 the system's hardware type, software operating-system, 191 and networking software." 192 ::= { system 1 } 194 sysObjectID OBJECT-TYPE 195 SYNTAX OBJECT IDENTIFIER 196 MAX-ACCESS read-only 197 STATUS current 198 DESCRIPTION 199 "The vendor's authoritative identification of the 200 network management subsystem contained in the entity. 201 This value is allocated within the SMI enterprises 202 subtree (1.3.6.1.4.1) and provides an easy and 203 unambiguous means for determining `what kind of box' is 204 being managed. For example, if vendor `Flintstones, 205 Inc.' was assigned the subtree 1.3.6.1.4.1.424242, 206 it could assign the identifier 1.3.6.1.4.1.424242.1.1 207 to its `Fred Router'." 208 ::= { system 2 } 210 sysUpTime OBJECT-TYPE 211 SYNTAX TimeTicks 212 MAX-ACCESS read-only 213 STATUS current 214 DESCRIPTION 215 "The time (in hundredths of a second) since the 216 network management portion of the system was last 217 re-initialized." 218 ::= { system 3 } 220 sysContact OBJECT-TYPE 221 SYNTAX DisplayString (SIZE (0..255)) 222 MAX-ACCESS read-write 223 STATUS current 224 DESCRIPTION 225 "The textual identification of the contact person for 226 this managed node, together with information on how 227 to contact this person. If no contact information is 228 known, the value is the zero-length string." 229 ::= { system 4 } 231 sysName OBJECT-TYPE 232 SYNTAX DisplayString (SIZE (0..255)) 233 MAX-ACCESS read-write 234 STATUS current 235 DESCRIPTION 236 "An administratively-assigned name for this managed 237 node. By convention, this is the node's fully-qualified 238 domain name. If the name is unknown, the value is 239 the zero-length string." 240 ::= { system 5 } 242 sysLocation OBJECT-TYPE 243 SYNTAX DisplayString (SIZE (0..255)) 244 MAX-ACCESS read-write 245 STATUS current 246 DESCRIPTION 247 "The physical location of this node (e.g., 'telephone 248 closet, 3rd floor'). If the location is unknown, the 249 value is the zero-length string." 250 ::= { system 6 } 252 sysServices OBJECT-TYPE 253 SYNTAX INTEGER (0..127) 254 MAX-ACCESS read-only 255 STATUS current 256 DESCRIPTION 257 "A value which indicates the set of services that this 258 entity may potentially offer. The value is a sum. 259 This sum initially takes the value zero. Then, for 260 each layer, L, in the range 1 through 7, that this node 261 performs transactions for, 2 raised to (L - 1) is added 262 to the sum. For example, a node which performs only 263 routing functions would have a value of 4 (2^(3-1)). 264 In contrast, a node which is a host offering application 265 services would have a value of 72 (2^(4-1) + 2^(7-1)). 266 Note that in the context of the Internet suite of 267 protocols, values should be calculated accordingly: 269 layer functionality 270 1 physical (e.g., repeaters) 271 2 datalink/subnetwork (e.g., bridges) 272 3 internet (e.g., supports the IP) 273 4 end-to-end (e.g., supports the TCP) 274 7 applications (e.g., supports the SMTP) 276 For systems including OSI protocols, layers 5 and 6 277 may also be counted." 278 ::= { system 7 } 280 -- object resource information 281 -- 282 -- a collection of objects which describe the SNMP entity's 283 -- (statically and dynamically configurable) support of 284 -- various MIB modules. 286 sysORLastChange OBJECT-TYPE 287 SYNTAX TimeStamp 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "The value of sysUpTime at the time of the most recent 292 change in state or value of any instance of sysORID." 293 ::= { system 8 } 295 sysORTable OBJECT-TYPE 296 SYNTAX SEQUENCE OF SysOREntry 297 MAX-ACCESS not-accessible 298 STATUS current 299 DESCRIPTION 300 "The (conceptual) table listing the capabilities of 301 the local SNMP application acting as a command 302 responder with respect to various MIB modules. 303 SNMP entities having dynamically-configurable support 304 of MIB modules will have a dynamically-varying number 305 of conceptual rows." 306 ::= { system 9 } 308 sysOREntry OBJECT-TYPE 309 SYNTAX SysOREntry 310 MAX-ACCESS not-accessible 311 STATUS current 312 DESCRIPTION 313 "An entry (conceptual row) in the sysORTable." 314 INDEX { sysORIndex } 315 ::= { sysORTable 1 } 317 SysOREntry ::= SEQUENCE { 318 sysORIndex INTEGER, 319 sysORID OBJECT IDENTIFIER, 320 sysORDescr DisplayString, 321 sysORUpTime TimeStamp 322 } 324 sysORIndex OBJECT-TYPE 325 SYNTAX INTEGER (1..2147483647) 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "The auxiliary variable used for identifying instances 330 of the columnar objects in the sysORTable." 331 ::= { sysOREntry 1 } 333 sysORID OBJECT-TYPE 334 SYNTAX OBJECT IDENTIFIER 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "An authoritative identification of a capabilities 339 statement with respect to various MIB modules supported 340 by the local SNMP application acting as a command 341 responder." 342 ::= { sysOREntry 2 } 344 sysORDescr OBJECT-TYPE 345 SYNTAX DisplayString 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 "A textual description of the capabilities identified 350 by the corresponding instance of sysORID." 351 ::= { sysOREntry 3 } 353 sysORUpTime OBJECT-TYPE 354 SYNTAX TimeStamp 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "The value of sysUpTime at the time this conceptual 359 row was last instantiated." 360 ::= { sysOREntry 4 } 362 -- the SNMP group 363 -- 364 -- a collection of objects providing basic instrumentation and 365 -- control of an SNMP entity. 367 snmp OBJECT IDENTIFIER ::= { mib-2 11 } 369 snmpInPkts OBJECT-TYPE 370 SYNTAX Counter32 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The total number of messages delivered to the SNMP 375 entity from the transport service." 376 ::= { snmp 1 } 378 snmpInBadVersions OBJECT-TYPE 379 SYNTAX Counter32 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "The total number of SNMP messages which were delivered 384 to the SNMP entity and were for an unsupported SNMP 385 version." 386 ::= { snmp 3 } 388 snmpInBadCommunityNames OBJECT-TYPE 389 SYNTAX Counter32 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The total number of community-based SNMP messages (for 394 example, SNMPv1) delivered to the SNMP entity which 395 used an SNMP community name not known to said entity. 396 Also, implementations which authenticate community-based 397 SNMP messages using check(s) in addition to matching 398 the community name (for example, by also checking 399 whether the message originated from a transport address 400 allowed to use a specified community name) MAY include 401 in this value the number of messages which failed the 402 additional check(s). It is strongly RECOMMENDED that 403 the documentation for any security model which is used 404 to authenticate community-based SNMP messages specify 405 the precise conditions that contribute to this value." 406 ::= { snmp 4 } 408 snmpInBadCommunityUses OBJECT-TYPE 409 SYNTAX Counter32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The total number of community-based SNMP messages (for 414 example, SNMPv1) delivered to the SNMP entity which 415 represented an SNMP operation that was not allowed for 416 the SNMP community named in the message. The precise 417 conditions under which this counter is incremented 418 (if at all) depend on how the SNMP entity implements 419 its access control mechanism and how its applications 420 interact with that access control mechanism. It is 421 strongly RECOMMENDED that the documentation for any 422 access control mechanism which is used to control access 423 to and visibility of MIB instrumentation specify the 424 precise conditions that contribute to this value." 425 ::= { snmp 5 } 427 snmpInASNParseErrs OBJECT-TYPE 428 SYNTAX Counter32 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The total number of ASN.1 or BER errors encountered by 433 the SNMP entity when decoding received SNMP messages." 434 ::= { snmp 6 } 436 snmpEnableAuthenTraps OBJECT-TYPE 437 SYNTAX INTEGER { enabled(1), disabled(2) } 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "Indicates whether the SNMP entity is permitted to 442 generate authenticationFailure traps. The value of this 443 object overrides any configuration information; as such, 444 it provides a means whereby all authenticationFailure 445 traps may be disabled. 447 Note that it is strongly recommended that this object 448 be stored in non-volatile memory so that it remains 449 constant across re-initializations of the network 450 management system." 451 ::= { snmp 30 } 453 snmpSilentDrops OBJECT-TYPE 454 SYNTAX Counter32 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The total number of Confirmed Class PDUs (such as 459 GetRequest-PDUs, GetNextRequest-PDUs, 460 GetBulkRequest-PDUs, SetRequest-PDUs, and 461 InformRequest-PDUs) delivered to the SNMP entity which 462 were silently dropped because the size of a reply 463 containing an alternate Response Class PDU (such as a 464 Response-PDU) with an empty variable-bindings field 465 was greater than either a local constraint or the 466 maximum message size associated with the originator of 467 the request." 468 ::= { snmp 31 } 470 snmpProxyDrops OBJECT-TYPE 471 SYNTAX Counter32 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The total number of Confirmed Class PDUs 476 (such as GetRequest-PDUs, GetNextRequest-PDUs, 477 GetBulkRequest-PDUs, SetRequest-PDUs, and 478 InformRequest-PDUs) delivered to the SNMP entity which 479 were silently dropped because the transmission of 480 the (possibly translated) message to a proxy target 481 failed in a manner (other than a time-out) such that 482 no Response Class PDU (such as a Response-PDU) could 483 be returned." 484 ::= { snmp 32 } 486 -- information for notifications 487 -- 488 -- a collection of objects which allow the SNMP entity, when 489 -- supporting a notification originator application, 490 -- to be configured to generate SNMPv2-Trap-PDUs. 492 snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 } 494 snmpTrapOID OBJECT-TYPE 495 SYNTAX OBJECT IDENTIFIER 496 MAX-ACCESS accessible-for-notify 497 STATUS current 498 DESCRIPTION 499 "The authoritative identification of the notification 500 currently being sent. This variable occurs as 501 the second varbind in every SNMPv2-Trap-PDU and 502 InformRequest-PDU." 503 ::= { snmpTrap 1 } 505 -- ::= { snmpTrap 2 } this OID is obsolete 507 snmpTrapEnterprise OBJECT-TYPE 508 SYNTAX OBJECT IDENTIFIER 509 MAX-ACCESS accessible-for-notify 510 STATUS current 511 DESCRIPTION 512 "The authoritative identification of the enterprise 513 associated with the trap currently being sent. When an 514 SNMP proxy agent is mapping an RFC1157 Trap-PDU 515 into a SNMPv2-Trap-PDU, this variable occurs as the 516 last varbind." 517 ::= { snmpTrap 3 } 519 -- ::= { snmpTrap 4 } this OID is obsolete 521 -- well-known traps 523 snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 } 525 coldStart NOTIFICATION-TYPE 526 STATUS current 527 DESCRIPTION 528 "A coldStart trap signifies that the SNMP entity, 529 supporting a notification originator application, is 530 reinitializing itself and that its configuration may 531 have been altered." 532 ::= { snmpTraps 1 } 534 warmStart NOTIFICATION-TYPE 535 STATUS current 536 DESCRIPTION 537 "A warmStart trap signifies that the SNMP entity, 538 supporting a notification originator application, 539 is reinitializing itself such that its configuration 540 is unaltered." 541 ::= { snmpTraps 2 } 543 -- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 } 544 -- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 } 545 -- are defined in RFC 2233 [RFC2233] 547 authenticationFailure NOTIFICATION-TYPE 548 STATUS current 549 DESCRIPTION 550 "An authenticationFailure trap signifies that the SNMP 551 entity has received a protocol message that is not 552 properly authenticated. While all implementations 553 of SNMP entities MAY be capable of generating this 554 trap, the snmpEnableAuthenTraps object indicates 555 whether this trap will be generated." 556 ::= { snmpTraps 5 } 558 -- Note the egpNeighborLoss notification is defined 559 -- as { snmpTraps 6 } in RFC 1213 561 -- the set group 562 -- 563 -- a collection of objects which allow several cooperating 564 -- command generator applications to coordinate their use of the 565 -- set operation. 567 snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 } 569 snmpSetSerialNo OBJECT-TYPE 570 SYNTAX TestAndIncr 571 MAX-ACCESS read-write 572 STATUS current 573 DESCRIPTION 574 "An advisory lock used to allow several cooperating 575 command generator applications to coordinate their 576 use of the SNMP set operation. 578 This object is used for coarse-grain coordination. 579 To achieve fine-grain coordination, one or more similar 580 objects might be defined within each MIB group, as 581 appropriate." 582 ::= { snmpSet 1 } 584 -- conformance information 586 snmpMIBConformance 587 OBJECT IDENTIFIER ::= { snmpMIB 2 } 589 snmpMIBCompliances 590 OBJECT IDENTIFIER ::= { snmpMIBConformance 1 } 591 snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 } 593 -- compliance statements 595 -- ::= { snmpMIBCompliances 1 } this OID is obsolete 596 snmpBasicCompliance MODULE-COMPLIANCE 597 STATUS deprecated 598 DESCRIPTION 599 "The compliance statement for SNMPv2 entities which 600 implement the SNMPv2 MIB. 602 This compliance statement is replaced by 603 snmpBasicComplianceRev2." 604 MODULE -- this module 605 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup, 606 snmpBasicNotificationsGroup } 608 GROUP snmpCommunityGroup 609 DESCRIPTION 610 "This group is mandatory for SNMPv2 entities which 611 support community-based authentication." 613 ::= { snmpMIBCompliances 2 } 615 snmpBasicComplianceRev2 MODULE-COMPLIANCE 616 STATUS current 617 DESCRIPTION 618 "The compliance statement for SNMP entities which 619 implement this MIB module." 620 MODULE -- this module 621 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup, 622 snmpBasicNotificationsGroup } 624 GROUP snmpCommunityGroup 625 DESCRIPTION 626 "This group is mandatory for SNMP entities which 627 support community-based authentication." 629 GROUP snmpWarmStartNotificationGroup 630 DESCRIPTION 631 "This group is mandatory for an SNMP entity which 632 supports command responder applications, and is 633 able to reinitialize itself such that its 634 configuration is unaltered." 636 ::= { snmpMIBCompliances 3 } 638 -- units of conformance 640 -- ::= { snmpMIBGroups 1 } this OID is obsolete 641 -- ::= { snmpMIBGroups 2 } this OID is obsolete 642 -- ::= { snmpMIBGroups 3 } this OID is obsolete 643 -- ::= { snmpMIBGroups 4 } this OID is obsolete 645 snmpGroup OBJECT-GROUP 646 OBJECTS { snmpInPkts, 647 snmpInBadVersions, 648 snmpInASNParseErrs, 649 snmpSilentDrops, 650 snmpProxyDrops, 651 snmpEnableAuthenTraps } 652 STATUS current 653 DESCRIPTION 654 "A collection of objects providing basic instrumentation 655 and control of an SNMP entity." 656 ::= { snmpMIBGroups 8 } 658 snmpCommunityGroup OBJECT-GROUP 659 OBJECTS { snmpInBadCommunityNames, 660 snmpInBadCommunityUses } 661 STATUS current 662 DESCRIPTION 663 "A collection of objects providing basic instrumentation 664 of a SNMP entity which supports community-based 665 authentication." 666 ::= { snmpMIBGroups 9 } 668 snmpSetGroup OBJECT-GROUP 669 OBJECTS { snmpSetSerialNo } 670 STATUS current 671 DESCRIPTION 672 "A collection of objects which allow several cooperating 673 command generator applications to coordinate their 674 use of the set operation." 675 ::= { snmpMIBGroups 5 } 677 systemGroup OBJECT-GROUP 678 OBJECTS { sysDescr, sysObjectID, sysUpTime, 679 sysContact, sysName, sysLocation, 680 sysServices, 681 sysORLastChange, sysORID, 682 sysORUpTime, sysORDescr } 683 STATUS current 684 DESCRIPTION 685 "The system group defines objects which are common to all 686 managed systems." 687 ::= { snmpMIBGroups 6 } 689 snmpBasicNotificationsGroup NOTIFICATION-GROUP 690 NOTIFICATIONS { coldStart, authenticationFailure } 691 STATUS current 692 DESCRIPTION 693 "The basic notifications implemented by an SNMP entity 694 supporting command responder applications." 695 ::= { snmpMIBGroups 7 } 697 snmpWarmStartNotificationGroup NOTIFICATION-GROUP 698 NOTIFICATIONS { warmStart } 699 STATUS current 700 DESCRIPTION 701 "An additional notification for an SNMP entity supporting 702 command responder applications, if it is able to reinitialize 703 itself such that its configuration is unaltered." 704 ::= { snmpMIBGroups 11 } 706 snmpNotificationGroup OBJECT-GROUP 707 OBJECTS { snmpTrapOID, snmpTrapEnterprise } 708 STATUS current 709 DESCRIPTION 710 "These objects are required for entities 711 which support notification originator applications." 712 ::= { snmpMIBGroups 12 } 714 -- definitions in RFC 1213 made obsolete by the inclusion of a 715 -- subset of the snmp group in this MIB 717 snmpOutPkts OBJECT-TYPE 718 SYNTAX Counter32 719 MAX-ACCESS read-only 720 STATUS obsolete 721 DESCRIPTION 722 "The total number of SNMP Messages which were 723 passed from the SNMP protocol entity to the 724 transport service." 725 ::= { snmp 2 } 727 -- { snmp 7 } is not used 729 snmpInTooBigs OBJECT-TYPE 730 SYNTAX Counter32 731 MAX-ACCESS read-only 732 STATUS obsolete 733 DESCRIPTION 734 "The total number of SNMP PDUs which were 735 delivered to the SNMP protocol entity and for 736 which the value of the error-status field was 737 `tooBig'." 738 ::= { snmp 8 } 740 snmpInNoSuchNames OBJECT-TYPE 741 SYNTAX Counter32 742 MAX-ACCESS read-only 743 STATUS obsolete 744 DESCRIPTION 745 "The total number of SNMP PDUs which were 746 delivered to the SNMP protocol entity and for 747 which the value of the error-status field was 748 `noSuchName'." 749 ::= { snmp 9 } 751 snmpInBadValues OBJECT-TYPE 752 SYNTAX Counter32 753 MAX-ACCESS read-only 754 STATUS obsolete 755 DESCRIPTION 756 "The total number of SNMP PDUs which were 757 delivered to the SNMP protocol entity and for 758 which the value of the error-status field was 759 `badValue'." 760 ::= { snmp 10 } 762 snmpInReadOnlys OBJECT-TYPE 763 SYNTAX Counter32 764 MAX-ACCESS read-only 765 STATUS obsolete 766 DESCRIPTION 767 "The total number valid SNMP PDUs which were delivered 768 to the SNMP protocol entity and for which the value 769 of the error-status field was `readOnly'. It should 770 be noted that it is a protocol error to generate an 771 SNMP PDU which contains the value `readOnly' in the 772 error-status field, as such this object is provided 773 as a means of detecting incorrect implementations of 774 the SNMP." 775 ::= { snmp 11 } 777 snmpInGenErrs OBJECT-TYPE 778 SYNTAX Counter32 779 MAX-ACCESS read-only 780 STATUS obsolete 781 DESCRIPTION 782 "The total number of SNMP PDUs which were delivered 783 to the SNMP protocol entity and for which the value 784 of the error-status field was `genErr'." 785 ::= { snmp 12 } 787 snmpInTotalReqVars OBJECT-TYPE 788 SYNTAX Counter32 789 MAX-ACCESS read-only 790 STATUS obsolete 791 DESCRIPTION 792 "The total number of MIB objects which have been 793 retrieved successfully by the SNMP protocol entity 794 as the result of receiving valid SNMP Get-Request 795 and Get-Next PDUs." 796 ::= { snmp 13 } 798 snmpInTotalSetVars OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS obsolete 802 DESCRIPTION 803 "The total number of MIB objects which have been 804 altered successfully by the SNMP protocol entity as 805 the result of receiving valid SNMP Set-Request PDUs." 806 ::= { snmp 14 } 808 snmpInGetRequests OBJECT-TYPE 809 SYNTAX Counter32 810 MAX-ACCESS read-only 811 STATUS obsolete 812 DESCRIPTION 813 "The total number of SNMP Get-Request PDUs which 814 have been accepted and processed by the SNMP 815 protocol entity." 816 ::= { snmp 15 } 818 snmpInGetNexts OBJECT-TYPE 819 SYNTAX Counter32 820 MAX-ACCESS read-only 821 STATUS obsolete 822 DESCRIPTION 823 "The total number of SNMP Get-Next PDUs which have been 824 accepted and processed by the SNMP protocol entity." 825 ::= { snmp 16 } 827 snmpInSetRequests OBJECT-TYPE 828 SYNTAX Counter32 829 MAX-ACCESS read-only 830 STATUS obsolete 831 DESCRIPTION 832 "The total number of SNMP Set-Request PDUs which 833 have been accepted and processed by the SNMP protocol 834 entity." 835 ::= { snmp 17 } 837 snmpInGetResponses OBJECT-TYPE 838 SYNTAX Counter32 839 MAX-ACCESS read-only 840 STATUS obsolete 841 DESCRIPTION 842 "The total number of SNMP Get-Response PDUs which 843 have been accepted and processed by the SNMP protocol 844 entity." 845 ::= { snmp 18 } 847 snmpInTraps OBJECT-TYPE 848 SYNTAX Counter32 849 MAX-ACCESS read-only 850 STATUS obsolete 851 DESCRIPTION 852 "The total number of SNMP Trap PDUs which have been 853 accepted and processed by the SNMP protocol entity." 854 ::= { snmp 19 } 856 snmpOutTooBigs OBJECT-TYPE 857 SYNTAX Counter32 858 MAX-ACCESS read-only 859 STATUS obsolete 860 DESCRIPTION 861 "The total number of SNMP PDUs which were generated 862 by the SNMP protocol entity and for which the value 863 of the error-status field was `tooBig.'" 864 ::= { snmp 20 } 866 snmpOutNoSuchNames OBJECT-TYPE 867 SYNTAX Counter32 868 MAX-ACCESS read-only 869 STATUS obsolete 870 DESCRIPTION 871 "The total number of SNMP PDUs which were generated 872 by the SNMP protocol entity and for which the value 873 of the error-status was `noSuchName'." 874 ::= { snmp 21 } 876 snmpOutBadValues OBJECT-TYPE 877 SYNTAX Counter32 878 MAX-ACCESS read-only 879 STATUS obsolete 880 DESCRIPTION 881 "The total number of SNMP PDUs which were generated 882 by the SNMP protocol entity and for which the value 883 of the error-status field was `badValue'." 884 ::= { snmp 22 } 886 -- { snmp 23 } is not used 887 snmpOutGenErrs OBJECT-TYPE 888 SYNTAX Counter32 889 MAX-ACCESS read-only 890 STATUS obsolete 891 DESCRIPTION 892 "The total number of SNMP PDUs which were generated 893 by the SNMP protocol entity and for which the value 894 of the error-status field was `genErr'." 895 ::= { snmp 24 } 897 snmpOutGetRequests OBJECT-TYPE 898 SYNTAX Counter32 899 MAX-ACCESS read-only 900 STATUS obsolete 901 DESCRIPTION 902 "The total number of SNMP Get-Request PDUs which 903 have been generated by the SNMP protocol entity." 904 ::= { snmp 25 } 906 snmpOutGetNexts OBJECT-TYPE 907 SYNTAX Counter32 908 MAX-ACCESS read-only 909 STATUS obsolete 910 DESCRIPTION 911 "The total number of SNMP Get-Next PDUs which have 912 been generated by the SNMP protocol entity." 913 ::= { snmp 26 } 915 snmpOutSetRequests OBJECT-TYPE 916 SYNTAX Counter32 917 MAX-ACCESS read-only 918 STATUS obsolete 919 DESCRIPTION 920 "The total number of SNMP Set-Request PDUs which 921 have been generated by the SNMP protocol entity." 922 ::= { snmp 27 } 924 snmpOutGetResponses OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS obsolete 928 DESCRIPTION 929 "The total number of SNMP Get-Response PDUs which 930 have been generated by the SNMP protocol entity." 931 ::= { snmp 28 } 933 snmpOutTraps OBJECT-TYPE 934 SYNTAX Counter32 935 MAX-ACCESS read-only 936 STATUS obsolete 937 DESCRIPTION 938 "The total number of SNMP Trap PDUs which have 939 been generated by the SNMP protocol entity." 940 ::= { snmp 29 } 942 snmpObsoleteGroup OBJECT-GROUP 943 OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames, 944 snmpInBadValues, snmpInReadOnlys, snmpInGenErrs, 945 snmpInTotalReqVars, snmpInTotalSetVars, 946 snmpInGetRequests, snmpInGetNexts, snmpInSetRequests, 947 snmpInGetResponses, snmpInTraps, snmpOutTooBigs, 948 snmpOutNoSuchNames, snmpOutBadValues, 949 snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts, 950 snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps 951 } 952 STATUS obsolete 953 DESCRIPTION 954 "A collection of objects from RFC 1213 made obsolete 955 by this MIB module." 956 ::= { snmpMIBGroups 10 } 958 END 960 3. Notice on Intellectual Property 962 The IETF takes no position regarding the validity or scope of any 963 intellectual property or other rights that might be claimed to 964 pertain to the implementation or use of the technology described in 965 this document or the extent to which any license under such rights 966 might or might not be available; neither does it represent that it 967 has made any effort to identify any such rights. Information on the 968 IETF's procedures with respect to rights in standards-track and 969 standards-related documentation can be found in BCP-11. Copies of 970 claims of rights made available for publication and any assurances of 971 licenses to be made available, or the result of an attempt made to 972 obtain a general license or permission for the use of such 973 proprietary rights by implementors or users of this specification can 974 be obtained from the IETF Secretariat. 976 The IETF invites any interested party to bring to its attention any 977 copyrights, patents or patent applications, or other proprietary 978 rights which may cover technology that may be required to practice 979 this standard. Please address the information to the IETF Executive 980 Director. 982 4. Acknowledgments 984 This document is the product of the SNMPv3 Working Group. Some 985 special thanks are in order to the following Working Group members: 987 Randy Bush 988 Jeffrey D. Case 989 Mike Daniele 990 Rob Frye 991 Lauren Heintz 992 Keith McCloghrie 993 Russ Mundy 994 David T. Perkins 995 Randy Presuhn 996 Aleksey Romanov 997 Juergen Schoenwaelder 998 Bert Wijnen 1000 This version of the document, edited by Randy Presuhn, was initially 1001 based on the work of a design team whose members were: 1003 Jeffrey D. Case 1004 Keith McCloghrie 1005 David T. Perkins 1006 Randy Presuhn 1007 Juergen Schoenwaelder 1009 The previous versions of this document, edited by Keith McCloghrie, 1010 was the result of significant work by four major contributors: 1012 Jeffrey D. Case 1013 Keith McCloghrie 1014 Marshall T. Rose 1015 Steven Waldbusser 1017 Additionally, the contributions of the SNMPv2 Working Group to the 1018 previous versions are also acknowledged. In particular, a special 1019 thanks is extended for the contributions of: 1021 Alexander I. Alten 1022 Dave Arneson 1023 Uri Blumenthal 1024 Doug Book 1025 Kim Curran 1026 Jim Galvin 1027 Maria Greene 1028 Iain Hanson 1029 Dave Harrington 1030 Nguyen Hien 1031 Jeff Johnson 1032 Michael Kornegay 1033 Deirdre Kostick 1034 David Levi 1035 Daniel Mahoney 1036 Bob Natale 1037 Brian O'Keefe 1038 Andrew Pearson 1039 Dave Perkins 1040 Randy Presuhn 1041 Aleksey Romanov 1042 Shawn Routhier 1043 Jon Saperia 1044 Juergen Schoenwaelder 1045 Bob Stewart 1046 Kaj Tesink 1047 Glenn Waters 1048 Bert Wijnen 1050 5. Security Considerations 1052 There are a number of management objects defined in this MIB that 1053 have a MAX-ACCESS clause of read-write. Such objects may be 1054 considered sensitive or vulnerable in some network environments. The 1055 support for SET operations in a non-secure environment without proper 1056 protection can have a negative effect on network operations. 1058 SNMPv1 by itself is not a secure environment. Even if the network 1059 itself is secure (for example by using IPSec), even then, there is no 1060 control as to who on the secure network is allowed to access and 1061 GET/SET (read/change) the objects in this MIB. 1063 It is recommended that the implementors consider the security 1064 features as provided by the SNMPv3 framework. Specifically, the use 1065 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1066 based Access Control Model RFC 2575 [RFC2575] is recommended. 1068 It is then a customer/user responsibility to ensure that the SNMP 1069 entity giving access to an instance of this MIB is properly 1070 configured to give access to the objects only to those principals 1071 (users) that have legitimate rights to indeed GET or SET (change) 1072 them. 1074 6. References 1076 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1077 Identification of Management Information for TCP/IP-based 1078 Internets", STD 16, RFC 1155, May 1990. 1080 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1081 "Simple Network Management Protocol", STD 15, RFC 1157, 1082 May 1990. 1084 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1085 STD 16, RFC 1212, March 1991. 1087 [RFC1213] McCloghrie, K., and M. Rose, "Management Information Base 1088 for Network Management of TCP/IP-based internets: MIB- 1089 II", STD 16, RFC 1213, March 1991. 1091 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 1092 the SNMP", RFC 1215, March 1991. 1094 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1095 "Introduction to Community-based SNMPv2", RFC 1901, 1096 January 1996. 1098 [RFC2233] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1099 MIB using SMIv2", RFC 2233, November 1997. 1101 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1102 "Introduction to Version 3 of the Internet-standard 1103 Network Management Framework", RFC 2570, April 1999. 1105 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1106 Architecture for Describing SNMP Management Frameworks", 1107 RFC 2571, April 1999. 1109 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1110 "Message Processing and Dispatching for the Simple 1111 Network Management Protocol (SNMP)", RFC 2572, April 1112 1999. 1114 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1115 Applications", RFC 2573, April 1999. 1117 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1118 (USM) for version 3 of the Simple Network Management 1119 Protocol (SNMPv3)", RFC 2574, April 1999. 1121 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1122 Access Control Model (VACM) for the Simple Network 1123 Management Protocol (SNMP)", RFC 2575, April 1999. 1125 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1126 Rose, M., and S. Waldbusser, "Structure of Management 1127 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1128 1999. 1130 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1131 Rose, M., and S. Waldbusser, "Textual Conventions for 1132 SMIv2", STD 58, RFC 2579, April 1999. 1134 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1135 Rose, M., and S. Waldbusser, "Conformance Statements for 1136 SMIv2", STD 58, RFC 2580, April 1999. 1138 [RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. 1139 Waldbusser, "Transport Mappings for the Simple Network 1140 Management Protocol", 1141 , August 2000. 1143 [RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. 1144 Waldbusser, "Protocol Operations for the Simple Network 1145 Management Protocol", 1146 , August 2000. 1148 7. Editor's Address 1150 Randy Presuhn 1151 BMC Software, Inc. 1152 2141 North First Street 1153 San Jose, CA 95131 1154 USA 1156 Phone: +1 408 546 1006 1157 EMail: randy_presuhn@bmc.com 1159 8. Changes from RFC 1907 1161 These are the changes from RFC 1907: 1163 - Corrected typo in copyright statement; 1165 - Updated copyright date; 1167 - Updated with new editor's name and contact information; 1169 - Cosmetic fixes to layout and typography; 1171 - Changed title; 1173 - Replace introduction with current MIB boilerplate; 1174 - Updated references; 1176 - Fixed typo in sysORUpTime; 1178 - Re-worded description of snmpSilentDrops; 1180 - Updated reference to RFC 1573 to 2233; 1182 - Added IPR boilerplate as required by RFC 2026; 1184 - Weakened authenticationFailure description from MUST to 1185 MAY, clarified that it pertains to all SNMP entities; 1187 - Clarified descriptions of snmpInBadCommunityNames and 1188 snmpInBadCommunityUses; 1190 - Updated module-identity and contact information; 1192 - Updated the acknowledgements section; 1194 - Replaced references to "manager role", "agent role" and 1195 "SNMPv2 entity" with appropriate terms from RFC 2571; 1197 - Updated document headers and footers; 1199 - Added security considerations, based on current 1200 recommendations for MIB modules. 1202 - Added NOTIFICATION-GROUP and OBJECT-GROUP constructs for 1203 NOTIFICATION-TYPEs and OBJECT-TYPEs that were left 1204 unreferenced in RFC 1907. 1206 - Fixed typos in sysServices DESCRIPTION. 1208 - Changed description of snmpProxyDrops to use terms from 1209 architecture. 1211 - Changed value used in example for sysObjectID. 1213 - Added an abstract. 1215 - Deprecated the snmpBasicCompliance MODULE-COMPLIANCE, and 1216 added the snmpBasicComplianceRev2 MODULE-COMPLIANCE to take 1217 its place. 1219 9. Issues 1221 This section is to be deleted when it is time to publish this 1222 document as an RFC. The issue labels are the same as those used in 1223 the on-line issues list at 1224 ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1907/index.html 1226 1907-01 Done; title changed. 1228 1907-02 Done; replaced introduction with current MIB 1229 boilerplate. 1231 1907-03 Done; resolution was to make no change. 1233 1907-04 Done; replaced occurrences of "SNMPv2 entity", 1234 "manager role", and "agent role" with appropriate 1235 terms from architecture. 1237 1907-05 Done; typo fixed. 1239 1907-06 Done; resolution was to make no change. 1241 1907-07 Done; description of snmpSilentDrops updated. 1243 1907-08 Done; reference to RFC 1573 replaced with reference to 1244 RFC 2233. 1246 1907-09 Done; resolution was to make no change. 1248 1907-10 Done; resolution was to make no change. 1250 1907-11 Done; resolution was to make no change. 1252 1907-12 Done; added security considerations based on 1253 recommended text from http://www.ops.ietf.org/ 1255 1907-13 Done; references and acknowledgements updated. 1257 1907-14 Done; IPR boilerplate aligned with RFC 2026. 1259 1907-15 Done; authenticationFailure weakened to MAY but 1260 permitted for all protocol versions. 1262 1907-16 Done; resolution was to make no change. 1264 1907-17 Done; clarified descriptions of 1265 snmpInBadCommunityNames and snmpInBadCommunityUses. 1267 1907-18 Done; resolution was to make no change. 1269 1907-19 Done; conformance material added. The 1270 snmpBasicCompliance MODULE-COMPLIANCE was deprecated, 1271 and the snmpBasicComplianceRev2 MODULE-COMPLIANCE was 1272 added. 1274 1907-20 Done; resolution was to make no change. 1276 1907-21 Done; resolution was to make no change. 1278 1907-22 Done; abstract added. 1280 10. Full Copyright Statement 1282 Copyright (C) The Internet Society (2000). All Rights Reserved. 1284 This document and translations of it may be copied and furnished to 1285 others, and derivative works that comment on or otherwise explain it 1286 or assist in its implementation may be prepared, copied, published 1287 and distributed, in whole or in part, without restriction of any 1288 kind, provided that the above copyright notice and this paragraph are 1289 included on all such copies and derivative works. However, this 1290 document itself may not be modified in any way, such as by removing 1291 the copyright notice or references to the Internet Society or other 1292 Internet organizations, except as needed for the purpose of 1293 developing Internet standards in which case the procedures for 1294 copyrights defined in the Internet Standards process must be 1295 followed, or as required to translate it into languages other than 1296 English. 1298 The limited permissions granted above are perpetual and will not be 1299 revoked by the Internet Society or its successors or assigns. 1301 This document and the information contained herein is provided on an 1302 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1303 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1304 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1305 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1306 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.