idnits 2.17.1 draft-ietf-mpls-bundle-mib-02.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 5 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([BUNDLING]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == 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 (May 2002) is 8016 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: 'LMP' is defined on line 2385, but no explicit reference was found in the text == Unused Reference: 'GMPLS' is defined on line 2392, but no explicit reference was found in the text == Unused Reference: 'OSPF' is defined on line 2414, but no explicit reference was found in the text == Unused Reference: 'LSP-HIER' is defined on line 2424, but no explicit reference was found in the text == Unused Reference: 'ZININ' is defined on line 2428, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2432, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 2437, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-ARCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSP-HIER' -- Possible downref: Non-RFC (?) normative reference: ref. 'ZININ' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) Summary: 21 errors (**), 0 flaws (~~), 10 warnings (==), 11 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: November 2002 5 Sudheer Dharanikota 6 Nayna Networks 8 Thomas D. Nadeau 9 Cisco Systems 11 Jonathan P. Lang 12 Calient Networks 14 May 2002 16 Link Bundling Management Information Base 18 draft-ietf-mpls-bundle-mib-02.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. dataBearingChannelTable ...................................... 7 56 7.7. dataBearingChannelDescriptorTable ............................ 7 57 7.8. dataBearingChannelBandwidthTable ............................. 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 an experimental portion of the Management Informa- 72 tion Base (MIB) for use with network management protocols in the 73 Internet community. In particular, it describes managed objects for 74 modeling link bundling as described in [BUNDLING]. 76 2. Introduction 78 OSPF, G-MPLS and LMP use the concept of traffic engineering (TE) 79 links to abstract link properties. The effect of this approach is the 80 reduction of the amount of routing information exchanged in the net- 81 work, which improves routing scalability. In addition, the use of TE 82 link allows the implementation of new capabilities such as link pro- 83 tection. 85 We present in this document a MIB that can be used to manage TE links 86 and their extension, the bundled link. This MIB enable both the con- 87 figuration and the performance monitoring of TE links and bundled 88 link. 90 Comments should be made directly to the MPLS mailing list at 91 mpls@uu.net. 93 This memo does not, in its draft form, specify a standard for the 94 Internet community. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119, reference 99 [BCP14]. 101 3. Terminology 103 This document uses terminology from the documents describing link 104 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 106 The link bundling feature is designed to aggregate one or more simi- 107 lar entities between a node pair into a bundled link [BUNDLING]. In 108 the document, those entities are referred to as TE links. A TE link 109 is a subinterface capable of carrying MPLS traffic engineered 110 traffic. A TE Link may be comprised of only one underlying data- 111 bearing channels. In cases where more than one data-bearing channel 112 is to be combined, multiple data-bearing links should be created with 113 differing priorities to indicate hot-standby or parallel utilization. 115 A bundled link is just another kind of Traffic Engineering (TE) link 116 (see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the 117 traffic of a group of one or more TE links. There should be more than 118 one TE Link in a link bundle, but this is not a requirement. Furth- 119 ermore, if there are more than one TE link in a link bundle at some 120 time, and at some point later, all but one of the links are deleted, 121 the agent may choose to either delete the link bundle, or it may 122 choose to leave it intact. Traffic counters on a link bundle are 123 cumulative for all subinterfaces which it binds together. 125 4. The SNMP Management Framework 127 The SNMP Management Framework presently consists of five major com- 128 ponents: 130 - An overall architecture, described in RFC 2571 [RFC2571]. 132 Mechanisms for describing and naming objects and events for the 133 purpose of management. The first version of this Structure of 134 Management Information (SMI) is called SMIv1 and described in 135 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 136 1215 [RFC1215]. The second version, called SMIv2, is described 137 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 138 STD 58, RFC 2580 [RFC2580]. 140 - Message protocols for transferring management information. The 141 first version of the SNMP message protocol is called SNMPv1 and 142 described in STD 15, RFC 1157 [RFC1157]. A second version of 143 the SNMP message protocol, which is not an Internet standards 144 track protocol, is called SNMPv2c and described in RFC 1901 145 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 146 message protocol is called SNMPv3 and described in RFC 1906 147 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 149 - Protocol operations for accessing management information. The 150 first set of protocol operations and associated PDU formats is 151 described in STD 15, RFC 1157 [RFC1157]. A second set of 152 protocol operations and associated PDU formats is described in 153 RFC 1905 [RFC1905]. 155 - A set of fundamental applications described in RFC 2573 156 [RFC2573] and the view-based access control mechanism described 157 in RFC 2575 [RFC2575]. 159 A more detailed introduction to the current SNMP Management Framework 160 can be found in RFC 2570 [RFC2570]. 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. Objects in the MIB are 164 defined using the mechanisms defined in the SMI. 166 This memo specifies a MIB module that is compliant to the SMIv2. A 167 MIB conforming to the SMIv1 can be produced through the appropriate 168 translations. The resulting translated MIB must be semantically 169 equivalent, except where objects or events are omitted because no 170 translation is possible (use of Counter64). Some machine readable 171 information in SMIv2 will be converted into textual descriptions in 172 SMIv1 during the translation process. However, this loss of machine 173 readable information is not considered to change the semantics of the 174 MIB. 176 5. Feature Checklist 178 The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the 179 following requirements and constraints: 181 - The MIB supports the management of TE links, including bundled 182 links. 184 - Support is provided for configuration of traffic engineering 185 parameters associated with TE links. 187 - The MIB is used to monitor the priority-based data-bearing channel 188 and TE link bandwidth values. 190 6. Outline 192 Configuring bundled links involves the following steps: 194 - Creating a bundled link. 196 - Creating TE links. 198 - Optionally specifying the shared risk link groups associated with 199 the TE links. 201 - Configuring the data-bearing channels including the bandwidth 202 parameters and associating the data-bearing channels with the 203 appropriate TE link. 205 - Associating the TE links with the appropriate bundled link. 207 6.1. Summary of Link Bundling MIB 209 The MIB objects for performing these actions consist of the following 210 tables: 212 - The TE link table (teLinkTable), which is used to 213 specify TE links, including bundled links, and their generic 214 traffic engineering parameters. 216 - The TE link descriptor table (teLinkDescriptorTable), which is 217 used to enumerate the TE link descriptors. 219 - The TE link OSPF traffic engineering table 220 (teLinkOspfTeTable), which is used for configuring OSPF 221 traffic engineering parameters associated with TE links. 223 - The shared risk link group (SRLG) table (teLinkSrlgTable), 224 which is used to specify the SRLGs associated with TE links. 226 - The TE link bandwidth table (teLinkBandwidthTable), 227 which is used for reporting priority-based bandwidth values 228 associated with TE links. 230 - The data-bearing channel table (dataBearingChannelTable), which is 231 used to identify the data-bearing channels that are associated 232 with the TE links and specify the data-bearing channel generic 233 traffic engineering parameters. 235 - The data-bearing channel link descriptor table 236 (dataBearingChannelDescriptorTable), which is used to enumerate 237 the data-bearing channel link descriptors. 239 - The data-bearing channel bandwidth table 240 (dataBearingChannelBandwidthTable), which is used to report 241 priority-based bandwidth values associated with data-bearing 242 channels. 244 These tables are described in the subsequent sections. 246 7. Brief Description of MIB Objects 248 Sections 7.1-7.5 describe objects pertaining to TE links. The MIB 249 objects were derived from the link bundling document [BUNDLING]. 251 7.1. teLinkTable 253 This table represents the TE links, including bundled links. 255 7.2. teLinkDescriptorTable 257 This table represents the TE link descriptors. 259 7.3. teLinkOspfTeTable 261 This table represents the OSPF traffic engineering parameters that 262 are associated with the TE links. 264 7.4. teLinkSrlgTable 266 This table represents the shared risk link groups (SRLGs) associated 267 with TE links. 269 7.5. teLinkBandwidthTable 271 This table specifies the priority-based bandwidth traffic engineering 272 parameters associated with TE links. 274 7.6. dataBearingChannelTable 276 This table enumerates the data-bearing channels and their association 277 with TE link. 279 7.7. dataBearingChannelDescriptorTable 281 This table enumerates the link descriptors that each data-bearing 282 channel supports. 284 7.8. dataBearingChannelBandwidthTable 286 The data-bearing channel bandwidth table specifies the priority-based 287 bandwidth values associated with the data-bearing channels. 289 8. Example of Bundled Link Setup 291 In this section we provide a brief example of using the MIB 292 objects described in section 10 to set up a bundled link. 293 While this example is not meant to illustrate every 294 nuance of the MIB, it is intended as an aid to understanding some 295 of the key concepts. It is meant to be read after going through the 296 MIB itself. 298 Suppose that one would like to manually create a bundled link 299 out of two 1:1 TE links. Assume that the bundled link is associated 300 with SRLGs 10 and 50. Finally, let the data-bearing channels be port 301 entity interfaces (lambdas). The following example illustrates which 302 rows and corresponding objects might be created to accomplish this. 304 First, a bundled link entry is created. An ifEntry with the same 305 ifIndex and with ifType teLink needs to be created beforehand. 307 In teLinkTable: 308 { 309 ifIndex = 25, 310 teLinkIpAddrType = unknown(0), 311 teLinkRowStatus = createAndGo(4) 312 } 314 In ifStackTable: 315 { 316 ifStackHigherLayer = 0, 317 ifStackLowerLayer = 25, 318 ifStackStatus = createAndGo(4) 319 } 321 Next, the two TE links are created. 323 In teLinkTable: 324 { 325 ifIndex = 20, 326 teLinkIpAddrType = unknown(0), 327 teLinkMetric = 5, 328 teLinkResourceClass = 3, 329 teLinkRowStatus = createAndWait(5) 330 } 332 In ifStackTable: 333 { 334 ifStackHigherLayer = 25, 335 ifStackLowerLayer = 20, 336 ifStackStatus = createAndGo(4) 337 } 339 In teLinkTable: 340 { 341 ifIndex = 21, 342 teLinkIpAddrType = unknown(0), 343 teLinkMetric = 5, 344 teLinkResourceClass = 3, 345 teLinkRowStatus = createAndWait(5) 346 } 348 In ifStackTable: 349 { 350 ifStackHigherLayer = 25, 351 ifStackLowerLayer = 21, 352 ifStackStatus = createAndGo(4) 354 } 356 The OSPF traffic engineering parameters are configured for the 357 TE links. 359 In teLinkOspfTeTable: 360 { 361 ifIndex = 20, 362 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 363 teLinkRowStatus = createAndGo(4) 364 } 366 In teLinkOspfTeTable: 367 { 368 ifIndex = 21, 369 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 370 teLinkRowStatus = createAndGo(4) 371 } 373 We assign SRLGs to the TE links. 375 In the teLinkSrlgTable: 376 { 377 ifIndex = 20, 378 srlg = 10, 379 srlgRowStatus = createAndGo(4) 380 } 382 In the teLinkSrlgTable: 383 { 384 ifIndex = 21, 385 srlg = 50, 386 srlgRowStatus = createAndGo(4) 387 } 389 The bundled link inherits the OSPF and SRLG properties from the 390 associated TE links. 392 Next, for each TE link, two data-bearing channels are created. 393 An ifEntry with the same ifIndex needs to be created beforehand. 395 In dataBearingChannelTable: 396 { 397 ifIndex = 40, 398 dataBearingChannelPreferredProtection = primary(1), 399 dataBearingChannelRowStatus = createAndGo(4) 400 } 401 In ifStackTable: 402 { 403 ifStackHigherLayer = 20, 404 ifStackLowerLayer = 40, 405 ifStackStatus = createAndGo(4) 406 } 408 In dataBearingChannelTable: 409 { 410 ifIndex = 43, 411 dataBearingChannelPreferredProtection = secondary(2), 412 dataBearingChannelRowStatus = createAndGo(4) 413 } 415 In ifStackTable: 416 { 417 ifStackHigherLayer = 20, 418 ifStackLowerLayer = 43, 419 ifStackStatus = createAndGo(4) 420 } 422 In dataBearingChannelTable: 423 { 424 ifIndex = 44, 425 dataBearingChannelPreferredProtection = primary(1), 426 dataBearingChannelRowStatus = createAndGo(4) 427 } 429 In ifStackTable: 430 { 431 ifStackHigherLayer = 21, 432 ifStackLowerLayer = 44, 433 ifStackStatus = createAndGo(4) 434 } 436 In dataBearingChannelTable: 437 { 438 ifIndex = 48, 439 dataBearingChannelPreferredProtection = secondary(2), 440 dataBearingChannelRowStatus = createAndGo(4) 441 } 443 In ifStackTable: 444 { 445 ifStackHigherLayer = 21, 446 ifStackLowerLayer = 48, 447 ifStackStatus = createAndGo(4) 448 } 449 In this example, once a data-bearing channel is added to the 450 dataBearingChannelTable, the associated link descriptors are 451 implicitly added to the dataBearingChannelDescriptorTable. 453 TE link link descriptors are derived from their data-bearing channel 454 link descriptors. 456 Note that the bandwidth attributes in teLinkDescriptorTable, 457 dataBearingChannelDescriptorTable, teLinkBandwidthTable 458 and dataBearingChannelBandwidthTable are maintained by the 459 device according to LSP creation/deletion at different priorities. 460 The values in the teLinkBandwidthTable are an aggregation 461 of the values for the data-bearing channels of the TE links and 462 the TE links of the bundled link. 464 9. Application of the Interfaces Group to TE Links 466 The Interfaces Group [IFMIB] defines generic managed objects for 467 managing interfaces. This memo contains the media-specific 468 extensions to the Interfaces Group for managing TE Link interfaces 469 as logical interfaces. 471 This memo assumes the interpretation of the Interfaces Group to be 472 in accordance with [IFMIB] which states that the interfaces table 473 (ifTable) contains information on the managed resource's 474 interfaces and that each sub-layer below the internetwork layer of 475 a network interface is considered an interface. Thus, the TE Link 476 interface is represented as an entry in the ifTable. The inter- 477 relation of entries in the ifTable is defined by Interfaces Stack 478 Group defined in [IFMIB]. 480 When using TE Link interfaces, the interface stack table might appear 481 as follows: 483 +----------------------------------------+ 484 | TE link-interface ifType = teLink(200) + 485 +----------------------------------------+ 486 | Underlying Layer... + 487 +----------------------------------------+ 489 In the above diagram, "Underlying Layer..." refers to the ifIndex 490 of any interface type, which has been defined for TE Link 491 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 493 9.1. Support of the TE Link Layer by ifTable 495 Some specific interpretations of ifTable for the TE Link layer 496 follow. 498 Object Use for the TE Link layer 500 ifIndex Each TE Link interface is represented by an ifEntry. 502 ifDescr Description of the TE Link interface. 504 ifType The value that is allocated for TE Link is 200. 506 ifSpeed The total bandwidth in bits per second for use by 507 the TE Link layer. 509 ifPhysAddress Unused. 511 ifAdminStatus This variable indicates the administrator's intent 512 as to whether TE Link should be enabled, disabled, or 513 running in some diagnostic testing mode on this 514 interface. Also see [IFMIB]. 516 ifOperStatus This value reflects the actual or operational 517 status of TE Link on this interface. 519 ifLastChange See [IFMIB]. 521 ifInOctets The number of received octets over the interface, 522 i.e., the number of received octets in all data-bearing 523 channels associated with the interface. 525 ifOutOctets The number of transmitted octets over the 526 interface, i.e., the number of octets transmitted 527 over all data-bearing channels associated with the 528 interface. 530 ifInErrors The number of packets dropped due to 531 uncorrectable errors. 533 ifInUnknownProtos 534 The number of received packets discarded during 535 packet header validation. 537 ifOutErrors See [IFMIB]. 539 ifName Textual name (unique on this system) of the 540 interface or an octet string of zero length. 542 ifLinkUpDownTrapEnable 543 Default is disabled (2). 545 ifConnectorPresent 546 Set to false (2). 548 ifHighSpeed See [IFMIB]. 550 ifHCInOctets The 64-bit version of ifInOctets; supported if 551 required by the compliance statements in [IFMIB]. 553 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 554 required by the compliance statements in [IFMIB]. 556 ifAlias The non-volatile 'alias' name for the interface as 557 specified by a network manager. 559 ifCounterDiscontinuityTime 560 See [IFMIB]. 562 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 563 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 564 if encoding type is clear. For other encoding types, traffic 565 counters on a TE link are cumulative for all subinterfaces which it 566 binds together. 568 9.2. Using ifStackTable 570 This section describes by example how to use ifStackTable to 571 represent the relationship of TE links with underlying TE-enabled 572 interfaces. Implementors of the stack table for TE link interfaces 573 should look at the appropriate RFC for the service being stacked 574 on TE links. Examples given below are for illustration purposes 575 only. 577 Example: MPLS is being carried on 2 bundled TE links. 578 Each bundled TE link runs over a 1:1 optical 579 transport interface. 581 +---------------------------------+ 582 | mpls | 583 +---------------------------------+ 584 | 585 +---------------------------------+ 586 | teLink (Link Bundle) | 587 +---------------------------------+ 588 | | 589 +---------------+ +---------------+ 590 | teLink | | teLink | 591 +---------------+ +---------------+ 592 | | | | 593 +------+ +------+ +------+ +------+ 594 |oTrans| |oTrans| |oTrans| |oTrans| 595 +------+ +------+ +------+ +------+ 597 The assignment of the index values could for example be: 599 ifIndex Description 600 1 mpls (type 166) 601 2 teLink (type 200) 602 3 teLink (type 200) 603 4 teLink (type 200) 604 5 opticalTransport (type 196) 605 6 opticalTransport (type 196) 606 7 opticalTransport (type 196) 607 8 opticalTransport (type 196) 609 The ifStackTable is then used to show the relationships between the 610 various interfaces. 612 ifStackTable Entries 614 HigherLayer LowerLayer 615 0 1 616 1 2 617 2 3 618 2 4 619 3 5 620 3 6 621 4 7 622 4 8 623 5 0 624 6 0 625 7 0 626 8 0 628 In the case where MPLS is using a single TE link, then 629 the upper TE link layer (link bundle) is not required. 631 +---------------+ 632 | mpls | 633 +---------------+ 634 | 636 +---------------+ 637 | teLink | 638 +---------------+ 639 | | 640 +------+ +------+ 641 |oTrans| |oTrans| 642 +------+ +------+ 644 The assignment of the index values could for example be: 646 ifIndex Description 647 1 mpls (type 166) 648 2 teLink (type 200) 649 3 opticalTransport (type 196) 650 4 opticalTransport (type 196) 652 The ifStackTable is then used to show the relationships between the 653 various interfaces. 655 ifStackTable Entries 657 HigherLayer LowerLayer 658 0 1 659 1 2 660 2 3 661 2 4 662 3 0 663 4 0 665 10. Link Bundling MIB Definitions 667 LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN 669 IMPORTS 670 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 671 experimental, Unsigned32 672 FROM SNMPv2-SMI 674 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 675 FROM SNMPv2-CONF 677 TruthValue, RowStatus, StorageType 678 FROM SNMPv2-TC 680 InterfaceIndexOrZero, ifIndex 681 FROM IF-MIB 683 RouterID 684 FROM OSPF-MIB 686 InetAddressType, InetAddress 687 FROM INET-ADDRESS-MIB; 689 linkBundlingMIB MODULE-IDENTITY 690 LAST-UPDATED "200205211200Z" -- 21 May 2002 12:00:00 EST 691 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 692 CONTACT-INFO 693 " Martin Dubuc 694 Postal: Meriton Networks 695 3026 Solandt Road 696 Kanata, ON, CANADA K2K 2A5 697 Tel: +1-613-270-9279 x253 698 Email: martin.dubuc@meriton.com 700 Sudheer Dharanikota 701 Postal: Nayna Networks, Inc. 702 157 Topaz Street 703 Milipitas, CA 95035 704 Tel: +1-408-956-8000 x357 705 Email: sudheer@nayna.com 707 Thomas D. Nadeau 708 Postal: Cisco Systems, Inc. 709 300 Apollo Drive 710 Chelmsford, MA 01824 711 Tel: +1-978-244-3051 712 Email: tnadeau@cisco.com 714 Jonathan P. Lang 715 Postal: Calient Networks, Inc. 716 25 Castilian Drive 717 Goleta, CA 93117 718 Email: jplang@calient.net" 720 DESCRIPTION 721 "This MIB contains managed object definitions for 722 MPLS traffic engineering link bundling as 723 defined in: Kompella, K., Rekhter, Y., Berger, L., 724 Link Bundling in MPLS Traffic Engineering 725 Internet Draft , 726 May 2002." 728 -- Revision history. 729 REVISION 730 "200205211200Z" -- 21 May 2002 12:00:00 EST 731 DESCRIPTION 732 "Addressed comments received during Last Call. 733 - Addressed syntax errors reports by smilint. 734 - Reintroduced teLinkIpAddrType. 735 - Replaced ifIndex in linkBundlingMismatch 736 notification with TE link endpoint objects." 737 REVISION 738 "200202261200Z" -- 26 February 2002 12:00:00 EST 739 DESCRIPTION 740 "- Updated MIB boiler plate and references. 741 - Added linkBundlingFullModuleCompliance conformance statement. 742 - Removed teLinkIpAddrType. Replaced numbered value with 743 ipV4 and ipV6 values in teLinkNumberingType. 744 - Updated description of all row status and storage type objects. 745 - Changed some of the enumerated value to start from 1 instead of 0. 746 - Updated references." 747 REVISION 748 "200109101200Z" -- 10 September 2001 12:00:00 EST 749 DESCRIPTION 750 "Removed teLinkRemoteId. Updated teLinkEncodingType and 751 dataBearingChannelEncodingType values." 752 REVISION 753 "200105221200Z" -- 22 May 2001 12:00:00 EST 754 DESCRIPTION 755 "Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress 756 and InetAddrType. Changed description of entries which extend 757 ifEntry. Made various minor corrections." 758 REVISION 759 "200105151200Z" -- 15 May 2001 12:00:00 EST 760 DESCRIPTION 761 "Replaced componentLinkTable by dataBearingChannelTable. 762 Replaced linkBundlingTable by teLinkTable. Converted TE links 763 into interfaces." 764 REVISION 765 "200102231200Z" -- 23 February 2001 12:00:00 EST 766 DESCRIPTION 767 "Initial draft version." 768 ::= { experimental 114 } 770 -- Textual Conventions 772 -- Top level components of this MIB 774 -- Notifications 775 linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } 776 -- Tables, Scalars 777 linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } 778 -- Conformance 779 linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } 781 -- TE Link Table 783 teLinkTable OBJECT-TYPE 784 SYNTAX SEQUENCE OF TeLinkEntry 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "This table specifies the grouping of data-bearing channels into 789 TE links and grouping of TE links into bundled links." 790 ::= { linkBundlingObjects 1 } 792 teLinkEntry OBJECT-TYPE 793 SYNTAX TeLinkEntry 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "An entry in this table exists for each ifEntry with an 798 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 799 in the ifTable must exist before a teLinkEntry is created with 800 the corresponding ifIndex. If a TE link entry in the ifTable is 801 destroyed, then so is the corresponding entry in the 802 teLinkTable. The administrative and operational status values 803 are controlled from the ifEntry. If the link is unnumbered, 804 ifIndex is also used as the outgoing interface identifier." 805 INDEX { ifIndex } 806 ::= { teLinkTable 1 } 808 TeLinkEntry ::= SEQUENCE { 809 teLinkIpAddrType InetAddressType, 810 teLinkIpAddr InetAddress, 811 teLinkRemoteIpAddr InetAddress, 812 teLinkMetric Unsigned32, 813 teLinkMuxCapability INTEGER, 814 teLinkProtectionType INTEGER, 815 teLinkWorkingPriority Unsigned32, 816 teLinkResourceClass Unsigned32, 817 teLinkIncomingIfId InterfaceIndexOrZero, 818 teLinkOutgoingIfId InterfaceIndexOrZero, 819 teLinkFlooding InterfaceIndexOrZero, 820 teLinkRowStatus RowStatus, 821 teLinkStorageType StorageType 822 } 823 teLinkIpAddrType OBJECT-TYPE 824 SYNTAX InetAddressType 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "For IPv4 and IPv6 numbered links, this object represents the 829 IP address type associated with the TE link. For 830 unnumbered links, a value of unknown(0) must be used." 831 ::= { teLinkEntry 1 } 833 teLinkIpAddr OBJECT-TYPE 834 SYNTAX InetAddress 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "For IPv4 and IPv6 numbered links, this object represents the 839 IP address associated with the TE link." 840 ::= { teLinkEntry 2 } 842 teLinkRemoteIpAddr OBJECT-TYPE 843 SYNTAX InetAddress 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "The remote IP address associated with the TE link (IPv4 and 848 IPv6 numbered links)." 849 ::= { teLinkEntry 3 } 851 teLinkMetric OBJECT-TYPE 852 SYNTAX Unsigned32 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "The traffic engineering metric for the TE link is 857 derived from its data-bearing channels. All data-bearing 858 channels within the TE link must have the same traffic 859 engineering metric." 860 REFERENCE 861 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 862 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 863 May 2002." 864 ::= { teLinkEntry 4 } 866 teLinkMuxCapability OBJECT-TYPE 867 SYNTAX INTEGER { 868 packetSwitch1(1), 869 packetSwitch2(2), 870 packetSwitch3(3), 871 packetSwitch4(4), 872 layer2Switch(51), 873 tdm(100), 874 lambdaSwitch(150), 875 fiberSwitch(200) 876 } 877 MAX-ACCESS read-create 878 STATUS current 879 DESCRIPTION 880 "This attribute specifies link multiplex capability of the 881 TE link, which is derived from its data-bearing channels. All 882 data-bearing channels within the same TE link must have the 883 same link multiplex capability." 884 REFERENCE 885 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 886 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 887 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 888 D. Saha, V. Sharma, May 2002." 889 ::= { teLinkEntry 5 } 891 teLinkProtectionType OBJECT-TYPE 892 SYNTAX INTEGER { 893 extraTraffic(1), 894 unprotected(2), 895 shared(3), 896 dedicated1For1(4), 897 dedicated1Plus1(5), 898 enhanced(6) 899 } 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "This attribute specifies link protection type of the 904 TE link." 905 REFERENCE 906 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 907 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 908 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 909 D. Saha, V. Sharma, May 2002." 910 ::= { teLinkEntry 6 } 912 teLinkWorkingPriority OBJECT-TYPE 913 SYNTAX Unsigned32 (0..7) 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "This object represents a priority value such that a new 918 connection with a higher priority, i.e. numerically lower than 919 this value, is guaranteed to be setup on a primary channel and 920 not on a secondary channel." 921 REFERENCE 922 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 923 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 924 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 925 D. Saha, V. Sharma, May 2002." 926 ::= { teLinkEntry 7 } 928 teLinkResourceClass OBJECT-TYPE 929 SYNTAX Unsigned32 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "This attribute specifies the TE link resource class. 934 The resource class is a 32 bit bitfield. The resource class for 935 a link bundle is derived from the resource class of its 936 TE links. All TE links within a link bundle must have the 937 same resource class." 938 ::= { teLinkEntry 8 } 940 teLinkIncomingIfId OBJECT-TYPE 941 SYNTAX InterfaceIndexOrZero 942 MAX-ACCESS read-create 943 STATUS current 944 DESCRIPTION 945 "For unnumbered links, the incoming interface is set to the 946 outgoing interface identifier chosen by the neighboring LSR 947 for the reverse link corresponding to this TE link." 948 REFERENCE 949 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 950 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 951 May 2002." 952 ::= { teLinkEntry 9 } 954 teLinkOutgoingIfId OBJECT-TYPE 955 SYNTAX InterfaceIndexOrZero 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "If the link is unnumbered, the outgoing interface identifier is 960 set to the outgoing interface identifier chosen for the TE link 961 by the advertising LSR." 962 REFERENCE 963 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 964 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 965 May 2002." 966 ::= { teLinkEntry 10 } 968 teLinkFlooding OBJECT-TYPE 969 SYNTAX InterfaceIndexOrZero 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION 973 "This object only has significance for link bundles which 974 encoding type is not clear. For these link bundles, this object 975 identifies the TE link on which to restrict flooding. If the 976 value is zero, then flooding must be done on all TE links 977 within the link bundle." 978 REFERENCE 979 "draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization 980 in link-state routing protocols, A. Zinin, M. Shand, 981 March 2001." 982 DEFVAL { 0 } 983 ::= { teLinkEntry 11 } 985 teLinkRowStatus OBJECT-TYPE 986 SYNTAX RowStatus 987 MAX-ACCESS read-create 988 STATUS current 989 DESCRIPTION 990 "This variable is used to create, modify, and/or 991 delete a row in this table. All read-create objects 992 can only be changed when teLinkRowStatus is active." 993 ::= { teLinkEntry 12 } 995 teLinkStorageType OBJECT-TYPE 996 SYNTAX StorageType 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "The storage type for this conceptual row in the 1001 teLinkTable. Conceptual rows having the value 1002 'permanent' need not allow write-access to any 1003 columnar object in the row." 1004 ::= { teLinkEntry 13 } 1006 -- End of teLinkTable 1008 -- TE Link Descriptor Table 1010 teLinkDescriptorTable OBJECT-TYPE 1011 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 1012 MAX-ACCESS not-accessible 1013 STATUS current 1014 DESCRIPTION 1015 "This table specifies the link descriptors associated with the 1016 TE links." 1017 ::= { linkBundlingObjects 2 } 1019 teLinkDescriptorEntry OBJECT-TYPE 1020 SYNTAX TeLinkDescriptorEntry 1021 MAX-ACCESS not-accessible 1022 STATUS current 1023 DESCRIPTION 1024 "An entry in this table is created for every TE link descriptor. 1025 An ifEntry in the ifTable must exist before a 1026 teLinkDescriptorEntry using the same ifIndex is created. 1027 If a TE link entry in the ifTable is destroyed, then so are all 1028 entries in the teLinkDescriptorTable that use the ifIndex of 1029 this TE link." 1030 INDEX { ifIndex, teLinkDescriptorId } 1031 ::= { teLinkDescriptorTable 1 } 1033 TeLinkDescriptorEntry ::= SEQUENCE { 1034 teLinkDescriptorId Unsigned32, 1035 teLinkEncodingType INTEGER, 1036 teLinkDescrPriority Unsigned32, 1037 teLinkMinReservableBandwidth Unsigned32, 1038 teLinkMaxReservableBandwidth Unsigned32, 1039 teLinkDescrRowStatus RowStatus, 1040 teLinkDescrStorageType StorageType 1041 } 1043 teLinkDescriptorId OBJECT-TYPE 1044 SYNTAX Unsigned32 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 "This object specifies the link descriptor identifier." 1049 ::= { teLinkDescriptorEntry 1 } 1051 teLinkEncodingType OBJECT-TYPE 1052 SYNTAX INTEGER { 1053 packet(1), 1054 ethernet(2), 1055 ansiEtsiPdh(3), 1056 sdhItuSonetAnsi(5), 1057 digitalWrapper(7), 1058 lambda(8), 1059 fiber(9), 1060 fiberChannel(11) 1061 } 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "This attribute specifies the TE link encoding type." 1066 REFERENCE 1067 "draft-ietf-mpls-generalized-signaling-08.txt - Generalized 1068 MPLS Signaling Functional Description, P. Ashwood-Smith, 1069 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 1070 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 1071 V. Sharma, G. Swallow, Z. Tang, April 2002." 1072 ::= { teLinkDescriptorEntry 2 } 1074 teLinkDescrPriority OBJECT-TYPE 1075 SYNTAX Unsigned32 (0..7) 1076 MAX-ACCESS read-create 1077 STATUS current 1078 DESCRIPTION 1079 "This object specifies the lowest priority at which that link 1080 encoding type is available." 1081 REFERENCE 1082 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1083 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1084 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1085 D. Saha, V. Sharma, May 2002." 1086 ::= { teLinkDescriptorEntry 3 } 1088 teLinkMinReservableBandwidth OBJECT-TYPE 1089 SYNTAX Unsigned32 1090 MAX-ACCESS read-create 1091 STATUS current 1092 DESCRIPTION 1093 "This attribute specifies the minimum reservable bandwidth on 1094 the TE link. This is derived from the union of the 1095 minimum reservable bandwidth of all the data-bearing 1096 channels associated with the TE link that can be used to carry 1097 live traffic. This value is an estimate in units of 1,000 bits 1098 per second." 1099 REFERENCE 1100 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1101 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1102 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1103 D. Saha, V. Sharma, May 2002." 1104 ::= { teLinkDescriptorEntry 4 } 1106 teLinkMaxReservableBandwidth OBJECT-TYPE 1107 SYNTAX Unsigned32 1108 MAX-ACCESS read-create 1109 STATUS current 1110 DESCRIPTION 1111 "This attribute specifies the maximum reservable bandwidth on 1112 the TE link. This is the union of the maximum reservable 1113 bandwidth of all the data-bearing channels within the 1114 TE link that can be used to carry live traffic. This value 1115 is an estimate in units of 1,000 bits per second." 1116 REFERENCE 1117 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1118 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1119 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1120 D. Saha, V. Sharma, May 2002." 1121 ::= { teLinkDescriptorEntry 5 } 1123 teLinkDescrRowStatus OBJECT-TYPE 1124 SYNTAX RowStatus 1125 MAX-ACCESS read-create 1126 STATUS current 1127 DESCRIPTION 1128 "This variable is used to create, modify, and/or 1129 delete a row in this table. All read-create objects 1130 can only be changed when teLinkDescrRowStatus is active." 1131 ::= { teLinkDescriptorEntry 6 } 1133 teLinkDescrStorageType OBJECT-TYPE 1134 SYNTAX StorageType 1135 MAX-ACCESS read-create 1136 STATUS current 1137 DESCRIPTION 1138 "The storage type for this conceptual row in the 1139 teLinkDescriptorTable. Conceptual rows having the value 1140 'permanent' need not allow write-access to any 1141 columnar object in the row." 1142 ::= { teLinkDescriptorEntry 7 } 1144 -- End of teLinkDescriptorTable 1146 -- OSPF Traffic Engineering Parameters for TE Links 1148 teLinkOspfTeTable OBJECT-TYPE 1149 SYNTAX SEQUENCE OF TeLinkOspfTeEntry 1150 MAX-ACCESS not-accessible 1151 STATUS current 1152 DESCRIPTION 1153 "This table specifies the OSPF traffic engineering information 1154 associated with TE links." 1155 ::= { linkBundlingObjects 3 } 1157 teLinkOspfTeEntry OBJECT-TYPE 1158 SYNTAX TeLinkOspfTeEntry 1159 MAX-ACCESS not-accessible 1160 STATUS current 1161 DESCRIPTION 1162 "If OSPF is enabled, an entry in this table is created for 1163 every TE link." 1164 AUGMENTS { teLinkEntry } 1165 ::= { teLinkOspfTeTable 1 } 1167 TeLinkOspfTeEntry ::= SEQUENCE { 1168 teLinkOspfLinkType INTEGER, 1169 teLinkOspfLinkId RouterID 1170 } 1172 teLinkOspfLinkType OBJECT-TYPE 1173 SYNTAX INTEGER { 1174 pointToPoint(1), 1175 multiAccess(2) 1176 } 1177 MAX-ACCESS read-create 1178 STATUS current 1179 DESCRIPTION 1180 "This attribute specifies the OSPF link type for the TE link. 1181 All TE links within the same bundle must have the same 1182 link type." 1183 ::= { teLinkOspfTeEntry 1 } 1185 teLinkOspfLinkId OBJECT-TYPE 1186 SYNTAX RouterID 1187 MAX-ACCESS read-create 1188 STATUS current 1189 DESCRIPTION 1190 "On point-to-point link, the link identifier is the Router ID 1191 of the neighbor. For bundled link, is derived from the link 1192 identifier associated with its TE links." 1193 REFERENCE 1194 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 1195 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1196 May 2002." 1197 ::= { teLinkOspfTeEntry 2 } 1199 -- End of teLinkOspfTeTable 1201 -- TE Link Shared Risk Link Group Table 1203 teLinkSrlgTable OBJECT-TYPE 1204 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1205 MAX-ACCESS not-accessible 1206 STATUS current 1207 DESCRIPTION 1208 "This table specifies the SRLGs associated with TE links." 1209 ::= { linkBundlingObjects 4 } 1211 teLinkSrlgEntry OBJECT-TYPE 1212 SYNTAX TeLinkSrlgEntry 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION 1216 "An entry in this table contains information about a 1217 SRLG associated with a TE link. 1218 An ifEntry in the ifTable must exist before a 1219 teLinkSrlgEntry using the same ifIndex is created. 1220 If a TE link entry in the ifTable is destroyed, then so are all 1221 entries in the teLinkSrlgTable that use the ifIndex of 1222 this TE link." 1223 INDEX { ifIndex, srlg } 1224 ::= { teLinkSrlgTable 1 } 1226 TeLinkSrlgEntry ::= SEQUENCE { 1227 srlg Unsigned32, 1228 srlgRowStatus RowStatus, 1229 srlgStorageType StorageType 1230 } 1232 srlg OBJECT-TYPE 1233 SYNTAX Unsigned32 1234 MAX-ACCESS not-accessible 1235 STATUS current 1236 DESCRIPTION 1237 "This identifies a SRLG supported by the TE link." 1238 REFERENCE 1239 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1240 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1241 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1242 D. Saha, V. Sharma, May 2002." 1243 ::= { teLinkSrlgEntry 1 } 1245 srlgRowStatus OBJECT-TYPE 1246 SYNTAX RowStatus 1247 MAX-ACCESS read-create 1248 STATUS current 1249 DESCRIPTION 1250 "This variable is used to create, modify, and/or 1251 delete a row in this table. All read-create objects 1252 can only be changed when srlgRowStatus is active." 1254 ::= { teLinkSrlgEntry 2 } 1256 srlgStorageType OBJECT-TYPE 1257 SYNTAX StorageType 1258 MAX-ACCESS read-create 1259 STATUS current 1260 DESCRIPTION 1261 "The storage type for this conceptual row in the 1262 teLinkSrlgTable. Conceptual rows having the value 1263 'permanent' need not allow write-access to any 1264 columnar object in the row." 1265 ::= { teLinkSrlgEntry 3 } 1267 -- End of teLinkSrlgTable 1269 -- TE Link Bandwidth Table 1271 teLinkBandwidthTable OBJECT-TYPE 1272 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "This table specifies the priority-based bandwidth table 1277 for TE links." 1278 ::= { linkBundlingObjects 5 } 1280 teLinkBandwidthEntry OBJECT-TYPE 1281 SYNTAX TeLinkBandwidthEntry 1282 MAX-ACCESS not-accessible 1283 STATUS current 1284 DESCRIPTION 1285 "An entry in this table contains information about 1286 the priority-based bandwidth of TE links. An ifEntry in the 1287 ifTable must exist before a teLinkBandwidthEntry using the 1288 same ifIndex is created. If a TE link entry in the ifTable 1289 is destroyed, then so are all entries in the teLinkBandwidthTable 1290 that use the ifIndex of this TE link." 1291 INDEX { ifIndex, teLinkPriority } 1292 ::= { teLinkBandwidthTable 1 } 1294 TeLinkBandwidthEntry ::= SEQUENCE { 1295 teLinkPriority Unsigned32, 1296 teLinkUnreservedBandwidth Unsigned32, 1297 teLinkMaximumLspBandwidth Unsigned32, 1298 teLinkBandwidthRowStatus RowStatus, 1299 teLinkBandwidthStorageType StorageType 1300 } 1301 teLinkPriority OBJECT-TYPE 1302 SYNTAX Unsigned32 (1..8) 1303 MAX-ACCESS not-accessible 1304 STATUS current 1305 DESCRIPTION 1306 "This attribute specifies the priority. It should be mapped 1307 to a number between 0 and 7" 1308 REFERENCE 1309 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1310 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1311 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1312 D. Saha, V. Sharma, May 2002." 1313 ::= { teLinkBandwidthEntry 1 } 1315 teLinkUnreservedBandwidth OBJECT-TYPE 1316 SYNTAX Unsigned32 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "This attribute specifies the TE link unreserved 1321 bandwidth at priority p. It is the sum of the unreserved 1322 bandwidths at priority p of all data-bearing channel associated 1323 with the TE link (excludes all channels that are strictly 1324 used as protecting channels). This value is an estimate in units 1325 of 1,000 bits per second." 1326 REFERENCE 1327 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 1328 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1329 May 2002." 1330 ::= { teLinkBandwidthEntry 2 } 1332 teLinkMaximumLspBandwidth OBJECT-TYPE 1333 SYNTAX Unsigned32 1334 MAX-ACCESS read-create 1335 STATUS current 1336 DESCRIPTION 1337 "This attribute specifies the TE link maximum 1338 LSP bandwidth at priority p. It is the maximum of all 1339 maximum LSP bandwidth at priority p of the data-bearing channels 1340 associated with the TE link (excludes all channels that are 1341 strictly used as protecting channels). This value is an estimate 1342 in units of 1,000 bits per second." 1343 REFERENCE 1344 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS 1345 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1346 May 2002." 1347 ::= { teLinkBandwidthEntry 3 } 1349 teLinkBandwidthRowStatus OBJECT-TYPE 1350 SYNTAX RowStatus 1351 MAX-ACCESS read-create 1352 STATUS current 1353 DESCRIPTION 1354 "This variable is used to create, modify, and/or 1355 delete a row in this table. All read-create objects 1356 can only be changed when teLinkBandwidthRowStatus is active." 1357 ::= { teLinkBandwidthEntry 4 } 1359 teLinkBandwidthStorageType OBJECT-TYPE 1360 SYNTAX StorageType 1361 MAX-ACCESS read-create 1362 STATUS current 1363 DESCRIPTION 1364 "The storage type for this conceptual row in the 1365 teLinkBandwidthTable. Conceptual rows having the value 1366 'permanent' need not allow write-access to any 1367 columnar object in the row." 1368 ::= { teLinkBandwidthEntry 5 } 1370 -- End of teLinkBandwidthTable 1372 -- Data-bearing Channel Table 1374 dataBearingChannelTable OBJECT-TYPE 1375 SYNTAX SEQUENCE OF DataBearingChannelEntry 1376 MAX-ACCESS not-accessible 1377 STATUS current 1378 DESCRIPTION 1379 "This table specifies the data-bearing channel 1380 parameters." 1381 ::= { linkBundlingObjects 6 } 1383 dataBearingChannelEntry OBJECT-TYPE 1384 SYNTAX DataBearingChannelEntry 1385 MAX-ACCESS not-accessible 1386 STATUS current 1387 DESCRIPTION 1388 "An entry in this table exists for each ifEntry that represents 1389 a data-bearing channel. An ifEntry must exist in the ifTable 1390 before a dataBearingChannelEntry is created with the 1391 corresponding ifIndex. If an entry representing a data-bearing 1392 channel is destroyed in the ifTable, then so is the 1393 corresponding entry in the dataBearingChannelTable. The 1394 administrative and operational status values are controlled 1395 from the ifEntry." 1397 INDEX { ifIndex } 1398 ::= { dataBearingChannelTable 1 } 1400 DataBearingChannelEntry ::= SEQUENCE { 1401 dataBearingChannelLinkMuxCapability INTEGER, 1402 dataBearingChannelPreferredProtection INTEGER, 1403 dataBearingChannelCurrentProtection INTEGER, 1404 dataBearingChannelRowStatus RowStatus, 1405 dataBearingChannelStorageType StorageType 1406 } 1408 dataBearingChannelLinkMuxCapability 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 data-bearing channel." 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 ::= { dataBearingChannelEntry 1 } 1431 dataBearingChannelPreferredProtection 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 data-bearing channel is 1440 a primary or secondary entity." 1441 ::= { dataBearingChannelEntry 2 } 1443 dataBearingChannelCurrentProtection 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 data-bearing channel is 1452 currently used as primary or secondary channel." 1453 ::= { dataBearingChannelEntry 3 } 1455 dataBearingChannelRowStatus 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 dataBearingChannelRowStatus is active." 1463 ::= { dataBearingChannelEntry 4 } 1465 dataBearingChannelStorageType 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 dataBearingChannelTable. Conceptual rows having the value 1472 'permanent' need not allow write-access to any 1473 columnar object in the row." 1474 ::= { dataBearingChannelEntry 5 } 1476 -- End of dataBearingChannelTable 1478 -- Data-bearing Channel Link Descriptor Table 1480 dataBearingChannelDescriptorTable OBJECT-TYPE 1481 SYNTAX SEQUENCE OF DataBearingChannelDescriptorEntry 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "This table specifies the link descriptors associated with the 1486 data-bearing channels." 1487 ::= { linkBundlingObjects 7 } 1489 dataBearingChannelDescriptorEntry OBJECT-TYPE 1490 SYNTAX DataBearingChannelDescriptorEntry 1491 MAX-ACCESS not-accessible 1492 STATUS current 1493 DESCRIPTION 1494 "An entry in this table is created for every data-bearing channel 1495 descriptor. An ifEntry in the ifTable must exist before a 1496 dataBearingChannelDescriptorEntry using the same ifIndex is created. 1497 If a data-bearing channel entry in the ifTable is destroyed, 1498 then so are all entries in the 1499 dataBearingChannelDescriptorTable that use the ifIndex of 1500 this data-bearing channel." 1501 INDEX { ifIndex, dataBearingChannelDescrId } 1502 ::= { dataBearingChannelDescriptorTable 1 } 1504 DataBearingChannelDescriptorEntry ::= SEQUENCE { 1505 dataBearingChannelDescrId Unsigned32, 1506 dataBearingChannelEncodingType INTEGER, 1507 dataBearingChannelDescrPriority Unsigned32, 1508 dataBearingChannelMinReservableBandwidth Unsigned32, 1509 dataBearingChannelMaxReservableBandwidth Unsigned32, 1510 dataBearingChannelDescrRowStatus RowStatus, 1511 dataBearingChannelDescrStorageType StorageType 1512 } 1514 dataBearingChannelDescrId OBJECT-TYPE 1515 SYNTAX Unsigned32 1516 MAX-ACCESS not-accessible 1517 STATUS current 1518 DESCRIPTION 1519 "This object specifies the link descriptor identifier." 1520 ::= { dataBearingChannelDescriptorEntry 1 } 1522 dataBearingChannelEncodingType OBJECT-TYPE 1523 SYNTAX INTEGER { 1524 packet(1), 1525 ethernet(2), 1526 ansiEtsiPdh(3), 1527 sdhItuSonetAnsi(5), 1528 digitalWrapper(7), 1529 lambda(8), 1530 fiber(9), 1531 fiberChannel(11) 1532 } 1533 MAX-ACCESS read-create 1534 STATUS current 1535 DESCRIPTION 1536 "This attribute specifies the data-bearing channel encoding type." 1537 REFERENCE 1538 "draft-ietf-mpls-generalized-signaling-08.txt - Generalized 1539 MPLS Signaling Functional Description, P. Ashwood-Smith, 1540 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 1541 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 1542 V. Sharma, G. Swallow, Z. Tang, April 2002." 1543 ::= { dataBearingChannelDescriptorEntry 2 } 1545 dataBearingChannelDescrPriority OBJECT-TYPE 1546 SYNTAX Unsigned32 (0..7) 1547 MAX-ACCESS read-create 1548 STATUS current 1549 DESCRIPTION 1550 "This object specifies the lowest priority at which that link 1551 encoding type is available for the data-bearing channel." 1552 REFERENCE 1553 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1554 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1555 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1556 D. Saha, V. Sharma, May 2002." 1557 ::= { dataBearingChannelDescriptorEntry 3 } 1559 dataBearingChannelMinReservableBandwidth OBJECT-TYPE 1560 SYNTAX Unsigned32 1561 MAX-ACCESS read-create 1562 STATUS current 1563 DESCRIPTION 1564 "This attribute specifies the minimum reservable bandwidth on 1565 the data-bearing channel. This value is an estimate 1566 in units of 1,000 bits per second." 1567 REFERENCE 1568 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1569 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1570 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1571 D. Saha, V. Sharma, May 2002." 1572 ::= { dataBearingChannelDescriptorEntry 4 } 1574 dataBearingChannelMaxReservableBandwidth OBJECT-TYPE 1575 SYNTAX Unsigned32 1576 MAX-ACCESS read-create 1577 STATUS current 1578 DESCRIPTION 1579 "This attribute specifies the maximum reservable bandwidth on 1580 the data-bearing channel. This value is an estimate 1581 in units of 1,000 bits per second." 1582 REFERENCE 1583 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1584 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1585 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1586 D. Saha, V. Sharma, May 2002." 1587 ::= { dataBearingChannelDescriptorEntry 5 } 1589 dataBearingChannelDescrRowStatus OBJECT-TYPE 1590 SYNTAX RowStatus 1591 MAX-ACCESS read-create 1592 STATUS current 1593 DESCRIPTION 1594 "This variable is used to create, modify, and/or 1595 delete a row in this table. All read-create objects 1596 can only be changed when dataBearingChannelDescrRowStatus 1597 is active." 1598 ::= { dataBearingChannelDescriptorEntry 6 } 1600 dataBearingChannelDescrStorageType OBJECT-TYPE 1601 SYNTAX StorageType 1602 MAX-ACCESS read-create 1603 STATUS current 1604 DESCRIPTION 1605 "The storage type for this conceptual row in the 1606 dataBearingChannelDescriptorTable. Conceptual rows 1607 having the value 'permanent' need not allow write-access 1608 to any columnar object in the row." 1609 ::= { dataBearingChannelDescriptorEntry 7 } 1611 -- End of dataBearingChannelDescriptorTable 1613 -- Data-bearing Channel Bandwidth Table 1615 dataBearingChannelBandwidthTable OBJECT-TYPE 1616 SYNTAX SEQUENCE OF DataBearingChannelBandwidthEntry 1617 MAX-ACCESS not-accessible 1618 STATUS current 1619 DESCRIPTION 1620 "This table specifies the priority-based bandwidth 1621 for data-bearing channels." 1622 ::= { linkBundlingObjects 8 } 1624 dataBearingChannelBandwidthEntry OBJECT-TYPE 1625 SYNTAX DataBearingChannelBandwidthEntry 1626 MAX-ACCESS not-accessible 1627 STATUS current 1628 DESCRIPTION 1629 "An entry in this table contains information about 1630 the priority-based bandwidth on data-bearing channels. 1631 An ifEntry in the ifTable must exist before a 1632 dataBearingChannelBandwidthEntry using the same ifIndex is 1633 created. If a data-bearing channel entry in the ifTable is 1634 destroyed, then so are all entries in the 1635 dataBearingChannelBandwidthTable that use the ifIndex of 1636 this data-bearing channel." 1637 INDEX { ifIndex, dataBearingChannelPriority } 1638 ::= { dataBearingChannelBandwidthTable 1 } 1640 DataBearingChannelBandwidthEntry ::= SEQUENCE { 1641 dataBearingChannelPriority Unsigned32, 1642 dataBearingChannelUnreservedBandwidth Unsigned32, 1643 dataBearingChannelMaximumLspBandwidth Unsigned32, 1644 dataBearingChannelBwRowStatus RowStatus, 1645 dataBearingChannelBwStorageType StorageType 1646 } 1648 dataBearingChannelPriority 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 ::= { dataBearingChannelBandwidthEntry 1 } 1662 dataBearingChannelUnreservedBandwidth OBJECT-TYPE 1663 SYNTAX Unsigned32 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "This attribute specifies the data-bearing channel 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 ::= { dataBearingChannelBandwidthEntry 2 } 1677 dataBearingChannelMaximumLspBandwidth OBJECT-TYPE 1678 SYNTAX Unsigned32 1679 MAX-ACCESS read-create 1680 STATUS current 1681 DESCRIPTION 1682 "This attribute specifies the data-bearing channel maximum 1683 LSP bandwidth at priority p. This value is an estimate 1684 in units of 1,000 bits per second." 1685 REFERENCE 1686 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions 1687 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1688 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1689 D. Saha, V. Sharma, May 2002." 1690 ::= { dataBearingChannelBandwidthEntry 3 } 1692 dataBearingChannelBwRowStatus OBJECT-TYPE 1693 SYNTAX RowStatus 1694 MAX-ACCESS read-create 1695 STATUS current 1696 DESCRIPTION 1697 "This variable is used to create, modify, and/or 1698 delete a row in this table. All read-create objects 1699 can only be changed when dataBearingChannelBwRowStatus is active." 1700 ::= { dataBearingChannelBandwidthEntry 4 } 1702 dataBearingChannelBwStorageType OBJECT-TYPE 1703 SYNTAX StorageType 1704 MAX-ACCESS read-create 1705 STATUS current 1706 DESCRIPTION 1707 "The storage type for this conceptual row in the 1708 dataBearingChannelBandwidthTable. Conceptual rows 1709 having the value 'permanent' need not allow write-access 1710 to any columnar object in the row." 1711 ::= { dataBearingChannelBandwidthEntry 5 } 1713 -- End of dataBearingChannelBandwidthTable 1715 -- Notification Configuration 1717 linkBundlingNotifEnable OBJECT-TYPE 1718 SYNTAX TruthValue 1719 MAX-ACCESS read-write 1720 STATUS current 1721 DESCRIPTION 1722 "If this object is true, then it enables the 1723 generation of the link bundling notifications, 1724 otherwise these notifications are not emitted." 1725 DEFVAL { false } 1726 ::= { linkBundlingObjects 9 } 1728 -- Notifications 1729 -- Bundled Link Notifications 1731 linkBundleMismatch NOTIFICATION-TYPE 1732 OBJECTS { teLinkIpAddrType, teLinkIpAddr, teLinkRemoteIpAddr } 1733 STATUS current 1734 DESCRIPTION 1735 "This notification is generated when a mismatch is found on a 1736 bundled link. Such mismatch can be detected for instance if one 1737 of the traffic engineering parameters is not consistent across 1738 all TE links within a bundled link (resource class, 1739 OSPF link type, etc.)." 1740 ::= { linkBundlingNotifications 1 } 1742 -- End of notifications 1744 -- Module compliance 1746 linkBundlingGroups 1747 OBJECT IDENTIFIER ::= { linkBundlingConformance 1 } 1749 linkBundlingCompliances 1750 OBJECT IDENTIFIER ::= { linkBundlingConformance 2 } 1752 linkBundlingFullModuleCompliance MODULE-COMPLIANCE 1753 STATUS current 1754 DESCRIPTION 1755 "Compliance statement for agents that support the 1756 configuration and monitoring of link bundling MIB." 1757 MODULE -- this module 1759 -- The mandatory groups have to be implemented 1760 -- by all devices supporting link bundling. However, they may all 1761 -- be supported as read-only objects in the case where automatic 1762 -- configuration is supported. 1764 MANDATORY-GROUPS { linkBundlingGroup, 1765 teLinkBandwidthGroup, 1766 dataBearingChannelBandwidthGroup } 1768 GROUP teLinkOspfTeGroup 1769 DESCRIPTION 1770 "This group is mandatory for OSPF enabled devices." 1772 GROUP teLinkSrlgGroup 1773 DESCRIPTION 1774 "This group is mandatory for G-MPLS enabled devices." 1776 GROUP linkBundlingNotificationGroup 1777 DESCRIPTION 1778 "This group is mandatory for equipment that support 1779 link bundling notifications." 1781 -- teLinkTable 1783 OBJECT teLinkIpAddrType 1784 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 1785 MIN-ACCESS read-only 1786 DESCRIPTION 1787 "The dns(16) address type need not be supported. 1788 The ipv4(1) and ipv6(2) address types need not be 1789 supported if numbered links are not supported. The 1790 unknown(0) address type need not be supported if 1791 unnumbered links are not supported." 1793 OBJECT teLinkIpAddr 1794 SYNTAX InetAddress (SIZE(0|4|16)) 1795 DESCRIPTION 1796 "Size of TE link IP address depends on type of TE link. 1797 TE link IP address size is zero if link is unnumbered, 1798 four if link IP address is IPv4 and sixteen if link IP 1799 address is IPv6." 1801 OBJECT teLinkRemoteIpAddr 1802 SYNTAX InetAddress (SIZE(0|4|16)) 1803 DESCRIPTION 1804 "Size of TE link IP address depends on type of TE link. 1805 TE link IP address size is zero if link is unnumbered, 1806 four if link IP address is IPv4 and sixteen if link IP 1807 address is IPv6." 1809 OBJECT teLinkMuxCapability 1810 MIN-ACCESS read-only 1811 DESCRIPTION 1812 "Write access is not required." 1814 OBJECT teLinkProtectionType 1815 MIN-ACCESS read-only 1816 DESCRIPTION 1817 "Write access is not required." 1819 OBJECT teLinkRowStatus 1820 SYNTAX INTEGER { active(1), notInService(2), 1821 createAndGo(4), destroy(6) } 1822 DESCRIPTION 1823 "The notReady(3) state need not be supported." 1825 OBJECT teLinkStorageType 1826 SYNTAX INTEGER { other(1) } 1827 DESCRIPTION 1828 "Only other(1) needs to be supported." 1830 -- teLinkDescriptorTable 1832 OBJECT teLinkEncodingType 1833 MIN-ACCESS read-only 1834 DESCRIPTION 1835 "Write access is not required." 1837 OBJECT teLinkDescrPriority 1838 MIN-ACCESS read-only 1839 DESCRIPTION 1840 "Write access is not required." 1842 OBJECT teLinkMinReservableBandwidth 1843 MIN-ACCESS read-only 1844 DESCRIPTION 1845 "Write access is not required." 1847 OBJECT teLinkMaxReservableBandwidth 1848 MIN-ACCESS read-only 1849 DESCRIPTION 1850 "Write access is not required." 1852 OBJECT teLinkDescrRowStatus 1853 SYNTAX INTEGER { active(1), notInService(2), 1854 createAndGo(4), destroy(6) } 1855 DESCRIPTION 1856 "The notReady(3) state need not be supported." 1858 OBJECT teLinkDescrStorageType 1859 SYNTAX INTEGER { other(1) } 1860 DESCRIPTION 1861 "Only other(1) needs to be supported." 1863 -- teLinkOspfTeTable 1865 OBJECT teLinkOspfLinkType 1866 SYNTAX INTEGER { pointToPoint(1) } 1867 MIN-ACCESS read-only 1868 DESCRIPTION 1869 "A value of multiAccess(2) need not be supported." 1871 OBJECT teLinkOspfLinkId 1872 MIN-ACCESS read-only 1873 DESCRIPTION 1874 "Write access is not required." 1876 -- teLinkSrlgTable 1878 OBJECT srlgRowStatus 1879 SYNTAX INTEGER { active(1), notInService(2), 1880 createAndGo(4), destroy(6) } 1881 DESCRIPTION 1882 "The notReady(3) and createAndWait(5) states need 1883 not be supported." 1885 OBJECT srlgStorageType 1886 SYNTAX INTEGER { other(1) } 1887 DESCRIPTION 1888 "Only other(1) needs to be supported." 1890 -- teLinkBandwidthTable 1892 OBJECT teLinkMaximumLspBandwidth 1893 MIN-ACCESS read-only 1894 DESCRIPTION 1895 "Write access is not required." 1897 OBJECT teLinkBandwidthRowStatus 1898 SYNTAX INTEGER { active(1), notInService(2), 1899 createAndGo(4), destroy(6) } 1900 DESCRIPTION 1901 "The notReady(3) and createAndWait(5) states need 1902 not be supported." 1904 OBJECT teLinkBandwidthStorageType 1905 SYNTAX INTEGER { other(1) } 1906 DESCRIPTION 1907 "Only other(1) needs to be supported." 1909 -- dataBearingChannelTable 1911 OBJECT dataBearingChannelLinkMuxCapability 1912 MIN-ACCESS read-only 1913 DESCRIPTION 1914 "Write access is not required." 1916 OBJECT dataBearingChannelMaxReservableBandwidth 1917 MIN-ACCESS read-only 1918 DESCRIPTION 1919 "Write access is not required." 1921 OBJECT dataBearingChannelRowStatus 1922 SYNTAX INTEGER { active(1), notInService(2), 1923 createAndGo(4), destroy(6) } 1924 DESCRIPTION 1925 "The notReady(3) and createAndWait(5) states need 1926 not be supported." 1928 OBJECT dataBearingChannelStorageType 1929 SYNTAX INTEGER { other(1) } 1930 DESCRIPTION 1931 "Only other(1) needs to be supported." 1933 -- dataBearingChannelDescriptorTable 1935 OBJECT dataBearingChannelDescrRowStatus 1936 SYNTAX INTEGER { active(1), notInService(2), 1937 createAndGo(4), destroy(6) } 1938 DESCRIPTION 1939 "The notReady(3) state need not be supported." 1941 OBJECT dataBearingChannelDescrStorageType 1942 SYNTAX INTEGER { other(1) } 1943 DESCRIPTION 1944 "Only other(1) needs to be supported." 1946 -- dataBearingChannelBandwidthTable 1948 OBJECT dataBearingChannelMaximumLspBandwidth 1949 MIN-ACCESS read-only 1950 DESCRIPTION 1951 "Write access is not required." 1953 OBJECT dataBearingChannelBwRowStatus 1954 SYNTAX INTEGER { active(1), notInService(2), 1955 createAndGo(4), destroy(6) } 1956 DESCRIPTION 1957 "The notReady(3) and createAndWait(5) states need 1958 not be supported." 1960 OBJECT dataBearingChannelBwStorageType 1961 SYNTAX INTEGER { other(1) } 1962 DESCRIPTION 1963 "Only other(1) needs to be supported." 1965 ::= { linkBundlingCompliances 1 } 1967 linkBundlingMonitoringModuleCompliance MODULE-COMPLIANCE 1968 STATUS current 1969 DESCRIPTION 1970 "Compliance statement for agents that support the 1971 monitoring of link bundling MIB." 1972 MODULE -- this module 1974 -- The mandatory groups have to be implemented 1975 -- by all devices supporting link bundling. However, they may all 1976 -- be supported as read-only objects in the case where manual 1977 -- configuration is unsupported. 1979 MANDATORY-GROUPS { linkBundlingGroup, 1980 teLinkBandwidthGroup, 1981 dataBearingChannelBandwidthGroup } 1983 GROUP teLinkOspfTeGroup 1984 DESCRIPTION 1985 "This group is mandatory for OSPF enabled devices." 1987 GROUP teLinkSrlgGroup 1988 DESCRIPTION 1989 "This group is mandatory for G-MPLS enabled devices." 1991 GROUP linkBundlingNotificationGroup 1992 DESCRIPTION 1993 "This group is optional." 1995 -- teLinkTable 1997 OBJECT teLinkIpAddrType 1998 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 1999 MIN-ACCESS read-only 2000 DESCRIPTION 2001 "The dns(16) address type need not be supported. 2002 The ipv4(1) and ipv6(2) address types need not be 2003 supported if numbered links are not supported. The 2004 unknown(0) address type need not be supported if 2005 unnumbered links are not supported." 2007 OBJECT teLinkIpAddr 2008 SYNTAX InetAddress (SIZE(0|4|16)) 2009 DESCRIPTION 2010 "Size of TE link IP address depends on type of TE link. 2011 TE link IP address size is zero if link is unnumbered, 2012 four if link IP address is IPv4 and sixteen if link IP 2013 address is IPv6." 2015 OBJECT teLinkRemoteIpAddr 2016 SYNTAX InetAddress (SIZE(0|4|16)) 2017 DESCRIPTION 2018 "Size of TE link IP address depends on type of TE link. 2019 TE link IP address size is zero if link is unnumbered, 2020 four if link IP address is IPv4 and sixteen if link IP 2021 address is IPv6." 2023 OBJECT teLinkMuxCapability 2024 MIN-ACCESS read-only 2025 DESCRIPTION 2026 "Write access is not required." 2028 OBJECT teLinkProtectionType 2029 MIN-ACCESS read-only 2030 DESCRIPTION 2031 "Write access is not required." 2033 OBJECT teLinkWorkingPriority 2034 MIN-ACCESS read-only 2035 DESCRIPTION 2036 "Write access is not required." 2038 OBJECT teLinkFlooding 2039 MIN-ACCESS read-only 2040 DESCRIPTION 2041 "Write access is not required." 2043 OBJECT teLinkRowStatus 2044 SYNTAX INTEGER { active(1), notInService(2), 2045 createAndGo(4), destroy(6) } 2046 MIN-ACCESS read-only 2047 DESCRIPTION 2048 "The notReady(3) state need not be supported." 2050 OBJECT teLinkStorageType 2051 SYNTAX INTEGER { other(1) } 2052 MIN-ACCESS read-only 2053 DESCRIPTION 2054 "Only other(1) needs to be supported." 2056 -- teLinkDescriptorTable 2058 OBJECT teLinkEncodingType 2059 MIN-ACCESS read-only 2060 DESCRIPTION 2061 "Write access is not required." 2063 OBJECT teLinkDescrPriority 2064 MIN-ACCESS read-only 2065 DESCRIPTION 2066 "Write access is not required." 2068 OBJECT teLinkMinReservableBandwidth 2069 MIN-ACCESS read-only 2070 DESCRIPTION 2071 "Write access is not required." 2073 OBJECT teLinkMaxReservableBandwidth 2074 MIN-ACCESS read-only 2075 DESCRIPTION 2076 "Write access is not required." 2078 OBJECT teLinkDescrRowStatus 2079 SYNTAX INTEGER { active(1), notInService(2), 2080 createAndGo(4), destroy(6) } 2081 MIN-ACCESS read-only 2082 DESCRIPTION 2083 "The notReady(3) state need not be supported." 2085 OBJECT teLinkDescrStorageType 2086 SYNTAX INTEGER { other(1) } 2087 MIN-ACCESS read-only 2088 DESCRIPTION 2089 "Only other(1) needs to be supported." 2091 -- teLinkOspfTeTable 2093 OBJECT teLinkOspfLinkType 2094 SYNTAX INTEGER { pointToPoint(1) } 2095 DESCRIPTION 2096 "A value of multiAccess(2) need not be supported." 2098 OBJECT teLinkOspfLinkId 2099 MIN-ACCESS read-only 2100 DESCRIPTION 2101 "Write access is not required." 2103 -- teLinkSrlgTable 2105 OBJECT srlgRowStatus 2106 SYNTAX INTEGER { active(1), notInService(2), 2107 createAndGo(4), destroy(6) } 2108 MIN-ACCESS read-only 2109 DESCRIPTION 2110 "The notReady(3) and createAndWait(5) states need 2111 not be supported." 2113 OBJECT srlgStorageType 2114 SYNTAX INTEGER { other(1) } 2115 MIN-ACCESS read-only 2116 DESCRIPTION 2117 "Only other(1) needs to be supported." 2119 -- teLinkBandwidthTable 2121 OBJECT teLinkMaximumLspBandwidth 2122 MIN-ACCESS read-only 2123 DESCRIPTION 2124 "Write access is not required." 2126 OBJECT teLinkBandwidthRowStatus 2127 SYNTAX INTEGER { active(1), notInService(2), 2128 createAndGo(4), destroy(6) } 2129 MIN-ACCESS read-only 2130 DESCRIPTION 2131 "The notReady(3) and createAndWait(5) states need 2132 not be supported." 2134 OBJECT teLinkBandwidthStorageType 2135 SYNTAX INTEGER { other(1) } 2136 MIN-ACCESS read-only 2137 DESCRIPTION 2138 "Only other(1) needs to be supported." 2140 -- dataBearingChannelTable 2142 OBJECT dataBearingChannelLinkMuxCapability 2143 MIN-ACCESS read-only 2144 DESCRIPTION 2145 "Write access is not required." 2147 OBJECT dataBearingChannelPreferredProtection 2148 MIN-ACCESS read-only 2149 DESCRIPTION 2150 "Write access is not required." 2152 OBJECT dataBearingChannelMaxReservableBandwidth 2153 MIN-ACCESS read-only 2154 DESCRIPTION 2155 "Write access is not required." 2157 OBJECT dataBearingChannelRowStatus 2158 SYNTAX INTEGER { active(1), notInService(2), 2159 createAndGo(4), destroy(6) } 2160 MIN-ACCESS read-only 2161 DESCRIPTION 2162 "The notReady(3) and createAndWait(5) states need 2163 not be supported." 2165 OBJECT dataBearingChannelStorageType 2166 SYNTAX INTEGER { other(1) } 2167 MIN-ACCESS read-only 2168 DESCRIPTION 2169 "Only other(1) needs to be supported." 2171 -- dataBearingChannelDescriptorTable 2173 OBJECT dataBearingChannelEncodingType 2174 MIN-ACCESS read-only 2175 DESCRIPTION 2176 "Write access is not required." 2178 OBJECT dataBearingChannelDescrPriority 2179 MIN-ACCESS read-only 2180 DESCRIPTION 2181 "Write access is not required." 2183 OBJECT dataBearingChannelMinReservableBandwidth 2184 MIN-ACCESS read-only 2185 DESCRIPTION 2186 "Write access is not required." 2188 OBJECT dataBearingChannelDescrRowStatus 2189 SYNTAX INTEGER { active(1), notInService(2), 2190 createAndGo(4), destroy(6) } 2191 MIN-ACCESS read-only 2192 DESCRIPTION 2193 "The notReady(3) state need not be supported." 2195 OBJECT dataBearingChannelDescrStorageType 2196 SYNTAX INTEGER { other(1) } 2197 MIN-ACCESS read-only 2198 DESCRIPTION 2199 "Only other(1) needs to be supported." 2201 -- dataBearingChannelBandwidthTable 2203 OBJECT dataBearingChannelMaximumLspBandwidth 2204 MIN-ACCESS read-only 2205 DESCRIPTION 2206 "Write access is not required." 2208 OBJECT dataBearingChannelBwRowStatus 2209 SYNTAX INTEGER { active(1), notInService(2), 2210 createAndGo(4), destroy(6) } 2211 MIN-ACCESS read-only 2212 DESCRIPTION 2213 "The notReady(3) and createAndWait(5) states need 2214 not be supported." 2216 OBJECT dataBearingChannelBwStorageType 2217 SYNTAX INTEGER { other(1) } 2218 MIN-ACCESS read-only 2219 DESCRIPTION 2220 "Only other(1) needs to be supported." 2222 ::= { linkBundlingCompliances 2 } 2224 -- Units of conformance 2226 linkBundlingGroup OBJECT-GROUP 2227 OBJECTS { teLinkIpAddrType, 2228 teLinkIpAddr, 2229 teLinkRemoteIpAddr, 2230 teLinkMetric, 2231 teLinkMuxCapability, 2232 teLinkProtectionType, 2233 teLinkWorkingPriority, 2234 teLinkResourceClass, 2235 teLinkIncomingIfId, 2236 teLinkOutgoingIfId, 2237 teLinkFlooding, 2238 teLinkRowStatus, 2239 teLinkStorageType, 2240 teLinkEncodingType, 2241 teLinkDescrPriority, 2242 teLinkMinReservableBandwidth, 2243 teLinkMaxReservableBandwidth, 2244 teLinkDescrRowStatus, 2245 teLinkDescrStorageType, 2246 dataBearingChannelLinkMuxCapability, 2247 dataBearingChannelPreferredProtection, 2248 dataBearingChannelCurrentProtection, 2249 dataBearingChannelRowStatus, 2250 dataBearingChannelStorageType, 2251 linkBundlingNotifEnable 2252 } 2254 STATUS current 2255 DESCRIPTION 2256 "Collection of objects needed for the monitoring of 2257 resources associated with TE links." 2258 ::= { linkBundlingGroups 1 } 2260 teLinkOspfTeGroup OBJECT-GROUP 2261 OBJECTS { teLinkOspfLinkType, 2262 teLinkOspfLinkId 2263 } 2265 STATUS current 2266 DESCRIPTION 2267 "Collection of objects needed for the OSPF traffic 2268 engineering parameters of TE links." 2269 ::= { linkBundlingGroups 2 } 2271 teLinkSrlgGroup OBJECT-GROUP 2272 OBJECTS { srlgRowStatus, 2273 srlgStorageType 2274 } 2276 STATUS current 2277 DESCRIPTION 2278 "Collection of objects needed for the monitoring of 2279 SRLG resources associated with TE links." 2280 ::= { linkBundlingGroups 3 } 2282 teLinkBandwidthGroup OBJECT-GROUP 2283 OBJECTS { teLinkUnreservedBandwidth, 2284 teLinkMaximumLspBandwidth, 2285 teLinkBandwidthRowStatus, 2286 teLinkBandwidthStorageType 2287 } 2289 STATUS current 2290 DESCRIPTION 2291 "Collection of objects needed for the monitoring of 2292 the priority-based bandwidth resources associated with 2293 TE links and data-bearing channels." 2294 ::= { linkBundlingGroups 4 } 2296 dataBearingChannelBandwidthGroup OBJECT-GROUP 2297 OBJECTS { dataBearingChannelEncodingType, 2298 dataBearingChannelDescrPriority, 2299 dataBearingChannelMinReservableBandwidth, 2300 dataBearingChannelMaxReservableBandwidth, 2301 dataBearingChannelDescrRowStatus, 2302 dataBearingChannelDescrStorageType, 2303 dataBearingChannelUnreservedBandwidth, 2304 dataBearingChannelMaximumLspBandwidth, 2305 dataBearingChannelBwRowStatus, 2306 dataBearingChannelBwStorageType 2307 } 2309 STATUS current 2310 DESCRIPTION 2311 "Collection of objects needed for the monitoring of 2312 bandwidth parameters associated with data-bearing channels." 2313 ::= { linkBundlingGroups 5 } 2315 linkBundlingNotificationGroup NOTIFICATION-GROUP 2316 NOTIFICATIONS { linkBundleMismatch } 2317 STATUS current 2318 DESCRIPTION 2319 "Set of notifications implemented in this module. 2320 None is mandatory." 2321 ::= { linkBundlingGroups 6 } 2323 -- End of LINK-BUNDLING-MIB 2324 END 2326 11. Security Considerations 2328 It is clear that this MIB is potentially useful for monitoring of 2329 link bundling enabled devices. This MIB can also be used for confi- 2330 guration of certain objects, and anything that can be configured can 2331 be incorrectly configured, with potentially disastrous results. 2333 At this writing, no security holes have been identified beyond those 2334 that SNMP Security [RFC2571] is itself intended to address. These 2335 relate to primarily controlled access to sensitive information and 2336 the ability to configure a device - or which might result from opera- 2337 tor error, which is beyond the scope of any security architecture. 2339 There are a number of management objects defined in this MIB which 2340 have a MAX-ACCESS clause of read-write and/or read-create. Such 2341 objects may be considered sensitive or vulnerable in some network 2342 environments. The support for SET operations in a non-secure environ- 2343 ment without proper protection can have a negative effect on network 2344 operations. The use of SNMP Version 3 is recommended over prior ver- 2345 sions, for configuration control, as its security model is improved. 2347 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 2348 the network itself is secure (for example by using IPSec [IPSEC]), 2349 there is no control as to who on the secure network is allowed to 2350 access and GET/SET (read/change/create/delete) the objects in this 2351 MIB. It is recommended that the implementers consider the security 2352 features as provided by the SNMPv3 framework. Specifically, the use 2353 of the User-based Security Model [RFC2574] and the View-based Access 2354 Control [RFC2575] is recommended. It is then a customer/user respon- 2355 sibility to ensure that the SNMP entity giving access to an instance 2356 of this MIB is properly configured to give access to the objects only 2357 to those principals (users) that have legitimate rights to indeed GET 2358 or SET (change/create/delete) them. 2360 There are a number of managed objects in this MIB that may contain 2361 information that may be sensitive from a business perspective, in 2362 that they can be used to derive the network topology, e.g. list of 2363 nodes and their IP address (teLinkTable), list of data-bearing chan- 2364 nels (dataBearingChannelTable) in addition to usage of network 2365 resources (teLinkBandwidthTable and dataBearingChannelBandwidthT- 2366 able). Allowing uncontrolled access to these objects could result in 2367 malicious and unwanted disruptions of network traffic, incorrect net- 2368 work configuration or theft of competitive business information. 2369 There are no objects that are particularly sensitive in their own 2370 right, such as passwords or monetary amounts. 2372 12. Acknowledgments 2374 The general structure of this draft has been modeled around draft- 2375 ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the 2376 contribution of Dmitry Ryumkin. 2378 13. References 2380 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2381 "Link Bundling in MPLS Traffic Engineering", 2382 Internet Draft , 2383 May 2002. 2385 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2386 Rekhter, Y., Berger, L., Rajagopalan, B., 2387 Basak, D., Sandick, H., Zinin, A., and 2388 Banarjee, A., "Link Management Protocol", 2389 Internet Draft , 2390 March 2002. 2392 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 2393 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2394 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2395 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2396 "Generalized MPLS Signaling Functional Description", 2397 Internet Draft 2398 , 2399 April 2002. 2401 [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., 2402 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2403 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2404 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2405 Lang, J., Liaw, F., Nadeau, T., Ong, L., 2406 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2407 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2408 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2409 Zinin, A., "Generalized Multi-Protocol Label Switching 2410 (GMPLS) Architecture", Internet Draft 2411 , 2412 March 2002. 2414 [OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to 2415 OSPF", Internet Draft 2416 , October 2001. 2418 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2419 Extensions in Support of Generalized MPLS", Internet 2420 Draft 2421 , 2422 May 2002. 2424 [LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE, 2425 Internet Draft , 2426 May 2001. 2428 [ZININ] Zinin, A., SHand, M., "Flooding optimizations in link- 2429 state routing protocols", Internet Draft, 2430 , March 2001. 2432 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2433 RFC 1700, October 1994. See also: 2434 http://www.isi.edu/in-notes/iana/assignments/smi- 2435 numbers 2437 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2438 FAMILY NUMBERS, (http://www.isi.edu/in- 2439 notes/iana/assignements/address-family-numbers), 2440 for MIB see: 2441 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2443 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2444 Architecture for Describing SNMP Management 2445 Frameworks", RFC 2571, April 1999. 2447 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2448 Identification of Management Information for TCP/IP- 2449 based Internets", STD 16, RFC 1155, May 1990. 2451 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2452 STD 16, RFC 1212, March 1991. 2454 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2455 the SNMP", RFC 1215, March 1991. 2457 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2458 J., Rose, M., and S. Waldbusser, "Structure of 2459 Management Information Version 2 (SMIv2)", STD 58, 2460 RFC 2578, April 1999. 2462 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2463 J., Rose, M., and S. Waldbusser, "Textual Conventions 2464 for SMIv2", STD 58, RFC 2579, April 1999. 2466 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2467 J., Rose, M., and S. Waldbusser, "Conformance 2468 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2470 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2471 "Simple Network Management Protocol", STD 15, RFC 1157, 2472 May 1990. 2474 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2475 "Introduction to Community-based SNMPv2", RFC 1901, 2476 January 1996. 2478 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2479 "Transport Mappings for Version 2 of the Simple Network 2480 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2482 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2483 "Message Processing and Dispatching for the Simple 2484 Network Management Protocol (SNMP)", RFC 2572, April 2485 1999. 2487 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2488 Model (USM) for version 3 of the Simple Network 2489 Management Protocol (SNMPv3)", RFC 2574, April 1999. 2491 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2492 "Protocol Operations for Version 2 of the Simple 2493 Network Management Protocol (SNMPv2)", RFC 1905, 2494 January 1996. 2496 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2497 Applications", RFC 2573, April 1999. 2499 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2500 Access Control Model (VACM) for the Simple Network 2501 Management Protocol (SNMP)", RFC 2575, April 1999. 2503 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2504 "Introduction to Version 3 of the Internet-standard 2505 Network Management Framework", RFC 2570, April 1999. 2507 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2508 for the Internet Protocol", RFC 2401, November 2509 1998. 2511 [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2512 Group MIB", RFC 2863, June 2000. 2514 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2515 Requirement Levels", BCP 14, RFC 2119, March 1997. 2517 14. Authors' Addresses 2519 Martin Dubuc Thomas D. Nadeau 2520 Meriton Networks Cisco Systems, Inc. 2521 3026 Solandt Road 300 Apollo Drive 2522 Kanata, ON, CANADA K2K 2A5 Chelmsford, MA 01824 2523 Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051 2524 Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com 2526 Sudheer Dharanikota Jonathan P. Lang 2527 Nayna Networks, Inc. Calient Networks, Inc. 2528 157 Topaz Street 25 Castilian Drive 2529 Milipitas, CA 95035 Goleta, CA 93117 2530 Phone: +1-408-956-8000 x357 Email: jplang@calient.net 2531 Email: sudheer@nayna.com 2533 15. Full Copyright Statement 2535 Copyright (C) The Internet Society (2001). All Rights Reserved. 2537 This document and translations of it may be copied and furnished to 2538 others, and derivative works that comment on or otherwise explain it 2539 or assist in its implementation may be prepared, copied, published 2540 and distributed, in whole or in part, without restriction of any 2541 kind, provided that the above copyright notice and this paragraph are 2542 included on all such copies and derivative works. However, this docu- 2543 ment itself may not be modified in any way, such as by removing the 2544 copyright notice or references to the Internet Society or other 2545 Internet organizations, except as needed for the purpose of develop- 2546 ing Internet standards in which case the procedures for copyrights 2547 defined in the Internet Standards process must be followed, or as 2548 required to translate it into languages other than English. 2550 The limited permissions granted above are perpetual and will not be 2551 revoked by the Internet Society or its successors or assigns. This 2552 document and the information contained herein is provided on an "AS 2553 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2554 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2555 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2556 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2557 OR FITNESS FOR A PARTICULAR PURPOSE.