idnits 2.17.1 draft-ietf-mpls-telink-mib-04.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 use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (September 2003) is 7500 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 (~~), 3 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft 4 Category: Standards Track Sudheer Dharanikota 5 Expires: March 2004 6 Thomas D. Nadeau 7 Cisco Systems 9 Jonathan P. Lang 10 Rincon Networks 12 September 2003 14 Traffic Engineering Link Management Information Base 16 draft-ietf-mpls-telink-mib-04.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 . . . . . . . . . . . . . . . . . . . . 50 66 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 51 67 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 68 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 52 69 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53 70 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53 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 91 Management Protocol (LMP) [LMP] use the concept of traffic 92 engineering (TE) links to abstract link properties. The effect of 93 this approach is the reduction of the amount of routing information 94 exchanged in the network, which improves routing scalability. In 95 addition, the use of TE link allows the implementation of new 96 capabilities such as link 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 114 similar entities between a node pair into a bundled link [BUNDLING]. 115 In the document, those entities are referred to as TE links. A TE 116 link is a subinterface capable of carrying MPLS traffic engineered 117 traffic. A TE Link may be comprised of only one underlying component 118 link. In cases where more than one component links are to be 119 combined, multiple component links should be created with differing 120 priorities 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. 126 Furthermore, if there are more than one TE link in a link bundle at 127 some time, and at some point later, all but one of the links are 128 deleted, the agent may choose to either delete the link bundle, or it 129 may 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 135 following 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 while 166 Sections 6.5-6.7 describe objects pertaining to component links. The 167 MIB objects were derived from the link bundling document [BUNDLING]. 169 6.1. teLinkTable 171 This table represents the TE links, including bundled links, and 172 their generic traffic engineering parameters. 174 6.2. teLinkDescriptorTable 176 This table represents the TE link interface switching capability 177 descriptors. 179 6.3. teLinkSrlgTable 181 This table represents the shared risk link groups (SRLGs) associated 182 with TE links. 184 6.4. teLinkBandwidthTable 186 This table specifies the priority-based bandwidth traffic engineering 187 parameters associated with TE links. 189 6.5. componentLinkTable 191 This table enumerates the component links and their generic traffic 192 engineering parameters. 194 6.6. componentLinkDescriptorTable 196 This table enumerates the interface switching capability descriptors 197 that each component link supports. 199 6.7. componentLinkBandwidthTable 201 The component link bandwidth table specifies the priority-based 202 bandwidth values associated with the component links. 204 Component links that belong to the same TE link must be compatible. 205 If these two tables are managed independently, mechanisms should be 206 put in place to ensure consistency between the two tables. TE links 207 that form a bundled link must have compatible traffic engineering 208 parameters (resource class, link metric and protection type). 210 The link descriptors of the teLinkDescriptorTable can be derived from 211 the link descriptors of the componentLinkDescrTable. 213 Some of the bandwidth parameters of the teLinkTable, 214 teLinkDescriptorTable, teLinkBandwidthTable are derived from the 215 bandwidth parameters of the componentLinkTable, 216 componentLinkDescriptorTable and componentLinkBandwidthTable (maximum 217 reservable bandwidth, minimum LSP bandwidth, maximum LSP bandwidth at 218 specified priority and unreserved bandwidth). 220 7. Example of Bundled Link Setup 222 In this section we provide a brief example of using the MIB 223 objects described in section 10 to set up a bundled link. 224 While this example is not meant to illustrate every nuance of the 225 MIB module, it is intended as an aid to understanding some 226 of the key concepts. It is meant to be read after going through the 227 MIB module itself. More details on the use of the ifStackTable 228 to establish relationship between bundled links, TE links and 229 component links are given in Section 8.2. 231 Suppose that one would like to manually create a bundled link 232 out of two 1:1 TE links as depicted on the figure in Section 8.2. 233 Assume that the bundled link is associated with SRLGs 10 and 50. 234 Finally, let the component links be port entity interfaces 235 (lambdas). The following example illustrates which rows and 236 corresponding objects might be created to accomplish this. 238 First, a bundled link entry is created. An ifEntry with the same 239 ifIndex and with ifType teLink needs to be created beforehand. 241 In teLinkTable: 242 { 243 ifIndex = 2, 244 teLinkAddressType = unknown(0), 245 teLinkLocalIpAddr = ''H, 246 teLinkRemoteIpAddr = ''H, 247 teLinkMetric = 5, 248 teLinkProtectionType = dedicated1For1(4), 249 teLinkWorkingPriority = 7, 250 teLinkResourceClass = 3, 251 teLinkIncomingIfId = 0, 252 teLinkOutgoingIfId = 2, 253 teLinkRowStatus = createAndGo(4), 254 teLinkStorageType = nonVolatile(3) 255 } 257 In ifStackTable: 258 { 259 ifStackHigherLayer = 0, 260 ifStackLowerLayer = 2, 261 ifStackStatus = createAndGo(4) 262 } 264 Next, the two TE links are created. 266 In teLinkTable: 267 { 268 ifIndex = 3, 269 teLinkAddressType = unknown(0), 270 teLinkLocalIpAddr = ''H, 271 teLinkRemoteIpAddr = ''H, 272 teLinkMetric = 5, 273 teLinkProtectionType = unprotected(2), 274 teLinkWorkingPriority = 7, 275 teLinkResourceClass = 3, 276 teLinkIncomingIfId = 0, 277 teLinkOutgoingIfId = 3, 278 teLinkRowStatus = createAndGo(4), 279 teLinkStorageType = nonVolatile(3) 280 } 282 In ifStackTable: 283 { 284 ifStackHigherLayer = 2, 285 ifStackLowerLayer = 3, 286 ifStackStatus = createAndGo(4) 287 } 289 In teLinkTable: 290 { 291 ifIndex = 4, 292 teLinkAddressType = unknown(0), 293 teLinkLocalIpAddr = ''H, 294 teLinkRemoteIpAddr = ''H, 295 teLinkMetric = 5, 296 teLinkProtectionType = unprotected(2), 297 teLinkWorkingPriority = 7, 298 teLinkResourceClass = 3, 299 teLinkIncomingIfId = 0, 300 teLinkOutgoingIfId = 4, 301 teLinkRowStatus = createAndGo(4), 302 teLinkStorageType = nonVolatile(3) 303 } 305 In ifStackTable: 306 { 307 ifStackHigherLayer = 2, 308 ifStackLowerLayer = 4, 309 ifStackStatus = createAndGo(4) 310 } 312 We assign SRLGs to the TE links. 314 In the teLinkSrlgTable: 315 { 316 ifIndex = 3, 317 teLinkSrlg = 10, 318 teLinkSrlgRowStatus = createAndGo(4), 319 teLinkSrlgStorageType = nonVolatile(3) 320 } 322 In the teLinkSrlgTable: 323 { 324 ifIndex = 4, 325 teLinkSrlg = 50, 326 teLinkSrlgRowStatus = createAndGo(4), 327 teLinkSrlgStorageType = nonVolatile(3) 328 } 330 The bundled link inherits the SRLG properties from the 331 associated TE links. 333 Next, for each unbundled TE link, a component link is created. 335 An ifEntry with the same ifIndex needs to be created beforehand. 337 In componentLinkTable: 338 { 339 ifIndex = 5, 340 componentLinkPreferredProtection = primary(1), 341 componentLinkRowStatus = createAndGo(4), 342 componentLinkStorageType = nonVolatile(3) 343 } 345 In ifStackTable: 346 { 347 ifStackHigherLayer = 3, 348 ifStackLowerLayer = 5, 349 ifStackStatus = createAndGo(4) 350 } 352 In componentLinkTable: 353 { 354 ifIndex = 6, 355 componentLinkPreferredProtection = secondary(2), 356 componentLinkRowStatus = createAndGo(4) 357 componentLinkStorageType = nonVolatile(3) 358 } 360 In ifStackTable: 361 { 362 ifStackHigherLayer = 4, 363 ifStackLowerLayer = 6, 364 ifStackStatus = createAndGo(4) 365 } 367 In this example, once a component link is added to the 368 componentLinkTable, the associated link descriptors are 369 implicitly added to the componentLinkDescriptorTable. 371 TE link link descriptors are derived from their component link 372 descriptors. 374 Note that the bandwidth attributes in teLinkDescriptorTable, 375 componentLinkDescriptorTable, teLinkBandwidthTable 376 and componentLinkBandwidthTable are maintained by the 377 device according to LSP creation/deletion at different priorities. 378 The values in the teLinkBandwidthTable are an aggregation 379 of the values for the component links of the TE links and 380 the TE links of the bundled link. 382 8. Application of the Interfaces Group to TE Links 384 The Interfaces Group [RFC2863] defines generic managed objects for 385 managing interfaces. This memo contains the media-specific 386 extensions to the Interfaces Group for managing TE Link interfaces 387 as logical interfaces. 389 This memo assumes the interpretation of the Interfaces Group to be 390 in accordance with [RFC2863] which states that the interfaces table 391 (ifTable) contains information on the managed resource's 392 interfaces and that each sub-layer below the internetwork layer of 393 a network interface is considered an interface. Thus, the TE Link 394 interface is represented as an entry in the ifTable. The 395 interrelation of entries in the ifTable is defined by Interfaces 396 Stack Group defined in [RFC2863]. 398 When using TE Link interfaces, the interface stack table might appear 399 as follows: 401 +----------------------------------------+ 402 | TE link-interface ifType = teLink(200) + 403 +----------------------------------------+ 404 | Underlying Layer... + 405 +----------------------------------------+ 407 In the above diagram, "Underlying Layer..." refers to the ifIndex 408 of any interface type, which has been defined for TE Link 409 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 411 8.1. Support of the TE Link Layer by ifTable 413 Some specific interpretations of ifTable for the TE Link layer 414 follow. 416 Object Use for the TE Link layer 418 ifIndex Each TE Link interface is represented by an ifEntry. 420 ifDescr Description of the TE Link interface. 422 ifType The value that is allocated for TE Link is 200 423 [IANAifType]. 425 ifSpeed The total bandwidth in bits per second for use by 426 the TE Link layer. 428 ifPhysAddress Unused. 430 ifAdminStatus This variable indicates the administrator's intent 431 as to whether TE Link should be enabled, disabled, or 432 running in some diagnostic testing mode on this 433 interface. Also see [RFC2863]. 435 ifOperStatus This value reflects the actual or operational 436 status of TE Link on this interface. 438 ifLastChange See [RFC2863]. 440 ifInOctets The number of received octets over the interface, 441 i.e., the number of received octets in all component 442 links associated with the interface. 444 ifOutOctets The number of transmitted octets over the 445 interface, i.e., the number of octets transmitted 446 over all component links associated with the 447 interface. 449 ifInErrors The number of packets dropped due to 450 uncorrectable errors. 452 ifInUnknownProtos 453 The number of received packets discarded during 454 packet header validation. 456 ifOutErrors See [RFC2863]. 458 ifName Textual name (unique on this system) of the 459 interface or an octet string of zero length. 461 ifLinkUpDownTrapEnable 462 Default is disabled (2). 464 ifConnectorPresent 465 Set to false (2). 467 ifHighSpeed See [RFC2863]. 469 ifHCInOctets The 64-bit version of ifInOctets; supported if 470 required by the compliance statements in [RFC2863]. 472 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 473 required by the compliance statements in [RFC2863]. 475 ifAlias The non-volatile 'alias' name for the interface as 476 specified by a network manager. 478 ifCounterDiscontinuityTime 479 See [RFC2863]. 481 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 482 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 483 if encoding type is clear. For other encoding types, traffic 484 counters on a TE link are cumulative for all subinterfaces which it 485 binds together. 487 8.2. Using ifStackTable 489 This section describes by example how to use ifStackTable to 490 represent the relationship of TE links with underlying TE-enabled 491 interfaces. Implementors of the stack table for TE link interfaces 492 should look at the appropriate RFC for the service being stacked 493 on TE links. Examples given below are for illustration purposes 494 only. 496 Example: MPLS is being carried on a bundled TE links. 497 The bundled TE link represents a 1:1 optical 498 transport interface. 500 In this example, the component link is a TE link. The two component 501 links/TE links are grouped in a bundled link. 503 +-------------------------------------------------------------------+ 504 | MPLS interface ifType = mpls(166) | 505 | ifIndex = 1 | 506 +-------------------------------------------------------------------+ 507 | TE link (bundled link) ifType = teLink(200) | 508 | ifIndex = 2 | 509 +--------------------------------+-+--------------------------------+ 510 | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | 511 | ifIndex = 3 | | ifIndex = 4 | 512 +--------------------------------+ +--------------------------------+ 513 | Component link | | Component link | 514 | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | 515 | ifIndex = 5 | | ifIndex = 6 | 516 +--------------------------------+ +--------------------------------+ 518 The assignment of the index values could for example be: 520 ifIndex Description 521 1 mpls (type 166) 522 2 teLink (type 200) 523 3 teLink (type 200) 524 4 teLink (type 200) 525 5 opticalTransport (type 196) 526 6 opticalTransport (type 196) 528 The ifStackTable is then used to show the relationships between the 529 various interfaces. 531 ifStackTable Entries 533 HigherLayer LowerLayer 534 0 1 535 1 2 536 2 3 537 2 4 538 3 5 539 4 6 540 5 0 541 6 0 543 In the case where MPLS is using a single TE link, then 544 the upper TE link layer (link bundle) is not required. 546 +-----------------------------------+ 547 | MPLS interface ifType = mpls(166) | 548 +-----------------------------------+ 549 | TE link ifType = teLink(200) | 550 +-----------------------------------+ 551 | Component link | 552 | ifType = opticalTransport(196) | 553 +-----------------------------------+ 555 The assignment of the index values could for example be: 557 ifIndex Description 558 1 mpls (type 166) 559 2 teLink (type 200) 560 3 opticalTransport (type 196) 562 The ifStackTable is then used to show the relationships between the 563 various interfaces. 565 ifStackTable Entries 567 HigherLayer LowerLayer 568 0 1 569 1 2 570 2 3 571 3 0 573 9. TE Link MIB Module Definitions 575 TE-LINK-STD-MIB DEFINITIONS ::= BEGIN 577 IMPORTS 578 MODULE-IDENTITY, OBJECT-TYPE, transmission, Unsigned32 579 FROM SNMPv2-SMI 581 MODULE-COMPLIANCE, OBJECT-GROUP 582 FROM SNMPv2-CONF 584 TEXTUAL-CONVENTION, RowStatus, StorageType 585 FROM SNMPv2-TC 587 InterfaceIndexOrZero, ifIndex 588 FROM IF-MIB 590 InetAddressType, InetAddress 591 FROM INET-ADDRESS-MIB; 593 teLinkStdMIB MODULE-IDENTITY 594 LAST-UPDATED "200309041200Z" -- 4 September 2003 12:00:00 EST 595 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 596 CONTACT-INFO 597 " Martin Dubuc 598 Email: dubuc.consulting@rogers.com 600 Sudheer Dharanikota 601 Email: sudheer@ieee.org 603 Thomas D. Nadeau 604 Email: tnadeau@cisco.com 606 Jonathan P. Lang 607 Email: jplang@ieee.org 609 Comments about this document should be emailed directly to 610 the MPLS working group mailing list at mpls@uu.net." 612 DESCRIPTION 613 "Copyright (C) 2003 The Internet Society. This version of 614 this MIB module is part of RFC XXXX; see the RFC 615 itself for full legal notices. 617 This MIB module contains managed object definitions for 618 MPLS traffic engineering links as defined in 619 'Link Bundling in MPLS Traffic Engineering'." 621 -- Revision history. 622 REVISION 623 "200309041200Z" -- 4 September 2003 12:00:00 EST 624 DESCRIPTION 625 "Initial version published as RFC xxxx (to be assigned by RFC 626 Editor)" 627 ::= { transmission xxx } -- To be assigned by IANA. 628 -- Request to assign 200 which is 629 -- ifType value for teLink. 631 -- Textual Conventions 633 TeLinkPriority ::= TEXTUAL-CONVENTION 634 DISPLAY-HINT "d" 635 STATUS current 636 DESCRIPTION 637 "This type is used to represent a priority. Each connection is 638 assigned a priority. This priority is used when accounting for 639 bandwidth on TE links or component links, for resource 640 allocation and for rerouting purposes. Value 0 is the highest 641 priority. Value 7 is the lowest priority." 642 SYNTAX Unsigned32 (0..7) 644 TeLinkProtection ::= TEXTUAL-CONVENTION 645 STATUS current 646 DESCRIPTION 647 "Link protection." 648 SYNTAX INTEGER { 649 primary(1), 650 secondary(2) 651 } 653 TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION 654 STATUS current 655 DESCRIPTION 656 "Switching capability as specified in the 'OSPF Extensions in 657 Support of Generalized MPLS' document. The values specified in 658 this document are not contiguous." 659 SYNTAX INTEGER { 660 packetSwitch1(1), 661 packetSwitch2(2), 662 packetSwitch3(3), 663 packetSwitch4(4), 664 layer2Switch(51), 665 tdm(100), 666 lambdaSwitch(150), 667 fiberSwitch(200) 669 } 671 TeLinkEncodingType ::= TEXTUAL-CONVENTION 672 STATUS current 673 DESCRIPTION 674 "Link encoding type as specified in 'GMPLS Signaling Functional 675 Description' document. The values specified in this document are 676 not contiguous." 677 SYNTAX INTEGER { 678 packet(1), 679 ethernet(2), 680 ansiEtsiPdh(3), 681 sdhItuSonetAnsi(5), 682 digitalWrapper(7), 683 lambda(8), 684 fiber(9), 685 fiberChannel(11) 686 } 688 TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION 689 STATUS current 690 DESCRIPTION 691 "This convention is used to indicate whether the interface 692 supports Standard or Arbitrary SONET/SDH. The values used 693 in this textual convention are as specified in the 694 interface switching capability specific information field." 695 REFERENCE 696 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 697 -- RFC Editor to fill in RFC number that will be assigned to 698 -- [GMPLS-OSPF] 699 SYNTAX INTEGER { 700 standard(0), 701 arbitrary(1) 702 } 704 -- Top level components of this MIB module 706 -- Notifications 707 teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } 708 -- Tables, Scalars 709 teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 } 710 -- Conformance 711 teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 } 713 -- TE Link Table 715 teLinkTable OBJECT-TYPE 716 SYNTAX SEQUENCE OF TeLinkEntry 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "This table specifies the grouping of component links into 721 TE links and grouping of TE links into bundled links." 722 ::= { teLinkObjects 1 } 724 teLinkEntry OBJECT-TYPE 725 SYNTAX TeLinkEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "An entry in this table exists for each ifEntry with an 730 ifType of teLink(200), i.e. for every TE link. An ifEntry 731 in the ifTable must exist before a teLinkEntry is created with 732 the corresponding ifIndex. If a TE link entry in the ifTable is 733 destroyed, then so is the corresponding entry in the 734 teLinkTable. The administrative and operational status values 735 are controlled from the ifEntry." 736 INDEX { ifIndex } 737 ::= { teLinkTable 1 } 739 TeLinkEntry ::= SEQUENCE { 740 teLinkAddressType InetAddressType, 741 teLinkLocalIpAddr InetAddress, 742 teLinkRemoteIpAddr InetAddress, 743 teLinkMetric Unsigned32, 744 teLinkMaximumReservableBandwidth Unsigned32, 745 teLinkProtectionType INTEGER, 746 teLinkWorkingPriority TeLinkPriority, 747 teLinkResourceClass Unsigned32, 748 teLinkIncomingIfId InterfaceIndexOrZero, 749 teLinkOutgoingIfId InterfaceIndexOrZero, 750 teLinkRowStatus RowStatus, 751 teLinkStorageType StorageType 752 } 754 teLinkAddressType OBJECT-TYPE 755 SYNTAX InetAddressType 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "The type of Internet address for the TE link." 760 ::= { teLinkEntry 1 } 762 teLinkLocalIpAddr OBJECT-TYPE 763 SYNTAX InetAddress 764 MAX-ACCESS read-create 765 STATUS current 766 DESCRIPTION 767 "The local Internet address for numbered links. The type of this 768 address is determined by the value of the teLinkAddressType 769 object. 771 For IPv4 and IPv6 numbered links, this object represents the 772 local IP address associated with the TE link. For an 773 unnumbered link, the local address is of type unknown and this 774 object is set to the zero length string and the 775 teLinkOutgoingIfId object then identifies the unnumbered 776 address. 778 If the TE link is a Forwarding Adjacency (FA), the local 779 IP address is set to the head-end address of the FA-LSP." 780 ::= { teLinkEntry 2 } 782 teLinkRemoteIpAddr OBJECT-TYPE 783 SYNTAX InetAddress 784 MAX-ACCESS read-create 785 STATUS current 786 DESCRIPTION 787 "The remote Internet address for numbered links. The type of 788 this address is determined by the value of the 789 teLinkAddressType object. 791 The remote IP address associated with the TE link (IPv4 and 792 IPv6 numbered links). For an unnumbered link, the remote 793 address is of type unknown and this object is set to the 794 zero length string and the teLinkIncomingIfId object then 795 identifies the unnumbered address. 797 If the TE link is a Forwarding Adjacency, the remote IP 798 address is set to the tail-end address of the FA-LSP." 799 ::= { teLinkEntry 3 } 801 teLinkMetric OBJECT-TYPE 802 SYNTAX Unsigned32 803 MAX-ACCESS read-create 804 STATUS current 805 DESCRIPTION 806 "The traffic engineering metric for the TE link is 807 derived from its component links. All component links 808 within the TE link must have the same traffic 809 engineering metric." 810 REFERENCE 811 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 812 -- RFC Editor to fill in RFC number that will be assigned to 813 -- [BUNDLING] 814 ::= { teLinkEntry 4 } 816 teLinkMaximumReservableBandwidth OBJECT-TYPE 817 SYNTAX Unsigned32 818 UNITS "thousand bps" 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "This attribute specifies the maximum reservable bandwidth on 823 the TE link. This is the union of the maximum reservable 824 bandwidth of all the component links within the 825 TE link that can be used to carry live traffic. This value 826 is an estimate in units of 1,000 bits per second." 827 REFERENCE 828 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 829 -- RFC Editor to fill in RFC number that will be assigned to 830 -- [GMPLS-OSPF] 831 ::= { teLinkEntry 5 } 833 teLinkProtectionType OBJECT-TYPE 834 SYNTAX INTEGER { 835 extraTraffic(1), 836 unprotected(2), 837 shared(3), 838 dedicated1For1(4), 839 dedicated1Plus1(5), 840 enhanced(6) 841 } 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "This attribute specifies link protection type of the 846 TE link. Description of the different protection types can be 847 found in the 'Routing Extensions in Support of Generalized 848 MPLS' document." 849 REFERENCE 850 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 851 Routing Extensions in Support of Generalized MPLS, RFC xxxx" 852 -- RFC Editor to fill in RFC number that will be assigned to 853 -- [GMPLS-OSPF] and [ROUTING] 854 ::= { teLinkEntry 6 } 856 teLinkWorkingPriority OBJECT-TYPE 857 SYNTAX TeLinkPriority 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "This object represents a priority value such that a new 862 connection with a higher priority, i.e. numerically lower than 863 this value, is guaranteed to be setup on a primary link and 864 not on a secondary link." 865 REFERENCE 866 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 867 -- RFC Editor to fill in RFC number that will be assigned to 868 -- [GMPLS-OSPF] 869 ::= { teLinkEntry 7 } 871 teLinkResourceClass OBJECT-TYPE 872 SYNTAX Unsigned32 873 MAX-ACCESS read-create 874 STATUS current 875 DESCRIPTION 876 "This attribute specifies the TE link resource class. 877 The resource class is a 32 bit bitfield. The resource class for 878 a link bundle is derived from the resource class of its 879 TE links. All TE links within a link bundle must have the 880 same resource class. Encoding of the resource class is described 881 in the 'Traffic Engineering Extensions to OSPF Version 2' 882 document." 883 REFERENCE 884 "Link Bundling in MPLS Traffic Engineering, RFC xxxx and 885 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 886 -- RFC Editor to fill in RFC number that will be assigned to 887 -- [BUNDLING] and [OSPF] 888 ::= { teLinkEntry 8 } 890 teLinkIncomingIfId OBJECT-TYPE 891 SYNTAX InterfaceIndexOrZero 892 MAX-ACCESS read-create 893 STATUS current 894 DESCRIPTION 895 "For unnumbered links, the incoming interface is set to the 896 outgoing interface identifier chosen by the neighboring LSR 897 for the reverse link corresponding to this TE link. For 898 numbered links, the address is stored in the teLinkRemoteIpAddr 899 instead." 900 REFERENCE 901 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 902 -- RFC Editor to fill in RFC number that will be assigned to 903 -- [BUNDLING] 904 ::= { teLinkEntry 9 } 906 teLinkOutgoingIfId OBJECT-TYPE 907 SYNTAX InterfaceIndexOrZero 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "If the link is unnumbered, the outgoing interface identifier is 912 set to the outgoing interface identifier chosen for the TE link 913 by the advertising LSR. For numbered links, the address is 914 stored in the teLinkLocalIpAddr instead." 915 REFERENCE 916 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 917 -- RFC Editor to fill in RFC number that will be assigned to 918 -- [BUNDLING] 919 ::= { teLinkEntry 10 } 921 teLinkRowStatus OBJECT-TYPE 922 SYNTAX RowStatus 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "This variable is used to create, modify, and/or 927 delete a row in this table. None of the writable objects in 928 a row can be changed if status is active(1)." 929 ::= { teLinkEntry 11 } 931 teLinkStorageType OBJECT-TYPE 932 SYNTAX StorageType 933 MAX-ACCESS read-create 934 STATUS current 935 DESCRIPTION 936 "The storage type for this conceptual row in the 937 teLinkTable. Conceptual rows having the value 938 'permanent' need not allow write-access to any 939 columnar object in the row." 940 ::= { teLinkEntry 12 } 942 -- End of teLinkTable 944 -- TE Link Descriptor Table 946 teLinkDescriptorTable OBJECT-TYPE 947 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "This table specifies the interface switching capability 952 descriptors associated with the TE links." 953 ::= { teLinkObjects 2 } 955 teLinkDescriptorEntry OBJECT-TYPE 956 SYNTAX TeLinkDescriptorEntry 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION 960 "An entry in this table is created for every TE link interface 961 switching capability descriptor. An ifEntry in the ifTable 962 must exist before a teLinkDescriptorEntry using the same 963 ifIndex is created. ifType of ifEntry must be teLink(200). 964 If a TE link entry in the ifTable is destroyed, then so are all 965 entries in the teLinkDescriptorTable that use the ifIndex of 966 this TE link." 967 INDEX { ifIndex, teLinkDescriptorId } 968 ::= { teLinkDescriptorTable 1 } 970 TeLinkDescriptorEntry ::= SEQUENCE { 971 teLinkDescriptorId Unsigned32, 972 teLinkDescrSwitchingCapability TeLinkSwitchingCapability, 973 teLinkDescrEncodingType TeLinkEncodingType, 974 teLinkDescrMinLspBandwidth Unsigned32, 975 teLinkDescrMaxLspBandwidthPrio0 Unsigned32, 976 teLinkDescrMaxLspBandwidthPrio1 Unsigned32, 977 teLinkDescrMaxLspBandwidthPrio2 Unsigned32, 978 teLinkDescrMaxLspBandwidthPrio3 Unsigned32, 979 teLinkDescrMaxLspBandwidthPrio4 Unsigned32, 980 teLinkDescrMaxLspBandwidthPrio5 Unsigned32, 981 teLinkDescrMaxLspBandwidthPrio6 Unsigned32, 982 teLinkDescrMaxLspBandwidthPrio7 Unsigned32, 983 teLinkDescrInterfaceMtu Unsigned32, 984 teLinkDescrIndication TeLinkSonetSdhIndication, 985 teLinkDescrRowStatus RowStatus, 986 teLinkDescrStorageType StorageType 987 } 989 teLinkDescriptorId OBJECT-TYPE 990 SYNTAX Unsigned32 (1..4294967295) 991 MAX-ACCESS not-accessible 992 STATUS current 993 DESCRIPTION 994 "This object specifies the link descriptor identifier." 995 ::= { teLinkDescriptorEntry 1 } 997 teLinkDescrSwitchingCapability OBJECT-TYPE 998 SYNTAX TeLinkSwitchingCapability 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "This attribute specifies interface switching capability of the 1003 TE link, which is derived from its component links." 1005 REFERENCE 1006 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1007 -- RFC Editor to fill in RFC number that will be assigned to 1008 -- [GMPLS-OSPF] 1009 ::= { teLinkDescriptorEntry 2 } 1011 teLinkDescrEncodingType OBJECT-TYPE 1012 SYNTAX TeLinkEncodingType 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "This attribute specifies the TE link encoding type." 1017 REFERENCE 1018 "Generalized MPLS Signaling Functional Description, RFC 3471" 1019 ::= { teLinkDescriptorEntry 3 } 1021 teLinkDescrMinLspBandwidth OBJECT-TYPE 1022 SYNTAX Unsigned32 1023 UNITS "thousand bps" 1024 MAX-ACCESS read-create 1025 STATUS current 1026 DESCRIPTION 1027 "This attribute specifies the minimum LSP bandwidth on 1028 the TE link. This is derived from the union of the 1029 minimum LSP bandwidth of all the component links 1030 associated with the TE link that can be used to carry 1031 live traffic. This value is an estimate in units of 1,000 bits 1032 per second." 1033 REFERENCE 1034 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1035 -- RFC Editor to fill in RFC number that will be assigned to 1036 -- [GMPLS-OSPF] 1037 ::= { teLinkDescriptorEntry 4 } 1039 teLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1040 SYNTAX Unsigned32 1041 UNITS "thousand bps" 1042 MAX-ACCESS read-create 1043 STATUS current 1044 DESCRIPTION 1045 "This attribute specifies the maximum LSP bandwidth at 1046 priority 0 on the TE link. This is the union of the maximum 1047 LSP bandwidth at priority 0 of all the component links within 1048 the TE link that can be used to carry live traffic. This 1049 value is an estimate in units of 1,000 bits per second." 1050 REFERENCE 1051 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1052 -- RFC Editor to fill in RFC number that will be assigned to 1053 -- [GMPLS-OSPF] 1054 ::= { teLinkDescriptorEntry 5 } 1056 teLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1057 SYNTAX Unsigned32 1058 UNITS "thousand bps" 1059 MAX-ACCESS read-create 1060 STATUS current 1061 DESCRIPTION 1062 "This attribute specifies the maximum LSP bandwidth at 1063 priority 1 on the TE link. This is the union of the maximum 1064 LSP bandwidth at priority 1 of all the component links within 1065 the TE link that can be used to carry live traffic. This 1066 value is an estimate in units of 1,000 bits per second." 1067 REFERENCE 1068 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1069 -- RFC Editor to fill in RFC number that will be assigned to 1070 -- [GMPLS-OSPF] 1071 ::= { teLinkDescriptorEntry 6 } 1073 teLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1074 SYNTAX Unsigned32 1075 UNITS "thousand bps" 1076 MAX-ACCESS read-create 1077 STATUS current 1078 DESCRIPTION 1079 "This attribute specifies the maximum LSP bandwidth at 1080 priority 2 on the TE link. This is the union of the maximum 1081 LSP bandwidth at priority 2 of all the component links within 1082 the TE link that can be used to carry live traffic. This 1083 value is an estimate in units of 1,000 bits per second." 1084 REFERENCE 1085 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1086 -- RFC Editor to fill in RFC number that will be assigned to 1087 -- [GMPLS-OSPF] 1088 ::= { teLinkDescriptorEntry 7 } 1090 teLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1091 SYNTAX Unsigned32 1092 UNITS "thousand bps" 1093 MAX-ACCESS read-create 1094 STATUS current 1095 DESCRIPTION 1096 "This attribute specifies the maximum LSP bandwidth at 1097 priority 3 on the TE link. This is the union of the maximum 1098 LSP bandwidth at priority 3 of all the component links within 1099 the TE link that can be used to carry live traffic. This 1100 value is an estimate in units of 1,000 bits per second." 1102 REFERENCE 1103 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1104 -- RFC Editor to fill in RFC number that will be assigned to 1105 -- [GMPLS-OSPF] 1106 ::= { teLinkDescriptorEntry 8 } 1108 teLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1109 SYNTAX Unsigned32 1110 UNITS "thousand bps" 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "This attribute specifies the maximum LSP bandwidth at 1115 priority 4 on the TE link. This is the union of the maximum 1116 LSP bandwidth at priority 4 of all the component links within 1117 the TE link that can be used to carry live traffic. This 1118 value is an estimate in units of 1,000 bits per second." 1119 REFERENCE 1120 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1121 -- RFC Editor to fill in RFC number that will be assigned to 1122 -- [GMPLS-OSPF] 1123 ::= { teLinkDescriptorEntry 9 } 1125 teLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1126 SYNTAX Unsigned32 1127 UNITS "thousand bps" 1128 MAX-ACCESS read-create 1129 STATUS current 1130 DESCRIPTION 1131 "This attribute specifies the maximum LSP bandwidth at 1132 priority 5 on the TE link. This is the union of the maximum 1133 LSP bandwidth at priority 5 of all the component links within 1134 the TE link that can be used to carry live traffic. This 1135 value is an estimate in units of 1,000 bits per second." 1136 REFERENCE 1137 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1138 -- RFC Editor to fill in RFC number that will be assigned to 1139 -- [GMPLS-OSPF] 1140 ::= { teLinkDescriptorEntry 10 } 1142 teLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1143 SYNTAX Unsigned32 1144 UNITS "thousand bps" 1145 MAX-ACCESS read-create 1146 STATUS current 1147 DESCRIPTION 1148 "This attribute specifies the maximum LSP bandwidth at 1149 priority 6 on the TE link. This is the union of the maximum 1150 LSP bandwidth at priority 6 of all the component links within 1151 the TE link that can be used to carry live traffic. This 1152 value is an estimate in units of 1,000 bits per second." 1153 REFERENCE 1154 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1155 -- RFC Editor to fill in RFC number that will be assigned to 1156 -- [GMPLS-OSPF] 1157 ::= { teLinkDescriptorEntry 11 } 1159 teLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1160 SYNTAX Unsigned32 1161 UNITS "thousand bps" 1162 MAX-ACCESS read-create 1163 STATUS current 1164 DESCRIPTION 1165 "This attribute specifies the maximum LSP bandwidth at 1166 priority 7 on the TE link. This is the union of the maximum 1167 LSP bandwidth at priority 7 of all the component links within 1168 the TE link that can be used to carry live traffic. This 1169 value is an estimate in units of 1,000 bits per second." 1170 REFERENCE 1171 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1172 -- RFC Editor to fill in RFC number that will be assigned to 1173 -- [GMPLS-OSPF] 1174 ::= { teLinkDescriptorEntry 12 } 1176 teLinkDescrInterfaceMtu OBJECT-TYPE 1177 SYNTAX Unsigned32 (1..65535) 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "This attribute specifies the interface MTU for the TE 1182 link descriptor." 1183 REFERENCE 1184 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1185 -- RFC Editor to fill in RFC number that will be assigned to 1186 -- [GMPLS-OSPF] 1187 ::= { teLinkDescriptorEntry 13 } 1189 teLinkDescrIndication OBJECT-TYPE 1190 SYNTAX TeLinkSonetSdhIndication 1191 MAX-ACCESS read-create 1192 STATUS current 1193 DESCRIPTION 1194 "This attribute specifies whether this interface supports 1195 Standard or Arbitrary SONET/SDH." 1196 REFERENCE 1197 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1198 -- RFC Editor to fill in RFC number that will be assigned to 1199 -- [GMPLS-OSPF] 1200 ::= { teLinkDescriptorEntry 14 } 1202 teLinkDescrRowStatus OBJECT-TYPE 1203 SYNTAX RowStatus 1204 MAX-ACCESS read-create 1205 STATUS current 1206 DESCRIPTION 1207 "This variable is used to create, modify, and/or 1208 delete a row in this table. No read-create object 1209 can changed if teLinkDescrRowStatus is in active(1) state." 1210 ::= { teLinkDescriptorEntry 15 } 1212 teLinkDescrStorageType OBJECT-TYPE 1213 SYNTAX StorageType 1214 MAX-ACCESS read-create 1215 STATUS current 1216 DESCRIPTION 1217 "The storage type for this conceptual row in the 1218 teLinkDescriptorTable. Conceptual rows having the value 1219 'permanent' need not allow write-access to any 1220 columnar object in the row." 1221 ::= { teLinkDescriptorEntry 16 } 1223 -- End of teLinkDescriptorTable 1225 -- TE Link Shared Risk Link Group Table 1227 teLinkSrlgTable OBJECT-TYPE 1228 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "This table specifies the SRLGs associated with TE links." 1233 ::= { teLinkObjects 3 } 1235 teLinkSrlgEntry OBJECT-TYPE 1236 SYNTAX TeLinkSrlgEntry 1237 MAX-ACCESS not-accessible 1238 STATUS current 1239 DESCRIPTION 1240 "An entry in this table contains information about a 1241 SRLG associated with a TE link. 1242 An ifEntry in the ifTable must exist before a 1243 teLinkSrlgEntry using the same ifIndex is created. 1244 ifType of ifEntry must be teLink(200). 1246 If a TE link entry in the ifTable is destroyed, then so are all 1247 entries in the teLinkSrlgTable that use the ifIndex of 1248 this TE link." 1249 INDEX { ifIndex, teLinkSrlg } 1250 ::= { teLinkSrlgTable 1 } 1252 TeLinkSrlgEntry ::= SEQUENCE { 1253 teLinkSrlg Unsigned32, 1254 teLinkSrlgRowStatus RowStatus, 1255 teLinkSrlgStorageType StorageType 1256 } 1258 teLinkSrlg OBJECT-TYPE 1259 SYNTAX Unsigned32 (0..4294967295) 1260 MAX-ACCESS not-accessible 1261 STATUS current 1262 DESCRIPTION 1263 "This identifies a SRLG supported by the TE link. An SRLG is 1264 identified with a 32 bit number that is unique within an IGP 1265 domain. Zero is a valid SRLG number." 1266 REFERENCE 1267 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1268 -- RFC Editor to fill in RFC number that will be assigned to 1269 -- [GMPLS-OSPF] 1270 ::= { teLinkSrlgEntry 1 } 1272 teLinkSrlgRowStatus OBJECT-TYPE 1273 SYNTAX RowStatus 1274 MAX-ACCESS read-create 1275 STATUS current 1276 DESCRIPTION 1277 "This variable is used to create, modify, and/or 1278 delete a row in this table. No read-create object can 1279 be modified if teLinkSrlgRowStatus is active(1)." 1280 ::= { teLinkSrlgEntry 2 } 1282 teLinkSrlgStorageType OBJECT-TYPE 1283 SYNTAX StorageType 1284 MAX-ACCESS read-create 1285 STATUS current 1286 DESCRIPTION 1287 "The storage type for this conceptual row in the 1288 teLinkSrlgTable. Conceptual rows having the value 1289 'permanent' need not allow write-access to any 1290 columnar object in the row." 1291 ::= { teLinkSrlgEntry 3 } 1293 -- End of teLinkSrlgTable 1294 -- TE Link Bandwidth Table 1296 teLinkBandwidthTable OBJECT-TYPE 1297 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1298 MAX-ACCESS not-accessible 1299 STATUS current 1300 DESCRIPTION 1301 "This table specifies the priority-based bandwidth table 1302 for TE links." 1303 ::= { teLinkObjects 4 } 1305 teLinkBandwidthEntry OBJECT-TYPE 1306 SYNTAX TeLinkBandwidthEntry 1307 MAX-ACCESS not-accessible 1308 STATUS current 1309 DESCRIPTION 1310 "An entry in this table contains information about 1311 the priority-based bandwidth of TE links. An ifEntry in the 1312 ifTable must exist before a teLinkBandwidthEntry using the 1313 same ifIndex is created. ifType of ifEntry must be teLink(200). 1314 If a TE link entry in the ifTable is destroyed, then so are 1315 all entries in the teLinkBandwidthTable that use the ifIndex of 1316 this TE link." 1317 INDEX { ifIndex, teLinkBandwidthPriority } 1318 ::= { teLinkBandwidthTable 1 } 1320 TeLinkBandwidthEntry ::= SEQUENCE { 1321 teLinkBandwidthPriority TeLinkPriority, 1322 teLinkBandwidthUnreserved Unsigned32, 1323 teLinkBandwidthRowStatus RowStatus, 1324 teLinkBandwidthStorageType StorageType 1325 } 1327 teLinkBandwidthPriority OBJECT-TYPE 1328 SYNTAX TeLinkPriority 1329 MAX-ACCESS not-accessible 1330 STATUS current 1331 DESCRIPTION 1332 "This attribute specifies the priority. A value of 0 is valid 1333 as specified in the 'Traffic Engineering Extensions to OSPF 1334 Version 2' document." 1335 REFERENCE 1336 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1337 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1338 -- RFC Editor to fill in RFC number that will be assigned to 1339 -- [GMPLS-OSPF] and [OSPF] 1340 ::= { teLinkBandwidthEntry 1 } 1342 teLinkBandwidthUnreserved OBJECT-TYPE 1343 SYNTAX Unsigned32 1344 UNITS "thousand bps" 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "This attribute specifies the TE link unreserved 1349 bandwidth at priority p. It is the sum of the unreserved 1350 bandwidths at priority p of all component links associated 1351 with the TE link (excludes all links that are strictly 1352 used as protecting links). This value is an estimate in units 1353 of 1,000 bits per second." 1354 REFERENCE 1355 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 1356 -- RFC Editor to fill in RFC number that will be assigned to 1357 -- [BUNDLING] 1358 ::= { teLinkBandwidthEntry 2 } 1360 teLinkBandwidthRowStatus OBJECT-TYPE 1361 SYNTAX RowStatus 1362 MAX-ACCESS read-create 1363 STATUS current 1364 DESCRIPTION 1365 "This variable is used to create, modify, and/or 1366 delete a row in this table. No read-create object 1367 can be modified when teLinkBandwidthRowStatus is active(1)." 1368 ::= { teLinkBandwidthEntry 4 } 1370 teLinkBandwidthStorageType OBJECT-TYPE 1371 SYNTAX StorageType 1372 MAX-ACCESS read-create 1373 STATUS current 1374 DESCRIPTION 1375 "The storage type for this conceptual row in the 1376 teLinkBandwidthTable. Conceptual rows having the value 1377 'permanent' need not allow write-access to any 1378 columnar object in the row." 1379 ::= { teLinkBandwidthEntry 5 } 1381 -- End of teLinkBandwidthTable 1383 -- Component Link Table 1385 componentLinkTable OBJECT-TYPE 1386 SYNTAX SEQUENCE OF ComponentLinkEntry 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "This table specifies the component link parameters." 1391 ::= { teLinkObjects 5 } 1393 componentLinkEntry OBJECT-TYPE 1394 SYNTAX ComponentLinkEntry 1395 MAX-ACCESS not-accessible 1396 STATUS current 1397 DESCRIPTION 1398 "An entry in this table exists for each ifEntry that represents 1399 a component link. An ifEntry must exist in the ifTable 1400 before a componentLinkEntry is created with the 1401 corresponding ifIndex. ifEntry's ifType can be 1402 of any interface type which has been defined for TE Link 1403 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 1404 If an entry representing a component link is destroyed in the 1405 ifTable, then so is the corresponding entry in the 1406 componentLinkTable. The administrative and operational status 1407 values are controlled from the ifEntry." 1408 INDEX { ifIndex } 1409 ::= { componentLinkTable 1 } 1411 ComponentLinkEntry ::= SEQUENCE { 1412 componentLinkMaxResBandwidth Unsigned32, 1413 componentLinkPreferredProtection TeLinkProtection, 1414 componentLinkCurrentProtection TeLinkProtection, 1415 componentLinkRowStatus RowStatus, 1416 componentLinkStorageType StorageType 1417 } 1419 componentLinkMaxResBandwidth OBJECT-TYPE 1420 SYNTAX Unsigned32 1421 UNITS "thousand bps" 1422 MAX-ACCESS read-create 1423 STATUS current 1424 DESCRIPTION 1425 "This attribute specifies the maximum reservable bandwidth on 1426 the component link. This value is an estimate in units of 1427 1,000 bits per second." 1428 REFERENCE 1429 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1430 -- RFC Editor to fill in RFC number that will be assigned to 1431 -- [GMPLS-OSPF] 1432 ::= { componentLinkEntry 1 } 1434 componentLinkPreferredProtection OBJECT-TYPE 1435 SYNTAX TeLinkProtection 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1439 "This attribute specifies whether this component link is 1440 a primary or secondary entity." 1441 ::= { componentLinkEntry 2 } 1443 componentLinkCurrentProtection OBJECT-TYPE 1444 SYNTAX TeLinkProtection 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "This attribute specifies whether this component link is 1449 currently used as primary or secondary link." 1450 ::= { componentLinkEntry 3 } 1452 componentLinkRowStatus OBJECT-TYPE 1453 SYNTAX RowStatus 1454 MAX-ACCESS read-create 1455 STATUS current 1456 DESCRIPTION 1457 "This variable is used to create, modify, and/or 1458 delete a row in this table. No read-create object 1459 can be modified when componentLinkRowStatus is active(1)." 1460 ::= { componentLinkEntry 4 } 1462 componentLinkStorageType OBJECT-TYPE 1463 SYNTAX StorageType 1464 MAX-ACCESS read-create 1465 STATUS current 1466 DESCRIPTION 1467 "The storage type for this conceptual row in the 1468 componentLinkTable. Conceptual rows having the value 1469 'permanent' need not allow write-access to any 1470 columnar object in the row." 1471 ::= { componentLinkEntry 5 } 1473 -- End of componentLinkTable 1475 -- Component Link Descriptor Table 1477 componentLinkDescriptorTable OBJECT-TYPE 1478 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1479 MAX-ACCESS not-accessible 1480 STATUS current 1481 DESCRIPTION 1482 "This table specifies the interface switching capability 1483 descriptors associated with the component links." 1485 ::= { teLinkObjects 6 } 1487 componentLinkDescriptorEntry OBJECT-TYPE 1488 SYNTAX ComponentLinkDescriptorEntry 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "An entry in this table is created for every component link 1493 descriptor. An ifEntry in the ifTable must exist before a 1494 componentLinkDescriptorEntry using the same ifIndex is created. 1495 ifEntry's ifType can be of any interface type which has been 1496 defined for TE Link interworking. Examples include ATM, Frame 1497 Relay, Ethernet, etc. If a component link entry in the ifTable 1498 is destroyed, then so are all entries in the 1499 componentLinkDescriptorTable that use the ifIndex of this 1500 component link." 1501 INDEX { ifIndex, componentLinkDescrId } 1502 ::= { componentLinkDescriptorTable 1 } 1504 ComponentLinkDescriptorEntry ::= SEQUENCE { 1505 componentLinkDescrId Unsigned32, 1506 componentLinkDescrSwitchingCapability TeLinkSwitchingCapability, 1507 componentLinkDescrEncodingType TeLinkEncodingType, 1508 componentLinkDescrMinLspBandwidth Unsigned32, 1509 componentLinkDescrMaxLspBandwidthPrio0 Unsigned32, 1510 componentLinkDescrMaxLspBandwidthPrio1 Unsigned32, 1511 componentLinkDescrMaxLspBandwidthPrio2 Unsigned32, 1512 componentLinkDescrMaxLspBandwidthPrio3 Unsigned32, 1513 componentLinkDescrMaxLspBandwidthPrio4 Unsigned32, 1514 componentLinkDescrMaxLspBandwidthPrio5 Unsigned32, 1515 componentLinkDescrMaxLspBandwidthPrio6 Unsigned32, 1516 componentLinkDescrMaxLspBandwidthPrio7 Unsigned32, 1517 componentLinkDescrInterfaceMtu Unsigned32, 1518 componentLinkDescrIndication TeLinkSonetSdhIndication, 1519 componentLinkDescrRowStatus RowStatus, 1520 componentLinkDescrStorageType StorageType 1521 } 1523 componentLinkDescrId OBJECT-TYPE 1524 SYNTAX Unsigned32 (1..4294967295) 1525 MAX-ACCESS not-accessible 1526 STATUS current 1527 DESCRIPTION 1528 "This object specifies the link descriptor identifier." 1529 ::= { componentLinkDescriptorEntry 1 } 1531 componentLinkDescrSwitchingCapability OBJECT-TYPE 1532 SYNTAX TeLinkSwitchingCapability 1533 MAX-ACCESS read-create 1534 STATUS current 1535 DESCRIPTION 1536 "This attribute specifies link multiplexing capabilities of the 1537 component link." 1538 REFERENCE 1539 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1540 -- RFC Editor to fill in RFC number that will be assigned to 1541 -- [GMPLS-OSPF] 1542 ::= { componentLinkDescriptorEntry 2 } 1544 componentLinkDescrEncodingType OBJECT-TYPE 1545 SYNTAX TeLinkEncodingType 1546 MAX-ACCESS read-create 1547 STATUS current 1548 DESCRIPTION 1549 "This attribute specifies the component link encoding type." 1550 REFERENCE 1551 "Generalized MPLS Signaling Functional Description, RFC 3471" 1552 ::= { componentLinkDescriptorEntry 3 } 1554 componentLinkDescrMinLspBandwidth OBJECT-TYPE 1555 SYNTAX Unsigned32 1556 UNITS "thousand bps" 1557 MAX-ACCESS read-create 1558 STATUS current 1559 DESCRIPTION 1560 "This attribute specifies the minimum LSP bandwidth on 1561 the component link. This value is an estimate 1562 in units of 1,000 bits per second." 1563 REFERENCE 1564 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1565 -- RFC Editor to fill in RFC number that will be assigned to 1566 -- [GMPLS-OSPF] 1567 ::= { componentLinkDescriptorEntry 4 } 1569 componentLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1570 SYNTAX Unsigned32 1571 UNITS "thousand bps" 1572 MAX-ACCESS read-create 1573 STATUS current 1574 DESCRIPTION 1575 "This attribute specifies the maximum LSP bandwidth at 1576 priority 0 on the component link. This value is an estimate 1577 in units of 1,000 bits per second." 1578 REFERENCE 1579 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1580 -- RFC Editor to fill in RFC number that will be assigned to 1581 -- [GMPLS-OSPF] 1582 ::= { componentLinkDescriptorEntry 5 } 1584 componentLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1585 SYNTAX Unsigned32 1586 UNITS "thousand bps" 1587 MAX-ACCESS read-create 1588 STATUS current 1589 DESCRIPTION 1590 "This attribute specifies the maximum LSP bandwidth at 1591 priority 1 on the component link. This value is an estimate 1592 in units of 1,000 bits per second." 1593 REFERENCE 1594 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1595 -- RFC Editor to fill in RFC number that will be assigned to 1596 -- [GMPLS-OSPF] 1597 ::= { componentLinkDescriptorEntry 6 } 1599 componentLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1600 SYNTAX Unsigned32 1601 UNITS "thousand bps" 1602 MAX-ACCESS read-create 1603 STATUS current 1604 DESCRIPTION 1605 "This attribute specifies the maximum LSP bandwidth at 1606 priority 2 on the component link. This value is an estimate 1607 in units of 1,000 bits per second." 1608 REFERENCE 1609 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1610 -- RFC Editor to fill in RFC number that will be assigned to 1611 -- [GMPLS-OSPF] 1612 ::= { componentLinkDescriptorEntry 7 } 1614 componentLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1615 SYNTAX Unsigned32 1616 UNITS "thousand bps" 1617 MAX-ACCESS read-create 1618 STATUS current 1619 DESCRIPTION 1620 "This attribute specifies the maximum LSP bandwidth at 1621 priority 3 on the component link. This value is an estimate 1622 in units of 1,000 bits per second." 1623 REFERENCE 1624 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1625 -- RFC Editor to fill in RFC number that will be assigned to 1626 -- [GMPLS-OSPF] 1627 ::= { componentLinkDescriptorEntry 8 } 1629 componentLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1630 SYNTAX Unsigned32 1631 UNITS "thousand bps" 1632 MAX-ACCESS read-create 1633 STATUS current 1634 DESCRIPTION 1635 "This attribute specifies the maximum LSP bandwidth at 1636 priority 4 on the component link. This value is an estimate 1637 in units of 1,000 bits per second." 1638 REFERENCE 1639 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1640 -- RFC Editor to fill in RFC number that will be assigned to 1641 -- [GMPLS-OSPF] 1642 ::= { componentLinkDescriptorEntry 9 } 1644 componentLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1645 SYNTAX Unsigned32 1646 UNITS "thousand bps" 1647 MAX-ACCESS read-create 1648 STATUS current 1649 DESCRIPTION 1650 "This attribute specifies the maximum LSP bandwidth at 1651 priority 5 on the component link. This value is an estimate 1652 in units of 1,000 bits per second." 1653 REFERENCE 1654 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1655 -- RFC Editor to fill in RFC number that will be assigned to 1656 -- [GMPLS-OSPF] 1657 ::= { componentLinkDescriptorEntry 10 } 1659 componentLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1660 SYNTAX Unsigned32 1661 UNITS "thousand bps" 1662 MAX-ACCESS read-create 1663 STATUS current 1664 DESCRIPTION 1665 "This attribute specifies the maximum LSP bandwidth at 1666 priority 6 on the component link. This value is an estimate 1667 in units of 1,000 bits per second." 1668 REFERENCE 1669 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1670 -- RFC Editor to fill in RFC number that will be assigned to 1671 -- [GMPLS-OSPF] 1672 ::= { componentLinkDescriptorEntry 11 } 1674 componentLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1675 SYNTAX Unsigned32 1676 UNITS "thousand bps" 1677 MAX-ACCESS read-create 1678 STATUS current 1679 DESCRIPTION 1680 "This attribute specifies the maximum LSP bandwidth at 1681 priority 7 on the component link. This value is an estimate 1682 in units of 1,000 bits per second." 1683 REFERENCE 1684 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1685 -- RFC Editor to fill in RFC number that will be assigned to 1686 -- [GMPLS-OSPF] 1687 ::= { componentLinkDescriptorEntry 12 } 1689 componentLinkDescrInterfaceMtu OBJECT-TYPE 1690 SYNTAX Unsigned32 (1..65535) 1691 MAX-ACCESS read-create 1692 STATUS current 1693 DESCRIPTION 1694 "This attribute specifies the interface MTU for the component 1695 link descriptor." 1696 REFERENCE 1697 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1698 -- RFC Editor to fill in RFC number that will be assigned to 1699 -- [GMPLS-OSPF] 1700 ::= { componentLinkDescriptorEntry 13 } 1702 componentLinkDescrIndication OBJECT-TYPE 1703 SYNTAX TeLinkSonetSdhIndication 1704 MAX-ACCESS read-create 1705 STATUS current 1706 DESCRIPTION 1707 "This attribute specifies whether this interface supports 1708 Standard or Arbitrary SONET/SDH." 1709 REFERENCE 1710 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1711 -- RFC Editor to fill in RFC number that will be assigned to 1712 -- [GMPLS-OSPF] 1713 ::= { componentLinkDescriptorEntry 14 } 1715 componentLinkDescrRowStatus OBJECT-TYPE 1716 SYNTAX RowStatus 1717 MAX-ACCESS read-create 1718 STATUS current 1719 DESCRIPTION 1720 "This variable is used to create, modify, and/or 1721 delete a row in this table. No read-create object 1722 can be modified when componentLinkDescrRowStatus 1723 is active(1)." 1724 ::= { componentLinkDescriptorEntry 15 } 1726 componentLinkDescrStorageType OBJECT-TYPE 1727 SYNTAX StorageType 1728 MAX-ACCESS read-create 1729 STATUS current 1730 DESCRIPTION 1731 "The storage type for this conceptual row in the 1732 componentLinkDescriptorTable. Conceptual rows 1733 having the value 'permanent' need not allow write-access 1734 to any columnar object in the row." 1735 ::= { componentLinkDescriptorEntry 16 } 1737 -- End of componentLinkDescriptorTable 1739 -- Component Link Bandwidth Table 1741 componentLinkBandwidthTable OBJECT-TYPE 1742 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1743 MAX-ACCESS not-accessible 1744 STATUS current 1745 DESCRIPTION 1746 "This table specifies the priority-based bandwidth 1747 for component links." 1748 ::= { teLinkObjects 7 } 1750 componentLinkBandwidthEntry OBJECT-TYPE 1751 SYNTAX ComponentLinkBandwidthEntry 1752 MAX-ACCESS not-accessible 1753 STATUS current 1754 DESCRIPTION 1755 "An entry in this table contains information about 1756 the priority-based bandwidth on component links. 1757 An ifEntry in the ifTable must exist before a 1758 componentLinkBandwidthEntry using the same ifIndex is 1759 created. ifEntry's ifType can be of any interface type which 1760 has been defined for TE Link interworking. Examples include 1761 ATM, Frame Relay, Ethernet, etc. If a component link entry in 1762 the ifTable is destroyed, then so are all entries in the 1763 componentLinkBandwidthTable that use the ifIndex of 1764 this component link." 1765 INDEX { ifIndex, componentLinkBandwidthPriority } 1766 ::= { componentLinkBandwidthTable 1 } 1768 ComponentLinkBandwidthEntry ::= SEQUENCE { 1769 componentLinkBandwidthPriority TeLinkPriority, 1770 componentLinkBandwidthUnreserved Unsigned32, 1771 componentLinkBandwidthRowStatus RowStatus, 1772 componentLinkBandwidthStorageType StorageType 1774 } 1776 componentLinkBandwidthPriority OBJECT-TYPE 1777 SYNTAX TeLinkPriority 1778 MAX-ACCESS not-accessible 1779 STATUS current 1780 DESCRIPTION 1781 "This attribute specifies the priority. A value of 0 is valid 1782 as specified in the 'Traffic Engineering Extensions to OSPF 1783 Version 2' document." 1784 REFERENCE 1785 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1786 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1787 -- RFC Editor to fill in RFC number that will be assigned to 1788 -- [GMPLS-OSPF] and [OSPF] 1789 ::= { componentLinkBandwidthEntry 1 } 1791 componentLinkBandwidthUnreserved OBJECT-TYPE 1792 SYNTAX Unsigned32 1793 UNITS "thousand bps" 1794 MAX-ACCESS read-only 1795 STATUS current 1796 DESCRIPTION 1797 "This attribute specifies the component link unreserved 1798 bandwidth at priority p. This value is an estimate 1799 in units of 1,000 bits per second." 1800 REFERENCE 1801 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1802 -- RFC Editor to fill in RFC number that will be assigned to 1803 -- [GMPLS-OSPF] 1804 ::= { componentLinkBandwidthEntry 2 } 1806 componentLinkBandwidthRowStatus OBJECT-TYPE 1807 SYNTAX RowStatus 1808 MAX-ACCESS read-create 1809 STATUS current 1810 DESCRIPTION 1811 "This variable is used to create, modify, and/or 1812 delete a row in this table. No read-create object can 1813 be modified when componentLinkBandwidthRowStatus is 1814 active(1)." 1815 ::= { componentLinkBandwidthEntry 4 } 1817 componentLinkBandwidthStorageType OBJECT-TYPE 1818 SYNTAX StorageType 1819 MAX-ACCESS read-create 1820 STATUS current 1821 DESCRIPTION 1822 "The storage type for this conceptual row in the 1823 componentLinkBandwidthTable. Conceptual rows 1824 having the value 'permanent' need not allow write-access 1825 to any columnar object in the row." 1826 ::= { componentLinkBandwidthEntry 5 } 1828 -- End of componentLinkBandwidthTable 1830 -- Module compliance 1832 teLinkCompliances 1833 OBJECT IDENTIFIER ::= { teLinkConformance 1 } 1835 teLinkGroups 1836 OBJECT IDENTIFIER ::= { teLinkConformance 2 } 1838 teLinkModuleFullCompliance MODULE-COMPLIANCE 1839 STATUS current 1840 DESCRIPTION 1841 "Compliance statement for agents that support read-create 1842 so that both configuration and monitoring of TE links can 1843 be accomplished via this MIB module." 1844 MODULE -- this module 1846 MANDATORY-GROUPS { teLinkGroup, 1847 teLinkBandwidthGroup, 1848 componentLinkBandwidthGroup } 1850 GROUP teLinkSrlgGroup 1851 DESCRIPTION 1852 "This group is mandatory for G-MPLS enabled devices." 1854 GROUP teLinkPscGroup 1855 DESCRIPTION 1856 "This group is mandatory for devices that support 1857 packet switching capability." 1859 GROUP teLinkTdmGroup 1860 DESCRIPTION 1861 "This group is mandatory for devices that support TDM 1862 switching capability." 1864 -- teLinkTable 1866 OBJECT teLinkAddressType 1867 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1868 DESCRIPTION 1869 "Only ipv4(1) and ipv6(2) address types need to be 1870 supported for numbered links. For unnumbered links, the 1871 unknown(0) address type needs to be supported." 1873 OBJECT teLinkLocalIpAddr 1874 SYNTAX InetAddress (SIZE(0|4|16)) 1875 DESCRIPTION 1876 "Size of TE link IP address depends on type of TE link. 1877 TE link IP address size is zero if link is unnumbered, 1878 four if link IP address is IPv4 and sixteen if link IP 1879 address is IPv6." 1881 OBJECT teLinkRemoteIpAddr 1882 SYNTAX InetAddress (SIZE(0|4|16)) 1883 DESCRIPTION 1884 "Size of TE link IP address depends on type of TE link. 1885 TE link IP address size is zero if link is unnumbered, 1886 four if link IP address is IPv4 and sixteen if link IP 1887 address is IPv6." 1889 OBJECT teLinkRowStatus 1890 SYNTAX RowStatus { active(1), notInService(2) } 1891 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1892 createAndGo(4), destroy(6) } 1893 DESCRIPTION 1894 "Support for notReady(3) and createAndWait(5) is 1895 not required." 1897 -- teLinkDescriptorTable 1899 OBJECT teLinkDescrRowStatus 1900 SYNTAX RowStatus { active(1), notInService(2) } 1901 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1902 createAndGo(4), destroy(6) } 1903 DESCRIPTION 1904 "Support for notReady(3) and createAndWait(5) is 1905 not required." 1907 -- teLinkSrlgTable 1909 OBJECT teLinkSrlgRowStatus 1910 SYNTAX RowStatus { active(1), notInService(2) } 1911 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1912 createAndGo(4), destroy(6) } 1913 DESCRIPTION 1914 "Support for notReady(3) and createAndWait(5) is 1915 not required." 1917 -- teLinkBandwidthTable 1919 OBJECT teLinkBandwidthRowStatus 1920 SYNTAX RowStatus { active(1), notInService(2) } 1921 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1922 createAndGo(4), destroy(6) } 1923 DESCRIPTION 1924 "Support for notReady(3) and createAndWait(5) is 1925 not required." 1927 -- componentLinkTable 1929 OBJECT componentLinkRowStatus 1930 SYNTAX RowStatus { active(1), notInService(2) } 1931 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1932 createAndGo(4), destroy(6) } 1933 DESCRIPTION 1934 "Support for notReady(3) and createAndWait(5) is 1935 not required." 1937 -- componentLinkDescriptorTable 1939 OBJECT componentLinkDescrRowStatus 1940 SYNTAX RowStatus { active(1), notInService(2) } 1941 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1942 createAndGo(4), destroy(6) } 1943 DESCRIPTION 1944 "Support for notReady(3) and createAndWait(5) is 1945 not required." 1947 -- componentLinkBandwidthTable 1949 OBJECT componentLinkBandwidthRowStatus 1950 SYNTAX RowStatus { active(1), notInService(2) } 1951 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1952 createAndGo(4), destroy(6) } 1953 DESCRIPTION 1954 "Support for notReady(3) and createAndWait(5) is 1955 not required." 1957 ::= { teLinkCompliances 1 } 1959 teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE 1960 STATUS current 1961 DESCRIPTION 1962 "Compliance statement for agents that support the 1963 monitoring of TE link MIB module." 1964 MODULE -- this module 1965 MANDATORY-GROUPS { teLinkGroup, 1966 teLinkBandwidthGroup, 1967 componentLinkBandwidthGroup } 1969 GROUP teLinkSrlgGroup 1970 DESCRIPTION 1971 "This group is mandatory for G-MPLS enabled devices." 1973 GROUP teLinkPscGroup 1974 DESCRIPTION 1975 "This group is mandatory for devices that support 1976 packet switching capability." 1978 GROUP teLinkTdmGroup 1979 DESCRIPTION 1980 "This group is mandatory for devices that support TDM 1981 switching capability." 1983 -- teLinkTable 1985 OBJECT teLinkAddressType 1986 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1987 MIN-ACCESS read-only 1988 DESCRIPTION 1989 "Only ipv4(1) and ipv6(2) address types need to be 1990 supported for numbered links. For unnumbered links, the 1991 unknown(0) address type needs to be supported." 1993 OBJECT teLinkLocalIpAddr 1994 SYNTAX InetAddress (SIZE(0|4|16)) 1995 MIN-ACCESS read-only 1996 DESCRIPTION 1997 "Size of TE link IP address depends on type of TE link. 1998 TE link IP address size is zero if link is unnumbered, 1999 four if link IP address is IPv4 and sixteen if link IP 2000 address is IPv6." 2002 OBJECT teLinkRemoteIpAddr 2003 SYNTAX InetAddress (SIZE(0|4|16)) 2004 MIN-ACCESS read-only 2005 DESCRIPTION 2006 "Size of TE link IP address depends on type of TE link. 2007 TE link IP address size is zero if link is unnumbered, 2008 four if link IP address is IPv4 and sixteen if link IP 2009 address is IPv6." 2011 OBJECT teLinkProtectionType 2012 MIN-ACCESS read-only 2013 DESCRIPTION 2014 "Write access is not required." 2016 OBJECT teLinkWorkingPriority 2017 MIN-ACCESS read-only 2018 DESCRIPTION 2019 "Write access is not required." 2021 OBJECT teLinkRowStatus 2022 SYNTAX RowStatus { active(1) } 2023 MIN-ACCESS read-only 2024 DESCRIPTION 2025 "Write access is not required and active(1) is the 2026 only status that needs to be supported." 2028 OBJECT teLinkStorageType 2029 MIN-ACCESS read-only 2030 DESCRIPTION 2031 "Write access is not required." 2033 -- teLinkDescriptorTable 2035 OBJECT teLinkDescrSwitchingCapability 2036 MIN-ACCESS read-only 2037 DESCRIPTION 2038 "Write access is not required." 2040 OBJECT teLinkDescrEncodingType 2041 MIN-ACCESS read-only 2042 DESCRIPTION 2043 "Write access is not required." 2045 OBJECT teLinkDescrMinLspBandwidth 2046 MIN-ACCESS read-only 2047 DESCRIPTION 2048 "Write access is not required." 2050 OBJECT teLinkDescrMaxLspBandwidthPrio0 2051 MIN-ACCESS read-only 2052 DESCRIPTION 2053 "Write access is not required." 2055 OBJECT teLinkDescrMaxLspBandwidthPrio1 2056 MIN-ACCESS read-only 2057 DESCRIPTION 2058 "Write access is not required." 2060 OBJECT teLinkDescrMaxLspBandwidthPrio2 2061 MIN-ACCESS read-only 2062 DESCRIPTION 2063 "Write access is not required." 2065 OBJECT teLinkDescrMaxLspBandwidthPrio3 2066 MIN-ACCESS read-only 2067 DESCRIPTION 2068 "Write access is not required." 2070 OBJECT teLinkDescrMaxLspBandwidthPrio4 2071 MIN-ACCESS read-only 2072 DESCRIPTION 2073 "Write access is not required." 2075 OBJECT teLinkDescrMaxLspBandwidthPrio5 2076 MIN-ACCESS read-only 2077 DESCRIPTION 2078 "Write access is not required." 2080 OBJECT teLinkDescrMaxLspBandwidthPrio6 2081 MIN-ACCESS read-only 2082 DESCRIPTION 2083 "Write access is not required." 2085 OBJECT teLinkDescrMaxLspBandwidthPrio7 2086 MIN-ACCESS read-only 2087 DESCRIPTION 2088 "Write access is not required." 2090 OBJECT teLinkDescrRowStatus 2091 SYNTAX RowStatus { active(1) } 2092 MIN-ACCESS read-only 2093 DESCRIPTION 2094 "Write access is not required and active(1) is the 2095 only status that needs to be supported." 2097 OBJECT teLinkDescrStorageType 2098 MIN-ACCESS read-only 2099 DESCRIPTION 2100 "Write access is not required." 2102 -- teLinkSrlgTable 2104 OBJECT teLinkSrlgRowStatus 2105 SYNTAX RowStatus { active(1) } 2106 MIN-ACCESS read-only 2107 DESCRIPTION 2108 "Write access is not required and active(1) is the 2109 only status that needs to be supported." 2111 OBJECT teLinkSrlgStorageType 2112 MIN-ACCESS read-only 2113 DESCRIPTION 2114 "Write access is not required." 2116 -- teLinkBandwidthTable 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 2251 teLinkGroup OBJECT-GROUP 2252 OBJECTS { teLinkAddressType, 2253 teLinkLocalIpAddr, 2254 teLinkRemoteIpAddr, 2255 teLinkMetric, 2256 teLinkProtectionType, 2257 teLinkWorkingPriority, 2258 teLinkResourceClass, 2259 teLinkIncomingIfId, 2260 teLinkOutgoingIfId, 2261 teLinkRowStatus, 2262 teLinkStorageType, 2263 teLinkDescrSwitchingCapability, 2264 teLinkDescrEncodingType, 2265 teLinkDescrRowStatus, 2266 teLinkDescrStorageType, 2267 componentLinkPreferredProtection, 2268 componentLinkCurrentProtection, 2269 componentLinkRowStatus, 2270 componentLinkStorageType, 2271 componentLinkDescrSwitchingCapability, 2272 componentLinkDescrEncodingType, 2273 componentLinkDescrRowStatus, 2274 componentLinkDescrStorageType 2275 } 2277 STATUS current 2278 DESCRIPTION 2279 "Collection of objects needed for the management of 2280 resources associated with TE links." 2281 ::= { teLinkGroups 1 } 2283 teLinkSrlgGroup OBJECT-GROUP 2284 OBJECTS { teLinkSrlgRowStatus, 2285 teLinkSrlgStorageType 2286 } 2288 STATUS current 2289 DESCRIPTION 2290 "Collection of objects needed for the management of 2291 SRLG resources associated with TE links." 2292 ::= { teLinkGroups 2 } 2294 teLinkBandwidthGroup OBJECT-GROUP 2295 OBJECTS { teLinkMaximumReservableBandwidth, 2296 teLinkDescrMaxLspBandwidthPrio0, 2297 teLinkDescrMaxLspBandwidthPrio1, 2298 teLinkDescrMaxLspBandwidthPrio2, 2299 teLinkDescrMaxLspBandwidthPrio3, 2300 teLinkDescrMaxLspBandwidthPrio4, 2301 teLinkDescrMaxLspBandwidthPrio5, 2302 teLinkDescrMaxLspBandwidthPrio6, 2303 teLinkDescrMaxLspBandwidthPrio7, 2304 teLinkBandwidthUnreserved, 2305 teLinkBandwidthRowStatus, 2306 teLinkBandwidthStorageType 2307 } 2309 STATUS current 2310 DESCRIPTION 2311 "Collection of objects needed for the management of 2312 the bandwidth resources associated with TE links and 2313 component links." 2314 ::= { teLinkGroups 3 } 2316 componentLinkBandwidthGroup OBJECT-GROUP 2317 OBJECTS { componentLinkMaxResBandwidth, 2318 componentLinkDescrMaxLspBandwidthPrio0, 2319 componentLinkDescrMaxLspBandwidthPrio1, 2320 componentLinkDescrMaxLspBandwidthPrio2, 2321 componentLinkDescrMaxLspBandwidthPrio3, 2322 componentLinkDescrMaxLspBandwidthPrio4, 2323 componentLinkDescrMaxLspBandwidthPrio5, 2324 componentLinkDescrMaxLspBandwidthPrio6, 2325 componentLinkDescrMaxLspBandwidthPrio7, 2326 componentLinkBandwidthUnreserved, 2327 componentLinkBandwidthRowStatus, 2328 componentLinkBandwidthStorageType 2329 } 2331 STATUS current 2332 DESCRIPTION 2333 "Collection of objects needed for the management of the 2334 bandwidth parameters associated with component links." 2335 ::= { teLinkGroups 4 } 2337 teLinkPscGroup OBJECT-GROUP 2338 OBJECTS { teLinkDescrMinLspBandwidth, 2339 teLinkDescrInterfaceMtu, 2340 componentLinkDescrMinLspBandwidth, 2341 componentLinkDescrInterfaceMtu 2342 } 2344 STATUS current 2345 DESCRIPTION 2346 "Collection of objects needed for devices that are 2347 packet switch capable." 2348 ::= { teLinkGroups 5 } 2350 teLinkTdmGroup OBJECT-GROUP 2351 OBJECTS { teLinkDescrMinLspBandwidth, 2352 teLinkDescrIndication, 2353 componentLinkDescrMinLspBandwidth, 2354 componentLinkDescrIndication 2355 } 2357 STATUS current 2358 DESCRIPTION 2359 "Collection of objects needed for devices that are 2360 TDM switching capable." 2361 ::= { teLinkGroups 6 } 2363 -- End of TE-LINK-MIB 2364 END 2366 10. Intellectual Property Considerations 2368 The IETF takes no position regarding the validity or scope of any 2369 intellectual property or other rights that might be claimed to 2370 pertain to the implementation or use of the technology described in 2371 this document or the extent to which any license under such rights 2372 might or might not be available; neither does it represent that it 2373 has made any effort to identify any such rights. Information on the 2374 IETF's procedures with respect to rights in standards-track and 2375 standards-related documentation can be found in BCP-11. Copies of 2376 claims of rights made available for publication and any assurances of 2377 licenses to be made available, or the result of an attempt made to 2378 obtain a general license or permission for the use of such 2379 proprietary rights by implementers or users of this specification can 2380 be obtained from the IETF Secretariat. 2382 The IETF invites any interested party to bring to its attention any 2383 copyrights, patents or patent applications, or other proprietary 2384 rights which may cover technology that may be required to practice 2385 this standard. Please address the information to the IETF Executive 2386 Director. 2388 11. Security Considerations 2390 There are a number of management objects defined in this MIB module 2391 with a MAX-ACCESS clause of read-write and/or read-create. Such 2392 objects may be considered sensitive or vulnerable in some network 2393 environments. The support for SET operations in a non-secure 2394 environment without proper protection can have a negative effect on 2395 network operations. These are the tables and objects and their 2396 sensitivity/vulnerability: 2398 - All the tables in this MIB module have routing information in 2399 them and so they all have the same security attributes. 2400 Unauthorized changes to attributes of these tables can disrupt 2401 resource allocation in the network. 2403 Some of the readable objects in this MIB module (i.e., objects with a 2404 MAX-ACCESS other than not-accessible) may be considered sensitive or 2405 vulnerable in some network environments. It is thus important to 2406 control even GET and/or NOTIFY access to these objects and possibly 2407 to even encrypt the values of these objects when sending them over 2408 the network via SNMP. These are the tables and objects and their 2409 sensitivity/vulnerability: 2411 - IP address entries in the teLinkTable (teLinkLocalIpAddr and 2412 teLinkRemoteIpAddr) may reveal the internals of a network provider 2413 IP address space. 2415 SNMP versions prior to SNMPv3 did not include adequate security. 2416 Even if the network itself is secure (for example by using IPSec), 2417 even then, there is no control as to who on the secure network is 2418 allowed to access and GET/SET (read/change/create/delete) the objects 2419 in this MIB module. 2421 It is RECOMMENDED that implementers consider the security features as 2422 provided by the SNMPv3 framework (see [RFC3410], section 8), 2423 including full support for the SNMPv3 cryptographic mechanisms (for 2424 authentication and privacy). 2426 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2427 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2428 enable cryptographic security. It is then a customer/operator 2429 responsibility to ensure that the SNMP entity giving access to an 2430 instance of this MIB module is properly configured to give access to 2431 the objects only to those principals (users) that have legitimate 2432 rights to indeed GET or SET (change/create/delete) them. 2434 12. Acknowledgments 2436 The authors would like to acknowledge the contribution of Dmitry 2437 Ryumkin. 2439 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@ieee.org 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 2551 document itself may not be modified in any way, such as by removing 2552 the copyright notice or references to the Internet Society or other 2553 Internet organizations, except as needed for the purpose of 2554 developing Internet standards in which case the procedures for 2555 copyrights defined in the Internet Standards process must be 2556 followed, or as required to translate it into languages other than 2557 English. 2559 The limited permissions granted above are perpetual and will not be 2560 revoked by the Internet Society or its successors or assigns. This 2561 document and the information contained herein is provided on an "AS 2562 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2563 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2564 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2565 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2566 OR FITNESS FOR A PARTICULAR PURPOSE.