idnits 2.17.1 draft-ietf-mpls-telink-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (August 2003) is 7552 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: 'RFC3291' is defined on line 2461, but no explicit reference was found in the text == Unused Reference: 'HIERARCHY' is defined on line 2482, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'HIERARCHY' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAifType' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'ROUTING' Summary: 3 errors (**), 0 flaws (~~), 2 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 4 Category: Standards Track Sudheer Dharanikota 5 Expires: February 2003 6 Thomas D. Nadeau 7 Cisco Systems 9 Jonathan P. Lang 10 Rincon Networks 12 August 2003 14 Traffic Engineering Link Management Information Base 16 draft-ietf-mpls-telink-mib-03.txt 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance with 21 all provisions of Section 10 of RFC 2026. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that other 25 groups may also distribute working documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it describes managed objects for modeling TE links as 43 described in the Link Bundling in MPLS Traffic Engineering document. 45 Table of Contents 46 1. The Internet-Standard Management Framework . . . . . . . . . . . 2 47 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 48 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3 50 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 51 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4 52 6.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4 54 6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4 55 6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4 56 6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5 57 6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5 58 6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5 59 7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5 60 8. Application of the Interfaces Group to TE Links . . . . . . . . . 9 61 8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9 62 8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11 63 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13 64 10. Intellectual Property Considerations . . . . . . . . . . . . . . 50 65 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51 66 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 51 67 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 68 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 52 69 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53 70 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54 71 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54 73 1. The Internet-Standard Management Framework 75 For a detailed overview of the documents that describe the current 76 Internet-Standard Management Framework, please refer to section 7 of 77 RFC 3410 [RFC3410]. 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. MIB objects are generally 81 accessed through the Simple Network Management Protocol (SNMP). 82 Objects in the MIB are defined using the mechanisms defined in the 83 Structure of Management Information (SMI). This memo specifies a MIB 84 module that is compliant to the SMIv2, which is described in STD 58, 85 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 86 [RFC2580]. 88 2. Introduction 90 OSPF [OSPF], Generalized MPLS (GMPLS) [RFC3471] and the Link Manage- 91 ment Protocol (LMP) [LMP] use the concept of traffic engineering (TE) 92 links to abstract link properties. The effect of this approach is the 93 reduction of the amount of routing information exchanged in the 94 network, which improves routing scalability. In addition, the use of 95 TE link allows the implementation of new capabilities such as link 96 protection. 98 We present in this document a MIB module that can be used to manage 99 TE links and their extension, the bundled link. This MIB module 100 enables both the configuration and the performance monitoring of TE 101 links and bundled link. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119, reference 106 [RFC2119]. 108 3. Terminology 110 This document uses terminology from the documents describing link 111 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 113 The link bundling feature is designed to aggregate one or more simi- 114 lar entities between a node pair into a bundled link [BUNDLING]. In 115 the document, those entities are referred to as TE links. A TE link 116 is a subinterface capable of carrying MPLS traffic engineered traf- 117 fic. A TE Link may be comprised of only one underlying component 118 link. In cases where more than one component links are to be com- 119 bined, multiple component links should be created with differing pri- 120 orities to indicate hot-standby or parallel utilization. 122 A bundled link is just another kind of Traffic Engineering (TE) link 123 (see [GMPLS-OSPF]). A link bundle is a subinterface which bounds the 124 traffic of a group of one or more TE links. There should be more than 125 one TE Link in a link bundle, but this is not a requirement. Fur- 126 thermore, if there are more than one TE link in a link bundle at some 127 time, and at some point later, all but one of the links are deleted, 128 the agent may choose to either delete the link bundle, or it may 129 choose to leave it intact. Traffic counters on a link bundle are 130 cumulative for all subinterfaces which it binds together. 132 4. Feature Checklist 134 The TE Link MIB module (TE-LINK-MIB) is designed to satisfy the fol- 135 lowing requirements and constraints: 137 - The MIB module supports the management of TE links, including 138 bundled links. 140 - Support is provided for configuration of traffic engineering 141 parameters associated with TE links. 143 - The MIB module is used to monitor the priority-based component 144 link and TE link bandwidth values. 146 5. Outline 148 Configuring bundled links involves the following steps: 150 - Creating a bundled link. 152 - Creating TE links. 154 - Optionally specifying the shared risk link groups associated with 155 the TE links. 157 - Configuring the component links including the bandwidth 158 parameters and associating the component links with the 159 appropriate TE link. 161 - Associating the TE links with the appropriate bundled link. 163 6. Brief Description of MIB Objects 165 Sections 6.1-6.4 describe objects pertaining to TE links. The MIB 166 objects were derived from the link bundling document [BUNDLING]. 168 6.1. teLinkTable 170 This table represents the TE links, including bundled links, and 171 their generic traffic engineering parameters. 173 6.2. teLinkDescriptorTable 175 This table represents the TE link interface switching capability 176 descriptors. 178 6.3. teLinkSrlgTable 180 This table represents the shared risk link groups (SRLGs) associated 181 with TE links. 183 6.4. teLinkBandwidthTable 185 This table specifies the priority-based bandwidth traffic engineering 186 parameters associated with TE links. 188 6.5. componentLinkTable 190 This table enumerates the component links and their generic traffic 191 engineering parameters. 193 6.6. componentLinkDescriptorTable 195 This table enumerates the interface switching capability descriptors 196 that each component link supports. 198 6.7. componentLinkBandwidthTable 200 The component link bandwidth table specifies the priority-based band- 201 width values associated with the component links. 203 Component links that belong to the same TE link must be compatible. 204 If these two tables are managed independently, mechanisms should be 205 put in place to ensure consistency between the two tables. TE links 206 that form a bundled link must have compatible traffic engineering 207 parameters (resource class, link metric and protection type). 209 The link descriptors of the teLinkDescriptorTable can be derived from 210 the link descriptors of the componentLinkDescrTable. 212 Some of the bandwidth parameters of the teLinkTable, teLinkDescrip- 213 torTable, teLinkBandwidthTable are derived from the bandwidth parame- 214 ters of the componentLinkTable, componentLinkDescriptorTable and com- 215 ponentLinkBandwidthTable (maximum reservable bandwidth, minimum LSP 216 bandwidth, maximum LSP bandwidth at specified priority and unreserved 217 bandwidth). 219 7. Example of Bundled Link Setup 221 In this section we provide a brief example of using the MIB 222 objects described in section 10 to set up a bundled link. 223 While this example is not meant to illustrate every nuance of the 224 MIB module, it is intended as an aid to understanding some 225 of the key concepts. It is meant to be read after going through the 226 MIB module itself. More details on the use of the ifStackTable 227 to establish relationship between bundled links, TE links and 228 component links are given in Section 8.2. 230 Suppose that one would like to manually create a bundled link 231 out of two 1:1 TE links as depicted on the figure in Section 8.2. 232 Assume that the bundled link is associated with SRLGs 10 and 50. 233 Finally, let the component links be port entity interfaces 234 (lambdas). The following example illustrates which rows and 235 corresponding objects might be created to accomplish this. 237 First, a bundled link entry is created. An ifEntry with the same 238 ifIndex and with ifType teLink needs to be created beforehand. 240 In teLinkTable: 241 { 242 ifIndex = 2, 243 teLinkAddressType = unknown(0), 244 teLinkLocalIpAddr = ''H, 245 teLinkRemoteIpAddr = ''H, 246 teLinkMetric = 5, 247 teLinkProtectionType = dedicated1For1(4), 248 teLinkWorkingPriority = 7, 249 teLinkResourceClass = 3, 250 teLinkIncomingIfId = 0, 251 teLinkOutgoingIfId = 2, 252 teLinkRowStatus = createAndGo(4), 253 teLinkStorageType = nonVolatile(3) 254 } 256 In ifStackTable: 257 { 258 ifStackHigherLayer = 0, 259 ifStackLowerLayer = 2, 260 ifStackStatus = createAndGo(4) 261 } 263 Next, the two TE links are created. 265 In teLinkTable: 266 { 267 ifIndex = 3, 268 teLinkAddressType = unknown(0), 269 teLinkLocalIpAddr = ''H, 270 teLinkRemoteIpAddr = ''H, 271 teLinkMetric = 5, 272 teLinkProtectionType = unprotected(2), 273 teLinkWorkingPriority = 7, 274 teLinkResourceClass = 3, 275 teLinkIncomingIfId = 0, 276 teLinkOutgoingIfId = 3, 277 teLinkRowStatus = createAndGo(4), 278 teLinkStorageType = nonVolatile(3) 279 } 281 In ifStackTable: 282 { 283 ifStackHigherLayer = 2, 284 ifStackLowerLayer = 3, 285 ifStackStatus = createAndGo(4) 286 } 288 In teLinkTable: 289 { 290 ifIndex = 4, 291 teLinkAddressType = unknown(0), 292 teLinkLocalIpAddr = ''H, 293 teLinkRemoteIpAddr = ''H, 294 teLinkMetric = 5, 295 teLinkProtectionType = unprotected(2), 296 teLinkWorkingPriority = 7, 297 teLinkResourceClass = 3, 298 teLinkIncomingIfId = 0, 299 teLinkOutgoingIfId = 4, 300 teLinkRowStatus = createAndGo(4), 301 teLinkStorageType = nonVolatile(3) 302 } 304 In ifStackTable: 305 { 306 ifStackHigherLayer = 2, 307 ifStackLowerLayer = 4, 308 ifStackStatus = createAndGo(4) 309 } 311 We assign SRLGs to the TE links. 313 In the teLinkSrlgTable: 314 { 315 ifIndex = 3, 316 teLinkSrlg = 10, 317 teLinkSrlgRowStatus = createAndGo(4), 318 teLinkSrlgStorageType = nonVolatile(3) 319 } 321 In the teLinkSrlgTable: 322 { 323 ifIndex = 4, 324 teLinkSrlg = 50, 325 teLinkSrlgRowStatus = createAndGo(4), 326 teLinkSrlgStorageType = nonVolatile(3) 327 } 329 The bundled link inherits the SRLG properties from the 330 associated TE links. 332 Next, for each unbundled TE link, a component link is created. 334 An ifEntry with the same ifIndex needs to be created beforehand. 336 In componentLinkTable: 337 { 338 ifIndex = 5, 339 componentLinkPreferredProtection = primary(1), 340 componentLinkRowStatus = createAndGo(4), 341 componentLinkStorageType = nonVolatile(3) 342 } 344 In ifStackTable: 345 { 346 ifStackHigherLayer = 3, 347 ifStackLowerLayer = 5, 348 ifStackStatus = createAndGo(4) 349 } 351 In componentLinkTable: 352 { 353 ifIndex = 6, 354 componentLinkPreferredProtection = secondary(2), 355 componentLinkRowStatus = createAndGo(4) 356 componentLinkStorageType = nonVolatile(3) 357 } 359 In ifStackTable: 360 { 361 ifStackHigherLayer = 4, 362 ifStackLowerLayer = 6, 363 ifStackStatus = createAndGo(4) 364 } 366 In this example, once a component link is added to the 367 componentLinkTable, the associated link descriptors are 368 implicitly added to the componentLinkDescriptorTable. 370 TE link link descriptors are derived from their component link 371 descriptors. 373 Note that the bandwidth attributes in teLinkDescriptorTable, 374 componentLinkDescriptorTable, teLinkBandwidthTable 375 and componentLinkBandwidthTable are maintained by the 376 device according to LSP creation/deletion at different priorities. 377 The values in the teLinkBandwidthTable are an aggregation 378 of the values for the component links of the TE links and 379 the TE links of the bundled link. 381 8. Application of the Interfaces Group to TE Links 383 The Interfaces Group [RFC2863] defines generic managed objects for 384 managing interfaces. This memo contains the media-specific 385 extensions to the Interfaces Group for managing TE Link interfaces 386 as logical interfaces. 388 This memo assumes the interpretation of the Interfaces Group to be 389 in accordance with [RFC2863] which states that the interfaces table 390 (ifTable) contains information on the managed resource's 391 interfaces and that each sub-layer below the internetwork layer of 392 a network interface is considered an interface. Thus, the TE Link 393 interface is represented as an entry in the ifTable. The inter- 394 relation of entries in the ifTable is defined by Interfaces Stack 395 Group defined in [RFC2863]. 397 When using TE Link interfaces, the interface stack table might appear 398 as follows: 400 +----------------------------------------+ 401 | TE link-interface ifType = teLink(200) + 402 +----------------------------------------+ 403 | Underlying Layer... + 404 +----------------------------------------+ 406 In the above diagram, "Underlying Layer..." refers to the ifIndex 407 of any interface type, which has been defined for TE Link 408 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 410 8.1. Support of the TE Link Layer by ifTable 412 Some specific interpretations of ifTable for the TE Link layer 413 follow. 415 Object Use for the TE Link layer 417 ifIndex Each TE Link interface is represented by an ifEntry. 419 ifDescr Description of the TE Link interface. 421 ifType The value that is allocated for TE Link is 200 422 [IANAifType]. 424 ifSpeed The total bandwidth in bits per second for use by 425 the TE Link layer. 427 ifPhysAddress Unused. 429 ifAdminStatus This variable indicates the administrator's intent 430 as to whether TE Link should be enabled, disabled, or 431 running in some diagnostic testing mode on this 432 interface. Also see [RFC2863]. 434 ifOperStatus This value reflects the actual or operational 435 status of TE Link on this interface. 437 ifLastChange See [RFC2863]. 439 ifInOctets The number of received octets over the interface, 440 i.e., the number of received octets in all component 441 links associated with the interface. 443 ifOutOctets The number of transmitted octets over the 444 interface, i.e., the number of octets transmitted 445 over all component links associated with the 446 interface. 448 ifInErrors The number of packets dropped due to 449 uncorrectable errors. 451 ifInUnknownProtos 452 The number of received packets discarded during 453 packet header validation. 455 ifOutErrors See [RFC2863]. 457 ifName Textual name (unique on this system) of the 458 interface or an octet string of zero length. 460 ifLinkUpDownTrapEnable 461 Default is disabled (2). 463 ifConnectorPresent 464 Set to false (2). 466 ifHighSpeed See [RFC2863]. 468 ifHCInOctets The 64-bit version of ifInOctets; supported if 469 required by the compliance statements in [RFC2863]. 471 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 472 required by the compliance statements in [RFC2863]. 474 ifAlias The non-volatile 'alias' name for the interface as 475 specified by a network manager. 477 ifCounterDiscontinuityTime 478 See [RFC2863]. 480 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 481 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 482 if encoding type is clear. For other encoding types, traffic 483 counters on a TE link are cumulative for all subinterfaces which it 484 binds together. 486 8.2. Using ifStackTable 488 This section describes by example how to use ifStackTable to 489 represent the relationship of TE links with underlying TE-enabled 490 interfaces. Implementors of the stack table for TE link interfaces 491 should look at the appropriate RFC for the service being stacked 492 on TE links. Examples given below are for illustration purposes 493 only. 495 Example: MPLS is being carried on a bundled TE links. 496 The bundled TE link represents a 1:1 optical 497 transport interface. 499 In this example, the component link is a TE link. The two component 500 links/TE links are grouped in a bundled link. 502 +-------------------------------------------------------------------+ 503 | MPLS interface ifType = mpls(166) | 504 | ifIndex = 1 | 505 +-------------------------------------------------------------------+ 506 | TE link (bundled link) ifType = teLink(200) | 507 | ifIndex = 2 | 508 +--------------------------------+-+--------------------------------+ 509 | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | 510 | ifIndex = 3 | | ifIndex = 4 | 511 +--------------------------------+ +--------------------------------+ 512 | Component link | | Component link | 513 | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | 514 | ifIndex = 5 | | ifIndex = 6 | 515 +--------------------------------+ +--------------------------------+ 517 The assignment of the index values could for example be: 519 ifIndex Description 520 1 mpls (type 166) 521 2 teLink (type 200) 522 3 teLink (type 200) 523 4 teLink (type 200) 524 5 opticalTransport (type 196) 525 6 opticalTransport (type 196) 527 The ifStackTable is then used to show the relationships between the 528 various interfaces. 530 ifStackTable Entries 532 HigherLayer LowerLayer 533 0 1 534 1 2 535 2 3 536 2 4 537 3 5 538 4 6 539 5 0 540 6 0 542 In the case where MPLS is using a single TE link, then 543 the upper TE link layer (link bundle) is not required. 545 +-----------------------------------+ 546 | MPLS interface ifType = mpls(166) | 547 +-----------------------------------+ 548 | TE link ifType = teLink(200) | 549 +-----------------------------------+ 550 | Component link | 551 | ifType = opticalTransport(196) | 552 +-----------------------------------+ 554 The assignment of the index values could for example be: 556 ifIndex Description 557 1 mpls (type 166) 558 2 teLink (type 200) 559 3 opticalTransport (type 196) 561 The ifStackTable is then used to show the relationships between the 562 various interfaces. 564 ifStackTable Entries 566 HigherLayer LowerLayer 567 0 1 568 1 2 569 2 3 570 3 0 572 9. TE Link MIB Module Definitions 574 TE-LINK-STD-MIB DEFINITIONS ::= BEGIN 576 IMPORTS 577 MODULE-IDENTITY, OBJECT-TYPE, transmission, Unsigned32 578 FROM SNMPv2-SMI 580 MODULE-COMPLIANCE, OBJECT-GROUP 581 FROM SNMPv2-CONF 583 TEXTUAL-CONVENTION, RowStatus, StorageType 584 FROM SNMPv2-TC 586 InterfaceIndexOrZero, ifIndex 587 FROM IF-MIB 589 InetAddressType, InetAddress 590 FROM INET-ADDRESS-MIB; 592 teLinkStdMIB MODULE-IDENTITY 593 LAST-UPDATED "200308261200Z" -- 26 August 2003 12:00:00 EST 594 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 595 CONTACT-INFO 596 " Martin Dubuc 597 Email: dubuc.consulting@rogers.com 599 Sudheer Dharanikota 600 Email: sudheer@ieee.org 602 Thomas D. Nadeau 603 Email: tnadeau@cisco.com 605 Jonathan P. Lang 606 Email: jplang@ieee.org 608 Comments about this document should be emailed directly to 609 the MPLS working group mailing list at mpls@uu.net." 611 DESCRIPTION 612 "Copyright (C) 2003 The Internet Society. This version of 613 this MIB module is part of RFC XXXX; see the RFC 614 itself for full legal notices. 616 This MIB module contains managed object definitions for 617 MPLS traffic engineering links as defined in 618 'Link Bundling in MPLS Traffic Engineering'." 620 -- Revision history. 621 REVISION 622 "200308261200Z" -- 26 August 2003 12:00:00 EST 623 DESCRIPTION 624 "Initial version published as RFC xxxx (to be assigned by RFC 625 Editor)" 626 ::= { transmission xxx } -- To be assigned by IANA. 627 -- Request to assign 200 which is 628 -- ifType value for teLink. 630 -- Textual Conventions 632 TeLinkPriority ::= TEXTUAL-CONVENTION 633 DISPLAY-HINT "d" 634 STATUS current 635 DESCRIPTION 636 "This type is used to represent a priority. Each connection is 637 assigned a priority. This priority is used when accounting for 638 bandwidth on TE links or component links, for resource 639 allocation and for rerouting purposes. Value 0 is the highest 640 priority. Value 7 is the lowest priority." 641 SYNTAX Unsigned32 (0..7) 643 TeLinkProtection ::= TEXTUAL-CONVENTION 644 STATUS current 645 DESCRIPTION 646 "Link protection." 647 SYNTAX INTEGER { 648 primary(1), 649 secondary(2) 650 } 652 TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION 653 STATUS current 654 DESCRIPTION 655 "Switching capability as specified in the 'OSPF Extensions in 656 Support of Generalized MPLS' document. The values specified in 657 this document are not contiguous." 658 SYNTAX INTEGER { 659 packetSwitch1(1), 660 packetSwitch2(2), 661 packetSwitch3(3), 662 packetSwitch4(4), 663 layer2Switch(51), 664 tdm(100), 665 lambdaSwitch(150), 666 fiberSwitch(200) 668 } 670 TeLinkEncodingType ::= TEXTUAL-CONVENTION 671 STATUS current 672 DESCRIPTION 673 "Link encoding type as specified in 'GMPLS Signaling Functional 674 Description' document. The values specified in this document are 675 not contiguous." 676 SYNTAX INTEGER { 677 packet(1), 678 ethernet(2), 679 ansiEtsiPdh(3), 680 sdhItuSonetAnsi(5), 681 digitalWrapper(7), 682 lambda(8), 683 fiber(9), 684 fiberChannel(11) 685 } 687 TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION 688 STATUS current 689 DESCRIPTION 690 "SONET/SDH indication type." 691 SYNTAX INTEGER { 692 standard(0), 693 arbitrary(1) 694 } 696 -- Top level components of this MIB module 698 -- Notifications 699 teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } 700 -- Tables, Scalars 701 teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 } 702 -- Conformance 703 teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 } 705 -- TE Link Table 707 teLinkTable OBJECT-TYPE 708 SYNTAX SEQUENCE OF TeLinkEntry 709 MAX-ACCESS not-accessible 710 STATUS current 711 DESCRIPTION 712 "This table specifies the grouping of component links into 713 TE links and grouping of TE links into bundled links." 714 ::= { teLinkObjects 1 } 716 teLinkEntry OBJECT-TYPE 717 SYNTAX TeLinkEntry 718 MAX-ACCESS not-accessible 719 STATUS current 720 DESCRIPTION 721 "An entry in this table exists for each ifEntry with an 722 ifType of teLink(200), i.e. for every TE link. An ifEntry 723 in the ifTable must exist before a teLinkEntry is created with 724 the corresponding ifIndex. If a TE link entry in the ifTable is 725 destroyed, then so is the corresponding entry in the 726 teLinkTable. The administrative and operational status values 727 are controlled from the ifEntry." 728 INDEX { ifIndex } 729 ::= { teLinkTable 1 } 731 TeLinkEntry ::= SEQUENCE { 732 teLinkAddressType InetAddressType, 733 teLinkLocalIpAddr InetAddress, 734 teLinkRemoteIpAddr InetAddress, 735 teLinkMetric Unsigned32, 736 teLinkMaximumReservableBandwidth Unsigned32, 737 teLinkProtectionType INTEGER, 738 teLinkWorkingPriority TeLinkPriority, 739 teLinkResourceClass Unsigned32, 740 teLinkIncomingIfId InterfaceIndexOrZero, 741 teLinkOutgoingIfId InterfaceIndexOrZero, 742 teLinkRowStatus RowStatus, 743 teLinkStorageType StorageType 744 } 746 teLinkAddressType OBJECT-TYPE 747 SYNTAX InetAddressType 748 MAX-ACCESS read-create 749 STATUS current 750 DESCRIPTION 751 "The type of Internet address for the TE link." 752 ::= { teLinkEntry 1 } 754 teLinkLocalIpAddr OBJECT-TYPE 755 SYNTAX InetAddress 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "The local Internet address for numbered links. The type of this 760 address is determined by the value of the teLinkAddressType 761 object. 763 For IPv4 and IPv6 numbered links, this object represents the 764 local IP address associated with the TE link. For an 765 unnumbered link, the local address is of type unknown and this 766 object is set to the zero length string and the 767 teLinkOutgoingIfId object then identifies the unnumbered 768 address. 770 If the TE link is a Forwarding Adjacency (FA), the local 771 IP address is set to the head-end address of the FA-LSP." 772 ::= { teLinkEntry 2 } 774 teLinkRemoteIpAddr OBJECT-TYPE 775 SYNTAX InetAddress 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "The remote Internet address for numbered links. The type of 780 this address is determined by the value of the 781 teLinkAddressType object. 783 The remote IP address associated with the TE link (IPv4 and 784 IPv6 numbered links). For an unnumbered link, the remote 785 address is of type unknown and this object is set to the 786 zero length string and the teLinkIncomingIfId object then 787 identifies the unnumbered address. 789 If the TE link is a Forwarding Adjacency, the remote IP 790 address is set to the tail-end address of the FA-LSP." 791 ::= { teLinkEntry 3 } 793 teLinkMetric OBJECT-TYPE 794 SYNTAX Unsigned32 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "The traffic engineering metric for the TE link is 799 derived from its component links. All component links 800 within the TE link must have the same traffic 801 engineering metric." 802 REFERENCE 803 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 804 -- RFC Editor to fill in RFC number that will be assigned to 805 -- [BUNDLING] 806 ::= { teLinkEntry 4 } 808 teLinkMaximumReservableBandwidth OBJECT-TYPE 809 SYNTAX Unsigned32 810 UNITS "thousand bps" 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "This attribute specifies the maximum reservable bandwidth on 815 the TE link. This is the union of the maximum reservable 816 bandwidth of all the component links within the 817 TE link that can be used to carry live traffic. This value 818 is an estimate in units of 1,000 bits per second." 819 REFERENCE 820 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 821 -- RFC Editor to fill in RFC number that will be assigned to 822 -- [GMPLS-OSPF] 823 ::= { teLinkEntry 5 } 825 teLinkProtectionType OBJECT-TYPE 826 SYNTAX INTEGER { 827 extraTraffic(1), 828 unprotected(2), 829 shared(3), 830 dedicated1For1(4), 831 dedicated1Plus1(5), 832 enhanced(6) 833 } 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "This attribute specifies link protection type of the 838 TE link. Description of the different protection types can be 839 found in the 'Routing Extensions in Support of Generalized 840 MPLS' document." 841 REFERENCE 842 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 843 Routing Extensions in Support of Generalized MPLS, RFC xxxx" 844 -- RFC Editor to fill in RFC number that will be assigned to 845 -- [GMPLS-OSPF] and [ROUTING] 846 ::= { teLinkEntry 6 } 848 teLinkWorkingPriority OBJECT-TYPE 849 SYNTAX TeLinkPriority 850 MAX-ACCESS read-create 851 STATUS current 852 DESCRIPTION 853 "This object represents a priority value such that a new 854 connection with a higher priority, i.e. numerically lower than 855 this value, is guaranteed to be setup on a primary link and 856 not on a secondary link." 857 REFERENCE 858 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 859 -- RFC Editor to fill in RFC number that will be assigned to 860 -- [GMPLS-OSPF] 861 ::= { teLinkEntry 7 } 863 teLinkResourceClass OBJECT-TYPE 864 SYNTAX Unsigned32 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "This attribute specifies the TE link resource class. 869 The resource class is a 32 bit bitfield. The resource class for 870 a link bundle is derived from the resource class of its 871 TE links. All TE links within a link bundle must have the 872 same resource class. Encoding of the resource class is described 873 in the 'Traffic Engineering Extensions to OSPF Version 2' 874 document." 875 REFERENCE 876 "Link Bundling in MPLS Traffic Engineering, RFC xxxx and 877 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 878 -- RFC Editor to fill in RFC number that will be assigned to 879 -- [BUNDLING] and [OSPF] 880 ::= { teLinkEntry 8 } 882 teLinkIncomingIfId OBJECT-TYPE 883 SYNTAX InterfaceIndexOrZero 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "For unnumbered links, the incoming interface is set to the 888 outgoing interface identifier chosen by the neighboring LSR 889 for the reverse link corresponding to this TE link. For 890 numbered links, the address is stored in the teLinkRemoteIpAddr 891 instead." 892 REFERENCE 893 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 894 -- RFC Editor to fill in RFC number that will be assigned to 895 -- [BUNDLING] 896 ::= { teLinkEntry 9 } 898 teLinkOutgoingIfId OBJECT-TYPE 899 SYNTAX InterfaceIndexOrZero 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "If the link is unnumbered, the outgoing interface identifier is 904 set to the outgoing interface identifier chosen for the TE link 905 by the advertising LSR. For numbered links, the address is 906 stored in the teLinkLocalIpAddr instead." 907 REFERENCE 908 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 909 -- RFC Editor to fill in RFC number that will be assigned to 910 -- [BUNDLING] 911 ::= { teLinkEntry 10 } 913 teLinkRowStatus OBJECT-TYPE 914 SYNTAX RowStatus 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "This variable is used to create, modify, and/or 919 delete a row in this table. None of the writable objects in 920 a row can be changed if status is active(1)." 921 ::= { teLinkEntry 11 } 923 teLinkStorageType OBJECT-TYPE 924 SYNTAX StorageType 925 MAX-ACCESS read-create 926 STATUS current 927 DESCRIPTION 928 "The storage type for this conceptual row in the 929 teLinkTable. Conceptual rows having the value 930 'permanent' need not allow write-access to any 931 columnar object in the row." 932 ::= { teLinkEntry 12 } 934 -- End of teLinkTable 936 -- TE Link Descriptor Table 938 teLinkDescriptorTable OBJECT-TYPE 939 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "This table specifies the interface switching capability 944 descriptors associated with the TE links." 945 ::= { teLinkObjects 2 } 947 teLinkDescriptorEntry OBJECT-TYPE 948 SYNTAX TeLinkDescriptorEntry 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "An entry in this table is created for every TE link interface 953 switching capability descriptor. An ifEntry in the ifTable 954 must exist before a teLinkDescriptorEntry using the same 955 ifIndex is created. ifType of ifEntry must be teLink(200). 956 If a TE link entry in the ifTable is destroyed, then so are all 957 entries in the teLinkDescriptorTable that use the ifIndex of 958 this TE link." 959 INDEX { ifIndex, teLinkDescriptorId } 960 ::= { teLinkDescriptorTable 1 } 962 TeLinkDescriptorEntry ::= SEQUENCE { 963 teLinkDescriptorId Unsigned32, 964 teLinkDescrSwitchingCapability TeLinkSwitchingCapability, 965 teLinkDescrEncodingType TeLinkEncodingType, 966 teLinkDescrMinLspBandwidth Unsigned32, 967 teLinkDescrMaxLspBandwidthPrio0 Unsigned32, 968 teLinkDescrMaxLspBandwidthPrio1 Unsigned32, 969 teLinkDescrMaxLspBandwidthPrio2 Unsigned32, 970 teLinkDescrMaxLspBandwidthPrio3 Unsigned32, 971 teLinkDescrMaxLspBandwidthPrio4 Unsigned32, 972 teLinkDescrMaxLspBandwidthPrio5 Unsigned32, 973 teLinkDescrMaxLspBandwidthPrio6 Unsigned32, 974 teLinkDescrMaxLspBandwidthPrio7 Unsigned32, 975 teLinkDescrInterfaceMtu Unsigned32, 976 teLinkDescrIndication TeLinkSonetSdhIndication, 977 teLinkDescrRowStatus RowStatus, 978 teLinkDescrStorageType StorageType 979 } 981 teLinkDescriptorId OBJECT-TYPE 982 SYNTAX Unsigned32 (1..4294967295) 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "This object specifies the link descriptor identifier." 987 ::= { teLinkDescriptorEntry 1 } 989 teLinkDescrSwitchingCapability OBJECT-TYPE 990 SYNTAX TeLinkSwitchingCapability 991 MAX-ACCESS read-create 992 STATUS current 993 DESCRIPTION 994 "This attribute specifies interface switching capability of the 995 TE link, which is derived from its component links." 996 REFERENCE 997 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 998 -- RFC Editor to fill in RFC number that will be assigned to 999 -- [GMPLS-OSPF] 1000 ::= { teLinkDescriptorEntry 2 } 1002 teLinkDescrEncodingType OBJECT-TYPE 1003 SYNTAX TeLinkEncodingType 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "This attribute specifies the TE link encoding type." 1008 REFERENCE 1009 "Generalized MPLS Signaling Functional Description, RFC 3471" 1010 ::= { teLinkDescriptorEntry 3 } 1012 teLinkDescrMinLspBandwidth OBJECT-TYPE 1013 SYNTAX Unsigned32 1014 UNITS "thousand bps" 1015 MAX-ACCESS read-create 1016 STATUS current 1017 DESCRIPTION 1018 "This attribute specifies the minimum LSP bandwidth on 1019 the TE link. This is derived from the union of the 1020 minimum LSP bandwidth of all the component links 1021 associated with the TE link that can be used to carry 1022 live traffic. This value is an estimate in units of 1,000 bits 1023 per second." 1024 REFERENCE 1025 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1026 -- RFC Editor to fill in RFC number that will be assigned to 1027 -- [GMPLS-OSPF] 1028 ::= { teLinkDescriptorEntry 4 } 1030 teLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1031 SYNTAX Unsigned32 1032 UNITS "thousand bps" 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "This attribute specifies the maximum LSP bandwidth at 1037 priority 0 on the TE link. This is the union of the maximum 1038 LSP bandwidth at priority 0 of all the component links within 1039 the TE link that can be used to carry live traffic. This 1040 value is an estimate in units of 1,000 bits per second." 1041 REFERENCE 1042 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1043 -- RFC Editor to fill in RFC number that will be assigned to 1044 -- [GMPLS-OSPF] 1045 ::= { teLinkDescriptorEntry 5 } 1047 teLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1048 SYNTAX Unsigned32 1049 UNITS "thousand bps" 1050 MAX-ACCESS read-create 1051 STATUS current 1052 DESCRIPTION 1053 "This attribute specifies the maximum LSP bandwidth at 1054 priority 1 on the TE link. This is the union of the maximum 1055 LSP bandwidth at priority 1 of all the component links within 1056 the TE link that can be used to carry live traffic. This 1057 value is an estimate in units of 1,000 bits per second." 1058 REFERENCE 1059 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1060 -- RFC Editor to fill in RFC number that will be assigned to 1061 -- [GMPLS-OSPF] 1062 ::= { teLinkDescriptorEntry 6 } 1064 teLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1065 SYNTAX Unsigned32 1066 UNITS "thousand bps" 1067 MAX-ACCESS read-create 1068 STATUS current 1069 DESCRIPTION 1070 "This attribute specifies the maximum LSP bandwidth at 1071 priority 2 on the TE link. This is the union of the maximum 1072 LSP bandwidth at priority 2 of all the component links within 1073 the TE link that can be used to carry live traffic. This 1074 value is an estimate in units of 1,000 bits per second." 1075 REFERENCE 1076 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1077 -- RFC Editor to fill in RFC number that will be assigned to 1078 -- [GMPLS-OSPF] 1079 ::= { teLinkDescriptorEntry 7 } 1081 teLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1082 SYNTAX Unsigned32 1083 UNITS "thousand bps" 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION 1087 "This attribute specifies the maximum LSP bandwidth at 1088 priority 3 on the TE link. This is the union of the maximum 1089 LSP bandwidth at priority 3 of all the component links within 1090 the TE link that can be used to carry live traffic. This 1091 value is an estimate in units of 1,000 bits per second." 1092 REFERENCE 1093 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1094 -- RFC Editor to fill in RFC number that will be assigned to 1095 -- [GMPLS-OSPF] 1096 ::= { teLinkDescriptorEntry 8 } 1098 teLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1099 SYNTAX Unsigned32 1100 UNITS "thousand bps" 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "This attribute specifies the maximum LSP bandwidth at 1105 priority 4 on the TE link. This is the union of the maximum 1106 LSP bandwidth at priority 4 of all the component links within 1107 the TE link that can be used to carry live traffic. This 1108 value is an estimate in units of 1,000 bits per second." 1109 REFERENCE 1110 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1111 -- RFC Editor to fill in RFC number that will be assigned to 1112 -- [GMPLS-OSPF] 1113 ::= { teLinkDescriptorEntry 9 } 1115 teLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1116 SYNTAX Unsigned32 1117 UNITS "thousand bps" 1118 MAX-ACCESS read-create 1119 STATUS current 1120 DESCRIPTION 1121 "This attribute specifies the maximum LSP bandwidth at 1122 priority 5 on the TE link. This is the union of the maximum 1123 LSP bandwidth at priority 5 of all the component links within 1124 the TE link that can be used to carry live traffic. This 1125 value is an estimate in units of 1,000 bits per second." 1126 REFERENCE 1127 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1128 -- RFC Editor to fill in RFC number that will be assigned to 1129 -- [GMPLS-OSPF] 1130 ::= { teLinkDescriptorEntry 10 } 1132 teLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1133 SYNTAX Unsigned32 1134 UNITS "thousand bps" 1135 MAX-ACCESS read-create 1136 STATUS current 1137 DESCRIPTION 1138 "This attribute specifies the maximum LSP bandwidth at 1139 priority 6 on the TE link. This is the union of the maximum 1140 LSP bandwidth at priority 6 of all the component links within 1141 the TE link that can be used to carry live traffic. This 1142 value is an estimate in units of 1,000 bits per second." 1143 REFERENCE 1144 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1145 -- RFC Editor to fill in RFC number that will be assigned to 1146 -- [GMPLS-OSPF] 1148 ::= { teLinkDescriptorEntry 11 } 1150 teLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1151 SYNTAX Unsigned32 1152 UNITS "thousand bps" 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "This attribute specifies the maximum LSP bandwidth at 1157 priority 7 on the TE link. This is the union of the maximum 1158 LSP bandwidth at priority 7 of all the component links within 1159 the TE link that can be used to carry live traffic. This 1160 value is an estimate in units of 1,000 bits per second." 1161 REFERENCE 1162 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1163 -- RFC Editor to fill in RFC number that will be assigned to 1164 -- [GMPLS-OSPF] 1165 ::= { teLinkDescriptorEntry 12 } 1167 teLinkDescrInterfaceMtu OBJECT-TYPE 1168 SYNTAX Unsigned32 (1..65535) 1169 MAX-ACCESS read-create 1170 STATUS current 1171 DESCRIPTION 1172 "This attribute specifies the interface MTU for the TE 1173 link descriptor." 1174 REFERENCE 1175 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1176 -- RFC Editor to fill in RFC number that will be assigned to 1177 -- [GMPLS-OSPF] 1178 ::= { teLinkDescriptorEntry 13 } 1180 teLinkDescrIndication OBJECT-TYPE 1181 SYNTAX TeLinkSonetSdhIndication 1182 MAX-ACCESS read-create 1183 STATUS current 1184 DESCRIPTION 1185 "This attribute specifies whether this interface supports 1186 Standard or Arbitrary SONET/SDH." 1187 REFERENCE 1188 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1189 -- RFC Editor to fill in RFC number that will be assigned to 1190 -- [GMPLS-OSPF] 1191 ::= { teLinkDescriptorEntry 14 } 1193 teLinkDescrRowStatus OBJECT-TYPE 1194 SYNTAX RowStatus 1195 MAX-ACCESS read-create 1196 STATUS current 1197 DESCRIPTION 1198 "This variable is used to create, modify, and/or 1199 delete a row in this table. No read-create object 1200 can changed if teLinkDescrRowStatus is in active(1) state." 1201 ::= { teLinkDescriptorEntry 15 } 1203 teLinkDescrStorageType OBJECT-TYPE 1204 SYNTAX StorageType 1205 MAX-ACCESS read-create 1206 STATUS current 1207 DESCRIPTION 1208 "The storage type for this conceptual row in the 1209 teLinkDescriptorTable. Conceptual rows having the value 1210 'permanent' need not allow write-access to any 1211 columnar object in the row." 1212 ::= { teLinkDescriptorEntry 16 } 1214 -- End of teLinkDescriptorTable 1216 -- TE Link Shared Risk Link Group Table 1218 teLinkSrlgTable OBJECT-TYPE 1219 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "This table specifies the SRLGs associated with TE links." 1224 ::= { teLinkObjects 3 } 1226 teLinkSrlgEntry OBJECT-TYPE 1227 SYNTAX TeLinkSrlgEntry 1228 MAX-ACCESS not-accessible 1229 STATUS current 1230 DESCRIPTION 1231 "An entry in this table contains information about a 1232 SRLG associated with a TE link. 1233 An ifEntry in the ifTable must exist before a 1234 teLinkSrlgEntry using the same ifIndex is created. 1235 ifType of ifEntry must be teLink(200). 1236 If a TE link entry in the ifTable is destroyed, then so are all 1237 entries in the teLinkSrlgTable that use the ifIndex of 1238 this TE link." 1239 INDEX { ifIndex, teLinkSrlg } 1240 ::= { teLinkSrlgTable 1 } 1242 TeLinkSrlgEntry ::= SEQUENCE { 1243 teLinkSrlg Unsigned32, 1244 teLinkSrlgRowStatus RowStatus, 1245 teLinkSrlgStorageType StorageType 1246 } 1248 teLinkSrlg OBJECT-TYPE 1249 SYNTAX Unsigned32 (0..4294967295) 1250 MAX-ACCESS not-accessible 1251 STATUS current 1252 DESCRIPTION 1253 "This identifies a SRLG supported by the TE link. An SRLG is 1254 identified with a 32 bit number that is unique within an IGP 1255 domain. Zero is a valid SRLG number." 1256 REFERENCE 1257 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1258 -- RFC Editor to fill in RFC number that will be assigned to 1259 -- [GMPLS-OSPF] 1260 ::= { teLinkSrlgEntry 1 } 1262 teLinkSrlgRowStatus OBJECT-TYPE 1263 SYNTAX RowStatus 1264 MAX-ACCESS read-create 1265 STATUS current 1266 DESCRIPTION 1267 "This variable is used to create, modify, and/or 1268 delete a row in this table. No read-create object can 1269 be modified if teLinkSrlgRowStatus is active(1)." 1270 ::= { teLinkSrlgEntry 2 } 1272 teLinkSrlgStorageType OBJECT-TYPE 1273 SYNTAX StorageType 1274 MAX-ACCESS read-create 1275 STATUS current 1276 DESCRIPTION 1277 "The storage type for this conceptual row in the 1278 teLinkSrlgTable. Conceptual rows having the value 1279 'permanent' need not allow write-access to any 1280 columnar object in the row." 1281 ::= { teLinkSrlgEntry 3 } 1283 -- End of teLinkSrlgTable 1285 -- TE Link Bandwidth Table 1287 teLinkBandwidthTable OBJECT-TYPE 1288 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1289 MAX-ACCESS not-accessible 1290 STATUS current 1291 DESCRIPTION 1292 "This table specifies the priority-based bandwidth table 1293 for TE links." 1294 ::= { teLinkObjects 4 } 1296 teLinkBandwidthEntry OBJECT-TYPE 1297 SYNTAX TeLinkBandwidthEntry 1298 MAX-ACCESS not-accessible 1299 STATUS current 1300 DESCRIPTION 1301 "An entry in this table contains information about 1302 the priority-based bandwidth of TE links. An ifEntry in the 1303 ifTable must exist before a teLinkBandwidthEntry using the 1304 same ifIndex is created. ifType of ifEntry must be teLink(200). 1305 If a TE link entry in the ifTable is destroyed, then so are 1306 all entries in the teLinkBandwidthTable that use the ifIndex of 1307 this TE link." 1308 INDEX { ifIndex, teLinkBandwidthPriority } 1309 ::= { teLinkBandwidthTable 1 } 1311 TeLinkBandwidthEntry ::= SEQUENCE { 1312 teLinkBandwidthPriority TeLinkPriority, 1313 teLinkBandwidthUnreserved Unsigned32, 1314 teLinkBandwidthRowStatus RowStatus, 1315 teLinkBandwidthStorageType StorageType 1316 } 1318 teLinkBandwidthPriority OBJECT-TYPE 1319 SYNTAX TeLinkPriority 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1323 "This attribute specifies the priority. A value of 0 is valid 1324 as specified in the 'Traffic Engineering Extensions to OSPF 1325 Version 2' document." 1326 REFERENCE 1327 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1328 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1329 -- RFC Editor to fill in RFC number that will be assigned to 1330 -- [GMPLS-OSPF] and [OSPF] 1331 ::= { teLinkBandwidthEntry 1 } 1333 teLinkBandwidthUnreserved OBJECT-TYPE 1334 SYNTAX Unsigned32 1335 UNITS "thousand bps" 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "This attribute specifies the TE link unreserved 1340 bandwidth at priority p. It is the sum of the unreserved 1341 bandwidths at priority p of all component links associated 1342 with the TE link (excludes all links that are strictly 1343 used as protecting links). This value is an estimate in units 1344 of 1,000 bits per second." 1345 REFERENCE 1346 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 1347 -- RFC Editor to fill in RFC number that will be assigned to 1348 -- [BUNDLING] 1349 ::= { teLinkBandwidthEntry 2 } 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. No read-create object 1358 can be modified when teLinkBandwidthRowStatus is active(1)." 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 ::= { teLinkObjects 5 } 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. ifEntry's ifType can be 1393 of any interface type which has been defined for TE Link 1394 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 1395 If an entry representing a component link is destroyed in the 1396 ifTable, then so is the corresponding entry in the 1397 componentLinkTable. The administrative and operational status 1398 values are controlled from the ifEntry." 1399 INDEX { ifIndex } 1400 ::= { componentLinkTable 1 } 1402 ComponentLinkEntry ::= SEQUENCE { 1403 componentLinkMaxResBandwidth Unsigned32, 1404 componentLinkPreferredProtection TeLinkProtection, 1405 componentLinkCurrentProtection TeLinkProtection, 1406 componentLinkRowStatus RowStatus, 1407 componentLinkStorageType StorageType 1408 } 1410 componentLinkMaxResBandwidth OBJECT-TYPE 1411 SYNTAX Unsigned32 1412 UNITS "thousand bps" 1413 MAX-ACCESS read-create 1414 STATUS current 1415 DESCRIPTION 1416 "This attribute specifies the maximum reservable bandwidth on 1417 the component link. This value is an estimate in units of 1418 1,000 bits per second." 1419 REFERENCE 1420 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1421 -- RFC Editor to fill in RFC number that will be assigned to 1422 -- [GMPLS-OSPF] 1423 ::= { componentLinkEntry 1 } 1425 componentLinkPreferredProtection OBJECT-TYPE 1426 SYNTAX TeLinkProtection 1427 MAX-ACCESS read-create 1428 STATUS current 1429 DESCRIPTION 1430 "This attribute specifies whether this component link is 1431 a primary or secondary entity." 1432 ::= { componentLinkEntry 2 } 1434 componentLinkCurrentProtection OBJECT-TYPE 1435 SYNTAX TeLinkProtection 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "This attribute specifies whether this component link is 1440 currently used as primary or secondary link." 1441 ::= { componentLinkEntry 3 } 1443 componentLinkRowStatus OBJECT-TYPE 1444 SYNTAX RowStatus 1445 MAX-ACCESS read-create 1446 STATUS current 1447 DESCRIPTION 1448 "This variable is used to create, modify, and/or 1449 delete a row in this table. No read-create object 1450 can be modified when componentLinkRowStatus is active(1)." 1451 ::= { componentLinkEntry 4 } 1453 componentLinkStorageType OBJECT-TYPE 1454 SYNTAX StorageType 1455 MAX-ACCESS read-create 1456 STATUS current 1457 DESCRIPTION 1458 "The storage type for this conceptual row in the 1459 componentLinkTable. Conceptual rows having the value 1460 'permanent' need not allow write-access to any 1461 columnar object in the row." 1462 ::= { componentLinkEntry 5 } 1464 -- End of componentLinkTable 1466 -- Component Link Descriptor Table 1468 componentLinkDescriptorTable OBJECT-TYPE 1469 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION 1473 "This table specifies the interface switching capability 1474 descriptors associated with the component links." 1475 ::= { teLinkObjects 6 } 1477 componentLinkDescriptorEntry OBJECT-TYPE 1478 SYNTAX ComponentLinkDescriptorEntry 1479 MAX-ACCESS not-accessible 1480 STATUS current 1481 DESCRIPTION 1482 "An entry in this table is created for every component link 1483 descriptor. An ifEntry in the ifTable must exist before a 1484 componentLinkDescriptorEntry using the same ifIndex is created. 1485 ifEntry's ifType can be of any interface type which has been 1486 defined for TE Link interworking. Examples include ATM, Frame 1487 Relay, Ethernet, etc. If a component link entry in the ifTable 1488 is destroyed, then so are all entries in the 1489 componentLinkDescriptorTable that use the ifIndex of this 1490 component link." 1491 INDEX { ifIndex, componentLinkDescrId } 1492 ::= { componentLinkDescriptorTable 1 } 1494 ComponentLinkDescriptorEntry ::= SEQUENCE { 1495 componentLinkDescrId Unsigned32, 1496 componentLinkDescrSwitchingCapability TeLinkSwitchingCapability, 1497 componentLinkDescrEncodingType TeLinkEncodingType, 1498 componentLinkDescrMinLspBandwidth Unsigned32, 1499 componentLinkDescrMaxLspBandwidthPrio0 Unsigned32, 1500 componentLinkDescrMaxLspBandwidthPrio1 Unsigned32, 1501 componentLinkDescrMaxLspBandwidthPrio2 Unsigned32, 1502 componentLinkDescrMaxLspBandwidthPrio3 Unsigned32, 1503 componentLinkDescrMaxLspBandwidthPrio4 Unsigned32, 1504 componentLinkDescrMaxLspBandwidthPrio5 Unsigned32, 1505 componentLinkDescrMaxLspBandwidthPrio6 Unsigned32, 1506 componentLinkDescrMaxLspBandwidthPrio7 Unsigned32, 1507 componentLinkDescrInterfaceMtu Unsigned32, 1508 componentLinkDescrIndication TeLinkSonetSdhIndication, 1509 componentLinkDescrRowStatus RowStatus, 1510 componentLinkDescrStorageType StorageType 1511 } 1513 componentLinkDescrId OBJECT-TYPE 1514 SYNTAX Unsigned32 (1..4294967295) 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "This object specifies the link descriptor identifier." 1519 ::= { componentLinkDescriptorEntry 1 } 1521 componentLinkDescrSwitchingCapability OBJECT-TYPE 1522 SYNTAX TeLinkSwitchingCapability 1523 MAX-ACCESS read-create 1524 STATUS current 1525 DESCRIPTION 1526 "This attribute specifies link multiplexing capabilities of the 1527 component link." 1528 REFERENCE 1529 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1530 -- RFC Editor to fill in RFC number that will be assigned to 1531 -- [GMPLS-OSPF] 1532 ::= { componentLinkDescriptorEntry 2 } 1534 componentLinkDescrEncodingType OBJECT-TYPE 1535 SYNTAX TeLinkEncodingType 1536 MAX-ACCESS read-create 1537 STATUS current 1538 DESCRIPTION 1539 "This attribute specifies the component link encoding type." 1540 REFERENCE 1541 "Generalized MPLS Signaling Functional Description, RFC 3471" 1542 ::= { componentLinkDescriptorEntry 3 } 1544 componentLinkDescrMinLspBandwidth OBJECT-TYPE 1545 SYNTAX Unsigned32 1546 UNITS "thousand bps" 1547 MAX-ACCESS read-create 1548 STATUS current 1549 DESCRIPTION 1550 "This attribute specifies the minimum LSP bandwidth on 1551 the component link. This value is an estimate 1552 in units of 1,000 bits per second." 1553 REFERENCE 1554 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1555 -- RFC Editor to fill in RFC number that will be assigned to 1556 -- [GMPLS-OSPF] 1557 ::= { componentLinkDescriptorEntry 4 } 1559 componentLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1560 SYNTAX Unsigned32 1561 UNITS "thousand bps" 1562 MAX-ACCESS read-create 1563 STATUS current 1564 DESCRIPTION 1565 "This attribute specifies the maximum LSP bandwidth at 1566 priority 0 on the component link. This value is an estimate 1567 in units of 1,000 bits per second." 1568 REFERENCE 1569 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1570 -- RFC Editor to fill in RFC number that will be assigned to 1571 -- [GMPLS-OSPF] 1572 ::= { componentLinkDescriptorEntry 5 } 1574 componentLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1575 SYNTAX Unsigned32 1576 UNITS "thousand bps" 1577 MAX-ACCESS read-create 1578 STATUS current 1579 DESCRIPTION 1580 "This attribute specifies the maximum LSP bandwidth at 1581 priority 1 on the component link. This value is an estimate 1582 in units of 1,000 bits per second." 1583 REFERENCE 1584 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1585 -- RFC Editor to fill in RFC number that will be assigned to 1586 -- [GMPLS-OSPF] 1587 ::= { componentLinkDescriptorEntry 6 } 1589 componentLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1590 SYNTAX Unsigned32 1591 UNITS "thousand bps" 1592 MAX-ACCESS read-create 1593 STATUS current 1594 DESCRIPTION 1595 "This attribute specifies the maximum LSP bandwidth at 1596 priority 2 on the component link. This value is an estimate 1597 in units of 1,000 bits per second." 1598 REFERENCE 1599 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1600 -- RFC Editor to fill in RFC number that will be assigned to 1601 -- [GMPLS-OSPF] 1602 ::= { componentLinkDescriptorEntry 7 } 1604 componentLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1605 SYNTAX Unsigned32 1606 UNITS "thousand bps" 1607 MAX-ACCESS read-create 1608 STATUS current 1609 DESCRIPTION 1610 "This attribute specifies the maximum LSP bandwidth at 1611 priority 3 on the component link. This value is an estimate 1612 in units of 1,000 bits per second." 1613 REFERENCE 1614 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1615 -- RFC Editor to fill in RFC number that will be assigned to 1616 -- [GMPLS-OSPF] 1617 ::= { componentLinkDescriptorEntry 8 } 1619 componentLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1620 SYNTAX Unsigned32 1621 UNITS "thousand bps" 1622 MAX-ACCESS read-create 1623 STATUS current 1624 DESCRIPTION 1625 "This attribute specifies the maximum LSP bandwidth at 1626 priority 4 on the component link. This value is an estimate 1627 in units of 1,000 bits per second." 1628 REFERENCE 1629 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1630 -- RFC Editor to fill in RFC number that will be assigned to 1631 -- [GMPLS-OSPF] 1632 ::= { componentLinkDescriptorEntry 9 } 1634 componentLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1635 SYNTAX Unsigned32 1636 UNITS "thousand bps" 1637 MAX-ACCESS read-create 1638 STATUS current 1639 DESCRIPTION 1640 "This attribute specifies the maximum LSP bandwidth at 1641 priority 5 on the component link. This value is an estimate 1642 in units of 1,000 bits per second." 1643 REFERENCE 1644 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1645 -- RFC Editor to fill in RFC number that will be assigned to 1646 -- [GMPLS-OSPF] 1647 ::= { componentLinkDescriptorEntry 10 } 1649 componentLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1650 SYNTAX Unsigned32 1651 UNITS "thousand bps" 1652 MAX-ACCESS read-create 1653 STATUS current 1654 DESCRIPTION 1655 "This attribute specifies the maximum LSP bandwidth at 1656 priority 6 on the component link. This value is an estimate 1657 in units of 1,000 bits per second." 1658 REFERENCE 1659 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1660 -- RFC Editor to fill in RFC number that will be assigned to 1661 -- [GMPLS-OSPF] 1662 ::= { componentLinkDescriptorEntry 11 } 1664 componentLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1665 SYNTAX Unsigned32 1666 UNITS "thousand bps" 1667 MAX-ACCESS read-create 1668 STATUS current 1669 DESCRIPTION 1670 "This attribute specifies the maximum LSP bandwidth at 1671 priority 7 on the component link. This value is an estimate 1672 in units of 1,000 bits per second." 1674 REFERENCE 1675 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1676 -- RFC Editor to fill in RFC number that will be assigned to 1677 -- [GMPLS-OSPF] 1678 ::= { componentLinkDescriptorEntry 12 } 1680 componentLinkDescrInterfaceMtu OBJECT-TYPE 1681 SYNTAX Unsigned32 (1..65535) 1682 MAX-ACCESS read-create 1683 STATUS current 1684 DESCRIPTION 1685 "This attribute specifies the interface MTU for the component 1686 link descriptor." 1687 REFERENCE 1688 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1689 -- RFC Editor to fill in RFC number that will be assigned to 1690 -- [GMPLS-OSPF] 1691 ::= { componentLinkDescriptorEntry 13 } 1693 componentLinkDescrIndication OBJECT-TYPE 1694 SYNTAX TeLinkSonetSdhIndication 1695 MAX-ACCESS read-create 1696 STATUS current 1697 DESCRIPTION 1698 "This attribute specifies whether this interface supports 1699 Standard or Arbitrary SONET/SDH." 1700 REFERENCE 1701 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1702 -- RFC Editor to fill in RFC number that will be assigned to 1703 -- [GMPLS-OSPF] 1704 ::= { componentLinkDescriptorEntry 14 } 1706 componentLinkDescrRowStatus OBJECT-TYPE 1707 SYNTAX RowStatus 1708 MAX-ACCESS read-create 1709 STATUS current 1710 DESCRIPTION 1711 "This variable is used to create, modify, and/or 1712 delete a row in this table. No read-create object 1713 can be modified when componentLinkDescrRowStatus 1714 is active(1)." 1715 ::= { componentLinkDescriptorEntry 15 } 1717 componentLinkDescrStorageType OBJECT-TYPE 1718 SYNTAX StorageType 1719 MAX-ACCESS read-create 1720 STATUS current 1721 DESCRIPTION 1722 "The storage type for this conceptual row in the 1723 componentLinkDescriptorTable. Conceptual rows 1724 having the value 'permanent' need not allow write-access 1725 to any columnar object in the row." 1726 ::= { componentLinkDescriptorEntry 16 } 1728 -- End of componentLinkDescriptorTable 1730 -- Component Link Bandwidth Table 1732 componentLinkBandwidthTable OBJECT-TYPE 1733 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1734 MAX-ACCESS not-accessible 1735 STATUS current 1736 DESCRIPTION 1737 "This table specifies the priority-based bandwidth 1738 for component links." 1739 ::= { teLinkObjects 7 } 1741 componentLinkBandwidthEntry OBJECT-TYPE 1742 SYNTAX ComponentLinkBandwidthEntry 1743 MAX-ACCESS not-accessible 1744 STATUS current 1745 DESCRIPTION 1746 "An entry in this table contains information about 1747 the priority-based bandwidth on component links. 1748 An ifEntry in the ifTable must exist before a 1749 componentLinkBandwidthEntry using the same ifIndex is 1750 created. ifEntry's ifType can be of any interface type which 1751 has been defined for TE Link interworking. Examples include 1752 ATM, Frame Relay, Ethernet, etc. If a component link entry in 1753 the ifTable is destroyed, then so are all entries in the 1754 componentLinkBandwidthTable that use the ifIndex of 1755 this component link." 1756 INDEX { ifIndex, componentLinkBandwidthPriority } 1757 ::= { componentLinkBandwidthTable 1 } 1759 ComponentLinkBandwidthEntry ::= SEQUENCE { 1760 componentLinkBandwidthPriority TeLinkPriority, 1761 componentLinkBandwidthUnreserved Unsigned32, 1762 componentLinkBandwidthRowStatus RowStatus, 1763 componentLinkBandwidthStorageType StorageType 1764 } 1766 componentLinkBandwidthPriority OBJECT-TYPE 1767 SYNTAX TeLinkPriority 1768 MAX-ACCESS not-accessible 1769 STATUS current 1770 DESCRIPTION 1771 "This attribute specifies the priority. A value of 0 is valid 1772 as specified in the 'Traffic Engineering Extensions to OSPF 1773 Version 2' document." 1774 REFERENCE 1775 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1776 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1777 -- RFC Editor to fill in RFC number that will be assigned to 1778 -- [GMPLS-OSPF] and [OSPF] 1779 ::= { componentLinkBandwidthEntry 1 } 1781 componentLinkBandwidthUnreserved OBJECT-TYPE 1782 SYNTAX Unsigned32 1783 UNITS "thousand bps" 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "This attribute specifies the component link unreserved 1788 bandwidth at priority p. This value is an estimate 1789 in units of 1,000 bits per second." 1790 REFERENCE 1791 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1792 -- RFC Editor to fill in RFC number that will be assigned to 1793 -- [GMPLS-OSPF] 1794 ::= { componentLinkBandwidthEntry 2 } 1796 componentLinkBandwidthRowStatus OBJECT-TYPE 1797 SYNTAX RowStatus 1798 MAX-ACCESS read-create 1799 STATUS current 1800 DESCRIPTION 1801 "This variable is used to create, modify, and/or 1802 delete a row in this table. No read-create object can 1803 be modified when componentLinkBandwidthRowStatus is 1804 active(1)." 1805 ::= { componentLinkBandwidthEntry 4 } 1807 componentLinkBandwidthStorageType OBJECT-TYPE 1808 SYNTAX StorageType 1809 MAX-ACCESS read-create 1810 STATUS current 1811 DESCRIPTION 1812 "The storage type for this conceptual row in the 1813 componentLinkBandwidthTable. Conceptual rows 1814 having the value 'permanent' need not allow write-access 1815 to any columnar object in the row." 1816 ::= { componentLinkBandwidthEntry 5 } 1818 -- End of componentLinkBandwidthTable 1820 -- Module compliance 1822 teLinkGroups 1823 OBJECT IDENTIFIER ::= { teLinkConformance 1 } 1825 teLinkCompliances 1826 OBJECT IDENTIFIER ::= { teLinkConformance 2 } 1828 teLinkModuleFullCompliance MODULE-COMPLIANCE 1829 STATUS current 1830 DESCRIPTION 1831 "Compliance statement for agents that support the 1832 configuration and monitoring of TE Link MIB module." 1833 MODULE -- this module 1835 MANDATORY-GROUPS { teLinkGroup, 1836 teLinkBandwidthGroup, 1837 componentLinkBandwidthGroup } 1839 GROUP teLinkSrlgGroup 1840 DESCRIPTION 1841 "This group is mandatory for G-MPLS enabled devices." 1843 GROUP teLinkPscGroup 1844 DESCRIPTION 1845 "This group is mandatory for devices that support 1846 packet switching capability." 1848 GROUP teLinkTdmGroup 1849 DESCRIPTION 1850 "This group is mandatory for devices that support TDM 1851 switching capability." 1853 -- teLinkTable 1855 OBJECT teLinkAddressType 1856 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1857 DESCRIPTION 1858 "Only ipv4(1) and ipv6(2) address types need to be 1859 supported for numbered links. For unnumbered links, the 1860 unknown(0) address type needs to be supported." 1862 OBJECT teLinkLocalIpAddr 1863 SYNTAX InetAddress (SIZE(0|4|16)) 1864 DESCRIPTION 1865 "Size of TE link IP address depends on type of TE link. 1866 TE link IP address size is zero if link is unnumbered, 1867 four if link IP address is IPv4 and sixteen if link IP 1868 address is IPv6." 1870 OBJECT teLinkRemoteIpAddr 1871 SYNTAX InetAddress (SIZE(0|4|16)) 1872 DESCRIPTION 1873 "Size of TE link IP address depends on type of TE link. 1874 TE link IP address size is zero if link is unnumbered, 1875 four if link IP address is IPv4 and sixteen if link IP 1876 address is IPv6." 1878 OBJECT teLinkRowStatus 1879 SYNTAX RowStatus { active(1), notInService(2) } 1880 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1881 createAndGo(4), destroy(6) } 1882 DESCRIPTION 1883 "Support for notReady(3) and createAndWait(5) is 1884 not required." 1886 -- teLinkDescriptorTable 1888 OBJECT teLinkDescrRowStatus 1889 SYNTAX RowStatus { active(1), notInService(2) } 1890 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1891 createAndGo(4), destroy(6) } 1892 DESCRIPTION 1893 "Support for notReady(3) and createAndWait(5) is 1894 not required." 1896 -- teLinkSrlgTable 1898 OBJECT teLinkSrlgRowStatus 1899 SYNTAX RowStatus { active(1), notInService(2) } 1900 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1901 createAndGo(4), destroy(6) } 1902 DESCRIPTION 1903 "Support for notReady(3) and createAndWait(5) is 1904 not required." 1906 -- teLinkBandwidthTable 1908 OBJECT teLinkBandwidthRowStatus 1909 SYNTAX RowStatus { active(1), notInService(2) } 1910 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1911 createAndGo(4), destroy(6) } 1912 DESCRIPTION 1913 "Support for notReady(3) and createAndWait(5) is 1914 not required." 1916 -- componentLinkTable 1918 OBJECT componentLinkRowStatus 1919 SYNTAX RowStatus { active(1), notInService(2) } 1920 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1921 createAndGo(4), destroy(6) } 1922 DESCRIPTION 1923 "Support for notReady(3) and createAndWait(5) is 1924 not required." 1926 -- componentLinkDescriptorTable 1928 OBJECT componentLinkDescrRowStatus 1929 SYNTAX RowStatus { active(1), notInService(2) } 1930 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1931 createAndGo(4), destroy(6) } 1932 DESCRIPTION 1933 "Support for notReady(3) and createAndWait(5) is 1934 not required." 1936 -- componentLinkBandwidthTable 1938 OBJECT componentLinkBandwidthRowStatus 1939 SYNTAX RowStatus { active(1), notInService(2) } 1940 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1941 createAndGo(4), destroy(6) } 1942 DESCRIPTION 1943 "Support for notReady(3) and createAndWait(5) is 1944 not required." 1946 ::= { teLinkCompliances 1 } 1948 teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE 1949 STATUS current 1950 DESCRIPTION 1951 "Compliance statement for agents that support the 1952 monitoring of TE link MIB module." 1953 MODULE -- this module 1955 -- The mandatory groups have to be implemented 1956 -- by all devices supporting TE links. However, they may all 1957 -- be supported as read-only objects in the case where manual 1958 -- configuration is unsupported. 1960 MANDATORY-GROUPS { teLinkGroup, 1961 teLinkBandwidthGroup, 1962 componentLinkBandwidthGroup } 1964 GROUP teLinkSrlgGroup 1965 DESCRIPTION 1966 "This group is mandatory for G-MPLS enabled devices." 1968 GROUP teLinkPscGroup 1969 DESCRIPTION 1970 "This group is mandatory for devices that support 1971 packet switching capability." 1973 GROUP teLinkTdmGroup 1974 DESCRIPTION 1975 "This group is mandatory for devices that support TDM 1976 switching capability." 1978 -- teLinkTable 1980 OBJECT teLinkAddressType 1981 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1982 MIN-ACCESS read-only 1983 DESCRIPTION 1984 "Only ipv4(1) and ipv6(2) address types need to be 1985 supported for numbered links. For unnumbered links, the 1986 unknown(0) address type needs to be supported." 1988 OBJECT teLinkLocalIpAddr 1989 SYNTAX InetAddress (SIZE(0|4|16)) 1990 MIN-ACCESS read-only 1991 DESCRIPTION 1992 "Size of TE link IP address depends on type of TE link. 1993 TE link IP address size is zero if link is unnumbered, 1994 four if link IP address is IPv4 and sixteen if link IP 1995 address is IPv6." 1997 OBJECT teLinkRemoteIpAddr 1998 SYNTAX InetAddress (SIZE(0|4|16)) 1999 MIN-ACCESS read-only 2000 DESCRIPTION 2001 "Size of TE link IP address depends on type of TE link. 2002 TE link IP address size is zero if link is unnumbered, 2003 four if link IP address is IPv4 and sixteen if link IP 2004 address is IPv6." 2006 OBJECT teLinkProtectionType 2007 MIN-ACCESS read-only 2008 DESCRIPTION 2009 "Write access is not required." 2011 OBJECT teLinkWorkingPriority 2012 MIN-ACCESS read-only 2013 DESCRIPTION 2014 "Write access is not required." 2016 OBJECT teLinkRowStatus 2017 SYNTAX RowStatus { active(1) } 2018 MIN-ACCESS read-only 2019 DESCRIPTION 2020 "Write access is not required and active(1) is the 2021 only status that needs to be supported." 2023 OBJECT teLinkStorageType 2024 MIN-ACCESS read-only 2025 DESCRIPTION 2026 "Write access is not required." 2028 -- teLinkDescriptorTable 2030 OBJECT teLinkDescrSwitchingCapability 2031 MIN-ACCESS read-only 2032 DESCRIPTION 2033 "Write access is not required." 2035 OBJECT teLinkDescrEncodingType 2036 MIN-ACCESS read-only 2037 DESCRIPTION 2038 "Write access is not required." 2040 OBJECT teLinkDescrMinLspBandwidth 2041 MIN-ACCESS read-only 2042 DESCRIPTION 2043 "Write access is not required." 2045 OBJECT teLinkDescrMaxLspBandwidthPrio0 2046 MIN-ACCESS read-only 2047 DESCRIPTION 2048 "Write access is not required." 2050 OBJECT teLinkDescrMaxLspBandwidthPrio1 2051 MIN-ACCESS read-only 2052 DESCRIPTION 2053 "Write access is not required." 2055 OBJECT teLinkDescrMaxLspBandwidthPrio2 2056 MIN-ACCESS read-only 2057 DESCRIPTION 2058 "Write access is not required." 2060 OBJECT teLinkDescrMaxLspBandwidthPrio3 2061 MIN-ACCESS read-only 2062 DESCRIPTION 2063 "Write access is not required." 2065 OBJECT teLinkDescrMaxLspBandwidthPrio4 2066 MIN-ACCESS read-only 2067 DESCRIPTION 2068 "Write access is not required." 2070 OBJECT teLinkDescrMaxLspBandwidthPrio5 2071 MIN-ACCESS read-only 2072 DESCRIPTION 2073 "Write access is not required." 2075 OBJECT teLinkDescrMaxLspBandwidthPrio6 2076 MIN-ACCESS read-only 2077 DESCRIPTION 2078 "Write access is not required." 2080 OBJECT teLinkDescrMaxLspBandwidthPrio7 2081 MIN-ACCESS read-only 2082 DESCRIPTION 2083 "Write access is not required." 2085 OBJECT teLinkDescrRowStatus 2086 SYNTAX RowStatus { active(1) } 2087 MIN-ACCESS read-only 2088 DESCRIPTION 2089 "Write access is not required and active(1) is the 2090 only status that needs to be supported." 2092 OBJECT teLinkDescrStorageType 2093 MIN-ACCESS read-only 2094 DESCRIPTION 2095 "Write access is not required." 2097 -- teLinkSrlgTable 2099 OBJECT teLinkSrlgRowStatus 2100 SYNTAX RowStatus { active(1) } 2101 MIN-ACCESS read-only 2102 DESCRIPTION 2103 "Write access is not required and active(1) is the 2104 only status that needs to be supported." 2106 OBJECT teLinkSrlgStorageType 2107 MIN-ACCESS read-only 2108 DESCRIPTION 2109 "Write access is not required." 2111 -- teLinkBandwidthTable 2113 OBJECT teLinkBandwidthUnreserved 2114 MIN-ACCESS read-only 2115 DESCRIPTION 2116 "Write access is not required." 2118 OBJECT teLinkBandwidthRowStatus 2119 SYNTAX RowStatus { active(1) } 2120 MIN-ACCESS read-only 2121 DESCRIPTION 2122 "Write access is not required and active(1) is the 2123 only status that needs to be supported." 2125 OBJECT teLinkBandwidthStorageType 2126 MIN-ACCESS read-only 2127 DESCRIPTION 2128 "Write access is not required." 2130 -- componentLinkTable 2132 OBJECT componentLinkMaxResBandwidth 2133 MIN-ACCESS read-only 2134 DESCRIPTION 2135 "Write access is not required." 2137 OBJECT componentLinkPreferredProtection 2138 MIN-ACCESS read-only 2139 DESCRIPTION 2140 "Write access is not required." 2142 OBJECT componentLinkRowStatus 2143 SYNTAX RowStatus { active(1) } 2144 MIN-ACCESS read-only 2145 DESCRIPTION 2146 "Write access is not required and active(1) is the 2147 only status that needs to be supported." 2149 OBJECT componentLinkStorageType 2150 MIN-ACCESS read-only 2151 DESCRIPTION 2152 "Write access is not required." 2154 -- componentLinkDescriptorTable 2156 OBJECT componentLinkDescrSwitchingCapability 2157 MIN-ACCESS read-only 2158 DESCRIPTION 2159 "Write access is not required." 2161 OBJECT componentLinkDescrEncodingType 2162 MIN-ACCESS read-only 2163 DESCRIPTION 2164 "Write access is not required." 2166 OBJECT componentLinkDescrMinLspBandwidth 2167 MIN-ACCESS read-only 2168 DESCRIPTION 2169 "Write access is not required." 2171 OBJECT componentLinkDescrMaxLspBandwidthPrio0 2172 MIN-ACCESS read-only 2173 DESCRIPTION 2174 "Write access is not required." 2176 OBJECT componentLinkDescrMaxLspBandwidthPrio1 2177 MIN-ACCESS read-only 2178 DESCRIPTION 2179 "Write access is not required." 2181 OBJECT componentLinkDescrMaxLspBandwidthPrio2 2182 MIN-ACCESS read-only 2183 DESCRIPTION 2184 "Write access is not required." 2186 OBJECT componentLinkDescrMaxLspBandwidthPrio3 2187 MIN-ACCESS read-only 2188 DESCRIPTION 2189 "Write access is not required." 2191 OBJECT componentLinkDescrMaxLspBandwidthPrio4 2192 MIN-ACCESS read-only 2193 DESCRIPTION 2194 "Write access is not required." 2196 OBJECT componentLinkDescrMaxLspBandwidthPrio5 2197 MIN-ACCESS read-only 2198 DESCRIPTION 2199 "Write access is not required." 2201 OBJECT componentLinkDescrMaxLspBandwidthPrio6 2202 MIN-ACCESS read-only 2203 DESCRIPTION 2204 "Write access is not required." 2206 OBJECT componentLinkDescrMaxLspBandwidthPrio7 2207 MIN-ACCESS read-only 2208 DESCRIPTION 2209 "Write access is not required." 2211 OBJECT componentLinkDescrInterfaceMtu 2212 MIN-ACCESS read-only 2213 DESCRIPTION 2214 "Write access is not required." 2216 OBJECT componentLinkDescrIndication 2217 MIN-ACCESS read-only 2218 DESCRIPTION 2219 "Write access is not required." 2221 OBJECT componentLinkDescrRowStatus 2222 SYNTAX RowStatus { active(1) } 2223 MIN-ACCESS read-only 2224 DESCRIPTION 2225 "Write access is not required and active(1) is the 2226 only status that needs to be supported." 2228 OBJECT componentLinkDescrStorageType 2229 MIN-ACCESS read-only 2230 DESCRIPTION 2231 "Write access is not required." 2233 -- componentLinkBandwidthTable 2235 OBJECT componentLinkBandwidthRowStatus 2236 SYNTAX RowStatus { active(1) } 2237 MIN-ACCESS read-only 2238 DESCRIPTION 2239 "Write access is not required and active(1) is the 2240 only status that needs to be supported." 2242 OBJECT componentLinkBandwidthStorageType 2243 MIN-ACCESS read-only 2244 DESCRIPTION 2245 "Write access is not required." 2247 ::= { teLinkCompliances 2 } 2249 -- Units of conformance 2250 teLinkGroup OBJECT-GROUP 2251 OBJECTS { teLinkAddressType, 2252 teLinkLocalIpAddr, 2253 teLinkRemoteIpAddr, 2254 teLinkMetric, 2255 teLinkProtectionType, 2256 teLinkWorkingPriority, 2257 teLinkResourceClass, 2258 teLinkIncomingIfId, 2259 teLinkOutgoingIfId, 2260 teLinkRowStatus, 2261 teLinkStorageType, 2262 teLinkDescrSwitchingCapability, 2263 teLinkDescrEncodingType, 2264 teLinkDescrRowStatus, 2265 teLinkDescrStorageType, 2266 componentLinkPreferredProtection, 2267 componentLinkCurrentProtection, 2268 componentLinkRowStatus, 2269 componentLinkStorageType, 2270 componentLinkDescrSwitchingCapability, 2271 componentLinkDescrEncodingType, 2272 componentLinkDescrRowStatus, 2273 componentLinkDescrStorageType 2274 } 2276 STATUS current 2277 DESCRIPTION 2278 "Collection of objects needed for the monitoring of 2279 resources associated with TE links." 2280 ::= { teLinkGroups 1 } 2282 teLinkSrlgGroup OBJECT-GROUP 2283 OBJECTS { teLinkSrlgRowStatus, 2284 teLinkSrlgStorageType 2285 } 2287 STATUS current 2288 DESCRIPTION 2289 "Collection of objects needed for the monitoring of 2290 SRLG resources associated with TE links." 2291 ::= { teLinkGroups 2 } 2293 teLinkBandwidthGroup OBJECT-GROUP 2294 OBJECTS { teLinkMaximumReservableBandwidth, 2295 teLinkDescrMaxLspBandwidthPrio0, 2296 teLinkDescrMaxLspBandwidthPrio1, 2297 teLinkDescrMaxLspBandwidthPrio2, 2298 teLinkDescrMaxLspBandwidthPrio3, 2299 teLinkDescrMaxLspBandwidthPrio4, 2300 teLinkDescrMaxLspBandwidthPrio5, 2301 teLinkDescrMaxLspBandwidthPrio6, 2302 teLinkDescrMaxLspBandwidthPrio7, 2303 teLinkBandwidthUnreserved, 2304 teLinkBandwidthRowStatus, 2305 teLinkBandwidthStorageType 2306 } 2308 STATUS current 2309 DESCRIPTION 2310 "Collection of objects needed for the monitoring of 2311 the priority-based bandwidth resources associated with 2312 TE links and component links." 2313 ::= { teLinkGroups 3 } 2315 componentLinkBandwidthGroup OBJECT-GROUP 2316 OBJECTS { componentLinkMaxResBandwidth, 2317 componentLinkDescrMaxLspBandwidthPrio0, 2318 componentLinkDescrMaxLspBandwidthPrio1, 2319 componentLinkDescrMaxLspBandwidthPrio2, 2320 componentLinkDescrMaxLspBandwidthPrio3, 2321 componentLinkDescrMaxLspBandwidthPrio4, 2322 componentLinkDescrMaxLspBandwidthPrio5, 2323 componentLinkDescrMaxLspBandwidthPrio6, 2324 componentLinkDescrMaxLspBandwidthPrio7, 2325 componentLinkBandwidthUnreserved, 2326 componentLinkBandwidthRowStatus, 2327 componentLinkBandwidthStorageType 2328 } 2330 STATUS current 2331 DESCRIPTION 2332 "Collection of objects needed for the monitoring of 2333 bandwidth parameters associated with component links." 2334 ::= { teLinkGroups 4 } 2336 teLinkPscGroup OBJECT-GROUP 2337 OBJECTS { teLinkDescrMinLspBandwidth, 2338 teLinkDescrInterfaceMtu, 2339 componentLinkDescrMinLspBandwidth, 2340 componentLinkDescrInterfaceMtu 2341 } 2343 STATUS current 2344 DESCRIPTION 2345 "Collection of objects needed for devices that are 2346 packet switch capable." 2347 ::= { teLinkGroups 5 } 2349 teLinkTdmGroup OBJECT-GROUP 2350 OBJECTS { teLinkDescrMinLspBandwidth, 2351 teLinkDescrIndication, 2352 componentLinkDescrMinLspBandwidth, 2353 componentLinkDescrIndication 2354 } 2356 STATUS current 2357 DESCRIPTION 2358 "Collection of objects needed for devices that are 2359 TDM switching capable." 2360 ::= { teLinkGroups 6 } 2362 -- End of TE-LINK-MIB 2363 END 2365 10. Intellectual Property Considerations 2367 The IETF takes no position regarding the validity or scope of any 2368 intellectual property or other rights that might be claimed to per- 2369 tain to the implementation or use of the technology described in this 2370 document or the extent to which any license under such rights might 2371 or might not be available; neither does it represent that it has made 2372 any effort to identify any such rights. Information on the IETF's 2373 procedures with respect to rights in standards-track and standards- 2374 related documentation can be found in BCP-11. Copies of claims of 2375 rights made available for publication and any assurances of licenses 2376 to be made available, or the result of an attempt made to obtain a 2377 general license or permission for the use of such proprietary rights 2378 by implementers or users of this specification can be obtained from 2379 the IETF Secretariat. 2381 The IETF invites any interested party to bring to its attention any 2382 copyrights, patents or patent applications, or other proprietary 2383 rights which may cover technology that may be required to practice 2384 this standard. Please address the information to the IETF Executive 2385 Director. 2387 11. Security Considerations 2389 There are a number of management objects defined in this MIB module 2390 with a MAX-ACCESS clause of read-write and/or read-create. Such 2391 objects may be considered sensitive or vulnerable in some network 2392 environments. The support for SET operations in a non-secure environ- 2393 ment without proper protection can have a negative effect on network 2394 operations. These are the tables and objects and their sensitiv- 2395 ity/vulnerability: 2397 - All the tables in this MIB module have routing information in 2398 them and so they all have the same security attributes. 2399 Unauthorized changes to attributes of these tables can disrupt 2400 resource allocation in the network. 2402 Some of the readable objects in this MIB module (i.e., objects with a 2403 MAX-ACCESS other than not-accessible) may be considered sensitive or 2404 vulnerable in some network environments. It is thus important to con- 2405 trol even GET and/or NOTIFY access to these objects and possibly to 2406 even encrypt the values of these objects when sending them over the 2407 network via SNMP. These are the tables and objects and their sensi- 2408 tivity/vulnerability: 2410 - IP address entries in the teLinkTable (teLinkLocalIpAddr and 2411 teLinkRemoteIpAddr) may reveal the internals of a network provider 2412 IP address space. 2414 SNMP versions prior to SNMPv3 did not include adequate security. 2415 Even if the network itself is secure (for example by using IPSec), 2416 even then, there is no control as to who on the secure network is 2417 allowed to access and GET/SET (read/change/create/delete) the objects 2418 in this MIB module. 2420 It is RECOMMENDED that implementers consider the security features as 2421 provided by the SNMPv3 framework (see [RFC3410], section 8), includ- 2422 ing full support for the SNMPv3 cryptographic mechanisms (for authen- 2423 tication and privacy). 2425 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOM- 2426 MENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable 2427 cryptographic security. It is then a customer/operator responsibility 2428 to ensure that the SNMP entity giving access to an instance of this 2429 MIB module is properly configured to give access to the objects only 2430 to those principals (users) that have legitimate rights to indeed GET 2431 or SET (change/create/delete) them. 2433 12. Acknowledgments 2435 The authors would like to acknowledge the contribution of Dmitry 2436 Ryumkin. 2438 13. References 2440 13.1. Normative References 2442 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2443 Requirement Levels", BCP 14, RFC 2119, March 1997. 2445 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2446 J., Rose, M., and S. Waldbusser, "Structure of 2447 Management Information Version 2 (SMIv2)", STD 58, 2448 RFC 2578, April 1999. 2450 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2451 J., Rose, M., and S. Waldbusser, "Textual Conventions 2452 for SMIv2", STD 58, RFC 2579, April 1999. 2454 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2455 J., Rose, M., and Waldbusser, S., "Conformance 2456 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2458 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2459 Group MIB", RFC 2863, June 2000. 2461 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 2462 Shoenwaelder, J., "Textual Conventions for Internet 2463 Network Addresses", RFC 3291, May 2002. 2465 [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., 2466 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2467 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2468 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2469 "Generalized MPLS Signaling Functional Description", 2470 RFC 3471, January 2003. 2472 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2473 "Link Bundling in MPLS Traffic Engineering", 2474 Internet Draft , 2475 July 2002. 2477 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2478 Extensions in Support of Generalized MPLS", Internet 2479 Draft , 2480 December 2002. 2482 [HIERARCHY] Kompella, K., Rekhter, Y., "LSP Hierarchy with 2483 Generalized MPLS TE", Internet Draft 2484 , 2485 September 2002. 2487 [IANAifType] "IANAifType MIB Module", 2488 http://www.iana.org/assignments/ianaiftype-mib. 2490 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2491 Rekhter, Y., Berger, L., Rajagopalan, B., 2492 Basak, D., Sandick, H., Zinin, A., 2493 Rajagopalan, B., and Ramamoorthi, S., 2494 "Link Management Protocol", 2495 Internet Draft , 2496 June 2003. 2498 [OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic 2499 Engineering Extensions to OSPF", Internet Draft 2500 , October 2002. 2502 [ROUTING] Kompella, K., Rekhter, Y., "Routing Extensions in 2503 Support of Generalized MPLS", Internet Draft 2504 , June 2003. 2506 13.2. Informative References 2508 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2509 "Introduction and Applicability Statements for 2510 Internet-Standard Management Framework", RFC 3410, 2511 December 2002. 2513 [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., 2514 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2515 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2516 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2517 Lang, J., Liaw, F., Nadeau, T., Ong, L., 2518 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2519 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2520 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2521 Zinin, A., "Generalized Multi-Protocol Label Switching 2522 (GMPLS) Architecture", Internet Draft 2523 , 2524 May 2003. 2526 14. Authors' Addresses 2528 Martin Dubuc Thomas D. Nadeau 2529 Email: dubuc.consulting@rogers.com Cisco Systems, Inc. 2530 300 Apollo Drive 2531 Chelmsford, MA 01824 2532 Phone: +1-978-244-3051 2533 Email: tnadeau@cisco.com 2535 Sudheer Dharanikota Jonathan P. Lang 2536 Email: sudheer@avici.com Rincon Networks, Inc. 2537 110 El Paseo 2538 Santa Barbara, CA 93101 2539 Email: jplang@ieee.org 2541 15. Full Copyright Statement 2543 Copyright (C) The Internet Society (2003). All Rights Reserved. 2545 This document and translations of it may be copied and furnished to 2546 others, and derivative works that comment on or otherwise explain it 2547 or assist in its implementation may be prepared, copied, published 2548 and distributed, in whole or in part, without restriction of any 2549 kind, provided that the above copyright notice and this paragraph are 2550 included on all such copies and derivative works. However, this docu- 2551 ment itself may not be modified in any way, such as by removing the 2552 copyright notice or references to the Internet Society or other 2553 Internet organizations, except as needed for the purpose of develop- 2554 ing Internet standards in which case the procedures for copyrights 2555 defined in the Internet Standards process must be followed, or as 2556 required to translate it into languages other than English. 2558 The limited permissions granted above are perpetual and will not be 2559 revoked by the Internet Society or its successors or assigns. This 2560 document and the information contained herein is provided on an "AS 2561 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2562 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2563 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2564 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2565 OR FITNESS FOR A PARTICULAR PURPOSE.