idnits 2.17.1 draft-ietf-mpls-telink-mib-07.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 : ---------------------------------------------------------------------------- No issues found here. 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 (May 2004) is 7280 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: 'IEEE' is defined on line 2477, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 2481, but no explicit reference was found in the text == Unused Reference: 'RFC2914' is defined on line 2507, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 2510, but no explicit reference was found in the text == Unused Reference: 'RFC3667' is defined on line 2525, but no explicit reference was found in the text == Unused Reference: 'RFC3668' is defined on line 2528, but no explicit reference was found in the text == Unused Reference: 'HIERARCHY' is defined on line 2541, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE' ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) ** Obsolete normative reference: RFC 3667 (Obsoleted by RFC 3978) ** Obsolete normative reference: RFC 3668 (Obsoleted by RFC 3979) -- 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. 'ROUTING' Summary: 5 errors (**), 0 flaws (~~), 8 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: November 2004 6 Thomas D. Nadeau 7 Cisco Systems 9 Jonathan P. Lang 10 Rincon Networks 12 May 2004 14 Traffic Engineering Link Management Information Base 16 draft-ietf-mpls-telink-mib-07.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 8.3 Applicability of ifRcvAddressTable . . . . . . . . . . . . . . . 13 64 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13 65 10. Intellectual Property Considerations . . . . . . . . . . . . . . 50 66 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51 67 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 52 68 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 52 69 13.1 IANA Considerations for TE-LINK-STD-MIB . . . . . . . . . . . . 52 70 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 71 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 53 72 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 54 73 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54 74 16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 55 76 1. The Internet-Standard Management Framework 78 For a detailed overview of the documents that describe the current 79 Internet-Standard Management Framework, please refer to section 7 of 80 RFC 3410 [RFC3410]. 82 Managed objects are accessed via a virtual information store, termed 83 the Management Information Base or MIB. MIB objects are generally 84 accessed through the Simple Network Management Protocol (SNMP). 85 Objects in the MIB are defined using the mechanisms defined in the 86 Structure of Management Information (SMI). This memo specifies a MIB 87 module that is compliant to the SMIv2, which is described in STD 58, 88 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 89 [RFC2580]. 91 2. Introduction 93 OSPF [RFC3630], Generalized MPLS (GMPLS) [RFC3471] and the Link 94 Management Protocol (LMP) [LMP] use the concept of traffic 95 engineering (TE) links to abstract link properties. The effect of 96 this approach is the reduction of the amount of routing information 97 exchanged in the network, which improves routing scalability. In 98 addition, the use of TE link allows the implementation of new 99 capabilities such as link protection. 101 We present in this document a MIB module that can be used to manage 102 TE links and their extension, the bundled link. This MIB module 103 enables both the configuration and the performance monitoring of TE 104 links and bundled link. 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in RFC 2119, reference 109 [RFC2119]. 111 3. Terminology 113 This document uses terminology from the documents describing link 114 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 116 The link bundling feature is designed to aggregate one or more 117 similar entities between a node pair into a bundled link [BUNDLING]. 118 In the document, those entities are referred to as TE links. A TE 119 link is a subinterface capable of carrying MPLS traffic engineered 120 traffic. A TE Link may be comprised of only one underlying component 121 link. In cases where more than one component links are to be 122 combined, multiple component links should be created with differing 123 priorities to indicate hot-standby or parallel utilization. 125 A bundled link is just another kind of Traffic Engineering (TE) link 126 (see [GMPLS-OSPF]). A link bundle is a subinterface which bounds the 127 traffic of a group of one or more TE links. There should be more than 128 one TE Link in a link bundle, but this is not a requirement. 129 Furthermore, if there are more than one TE link in a link bundle at 130 some time, and at some point later, all but one of the links are 131 deleted, the agent may choose to either delete the link bundle, or it 132 may choose to leave it intact. Traffic counters on a link bundle are 133 cumulative for all subinterfaces which it binds together. 135 4. Feature Checklist 137 The TE Link MIB module (TE-LINK-STD-MIB) is designed to satisfy the 138 following requirements and constraints: 140 - The MIB module supports the management of TE links, including 141 bundled links. 143 - Support is provided for configuration of traffic engineering 144 parameters associated with TE links. 146 - The MIB module is used to monitor the priority-based component 147 link and TE link bandwidth values. 149 5. Outline 151 Configuring bundled links involves the following steps: 153 - Creating a bundled link. 155 - Creating TE links. 157 - Optionally specifying the shared risk link groups associated with 158 the TE links. 160 - Configuring the component links including the bandwidth 161 parameters and associating the component links with the 162 appropriate TE link. 164 - Associating the TE links with the appropriate bundled link. 166 6. Brief Description of MIB Objects 168 Sections 6.1-6.4 describe objects pertaining to TE links while 169 Sections 6.5-6.7 describe objects pertaining to component links. The 170 MIB objects were derived from the link bundling document [BUNDLING]. 172 6.1. teLinkTable 174 This table represents the TE links, including bundled links, and 175 their generic traffic engineering parameters. 177 6.2. teLinkDescriptorTable 179 This table represents the TE link interface switching capability 180 descriptors. 182 6.3. teLinkSrlgTable 184 This table represents the shared risk link groups (SRLGs) associated 185 with TE links. 187 6.4. teLinkBandwidthTable 189 This table specifies the priority-based bandwidth traffic engineering 190 parameters associated with TE links. 192 6.5. componentLinkTable 194 This table enumerates the component links and their generic traffic 195 engineering parameters. 197 6.6. componentLinkDescriptorTable 199 This table enumerates the interface switching capability descriptors 200 that each component link supports. 202 6.7. componentLinkBandwidthTable 204 The component link bandwidth table specifies the priority-based 205 bandwidth values associated with the component links. 207 Component links that belong to the same TE link must be compatible. 208 If these two tables are managed independently, mechanisms should be 209 put in place to ensure consistency between the two tables. TE links 210 that form a bundled link must have compatible traffic engineering 211 parameters (resource class, link metric and protection type). 213 The link descriptors of the teLinkDescriptorTable can be derived from 214 the link descriptors of the componentLinkDescrTable. 216 Some of the bandwidth parameters of the teLinkTable, 217 teLinkDescriptorTable, teLinkBandwidthTable are derived from the 218 bandwidth parameters of the componentLinkTable, 219 componentLinkDescriptorTable and componentLinkBandwidthTable (maximum 220 reservable bandwidth, minimum LSP bandwidth, maximum LSP bandwidth at 221 specified priority and unreserved bandwidth). 223 7. Example of Bundled Link Setup 225 In this section we provide a brief example of using the MIB 226 objects described in section 10 to set up a bundled link. 227 While this example is not meant to illustrate every nuance of the 228 MIB module, it is intended as an aid to understanding some 229 of the key concepts. It is meant to be read after going through the 230 MIB module itself. More details on the use of the ifStackTable 231 to establish relationship between bundled links, TE links and 232 component links are given in Section 8.2. 234 Suppose that one would like to manually create a bundled link 235 out of two 1:1 TE links as depicted on the figure in Section 8.2. 236 Assume that the bundled link is associated with SRLGs 10 and 50. 237 Finally, let the component links be port entity interfaces 238 (lambdas). The following example illustrates which rows and 239 corresponding objects might be created to accomplish this. 241 First, a bundled link entry is created. An ifEntry with the same 242 ifIndex and with ifType teLink needs to be created beforehand. 244 In teLinkTable: 245 { 246 ifIndex = 2, 247 teLinkAddressType = unknown(0), 248 teLinkLocalIpAddr = ''H, 249 teLinkRemoteIpAddr = ''H, 250 teLinkMetric = 5, 251 teLinkProtectionType = dedicated1For1(4), 252 teLinkWorkingPriority = 7, 253 teLinkResourceClass = 3, 254 teLinkIncomingIfId = 0, 255 teLinkOutgoingIfId = 2, 256 teLinkRowStatus = createAndGo(4), 257 teLinkStorageType = nonVolatile(3) 258 } 260 In ifStackTable: 261 { 262 ifStackHigherLayer = 0, 263 ifStackLowerLayer = 2, 264 ifStackStatus = createAndGo(4) 265 } 267 Next, the two TE links are created. 269 In teLinkTable: 270 { 271 ifIndex = 3, 272 teLinkAddressType = unknown(0), 273 teLinkLocalIpAddr = ''H, 274 teLinkRemoteIpAddr = ''H, 275 teLinkMetric = 5, 276 teLinkProtectionType = unprotected(2), 277 teLinkWorkingPriority = 7, 278 teLinkResourceClass = 3, 279 teLinkIncomingIfId = 0, 280 teLinkOutgoingIfId = 3, 281 teLinkRowStatus = createAndGo(4), 282 teLinkStorageType = nonVolatile(3) 284 } 286 In ifStackTable: 287 { 288 ifStackHigherLayer = 2, 289 ifStackLowerLayer = 3, 290 ifStackStatus = createAndGo(4) 291 } 293 In teLinkTable: 294 { 295 ifIndex = 4, 296 teLinkAddressType = unknown(0), 297 teLinkLocalIpAddr = ''H, 298 teLinkRemoteIpAddr = ''H, 299 teLinkMetric = 5, 300 teLinkProtectionType = unprotected(2), 301 teLinkWorkingPriority = 7, 302 teLinkResourceClass = 3, 303 teLinkIncomingIfId = 0, 304 teLinkOutgoingIfId = 4, 305 teLinkRowStatus = createAndGo(4), 306 teLinkStorageType = nonVolatile(3) 307 } 309 In ifStackTable: 310 { 311 ifStackHigherLayer = 2, 312 ifStackLowerLayer = 4, 313 ifStackStatus = createAndGo(4) 314 } 316 We assign SRLGs to the TE links. 318 In the teLinkSrlgTable: 319 { 320 ifIndex = 3, 321 teLinkSrlg = 10, 322 teLinkSrlgRowStatus = createAndGo(4), 323 teLinkSrlgStorageType = nonVolatile(3) 324 } 326 In the teLinkSrlgTable: 327 { 328 ifIndex = 4, 329 teLinkSrlg = 50, 330 teLinkSrlgRowStatus = createAndGo(4), 331 teLinkSrlgStorageType = nonVolatile(3) 333 } 335 The bundled link inherits the SRLG properties from the 336 associated TE links. 338 Next, for each unbundled TE link, a component link is created. 339 An ifEntry with the same ifIndex needs to be created beforehand. 341 In componentLinkTable: 342 { 343 ifIndex = 5, 344 componentLinkPreferredProtection = primary(1), 345 componentLinkRowStatus = createAndGo(4), 346 componentLinkStorageType = nonVolatile(3) 347 } 349 In ifStackTable: 350 { 351 ifStackHigherLayer = 3, 352 ifStackLowerLayer = 5, 353 ifStackStatus = createAndGo(4) 354 } 356 In componentLinkTable: 357 { 358 ifIndex = 6, 359 componentLinkPreferredProtection = secondary(2), 360 componentLinkRowStatus = createAndGo(4) 361 componentLinkStorageType = nonVolatile(3) 362 } 364 In ifStackTable: 365 { 366 ifStackHigherLayer = 4, 367 ifStackLowerLayer = 6, 368 ifStackStatus = createAndGo(4) 369 } 371 In this example, once a component link is added to the 372 componentLinkTable, the associated link descriptors are 373 implicitly added to the componentLinkDescriptorTable. 375 TE link link descriptors are derived from their component link 376 descriptors. 378 Note that the bandwidth attributes in teLinkDescriptorTable, 379 componentLinkDescriptorTable, teLinkBandwidthTable 380 and componentLinkBandwidthTable are maintained by the 381 device according to LSP creation/deletion at different priorities. 382 The values in the teLinkBandwidthTable are an aggregation 383 of the values for the component links of the TE links and 384 the TE links of the bundled link. 386 8. Application of the Interfaces Group to TE Links 388 The Interfaces Group [RFC2863] defines generic managed objects for 389 managing interfaces. This memo contains the media-specific 390 extensions to the Interfaces Group for managing TE Link interfaces 391 as logical interfaces. 393 This memo assumes the interpretation of the Interfaces Group to be 394 in accordance with [RFC2863] which states that the interfaces table 395 (ifTable) contains information on the managed resource's 396 interfaces and that each sub-layer below the internetwork layer of 397 a network interface is considered an interface. Thus, the TE Link 398 interface is represented as an entry in the ifTable. The 399 interrelation of entries in the ifTable is defined by Interfaces 400 Stack Group defined in [RFC2863]. 402 When using TE Link interfaces, the interface stack table might appear 403 as follows: 405 +----------------------------------------+ 406 | TE link-interface ifType = teLink(200) + 407 +----------------------------------------+ 408 | Underlying Layer... + 409 +----------------------------------------+ 411 In the above diagram, "Underlying Layer..." refers to the ifIndex 412 of any interface type, which has been defined for TE Link 413 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 415 8.1. Support of the TE Link Layer by ifTable 417 Some specific interpretations of ifTable for the TE Link layer 418 follow. 420 Object Use for the TE Link layer 422 ifIndex Each TE Link interface is represented by an ifEntry. 424 ifDescr Description of the TE Link interface. 426 ifType The value that is allocated for TE Link is 200 427 [IANAifType]. 429 ifSpeed The total bandwidth in bits per second for use by 430 the TE Link layer. 432 ifPhysAddress Unused. 434 ifAdminStatus This variable indicates the administrator's intent 435 as to whether TE Link should be enabled, disabled, or 436 running in some diagnostic testing mode on this 437 interface. Also see [RFC2863]. 439 ifOperStatus This value reflects the actual or operational 440 status of TE Link on this interface. 442 ifLastChange See [RFC2863]. 444 ifInOctets The number of received octets over the interface, 445 i.e., the number of received octets in all component 446 links associated with the interface. 448 ifOutOctets The number of transmitted octets over the 449 interface, i.e., the number of octets transmitted 450 over all component links associated with the 451 interface. 453 ifInErrors The number of packets dropped due to 454 uncorrectable errors. 456 ifInUnknownProtos 457 The number of received packets discarded during 458 packet header validation. 460 ifOutErrors See [RFC2863]. 462 ifName Textual name (unique on this system) of the 463 interface or an octet string of zero length. 465 ifLinkUpDownTrapEnable 466 Default is disabled (2). 468 ifConnectorPresent 469 Set to false (2). 471 ifHighSpeed See [RFC2863]. 473 ifHCInOctets The 64-bit version of ifInOctets; supported if 474 required by the compliance statements in [RFC2863]. 476 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 477 required by the compliance statements in [RFC2863]. 479 ifAlias The non-volatile 'alias' name for the interface as 480 specified by a network manager. 482 ifCounterDiscontinuityTime 483 See [RFC2863]. 485 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 486 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 487 if encoding type is clear. For other encoding types, traffic 488 counters on a TE link are cumulative for all subinterfaces which it 489 binds together. 491 8.2. Using ifStackTable 493 This section describes by example how to use ifStackTable to 494 represent the relationship of TE links with underlying TE-enabled 495 interfaces. Implementors of the stack table for TE link interfaces 496 should look at the appropriate RFC for the service being stacked 497 on TE links. Examples given below are for illustration purposes 498 only. 500 Example: MPLS is being carried on a bundled TE links. 501 The bundled TE link represents a 1:1 optical 502 transport interface. 504 In this example, the component link is a TE link. The two component 505 links/TE links are grouped in a bundled link. 507 +-------------------------------------------------------------------+ 508 | MPLS interface ifType = mpls(166) | 509 | ifIndex = 1 | 510 +-------------------------------------------------------------------+ 511 | TE link (bundled link) ifType = teLink(200) | 512 | ifIndex = 2 | 513 +--------------------------------+-+--------------------------------+ 514 | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | 515 | ifIndex = 3 | | ifIndex = 4 | 516 +--------------------------------+ +--------------------------------+ 517 | Component link | | Component link | 518 | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | 519 | ifIndex = 5 | | ifIndex = 6 | 520 +--------------------------------+ +--------------------------------+ 522 The assignment of the index values could for example be: 524 ifIndex Description 525 1 mpls (type 166) 526 2 teLink (type 200) 527 3 teLink (type 200) 528 4 teLink (type 200) 529 5 opticalTransport (type 196) 530 6 opticalTransport (type 196) 532 The ifStackTable is then used to show the relationships between the 533 various interfaces. 535 ifStackTable Entries 537 HigherLayer LowerLayer 538 0 1 539 1 2 540 2 3 541 2 4 542 3 5 543 4 6 544 5 0 545 6 0 547 In the case where MPLS is using a single TE link, then 548 the upper TE link layer (link bundle) is not required. 550 +-----------------------------------+ 551 | MPLS interface ifType = mpls(166) | 552 +-----------------------------------+ 553 | TE link ifType = teLink(200) | 554 +-----------------------------------+ 555 | Component link | 556 | ifType = opticalTransport(196) | 557 +-----------------------------------+ 559 The assignment of the index values could for example be: 561 ifIndex Description 562 1 mpls (type 166) 563 2 teLink (type 200) 564 3 opticalTransport (type 196) 566 The ifStackTable is then used to show the relationships between the 567 various interfaces. 569 ifStackTable Entries 571 HigherLayer LowerLayer 572 0 1 573 1 2 574 2 3 575 3 0 577 8.3. Applicability of ifRcvAddressTable 579 TE link interfaces are logical interfaces with no media-level 580 addresses. As such, the ifRcvAddressTable is not applicable 581 to these interfaces. 583 9. TE Link MIB Module Definitions 585 TE-LINK-STD-MIB DEFINITIONS ::= BEGIN 587 IMPORTS 588 MODULE-IDENTITY, OBJECT-TYPE, transmission, Integer32, Unsigned32 589 FROM SNMPv2-SMI 591 MODULE-COMPLIANCE, OBJECT-GROUP 592 FROM SNMPv2-CONF 594 TEXTUAL-CONVENTION, RowStatus, StorageType 595 FROM SNMPv2-TC 597 InterfaceIndexOrZero, ifIndex 598 FROM IF-MIB 600 InetAddressType, InetAddress 601 FROM INET-ADDRESS-MIB; 603 teLinkStdMIB MODULE-IDENTITY 604 LAST-UPDATED "200405141200Z" -- 14 May 2004 12:00:00 EST 605 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 606 CONTACT-INFO 607 " Martin Dubuc 608 Email: mdubuc@ncf.ca 610 Sudheer Dharanikota 611 Email: sudheer@ieee.org 613 Thomas D. Nadeau 614 Email: tnadeau@cisco.com 616 Jonathan P. Lang 617 Email: jplang@ieee.org 618 Comments about this document should be emailed directly to 619 the MPLS working group mailing list at mpls@uu.net." 621 DESCRIPTION 622 "Copyright (C) 2004 The Internet Society. This version of 623 this MIB module is part of RFC XXXX; see the RFC 624 itself for full legal notices. 626 This MIB module contains managed object definitions for 627 MPLS traffic engineering links as defined in 628 'Link Bundling in MPLS Traffic Engineering'." 630 -- Revision history. 631 REVISION 632 "200405141200Z" -- 14 May 2004 12:00:00 EST 633 DESCRIPTION 634 "Initial version published as RFC xxxx (to be assigned by RFC 635 Editor)" 636 ::= { transmission xxx } -- To be assigned by IANA. 637 -- Request to assign 200 which is 638 -- ifType value for teLink. 640 -- Textual Conventions 642 TeLinkBandwidth ::= TEXTUAL-CONVENTION 643 STATUS current 644 DESCRIPTION 645 "This type is used to represent link bandwidth in bps. This 646 value is represented using a 4 octet IEEE floating point 647 format. The floating point representation is not used to 648 represent fractional value but rather to allow 649 specification of large numbers that cannot be expressed 650 with 32-bit integers." 651 REFERENCE 652 "IEEE Standard for Binary Floating-Point Arithmetic, 653 Standard 754-1985" 654 SYNTAX OCTET STRING (SIZE(4)) 656 TeLinkPriority ::= TEXTUAL-CONVENTION 657 DISPLAY-HINT "d" 658 STATUS current 659 DESCRIPTION 660 "This type is used to represent a priority. Each connection is 661 assigned a priority. This priority is used when accounting for 662 bandwidth on TE links or component links, for resource 663 allocation and for rerouting purposes. Value 0 is the highest 664 priority. Value 7 is the lowest priority." 666 SYNTAX Unsigned32 (0..7) 668 TeLinkProtection ::= TEXTUAL-CONVENTION 669 STATUS current 670 DESCRIPTION 671 "Link protection." 672 SYNTAX INTEGER { 673 primary(1), 674 secondary(2) 675 } 677 TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION 678 STATUS current 679 DESCRIPTION 680 "Switching capability as specified in the 'OSPF Extensions in 681 Support of Generalized MPLS' document. The values specified in 682 this document are not contiguous." 683 SYNTAX INTEGER { 684 packetSwitch1(1), 685 packetSwitch2(2), 686 packetSwitch3(3), 687 packetSwitch4(4), 688 layer2Switch(51), 689 tdm(100), 690 lambdaSwitch(150), 691 fiberSwitch(200) 692 } 694 TeLinkEncodingType ::= TEXTUAL-CONVENTION 695 STATUS current 696 DESCRIPTION 697 "Link encoding type as specified in 'GMPLS Signaling Functional 698 Description' document. The values specified in this document are 699 not contiguous." 700 SYNTAX INTEGER { 701 packet(1), 702 ethernet(2), 703 ansiEtsiPdh(3), 704 sdhItuSonetAnsi(5), 705 digitalWrapper(7), 706 lambda(8), 707 fiber(9), 708 fiberChannel(11) 709 } 711 TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION 712 STATUS current 713 DESCRIPTION 714 "This convention is used to indicate whether the interface 715 supports Standard or Arbitrary SONET/SDH. To simplify the 716 mapping process, the values used in this textual convention 717 match the values specified in the interface switching 718 capability specific information field, i.e. 0 for Standard 719 SONET/SDH and 1 for Arbitrary SONET/SDH." 720 REFERENCE 721 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 722 -- RFC Editor to fill in RFC number that will be assigned to 723 -- [GMPLS-OSPF] 724 SYNTAX INTEGER { 725 standard(0), 726 arbitrary(1) 727 } 729 -- Top level components of this MIB module 731 -- Notifications 732 teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } 733 -- Tables, Scalars 734 teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 } 735 -- Conformance 736 teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 } 738 -- TE Link Table 740 teLinkTable OBJECT-TYPE 741 SYNTAX SEQUENCE OF TeLinkEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "This table specifies the grouping of component links into 746 TE links and grouping of TE links into bundled links." 747 ::= { teLinkObjects 1 } 749 teLinkEntry OBJECT-TYPE 750 SYNTAX TeLinkEntry 751 MAX-ACCESS not-accessible 752 STATUS current 753 DESCRIPTION 754 "An entry in this table exists for each ifEntry with an 755 ifType of teLink(200), i.e. for every TE link. An ifEntry 756 in the ifTable must exist before a teLinkEntry is created with 757 the corresponding ifIndex. If a TE link entry in the ifTable is 758 destroyed, then so is the corresponding entry in the 759 teLinkTable. The administrative and operational status values 760 are controlled from the ifEntry." 761 INDEX { ifIndex } 762 ::= { teLinkTable 1 } 764 TeLinkEntry ::= SEQUENCE { 765 teLinkAddressType InetAddressType, 766 teLinkLocalIpAddr InetAddress, 767 teLinkRemoteIpAddr InetAddress, 768 teLinkMetric Unsigned32, 769 teLinkMaximumReservableBandwidth TeLinkBandwidth, 770 teLinkProtectionType INTEGER, 771 teLinkWorkingPriority TeLinkPriority, 772 teLinkResourceClass Unsigned32, 773 teLinkIncomingIfId Integer32, 774 teLinkOutgoingIfId InterfaceIndexOrZero, 775 teLinkRowStatus RowStatus, 776 teLinkStorageType StorageType 777 } 779 teLinkAddressType OBJECT-TYPE 780 SYNTAX InetAddressType 781 MAX-ACCESS read-create 782 STATUS current 783 DESCRIPTION 784 "The type of Internet address for the TE link." 785 ::= { teLinkEntry 1 } 787 teLinkLocalIpAddr OBJECT-TYPE 788 SYNTAX InetAddress 789 MAX-ACCESS read-create 790 STATUS current 791 DESCRIPTION 792 "The local Internet address for numbered links. The type of this 793 address is determined by the value of the teLinkAddressType 794 object. 796 For IPv4 and IPv6 numbered links, this object represents the 797 local IP address associated with the TE link. For an 798 unnumbered link, the local address is of type unknown and this 799 object is set to the zero length string and the 800 teLinkOutgoingIfId object then identifies the unnumbered 801 address. 803 If the TE link is a Forwarding Adjacency (FA), the local 804 IP address is set to the head-end address of the FA-LSP. 806 If ipAddrTable is implemented, this object must have the 807 same value as the ipAdEntAddr object that belongs to the 808 row in ipAddrTable where ipAdEntIfIndex is equal to 809 ifIndex." 811 ::= { teLinkEntry 2 } 813 teLinkRemoteIpAddr OBJECT-TYPE 814 SYNTAX InetAddress 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "The remote Internet address for numbered links. The type of 819 this address is determined by the value of the 820 teLinkAddressType object. 822 The remote IP address associated with the TE link (IPv4 and 823 IPv6 numbered links). For an unnumbered link, the remote 824 address is of type unknown and this object is set to the 825 zero length string and the teLinkIncomingIfId object then 826 identifies the unnumbered address. 828 If the TE link is a Forwarding Adjacency, the remote IP 829 address is set to the tail-end address of the FA-LSP." 830 ::= { teLinkEntry 3 } 832 teLinkMetric OBJECT-TYPE 833 SYNTAX Unsigned32 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "The traffic engineering metric for the TE link is 838 derived from its component links. All component links 839 within the TE link must have the same traffic 840 engineering metric." 841 REFERENCE 842 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 843 -- RFC Editor to fill in RFC number that will be assigned to 844 -- [BUNDLING] 845 ::= { teLinkEntry 4 } 847 teLinkMaximumReservableBandwidth OBJECT-TYPE 848 SYNTAX TeLinkBandwidth 849 UNITS "bps" 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "This attribute specifies the maximum reservable bandwidth on 854 the TE link. This is the union of the maximum reservable 855 bandwidth of all the component links within the 856 TE link that can be used to carry live traffic." 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 5 } 863 teLinkProtectionType OBJECT-TYPE 864 SYNTAX INTEGER { 865 extraTraffic(1), 866 unprotected(2), 867 shared(3), 868 dedicated1For1(4), 869 dedicated1Plus1(5), 870 enhanced(6) 871 } 872 MAX-ACCESS read-create 873 STATUS current 874 DESCRIPTION 875 "This attribute specifies link protection type of the 876 TE link. Description of the different protection types can be 877 found in the 'Routing Extensions in Support of Generalized 878 MPLS' document." 879 REFERENCE 880 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 881 Routing Extensions in Support of Generalized MPLS, RFC xxxx" 882 -- RFC Editor to fill in RFC number that will be assigned to 883 -- [GMPLS-OSPF] and [ROUTING] 884 ::= { teLinkEntry 6 } 886 teLinkWorkingPriority OBJECT-TYPE 887 SYNTAX TeLinkPriority 888 MAX-ACCESS read-create 889 STATUS current 890 DESCRIPTION 891 "This object represents a priority value such that a new 892 connection with a higher priority, i.e. numerically lower than 893 this value, is guaranteed to be setup on a primary link and 894 not on a secondary link." 895 REFERENCE 896 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 897 -- RFC Editor to fill in RFC number that will be assigned to 898 -- [GMPLS-OSPF] 899 ::= { teLinkEntry 7 } 901 teLinkResourceClass OBJECT-TYPE 902 SYNTAX Unsigned32 903 MAX-ACCESS read-create 904 STATUS current 905 DESCRIPTION 906 "This attribute specifies the TE link resource class. 908 The resource class is a 32 bit bitfield. The resource class for 909 a link bundle is derived from the resource class of its 910 TE links. All TE links within a link bundle must have the 911 same resource class. Encoding of the resource class is described 912 in the 'Traffic Engineering Extensions to OSPF Version 2' 913 document." 914 REFERENCE 915 "Link Bundling in MPLS Traffic Engineering, RFC xxxx and 916 Traffic Engineering (TE) Extensions to OSPF Version 2, 917 RFC 3630" 918 -- RFC Editor to fill in RFC number that will be assigned to 919 -- [BUNDLING] 920 ::= { teLinkEntry 8 } 922 teLinkIncomingIfId OBJECT-TYPE 923 SYNTAX Integer32 (0..2147483647) 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "For unnumbered links, the incoming interface is set to the 928 outgoing interface identifier chosen by the neighboring LSR 929 for the reverse link corresponding to this TE link. If the 930 link is numbered, the value of this object is 0 and the 931 address is stored in the teLinkRemoteIpAddr instead." 932 REFERENCE 933 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 934 -- RFC Editor to fill in RFC number that will be assigned to 935 -- [BUNDLING] 936 ::= { teLinkEntry 9 } 938 teLinkOutgoingIfId OBJECT-TYPE 939 SYNTAX InterfaceIndexOrZero 940 MAX-ACCESS read-create 941 STATUS current 942 DESCRIPTION 943 "If the link is unnumbered, the outgoing interface identifier is 944 set to the outgoing interface identifier chosen for the TE link 945 by the advertising LSR. If the link is numbered, the value of 946 this object is 0 and the address is stored in the 947 teLinkLocalIpAddr instead." 948 REFERENCE 949 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 950 -- RFC Editor to fill in RFC number that will be assigned to 951 -- [BUNDLING] 952 ::= { teLinkEntry 10 } 954 teLinkRowStatus OBJECT-TYPE 955 SYNTAX RowStatus 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "This variable is used to create, modify, and/or 960 delete a row in this table. None of the writable objects in 961 a row can be changed if status is active(1)." 962 ::= { teLinkEntry 11 } 964 teLinkStorageType OBJECT-TYPE 965 SYNTAX StorageType 966 MAX-ACCESS read-create 967 STATUS current 968 DESCRIPTION 969 "The storage type for this conceptual row in the 970 teLinkTable. Conceptual rows having the value 971 'permanent' need not allow write-access to any 972 columnar object in the row." 973 ::= { teLinkEntry 12 } 975 -- End of teLinkTable 977 -- TE Link Descriptor Table 979 teLinkDescriptorTable OBJECT-TYPE 980 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 981 MAX-ACCESS not-accessible 982 STATUS current 983 DESCRIPTION 984 "This table specifies the interface switching capability 985 descriptors associated with the TE links." 986 ::= { teLinkObjects 2 } 988 teLinkDescriptorEntry OBJECT-TYPE 989 SYNTAX TeLinkDescriptorEntry 990 MAX-ACCESS not-accessible 991 STATUS current 992 DESCRIPTION 993 "An entry in this table is created for every TE link interface 994 switching capability descriptor. An ifEntry in the ifTable 995 must exist before a teLinkDescriptorEntry using the same 996 ifIndex is created. ifType of ifEntry must be teLink(200). 997 If a TE link entry in the ifTable is destroyed, then so are all 998 entries in the teLinkDescriptorTable that use the ifIndex of 999 this TE link." 1000 INDEX { ifIndex, teLinkDescriptorId } 1001 ::= { teLinkDescriptorTable 1 } 1003 TeLinkDescriptorEntry ::= SEQUENCE { 1004 teLinkDescriptorId Unsigned32, 1005 teLinkDescrSwitchingCapability TeLinkSwitchingCapability, 1006 teLinkDescrEncodingType TeLinkEncodingType, 1007 teLinkDescrMinLspBandwidth TeLinkBandwidth, 1008 teLinkDescrMaxLspBandwidthPrio0 TeLinkBandwidth, 1009 teLinkDescrMaxLspBandwidthPrio1 TeLinkBandwidth, 1010 teLinkDescrMaxLspBandwidthPrio2 TeLinkBandwidth, 1011 teLinkDescrMaxLspBandwidthPrio3 TeLinkBandwidth, 1012 teLinkDescrMaxLspBandwidthPrio4 TeLinkBandwidth, 1013 teLinkDescrMaxLspBandwidthPrio5 TeLinkBandwidth, 1014 teLinkDescrMaxLspBandwidthPrio6 TeLinkBandwidth, 1015 teLinkDescrMaxLspBandwidthPrio7 TeLinkBandwidth, 1016 teLinkDescrInterfaceMtu Unsigned32, 1017 teLinkDescrIndication TeLinkSonetSdhIndication, 1018 teLinkDescrRowStatus RowStatus, 1019 teLinkDescrStorageType StorageType 1020 } 1022 teLinkDescriptorId OBJECT-TYPE 1023 SYNTAX Unsigned32 (1..4294967295) 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "This object specifies the link descriptor identifier." 1028 ::= { teLinkDescriptorEntry 1 } 1030 teLinkDescrSwitchingCapability OBJECT-TYPE 1031 SYNTAX TeLinkSwitchingCapability 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "This attribute specifies interface switching capability of the 1036 TE link, which is derived from its component links." 1037 REFERENCE 1038 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1039 -- RFC Editor to fill in RFC number that will be assigned to 1040 -- [GMPLS-OSPF] 1041 ::= { teLinkDescriptorEntry 2 } 1043 teLinkDescrEncodingType OBJECT-TYPE 1044 SYNTAX TeLinkEncodingType 1045 MAX-ACCESS read-create 1046 STATUS current 1047 DESCRIPTION 1048 "This attribute specifies the TE link encoding type." 1049 REFERENCE 1050 "Generalized MPLS Signaling Functional Description, RFC 3471" 1052 ::= { teLinkDescriptorEntry 3 } 1054 teLinkDescrMinLspBandwidth OBJECT-TYPE 1055 SYNTAX TeLinkBandwidth 1056 UNITS "bps" 1057 MAX-ACCESS read-create 1058 STATUS current 1059 DESCRIPTION 1060 "This attribute specifies the minimum LSP bandwidth on 1061 the TE link. This is derived from the union of the 1062 minimum LSP bandwidth of all the component links 1063 associated with the TE link that can be used to carry 1064 live traffic." 1065 REFERENCE 1066 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1067 -- RFC Editor to fill in RFC number that will be assigned to 1068 -- [GMPLS-OSPF] 1069 ::= { teLinkDescriptorEntry 4 } 1071 teLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1072 SYNTAX TeLinkBandwidth 1073 UNITS "bps" 1074 MAX-ACCESS read-create 1075 STATUS current 1076 DESCRIPTION 1077 "This attribute specifies the maximum LSP bandwidth at 1078 priority 0 on the TE link. This is the union of the maximum 1079 LSP bandwidth at priority 0 of all the component links within 1080 the TE link that can be used to carry live traffic." 1081 REFERENCE 1082 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1083 -- RFC Editor to fill in RFC number that will be assigned to 1084 -- [GMPLS-OSPF] 1085 ::= { teLinkDescriptorEntry 5 } 1087 teLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1088 SYNTAX TeLinkBandwidth 1089 UNITS "bps" 1090 MAX-ACCESS read-create 1091 STATUS current 1092 DESCRIPTION 1093 "This attribute specifies the maximum LSP bandwidth at 1094 priority 1 on the TE link. This is the union of the maximum 1095 LSP bandwidth at priority 1 of all the component links within 1096 the TE link that can be used to carry live traffic." 1097 REFERENCE 1098 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1099 -- RFC Editor to fill in RFC number that will be assigned to 1100 -- [GMPLS-OSPF] 1101 ::= { teLinkDescriptorEntry 6 } 1103 teLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1104 SYNTAX TeLinkBandwidth 1105 UNITS "bps" 1106 MAX-ACCESS read-create 1107 STATUS current 1108 DESCRIPTION 1109 "This attribute specifies the maximum LSP bandwidth at 1110 priority 2 on the TE link. This is the union of the maximum 1111 LSP bandwidth at priority 2 of all the component links within 1112 the TE link that can be used to carry live traffic." 1113 REFERENCE 1114 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1115 -- RFC Editor to fill in RFC number that will be assigned to 1116 -- [GMPLS-OSPF] 1117 ::= { teLinkDescriptorEntry 7 } 1119 teLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1120 SYNTAX TeLinkBandwidth 1121 UNITS "bps" 1122 MAX-ACCESS read-create 1123 STATUS current 1124 DESCRIPTION 1125 "This attribute specifies the maximum LSP bandwidth at 1126 priority 3 on the TE link. This is the union of the maximum 1127 LSP bandwidth at priority 3 of all the component links within 1128 the TE link that can be used to carry live traffic." 1129 REFERENCE 1130 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1131 -- RFC Editor to fill in RFC number that will be assigned to 1132 -- [GMPLS-OSPF] 1133 ::= { teLinkDescriptorEntry 8 } 1135 teLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1136 SYNTAX TeLinkBandwidth 1137 UNITS "bps" 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "This attribute specifies the maximum LSP bandwidth at 1142 priority 4 on the TE link. This is the union of the maximum 1143 LSP bandwidth at priority 4 of all the component links within 1144 the TE link that can be used to carry live traffic." 1145 REFERENCE 1146 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1147 -- RFC Editor to fill in RFC number that will be assigned to 1148 -- [GMPLS-OSPF] 1149 ::= { teLinkDescriptorEntry 9 } 1151 teLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1152 SYNTAX TeLinkBandwidth 1153 UNITS "bps" 1154 MAX-ACCESS read-create 1155 STATUS current 1156 DESCRIPTION 1157 "This attribute specifies the maximum LSP bandwidth at 1158 priority 5 on the TE link. This is the union of the maximum 1159 LSP bandwidth at priority 5 of all the component links within 1160 the TE link that can be used to carry live traffic." 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 10 } 1167 teLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1168 SYNTAX TeLinkBandwidth 1169 UNITS "bps" 1170 MAX-ACCESS read-create 1171 STATUS current 1172 DESCRIPTION 1173 "This attribute specifies the maximum LSP bandwidth at 1174 priority 6 on the TE link. This is the union of the maximum 1175 LSP bandwidth at priority 6 of all the component links within 1176 the TE link that can be used to carry live traffic." 1177 REFERENCE 1178 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1179 -- RFC Editor to fill in RFC number that will be assigned to 1180 -- [GMPLS-OSPF] 1181 ::= { teLinkDescriptorEntry 11 } 1183 teLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1184 SYNTAX TeLinkBandwidth 1185 UNITS "bps" 1186 MAX-ACCESS read-create 1187 STATUS current 1188 DESCRIPTION 1189 "This attribute specifies the maximum LSP bandwidth at 1190 priority 7 on the TE link. This is the union of the maximum 1191 LSP bandwidth at priority 7 of all the component links within 1192 the TE link that can be used to carry live traffic." 1193 REFERENCE 1194 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1195 -- RFC Editor to fill in RFC number that will be assigned to 1196 -- [GMPLS-OSPF] 1197 ::= { teLinkDescriptorEntry 12 } 1199 teLinkDescrInterfaceMtu OBJECT-TYPE 1200 SYNTAX Unsigned32 (1..65535) 1201 MAX-ACCESS read-create 1202 STATUS current 1203 DESCRIPTION 1204 "This attribute specifies the interface MTU for the TE 1205 link descriptor." 1206 REFERENCE 1207 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1208 -- RFC Editor to fill in RFC number that will be assigned to 1209 -- [GMPLS-OSPF] 1210 ::= { teLinkDescriptorEntry 13 } 1212 teLinkDescrIndication OBJECT-TYPE 1213 SYNTAX TeLinkSonetSdhIndication 1214 MAX-ACCESS read-create 1215 STATUS current 1216 DESCRIPTION 1217 "This attribute specifies whether this interface supports 1218 Standard or Arbitrary SONET/SDH." 1219 REFERENCE 1220 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1221 -- RFC Editor to fill in RFC number that will be assigned to 1222 -- [GMPLS-OSPF] 1223 ::= { teLinkDescriptorEntry 14 } 1225 teLinkDescrRowStatus OBJECT-TYPE 1226 SYNTAX RowStatus 1227 MAX-ACCESS read-create 1228 STATUS current 1229 DESCRIPTION 1230 "This variable is used to create, modify, and/or 1231 delete a row in this table. No read-create object 1232 can changed if teLinkDescrRowStatus is in active(1) state." 1233 ::= { teLinkDescriptorEntry 15 } 1235 teLinkDescrStorageType OBJECT-TYPE 1236 SYNTAX StorageType 1237 MAX-ACCESS read-create 1238 STATUS current 1239 DESCRIPTION 1240 "The storage type for this conceptual row in the 1241 teLinkDescriptorTable. Conceptual rows having the value 1242 'permanent' need not allow write-access to any 1243 columnar object in the row." 1245 ::= { teLinkDescriptorEntry 16 } 1247 -- End of teLinkDescriptorTable 1249 -- TE Link Shared Risk Link Group Table 1251 teLinkSrlgTable OBJECT-TYPE 1252 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION 1256 "This table specifies the SRLGs associated with TE links." 1257 ::= { teLinkObjects 3 } 1259 teLinkSrlgEntry OBJECT-TYPE 1260 SYNTAX TeLinkSrlgEntry 1261 MAX-ACCESS not-accessible 1262 STATUS current 1263 DESCRIPTION 1264 "An entry in this table contains information about a 1265 SRLG associated with a TE link. 1266 An ifEntry in the ifTable must exist before a 1267 teLinkSrlgEntry using the same ifIndex is created. 1268 ifType of ifEntry must be teLink(200). 1269 If a TE link entry in the ifTable is destroyed, then so are all 1270 entries in the teLinkSrlgTable that use the ifIndex of 1271 this TE link." 1272 INDEX { ifIndex, teLinkSrlg } 1273 ::= { teLinkSrlgTable 1 } 1275 TeLinkSrlgEntry ::= SEQUENCE { 1276 teLinkSrlg Unsigned32, 1277 teLinkSrlgRowStatus RowStatus, 1278 teLinkSrlgStorageType StorageType 1279 } 1281 teLinkSrlg OBJECT-TYPE 1282 SYNTAX Unsigned32 (0..4294967295) 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "This identifies a SRLG supported by the TE link. An SRLG is 1287 identified with a 32 bit number that is unique within an IGP 1288 domain. Zero is a valid SRLG number." 1289 REFERENCE 1290 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1291 -- RFC Editor to fill in RFC number that will be assigned to 1292 -- [GMPLS-OSPF] 1293 ::= { teLinkSrlgEntry 1 } 1295 teLinkSrlgRowStatus OBJECT-TYPE 1296 SYNTAX RowStatus 1297 MAX-ACCESS read-create 1298 STATUS current 1299 DESCRIPTION 1300 "This variable is used to create, modify, and/or 1301 delete a row in this table. No read-create object can 1302 be modified if teLinkSrlgRowStatus is active(1)." 1303 ::= { teLinkSrlgEntry 2 } 1305 teLinkSrlgStorageType OBJECT-TYPE 1306 SYNTAX StorageType 1307 MAX-ACCESS read-create 1308 STATUS current 1309 DESCRIPTION 1310 "The storage type for this conceptual row in the 1311 teLinkSrlgTable. Conceptual rows having the value 1312 'permanent' need not allow write-access to any 1313 columnar object in the row." 1314 ::= { teLinkSrlgEntry 3 } 1316 -- End of teLinkSrlgTable 1318 -- TE Link Bandwidth Table 1320 teLinkBandwidthTable OBJECT-TYPE 1321 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "This table specifies the priority-based bandwidth table 1326 for TE links." 1327 ::= { teLinkObjects 4 } 1329 teLinkBandwidthEntry OBJECT-TYPE 1330 SYNTAX TeLinkBandwidthEntry 1331 MAX-ACCESS not-accessible 1332 STATUS current 1333 DESCRIPTION 1334 "An entry in this table contains information about 1335 the priority-based bandwidth of TE links. An ifEntry in the 1336 ifTable must exist before a teLinkBandwidthEntry using the 1337 same ifIndex is created. ifType of ifEntry must be teLink(200). 1338 If a TE link entry in the ifTable is destroyed, then so are 1339 all entries in the teLinkBandwidthTable that use the ifIndex of 1340 this TE link." 1341 INDEX { ifIndex, teLinkBandwidthPriority } 1342 ::= { teLinkBandwidthTable 1 } 1344 TeLinkBandwidthEntry ::= SEQUENCE { 1345 teLinkBandwidthPriority TeLinkPriority, 1346 teLinkBandwidthUnreserved TeLinkBandwidth, 1347 teLinkBandwidthRowStatus RowStatus, 1348 teLinkBandwidthStorageType StorageType 1349 } 1351 teLinkBandwidthPriority OBJECT-TYPE 1352 SYNTAX TeLinkPriority 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "This attribute specifies the priority. A value of 0 is valid 1357 as specified in the 'Traffic Engineering Extensions to OSPF 1358 Version 2' document." 1359 REFERENCE 1360 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1361 Traffic Engineering (TE) Extensions to OSPF Version 2, 1362 RFC 3630" 1363 -- RFC Editor to fill in RFC number that will be assigned to 1364 -- [GMPLS-OSPF] 1365 ::= { teLinkBandwidthEntry 1 } 1367 teLinkBandwidthUnreserved OBJECT-TYPE 1368 SYNTAX TeLinkBandwidth 1369 UNITS "bps" 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "This attribute specifies the TE link unreserved 1374 bandwidth at priority p. It is the sum of the unreserved 1375 bandwidths at priority p of all component links associated 1376 with the TE link (excludes all links that are strictly 1377 used as protecting links)." 1378 REFERENCE 1379 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 1380 -- RFC Editor to fill in RFC number that will be assigned to 1381 -- [BUNDLING] 1382 ::= { teLinkBandwidthEntry 2 } 1384 teLinkBandwidthRowStatus OBJECT-TYPE 1385 SYNTAX RowStatus 1386 MAX-ACCESS read-create 1387 STATUS current 1388 DESCRIPTION 1389 "This variable is used to create, modify, and/or 1390 delete a row in this table. No read-create object 1391 can be modified when teLinkBandwidthRowStatus is active(1)." 1392 ::= { teLinkBandwidthEntry 3 } 1394 teLinkBandwidthStorageType OBJECT-TYPE 1395 SYNTAX StorageType 1396 MAX-ACCESS read-create 1397 STATUS current 1398 DESCRIPTION 1399 "The storage type for this conceptual row in the 1400 teLinkBandwidthTable. Conceptual rows having the value 1401 'permanent' need not allow write-access to any 1402 columnar object in the row." 1403 ::= { teLinkBandwidthEntry 4 } 1405 -- End of teLinkBandwidthTable 1407 -- Component Link Table 1409 componentLinkTable OBJECT-TYPE 1410 SYNTAX SEQUENCE OF ComponentLinkEntry 1411 MAX-ACCESS not-accessible 1412 STATUS current 1413 DESCRIPTION 1414 "This table specifies the component link parameters." 1415 ::= { teLinkObjects 5 } 1417 componentLinkEntry OBJECT-TYPE 1418 SYNTAX ComponentLinkEntry 1419 MAX-ACCESS not-accessible 1420 STATUS current 1421 DESCRIPTION 1422 "An entry in this table exists for each ifEntry that represents 1423 a component link. An ifEntry must exist in the ifTable 1424 before a componentLinkEntry is created with the 1425 corresponding ifIndex. ifEntry's ifType can be 1426 of any interface type which has been defined for TE Link 1427 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 1428 If an entry representing a component link is destroyed in the 1429 ifTable, then so is the corresponding entry in the 1430 componentLinkTable. The administrative and operational status 1431 values are controlled from the ifEntry." 1432 INDEX { ifIndex } 1433 ::= { componentLinkTable 1 } 1435 ComponentLinkEntry ::= SEQUENCE { 1436 componentLinkMaxResBandwidth TeLinkBandwidth, 1437 componentLinkPreferredProtection TeLinkProtection, 1438 componentLinkCurrentProtection TeLinkProtection, 1439 componentLinkRowStatus RowStatus, 1440 componentLinkStorageType StorageType 1441 } 1443 componentLinkMaxResBandwidth OBJECT-TYPE 1444 SYNTAX TeLinkBandwidth 1445 UNITS "bps" 1446 MAX-ACCESS read-create 1447 STATUS current 1448 DESCRIPTION 1449 "This attribute specifies the maximum reservable bandwidth on 1450 the component link." 1451 REFERENCE 1452 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1453 -- RFC Editor to fill in RFC number that will be assigned to 1454 -- [GMPLS-OSPF] 1455 ::= { componentLinkEntry 1 } 1457 componentLinkPreferredProtection OBJECT-TYPE 1458 SYNTAX TeLinkProtection 1459 MAX-ACCESS read-create 1460 STATUS current 1461 DESCRIPTION 1462 "This attribute specifies whether this component link is 1463 a primary or secondary entity." 1464 ::= { componentLinkEntry 2 } 1466 componentLinkCurrentProtection OBJECT-TYPE 1467 SYNTAX TeLinkProtection 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "This attribute specifies whether this component link is 1472 currently used as primary or secondary link." 1473 ::= { componentLinkEntry 3 } 1475 componentLinkRowStatus OBJECT-TYPE 1476 SYNTAX RowStatus 1477 MAX-ACCESS read-create 1478 STATUS current 1479 DESCRIPTION 1480 "This variable is used to create, modify, and/or 1481 delete a row in this table. No read-create object 1482 can be modified when componentLinkRowStatus is active(1)." 1484 ::= { componentLinkEntry 4 } 1486 componentLinkStorageType OBJECT-TYPE 1487 SYNTAX StorageType 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "The storage type for this conceptual row in the 1492 componentLinkTable. Conceptual rows having the value 1493 'permanent' need not allow write-access to any 1494 columnar object in the row." 1495 ::= { componentLinkEntry 5 } 1497 -- End of componentLinkTable 1499 -- Component Link Descriptor Table 1501 componentLinkDescriptorTable OBJECT-TYPE 1502 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "This table specifies the interface switching capability 1507 descriptors associated with the component links." 1508 ::= { teLinkObjects 6 } 1510 componentLinkDescriptorEntry OBJECT-TYPE 1511 SYNTAX ComponentLinkDescriptorEntry 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "An entry in this table is created for every component link 1516 descriptor. An ifEntry in the ifTable must exist before a 1517 componentLinkDescriptorEntry using the same ifIndex is created. 1518 ifEntry's ifType can be of any interface type which has been 1519 defined for TE Link interworking. Examples include ATM, Frame 1520 Relay, Ethernet, etc. If a component link entry in the ifTable 1521 is destroyed, then so are all entries in the 1522 componentLinkDescriptorTable that use the ifIndex of this 1523 component link." 1524 INDEX { ifIndex, componentLinkDescrId } 1525 ::= { componentLinkDescriptorTable 1 } 1527 ComponentLinkDescriptorEntry ::= SEQUENCE { 1528 componentLinkDescrId Unsigned32, 1529 componentLinkDescrSwitchingCapability TeLinkSwitchingCapability, 1530 componentLinkDescrEncodingType TeLinkEncodingType, 1531 componentLinkDescrMinLspBandwidth TeLinkBandwidth, 1532 componentLinkDescrMaxLspBandwidthPrio0 TeLinkBandwidth, 1533 componentLinkDescrMaxLspBandwidthPrio1 TeLinkBandwidth, 1534 componentLinkDescrMaxLspBandwidthPrio2 TeLinkBandwidth, 1535 componentLinkDescrMaxLspBandwidthPrio3 TeLinkBandwidth, 1536 componentLinkDescrMaxLspBandwidthPrio4 TeLinkBandwidth, 1537 componentLinkDescrMaxLspBandwidthPrio5 TeLinkBandwidth, 1538 componentLinkDescrMaxLspBandwidthPrio6 TeLinkBandwidth, 1539 componentLinkDescrMaxLspBandwidthPrio7 TeLinkBandwidth, 1540 componentLinkDescrInterfaceMtu Unsigned32, 1541 componentLinkDescrIndication TeLinkSonetSdhIndication, 1542 componentLinkDescrRowStatus RowStatus, 1543 componentLinkDescrStorageType StorageType 1544 } 1546 componentLinkDescrId OBJECT-TYPE 1547 SYNTAX Unsigned32 (1..4294967295) 1548 MAX-ACCESS not-accessible 1549 STATUS current 1550 DESCRIPTION 1551 "This object specifies the link descriptor identifier." 1552 ::= { componentLinkDescriptorEntry 1 } 1554 componentLinkDescrSwitchingCapability OBJECT-TYPE 1555 SYNTAX TeLinkSwitchingCapability 1556 MAX-ACCESS read-create 1557 STATUS current 1558 DESCRIPTION 1559 "This attribute specifies link multiplexing capabilities of the 1560 component link." 1561 REFERENCE 1562 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1563 -- RFC Editor to fill in RFC number that will be assigned to 1564 -- [GMPLS-OSPF] 1565 ::= { componentLinkDescriptorEntry 2 } 1567 componentLinkDescrEncodingType OBJECT-TYPE 1568 SYNTAX TeLinkEncodingType 1569 MAX-ACCESS read-create 1570 STATUS current 1571 DESCRIPTION 1572 "This attribute specifies the component link encoding type." 1573 REFERENCE 1574 "Generalized MPLS Signaling Functional Description, RFC 3471" 1575 ::= { componentLinkDescriptorEntry 3 } 1577 componentLinkDescrMinLspBandwidth OBJECT-TYPE 1578 SYNTAX TeLinkBandwidth 1579 UNITS "bps" 1580 MAX-ACCESS read-create 1581 STATUS current 1582 DESCRIPTION 1583 "This attribute specifies the minimum LSP bandwidth on 1584 the component link." 1585 REFERENCE 1586 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1587 -- RFC Editor to fill in RFC number that will be assigned to 1588 -- [GMPLS-OSPF] 1589 ::= { componentLinkDescriptorEntry 4 } 1591 componentLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1592 SYNTAX TeLinkBandwidth 1593 UNITS "bps" 1594 MAX-ACCESS read-create 1595 STATUS current 1596 DESCRIPTION 1597 "This attribute specifies the maximum LSP bandwidth at 1598 priority 0 on the component link." 1599 REFERENCE 1600 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1601 -- RFC Editor to fill in RFC number that will be assigned to 1602 -- [GMPLS-OSPF] 1603 ::= { componentLinkDescriptorEntry 5 } 1605 componentLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1606 SYNTAX TeLinkBandwidth 1607 UNITS "bps" 1608 MAX-ACCESS read-create 1609 STATUS current 1610 DESCRIPTION 1611 "This attribute specifies the maximum LSP bandwidth at 1612 priority 1 on the component link." 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 6 } 1619 componentLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1620 SYNTAX TeLinkBandwidth 1621 UNITS "bps" 1622 MAX-ACCESS read-create 1623 STATUS current 1624 DESCRIPTION 1625 "This attribute specifies the maximum LSP bandwidth at 1626 priority 2 on the component link." 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 7 } 1634 componentLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1635 SYNTAX TeLinkBandwidth 1636 UNITS "bps" 1637 MAX-ACCESS read-create 1638 STATUS current 1639 DESCRIPTION 1640 "This attribute specifies the maximum LSP bandwidth at 1641 priority 3 on the component link." 1642 REFERENCE 1643 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1644 -- RFC Editor to fill in RFC number that will be assigned to 1645 -- [GMPLS-OSPF] 1646 ::= { componentLinkDescriptorEntry 8 } 1648 componentLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1649 SYNTAX TeLinkBandwidth 1650 UNITS "bps" 1651 MAX-ACCESS read-create 1652 STATUS current 1653 DESCRIPTION 1654 "This attribute specifies the maximum LSP bandwidth at 1655 priority 4 on the component link." 1656 REFERENCE 1657 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1658 -- RFC Editor to fill in RFC number that will be assigned to 1659 -- [GMPLS-OSPF] 1660 ::= { componentLinkDescriptorEntry 9 } 1662 componentLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1663 SYNTAX TeLinkBandwidth 1664 UNITS "thousand bps" 1665 MAX-ACCESS read-create 1666 STATUS current 1667 DESCRIPTION 1668 "This attribute specifies the maximum LSP bandwidth at 1669 priority 5 on the component link." 1670 REFERENCE 1671 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1672 -- RFC Editor to fill in RFC number that will be assigned to 1673 -- [GMPLS-OSPF] 1674 ::= { componentLinkDescriptorEntry 10 } 1676 componentLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1677 SYNTAX TeLinkBandwidth 1678 UNITS "bps" 1679 MAX-ACCESS read-create 1680 STATUS current 1681 DESCRIPTION 1682 "This attribute specifies the maximum LSP bandwidth at 1683 priority 6 on the component link." 1684 REFERENCE 1685 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1686 -- RFC Editor to fill in RFC number that will be assigned to 1687 -- [GMPLS-OSPF] 1688 ::= { componentLinkDescriptorEntry 11 } 1690 componentLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1691 SYNTAX TeLinkBandwidth 1692 UNITS "bps" 1693 MAX-ACCESS read-create 1694 STATUS current 1695 DESCRIPTION 1696 "This attribute specifies the maximum LSP bandwidth at 1697 priority 7 on the component link." 1698 REFERENCE 1699 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1700 -- RFC Editor to fill in RFC number that will be assigned to 1701 -- [GMPLS-OSPF] 1702 ::= { componentLinkDescriptorEntry 12 } 1704 componentLinkDescrInterfaceMtu OBJECT-TYPE 1705 SYNTAX Unsigned32 (1..65535) 1706 MAX-ACCESS read-create 1707 STATUS current 1708 DESCRIPTION 1709 "This attribute specifies the interface MTU for the component 1710 link descriptor." 1711 REFERENCE 1712 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1713 -- RFC Editor to fill in RFC number that will be assigned to 1714 -- [GMPLS-OSPF] 1715 ::= { componentLinkDescriptorEntry 13 } 1717 componentLinkDescrIndication OBJECT-TYPE 1718 SYNTAX TeLinkSonetSdhIndication 1719 MAX-ACCESS read-create 1720 STATUS current 1721 DESCRIPTION 1722 "This attribute specifies whether this interface supports 1723 Standard or Arbitrary SONET/SDH." 1725 REFERENCE 1726 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1727 -- RFC Editor to fill in RFC number that will be assigned to 1728 -- [GMPLS-OSPF] 1729 ::= { componentLinkDescriptorEntry 14 } 1731 componentLinkDescrRowStatus OBJECT-TYPE 1732 SYNTAX RowStatus 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "This variable is used to create, modify, and/or 1737 delete a row in this table. No read-create object 1738 can be modified when componentLinkDescrRowStatus 1739 is active(1)." 1740 ::= { componentLinkDescriptorEntry 15 } 1742 componentLinkDescrStorageType OBJECT-TYPE 1743 SYNTAX StorageType 1744 MAX-ACCESS read-create 1745 STATUS current 1746 DESCRIPTION 1747 "The storage type for this conceptual row in the 1748 componentLinkDescriptorTable. Conceptual rows 1749 having the value 'permanent' need not allow write-access 1750 to any columnar object in the row." 1751 ::= { componentLinkDescriptorEntry 16 } 1753 -- End of componentLinkDescriptorTable 1755 -- Component Link Bandwidth Table 1757 componentLinkBandwidthTable OBJECT-TYPE 1758 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1759 MAX-ACCESS not-accessible 1760 STATUS current 1761 DESCRIPTION 1762 "This table specifies the priority-based bandwidth 1763 for component links." 1764 ::= { teLinkObjects 7 } 1766 componentLinkBandwidthEntry OBJECT-TYPE 1767 SYNTAX ComponentLinkBandwidthEntry 1768 MAX-ACCESS not-accessible 1769 STATUS current 1770 DESCRIPTION 1771 "An entry in this table contains information about 1772 the priority-based bandwidth on component links. 1773 An ifEntry in the ifTable must exist before a 1774 componentLinkBandwidthEntry using the same ifIndex is 1775 created. ifEntry's ifType can be of any interface type which 1776 has been defined for TE Link interworking. Examples include 1777 ATM, Frame Relay, Ethernet, etc. If a component link entry in 1778 the ifTable is destroyed, then so are all entries in the 1779 componentLinkBandwidthTable that use the ifIndex of 1780 this component link." 1781 INDEX { ifIndex, componentLinkBandwidthPriority } 1782 ::= { componentLinkBandwidthTable 1 } 1784 ComponentLinkBandwidthEntry ::= SEQUENCE { 1785 componentLinkBandwidthPriority TeLinkPriority, 1786 componentLinkBandwidthUnreserved TeLinkBandwidth, 1787 componentLinkBandwidthRowStatus RowStatus, 1788 componentLinkBandwidthStorageType StorageType 1789 } 1791 componentLinkBandwidthPriority OBJECT-TYPE 1792 SYNTAX TeLinkPriority 1793 MAX-ACCESS not-accessible 1794 STATUS current 1795 DESCRIPTION 1796 "This attribute specifies the priority. A value of 0 is valid 1797 as specified in the 'Traffic Engineering Extensions to OSPF 1798 Version 2' document." 1799 REFERENCE 1800 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1801 Traffic Engineering (TE) Extensions to OSPF Version 2, 1802 RFC 3630" 1803 -- RFC Editor to fill in RFC number that will be assigned to 1804 -- [GMPLS-OSPF] 1805 ::= { componentLinkBandwidthEntry 1 } 1807 componentLinkBandwidthUnreserved OBJECT-TYPE 1808 SYNTAX TeLinkBandwidth 1809 UNITS "bps" 1810 MAX-ACCESS read-only 1811 STATUS current 1812 DESCRIPTION 1813 "This attribute specifies the component link unreserved 1814 bandwidth at priority p." 1815 REFERENCE 1816 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1817 -- RFC Editor to fill in RFC number that will be assigned to 1818 -- [GMPLS-OSPF] 1819 ::= { componentLinkBandwidthEntry 2 } 1821 componentLinkBandwidthRowStatus OBJECT-TYPE 1822 SYNTAX RowStatus 1823 MAX-ACCESS read-create 1824 STATUS current 1825 DESCRIPTION 1826 "This variable is used to create, modify, and/or 1827 delete a row in this table. No read-create object can 1828 be modified when componentLinkBandwidthRowStatus is 1829 active(1)." 1830 ::= { componentLinkBandwidthEntry 3 } 1832 componentLinkBandwidthStorageType OBJECT-TYPE 1833 SYNTAX StorageType 1834 MAX-ACCESS read-create 1835 STATUS current 1836 DESCRIPTION 1837 "The storage type for this conceptual row in the 1838 componentLinkBandwidthTable. Conceptual rows 1839 having the value 'permanent' need not allow write-access 1840 to any columnar object in the row." 1841 ::= { componentLinkBandwidthEntry 4 } 1843 -- End of componentLinkBandwidthTable 1845 -- Module compliance 1847 teLinkCompliances 1848 OBJECT IDENTIFIER ::= { teLinkConformance 1 } 1850 teLinkGroups 1851 OBJECT IDENTIFIER ::= { teLinkConformance 2 } 1853 teLinkModuleFullCompliance MODULE-COMPLIANCE 1854 STATUS current 1855 DESCRIPTION 1856 "Compliance statement for agents that support read-create 1857 so that both configuration and monitoring of TE links can 1858 be accomplished via this MIB module." 1859 MODULE -- this module 1861 MANDATORY-GROUPS { teLinkGroup, 1862 teLinkBandwidthGroup, 1863 componentLinkBandwidthGroup } 1865 GROUP teLinkSrlgGroup 1866 DESCRIPTION 1867 "This group is mandatory for G-MPLS enabled devices." 1869 GROUP teLinkPscGroup 1870 DESCRIPTION 1871 "This group is mandatory for devices that support 1872 packet switching capability." 1874 GROUP teLinkTdmGroup 1875 DESCRIPTION 1876 "This group is mandatory for devices that support TDM 1877 switching capability." 1879 -- teLinkTable 1881 OBJECT teLinkAddressType 1882 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1883 DESCRIPTION 1884 "Only ipv4(1) and ipv6(2) address types need to be 1885 supported for numbered links. For unnumbered links, the 1886 unknown(0) address type needs to be supported." 1888 OBJECT teLinkLocalIpAddr 1889 SYNTAX InetAddress (SIZE(0|4|16)) 1890 DESCRIPTION 1891 "Size of TE link IP address depends on type of TE link. 1892 TE link IP address size is zero if link is unnumbered, 1893 four if link IP address is IPv4 and sixteen if link IP 1894 address is IPv6." 1896 OBJECT teLinkRemoteIpAddr 1897 SYNTAX InetAddress (SIZE(0|4|16)) 1898 DESCRIPTION 1899 "Size of TE link IP address depends on type of TE link. 1900 TE link IP address size is zero if link is unnumbered, 1901 four if link IP address is IPv4 and sixteen if link IP 1902 address is IPv6." 1904 OBJECT teLinkRowStatus 1905 SYNTAX RowStatus { active(1), notInService(2) } 1906 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1907 createAndGo(4), destroy(6) } 1908 DESCRIPTION 1909 "Support for notReady(3) and createAndWait(5) is 1910 not required." 1912 -- teLinkDescriptorTable 1914 OBJECT teLinkDescrRowStatus 1915 SYNTAX RowStatus { active(1), notInService(2) } 1916 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1917 createAndGo(4), destroy(6) } 1918 DESCRIPTION 1919 "Support for notReady(3) and createAndWait(5) is 1920 not required." 1922 -- teLinkSrlgTable 1924 OBJECT teLinkSrlgRowStatus 1925 SYNTAX RowStatus { active(1), notInService(2) } 1926 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1927 createAndGo(4), destroy(6) } 1928 DESCRIPTION 1929 "Support for notReady(3) and createAndWait(5) is 1930 not required." 1932 -- teLinkBandwidthTable 1934 OBJECT teLinkBandwidthRowStatus 1935 SYNTAX RowStatus { active(1), notInService(2) } 1936 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1937 createAndGo(4), destroy(6) } 1938 DESCRIPTION 1939 "Support for notReady(3) and createAndWait(5) is 1940 not required." 1942 -- componentLinkTable 1944 OBJECT componentLinkRowStatus 1945 SYNTAX RowStatus { active(1), notInService(2) } 1946 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1947 createAndGo(4), destroy(6) } 1948 DESCRIPTION 1949 "Support for notReady(3) and createAndWait(5) is 1950 not required." 1952 -- componentLinkDescriptorTable 1954 OBJECT componentLinkDescrRowStatus 1955 SYNTAX RowStatus { active(1), notInService(2) } 1956 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1957 createAndGo(4), destroy(6) } 1958 DESCRIPTION 1959 "Support for notReady(3) and createAndWait(5) is 1960 not required." 1962 -- componentLinkBandwidthTable 1964 OBJECT componentLinkBandwidthRowStatus 1965 SYNTAX RowStatus { active(1), notInService(2) } 1966 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1967 createAndGo(4), destroy(6) } 1968 DESCRIPTION 1969 "Support for notReady(3) and createAndWait(5) is 1970 not required." 1972 ::= { teLinkCompliances 1 } 1974 teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE 1975 STATUS current 1976 DESCRIPTION 1977 "Compliance statement for agents that support the 1978 monitoring of TE link MIB module." 1979 MODULE -- this module 1981 MANDATORY-GROUPS { teLinkGroup, 1982 teLinkBandwidthGroup, 1983 componentLinkBandwidthGroup } 1985 GROUP teLinkSrlgGroup 1986 DESCRIPTION 1987 "This group is mandatory for G-MPLS enabled devices." 1989 GROUP teLinkPscGroup 1990 DESCRIPTION 1991 "This group is mandatory for devices that support 1992 packet switching capability." 1994 GROUP teLinkTdmGroup 1995 DESCRIPTION 1996 "This group is mandatory for devices that support TDM 1997 switching capability." 1999 -- teLinkTable 2001 OBJECT teLinkAddressType 2002 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 2003 MIN-ACCESS read-only 2004 DESCRIPTION 2005 "Only ipv4(1) and ipv6(2) address types need to be 2006 supported for numbered links. For unnumbered links, the 2007 unknown(0) address type needs to be supported." 2009 OBJECT teLinkLocalIpAddr 2010 SYNTAX InetAddress (SIZE(0|4|16)) 2011 MIN-ACCESS read-only 2012 DESCRIPTION 2013 "Size of TE link IP address depends on type of TE link. 2014 TE link IP address size is zero if link is unnumbered, 2015 four if link IP address is IPv4 and sixteen if link IP 2016 address is IPv6." 2018 OBJECT teLinkRemoteIpAddr 2019 SYNTAX InetAddress (SIZE(0|4|16)) 2020 MIN-ACCESS read-only 2021 DESCRIPTION 2022 "Size of TE link IP address depends on type of TE link. 2023 TE link IP address size is zero if link is unnumbered, 2024 four if link IP address is IPv4 and sixteen if link IP 2025 address is IPv6." 2027 OBJECT teLinkProtectionType 2028 MIN-ACCESS read-only 2029 DESCRIPTION 2030 "Write access is not required." 2032 OBJECT teLinkWorkingPriority 2033 MIN-ACCESS read-only 2034 DESCRIPTION 2035 "Write access is not required." 2037 OBJECT teLinkRowStatus 2038 SYNTAX RowStatus { active(1) } 2039 MIN-ACCESS read-only 2040 DESCRIPTION 2041 "Write access is not required and active(1) is the 2042 only status that needs to be supported." 2044 OBJECT teLinkStorageType 2045 MIN-ACCESS read-only 2046 DESCRIPTION 2047 "Write access is not required." 2049 -- teLinkDescriptorTable 2051 OBJECT teLinkDescrSwitchingCapability 2052 MIN-ACCESS read-only 2053 DESCRIPTION 2054 "Write access is not required." 2056 OBJECT teLinkDescrEncodingType 2057 MIN-ACCESS read-only 2058 DESCRIPTION 2059 "Write access is not required." 2061 OBJECT teLinkDescrMinLspBandwidth 2062 MIN-ACCESS read-only 2063 DESCRIPTION 2064 "Write access is not required." 2066 OBJECT teLinkDescrMaxLspBandwidthPrio0 2067 MIN-ACCESS read-only 2068 DESCRIPTION 2069 "Write access is not required." 2071 OBJECT teLinkDescrMaxLspBandwidthPrio1 2072 MIN-ACCESS read-only 2073 DESCRIPTION 2074 "Write access is not required." 2076 OBJECT teLinkDescrMaxLspBandwidthPrio2 2077 MIN-ACCESS read-only 2078 DESCRIPTION 2079 "Write access is not required." 2081 OBJECT teLinkDescrMaxLspBandwidthPrio3 2082 MIN-ACCESS read-only 2083 DESCRIPTION 2084 "Write access is not required." 2086 OBJECT teLinkDescrMaxLspBandwidthPrio4 2087 MIN-ACCESS read-only 2088 DESCRIPTION 2089 "Write access is not required." 2091 OBJECT teLinkDescrMaxLspBandwidthPrio5 2092 MIN-ACCESS read-only 2093 DESCRIPTION 2094 "Write access is not required." 2096 OBJECT teLinkDescrMaxLspBandwidthPrio6 2097 MIN-ACCESS read-only 2098 DESCRIPTION 2099 "Write access is not required." 2101 OBJECT teLinkDescrMaxLspBandwidthPrio7 2102 MIN-ACCESS read-only 2103 DESCRIPTION 2104 "Write access is not required." 2106 OBJECT teLinkDescrRowStatus 2107 SYNTAX RowStatus { active(1) } 2108 MIN-ACCESS read-only 2109 DESCRIPTION 2110 "Write access is not required and active(1) is the 2111 only status that needs to be supported." 2113 OBJECT teLinkDescrStorageType 2114 MIN-ACCESS read-only 2115 DESCRIPTION 2116 "Write access is not required." 2118 -- teLinkSrlgTable 2120 OBJECT teLinkSrlgRowStatus 2121 SYNTAX RowStatus { active(1) } 2122 MIN-ACCESS read-only 2123 DESCRIPTION 2124 "Write access is not required and active(1) is the 2125 only status that needs to be supported." 2127 OBJECT teLinkSrlgStorageType 2128 MIN-ACCESS read-only 2129 DESCRIPTION 2130 "Write access is not required." 2132 -- teLinkBandwidthTable 2134 OBJECT teLinkBandwidthRowStatus 2135 SYNTAX RowStatus { active(1) } 2136 MIN-ACCESS read-only 2137 DESCRIPTION 2138 "Write access is not required and active(1) is the 2139 only status that needs to be supported." 2141 OBJECT teLinkBandwidthStorageType 2142 MIN-ACCESS read-only 2143 DESCRIPTION 2144 "Write access is not required." 2146 -- componentLinkTable 2148 OBJECT componentLinkMaxResBandwidth 2149 MIN-ACCESS read-only 2150 DESCRIPTION 2151 "Write access is not required." 2153 OBJECT componentLinkPreferredProtection 2154 MIN-ACCESS read-only 2155 DESCRIPTION 2156 "Write access is not required." 2158 OBJECT componentLinkRowStatus 2159 SYNTAX RowStatus { active(1) } 2160 MIN-ACCESS read-only 2161 DESCRIPTION 2162 "Write access is not required and active(1) is the 2163 only status that needs to be supported." 2165 OBJECT componentLinkStorageType 2166 MIN-ACCESS read-only 2167 DESCRIPTION 2168 "Write access is not required." 2170 -- componentLinkDescriptorTable 2172 OBJECT componentLinkDescrSwitchingCapability 2173 MIN-ACCESS read-only 2174 DESCRIPTION 2175 "Write access is not required." 2177 OBJECT componentLinkDescrEncodingType 2178 MIN-ACCESS read-only 2179 DESCRIPTION 2180 "Write access is not required." 2182 OBJECT componentLinkDescrMinLspBandwidth 2183 MIN-ACCESS read-only 2184 DESCRIPTION 2185 "Write access is not required." 2187 OBJECT componentLinkDescrMaxLspBandwidthPrio0 2188 MIN-ACCESS read-only 2189 DESCRIPTION 2190 "Write access is not required." 2192 OBJECT componentLinkDescrMaxLspBandwidthPrio1 2193 MIN-ACCESS read-only 2194 DESCRIPTION 2195 "Write access is not required." 2197 OBJECT componentLinkDescrMaxLspBandwidthPrio2 2198 MIN-ACCESS read-only 2199 DESCRIPTION 2200 "Write access is not required." 2202 OBJECT componentLinkDescrMaxLspBandwidthPrio3 2203 MIN-ACCESS read-only 2204 DESCRIPTION 2205 "Write access is not required." 2207 OBJECT componentLinkDescrMaxLspBandwidthPrio4 2208 MIN-ACCESS read-only 2209 DESCRIPTION 2210 "Write access is not required." 2212 OBJECT componentLinkDescrMaxLspBandwidthPrio5 2213 MIN-ACCESS read-only 2214 DESCRIPTION 2215 "Write access is not required." 2217 OBJECT componentLinkDescrMaxLspBandwidthPrio6 2218 MIN-ACCESS read-only 2219 DESCRIPTION 2220 "Write access is not required." 2222 OBJECT componentLinkDescrMaxLspBandwidthPrio7 2223 MIN-ACCESS read-only 2224 DESCRIPTION 2225 "Write access is not required." 2227 OBJECT componentLinkDescrInterfaceMtu 2228 MIN-ACCESS read-only 2229 DESCRIPTION 2230 "Write access is not required." 2232 OBJECT componentLinkDescrIndication 2233 MIN-ACCESS read-only 2234 DESCRIPTION 2235 "Write access is not required." 2237 OBJECT componentLinkDescrRowStatus 2238 SYNTAX RowStatus { active(1) } 2239 MIN-ACCESS read-only 2240 DESCRIPTION 2241 "Write access is not required and active(1) is the 2242 only status that needs to be supported." 2244 OBJECT componentLinkDescrStorageType 2245 MIN-ACCESS read-only 2246 DESCRIPTION 2247 "Write access is not required." 2249 -- componentLinkBandwidthTable 2251 OBJECT componentLinkBandwidthRowStatus 2252 SYNTAX RowStatus { active(1) } 2253 MIN-ACCESS read-only 2254 DESCRIPTION 2255 "Write access is not required and active(1) is the 2256 only status that needs to be supported." 2258 OBJECT componentLinkBandwidthStorageType 2259 MIN-ACCESS read-only 2260 DESCRIPTION 2261 "Write access is not required." 2263 ::= { teLinkCompliances 2 } 2265 -- Units of conformance 2267 teLinkGroup OBJECT-GROUP 2268 OBJECTS { teLinkAddressType, 2269 teLinkLocalIpAddr, 2270 teLinkRemoteIpAddr, 2271 teLinkMetric, 2272 teLinkProtectionType, 2273 teLinkWorkingPriority, 2274 teLinkResourceClass, 2275 teLinkIncomingIfId, 2276 teLinkOutgoingIfId, 2277 teLinkRowStatus, 2278 teLinkStorageType, 2279 teLinkDescrSwitchingCapability, 2280 teLinkDescrEncodingType, 2281 teLinkDescrRowStatus, 2282 teLinkDescrStorageType, 2283 componentLinkPreferredProtection, 2284 componentLinkCurrentProtection, 2285 componentLinkRowStatus, 2286 componentLinkStorageType, 2287 componentLinkDescrSwitchingCapability, 2288 componentLinkDescrEncodingType, 2289 componentLinkDescrRowStatus, 2290 componentLinkDescrStorageType 2291 } 2293 STATUS current 2294 DESCRIPTION 2295 "Collection of objects needed for the management of 2296 resources associated with TE links." 2297 ::= { teLinkGroups 1 } 2299 teLinkSrlgGroup OBJECT-GROUP 2300 OBJECTS { teLinkSrlgRowStatus, 2301 teLinkSrlgStorageType 2302 } 2304 STATUS current 2305 DESCRIPTION 2306 "Collection of objects needed for the management of 2307 SRLG resources associated with TE links." 2308 ::= { teLinkGroups 2 } 2310 teLinkBandwidthGroup OBJECT-GROUP 2311 OBJECTS { teLinkMaximumReservableBandwidth, 2312 teLinkDescrMaxLspBandwidthPrio0, 2313 teLinkDescrMaxLspBandwidthPrio1, 2314 teLinkDescrMaxLspBandwidthPrio2, 2315 teLinkDescrMaxLspBandwidthPrio3, 2316 teLinkDescrMaxLspBandwidthPrio4, 2317 teLinkDescrMaxLspBandwidthPrio5, 2318 teLinkDescrMaxLspBandwidthPrio6, 2319 teLinkDescrMaxLspBandwidthPrio7, 2320 teLinkBandwidthUnreserved, 2321 teLinkBandwidthRowStatus, 2322 teLinkBandwidthStorageType 2323 } 2325 STATUS current 2326 DESCRIPTION 2327 "Collection of objects needed for the management of 2328 the bandwidth resources associated with TE links and 2329 component links." 2330 ::= { teLinkGroups 3 } 2332 componentLinkBandwidthGroup OBJECT-GROUP 2333 OBJECTS { componentLinkMaxResBandwidth, 2334 componentLinkDescrMaxLspBandwidthPrio0, 2335 componentLinkDescrMaxLspBandwidthPrio1, 2336 componentLinkDescrMaxLspBandwidthPrio2, 2337 componentLinkDescrMaxLspBandwidthPrio3, 2338 componentLinkDescrMaxLspBandwidthPrio4, 2339 componentLinkDescrMaxLspBandwidthPrio5, 2340 componentLinkDescrMaxLspBandwidthPrio6, 2341 componentLinkDescrMaxLspBandwidthPrio7, 2342 componentLinkBandwidthUnreserved, 2343 componentLinkBandwidthRowStatus, 2344 componentLinkBandwidthStorageType 2345 } 2347 STATUS current 2348 DESCRIPTION 2349 "Collection of objects needed for the management of the 2350 bandwidth parameters associated with component links." 2351 ::= { teLinkGroups 4 } 2353 teLinkPscGroup OBJECT-GROUP 2354 OBJECTS { teLinkDescrMinLspBandwidth, 2355 teLinkDescrInterfaceMtu, 2356 componentLinkDescrMinLspBandwidth, 2357 componentLinkDescrInterfaceMtu 2358 } 2360 STATUS current 2361 DESCRIPTION 2362 "Collection of objects needed for devices that are 2363 packet switch capable." 2364 ::= { teLinkGroups 5 } 2366 teLinkTdmGroup OBJECT-GROUP 2367 OBJECTS { teLinkDescrMinLspBandwidth, 2368 teLinkDescrIndication, 2369 componentLinkDescrMinLspBandwidth, 2370 componentLinkDescrIndication 2371 } 2373 STATUS current 2374 DESCRIPTION 2375 "Collection of objects needed for devices that are 2376 TDM switching capable." 2377 ::= { teLinkGroups 6 } 2379 -- End of TE-LINK-STD-MIB 2380 END 2382 10. Intellectual Property Considerations 2384 The IETF takes no position regarding the validity or scope of any 2385 intellectual property or other rights that might be claimed to 2386 pertain to the implementation or use of the technology described in 2387 this document or the extent to which any license under such rights 2388 might or might not be available; neither does it represent that it 2389 has made any effort to identify any such rights. Information on the 2390 IETF's procedures with respect to rights in standards-track and 2391 standards-related documentation can be found in BCP-11. Copies of 2392 claims of rights made available for publication and any assurances of 2393 licenses to be made available, or the result of an attempt made to 2394 obtain a general license or permission for the use of such 2395 proprietary rights by implementers or users of this specification can 2396 be obtained from the IETF Secretariat. 2398 The IETF invites any interested party to bring to its attention any 2399 copyrights, patents or patent applications, or other proprietary 2400 rights which may cover technology that may be required to practice 2401 this standard. Please address the information to the IETF Executive 2402 Director. 2404 By submitting this Internet Draft, we certify that any applicable 2405 patent or other IPR claims of which we are aware have been disclosed, 2406 and ant of which we become aware will be disclosed, in accordance 2407 with RFC 3668. 2409 11. Security Considerations 2411 There are a number of management objects defined in this MIB module 2412 with a MAX-ACCESS clause of read-write and/or read-create. Such 2413 objects may be considered sensitive or vulnerable in some network 2414 environments. The support for SET operations in a non-secure 2415 environment without proper protection can have a negative effect on 2416 network operations. These are the tables and objects and their 2417 sensitivity/vulnerability: 2419 - All the tables in this MIB module have routing information in 2420 them and so they all have the same security attributes. 2421 Unauthorized changes to attributes of these tables can disrupt 2422 resource allocation in the network. 2424 Some of the readable objects in this MIB module (i.e., objects with a 2425 MAX-ACCESS other than not-accessible) may be considered sensitive or 2426 vulnerable in some network environments. It is thus important to 2427 control even GET and/or NOTIFY access to these objects and possibly 2428 to even encrypt the values of these objects when sending them over 2429 the network via SNMP. These are the tables and objects and their 2430 sensitivity/vulnerability: 2432 - IP address entries in the teLinkTable (teLinkLocalIpAddr and 2433 teLinkRemoteIpAddr) may reveal the internals of a network provider 2434 IP address space. 2436 SNMP versions prior to SNMPv3 did not include adequate security. 2437 Even if the network itself is secure (for example by using IPSec), 2438 even then, there is no control as to who on the secure network is 2439 allowed to access and GET/SET (read/change/create/delete) the objects 2440 in this MIB module. 2442 It is RECOMMENDED that implementers consider the security features as 2443 provided by the SNMPv3 framework (see [RFC3410], section 8), 2444 including full support for the SNMPv3 cryptographic mechanisms (for 2445 authentication and privacy). 2447 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2448 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2449 enable cryptographic security. It is then a customer/operator 2450 responsibility to ensure that the SNMP entity giving access to an 2451 instance of this MIB module is properly configured to give access to 2452 the objects only to those principals (users) that have legitimate 2453 rights to indeed GET or SET (change/create/delete) them. 2455 12. Acknowledgments 2457 The authors would like to acknowledge the contribution of Dmitry 2458 Ryumkin. 2460 13. IANA Considerations 2462 The following "IANA Considerations" subsection requests IANA for a 2463 new assignment. New assignments can only be made via Standards Action 2464 as specified in [RFC2434]. 2466 13.1. IANA Considerations for TE-LINK-STD-MIB 2468 TE-LINK-STD-MIB should be rooted under the transmission subtree. The 2469 IANA is requested to assign { transmission TBD } to the TE-LINK-STD- 2470 MIB module specified in this document. The IANA is requested to use 2471 same number as the telink ifType. 2473 14. References 2475 14.1. Normative References 2477 [IEEE] IEEE, "IEEE Standard for Binary Floating-Point 2478 Arithmetic", Standard 754-1985, 1985 2479 (ISBN 1-5593-7653-8). 2481 [RFC2026] Bradner, S., "The Internet Standards Process - 2482 Revision 3", RFC 2026, October 1996. 2484 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2485 Requirement Levels", BCP 14, RFC 2119, March 1997. 2487 [RFC2434] Narten, T., Alverstrand, H., "Guidelines for Writing 2488 an IANA Considerations Section in RFCs", RFC 2434, 2489 October 1998. 2491 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2492 J., Rose, M., and S. Waldbusser, "Structure of 2493 Management Information Version 2 (SMIv2)", STD 58, 2494 RFC 2578, April 1999. 2496 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2497 J., Rose, M., and S. Waldbusser, "Textual Conventions 2498 for SMIv2", STD 58, RFC 2579, April 1999. 2500 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2501 J., Rose, M., and Waldbusser, S., "Conformance 2502 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2504 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2505 Group MIB", RFC 2863, June 2000. 2507 [RFC2914] Floyd, S., "Congestion Control Principles", RFC 2914, 2508 September 2000. 2510 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 2511 Shoenwaelder, J., "Textual Conventions for Internet 2512 Network Addresses", RFC 3291, May 2002. 2514 [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., 2515 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2516 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2517 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2518 "Generalized MPLS Signaling Functional Description", 2519 RFC 3471, January 2003. 2521 [RFC3630] Katz, D., Kompella, K., and Yeung, D., "Traffic 2522 Engineering (TE) Extensions to OSPF Version 2", 2523 RFC 3630, September 2003. 2525 [RFC3667] Bradner, S., "IETF Rights in Contributions", 2526 RFC 3667, February 2004. 2528 [RFC3668] Bradner, S., "Intellectual Property Rights in IETF 2529 Technology", RFC 3668, February 2004. 2531 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2532 "Link Bundling in MPLS Traffic Engineering", 2533 Internet Draft , 2534 July 2002. 2536 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2537 Extensions in Support of Generalized MPLS", Internet 2538 Draft , 2539 October 2003. 2541 [HIERARCHY] Kompella, K., Rekhter, Y., "LSP Hierarchy with 2542 Generalized MPLS TE", Internet Draft 2543 , 2544 September 2002. 2546 [IANAifType] "IANAifType MIB Module", 2547 http://www.iana.org/assignments/ianaiftype-mib. 2549 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2550 Rekhter, Y., Berger, L., Saha, D., 2551 Basak, D., Sandick, H., Zinin, A., 2552 Rajagopalan, B., and Ramamoorthi, S., 2553 "Link Management Protocol", 2554 Internet Draft , 2555 October 2003. 2557 [ROUTING] Kompella, K., Rekhter, Y., "Routing Extensions in 2558 Support of Generalized MPLS", Internet Draft 2559 , October 2003. 2561 14.2. Informative References 2563 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2564 "Introduction and Applicability Statements for 2565 Internet-Standard Management Framework", RFC 3410, 2566 December 2002. 2568 [GMPLS-ARCH] Ashwood-Smith, P., Awduche, D., 2569 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2570 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2571 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2572 Lang, J., Liaw, Mannie, E., F., Nadeau, T., Ong, L., 2573 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2574 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2575 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2576 Zinin, A., "Generalized Multi-Protocol Label Switching 2577 (GMPLS) Architecture", Internet Draft 2578 , 2579 May 2003. 2581 15. Authors' Addresses 2583 Martin Dubuc Thomas D. Nadeau 2584 Email: mdubuc@ncf.ca Cisco Systems, Inc. 2585 300 Apollo Drive 2586 Chelmsford, MA 01824 2587 Phone: +1-978-244-3051 2588 Email: tnadeau@cisco.com 2590 Sudheer Dharanikota Jonathan P. Lang 2591 Email: sudheer@ieee.org Rincon Networks, Inc. 2592 110 El Paseo 2593 Santa Barbara, CA 93101 2594 Email: jplang@ieee.org 2596 16. Full Copyright Statement 2598 Copyright (C) The Internet Society (2004). This document is subject 2599 to the rights, licenses and restrictions contained in BCP 78, and 2600 except as set forth therein, the authors retain all their rights. 2602 This document and translations of it may be copied and furnished to 2603 others, and derivative works that comment on or otherwise explain it 2604 or assist in its implementation may be prepared, copied, published 2605 and distributed, in whole or in part, without restriction of any 2606 kind, provided that the above copyright notice and this paragraph are 2607 included on all such copies and derivative works. However, this 2608 document itself may not be modified in any way, such as by removing 2609 the copyright notice or references to the Internet Society or other 2610 Internet organizations, except as needed for the purpose of 2611 developing Internet standards in which case the procedures for 2612 copyrights defined in the Internet Standards process must be 2613 followed, or as required to translate it into languages other than 2614 English. 2616 The limited permissions granted above are perpetual and will not be 2617 revoked by the Internet Society or its successors or assigns. This 2618 document and the information contained herein is provided on an "AS 2619 IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 2620 IS SPONSORED BY (IF ANY),THE INTERNET SOCIETY AND THE INTERNET 2621 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2622 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2623 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2624 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.