idnits 2.17.1 draft-ietf-mpls-bundle-mib-03.txt: ** The Abstract section seems to be numbered 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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? == 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. ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (June 2002) is 7986 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) ** 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 2401 (Obsoleted by RFC 4301) ** 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 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-ARCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' Summary: 20 errors (**), 0 flaws (~~), 3 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft Meriton Networks 4 Expires: December 2002 5 Sudheer Dharanikota 6 Nayna Networks 8 Thomas D. Nadeau 9 Cisco Systems 11 Jonathan P. Lang 12 Calient Networks 14 June 2002 16 Link Bundling Management Information Base 18 draft-ietf-mpls-bundle-mib-03.txt 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 RFC 2026. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that other 27 groups may also distribute working documents as Internet- Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet- Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Table of Contents 42 1. Abstract ..................................................... 2 43 2. Introduction ................................................. 2 44 3. Terminology .................................................. 3 45 4. The SNMP Management Framework ................................ 3 46 5. Feature Checklist ............................................ 4 47 6. Outline ...................................................... 5 48 6.1. Summary of Link Bundling MIB ................................. 5 49 7. Brief Description of MIB Objects ............................. 6 50 7.1. teLinkTable .................................................. 6 51 7.2. teLinkDescriptorTable ........................................ 6 52 7.3. teLinkOspfTeTable ............................................ 6 53 7.4. teLinkSrlgTable .............................................. 6 54 7.5. teLinkBandwidthTable ......................................... 7 55 7.6. componentLinkTable ........................................... 7 56 7.7. componentLinkDescriptorTable ................................. 7 57 7.8. componentLinkBandwidthTable .................................. 7 58 8. Example of Bundled Link Setup ................................ 7 59 9. Application of the Interfaces Group to TE Links .............. 11 60 9.1 Support of the TE Link Layer by ifTable ...................... 12 61 9.2 Using ifStackTable ........................................... 13 62 10. Link Bundling MIB Definitions ................................ 15 63 11. Security Considerations ...................................... 50 64 12. Acknowledgments .............................................. 51 65 13. References ................................................... 51 66 14. Authors' Addresses ........................................... 54 67 15. Full Copyright Statement ..................................... 54 69 1. Abstract 71 This memo defines a portion of the Management Information Base (MIB) 72 for use with network management protocols in the Internet community. 73 In particular, it describes managed objects for modeling link bun- 74 dling as described in the Link Bundling in MPLS Traffic Engineering 75 Internet Draft. 77 2. Introduction 79 OSPF [OSPF], Generalized MPLS (GMPLS) [GMPLS] and the Link Management 80 Protocol (LMP) [LMP] use the concept of traffic engineering (TE) 81 links to abstract link properties. The effect of this approach is the 82 reduction of the amount of routing information exchanged in the net- 83 work, which improves routing scalability. In addition, the use of TE 84 link allows the implementation of new capabilities such as link pro- 85 tection. 87 We present in this document a MIB that can be used to manage TE links 88 and their extension, the bundled link. This MIB enable both the con- 89 figuration and the performance monitoring of TE links and bundled 90 link. 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC 2119, reference 95 [RFC2119]. 97 3. Terminology 99 This document uses terminology from the documents describing link 100 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 102 The link bundling feature is designed to aggregate one or more simi- 103 lar entities between a node pair into a bundled link [BUNDLING]. In 104 the document, those entities are referred to as TE links. A TE link 105 is a subinterface capable of carrying MPLS traffic engineered 106 traffic. A TE Link may be comprised of only one underlying component 107 links. In cases where more than one component link is to be com- 108 bined, multiple component links should be created with differing 109 priorities to indicate hot-standby or parallel utilization. 111 A bundled link is just another kind of Traffic Engineering (TE) link 112 (see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the 113 traffic of a group of one or more TE links. There should be more than 114 one TE Link in a link bundle, but this is not a requirement. Furth- 115 ermore, if there are more than one TE link in a link bundle at some 116 time, and at some point later, all but one of the links are deleted, 117 the agent may choose to either delete the link bundle, or it may 118 choose to leave it intact. Traffic counters on a link bundle are 119 cumulative for all subinterfaces which it binds together. 121 4. The SNMP Management Framework 123 The SNMP Management Framework presently consists of five major com- 124 ponents: 126 - An overall architecture, described in RFC 2571 [RFC2571]. 128 Mechanisms for describing and naming objects and events for the 129 purpose of management. The first version of this Structure of 130 Management Information (SMI) is called SMIv1 and described in 131 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 132 1215 [RFC1215]. The second version, called SMIv2, is described 133 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 134 STD 58, RFC 2580 [RFC2580]. 136 - Message protocols for transferring management information. The 137 first version of the SNMP message protocol is called SNMPv1 and 138 described in STD 15, RFC 1157 [RFC1157]. A second version of 139 the SNMP message protocol, which is not an Internet standards 140 track protocol, is called SNMPv2c and described in RFC 1901 141 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 142 message protocol is called SNMPv3 and described in RFC 1906 143 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 145 - Protocol operations for accessing management information. The 146 first set of protocol operations and associated PDU formats is 147 described in STD 15, RFC 1157 [RFC1157]. A second set of 148 protocol operations and associated PDU formats is described in 149 RFC 1905 [RFC1905]. 151 - A set of fundamental applications described in RFC 2573 152 [RFC2573] and the view-based access control mechanism described 153 in RFC 2575 [RFC2575]. 155 A more detailed introduction to the current SNMP Management Framework 156 can be found in RFC 2570 [RFC2570]. 158 Managed objects are accessed via a virtual information store, termed 159 the Management Information Base or MIB. Objects in the MIB are 160 defined using the mechanisms defined in the SMI. 162 This memo specifies a MIB module that is compliant to the SMIv2. A 163 MIB conforming to the SMIv1 can be produced through the appropriate 164 translations. The resulting translated MIB must be semantically 165 equivalent, except where objects or events are omitted because no 166 translation is possible (use of Counter64). Some machine readable 167 information in SMIv2 will be converted into textual descriptions in 168 SMIv1 during the translation process. However, this loss of machine 169 readable information is not considered to change the semantics of the 170 MIB. 172 5. Feature Checklist 174 The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the 175 following requirements and constraints: 177 - The MIB supports the management of TE links, including bundled 178 links. 180 - Support is provided for configuration of traffic engineering 181 parameters associated with TE links. 183 - The MIB is used to monitor the priority-based component link 184 and TE link bandwidth values. 186 6. Outline 188 Configuring bundled links involves the following steps: 190 - Creating a bundled link. 192 - Creating TE links. 194 - Optionally specifying the shared risk link groups associated with 195 the TE links. 197 - Configuring the component links including the bandwidth 198 parameters and associating the component links with the 199 appropriate TE link. 201 - Associating the TE links with the appropriate bundled link. 203 6.1. Summary of Link Bundling MIB 205 The MIB objects for performing these actions consist of the following 206 tables: 208 - The TE link table (teLinkTable), which is used to 209 specify TE links, including bundled links, and their generic 210 traffic engineering parameters. 212 - The TE link descriptor table (teLinkDescriptorTable), which is 213 used to enumerate the TE link descriptors. 215 - The TE link OSPF traffic engineering table 216 (teLinkOspfTeTable), which is used for configuring OSPF 217 traffic engineering parameters associated with TE links. 219 - The shared risk link group (SRLG) table (teLinkSrlgTable), 220 which is used to specify the SRLGs associated with TE links. 222 - The TE link bandwidth table (teLinkBandwidthTable), 223 which is used for reporting priority-based bandwidth values 224 associated with TE links. 226 - The component link table (componentLinkTable), which is 227 used to identify the component links that are associated 228 with the TE links and specify the component link generic 229 traffic engineering parameters. 231 - The component link descriptor table 232 (componentLinkDescriptorTable), which is used to enumerate 233 the component link descriptors. 235 - The component link bandwidth table 236 (componentLinkBandwidthTable), which is used to report 237 priority-based bandwidth values associated with component links. 239 These tables are described in the subsequent sections. 241 7. Brief Description of MIB Objects 243 Sections 7.1-7.5 describe objects pertaining to TE links. The MIB 244 objects were derived from the link bundling document [BUNDLING]. 246 7.1. teLinkTable 248 This table represents the TE links, including bundled links. 250 7.2. teLinkDescriptorTable 252 This table represents the TE link descriptors. 254 7.3. teLinkOspfTeTable 256 This table represents the OSPF traffic engineering parameters that 257 are associated with the TE links. 259 7.4. teLinkSrlgTable 261 This table represents the shared risk link groups (SRLGs) associated 262 with TE links. 264 7.5. teLinkBandwidthTable 266 This table specifies the priority-based bandwidth traffic engineering 267 parameters associated with TE links. 269 7.6. componentLinkTable 271 This table enumerates the component links and their association with 272 TE link. 274 7.7. componentLinkDescriptorTable 276 This table enumerates the link descriptors that each component link 277 supports. 279 7.8. componentLinkBandwidthTable 281 The component link bandwidth table specifies the priority-based 282 bandwidth values associated with the component links. 284 8. Example of Bundled Link Setup 286 In this section we provide a brief example of using the MIB 287 objects described in section 10 to set up a bundled link. 288 While this example is not meant to illustrate every 289 nuance of the MIB, it is intended as an aid to understanding some 290 of the key concepts. It is meant to be read after going through the 291 MIB itself. 293 Suppose that one would like to manually create a bundled link 294 out of two 1:1 TE links. Assume that the bundled link is associated 295 with SRLGs 10 and 50. Finally, let the component links be port 296 entity interfaces (lambdas). The following example illustrates which 297 rows and corresponding objects might be created to accomplish this. 299 First, a bundled link entry is created. An ifEntry with the same 300 ifIndex and with ifType teLink needs to be created beforehand. 302 In teLinkTable: 303 { 304 ifIndex = 25, 305 teLinkIpAddrType = unknown(0), 306 teLinkRowStatus = createAndGo(4) 307 } 309 In ifStackTable: 310 { 311 ifStackHigherLayer = 0, 312 ifStackLowerLayer = 25, 313 ifStackStatus = createAndGo(4) 314 } 316 Next, the two TE links are created. 318 In teLinkTable: 319 { 320 ifIndex = 20, 321 teLinkIpAddrType = unknown(0), 322 teLinkMetric = 5, 323 teLinkResourceClass = 3, 324 teLinkRowStatus = createAndWait(5) 325 } 327 In ifStackTable: 328 { 329 ifStackHigherLayer = 25, 330 ifStackLowerLayer = 20, 331 ifStackStatus = createAndGo(4) 332 } 334 In teLinkTable: 335 { 336 ifIndex = 21, 337 teLinkIpAddrType = unknown(0), 338 teLinkMetric = 5, 339 teLinkResourceClass = 3, 340 teLinkRowStatus = createAndWait(5) 341 } 343 In ifStackTable: 344 { 345 ifStackHigherLayer = 25, 346 ifStackLowerLayer = 21, 347 ifStackStatus = createAndGo(4) 348 } 350 The OSPF traffic engineering parameters are configured for the 351 TE links. 353 In teLinkOspfTeTable: 354 { 355 ifIndex = 20, 356 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 357 teLinkRowStatus = createAndGo(4) 358 } 360 In teLinkOspfTeTable: 361 { 362 ifIndex = 21, 363 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 364 teLinkRowStatus = createAndGo(4) 365 } 367 We assign SRLGs to the TE links. 369 In the teLinkSrlgTable: 370 { 371 ifIndex = 20, 372 srlg = 10, 373 srlgRowStatus = createAndGo(4) 374 } 376 In the teLinkSrlgTable: 377 { 378 ifIndex = 21, 379 srlg = 50, 380 srlgRowStatus = createAndGo(4) 381 } 383 The bundled link inherits the OSPF and SRLG properties from the 384 associated TE links. 386 Next, for each TE link, two component links are created. 387 An ifEntry with the same ifIndex needs to be created beforehand. 389 In componentLinkTable: 390 { 391 ifIndex = 40, 392 componentLinkPreferredProtection = primary(1), 393 componentLinkRowStatus = createAndGo(4) 394 } 396 In ifStackTable: 397 { 398 ifStackHigherLayer = 20, 399 ifStackLowerLayer = 40, 400 ifStackStatus = createAndGo(4) 402 } 404 In componentLinkTable: 405 { 406 ifIndex = 43, 407 componentLinkPreferredProtection = secondary(2), 408 componentLinkRowStatus = createAndGo(4) 409 } 411 In ifStackTable: 412 { 413 ifStackHigherLayer = 20, 414 ifStackLowerLayer = 43, 415 ifStackStatus = createAndGo(4) 416 } 418 In componentLinkTable: 419 { 420 ifIndex = 44, 421 componentLinkPreferredProtection = primary(1), 422 componentLinkRowStatus = createAndGo(4) 423 } 425 In ifStackTable: 426 { 427 ifStackHigherLayer = 21, 428 ifStackLowerLayer = 44, 429 ifStackStatus = createAndGo(4) 430 } 432 In componentLinkTable: 433 { 434 ifIndex = 48, 435 componentLinkPreferredProtection = secondary(2), 436 componentLinkRowStatus = createAndGo(4) 437 } 439 In ifStackTable: 440 { 441 ifStackHigherLayer = 21, 442 ifStackLowerLayer = 48, 443 ifStackStatus = createAndGo(4) 444 } 446 In this example, once a component link is added to the 447 componentLinkTable, the associated link descriptors are 448 implicitly added to the componentLinkDescriptorTable. 450 TE link link descriptors are derived from their component link 451 descriptors. 453 Note that the bandwidth attributes in teLinkDescriptorTable, 454 componentLinkDescriptorTable, teLinkBandwidthTable 455 and componentLinkBandwidthTable are maintained by the 456 device according to LSP creation/deletion at different priorities. 457 The values in the teLinkBandwidthTable are an aggregation 458 of the values for the component links of the TE links and 459 the TE links of the bundled link. 461 9. Application of the Interfaces Group to TE Links 463 The Interfaces Group [RFC2863] defines generic managed objects for 464 managing interfaces. This memo contains the media-specific 465 extensions to the Interfaces Group for managing TE Link interfaces 466 as logical interfaces. 468 This memo assumes the interpretation of the Interfaces Group to be 469 in accordance with [RFC2863] which states that the interfaces table 470 (ifTable) contains information on the managed resource's 471 interfaces and that each sub-layer below the internetwork layer of 472 a network interface is considered an interface. Thus, the TE Link 473 interface is represented as an entry in the ifTable. The inter- 474 relation of entries in the ifTable is defined by Interfaces Stack 475 Group defined in [RFC2863]. 477 When using TE Link interfaces, the interface stack table might appear 478 as follows: 480 +----------------------------------------+ 481 | TE link-interface ifType = teLink(200) + 482 +----------------------------------------+ 483 | Underlying Layer... + 484 +----------------------------------------+ 486 In the above diagram, "Underlying Layer..." refers to the ifIndex 487 of any interface type, which has been defined for TE Link 488 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 490 9.1. Support of the TE Link Layer by ifTable 492 Some specific interpretations of ifTable for the TE Link layer 493 follow. 495 Object Use for the TE Link layer 497 ifIndex Each TE Link interface is represented by an ifEntry. 499 ifDescr Description of the TE Link interface. 501 ifType The value that is allocated for TE Link is 200 502 [IANAFamily]. 504 ifSpeed The total bandwidth in bits per second for use by 505 the TE Link layer. 507 ifPhysAddress Unused. 509 ifAdminStatus This variable indicates the administrator's intent 510 as to whether TE Link should be enabled, disabled, or 511 running in some diagnostic testing mode on this 512 interface. Also see [RFC2863]. 514 ifOperStatus This value reflects the actual or operational 515 status of TE Link on this interface. 517 ifLastChange See [RFC2863]. 519 ifInOctets The number of received octets over the interface, 520 i.e., the number of received octets in all component 521 links associated with the interface. 523 ifOutOctets The number of transmitted octets over the 524 interface, i.e., the number of octets transmitted 525 over all component links associated with the 526 interface. 528 ifInErrors The number of packets dropped due to 529 uncorrectable errors. 531 ifInUnknownProtos 532 The number of received packets discarded during 533 packet header validation. 535 ifOutErrors See [RFC2863]. 537 ifName Textual name (unique on this system) of the 538 interface or an octet string of zero length. 540 ifLinkUpDownTrapEnable 541 Default is disabled (2). 543 ifConnectorPresent 544 Set to false (2). 546 ifHighSpeed See [RFC2863]. 548 ifHCInOctets The 64-bit version of ifInOctets; supported if 549 required by the compliance statements in [RFC2863]. 551 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 552 required by the compliance statements in [RFC2863]. 554 ifAlias The non-volatile 'alias' name for the interface as 555 specified by a network manager. 557 ifCounterDiscontinuityTime 558 See [RFC2863]. 560 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 561 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 562 if encoding type is clear. For other encoding types, traffic 563 counters on a TE link are cumulative for all subinterfaces which it 564 binds together. 566 9.2. Using ifStackTable 568 This section describes by example how to use ifStackTable to 569 represent the relationship of TE links with underlying TE-enabled 570 interfaces. Implementors of the stack table for TE link interfaces 571 should look at the appropriate RFC for the service being stacked 572 on TE links. Examples given below are for illustration purposes 573 only. 575 Example: MPLS is being carried on 2 bundled TE links. 576 Each bundled TE link runs over a 1:1 optical 577 transport interface. 579 +---------------------------------+ 580 | mpls | 581 +---------------------------------+ 582 | 583 +---------------------------------+ 584 | teLink (Link Bundle) | 585 +---------------------------------+ 586 | | 587 +---------------+ +---------------+ 588 | teLink | | teLink | 589 +---------------+ +---------------+ 590 | | | | 591 +------+ +------+ +------+ +------+ 592 |oTrans| |oTrans| |oTrans| |oTrans| 593 +------+ +------+ +------+ +------+ 595 The assignment of the index values could for example be: 597 ifIndex Description 598 1 mpls (type 166) 599 2 teLink (type 200) 600 3 teLink (type 200) 601 4 teLink (type 200) 602 5 opticalTransport (type 196) 603 6 opticalTransport (type 196) 604 7 opticalTransport (type 196) 605 8 opticalTransport (type 196) 607 The ifStackTable is then used to show the relationships between the 608 various interfaces. 610 ifStackTable Entries 612 HigherLayer LowerLayer 613 0 1 614 1 2 615 2 3 616 2 4 617 3 5 618 3 6 619 4 7 620 4 8 621 5 0 622 6 0 623 7 0 624 8 0 626 In the case where MPLS is using a single TE link, then 627 the upper TE link layer (link bundle) is not required. 629 +---------------+ 630 | mpls | 631 +---------------+ 632 | 633 +---------------+ 634 | teLink | 635 +---------------+ 636 | | 637 +------+ +------+ 638 |oTrans| |oTrans| 639 +------+ +------+ 641 The assignment of the index values could for example be: 643 ifIndex Description 644 1 mpls (type 166) 645 2 teLink (type 200) 646 3 opticalTransport (type 196) 647 4 opticalTransport (type 196) 649 The ifStackTable is then used to show the relationships between the 650 various interfaces. 652 ifStackTable Entries 654 HigherLayer LowerLayer 655 0 1 656 1 2 657 2 3 658 2 4 659 3 0 660 4 0 662 10. Link Bundling MIB Definitions 664 LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN 666 IMPORTS 667 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 668 experimental, Unsigned32 669 FROM SNMPv2-SMI 671 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 672 FROM SNMPv2-CONF 674 TruthValue, RowStatus, StorageType 675 FROM SNMPv2-TC 677 InterfaceIndexOrZero, ifIndex 678 FROM IF-MIB 680 RouterID 681 FROM OSPF-MIB 683 InetAddressType, InetAddress 684 FROM INET-ADDRESS-MIB; 686 linkBundlingMIB MODULE-IDENTITY 687 LAST-UPDATED "200206211200Z" -- 21 June 2002 12:00:00 EST 688 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 689 CONTACT-INFO 690 " Martin Dubuc 691 Postal: Meriton Networks 692 3026 Solandt Road 693 Kanata, ON, CANADA K2K 2A5 694 Tel: +1-613-270-9279 x253 695 Email: martin.dubuc@meriton.com 697 Sudheer Dharanikota 698 Postal: Nayna Networks, Inc. 699 157 Topaz Street 700 Milipitas, CA 95035 701 Tel: +1-408-956-8000 x357 702 Email: sudheer@nayna.com 704 Thomas D. Nadeau 705 Postal: Cisco Systems, Inc. 706 300 Apollo Drive 707 Chelmsford, MA 01824 708 Tel: +1-978-244-3051 709 Email: tnadeau@cisco.com 711 Jonathan P. Lang 712 Postal: Calient Networks, Inc. 713 25 Castilian Drive 714 Goleta, CA 93117 715 Email: jplang@calient.net" 717 DESCRIPTION 718 "This MIB contains managed object definitions for 719 MPLS traffic engineering link bundling as 720 defined in: Kompella, K., Rekhter, Y., Berger, L., 721 Link Bundling in MPLS Traffic Engineering 722 Internet Draft , 723 May 2002." 725 -- Revision history. 726 REVISION 727 "200206141200Z" -- 21 June 2002 12:00:00 EST 728 DESCRIPTION 729 "Addressed WG chair comments." 731 REVISION 732 "200205211200Z" -- 21 May 2002 12:00:00 EST 733 DESCRIPTION 734 "Addressed comments received during Last Call. 735 - Addressed syntax errors reports by smilint. 736 - Reintroduced teLinkIpAddrType. 737 - Replaced ifIndex in linkBundlingMismatch 738 notification with TE link endpoint objects." 739 REVISION 740 "200202261200Z" -- 26 February 2002 12:00:00 EST 741 DESCRIPTION 742 "- Updated MIB boiler plate and references. 743 - Added linkBundlingFullModuleCompliance conformance statement. 744 - Removed teLinkIpAddrType. Replaced numbered value with 745 ipV4 and ipV6 values in teLinkNumberingType. 746 - Updated description of all row status and storage type objects. 747 - Changed some of the enumerated value to start from 1 instead of 0. 748 - Updated references." 749 REVISION 750 "200109101200Z" -- 10 September 2001 12:00:00 EST 751 DESCRIPTION 752 "Removed teLinkRemoteId. Updated teLinkEncodingType and 753 componentLinkEncodingType values." 754 REVISION 755 "200105221200Z" -- 22 May 2001 12:00:00 EST 756 DESCRIPTION 757 "Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress 758 and InetAddrType. Changed description of entries which extend 759 ifEntry. Made various minor corrections." 760 REVISION 761 "200105151200Z" -- 15 May 2001 12:00:00 EST 762 DESCRIPTION 763 "Replaced componentLinkTable by componentLinkTable. 764 Replaced linkBundlingTable by teLinkTable. Converted TE links 765 into interfaces." 766 REVISION 767 "200102231200Z" -- 23 February 2001 12:00:00 EST 768 DESCRIPTION 769 "Initial draft version." 770 ::= { experimental 114 } -- See [Assigned] 772 -- Textual Conventions 774 -- Top level components of this MIB 776 -- Notifications 777 linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } 778 -- Tables, Scalars 779 linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } 780 -- Conformance 781 linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } 783 -- TE Link Table 785 teLinkTable OBJECT-TYPE 786 SYNTAX SEQUENCE OF TeLinkEntry 787 MAX-ACCESS not-accessible 788 STATUS current 789 DESCRIPTION 790 "This table specifies the grouping of component links into 791 TE links and grouping of TE links into bundled links." 792 ::= { linkBundlingObjects 1 } 794 teLinkEntry OBJECT-TYPE 795 SYNTAX TeLinkEntry 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "An entry in this table exists for each ifEntry with an 800 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 801 in the ifTable must exist before a teLinkEntry is created with 802 the corresponding ifIndex. If a TE link entry in the ifTable is 803 destroyed, then so is the corresponding entry in the 804 teLinkTable. The administrative and operational status values 805 are controlled from the ifEntry. If the link is unnumbered, 806 ifIndex is also used as the outgoing interface identifier." 807 INDEX { ifIndex } 808 ::= { teLinkTable 1 } 810 TeLinkEntry ::= SEQUENCE { 811 teLinkIpAddrType InetAddressType, 812 teLinkIpAddr InetAddress, 813 teLinkRemoteIpAddr InetAddress, 814 teLinkMetric Unsigned32, 815 teLinkMuxCapability INTEGER, 816 teLinkProtectionType INTEGER, 817 teLinkWorkingPriority Unsigned32, 818 teLinkResourceClass Unsigned32, 819 teLinkIncomingIfId InterfaceIndexOrZero, 820 teLinkOutgoingIfId InterfaceIndexOrZero, 821 teLinkFlooding InterfaceIndexOrZero, 822 teLinkRowStatus RowStatus, 823 teLinkStorageType StorageType 824 } 825 teLinkIpAddrType OBJECT-TYPE 826 SYNTAX InetAddressType 827 MAX-ACCESS read-create 828 STATUS current 829 DESCRIPTION 830 "For IPv4 and IPv6 numbered links, this object represents the 831 IP address type associated with the TE link. For 832 unnumbered links, a value of unknown(0) must be used." 833 ::= { teLinkEntry 1 } 835 teLinkIpAddr OBJECT-TYPE 836 SYNTAX InetAddress 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "For IPv4 and IPv6 numbered links, this object represents the 841 IP address associated with the TE link." 842 ::= { teLinkEntry 2 } 844 teLinkRemoteIpAddr OBJECT-TYPE 845 SYNTAX InetAddress 846 MAX-ACCESS read-create 847 STATUS current 848 DESCRIPTION 849 "The remote IP address associated with the TE link (IPv4 and 850 IPv6 numbered links)." 851 ::= { teLinkEntry 3 } 853 teLinkMetric OBJECT-TYPE 854 SYNTAX Unsigned32 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "The traffic engineering metric for the TE link is 859 derived from its component links. All component links 860 within the TE link must have the same traffic 861 engineering metric." 862 REFERENCE 863 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 864 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 865 May 2002." 866 ::= { teLinkEntry 4 } 868 teLinkMuxCapability OBJECT-TYPE 869 SYNTAX INTEGER { 870 packetSwitch1(1), 871 packetSwitch2(2), 872 packetSwitch3(3), 873 packetSwitch4(4), 874 layer2Switch(51), 875 tdm(100), 876 lambdaSwitch(150), 877 fiberSwitch(200) 878 } 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "This attribute specifies link multiplex capability of the 883 TE link, which is derived from its component links. All 884 component links within the same TE link must have the 885 same link multiplex capability." 886 REFERENCE 887 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 888 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 889 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 890 D. Saha, V. Sharma, May 2002." 891 ::= { teLinkEntry 5 } 893 teLinkProtectionType OBJECT-TYPE 894 SYNTAX INTEGER { 895 extraTraffic(1), 896 unprotected(2), 897 shared(3), 898 dedicated1For1(4), 899 dedicated1Plus1(5), 900 enhanced(6) 901 } 902 MAX-ACCESS read-create 903 STATUS current 904 DESCRIPTION 905 "This attribute specifies link protection type of the 906 TE link." 907 REFERENCE 908 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 909 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 910 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 911 D. Saha, V. Sharma, May 2002." 912 ::= { teLinkEntry 6 } 914 teLinkWorkingPriority OBJECT-TYPE 915 SYNTAX Unsigned32 (0..7) 916 MAX-ACCESS read-create 917 STATUS current 918 DESCRIPTION 919 "This object represents a priority value such that a new 920 connection with a higher priority, i.e. numerically lower than 921 this value, is guaranteed to be setup on a primary link and 922 not on a secondary link." 923 REFERENCE 924 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 925 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 926 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 927 D. Saha, V. Sharma, May 2002." 928 ::= { teLinkEntry 7 } 930 teLinkResourceClass OBJECT-TYPE 931 SYNTAX Unsigned32 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 "This attribute specifies the TE link resource class. 936 The resource class is a 32 bit bitfield. The resource class for 937 a link bundle is derived from the resource class of its 938 TE links. All TE links within a link bundle must have the 939 same resource class." 940 ::= { teLinkEntry 8 } 942 teLinkIncomingIfId OBJECT-TYPE 943 SYNTAX InterfaceIndexOrZero 944 MAX-ACCESS read-create 945 STATUS current 946 DESCRIPTION 947 "For unnumbered links, the incoming interface is set to the 948 outgoing interface identifier chosen by the neighboring LSR 949 for the reverse link corresponding to this TE link." 950 REFERENCE 951 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 952 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 953 May 2002." 954 ::= { teLinkEntry 9 } 956 teLinkOutgoingIfId OBJECT-TYPE 957 SYNTAX InterfaceIndexOrZero 958 MAX-ACCESS read-create 959 STATUS current 960 DESCRIPTION 961 "If the link is unnumbered, the outgoing interface identifier is 962 set to the outgoing interface identifier chosen for the TE link 963 by the advertising LSR." 964 REFERENCE 965 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 966 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 967 May 2002." 968 ::= { teLinkEntry 10 } 970 teLinkFlooding OBJECT-TYPE 971 SYNTAX InterfaceIndexOrZero 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "This object only has significance for link bundles which 976 encoding type is not clear. For these link bundles, this object 977 identifies the TE link on which to restrict flooding. If the 978 value is zero, then flooding must be done on all TE links 979 within the link bundle." 980 REFERENCE 981 "draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization 982 in link-state routing protocols, A. Zinin, M. Shand, 983 March 2001." 984 DEFVAL { 0 } 985 ::= { teLinkEntry 11 } 987 teLinkRowStatus OBJECT-TYPE 988 SYNTAX RowStatus 989 MAX-ACCESS read-create 990 STATUS current 991 DESCRIPTION 992 "This variable is used to create, modify, and/or 993 delete a row in this table. All read-create objects 994 can only be changed when teLinkRowStatus is active." 995 ::= { teLinkEntry 12 } 997 teLinkStorageType OBJECT-TYPE 998 SYNTAX StorageType 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "The storage type for this conceptual row in the 1003 teLinkTable. Conceptual rows having the value 1004 'permanent' need not allow write-access to any 1005 columnar object in the row." 1006 ::= { teLinkEntry 13 } 1008 -- End of teLinkTable 1010 -- TE Link Descriptor Table 1012 teLinkDescriptorTable OBJECT-TYPE 1013 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "This table specifies the link descriptors associated with the 1018 TE links." 1019 ::= { linkBundlingObjects 2 } 1021 teLinkDescriptorEntry OBJECT-TYPE 1022 SYNTAX TeLinkDescriptorEntry 1023 MAX-ACCESS not-accessible 1024 STATUS current 1025 DESCRIPTION 1026 "An entry in this table is created for every TE link descriptor. 1027 An ifEntry in the ifTable must exist before a 1028 teLinkDescriptorEntry using the same ifIndex is created. 1029 If a TE link entry in the ifTable is destroyed, then so are all 1030 entries in the teLinkDescriptorTable that use the ifIndex of 1031 this TE link." 1032 INDEX { ifIndex, teLinkDescriptorId } 1033 ::= { teLinkDescriptorTable 1 } 1035 TeLinkDescriptorEntry ::= SEQUENCE { 1036 teLinkDescriptorId Unsigned32, 1037 teLinkEncodingType INTEGER, 1038 teLinkDescrPriority Unsigned32, 1039 teLinkMinReservableBandwidth Unsigned32, 1040 teLinkMaxReservableBandwidth Unsigned32, 1041 teLinkDescrRowStatus RowStatus, 1042 teLinkDescrStorageType StorageType 1043 } 1045 teLinkDescriptorId OBJECT-TYPE 1046 SYNTAX Unsigned32 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 "This object specifies the link descriptor identifier." 1051 ::= { teLinkDescriptorEntry 1 } 1053 teLinkEncodingType OBJECT-TYPE 1054 SYNTAX INTEGER { 1055 packet(1), 1056 ethernet(2), 1057 ansiEtsiPdh(3), 1058 sdhItuSonetAnsi(5), 1059 digitalWrapper(7), 1060 lambda(8), 1061 fiber(9), 1062 fiberChannel(11) 1063 } 1064 MAX-ACCESS read-create 1065 STATUS current 1066 DESCRIPTION 1067 "This attribute specifies the TE link encoding type." 1068 REFERENCE 1069 "draft-ietf-mpls-generalized-signaling-08.txt - Generalized 1070 MPLS Signaling Functional Description, P. Ashwood-Smith, 1071 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 1072 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 1073 V. Sharma, G. Swallow, Z. Tang, April 2002." 1074 ::= { teLinkDescriptorEntry 2 } 1076 teLinkDescrPriority OBJECT-TYPE 1077 SYNTAX Unsigned32 (0..7) 1078 MAX-ACCESS read-create 1079 STATUS current 1080 DESCRIPTION 1081 "This object specifies the lowest priority at which that link 1082 encoding type is available." 1083 REFERENCE 1084 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1085 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1086 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1087 D. Saha, V. Sharma, May 2002." 1088 ::= { teLinkDescriptorEntry 3 } 1090 teLinkMinReservableBandwidth OBJECT-TYPE 1091 SYNTAX Unsigned32 1092 MAX-ACCESS read-create 1093 STATUS current 1094 DESCRIPTION 1095 "This attribute specifies the minimum reservable bandwidth on 1096 the TE link. This is derived from the union of the 1097 minimum reservable bandwidth of all the component links 1098 associated with the TE link that can be used to carry 1099 live traffic. This value is an estimate in units of 1,000 bits 1100 per second." 1101 REFERENCE 1102 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1103 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1104 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1105 D. Saha, V. Sharma, May 2002." 1106 ::= { teLinkDescriptorEntry 4 } 1108 teLinkMaxReservableBandwidth OBJECT-TYPE 1109 SYNTAX Unsigned32 1110 MAX-ACCESS read-create 1111 STATUS current 1112 DESCRIPTION 1113 "This attribute specifies the maximum reservable bandwidth on 1114 the TE link. This is the union of the maximum reservable 1115 bandwidth of all the component links within the 1116 TE link that can be used to carry live traffic. This value 1117 is an estimate in units of 1,000 bits per second." 1118 REFERENCE 1119 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1120 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1121 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1122 D. Saha, V. Sharma, May 2002." 1123 ::= { teLinkDescriptorEntry 5 } 1125 teLinkDescrRowStatus OBJECT-TYPE 1126 SYNTAX RowStatus 1127 MAX-ACCESS read-create 1128 STATUS current 1129 DESCRIPTION 1130 "This variable is used to create, modify, and/or 1131 delete a row in this table. All read-create objects 1132 can only be changed when teLinkDescrRowStatus is active." 1133 ::= { teLinkDescriptorEntry 6 } 1135 teLinkDescrStorageType OBJECT-TYPE 1136 SYNTAX StorageType 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "The storage type for this conceptual row in the 1141 teLinkDescriptorTable. Conceptual rows having the value 1142 'permanent' need not allow write-access to any 1143 columnar object in the row." 1144 ::= { teLinkDescriptorEntry 7 } 1146 -- End of teLinkDescriptorTable 1148 -- OSPF Traffic Engineering Parameters for TE Links 1150 teLinkOspfTeTable OBJECT-TYPE 1151 SYNTAX SEQUENCE OF TeLinkOspfTeEntry 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "This table specifies the OSPF traffic engineering information 1156 associated with TE links." 1157 ::= { linkBundlingObjects 3 } 1159 teLinkOspfTeEntry OBJECT-TYPE 1160 SYNTAX TeLinkOspfTeEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "If OSPF is enabled, an entry in this table is created for 1165 every TE link." 1166 AUGMENTS { teLinkEntry } 1167 ::= { teLinkOspfTeTable 1 } 1169 TeLinkOspfTeEntry ::= SEQUENCE { 1170 teLinkOspfLinkType INTEGER, 1171 teLinkOspfLinkId RouterID 1172 } 1174 teLinkOspfLinkType OBJECT-TYPE 1175 SYNTAX INTEGER { 1176 pointToPoint(1), 1177 multiAccess(2) 1178 } 1179 MAX-ACCESS read-create 1180 STATUS current 1181 DESCRIPTION 1182 "This attribute specifies the OSPF link type for the TE link. 1183 All TE links within the same bundle must have the same 1184 link type." 1185 ::= { teLinkOspfTeEntry 1 } 1187 teLinkOspfLinkId OBJECT-TYPE 1188 SYNTAX RouterID 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "On point-to-point link, the link identifier is the Router ID 1193 of the neighbor. For bundled link, is derived from the link 1194 identifier associated with its TE links." 1195 REFERENCE 1196 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 1197 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1198 May 2002." 1199 ::= { teLinkOspfTeEntry 2 } 1201 -- End of teLinkOspfTeTable 1203 -- TE Link Shared Risk Link Group Table 1205 teLinkSrlgTable OBJECT-TYPE 1206 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1207 MAX-ACCESS not-accessible 1208 STATUS current 1209 DESCRIPTION 1210 "This table specifies the SRLGs associated with TE links." 1211 ::= { linkBundlingObjects 4 } 1213 teLinkSrlgEntry OBJECT-TYPE 1214 SYNTAX TeLinkSrlgEntry 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION 1218 "An entry in this table contains information about a 1219 SRLG associated with a TE link. 1220 An ifEntry in the ifTable must exist before a 1221 teLinkSrlgEntry using the same ifIndex is created. 1222 If a TE link entry in the ifTable is destroyed, then so are all 1223 entries in the teLinkSrlgTable that use the ifIndex of 1224 this TE link." 1225 INDEX { ifIndex, srlg } 1226 ::= { teLinkSrlgTable 1 } 1228 TeLinkSrlgEntry ::= SEQUENCE { 1229 srlg Unsigned32, 1230 srlgRowStatus RowStatus, 1231 srlgStorageType StorageType 1232 } 1234 srlg OBJECT-TYPE 1235 SYNTAX Unsigned32 1236 MAX-ACCESS not-accessible 1237 STATUS current 1238 DESCRIPTION 1239 "This identifies a SRLG supported by the TE link." 1240 REFERENCE 1241 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1242 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1243 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1244 D. Saha, V. Sharma, May 2002." 1245 ::= { teLinkSrlgEntry 1 } 1247 srlgRowStatus OBJECT-TYPE 1248 SYNTAX RowStatus 1249 MAX-ACCESS read-create 1250 STATUS current 1251 DESCRIPTION 1252 "This variable is used to create, modify, and/or 1253 delete a row in this table. All read-create objects 1254 can only be changed when srlgRowStatus is active." 1256 ::= { teLinkSrlgEntry 2 } 1258 srlgStorageType OBJECT-TYPE 1259 SYNTAX StorageType 1260 MAX-ACCESS read-create 1261 STATUS current 1262 DESCRIPTION 1263 "The storage type for this conceptual row in the 1264 teLinkSrlgTable. Conceptual rows having the value 1265 'permanent' need not allow write-access to any 1266 columnar object in the row." 1267 ::= { teLinkSrlgEntry 3 } 1269 -- End of teLinkSrlgTable 1271 -- TE Link Bandwidth Table 1273 teLinkBandwidthTable OBJECT-TYPE 1274 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "This table specifies the priority-based bandwidth table 1279 for TE links." 1280 ::= { linkBundlingObjects 5 } 1282 teLinkBandwidthEntry OBJECT-TYPE 1283 SYNTAX TeLinkBandwidthEntry 1284 MAX-ACCESS not-accessible 1285 STATUS current 1286 DESCRIPTION 1287 "An entry in this table contains information about 1288 the priority-based bandwidth of TE links. An ifEntry in the 1289 ifTable must exist before a teLinkBandwidthEntry using the 1290 same ifIndex is created. If a TE link entry in the ifTable 1291 is destroyed, then so are all entries in the teLinkBandwidthTable 1292 that use the ifIndex of this TE link." 1293 INDEX { ifIndex, teLinkPriority } 1294 ::= { teLinkBandwidthTable 1 } 1296 TeLinkBandwidthEntry ::= SEQUENCE { 1297 teLinkPriority Unsigned32, 1298 teLinkUnreservedBandwidth Unsigned32, 1299 teLinkMaximumLspBandwidth Unsigned32, 1300 teLinkBandwidthRowStatus RowStatus, 1301 teLinkBandwidthStorageType StorageType 1302 } 1303 teLinkPriority OBJECT-TYPE 1304 SYNTAX Unsigned32 (1..8) 1305 MAX-ACCESS not-accessible 1306 STATUS current 1307 DESCRIPTION 1308 "This attribute specifies the priority. It should be mapped 1309 to a number between 0 and 7" 1310 REFERENCE 1311 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1312 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1313 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1314 D. Saha, V. Sharma, May 2002." 1315 ::= { teLinkBandwidthEntry 1 } 1317 teLinkUnreservedBandwidth OBJECT-TYPE 1318 SYNTAX Unsigned32 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "This attribute specifies the TE link unreserved 1323 bandwidth at priority p. It is the sum of the unreserved 1324 bandwidths at priority p of all component links associated 1325 with the TE link (excludes all links that are strictly 1326 used as protecting links). This value is an estimate in units 1327 of 1,000 bits per second." 1328 REFERENCE 1329 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 1330 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1331 May 2002." 1332 ::= { teLinkBandwidthEntry 2 } 1334 teLinkMaximumLspBandwidth OBJECT-TYPE 1335 SYNTAX Unsigned32 1336 MAX-ACCESS read-create 1337 STATUS current 1338 DESCRIPTION 1339 "This attribute specifies the TE link maximum 1340 LSP bandwidth at priority p. It is the maximum of all 1341 maximum LSP bandwidth at priority p of the component links 1342 associated with the TE link (excludes all links that are 1343 strictly used as protecting links). This value is an estimate 1344 in units of 1,000 bits per second." 1345 REFERENCE 1346 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 1347 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1348 May 2002." 1349 ::= { teLinkBandwidthEntry 3 } 1351 teLinkBandwidthRowStatus OBJECT-TYPE 1352 SYNTAX RowStatus 1353 MAX-ACCESS read-create 1354 STATUS current 1355 DESCRIPTION 1356 "This variable is used to create, modify, and/or 1357 delete a row in this table. All read-create objects 1358 can only be changed when teLinkBandwidthRowStatus is active." 1359 ::= { teLinkBandwidthEntry 4 } 1361 teLinkBandwidthStorageType OBJECT-TYPE 1362 SYNTAX StorageType 1363 MAX-ACCESS read-create 1364 STATUS current 1365 DESCRIPTION 1366 "The storage type for this conceptual row in the 1367 teLinkBandwidthTable. Conceptual rows having the value 1368 'permanent' need not allow write-access to any 1369 columnar object in the row." 1370 ::= { teLinkBandwidthEntry 5 } 1372 -- End of teLinkBandwidthTable 1374 -- Component Link Table 1376 componentLinkTable OBJECT-TYPE 1377 SYNTAX SEQUENCE OF ComponentLinkEntry 1378 MAX-ACCESS not-accessible 1379 STATUS current 1380 DESCRIPTION 1381 "This table specifies the component link parameters." 1382 ::= { linkBundlingObjects 6 } 1384 componentLinkEntry OBJECT-TYPE 1385 SYNTAX ComponentLinkEntry 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "An entry in this table exists for each ifEntry that represents 1390 a component link. An ifEntry must exist in the ifTable 1391 before a componentLinkEntry is created with the 1392 corresponding ifIndex. If an entry representing a component 1393 link is destroyed in the ifTable, then so is the 1394 corresponding entry in the componentLinkTable. The 1395 administrative and operational status values are controlled 1396 from the ifEntry." 1397 INDEX { ifIndex } 1398 ::= { componentLinkTable 1 } 1400 ComponentLinkEntry ::= SEQUENCE { 1401 componentLinkMuxCapability INTEGER, 1402 componentLinkPreferredProtection INTEGER, 1403 componentLinkCurrentProtection INTEGER, 1404 componentLinkRowStatus RowStatus, 1405 componentLinkStorageType StorageType 1406 } 1408 componentLinkMuxCapability OBJECT-TYPE 1409 SYNTAX INTEGER { 1410 packetSwitch1(1), 1411 packetSwitch2(2), 1412 packetSwitch3(3), 1413 packetSwitch4(4), 1414 layer2Switch(51), 1415 tdm(100), 1416 lambdaSwitch(150), 1417 fiberSwitch(200) 1418 } 1419 MAX-ACCESS read-create 1420 STATUS current 1421 DESCRIPTION 1422 "This attribute specifies link multiplexing capabilities of the 1423 component link." 1424 REFERENCE 1425 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1426 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1427 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1428 D. Saha, V. Sharma, May 2002." 1429 ::= { componentLinkEntry 1 } 1431 componentLinkPreferredProtection OBJECT-TYPE 1432 SYNTAX INTEGER { 1433 primary(1), 1434 secondary(2) 1435 } 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1439 "This attribute specifies whether this component link is 1440 a primary or secondary entity." 1441 ::= { componentLinkEntry 2 } 1443 componentLinkCurrentProtection OBJECT-TYPE 1444 SYNTAX INTEGER { 1445 primary(1), 1446 secondary(2) 1447 } 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "This attribute specifies whether this component link is 1452 currently used as primary or secondary link." 1453 ::= { componentLinkEntry 3 } 1455 componentLinkRowStatus OBJECT-TYPE 1456 SYNTAX RowStatus 1457 MAX-ACCESS read-create 1458 STATUS current 1459 DESCRIPTION 1460 "This variable is used to create, modify, and/or 1461 delete a row in this table. All read-create objects 1462 can only be changed when componentLinkRowStatus is active." 1463 ::= { componentLinkEntry 4 } 1465 componentLinkStorageType OBJECT-TYPE 1466 SYNTAX StorageType 1467 MAX-ACCESS read-create 1468 STATUS current 1469 DESCRIPTION 1470 "The storage type for this conceptual row in the 1471 componentLinkTable. Conceptual rows having the value 1472 'permanent' need not allow write-access to any 1473 columnar object in the row." 1474 ::= { componentLinkEntry 5 } 1476 -- End of componentLinkTable 1478 -- Component Link Descriptor Table 1480 componentLinkDescriptorTable OBJECT-TYPE 1481 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "This table specifies the link descriptors associated with the 1486 component links." 1487 ::= { linkBundlingObjects 7 } 1489 componentLinkDescriptorEntry OBJECT-TYPE 1490 SYNTAX ComponentLinkDescriptorEntry 1491 MAX-ACCESS not-accessible 1492 STATUS current 1493 DESCRIPTION 1494 "An entry in this table is created for every component link 1495 descriptor. An ifEntry in the ifTable must exist before a 1496 componentLinkDescriptorEntry using the same ifIndex is created. 1497 If a component link entry in the ifTable is destroyed, 1498 then so are all entries in the componentLinkDescriptorTable 1499 that use the ifIndex of this component link." 1500 INDEX { ifIndex, componentLinkDescrId } 1501 ::= { componentLinkDescriptorTable 1 } 1503 ComponentLinkDescriptorEntry ::= SEQUENCE { 1504 componentLinkDescrId Unsigned32, 1505 componentLinkEncodingType INTEGER, 1506 componentLinkDescrPriority Unsigned32, 1507 componentLinkMinReservBandwidth Unsigned32, 1508 componentLinkMaxReservBandwidth Unsigned32, 1509 componentLinkDescrRowStatus RowStatus, 1510 componentLinkDescrStorageType StorageType 1511 } 1513 componentLinkDescrId OBJECT-TYPE 1514 SYNTAX Unsigned32 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "This object specifies the link descriptor identifier." 1519 ::= { componentLinkDescriptorEntry 1 } 1521 componentLinkEncodingType OBJECT-TYPE 1522 SYNTAX INTEGER { 1523 packet(1), 1524 ethernet(2), 1525 ansiEtsiPdh(3), 1526 sdhItuSonetAnsi(5), 1527 digitalWrapper(7), 1528 lambda(8), 1529 fiber(9), 1530 fiberChannel(11) 1531 } 1532 MAX-ACCESS read-create 1533 STATUS current 1534 DESCRIPTION 1535 "This attribute specifies the component link encoding type." 1536 REFERENCE 1537 "draft-ietf-mpls-generalized-signaling-08.txt - Generalized 1538 MPLS Signaling Functional Description, P. Ashwood-Smith, 1539 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 1540 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 1541 V. Sharma, G. Swallow, Z. Tang, April 2002." 1542 ::= { componentLinkDescriptorEntry 2 } 1544 componentLinkDescrPriority OBJECT-TYPE 1545 SYNTAX Unsigned32 (0..7) 1546 MAX-ACCESS read-create 1547 STATUS current 1548 DESCRIPTION 1549 "This object specifies the lowest priority at which that link 1550 encoding type is available for the component link." 1551 REFERENCE 1552 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1553 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1554 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1555 D. Saha, V. Sharma, May 2002." 1556 ::= { componentLinkDescriptorEntry 3 } 1558 componentLinkMinReservBandwidth OBJECT-TYPE 1559 SYNTAX Unsigned32 1560 MAX-ACCESS read-create 1561 STATUS current 1562 DESCRIPTION 1563 "This attribute specifies the minimum reservable bandwidth on 1564 the component link. This value is an estimate 1565 in units of 1,000 bits per second." 1566 REFERENCE 1567 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1568 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1569 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1570 D. Saha, V. Sharma, May 2002." 1571 ::= { componentLinkDescriptorEntry 4 } 1573 componentLinkMaxReservBandwidth OBJECT-TYPE 1574 SYNTAX Unsigned32 1575 MAX-ACCESS read-create 1576 STATUS current 1577 DESCRIPTION 1578 "This attribute specifies the maximum reservable bandwidth on 1579 the component link. This value is an estimate 1580 in units of 1,000 bits per second." 1581 REFERENCE 1582 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1583 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1584 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1585 D. Saha, V. Sharma, May 2002." 1586 ::= { componentLinkDescriptorEntry 5 } 1588 componentLinkDescrRowStatus OBJECT-TYPE 1589 SYNTAX RowStatus 1590 MAX-ACCESS read-create 1591 STATUS current 1592 DESCRIPTION 1593 "This variable is used to create, modify, and/or 1594 delete a row in this table. All read-create objects 1595 can only be changed when componentLinkDescrRowStatus 1596 is active." 1597 ::= { componentLinkDescriptorEntry 6 } 1599 componentLinkDescrStorageType OBJECT-TYPE 1600 SYNTAX StorageType 1601 MAX-ACCESS read-create 1602 STATUS current 1603 DESCRIPTION 1604 "The storage type for this conceptual row in the 1605 componentLinkDescriptorTable. Conceptual rows 1606 having the value 'permanent' need not allow write-access 1607 to any columnar object in the row." 1608 ::= { componentLinkDescriptorEntry 7 } 1610 -- End of componentLinkDescriptorTable 1612 -- Component Link Bandwidth Table 1614 componentLinkBandwidthTable OBJECT-TYPE 1615 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "This table specifies the priority-based bandwidth 1620 for component links." 1621 ::= { linkBundlingObjects 8 } 1623 componentLinkBandwidthEntry OBJECT-TYPE 1624 SYNTAX ComponentLinkBandwidthEntry 1625 MAX-ACCESS not-accessible 1626 STATUS current 1627 DESCRIPTION 1628 "An entry in this table contains information about 1629 the priority-based bandwidth on component links. 1630 An ifEntry in the ifTable must exist before a 1631 componentLinkBandwidthEntry using the same ifIndex is 1632 created. If a component link entry in the ifTable is 1633 destroyed, then so are all entries in the 1634 componentLinkBandwidthTable that use the ifIndex of 1635 this component link." 1637 INDEX { ifIndex, componentLinkPriority } 1638 ::= { componentLinkBandwidthTable 1 } 1640 ComponentLinkBandwidthEntry ::= SEQUENCE { 1641 componentLinkPriority Unsigned32, 1642 componentLinkUnreservedBandwidth Unsigned32, 1643 componentLinkMaximumLspBandwidth Unsigned32, 1644 componentLinkBandwidthRowStatus RowStatus, 1645 componentLinkBwStorageType StorageType 1646 } 1648 componentLinkPriority OBJECT-TYPE 1649 SYNTAX Unsigned32 (1..8) 1650 MAX-ACCESS not-accessible 1651 STATUS current 1652 DESCRIPTION 1653 "This attribute specifies the priority. It should be mapped 1654 to a number between 0 and 7." 1655 REFERENCE 1656 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1657 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1658 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1659 D. Saha, V. Sharma, May 2002." 1660 ::= { componentLinkBandwidthEntry 1 } 1662 componentLinkUnreservedBandwidth OBJECT-TYPE 1663 SYNTAX Unsigned32 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "This attribute specifies the component link unreserved 1668 bandwidth at priority p. This value is an estimate 1669 in units of 1,000 bits per second." 1670 REFERENCE 1671 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1672 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1673 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1674 D. Saha, V. Sharma, May 2002." 1675 ::= { componentLinkBandwidthEntry 2 } 1677 componentLinkMaximumLspBandwidth OBJECT-TYPE 1678 SYNTAX Unsigned32 1679 MAX-ACCESS read-create 1680 STATUS current 1681 DESCRIPTION 1682 "This attribute specifies the component link maximum 1683 LSP bandwidth at priority p. This value is an estimate 1684 in units of 1,000 bits per second." 1686 REFERENCE 1687 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1688 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1689 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1690 D. Saha, V. Sharma, May 2002." 1691 ::= { componentLinkBandwidthEntry 3 } 1693 componentLinkBandwidthRowStatus OBJECT-TYPE 1694 SYNTAX RowStatus 1695 MAX-ACCESS read-create 1696 STATUS current 1697 DESCRIPTION 1698 "This variable is used to create, modify, and/or 1699 delete a row in this table. All read-create objects can only 1700 be changed when componentLinkBandwidthRowStatus is active." 1701 ::= { componentLinkBandwidthEntry 4 } 1703 componentLinkBwStorageType OBJECT-TYPE 1704 SYNTAX StorageType 1705 MAX-ACCESS read-create 1706 STATUS current 1707 DESCRIPTION 1708 "The storage type for this conceptual row in the 1709 componentLinkBandwidthTable. Conceptual rows 1710 having the value 'permanent' need not allow write-access 1711 to any columnar object in the row." 1712 ::= { componentLinkBandwidthEntry 5 } 1714 -- End of componentLinkBandwidthTable 1716 -- Notification Configuration 1718 linkBundlingNotifEnable OBJECT-TYPE 1719 SYNTAX TruthValue 1720 MAX-ACCESS read-write 1721 STATUS current 1722 DESCRIPTION 1723 "If this object is true, then it enables the 1724 generation of the link bundling notifications, 1725 otherwise these notifications are not emitted." 1726 DEFVAL { false } 1727 ::= { linkBundlingObjects 9 } 1729 -- Notifications 1730 -- Bundled Link Notifications 1732 linkBundleMismatch NOTIFICATION-TYPE 1733 OBJECTS { teLinkIpAddrType, teLinkIpAddr, teLinkRemoteIpAddr } 1734 STATUS current 1735 DESCRIPTION 1736 "This notification is generated when a mismatch is found on a 1737 bundled link. Such mismatch can be detected for instance if one 1738 of the traffic engineering parameters is not consistent across 1739 all TE links within a bundled link (resource class, 1740 OSPF link type, etc.)." 1741 ::= { linkBundlingNotifications 1 } 1743 -- End of notifications 1745 -- Module compliance 1747 linkBundlingGroups 1748 OBJECT IDENTIFIER ::= { linkBundlingConformance 1 } 1750 linkBundlingCompliances 1751 OBJECT IDENTIFIER ::= { linkBundlingConformance 2 } 1753 linkBundlingFullModuleCompliance MODULE-COMPLIANCE 1754 STATUS current 1755 DESCRIPTION 1756 "Compliance statement for agents that support the 1757 configuration and monitoring of link bundling MIB." 1758 MODULE -- this module 1760 -- The mandatory groups have to be implemented 1761 -- by all devices supporting link bundling. However, they may all 1762 -- be supported as read-only objects in the case where automatic 1763 -- configuration is supported. 1765 MANDATORY-GROUPS { linkBundlingGroup, 1766 teLinkBandwidthGroup, 1767 componentLinkBandwidthGroup } 1769 GROUP teLinkOspfTeGroup 1770 DESCRIPTION 1771 "This group is mandatory for OSPF enabled devices." 1773 GROUP teLinkSrlgGroup 1774 DESCRIPTION 1775 "This group is mandatory for G-MPLS enabled devices." 1777 GROUP linkBundlingNotificationGroup 1778 DESCRIPTION 1779 "This group is mandatory for equipment that support 1780 link bundling notifications." 1782 -- teLinkTable 1784 OBJECT teLinkIpAddrType 1785 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1786 MIN-ACCESS read-only 1787 DESCRIPTION 1788 "The dns(16) address type need not be supported. 1789 The ipv4(1) and ipv6(2) address types need not be 1790 supported if numbered links are not supported. The 1791 unknown(0) address type need not be supported if 1792 unnumbered links are not supported." 1794 OBJECT teLinkIpAddr 1795 SYNTAX InetAddress (SIZE(0|4|16)) 1796 DESCRIPTION 1797 "Size of TE link IP address depends on type of TE link. 1798 TE link IP address size is zero if link is unnumbered, 1799 four if link IP address is IPv4 and sixteen if link IP 1800 address is IPv6." 1802 OBJECT teLinkRemoteIpAddr 1803 SYNTAX InetAddress (SIZE(0|4|16)) 1804 DESCRIPTION 1805 "Size of TE link IP address depends on type of TE link. 1806 TE link IP address size is zero if link is unnumbered, 1807 four if link IP address is IPv4 and sixteen if link IP 1808 address is IPv6." 1810 OBJECT teLinkMuxCapability 1811 MIN-ACCESS read-only 1812 DESCRIPTION 1813 "Write access is not required." 1815 OBJECT teLinkProtectionType 1816 MIN-ACCESS read-only 1817 DESCRIPTION 1818 "Write access is not required." 1820 OBJECT teLinkRowStatus 1821 SYNTAX INTEGER { active(1), notInService(2), 1822 createAndGo(4), destroy(6) } 1823 DESCRIPTION 1824 "The notReady(3) state need not be supported." 1826 OBJECT teLinkStorageType 1827 SYNTAX INTEGER { other(1) } 1828 DESCRIPTION 1829 "Only other(1) needs to be supported." 1831 -- teLinkDescriptorTable 1833 OBJECT teLinkEncodingType 1834 MIN-ACCESS read-only 1835 DESCRIPTION 1836 "Write access is not required." 1838 OBJECT teLinkDescrPriority 1839 MIN-ACCESS read-only 1840 DESCRIPTION 1841 "Write access is not required." 1843 OBJECT teLinkMinReservableBandwidth 1844 MIN-ACCESS read-only 1845 DESCRIPTION 1846 "Write access is not required." 1848 OBJECT teLinkMaxReservableBandwidth 1849 MIN-ACCESS read-only 1850 DESCRIPTION 1851 "Write access is not required." 1853 OBJECT teLinkDescrRowStatus 1854 SYNTAX INTEGER { active(1), notInService(2), 1855 createAndGo(4), destroy(6) } 1856 DESCRIPTION 1857 "The notReady(3) state need not be supported." 1859 OBJECT teLinkDescrStorageType 1860 SYNTAX INTEGER { other(1) } 1861 DESCRIPTION 1862 "Only other(1) needs to be supported." 1864 -- teLinkOspfTeTable 1866 OBJECT teLinkOspfLinkType 1867 SYNTAX INTEGER { pointToPoint(1) } 1868 MIN-ACCESS read-only 1869 DESCRIPTION 1870 "A value of multiAccess(2) need not be supported." 1872 OBJECT teLinkOspfLinkId 1873 MIN-ACCESS read-only 1874 DESCRIPTION 1875 "Write access is not required." 1877 -- teLinkSrlgTable 1879 OBJECT srlgRowStatus 1880 SYNTAX INTEGER { active(1), notInService(2), 1881 createAndGo(4), destroy(6) } 1882 DESCRIPTION 1883 "The notReady(3) and createAndWait(5) states need 1884 not be supported." 1886 OBJECT srlgStorageType 1887 SYNTAX INTEGER { other(1) } 1888 DESCRIPTION 1889 "Only other(1) needs to be supported." 1891 -- teLinkBandwidthTable 1893 OBJECT teLinkMaximumLspBandwidth 1894 MIN-ACCESS read-only 1895 DESCRIPTION 1896 "Write access is not required." 1898 OBJECT teLinkBandwidthRowStatus 1899 SYNTAX INTEGER { active(1), notInService(2), 1900 createAndGo(4), destroy(6) } 1901 DESCRIPTION 1902 "The notReady(3) and createAndWait(5) states need 1903 not be supported." 1905 OBJECT teLinkBandwidthStorageType 1906 SYNTAX INTEGER { other(1) } 1907 DESCRIPTION 1908 "Only other(1) needs to be supported." 1910 -- componentLinkTable 1912 OBJECT componentLinkMuxCapability 1913 MIN-ACCESS read-only 1914 DESCRIPTION 1915 "Write access is not required." 1917 OBJECT componentLinkMaxReservBandwidth 1918 MIN-ACCESS read-only 1919 DESCRIPTION 1920 "Write access is not required." 1922 OBJECT componentLinkRowStatus 1923 SYNTAX INTEGER { active(1), notInService(2), 1924 createAndGo(4), destroy(6) } 1925 DESCRIPTION 1926 "The notReady(3) and createAndWait(5) states need 1927 not be supported." 1929 OBJECT componentLinkStorageType 1930 SYNTAX INTEGER { other(1) } 1931 DESCRIPTION 1932 "Only other(1) needs to be supported." 1934 -- componentLinkDescriptorTable 1936 OBJECT componentLinkDescrRowStatus 1937 SYNTAX INTEGER { active(1), notInService(2), 1938 createAndGo(4), destroy(6) } 1939 DESCRIPTION 1940 "The notReady(3) state need not be supported." 1942 OBJECT componentLinkDescrStorageType 1943 SYNTAX INTEGER { other(1) } 1944 DESCRIPTION 1945 "Only other(1) needs to be supported." 1947 -- componentLinkBandwidthTable 1949 OBJECT componentLinkMaximumLspBandwidth 1950 MIN-ACCESS read-only 1951 DESCRIPTION 1952 "Write access is not required." 1954 OBJECT componentLinkBandwidthRowStatus 1955 SYNTAX INTEGER { active(1), notInService(2), 1956 createAndGo(4), destroy(6) } 1957 DESCRIPTION 1958 "The notReady(3) and createAndWait(5) states need 1959 not be supported." 1961 OBJECT componentLinkBwStorageType 1962 SYNTAX INTEGER { other(1) } 1963 DESCRIPTION 1964 "Only other(1) needs to be supported." 1966 ::= { linkBundlingCompliances 1 } 1968 linkBundlingMonModuleCompliance MODULE-COMPLIANCE 1969 STATUS current 1970 DESCRIPTION 1971 "Compliance statement for agents that support the 1972 monitoring of link bundling MIB." 1973 MODULE -- this module 1975 -- The mandatory groups have to be implemented 1976 -- by all devices supporting link bundling. However, they may all 1977 -- be supported as read-only objects in the case where manual 1978 -- configuration is unsupported. 1980 MANDATORY-GROUPS { linkBundlingGroup, 1981 teLinkBandwidthGroup, 1982 componentLinkBandwidthGroup } 1984 GROUP teLinkOspfTeGroup 1985 DESCRIPTION 1986 "This group is mandatory for OSPF enabled devices." 1988 GROUP teLinkSrlgGroup 1989 DESCRIPTION 1990 "This group is mandatory for G-MPLS enabled devices." 1992 GROUP linkBundlingNotificationGroup 1993 DESCRIPTION 1994 "This group is optional." 1996 -- teLinkTable 1998 OBJECT teLinkIpAddrType 1999 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 2000 MIN-ACCESS read-only 2001 DESCRIPTION 2002 "The dns(16) address type need not be supported. 2003 The ipv4(1) and ipv6(2) address types need not be 2004 supported if numbered links are not supported. The 2005 unknown(0) address type need not be supported if 2006 unnumbered links are not supported." 2008 OBJECT teLinkIpAddr 2009 SYNTAX InetAddress (SIZE(0|4|16)) 2010 DESCRIPTION 2011 "Size of TE link IP address depends on type of TE link. 2012 TE link IP address size is zero if link is unnumbered, 2013 four if link IP address is IPv4 and sixteen if link IP 2014 address is IPv6." 2016 OBJECT teLinkRemoteIpAddr 2017 SYNTAX InetAddress (SIZE(0|4|16)) 2018 DESCRIPTION 2019 "Size of TE link IP address depends on type of TE link. 2020 TE link IP address size is zero if link is unnumbered, 2021 four if link IP address is IPv4 and sixteen if link IP 2022 address is IPv6." 2024 OBJECT teLinkMuxCapability 2025 MIN-ACCESS read-only 2026 DESCRIPTION 2027 "Write access is not required." 2029 OBJECT teLinkProtectionType 2030 MIN-ACCESS read-only 2031 DESCRIPTION 2032 "Write access is not required." 2034 OBJECT teLinkWorkingPriority 2035 MIN-ACCESS read-only 2036 DESCRIPTION 2037 "Write access is not required." 2039 OBJECT teLinkFlooding 2040 MIN-ACCESS read-only 2041 DESCRIPTION 2042 "Write access is not required." 2044 OBJECT teLinkRowStatus 2045 SYNTAX INTEGER { active(1), notInService(2), 2046 createAndGo(4), destroy(6) } 2047 MIN-ACCESS read-only 2048 DESCRIPTION 2049 "The notReady(3) state need not be supported." 2051 OBJECT teLinkStorageType 2052 SYNTAX INTEGER { other(1) } 2053 MIN-ACCESS read-only 2054 DESCRIPTION 2055 "Only other(1) needs to be supported." 2057 -- teLinkDescriptorTable 2059 OBJECT teLinkEncodingType 2060 MIN-ACCESS read-only 2061 DESCRIPTION 2062 "Write access is not required." 2064 OBJECT teLinkDescrPriority 2065 MIN-ACCESS read-only 2066 DESCRIPTION 2067 "Write access is not required." 2069 OBJECT teLinkMinReservableBandwidth 2070 MIN-ACCESS read-only 2071 DESCRIPTION 2072 "Write access is not required." 2074 OBJECT teLinkMaxReservableBandwidth 2075 MIN-ACCESS read-only 2076 DESCRIPTION 2077 "Write access is not required." 2079 OBJECT teLinkDescrRowStatus 2080 SYNTAX INTEGER { active(1), notInService(2), 2081 createAndGo(4), destroy(6) } 2082 MIN-ACCESS read-only 2083 DESCRIPTION 2084 "The notReady(3) state need not be supported." 2086 OBJECT teLinkDescrStorageType 2087 SYNTAX INTEGER { other(1) } 2088 MIN-ACCESS read-only 2089 DESCRIPTION 2090 "Only other(1) needs to be supported." 2092 -- teLinkOspfTeTable 2094 OBJECT teLinkOspfLinkType 2095 SYNTAX INTEGER { pointToPoint(1) } 2096 DESCRIPTION 2097 "A value of multiAccess(2) need not be supported." 2099 OBJECT teLinkOspfLinkId 2100 MIN-ACCESS read-only 2101 DESCRIPTION 2102 "Write access is not required." 2104 -- teLinkSrlgTable 2106 OBJECT srlgRowStatus 2107 SYNTAX INTEGER { active(1), notInService(2), 2108 createAndGo(4), destroy(6) } 2109 MIN-ACCESS read-only 2110 DESCRIPTION 2111 "The notReady(3) and createAndWait(5) states need 2112 not be supported." 2114 OBJECT srlgStorageType 2115 SYNTAX INTEGER { other(1) } 2116 MIN-ACCESS read-only 2117 DESCRIPTION 2118 "Only other(1) needs to be supported." 2120 -- teLinkBandwidthTable 2122 OBJECT teLinkMaximumLspBandwidth 2123 MIN-ACCESS read-only 2124 DESCRIPTION 2125 "Write access is not required." 2127 OBJECT teLinkBandwidthRowStatus 2128 SYNTAX INTEGER { active(1), notInService(2), 2129 createAndGo(4), destroy(6) } 2130 MIN-ACCESS read-only 2131 DESCRIPTION 2132 "The notReady(3) and createAndWait(5) states need 2133 not be supported." 2135 OBJECT teLinkBandwidthStorageType 2136 SYNTAX INTEGER { other(1) } 2137 MIN-ACCESS read-only 2138 DESCRIPTION 2139 "Only other(1) needs to be supported." 2141 -- componentLinkTable 2143 OBJECT componentLinkMuxCapability 2144 MIN-ACCESS read-only 2145 DESCRIPTION 2146 "Write access is not required." 2148 OBJECT componentLinkPreferredProtection 2149 MIN-ACCESS read-only 2150 DESCRIPTION 2151 "Write access is not required." 2153 OBJECT componentLinkMaxReservBandwidth 2154 MIN-ACCESS read-only 2155 DESCRIPTION 2156 "Write access is not required." 2158 OBJECT componentLinkRowStatus 2159 SYNTAX INTEGER { active(1), notInService(2), 2160 createAndGo(4), destroy(6) } 2161 MIN-ACCESS read-only 2162 DESCRIPTION 2163 "The notReady(3) and createAndWait(5) states need 2164 not be supported." 2166 OBJECT componentLinkStorageType 2167 SYNTAX INTEGER { other(1) } 2168 MIN-ACCESS read-only 2169 DESCRIPTION 2170 "Only other(1) needs to be supported." 2172 -- componentLinkDescriptorTable 2174 OBJECT componentLinkEncodingType 2175 MIN-ACCESS read-only 2176 DESCRIPTION 2177 "Write access is not required." 2179 OBJECT componentLinkDescrPriority 2180 MIN-ACCESS read-only 2181 DESCRIPTION 2182 "Write access is not required." 2184 OBJECT componentLinkMinReservBandwidth 2185 MIN-ACCESS read-only 2186 DESCRIPTION 2187 "Write access is not required." 2189 OBJECT componentLinkDescrRowStatus 2190 SYNTAX INTEGER { active(1), notInService(2), 2191 createAndGo(4), destroy(6) } 2192 MIN-ACCESS read-only 2193 DESCRIPTION 2194 "The notReady(3) state need not be supported." 2196 OBJECT componentLinkDescrStorageType 2197 SYNTAX INTEGER { other(1) } 2198 MIN-ACCESS read-only 2199 DESCRIPTION 2200 "Only other(1) needs to be supported." 2202 -- componentLinkBandwidthTable 2204 OBJECT componentLinkMaximumLspBandwidth 2205 MIN-ACCESS read-only 2206 DESCRIPTION 2207 "Write access is not required." 2209 OBJECT componentLinkBandwidthRowStatus 2210 SYNTAX INTEGER { active(1), notInService(2), 2211 createAndGo(4), destroy(6) } 2212 MIN-ACCESS read-only 2213 DESCRIPTION 2214 "The notReady(3) and createAndWait(5) states need 2215 not be supported." 2217 OBJECT componentLinkBwStorageType 2218 SYNTAX INTEGER { other(1) } 2219 MIN-ACCESS read-only 2220 DESCRIPTION 2221 "Only other(1) needs to be supported." 2223 ::= { linkBundlingCompliances 2 } 2225 -- Units of conformance 2227 linkBundlingGroup OBJECT-GROUP 2228 OBJECTS { teLinkIpAddrType, 2229 teLinkIpAddr, 2230 teLinkRemoteIpAddr, 2231 teLinkMetric, 2232 teLinkMuxCapability, 2233 teLinkProtectionType, 2234 teLinkWorkingPriority, 2235 teLinkResourceClass, 2236 teLinkIncomingIfId, 2237 teLinkOutgoingIfId, 2238 teLinkFlooding, 2239 teLinkRowStatus, 2240 teLinkStorageType, 2241 teLinkEncodingType, 2242 teLinkDescrPriority, 2243 teLinkMinReservableBandwidth, 2244 teLinkMaxReservableBandwidth, 2245 teLinkDescrRowStatus, 2246 teLinkDescrStorageType, 2247 componentLinkMuxCapability, 2248 componentLinkPreferredProtection, 2249 componentLinkCurrentProtection, 2250 componentLinkRowStatus, 2251 componentLinkStorageType, 2252 linkBundlingNotifEnable 2253 } 2255 STATUS current 2256 DESCRIPTION 2257 "Collection of objects needed for the monitoring of 2258 resources associated with TE links." 2259 ::= { linkBundlingGroups 1 } 2261 teLinkOspfTeGroup OBJECT-GROUP 2262 OBJECTS { teLinkOspfLinkType, 2263 teLinkOspfLinkId 2264 } 2266 STATUS current 2267 DESCRIPTION 2268 "Collection of objects needed for the OSPF traffic 2269 engineering parameters of TE links." 2270 ::= { linkBundlingGroups 2 } 2272 teLinkSrlgGroup OBJECT-GROUP 2273 OBJECTS { srlgRowStatus, 2274 srlgStorageType 2275 } 2277 STATUS current 2278 DESCRIPTION 2279 "Collection of objects needed for the monitoring of 2280 SRLG resources associated with TE links." 2281 ::= { linkBundlingGroups 3 } 2283 teLinkBandwidthGroup OBJECT-GROUP 2284 OBJECTS { teLinkUnreservedBandwidth, 2285 teLinkMaximumLspBandwidth, 2286 teLinkBandwidthRowStatus, 2287 teLinkBandwidthStorageType 2288 } 2290 STATUS current 2291 DESCRIPTION 2292 "Collection of objects needed for the monitoring of 2293 the priority-based bandwidth resources associated with 2294 TE links and component links." 2295 ::= { linkBundlingGroups 4 } 2297 componentLinkBandwidthGroup OBJECT-GROUP 2298 OBJECTS { componentLinkEncodingType, 2299 componentLinkDescrPriority, 2300 componentLinkMinReservBandwidth, 2301 componentLinkMaxReservBandwidth, 2302 componentLinkDescrRowStatus, 2303 componentLinkDescrStorageType, 2304 componentLinkUnreservedBandwidth, 2305 componentLinkMaximumLspBandwidth, 2306 componentLinkBandwidthRowStatus, 2307 componentLinkBwStorageType 2308 } 2310 STATUS current 2311 DESCRIPTION 2312 "Collection of objects needed for the monitoring of 2313 bandwidth parameters associated with component links." 2314 ::= { linkBundlingGroups 5 } 2316 linkBundlingNotificationGroup NOTIFICATION-GROUP 2317 NOTIFICATIONS { linkBundleMismatch } 2318 STATUS current 2319 DESCRIPTION 2320 "Set of notifications implemented in this module. 2321 None is mandatory." 2322 ::= { linkBundlingGroups 6 } 2324 -- End of LINK-BUNDLING-MIB 2325 END 2327 11. Security Considerations 2329 It is clear that this MIB is potentially useful for monitoring of 2330 link bundling enabled devices. This MIB can also be used for confi- 2331 guration of certain objects, and anything that can be configured can 2332 be incorrectly configured, with potentially disastrous results. 2334 At this writing, no security holes have been identified beyond those 2335 that SNMP Security [RFC2571] is itself intended to address. These 2336 relate to primarily controlled access to sensitive information and 2337 the ability to configure a device - or which might result from opera- 2338 tor error, which is beyond the scope of any security architecture. 2340 There are a number of management objects defined in this MIB which 2341 have a MAX-ACCESS clause of read-write and/or read-create. Such 2342 objects may be considered sensitive or vulnerable in some network 2343 environments. The support for SET operations in a non-secure environ- 2344 ment without proper protection can have a negative effect on network 2345 operations. The use of SNMP Version 3 is recommended over prior ver- 2346 sions, for configuration control, as its security model is improved. 2348 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 2349 the network itself is secure (for example by using IPSec [RFC2401]), 2350 there is no control as to who on the secure network is allowed to 2351 access and GET/SET (read/change/create/delete) the objects in this 2352 MIB. It is recommended that the implementers consider the security 2353 features as provided by the SNMPv3 framework. Specifically, the use 2354 of the User-based Security Model [RFC2574] and the View-based Access 2355 Control [RFC2575] is recommended. It is then a customer/user respon- 2356 sibility to ensure that the SNMP entity giving access to an instance 2357 of this MIB is properly configured to give access to the objects only 2358 to those principals (users) that have legitimate rights to indeed GET 2359 or SET (change/create/delete) them. 2361 There are a number of managed objects in this MIB that may contain 2362 information that may be sensitive from a business perspective, in 2363 that they can be used to derive the network topology, e.g. list of 2364 nodes and their IP address (teLinkTable), list of component links 2365 (componentLinkTable) in addition to usage of network resources (teL- 2366 inkBandwidthTable and componentLinkBandwidthTable). Allowing uncon- 2367 trolled access to these objects could result in malicious and 2368 unwanted disruptions of network traffic, incorrect network configura- 2369 tion or theft of competitive business information. There are no 2370 objects that are particularly sensitive in their own right, such as 2371 passwords or monetary amounts. 2373 12. Acknowledgments 2375 The general structure of this draft has been modeled around draft- 2376 ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the 2377 contribution of Dmitry Ryumkin. 2379 13. References 2381 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2382 Identification of Management Information for TCP/IP- 2383 based Internets", STD 16, RFC 1155, May 1990. 2385 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2386 "Simple Network Management Protocol", STD 15, RFC 1157, 2387 May 1990. 2389 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2390 STD 16, RFC 1212, March 1991. 2392 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2393 the SNMP", RFC 1215, March 1991. 2395 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2396 "Introduction to Community-based SNMPv2", RFC 1901, 2397 January 1996. 2399 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2400 "Protocol Operations for Version 2 of the Simple 2401 Network Management Protocol (SNMPv2)", RFC 1905, 2402 January 1996. 2404 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2405 "Transport Mappings for Version 2 of the Simple Network 2406 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2408 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2409 Requirement Levels", BCP 14, RFC 2119, March 1997. 2411 [RFC2401] Kent, S., and Atkinson, R., "Security Architecture 2412 for the Internet Protocol", RFC 2401, November 2413 1998. 2415 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2416 "Introduction to Version 3 of the Internet-standard 2417 Network Management Framework", RFC 2570, April 1999. 2419 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2420 Architecture for Describing SNMP Management 2421 Frameworks", RFC 2571, April 1999. 2423 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2424 "Message Processing and Dispatching for the Simple 2425 Network Management Protocol (SNMP)", RFC 2572, April 2426 1999. 2428 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2429 Applications", RFC 2573, April 1999. 2431 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2432 Model (USM) for version 3 of the Simple Network 2433 Management Protocol (SNMPv3)", RFC 2574, April 1999. 2435 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2436 Access Control Model (VACM) for the Simple Network 2437 Management Protocol (SNMP)", RFC 2575, April 1999. 2439 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2440 J., Rose, M., and S. Waldbusser, "Structure of 2441 Management Information Version 2 (SMIv2)", STD 58, 2442 RFC 2578, April 1999. 2444 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2445 J., Rose, M., and S. Waldbusser, "Textual Conventions 2446 for SMIv2", STD 58, RFC 2579, April 1999. 2448 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2449 J., Rose, M., and S. Waldbusser, "Conformance 2450 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2452 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2453 Group MIB", RFC 2863, June 2000. 2455 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2456 RFC 1700, October 1994. See also: 2457 http://www.iana.org/assignments/smi-numbers 2459 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2460 "Link Bundling in MPLS Traffic Engineering", 2461 Internet Draft , 2462 May 2002. 2464 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 2465 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2466 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2467 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2468 "Generalized MPLS Signaling Functional Description", 2469 Internet Draft 2470 , 2471 April 2002. 2473 [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., 2474 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2475 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2476 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2477 Lang, J., Liaw, F., Nadeau, T., Ong, L., 2478 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2479 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2480 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2481 Zinin, A., "Generalized Multi-Protocol Label Switching 2482 (GMPLS) Architecture", Internet Draft 2483 , 2484 March 2002. 2486 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2487 Extensions in Support of Generalized MPLS", Internet 2488 Draft 2489 , 2490 May 2002. 2492 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2493 FAMILY NUMBERS, (http://www.isi.edu/in- 2494 notes/iana/assignements/address-family-numbers), 2495 for MIB see: 2497 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2499 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2500 Rekhter, Y., Berger, L., Rajagopalan, B., 2501 Basak, D., Sandick, H., Zinin, A., and 2502 Banarjee, A., "Link Management Protocol", 2503 Internet Draft , 2504 March 2002. 2506 [OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to 2507 OSPF", Internet Draft 2508 , October 2001. 2510 14. Authors' Addresses 2512 Martin Dubuc Thomas D. Nadeau 2513 Meriton Networks Cisco Systems, Inc. 2514 3026 Solandt Road 300 Apollo Drive 2515 Kanata, ON, CANADA K2K 2A5 Chelmsford, MA 01824 2516 Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051 2517 Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com 2519 Sudheer Dharanikota Jonathan P. Lang 2520 Nayna Networks, Inc. Calient Networks, Inc. 2521 157 Topaz Street 25 Castilian Drive 2522 Milipitas, CA 95035 Goleta, CA 93117 2523 Phone: +1-408-956-8000 x357 Email: jplang@calient.net 2524 Email: sudheer@nayna.com 2526 15. Full Copyright Statement 2528 Copyright (C) The Internet Society (2001). All Rights Reserved. 2530 This document and translations of it may be copied and furnished to 2531 others, and derivative works that comment on or otherwise explain it 2532 or assist in its implementation may be prepared, copied, published 2533 and distributed, in whole or in part, without restriction of any 2534 kind, provided that the above copyright notice and this paragraph are 2535 included on all such copies and derivative works. However, this docu- 2536 ment itself may not be modified in any way, such as by removing the 2537 copyright notice or references to the Internet Society or other 2538 Internet organizations, except as needed for the purpose of develop- 2539 ing Internet standards in which case the procedures for copyrights 2540 defined in the Internet Standards process must be followed, or as 2541 required to translate it into languages other than English. 2543 The limited permissions granted above are perpetual and will not be 2544 revoked by the Internet Society or its successors or assigns. This 2545 document and the information contained herein is provided on an "AS 2546 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2547 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2548 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2549 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2550 OR FITNESS FOR A PARTICULAR PURPOSE.