idnits 2.17.1 draft-ietf-mpls-tc-mib-03.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 206 has weird spacing: '...lly the defau...' -- 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 (January 2002) is 8136 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 425, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 452, but no explicit reference was found in the text == Unused Reference: 'RFC3036' is defined on line 517, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 521, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 526, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 530, 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 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** 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) ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) Summary: 16 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: July 2002 4 Joan Cucchiara 5 Crescent Networks 7 Cheenu Srinivasan 8 Parama Networks, Inc. 10 Arun Viswanathan 11 Force10 Networks, Inc. 13 Hans Sjostrand 14 ipUnplugged 16 January 2002 18 Definition of Textual Conventions and OBJECT-IDENTITIES for 19 Multiprotocol Label Switching (MPLS) Management 21 draft-ietf-mpls-tc-mib-03.txt 23 Status of this Memo 25 This document is an Internet-Draft and is in full 26 conformance with all provisions of Section 10 of RFC 2026. 28 Internet-Drafts are working documents of the Internet 29 Engineering Task Force (IETF), its areas, and its working 30 groups. Note that other groups may also distribute working 31 documents as Internet-Drafts. 33 Internet-Drafts are draft documents valid for a maximum of 34 six months and may be updated, replaced, or obsoleted by 35 other documents at any time. It is inappropriate to use 36 Internet-Drafts as reference material or to cite them other 37 than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be 43 accessed at http://www.ietf.org/shadow.html. 45 Abstract 47 This memo describes Textual Conventions and OBJECT- 48 IDENTITIES common to the Management Information Bases 49 (MIBs) for managing Multiprotocol Label Switching (MPLS) 50 networks. 52 Table of Contents 54 1. Introduction .............................................. 2 55 2. The SNMP Management Framework ............................. 2 56 3. MPLS TC MIB Definitions ................................... 3 57 4. Security Considerations ................................... 9 58 5. References ................................................ 9 59 6. Authors' Addresses ........................................ 11 60 7. Full Copyright Statement .................................. 12 62 1. Introduction 64 This memo defines a portion of the Management Information 65 Base (MIB) for use with network management protocols in the 66 Internet community. In particular, it defines Textual 67 Conventions used in IETF MPLS and MPLS-related MIBs. 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 70 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 71 and "OPTIONAL" in this document are to be interpreted as 72 described in RFC 2119, reference [RFC2119]. 74 For an introduction to the concepts of MPLS, see [RFC3031]. 76 2. The SNMP Management Framework 78 The SNMP Management Framework presently consists of five 79 major components: 81 - An overall architecture, described in RFC 2571 82 [RFC2571]. 84 - Mechanisms for describing and naming objects and events 85 for the purpose of management. The first version of 86 this Structure of Management Information (SMI) is 87 called SMIv1 and described in STD 16, RFC 1155 88 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 89 [RFC1215]. The second version, called SMIv2, is 90 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 91 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 93 - Message protocols for transferring management 94 information. The first version of the SNMP message 95 protocol is called SNMPv1 and described in STD 15, RFC 96 1157 [RFC1157]. A second version of the SNMP message 97 protocol, which is not an Internet standards track 98 protocol, is called SNMPv2c and described in RFC 1901 100 [RFC1901] and RFC 1906 [RFC1906]. The third version of 101 the message protocol is called SNMPv3 and described in 102 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 103 [RFC2574]. 105 - Protocol operations for accessing management 106 information. The first set of protocol operations and 107 associated PDU formats is described in STD 15, RFC 1157 108 [RFC1157]. A second set of protocol operations and 109 associated PDU formats is described in RFC 1905 110 [RFC1905]. 112 - A set of fundamental applications described in RFC 2573 113 [RFC2573] and the view-based access control mechanism 114 described in RFC 2575 [RFC2575]. 116 A more detailed introduction to the current SNMP Management 117 Framework can be found in RFC 2570 [RFC2570]. 119 Managed objects are accessed via a virtual information 120 store, termed the Management Information Base or MIB. 121 Objects in the MIB are defined using the mechanisms defined 122 in the SMI. 124 This memo specifies a MIB module that is compliant to the 125 SMIv2. A MIB conforming to the SMIv1 can be produced 126 through the appropriate translations. The resulting 127 translated MIB must be semantically equivalent, except 128 where objects or events are omitted because no translation 129 is possible (use of Counter64). Some machine readable 130 information in SMIv2 will be converted into textual 131 descriptions in SMIv1 during the translation process. 132 However, this loss of machine readable information is not 133 considered to change the semantics of the MIB. 135 3. MPLS TC MIB Definitions 137 MPLS-TC-MIB DEFINITIONS ::= BEGIN 139 IMPORTS 140 MODULE-IDENTITY, Unsigned32, Integer32 141 FROM SNMPv2-SMI 142 transmission 143 FROM RFC1213-MIB 144 TEXTUAL-CONVENTION 145 FROM SNMPv2-TC; 147 mplsTCMIB MODULE-IDENTITY 148 LAST-UPDATED 149 "200101041200Z" -- 4 January 2002 12:00:00 GMT 150 ORGANIZATION 151 "Multiprotocol Label Switching (MPLS) Working Group" 152 CONTACT-INFO 153 " Thomas D. Nadeau 154 Cisco Systems, Inc. 155 tnadeau@cisco.com 157 Joan Cucchiara 158 Crescent Networks 159 jcucchiara@crescentnetworks.com 161 Cheenu Srinivasan 162 Parama Networks, Inc. 163 cheenu@paramanet.com 165 Arun Viswanathan 166 Force10 Networks, Inc. 167 arun@force10networks.com 169 Hans Sjostrand 170 ipUnplugged 171 hans@ipunplugged.com 173 Email comments to the MPLS WG Mailing List at 174 mpls@uu.net." 175 DESCRIPTION 176 "This MIB module defines Textual Conventions and 177 OBJECT-IDENTITIES for use in documents defining 178 management information bases (MIBs) for managing 179 MPLS networks." 181 -- Revision history. 183 REVISION 184 "200101041200Z" -- 4 January 2002 12:00:00 GMT 185 DESCRIPTION 186 "Initial version published as part of RFC XXXX." 187 ::= { mplsMIB 1 } 189 -- This object identifier needs to be assigned by IANA. 190 -- Since mpls has been assigned an ifType of 166 we recommend 191 -- that this OID be 166 as well. 193 mplsMIB OBJECT IDENTIFIER 194 ::= { transmission xxx } 196 -- Textual Conventions (sorted alphabetically). 198 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION 199 STATUS current 200 DESCRIPTION 201 "The VCI value for a VCL. The maximum VCI value 202 cannot exceed the value allowable by 203 atmInterfaceMaxVciBits defined in ATM-MIB. The 204 minimum value is 32, values 0 to 31 are reserved 205 for other uses by the ITU and ATM Forum. 32 is 206 typically the default value for the Control VC." 207 REFERENCE 208 "Definitions of Textual Conventions and OBJECT- 209 IDENTITIES for ATM Management, RFC 2514, Feb. 210 1999." 211 SYNTAX Integer32 (32..65535) 213 MplsBitRate ::= TEXTUAL-CONVENTION 214 DISPLAY-HINT "d" 215 STATUS current 216 DESCRIPTION 217 "An estimate of bandwidth in units of 1,000 bits per 218 second. If this object reports a value of 'n' then 219 the rate of the object is somewhere in the range of 220 'n-500' to 'n+499'. For objects which do not vary 221 in bit rate, or for those where no accurate 222 estimation can be made, this object should contain 223 the nominal bit rate." 224 SYNTAX Integer32 (1..2147483647) 226 MplsBurstSize ::= TEXTUAL-CONVENTION 227 DISPLAY-HINT "d" 228 STATUS current 229 DESCRIPTION 230 "The number of octets of MPLS data that the stream 231 may send back-to-back without concern for 232 policing." 233 SYNTAX Unsigned32 (1..4294967295) 235 MplsExtendedTunnelId ::= TEXTUAL-CONVENTION 236 STATUS current 237 DESCRIPTION 238 "A unique identifier for an MPLS Tunnel. This MAY 239 represent an IpV4 address of the ingress or egress 240 LSR for the tunnel. This value is derived from the 241 Extended Tunnel Id in RSVP or the Ingress Router ID 242 for CR-LDP." 243 REFERENCE 244 "1. Awduche, D., et al., RSVP-TE: Extensions to RSVP 245 for LSP Tunnels, RFC 3209, December 2001. 246 2. Constraint-Based LSP Setup using LDP, Jamoussi, 247 B., et al., draft-ietf-mpls-cr-ldp-06.txt, November 248 2001." 250 SYNTAX Unsigned32 252 MplsInitialCreationSource ::= TEXTUAL-CONVENTION 253 STATUS current 254 DESCRIPTION 255 "The entity that originally created the object in 256 question. The values of this enumeration are 257 defined as follows: 259 other(1) - This is used when an entity which has not 260 been enumerated in this textual convention but 261 which is known by the agent. 263 snmp(2) - The Simple Network Management Protocol was 264 used to configure this object initially. 266 ldp(3 - The Label Distribution Protocol was used to 267 configure this object initially. 269 rsvp(4) - The Resource Reservation Protocol was used 270 to configure this object initially. 272 crldp(5) - The Constraint-Based Label Distribution 273 Protocol was used to configure this object 274 initially. 276 policyAgent(6) - A policy agent (perhaps in 277 combination with one of the above protocols) was 278 used to configure this object initially. 280 unknown(7) - the agent cannot discern which 281 component created the object." 282 SYNTAX INTEGER { 283 other(1), 284 snmp(2), 285 ldp(3), 286 rsvp(4), 287 crldp(5), 288 policyAgent(6), 289 unknown (7) 290 } 292 MplsLSPID ::= TEXTUAL-CONVENTION 293 STATUS current 294 DESCRIPTION 295 "An identifier that is assigned to each LSP and is 296 used to uniquely identify it. This is assigned at 297 the head end of the LSP and can be used by all LSRs 298 to identify this LSP. This value is piggybacked by 299 the signaling protocol when this LSP is signaled 300 within the network. This identifier can then be 301 used at each LSR to identify which labels are being 302 swapped to other labels for this LSP. For IPv4 303 addresses this results in a 6-octet long cookie." 304 SYNTAX OCTET STRING (SIZE (0..31)) 306 MplsLabel ::= TEXTUAL-CONVENTION 307 STATUS current 308 DESCRIPTION 309 "This value represents an MPLS label as defined in 310 [RFC3031], [RFC3032], [RFC3034] and [RFC3035]." 311 REFERENCE 312 "1. Multiprotocol Label Switching Architecture, Rosen 313 et al, RFC 3031, August 1999. 314 2. MPLS Label Stack Encoding, Rosen et al, RFC 3032, 315 January 2001. 316 3. Use of Label Switching on Frame Relay Networks, 317 Conta et al, RFC 3034, January 2001. 318 4. MPLS using LDP and ATM VC switching, Davie et al, 319 RFC 3035, January 2001." 320 SYNTAX Unsigned32 (0..4294967295) 322 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 323 STATUS current 324 DESCRIPTION 325 "The value of an network layer or data link layer 326 address." 327 SYNTAX OCTET STRING (SIZE (0..64)) 329 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 330 STATUS current 331 DESCRIPTION 332 "The LDP identifier is a six octet quantity which is 333 used to identify an Label Switch Router (LSR) label 334 space. 336 The first four octets identify the LSR and must be a 337 globally unique value, such as a 32-bit router ID 338 assigned to the LSR, and the last two octets 339 identify a specific label space within the LSR." 340 SYNTAX OCTET STRING (SIZE (6)) 342 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 343 STATUS current 344 DESCRIPTION 345 "The Layer 2 label types which are defined for MPLS 346 LDP/CRLDP are generic(1), atm(2), or 347 frameRelay(3)." 348 SYNTAX INTEGER { 349 generic(1), 350 atm(2), 351 frameRelay(3) 352 } 354 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 355 STATUS current 356 DESCRIPTION 357 "The Label Switch Router (LSR) identifier is the 358 first 4 bytes of the Label Distribution Protocol 359 (LDP) identifier." 360 SYNTAX OCTET STRING (SIZE (4)) 362 MplsPathIndex ::= TEXTUAL-CONVENTION 363 STATUS current 364 DESCRIPTION 365 "A unique identifier used to identify a specific path 366 used by a tunnel." 367 SYNTAX Unsigned32 369 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION 370 STATUS current 371 DESCRIPTION 372 "A unique identifier used to identify a specific path 373 used by a tunnel. If this value is set to 0, it 374 indicates that no path is in use." 375 SYNTAX Unsigned32 377 MplsPortNumber ::= TEXTUAL-CONVENTION 378 STATUS current 379 DESCRIPTION 380 "A TCP or UDP port number. Along with an IP address 381 identifies a stream of IP traffic uniquely." 382 SYNTAX Integer32 (0..65535) 384 MplsTunnelAffinity ::= TEXTUAL-CONVENTION 385 STATUS current 386 DESCRIPTION 387 "Include-any, include-all, or exclude-all constraint 388 for link selection." 389 SYNTAX Unsigned32 391 MplsTunnelIndex ::= TEXTUAL-CONVENTION 392 STATUS current 393 DESCRIPTION 394 "Index into mplsTunnelTable." 395 SYNTAX Integer32 (1..65535) 397 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION 398 STATUS current 399 DESCRIPTION 400 "Instance index into mplsTunnelTable." 401 SYNTAX Unsigned32 (0..65535) 403 END 405 4. Security Considerations 407 This memo defines textual conventions and object identities 408 for use in MPLS MIB modules. Security issues for these MIB 409 modules are addressed in the memos defining those modules. 411 5. References 413 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 414 Identification of Management Information for 415 TCP/IP-based Internets", STD 16, RFC 1155, 416 May 1990. 418 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 419 Davin, "Simple Network Management Protocol", 420 STD 15, RFC 1157, May 1990. 422 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 423 Definitions", STD 16, RFC 1212, March 1991. 425 [RFC1213] McCloghrie, K, and M. Rose, "Management 426 Information Base for Network Management of 427 TCP/IP Based Internets", RFC 1213, March 428 1991. 430 [RFC1215] M. Rose, "A Convention for Defining Traps 431 for use with the SNMP", RFC 1215, March 432 1991. 434 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 435 Waldbusser, "Introduction to Community-based 436 SNMPv2", RFC 1901, January 1996. 438 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 439 Waldbusser, "Protocol Operations for Version 440 2 of the Simple Network Management Protocol 441 (SNMPv2)", RFC 1905, January 1996. 443 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 444 Waldbusser, "Transport Mappings for Version 445 2 of the Simple Network Management Protocol 446 (SNMPv2)", RFC 1906, January 1996. 448 [RFC2119] Bradner, S., "Key words for use in RFCs to 449 Indicate Requirement Levels", BCP 14, RFC 450 2119, March 1997. 452 [RFC2514] Noto, et. al., "Definitions of Textual 453 Conventions and OBJECT-IDENTITIES for ATM 454 Management", RFC 2514, Feb. 1999 456 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 457 Stewart, "Introduction to Version 3 of the 458 Internet-standard Network Management 459 Framework", RFC 2570, April 1999. 461 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 462 "An Architecture for Describing SNMP 463 Management Frameworks", RFC 2571, April 464 1999. 466 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 467 Wijnen, "Message Processing and Dispatching 468 for the Simple Network Management Protocol 469 (SNMP)", RFC 2572, April 1999. 471 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 472 Applications", RFC 2573, April 1999. 474 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 475 Security Model (USM) for version 3 of the 476 Simple Network Management Protocol 477 (SNMPv3)", RFC 2574, April 1999. 479 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 480 "View-based Access Control Model (VACM) for 481 the Simple Network Management Protocol 482 (SNMP)", RFC 2575, April 1999. 484 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 485 J., Case, J., Rose, M., and S. Waldbusser, 486 "Structure of Management Information Version 487 2 (SMIv2)", STD 58, RFC 2578, April 1999. 489 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 490 J., Case, J., Rose, M., and S. Waldbusser, 491 "Textual Conventions for SMIv2", STD 58, RFC 492 2579, April 1999. 494 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 495 J., Case, J., Rose, M., and S. Waldbusser, 496 "Conformance Statements for SMIv2", STD 58, 497 RFC 2580, April 1999. 499 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 500 "Multiprotocol Label Switching 501 Architecture", RFC 3031, August 1999. 503 [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., 504 Farinacci, D., Federokow, G., Li, T., and A. 505 Conta, "MPLS Label Stack Encoding", RFC 506 3032, January 2001. 508 [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of 509 Label Switching on Frame Relay Networks 510 Specification", RFC 3034, January 2001. 512 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., 513 Rosen, E., Swallow, G., Rekhter, Y., and P. 514 Doolan, "MPLS using LDP and ATM VC 515 switching", RFC 3035, January 2001. 517 [RFC3036] Anderson, L., Doolan, P., Feldman, N., 518 Fredette, A., and B. Thomas, "LDP 519 Specification", RFC 3036, January 2001. 521 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 522 Srinivasan, V., and G. Swallow, "RSVP-TE: 523 Extensions to RSVP for LSP Tunnels", RFC 524 3209, December 2001. 526 [Assigned] Reynolds, J., and J. Postel, "Assigned 527 Numbers", RFC 1700, October 1994. See also: 528 http://www.iana.org/assignments/smi-numbers 530 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP 531 Setup using LDP", draft-ietf-mpls-cr-ldp- 532 06.txt, November 2001." 534 6. Authors' Addresses 536 Thomas D. Nadeau 537 Cisco Systems, Inc. 538 250 Apollo Drive 539 Chelmsford, MA 01824 540 Phone: +1-978-244-3051 541 Email: tnadeau@cisco.com 543 Joan Cucchiara 544 Crescent Networks 545 900 Chelmsford Street 546 Lowell, MA 01851 547 Phone: +1-978-275-3183 548 email: jcucchiara@crescentnetworks.com 550 Cheenu Srinivasan 551 Parama Networks, Inc. 552 1030 Broad Street 553 Shrewsbury, NJ 07702 554 Phone: +1-732-544-9120 x731 555 Email: cheenu@paramanet.com 557 Arun Viswanathan 558 Force10 Networks, Inc. 559 1440 McCarthy Blvd 560 Milpitas, CA 95035 561 Phone: +1-408-571-3516 562 Email: arun@force10networks.com 564 Hans Sjostrand 565 ipUnplugged 566 P.O. Box 101 60 567 S-121 28 Stockholm, Sweden 568 Phone: +46-8-725-5930 569 Email: hans@ipunplugged.com 571 7. Full Copyright Statement 573 Copyright (C) The Internet Society (2001). All Rights 574 Reserved. 576 This document and translations of it may be copied and 577 furnished to others, and derivative works that comment on 578 or otherwise explain it or assist in its implementation may 579 be prepared, copied, published and distributed, in whole or 580 in part, without restriction of any kind, provided that the 581 above copyright notice and this paragraph are included on 582 all such copies and derivative works. However, this 583 document itself may not be modified in any way, such as by 584 removing the copyright notice or references to the Internet 585 Society or other Internet organizations, except as needed 586 for the purpose of developing Internet standards in which 587 case the procedures for copyrights defined in the Internet 588 Standards process must be followed, or as required to 589 translate it into languages other than English. 591 The limited permissions granted above are perpetual and 592 will not be revoked by the Internet Society or its 593 successors or assigns. This document and the information 594 contained herein is provided on an "AS IS" basis and THE 595 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 596 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 597 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 598 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 599 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 600 PURPOSE.