idnits 2.17.1 draft-ietf-mpls-telink-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 2004) is 7377 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 2443, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 2466, but no explicit reference was found in the text == Unused Reference: 'HIERARCHY' is defined on line 2487, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE' ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'HIERARCHY' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAifType' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'ROUTING' Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Martin Dubuc 2 Internet Draft 3 Category: Standards Track Sudheer Dharanikota 4 Expires: August 2004 5 Thomas D. Nadeau 6 Cisco Systems 8 Jonathan P. Lang 9 Rincon Networks 11 February 2004 13 Traffic Engineering Link Management Information Base 15 draft-ietf-mpls-telink-mib-06.txt 17 Status of this Memo 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC 2026. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that other 24 groups may also distribute working documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects for modeling TE links as 42 described in the Link Bundling in MPLS Traffic Engineering document. 44 Table of Contents 45 1. The Internet-Standard Management Framework . . . . . . . . . . . 2 46 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 47 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3 49 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 50 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4 51 6.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4 52 6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4 53 6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4 54 6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4 55 6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5 56 6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5 57 6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5 58 7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5 59 8. Application of the Interfaces Group to TE Links . . . . . . . . . 9 60 8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9 61 8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11 62 8.3 Applicability of ifRcvAddressTable . . . . . . . . . . . . . . . 13 63 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13 64 10. Intellectual Property Considerations . . . . . . . . . . . . . . 50 65 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51 66 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 52 67 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 68 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 53 69 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53 70 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54 71 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54 73 1. The Internet-Standard Management Framework 75 For a detailed overview of the documents that describe the current 76 Internet-Standard Management Framework, please refer to section 7 of 77 RFC 3410 [RFC3410]. 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. MIB objects are generally 81 accessed through the Simple Network Management Protocol (SNMP). 82 Objects in the MIB are defined using the mechanisms defined in the 83 Structure of Management Information (SMI). This memo specifies a MIB 84 module that is compliant to the SMIv2, which is described in STD 58, 85 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 86 [RFC2580]. 88 2. Introduction 90 OSPF [OSPF], Generalized MPLS (GMPLS) [RFC3471] and the Link 91 Management Protocol (LMP) [LMP] use the concept of traffic 92 engineering (TE) links to abstract link properties. The effect of 93 this approach is the reduction of the amount of routing information 94 exchanged in the network, which improves routing scalability. In 95 addition, the use of TE link allows the implementation of new 96 capabilities such as link protection. 98 We present in this document a MIB module that can be used to manage 99 TE links and their extension, the bundled link. This MIB module 100 enables both the configuration and the performance monitoring of TE 101 links and bundled link. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119, reference 106 [RFC2119]. 108 3. Terminology 110 This document uses terminology from the documents describing link 111 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 113 The link bundling feature is designed to aggregate one or more 114 similar entities between a node pair into a bundled link [BUNDLING]. 115 In the document, those entities are referred to as TE links. A TE 116 link is a subinterface capable of carrying MPLS traffic engineered 117 traffic. A TE Link may be comprised of only one underlying component 118 link. In cases where more than one component links are to be 119 combined, multiple component links should be created with differing 120 priorities to indicate hot-standby or parallel utilization. 122 A bundled link is just another kind of Traffic Engineering (TE) link 123 (see [GMPLS-OSPF]). A link bundle is a subinterface which bounds the 124 traffic of a group of one or more TE links. There should be more than 125 one TE Link in a link bundle, but this is not a requirement. 126 Furthermore, if there are more than one TE link in a link bundle at 127 some time, and at some point later, all but one of the links are 128 deleted, the agent may choose to either delete the link bundle, or it 129 may choose to leave it intact. Traffic counters on a link bundle are 130 cumulative for all subinterfaces which it binds together. 132 4. Feature Checklist 134 The TE Link MIB module (TE-LINK-STD-MIB) is designed to satisfy the 135 following requirements and constraints: 137 - The MIB module supports the management of TE links, including 138 bundled links. 140 - Support is provided for configuration of traffic engineering 141 parameters associated with TE links. 143 - The MIB module is used to monitor the priority-based component 144 link and TE link bandwidth values. 146 5. Outline 148 Configuring bundled links involves the following steps: 150 - Creating a bundled link. 152 - Creating TE links. 154 - Optionally specifying the shared risk link groups associated with 155 the TE links. 157 - Configuring the component links including the bandwidth 158 parameters and associating the component links with the 159 appropriate TE link. 161 - Associating the TE links with the appropriate bundled link. 163 6. Brief Description of MIB Objects 165 Sections 6.1-6.4 describe objects pertaining to TE links while 166 Sections 6.5-6.7 describe objects pertaining to component links. The 167 MIB objects were derived from the link bundling document [BUNDLING]. 169 6.1. teLinkTable 171 This table represents the TE links, including bundled links, and 172 their generic traffic engineering parameters. 174 6.2. teLinkDescriptorTable 176 This table represents the TE link interface switching capability 177 descriptors. 179 6.3. teLinkSrlgTable 181 This table represents the shared risk link groups (SRLGs) associated 182 with TE links. 184 6.4. teLinkBandwidthTable 186 This table specifies the priority-based bandwidth traffic engineering 187 parameters associated with TE links. 189 6.5. componentLinkTable 191 This table enumerates the component links and their generic traffic 192 engineering parameters. 194 6.6. componentLinkDescriptorTable 196 This table enumerates the interface switching capability descriptors 197 that each component link supports. 199 6.7. componentLinkBandwidthTable 201 The component link bandwidth table specifies the priority-based 202 bandwidth values associated with the component links. 204 Component links that belong to the same TE link must be compatible. 205 If these two tables are managed independently, mechanisms should be 206 put in place to ensure consistency between the two tables. TE links 207 that form a bundled link must have compatible traffic engineering 208 parameters (resource class, link metric and protection type). 210 The link descriptors of the teLinkDescriptorTable can be derived from 211 the link descriptors of the componentLinkDescrTable. 213 Some of the bandwidth parameters of the teLinkTable, 214 teLinkDescriptorTable, teLinkBandwidthTable are derived from the 215 bandwidth parameters of the componentLinkTable, 216 componentLinkDescriptorTable and componentLinkBandwidthTable (maximum 217 reservable bandwidth, minimum LSP bandwidth, maximum LSP bandwidth at 218 specified priority and unreserved bandwidth). 220 7. Example of Bundled Link Setup 222 In this section we provide a brief example of using the MIB 223 objects described in section 10 to set up a bundled link. 224 While this example is not meant to illustrate every nuance of the 225 MIB module, it is intended as an aid to understanding some 226 of the key concepts. It is meant to be read after going through the 227 MIB module itself. More details on the use of the ifStackTable 228 to establish relationship between bundled links, TE links and 229 component links are given in Section 8.2. 231 Suppose that one would like to manually create a bundled link 232 out of two 1:1 TE links as depicted on the figure in Section 8.2. 233 Assume that the bundled link is associated with SRLGs 10 and 50. 234 Finally, let the component links be port entity interfaces 235 (lambdas). The following example illustrates which rows and 236 corresponding objects might be created to accomplish this. 238 First, a bundled link entry is created. An ifEntry with the same 239 ifIndex and with ifType teLink needs to be created beforehand. 241 In teLinkTable: 242 { 243 ifIndex = 2, 244 teLinkAddressType = unknown(0), 245 teLinkLocalIpAddr = ''H, 246 teLinkRemoteIpAddr = ''H, 247 teLinkMetric = 5, 248 teLinkProtectionType = dedicated1For1(4), 249 teLinkWorkingPriority = 7, 250 teLinkResourceClass = 3, 251 teLinkIncomingIfId = 0, 252 teLinkOutgoingIfId = 2, 253 teLinkRowStatus = createAndGo(4), 254 teLinkStorageType = nonVolatile(3) 255 } 257 In ifStackTable: 258 { 259 ifStackHigherLayer = 0, 260 ifStackLowerLayer = 2, 261 ifStackStatus = createAndGo(4) 262 } 264 Next, the two TE links are created. 266 In teLinkTable: 267 { 268 ifIndex = 3, 269 teLinkAddressType = unknown(0), 270 teLinkLocalIpAddr = ''H, 271 teLinkRemoteIpAddr = ''H, 272 teLinkMetric = 5, 273 teLinkProtectionType = unprotected(2), 274 teLinkWorkingPriority = 7, 275 teLinkResourceClass = 3, 276 teLinkIncomingIfId = 0, 277 teLinkOutgoingIfId = 3, 278 teLinkRowStatus = createAndGo(4), 279 teLinkStorageType = nonVolatile(3) 280 } 282 In ifStackTable: 283 { 284 ifStackHigherLayer = 2, 285 ifStackLowerLayer = 3, 286 ifStackStatus = createAndGo(4) 287 } 289 In teLinkTable: 290 { 291 ifIndex = 4, 292 teLinkAddressType = unknown(0), 293 teLinkLocalIpAddr = ''H, 294 teLinkRemoteIpAddr = ''H, 295 teLinkMetric = 5, 296 teLinkProtectionType = unprotected(2), 297 teLinkWorkingPriority = 7, 298 teLinkResourceClass = 3, 299 teLinkIncomingIfId = 0, 300 teLinkOutgoingIfId = 4, 301 teLinkRowStatus = createAndGo(4), 302 teLinkStorageType = nonVolatile(3) 303 } 305 In ifStackTable: 306 { 307 ifStackHigherLayer = 2, 308 ifStackLowerLayer = 4, 309 ifStackStatus = createAndGo(4) 310 } 312 We assign SRLGs to the TE links. 314 In the teLinkSrlgTable: 315 { 316 ifIndex = 3, 317 teLinkSrlg = 10, 318 teLinkSrlgRowStatus = createAndGo(4), 319 teLinkSrlgStorageType = nonVolatile(3) 320 } 322 In the teLinkSrlgTable: 323 { 324 ifIndex = 4, 325 teLinkSrlg = 50, 326 teLinkSrlgRowStatus = createAndGo(4), 327 teLinkSrlgStorageType = nonVolatile(3) 328 } 330 The bundled link inherits the SRLG properties from the 331 associated TE links. 333 Next, for each unbundled TE link, a component link is created. 335 An ifEntry with the same ifIndex needs to be created beforehand. 337 In componentLinkTable: 338 { 339 ifIndex = 5, 340 componentLinkPreferredProtection = primary(1), 341 componentLinkRowStatus = createAndGo(4), 342 componentLinkStorageType = nonVolatile(3) 343 } 345 In ifStackTable: 346 { 347 ifStackHigherLayer = 3, 348 ifStackLowerLayer = 5, 349 ifStackStatus = createAndGo(4) 350 } 352 In componentLinkTable: 353 { 354 ifIndex = 6, 355 componentLinkPreferredProtection = secondary(2), 356 componentLinkRowStatus = createAndGo(4) 357 componentLinkStorageType = nonVolatile(3) 358 } 360 In ifStackTable: 361 { 362 ifStackHigherLayer = 4, 363 ifStackLowerLayer = 6, 364 ifStackStatus = createAndGo(4) 365 } 367 In this example, once a component link is added to the 368 componentLinkTable, the associated link descriptors are 369 implicitly added to the componentLinkDescriptorTable. 371 TE link link descriptors are derived from their component link 372 descriptors. 374 Note that the bandwidth attributes in teLinkDescriptorTable, 375 componentLinkDescriptorTable, teLinkBandwidthTable 376 and componentLinkBandwidthTable are maintained by the 377 device according to LSP creation/deletion at different priorities. 378 The values in the teLinkBandwidthTable are an aggregation 379 of the values for the component links of the TE links and 380 the TE links of the bundled link. 382 8. Application of the Interfaces Group to TE Links 384 The Interfaces Group [RFC2863] defines generic managed objects for 385 managing interfaces. This memo contains the media-specific 386 extensions to the Interfaces Group for managing TE Link interfaces 387 as logical interfaces. 389 This memo assumes the interpretation of the Interfaces Group to be 390 in accordance with [RFC2863] which states that the interfaces table 391 (ifTable) contains information on the managed resource's 392 interfaces and that each sub-layer below the internetwork layer of 393 a network interface is considered an interface. Thus, the TE Link 394 interface is represented as an entry in the ifTable. The 395 interrelation of entries in the ifTable is defined by Interfaces 396 Stack Group defined in [RFC2863]. 398 When using TE Link interfaces, the interface stack table might appear 399 as follows: 401 +----------------------------------------+ 402 | TE link-interface ifType = teLink(200) + 403 +----------------------------------------+ 404 | Underlying Layer... + 405 +----------------------------------------+ 407 In the above diagram, "Underlying Layer..." refers to the ifIndex 408 of any interface type, which has been defined for TE Link 409 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 411 8.1. Support of the TE Link Layer by ifTable 413 Some specific interpretations of ifTable for the TE Link layer 414 follow. 416 Object Use for the TE Link layer 418 ifIndex Each TE Link interface is represented by an ifEntry. 420 ifDescr Description of the TE Link interface. 422 ifType The value that is allocated for TE Link is 200 423 [IANAifType]. 425 ifSpeed The total bandwidth in bits per second for use by 426 the TE Link layer. 428 ifPhysAddress Unused. 430 ifAdminStatus This variable indicates the administrator's intent 431 as to whether TE Link should be enabled, disabled, or 432 running in some diagnostic testing mode on this 433 interface. Also see [RFC2863]. 435 ifOperStatus This value reflects the actual or operational 436 status of TE Link on this interface. 438 ifLastChange See [RFC2863]. 440 ifInOctets The number of received octets over the interface, 441 i.e., the number of received octets in all component 442 links associated with the interface. 444 ifOutOctets The number of transmitted octets over the 445 interface, i.e., the number of octets transmitted 446 over all component links associated with the 447 interface. 449 ifInErrors The number of packets dropped due to 450 uncorrectable errors. 452 ifInUnknownProtos 453 The number of received packets discarded during 454 packet header validation. 456 ifOutErrors See [RFC2863]. 458 ifName Textual name (unique on this system) of the 459 interface or an octet string of zero length. 461 ifLinkUpDownTrapEnable 462 Default is disabled (2). 464 ifConnectorPresent 465 Set to false (2). 467 ifHighSpeed See [RFC2863]. 469 ifHCInOctets The 64-bit version of ifInOctets; supported if 470 required by the compliance statements in [RFC2863]. 472 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 473 required by the compliance statements in [RFC2863]. 475 ifAlias The non-volatile 'alias' name for the interface as 476 specified by a network manager. 478 ifCounterDiscontinuityTime 479 See [RFC2863]. 481 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 482 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 483 if encoding type is clear. For other encoding types, traffic 484 counters on a TE link are cumulative for all subinterfaces which it 485 binds together. 487 8.2. Using ifStackTable 489 This section describes by example how to use ifStackTable to 490 represent the relationship of TE links with underlying TE-enabled 491 interfaces. Implementors of the stack table for TE link interfaces 492 should look at the appropriate RFC for the service being stacked 493 on TE links. Examples given below are for illustration purposes 494 only. 496 Example: MPLS is being carried on a bundled TE links. 497 The bundled TE link represents a 1:1 optical 498 transport interface. 500 In this example, the component link is a TE link. The two component 501 links/TE links are grouped in a bundled link. 503 +-------------------------------------------------------------------+ 504 | MPLS interface ifType = mpls(166) | 505 | ifIndex = 1 | 506 +-------------------------------------------------------------------+ 507 | TE link (bundled link) ifType = teLink(200) | 508 | ifIndex = 2 | 509 +--------------------------------+-+--------------------------------+ 510 | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | 511 | ifIndex = 3 | | ifIndex = 4 | 512 +--------------------------------+ +--------------------------------+ 513 | Component link | | Component link | 514 | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | 515 | ifIndex = 5 | | ifIndex = 6 | 516 +--------------------------------+ +--------------------------------+ 518 The assignment of the index values could for example be: 520 ifIndex Description 521 1 mpls (type 166) 522 2 teLink (type 200) 523 3 teLink (type 200) 524 4 teLink (type 200) 525 5 opticalTransport (type 196) 526 6 opticalTransport (type 196) 528 The ifStackTable is then used to show the relationships between the 529 various interfaces. 531 ifStackTable Entries 533 HigherLayer LowerLayer 534 0 1 535 1 2 536 2 3 537 2 4 538 3 5 539 4 6 540 5 0 541 6 0 543 In the case where MPLS is using a single TE link, then 544 the upper TE link layer (link bundle) is not required. 546 +-----------------------------------+ 547 | MPLS interface ifType = mpls(166) | 548 +-----------------------------------+ 549 | TE link ifType = teLink(200) | 550 +-----------------------------------+ 551 | Component link | 552 | ifType = opticalTransport(196) | 553 +-----------------------------------+ 555 The assignment of the index values could for example be: 557 ifIndex Description 558 1 mpls (type 166) 559 2 teLink (type 200) 560 3 opticalTransport (type 196) 562 The ifStackTable is then used to show the relationships between the 563 various interfaces. 565 ifStackTable Entries 567 HigherLayer LowerLayer 568 0 1 569 1 2 570 2 3 571 3 0 573 8.3. Applicability of ifRcvAddressTable 575 TE link interfaces are logical interfaces with no media-level 576 addresses. As such, the ifRcvAddressTable is not applicable 577 to these interfaces. 579 9. TE Link MIB Module Definitions 581 TE-LINK-STD-MIB DEFINITIONS ::= BEGIN 583 IMPORTS 584 MODULE-IDENTITY, OBJECT-TYPE, transmission, Integer32, Unsigned32 585 FROM SNMPv2-SMI 587 MODULE-COMPLIANCE, OBJECT-GROUP 588 FROM SNMPv2-CONF 590 TEXTUAL-CONVENTION, RowStatus, StorageType 591 FROM SNMPv2-TC 593 InterfaceIndexOrZero, ifIndex 594 FROM IF-MIB 596 InetAddressType, InetAddress 597 FROM INET-ADDRESS-MIB; 599 teLinkStdMIB MODULE-IDENTITY 600 LAST-UPDATED "200402011200Z" -- 1 February 2004 12:00:00 EST 601 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 602 CONTACT-INFO 603 " Martin Dubuc 604 Email: dubuc.consulting@rogers.com 606 Sudheer Dharanikota 607 Email: sudheer@ieee.org 609 Thomas D. Nadeau 610 Email: tnadeau@cisco.com 612 Jonathan P. Lang 613 Email: jplang@ieee.org 615 Comments about this document should be emailed directly to 616 the MPLS working group mailing list at mpls@uu.net." 618 DESCRIPTION 619 "Copyright (C) 2004 The Internet Society. This version of 620 this MIB module is part of RFC XXXX; see the RFC 621 itself for full legal notices. 623 This MIB module contains managed object definitions for 624 MPLS traffic engineering links as defined in 625 'Link Bundling in MPLS Traffic Engineering'." 627 -- Revision history. 628 REVISION 629 "200402011200Z" -- 1 February 2004 12:00:00 EST 630 DESCRIPTION 631 "Initial version published as RFC xxxx (to be assigned by RFC 632 Editor)" 633 ::= { transmission xxx } -- To be assigned by IANA. 634 -- Request to assign 200 which is 635 -- ifType value for teLink. 637 -- Textual Conventions 639 TeLinkBandwidth ::= TEXTUAL-CONVENTION 640 STATUS current 641 DESCRIPTION 642 "This type is used to represent link bandwidth in bps. This 643 value is represented using a 4 octet IEEE floating point 644 format." 645 REFERENCE 646 "IEEE Standard for Binary Floating-Point Arithmetic, 647 Standard 754-1985" 648 SYNTAX OCTET STRING (SIZE(4)) 650 TeLinkPriority ::= TEXTUAL-CONVENTION 651 DISPLAY-HINT "d" 652 STATUS current 653 DESCRIPTION 654 "This type is used to represent a priority. Each connection is 655 assigned a priority. This priority is used when accounting for 656 bandwidth on TE links or component links, for resource 657 allocation and for rerouting purposes. Value 0 is the highest 658 priority. Value 7 is the lowest priority." 659 SYNTAX Unsigned32 (0..7) 661 TeLinkProtection ::= TEXTUAL-CONVENTION 662 STATUS current 663 DESCRIPTION 664 "Link protection." 665 SYNTAX INTEGER { 666 primary(1), 667 secondary(2) 668 } 670 TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION 671 STATUS current 672 DESCRIPTION 673 "Switching capability as specified in the 'OSPF Extensions in 674 Support of Generalized MPLS' document. The values specified in 675 this document are not contiguous." 676 SYNTAX INTEGER { 677 packetSwitch1(1), 678 packetSwitch2(2), 679 packetSwitch3(3), 680 packetSwitch4(4), 681 layer2Switch(51), 682 tdm(100), 683 lambdaSwitch(150), 684 fiberSwitch(200) 685 } 687 TeLinkEncodingType ::= TEXTUAL-CONVENTION 688 STATUS current 689 DESCRIPTION 690 "Link encoding type as specified in 'GMPLS Signaling Functional 691 Description' document. The values specified in this document are 692 not contiguous." 693 SYNTAX INTEGER { 694 packet(1), 695 ethernet(2), 696 ansiEtsiPdh(3), 697 sdhItuSonetAnsi(5), 698 digitalWrapper(7), 699 lambda(8), 700 fiber(9), 701 fiberChannel(11) 702 } 704 TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION 705 STATUS current 706 DESCRIPTION 707 "This convention is used to indicate whether the interface 708 supports Standard or Arbitrary SONET/SDH. To simplify the 709 mapping process, the values used in this textual convention 710 match the values specified in the interface switching 711 capability specific information field, i.e. 0 for Standard 712 SONET/SDH and 1 for Arbitrary SONET/SDH." 713 REFERENCE 714 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 715 -- RFC Editor to fill in RFC number that will be assigned to 716 -- [GMPLS-OSPF] 717 SYNTAX INTEGER { 718 standard(0), 719 arbitrary(1) 720 } 722 -- Top level components of this MIB module 724 -- Notifications 725 teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } 726 -- Tables, Scalars 727 teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 } 728 -- Conformance 729 teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 } 731 -- TE Link Table 733 teLinkTable OBJECT-TYPE 734 SYNTAX SEQUENCE OF TeLinkEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "This table specifies the grouping of component links into 739 TE links and grouping of TE links into bundled links." 740 ::= { teLinkObjects 1 } 742 teLinkEntry OBJECT-TYPE 743 SYNTAX TeLinkEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "An entry in this table exists for each ifEntry with an 748 ifType of teLink(200), i.e. for every TE link. An ifEntry 749 in the ifTable must exist before a teLinkEntry is created with 750 the corresponding ifIndex. If a TE link entry in the ifTable is 751 destroyed, then so is the corresponding entry in the 752 teLinkTable. The administrative and operational status values 753 are controlled from the ifEntry." 754 INDEX { ifIndex } 755 ::= { teLinkTable 1 } 757 TeLinkEntry ::= SEQUENCE { 758 teLinkAddressType InetAddressType, 759 teLinkLocalIpAddr InetAddress, 760 teLinkRemoteIpAddr InetAddress, 761 teLinkMetric Unsigned32, 762 teLinkMaximumReservableBandwidth TeLinkBandwidth, 763 teLinkProtectionType INTEGER, 764 teLinkWorkingPriority TeLinkPriority, 765 teLinkResourceClass Unsigned32, 766 teLinkIncomingIfId Integer32, 767 teLinkOutgoingIfId InterfaceIndexOrZero, 768 teLinkRowStatus RowStatus, 769 teLinkStorageType StorageType 770 } 772 teLinkAddressType OBJECT-TYPE 773 SYNTAX InetAddressType 774 MAX-ACCESS read-create 775 STATUS current 776 DESCRIPTION 777 "The type of Internet address for the TE link." 778 ::= { teLinkEntry 1 } 780 teLinkLocalIpAddr OBJECT-TYPE 781 SYNTAX InetAddress 782 MAX-ACCESS read-create 783 STATUS current 784 DESCRIPTION 785 "The local Internet address for numbered links. The type of this 786 address is determined by the value of the teLinkAddressType 787 object. 789 For IPv4 and IPv6 numbered links, this object represents the 790 local IP address associated with the TE link. For an 791 unnumbered link, the local address is of type unknown and this 792 object is set to the zero length string and the 793 teLinkOutgoingIfId object then identifies the unnumbered 794 address. 796 If the TE link is a Forwarding Adjacency (FA), the local 797 IP address is set to the head-end address of the FA-LSP. 799 If ipAddrTable is implemented, this object must have the 800 same value as the ipAdEntAddr object that belongs to the 801 row in ipAddrTable where ipAdEntIfIndex is equal to 802 ifIndex." 803 ::= { teLinkEntry 2 } 805 teLinkRemoteIpAddr OBJECT-TYPE 806 SYNTAX InetAddress 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "The remote Internet address for numbered links. The type of 811 this address is determined by the value of the 812 teLinkAddressType object. 814 The remote IP address associated with the TE link (IPv4 and 815 IPv6 numbered links). For an unnumbered link, the remote 816 address is of type unknown and this object is set to the 817 zero length string and the teLinkIncomingIfId object then 818 identifies the unnumbered address. 820 If the TE link is a Forwarding Adjacency, the remote IP 821 address is set to the tail-end address of the FA-LSP." 822 ::= { teLinkEntry 3 } 824 teLinkMetric OBJECT-TYPE 825 SYNTAX Unsigned32 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "The traffic engineering metric for the TE link is 830 derived from its component links. All component links 831 within the TE link must have the same traffic 832 engineering metric." 833 REFERENCE 834 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 835 -- RFC Editor to fill in RFC number that will be assigned to 836 -- [BUNDLING] 837 ::= { teLinkEntry 4 } 839 teLinkMaximumReservableBandwidth OBJECT-TYPE 840 SYNTAX TeLinkBandwidth 841 UNITS "bps" 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "This attribute specifies the maximum reservable bandwidth on 846 the TE link. This is the union of the maximum reservable 847 bandwidth of all the component links within the 848 TE link that can be used to carry live traffic." 849 REFERENCE 850 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 851 -- RFC Editor to fill in RFC number that will be assigned to 852 -- [GMPLS-OSPF] 853 ::= { teLinkEntry 5 } 855 teLinkProtectionType OBJECT-TYPE 856 SYNTAX INTEGER { 857 extraTraffic(1), 858 unprotected(2), 859 shared(3), 860 dedicated1For1(4), 861 dedicated1Plus1(5), 862 enhanced(6) 863 } 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "This attribute specifies link protection type of the 868 TE link. Description of the different protection types can be 869 found in the 'Routing Extensions in Support of Generalized 870 MPLS' document." 871 REFERENCE 872 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 873 Routing Extensions in Support of Generalized MPLS, RFC xxxx" 874 -- RFC Editor to fill in RFC number that will be assigned to 875 -- [GMPLS-OSPF] and [ROUTING] 876 ::= { teLinkEntry 6 } 878 teLinkWorkingPriority OBJECT-TYPE 879 SYNTAX TeLinkPriority 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "This object represents a priority value such that a new 884 connection with a higher priority, i.e. numerically lower than 885 this value, is guaranteed to be setup on a primary link and 886 not on a secondary link." 887 REFERENCE 888 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 889 -- RFC Editor to fill in RFC number that will be assigned to 890 -- [GMPLS-OSPF] 891 ::= { teLinkEntry 7 } 893 teLinkResourceClass OBJECT-TYPE 894 SYNTAX Unsigned32 895 MAX-ACCESS read-create 896 STATUS current 897 DESCRIPTION 898 "This attribute specifies the TE link resource class. 899 The resource class is a 32 bit bitfield. The resource class for 900 a link bundle is derived from the resource class of its 901 TE links. All TE links within a link bundle must have the 902 same resource class. Encoding of the resource class is described 903 in the 'Traffic Engineering Extensions to OSPF Version 2' 904 document." 905 REFERENCE 906 "Link Bundling in MPLS Traffic Engineering, RFC xxxx and 907 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 908 -- RFC Editor to fill in RFC number that will be assigned to 909 -- [BUNDLING] and [OSPF] 910 ::= { teLinkEntry 8 } 912 teLinkIncomingIfId OBJECT-TYPE 913 SYNTAX Integer32 (0..2147483647) 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "For unnumbered links, the incoming interface is set to the 918 outgoing interface identifier chosen by the neighboring LSR 919 for the reverse link corresponding to this TE link. If the 920 link is numbered, the value of this object is 0 and the 921 address is stored in the teLinkRemoteIpAddr instead." 922 REFERENCE 923 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 924 -- RFC Editor to fill in RFC number that will be assigned to 925 -- [BUNDLING] 926 ::= { teLinkEntry 9 } 928 teLinkOutgoingIfId OBJECT-TYPE 929 SYNTAX InterfaceIndexOrZero 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "If the link is unnumbered, the outgoing interface identifier is 934 set to the outgoing interface identifier chosen for the TE link 935 by the advertising LSR. If the link is numbered, the value of 936 this object is 0 and the address is stored in the 937 teLinkLocalIpAddr instead." 938 REFERENCE 939 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 940 -- RFC Editor to fill in RFC number that will be assigned to 941 -- [BUNDLING] 942 ::= { teLinkEntry 10 } 944 teLinkRowStatus OBJECT-TYPE 945 SYNTAX RowStatus 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "This variable is used to create, modify, and/or 950 delete a row in this table. None of the writable objects in 951 a row can be changed if status is active(1)." 952 ::= { teLinkEntry 11 } 954 teLinkStorageType OBJECT-TYPE 955 SYNTAX StorageType 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "The storage type for this conceptual row in the 960 teLinkTable. Conceptual rows having the value 961 'permanent' need not allow write-access to any 962 columnar object in the row." 963 ::= { teLinkEntry 12 } 965 -- End of teLinkTable 967 -- TE Link Descriptor Table 969 teLinkDescriptorTable OBJECT-TYPE 970 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "This table specifies the interface switching capability 975 descriptors associated with the TE links." 976 ::= { teLinkObjects 2 } 978 teLinkDescriptorEntry OBJECT-TYPE 979 SYNTAX TeLinkDescriptorEntry 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "An entry in this table is created for every TE link interface 984 switching capability descriptor. An ifEntry in the ifTable 985 must exist before a teLinkDescriptorEntry using the same 986 ifIndex is created. ifType of ifEntry must be teLink(200). 987 If a TE link entry in the ifTable is destroyed, then so are all 988 entries in the teLinkDescriptorTable that use the ifIndex of 989 this TE link." 990 INDEX { ifIndex, teLinkDescriptorId } 991 ::= { teLinkDescriptorTable 1 } 993 TeLinkDescriptorEntry ::= SEQUENCE { 994 teLinkDescriptorId Unsigned32, 995 teLinkDescrSwitchingCapability TeLinkSwitchingCapability, 996 teLinkDescrEncodingType TeLinkEncodingType, 997 teLinkDescrMinLspBandwidth TeLinkBandwidth, 998 teLinkDescrMaxLspBandwidthPrio0 TeLinkBandwidth, 999 teLinkDescrMaxLspBandwidthPrio1 TeLinkBandwidth, 1000 teLinkDescrMaxLspBandwidthPrio2 TeLinkBandwidth, 1001 teLinkDescrMaxLspBandwidthPrio3 TeLinkBandwidth, 1002 teLinkDescrMaxLspBandwidthPrio4 TeLinkBandwidth, 1003 teLinkDescrMaxLspBandwidthPrio5 TeLinkBandwidth, 1004 teLinkDescrMaxLspBandwidthPrio6 TeLinkBandwidth, 1005 teLinkDescrMaxLspBandwidthPrio7 TeLinkBandwidth, 1006 teLinkDescrInterfaceMtu Unsigned32, 1007 teLinkDescrIndication TeLinkSonetSdhIndication, 1008 teLinkDescrRowStatus RowStatus, 1009 teLinkDescrStorageType StorageType 1010 } 1012 teLinkDescriptorId OBJECT-TYPE 1013 SYNTAX Unsigned32 (1..4294967295) 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "This object specifies the link descriptor identifier." 1018 ::= { teLinkDescriptorEntry 1 } 1020 teLinkDescrSwitchingCapability OBJECT-TYPE 1021 SYNTAX TeLinkSwitchingCapability 1022 MAX-ACCESS read-create 1023 STATUS current 1024 DESCRIPTION 1025 "This attribute specifies interface switching capability of the 1026 TE link, which is derived from its component links." 1027 REFERENCE 1028 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1029 -- RFC Editor to fill in RFC number that will be assigned to 1030 -- [GMPLS-OSPF] 1031 ::= { teLinkDescriptorEntry 2 } 1033 teLinkDescrEncodingType OBJECT-TYPE 1034 SYNTAX TeLinkEncodingType 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "This attribute specifies the TE link encoding type." 1039 REFERENCE 1040 "Generalized MPLS Signaling Functional Description, RFC 3471" 1041 ::= { teLinkDescriptorEntry 3 } 1043 teLinkDescrMinLspBandwidth OBJECT-TYPE 1044 SYNTAX TeLinkBandwidth 1045 UNITS "bps" 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 "This attribute specifies the minimum LSP bandwidth on 1050 the TE link. This is derived from the union of the 1051 minimum LSP bandwidth of all the component links 1052 associated with the TE link that can be used to carry 1053 live traffic." 1054 REFERENCE 1055 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1056 -- RFC Editor to fill in RFC number that will be assigned to 1057 -- [GMPLS-OSPF] 1058 ::= { teLinkDescriptorEntry 4 } 1060 teLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1061 SYNTAX TeLinkBandwidth 1062 UNITS "bps" 1063 MAX-ACCESS read-create 1064 STATUS current 1065 DESCRIPTION 1066 "This attribute specifies the maximum LSP bandwidth at 1067 priority 0 on the TE link. This is the union of the maximum 1068 LSP bandwidth at priority 0 of all the component links within 1069 the TE link that can be used to carry live traffic." 1070 REFERENCE 1071 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1072 -- RFC Editor to fill in RFC number that will be assigned to 1073 -- [GMPLS-OSPF] 1074 ::= { teLinkDescriptorEntry 5 } 1076 teLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE 1077 SYNTAX TeLinkBandwidth 1078 UNITS "bps" 1079 MAX-ACCESS read-create 1080 STATUS current 1081 DESCRIPTION 1082 "This attribute specifies the maximum LSP bandwidth at 1083 priority 1 on the TE link. This is the union of the maximum 1084 LSP bandwidth at priority 1 of all the component links within 1085 the TE link that can be used to carry live traffic." 1086 REFERENCE 1087 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1088 -- RFC Editor to fill in RFC number that will be assigned to 1089 -- [GMPLS-OSPF] 1090 ::= { teLinkDescriptorEntry 6 } 1092 teLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE 1093 SYNTAX TeLinkBandwidth 1094 UNITS "bps" 1095 MAX-ACCESS read-create 1096 STATUS current 1097 DESCRIPTION 1098 "This attribute specifies the maximum LSP bandwidth at 1099 priority 2 on the TE link. This is the union of the maximum 1100 LSP bandwidth at priority 2 of all the component links within 1101 the TE link that can be used to carry live traffic." 1102 REFERENCE 1103 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1104 -- RFC Editor to fill in RFC number that will be assigned to 1105 -- [GMPLS-OSPF] 1106 ::= { teLinkDescriptorEntry 7 } 1108 teLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE 1109 SYNTAX TeLinkBandwidth 1110 UNITS "bps" 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "This attribute specifies the maximum LSP bandwidth at 1115 priority 3 on the TE link. This is the union of the maximum 1116 LSP bandwidth at priority 3 of all the component links within 1117 the TE link that can be used to carry live traffic." 1118 REFERENCE 1119 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1120 -- RFC Editor to fill in RFC number that will be assigned to 1121 -- [GMPLS-OSPF] 1122 ::= { teLinkDescriptorEntry 8 } 1124 teLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1125 SYNTAX TeLinkBandwidth 1126 UNITS "bps" 1127 MAX-ACCESS read-create 1128 STATUS current 1129 DESCRIPTION 1130 "This attribute specifies the maximum LSP bandwidth at 1131 priority 4 on the TE link. This is the union of the maximum 1132 LSP bandwidth at priority 4 of all the component links within 1133 the TE link that can be used to carry live traffic." 1134 REFERENCE 1135 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1136 -- RFC Editor to fill in RFC number that will be assigned to 1137 -- [GMPLS-OSPF] 1138 ::= { teLinkDescriptorEntry 9 } 1140 teLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1141 SYNTAX TeLinkBandwidth 1142 UNITS "bps" 1143 MAX-ACCESS read-create 1144 STATUS current 1145 DESCRIPTION 1146 "This attribute specifies the maximum LSP bandwidth at 1147 priority 5 on the TE link. This is the union of the maximum 1148 LSP bandwidth at priority 5 of all the component links within 1149 the TE link that can be used to carry live traffic." 1150 REFERENCE 1151 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1152 -- RFC Editor to fill in RFC number that will be assigned to 1153 -- [GMPLS-OSPF] 1154 ::= { teLinkDescriptorEntry 10 } 1156 teLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1157 SYNTAX TeLinkBandwidth 1158 UNITS "bps" 1159 MAX-ACCESS read-create 1160 STATUS current 1161 DESCRIPTION 1162 "This attribute specifies the maximum LSP bandwidth at 1163 priority 6 on the TE link. This is the union of the maximum 1164 LSP bandwidth at priority 6 of all the component links within 1165 the TE link that can be used to carry live traffic." 1166 REFERENCE 1167 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1168 -- RFC Editor to fill in RFC number that will be assigned to 1169 -- [GMPLS-OSPF] 1170 ::= { teLinkDescriptorEntry 11 } 1172 teLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1173 SYNTAX TeLinkBandwidth 1174 UNITS "bps" 1175 MAX-ACCESS read-create 1176 STATUS current 1177 DESCRIPTION 1178 "This attribute specifies the maximum LSP bandwidth at 1179 priority 7 on the TE link. This is the union of the maximum 1180 LSP bandwidth at priority 7 of all the component links within 1181 the TE link that can be used to carry live traffic." 1182 REFERENCE 1183 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1184 -- RFC Editor to fill in RFC number that will be assigned to 1185 -- [GMPLS-OSPF] 1186 ::= { teLinkDescriptorEntry 12 } 1188 teLinkDescrInterfaceMtu OBJECT-TYPE 1189 SYNTAX Unsigned32 (1..65535) 1190 MAX-ACCESS read-create 1191 STATUS current 1192 DESCRIPTION 1193 "This attribute specifies the interface MTU for the TE 1194 link descriptor." 1195 REFERENCE 1196 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1197 -- RFC Editor to fill in RFC number that will be assigned to 1198 -- [GMPLS-OSPF] 1199 ::= { teLinkDescriptorEntry 13 } 1201 teLinkDescrIndication OBJECT-TYPE 1202 SYNTAX TeLinkSonetSdhIndication 1203 MAX-ACCESS read-create 1204 STATUS current 1205 DESCRIPTION 1206 "This attribute specifies whether this interface supports 1207 Standard or Arbitrary SONET/SDH." 1208 REFERENCE 1209 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1210 -- RFC Editor to fill in RFC number that will be assigned to 1211 -- [GMPLS-OSPF] 1212 ::= { teLinkDescriptorEntry 14 } 1214 teLinkDescrRowStatus OBJECT-TYPE 1215 SYNTAX RowStatus 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "This variable is used to create, modify, and/or 1220 delete a row in this table. No read-create object 1221 can changed if teLinkDescrRowStatus is in active(1) state." 1222 ::= { teLinkDescriptorEntry 15 } 1224 teLinkDescrStorageType OBJECT-TYPE 1225 SYNTAX StorageType 1226 MAX-ACCESS read-create 1227 STATUS current 1228 DESCRIPTION 1229 "The storage type for this conceptual row in the 1230 teLinkDescriptorTable. Conceptual rows having the value 1231 'permanent' need not allow write-access to any 1232 columnar object in the row." 1233 ::= { teLinkDescriptorEntry 16 } 1235 -- End of teLinkDescriptorTable 1237 -- TE Link Shared Risk Link Group Table 1239 teLinkSrlgTable OBJECT-TYPE 1240 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1241 MAX-ACCESS not-accessible 1242 STATUS current 1243 DESCRIPTION 1244 "This table specifies the SRLGs associated with TE links." 1245 ::= { teLinkObjects 3 } 1247 teLinkSrlgEntry OBJECT-TYPE 1248 SYNTAX TeLinkSrlgEntry 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "An entry in this table contains information about a 1253 SRLG associated with a TE link. 1254 An ifEntry in the ifTable must exist before a 1255 teLinkSrlgEntry using the same ifIndex is created. 1256 ifType of ifEntry must be teLink(200). 1257 If a TE link entry in the ifTable is destroyed, then so are all 1258 entries in the teLinkSrlgTable that use the ifIndex of 1259 this TE link." 1260 INDEX { ifIndex, teLinkSrlg } 1261 ::= { teLinkSrlgTable 1 } 1263 TeLinkSrlgEntry ::= SEQUENCE { 1264 teLinkSrlg Unsigned32, 1265 teLinkSrlgRowStatus RowStatus, 1266 teLinkSrlgStorageType StorageType 1267 } 1269 teLinkSrlg OBJECT-TYPE 1270 SYNTAX Unsigned32 (0..4294967295) 1271 MAX-ACCESS not-accessible 1272 STATUS current 1273 DESCRIPTION 1274 "This identifies a SRLG supported by the TE link. An SRLG is 1275 identified with a 32 bit number that is unique within an IGP 1276 domain. Zero is a valid SRLG number." 1277 REFERENCE 1278 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1279 -- RFC Editor to fill in RFC number that will be assigned to 1280 -- [GMPLS-OSPF] 1281 ::= { teLinkSrlgEntry 1 } 1283 teLinkSrlgRowStatus OBJECT-TYPE 1284 SYNTAX RowStatus 1285 MAX-ACCESS read-create 1286 STATUS current 1287 DESCRIPTION 1288 "This variable is used to create, modify, and/or 1289 delete a row in this table. No read-create object can 1290 be modified if teLinkSrlgRowStatus is active(1)." 1291 ::= { teLinkSrlgEntry 2 } 1293 teLinkSrlgStorageType OBJECT-TYPE 1294 SYNTAX StorageType 1295 MAX-ACCESS read-create 1296 STATUS current 1297 DESCRIPTION 1298 "The storage type for this conceptual row in the 1299 teLinkSrlgTable. Conceptual rows having the value 1300 'permanent' need not allow write-access to any 1301 columnar object in the row." 1302 ::= { teLinkSrlgEntry 3 } 1304 -- End of teLinkSrlgTable 1306 -- TE Link Bandwidth Table 1308 teLinkBandwidthTable OBJECT-TYPE 1309 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "This table specifies the priority-based bandwidth table 1314 for TE links." 1315 ::= { teLinkObjects 4 } 1317 teLinkBandwidthEntry OBJECT-TYPE 1318 SYNTAX TeLinkBandwidthEntry 1319 MAX-ACCESS not-accessible 1320 STATUS current 1321 DESCRIPTION 1322 "An entry in this table contains information about 1323 the priority-based bandwidth of TE links. An ifEntry in the 1324 ifTable must exist before a teLinkBandwidthEntry using the 1325 same ifIndex is created. ifType of ifEntry must be teLink(200). 1326 If a TE link entry in the ifTable is destroyed, then so are 1327 all entries in the teLinkBandwidthTable that use the ifIndex of 1328 this TE link." 1329 INDEX { ifIndex, teLinkBandwidthPriority } 1330 ::= { teLinkBandwidthTable 1 } 1332 TeLinkBandwidthEntry ::= SEQUENCE { 1333 teLinkBandwidthPriority TeLinkPriority, 1334 teLinkBandwidthUnreserved TeLinkBandwidth, 1335 teLinkBandwidthRowStatus RowStatus, 1336 teLinkBandwidthStorageType StorageType 1337 } 1339 teLinkBandwidthPriority OBJECT-TYPE 1340 SYNTAX TeLinkPriority 1341 MAX-ACCESS not-accessible 1342 STATUS current 1343 DESCRIPTION 1344 "This attribute specifies the priority. A value of 0 is valid 1345 as specified in the 'Traffic Engineering Extensions to OSPF 1346 Version 2' document." 1347 REFERENCE 1348 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1349 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1350 -- RFC Editor to fill in RFC number that will be assigned to 1351 -- [GMPLS-OSPF] and [OSPF] 1352 ::= { teLinkBandwidthEntry 1 } 1354 teLinkBandwidthUnreserved OBJECT-TYPE 1355 SYNTAX TeLinkBandwidth 1356 UNITS "bps" 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "This attribute specifies the TE link unreserved 1361 bandwidth at priority p. It is the sum of the unreserved 1362 bandwidths at priority p of all component links associated 1363 with the TE link (excludes all links that are strictly 1364 used as protecting links)." 1365 REFERENCE 1366 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 1367 -- RFC Editor to fill in RFC number that will be assigned to 1368 -- [BUNDLING] 1369 ::= { teLinkBandwidthEntry 2 } 1371 teLinkBandwidthRowStatus OBJECT-TYPE 1372 SYNTAX RowStatus 1373 MAX-ACCESS read-create 1374 STATUS current 1375 DESCRIPTION 1376 "This variable is used to create, modify, and/or 1377 delete a row in this table. No read-create object 1378 can be modified when teLinkBandwidthRowStatus is active(1)." 1379 ::= { teLinkBandwidthEntry 4 } 1381 teLinkBandwidthStorageType OBJECT-TYPE 1382 SYNTAX StorageType 1383 MAX-ACCESS read-create 1384 STATUS current 1385 DESCRIPTION 1386 "The storage type for this conceptual row in the 1387 teLinkBandwidthTable. Conceptual rows having the value 1388 'permanent' need not allow write-access to any 1389 columnar object in the row." 1390 ::= { teLinkBandwidthEntry 5 } 1392 -- End of teLinkBandwidthTable 1394 -- Component Link Table 1396 componentLinkTable OBJECT-TYPE 1397 SYNTAX SEQUENCE OF ComponentLinkEntry 1398 MAX-ACCESS not-accessible 1399 STATUS current 1400 DESCRIPTION 1401 "This table specifies the component link parameters." 1402 ::= { teLinkObjects 5 } 1404 componentLinkEntry OBJECT-TYPE 1405 SYNTAX ComponentLinkEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "An entry in this table exists for each ifEntry that represents 1410 a component link. An ifEntry must exist in the ifTable 1411 before a componentLinkEntry is created with the 1412 corresponding ifIndex. ifEntry's ifType can be 1413 of any interface type which has been defined for TE Link 1414 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 1415 If an entry representing a component link is destroyed in the 1416 ifTable, then so is the corresponding entry in the 1417 componentLinkTable. The administrative and operational status 1418 values are controlled from the ifEntry." 1419 INDEX { ifIndex } 1420 ::= { componentLinkTable 1 } 1422 ComponentLinkEntry ::= SEQUENCE { 1423 componentLinkMaxResBandwidth TeLinkBandwidth, 1424 componentLinkPreferredProtection TeLinkProtection, 1425 componentLinkCurrentProtection TeLinkProtection, 1426 componentLinkRowStatus RowStatus, 1427 componentLinkStorageType StorageType 1428 } 1430 componentLinkMaxResBandwidth OBJECT-TYPE 1431 SYNTAX TeLinkBandwidth 1432 UNITS "bps" 1433 MAX-ACCESS read-create 1434 STATUS current 1435 DESCRIPTION 1436 "This attribute specifies the maximum reservable bandwidth on 1437 the component link." 1438 REFERENCE 1439 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1440 -- RFC Editor to fill in RFC number that will be assigned to 1441 -- [GMPLS-OSPF] 1442 ::= { componentLinkEntry 1 } 1444 componentLinkPreferredProtection OBJECT-TYPE 1445 SYNTAX TeLinkProtection 1446 MAX-ACCESS read-create 1447 STATUS current 1448 DESCRIPTION 1449 "This attribute specifies whether this component link is 1450 a primary or secondary entity." 1451 ::= { componentLinkEntry 2 } 1453 componentLinkCurrentProtection OBJECT-TYPE 1454 SYNTAX TeLinkProtection 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "This attribute specifies whether this component link is 1459 currently used as primary or secondary link." 1460 ::= { componentLinkEntry 3 } 1462 componentLinkRowStatus OBJECT-TYPE 1463 SYNTAX RowStatus 1464 MAX-ACCESS read-create 1465 STATUS current 1466 DESCRIPTION 1467 "This variable is used to create, modify, and/or 1468 delete a row in this table. No read-create object 1469 can be modified when componentLinkRowStatus is active(1)." 1470 ::= { componentLinkEntry 4 } 1472 componentLinkStorageType OBJECT-TYPE 1473 SYNTAX StorageType 1474 MAX-ACCESS read-create 1475 STATUS current 1476 DESCRIPTION 1477 "The storage type for this conceptual row in the 1478 componentLinkTable. Conceptual rows having the value 1479 'permanent' need not allow write-access to any 1480 columnar object in the row." 1481 ::= { componentLinkEntry 5 } 1483 -- End of componentLinkTable 1485 -- Component Link Descriptor Table 1487 componentLinkDescriptorTable OBJECT-TYPE 1488 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "This table specifies the interface switching capability 1493 descriptors associated with the component links." 1494 ::= { teLinkObjects 6 } 1496 componentLinkDescriptorEntry OBJECT-TYPE 1497 SYNTAX ComponentLinkDescriptorEntry 1498 MAX-ACCESS not-accessible 1499 STATUS current 1500 DESCRIPTION 1501 "An entry in this table is created for every component link 1502 descriptor. An ifEntry in the ifTable must exist before a 1503 componentLinkDescriptorEntry using the same ifIndex is created. 1504 ifEntry's ifType can be of any interface type which has been 1505 defined for TE Link interworking. Examples include ATM, Frame 1506 Relay, Ethernet, etc. If a component link entry in the ifTable 1507 is destroyed, then so are all entries in the 1508 componentLinkDescriptorTable that use the ifIndex of this 1509 component link." 1510 INDEX { ifIndex, componentLinkDescrId } 1511 ::= { componentLinkDescriptorTable 1 } 1513 ComponentLinkDescriptorEntry ::= SEQUENCE { 1514 componentLinkDescrId Unsigned32, 1515 componentLinkDescrSwitchingCapability TeLinkSwitchingCapability, 1516 componentLinkDescrEncodingType TeLinkEncodingType, 1517 componentLinkDescrMinLspBandwidth TeLinkBandwidth, 1518 componentLinkDescrMaxLspBandwidthPrio0 TeLinkBandwidth, 1519 componentLinkDescrMaxLspBandwidthPrio1 TeLinkBandwidth, 1520 componentLinkDescrMaxLspBandwidthPrio2 TeLinkBandwidth, 1521 componentLinkDescrMaxLspBandwidthPrio3 TeLinkBandwidth, 1522 componentLinkDescrMaxLspBandwidthPrio4 TeLinkBandwidth, 1523 componentLinkDescrMaxLspBandwidthPrio5 TeLinkBandwidth, 1524 componentLinkDescrMaxLspBandwidthPrio6 TeLinkBandwidth, 1525 componentLinkDescrMaxLspBandwidthPrio7 TeLinkBandwidth, 1526 componentLinkDescrInterfaceMtu Unsigned32, 1527 componentLinkDescrIndication TeLinkSonetSdhIndication, 1528 componentLinkDescrRowStatus RowStatus, 1529 componentLinkDescrStorageType StorageType 1530 } 1532 componentLinkDescrId OBJECT-TYPE 1533 SYNTAX Unsigned32 (1..4294967295) 1534 MAX-ACCESS not-accessible 1535 STATUS current 1536 DESCRIPTION 1537 "This object specifies the link descriptor identifier." 1538 ::= { componentLinkDescriptorEntry 1 } 1540 componentLinkDescrSwitchingCapability OBJECT-TYPE 1541 SYNTAX TeLinkSwitchingCapability 1542 MAX-ACCESS read-create 1543 STATUS current 1544 DESCRIPTION 1545 "This attribute specifies link multiplexing capabilities of the 1546 component link." 1547 REFERENCE 1548 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1549 -- RFC Editor to fill in RFC number that will be assigned to 1550 -- [GMPLS-OSPF] 1551 ::= { componentLinkDescriptorEntry 2 } 1553 componentLinkDescrEncodingType OBJECT-TYPE 1554 SYNTAX TeLinkEncodingType 1555 MAX-ACCESS read-create 1556 STATUS current 1557 DESCRIPTION 1558 "This attribute specifies the component link encoding type." 1559 REFERENCE 1560 "Generalized MPLS Signaling Functional Description, RFC 3471" 1561 ::= { componentLinkDescriptorEntry 3 } 1563 componentLinkDescrMinLspBandwidth OBJECT-TYPE 1564 SYNTAX TeLinkBandwidth 1565 UNITS "bps" 1566 MAX-ACCESS read-create 1567 STATUS current 1568 DESCRIPTION 1569 "This attribute specifies the minimum LSP bandwidth on 1570 the component link." 1571 REFERENCE 1572 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1573 -- RFC Editor to fill in RFC number that will be assigned to 1574 -- [GMPLS-OSPF] 1575 ::= { componentLinkDescriptorEntry 4 } 1577 componentLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE 1578 SYNTAX TeLinkBandwidth 1579 UNITS "bps" 1580 MAX-ACCESS read-create 1581 STATUS current 1582 DESCRIPTION 1583 "This attribute specifies the maximum LSP bandwidth at 1584 priority 0 on 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 5 } 1591 componentLinkDescrMaxLspBandwidthPrio1 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 1 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 6 } 1605 componentLinkDescrMaxLspBandwidthPrio2 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 2 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 7 } 1619 componentLinkDescrMaxLspBandwidthPrio3 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 3 on the component link." 1627 REFERENCE 1628 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1629 -- RFC Editor to fill in RFC number that will be assigned to 1630 -- [GMPLS-OSPF] 1631 ::= { componentLinkDescriptorEntry 8 } 1633 componentLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE 1634 SYNTAX TeLinkBandwidth 1635 UNITS "bps" 1636 MAX-ACCESS read-create 1637 STATUS current 1638 DESCRIPTION 1639 "This attribute specifies the maximum LSP bandwidth at 1640 priority 4 on the component link." 1641 REFERENCE 1642 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1643 -- RFC Editor to fill in RFC number that will be assigned to 1644 -- [GMPLS-OSPF] 1645 ::= { componentLinkDescriptorEntry 9 } 1647 componentLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE 1648 SYNTAX TeLinkBandwidth 1649 UNITS "thousand bps" 1650 MAX-ACCESS read-create 1651 STATUS current 1652 DESCRIPTION 1653 "This attribute specifies the maximum LSP bandwidth at 1654 priority 5 on the component link." 1655 REFERENCE 1656 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1657 -- RFC Editor to fill in RFC number that will be assigned to 1658 -- [GMPLS-OSPF] 1659 ::= { componentLinkDescriptorEntry 10 } 1661 componentLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE 1662 SYNTAX TeLinkBandwidth 1663 UNITS "bps" 1664 MAX-ACCESS read-create 1665 STATUS current 1666 DESCRIPTION 1667 "This attribute specifies the maximum LSP bandwidth at 1668 priority 6 on the component link." 1669 REFERENCE 1670 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1671 -- RFC Editor to fill in RFC number that will be assigned to 1672 -- [GMPLS-OSPF] 1673 ::= { componentLinkDescriptorEntry 11 } 1675 componentLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE 1676 SYNTAX TeLinkBandwidth 1677 UNITS "bps" 1678 MAX-ACCESS read-create 1679 STATUS current 1680 DESCRIPTION 1681 "This attribute specifies the maximum LSP bandwidth at 1682 priority 7 on the component link." 1683 REFERENCE 1684 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1685 -- RFC Editor to fill in RFC number that will be assigned to 1686 -- [GMPLS-OSPF] 1687 ::= { componentLinkDescriptorEntry 12 } 1689 componentLinkDescrInterfaceMtu OBJECT-TYPE 1690 SYNTAX Unsigned32 (1..65535) 1691 MAX-ACCESS read-create 1692 STATUS current 1693 DESCRIPTION 1694 "This attribute specifies the interface MTU for the component 1695 link descriptor." 1696 REFERENCE 1697 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1698 -- RFC Editor to fill in RFC number that will be assigned to 1699 -- [GMPLS-OSPF] 1700 ::= { componentLinkDescriptorEntry 13 } 1702 componentLinkDescrIndication OBJECT-TYPE 1703 SYNTAX TeLinkSonetSdhIndication 1704 MAX-ACCESS read-create 1705 STATUS current 1706 DESCRIPTION 1707 "This attribute specifies whether this interface supports 1708 Standard or Arbitrary SONET/SDH." 1709 REFERENCE 1710 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1711 -- RFC Editor to fill in RFC number that will be assigned to 1712 -- [GMPLS-OSPF] 1713 ::= { componentLinkDescriptorEntry 14 } 1715 componentLinkDescrRowStatus OBJECT-TYPE 1716 SYNTAX RowStatus 1717 MAX-ACCESS read-create 1718 STATUS current 1719 DESCRIPTION 1720 "This variable is used to create, modify, and/or 1721 delete a row in this table. No read-create object 1722 can be modified when componentLinkDescrRowStatus 1723 is active(1)." 1724 ::= { componentLinkDescriptorEntry 15 } 1726 componentLinkDescrStorageType OBJECT-TYPE 1727 SYNTAX StorageType 1728 MAX-ACCESS read-create 1729 STATUS current 1730 DESCRIPTION 1731 "The storage type for this conceptual row in the 1732 componentLinkDescriptorTable. Conceptual rows 1733 having the value 'permanent' need not allow write-access 1734 to any columnar object in the row." 1735 ::= { componentLinkDescriptorEntry 16 } 1737 -- End of componentLinkDescriptorTable 1739 -- Component Link Bandwidth Table 1741 componentLinkBandwidthTable OBJECT-TYPE 1742 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1743 MAX-ACCESS not-accessible 1744 STATUS current 1745 DESCRIPTION 1746 "This table specifies the priority-based bandwidth 1747 for component links." 1748 ::= { teLinkObjects 7 } 1750 componentLinkBandwidthEntry OBJECT-TYPE 1751 SYNTAX ComponentLinkBandwidthEntry 1752 MAX-ACCESS not-accessible 1753 STATUS current 1754 DESCRIPTION 1755 "An entry in this table contains information about 1756 the priority-based bandwidth on component links. 1757 An ifEntry in the ifTable must exist before a 1758 componentLinkBandwidthEntry using the same ifIndex is 1759 created. ifEntry's ifType can be of any interface type which 1760 has been defined for TE Link interworking. Examples include 1761 ATM, Frame Relay, Ethernet, etc. If a component link entry in 1762 the ifTable is destroyed, then so are all entries in the 1763 componentLinkBandwidthTable that use the ifIndex of 1764 this component link." 1766 INDEX { ifIndex, componentLinkBandwidthPriority } 1767 ::= { componentLinkBandwidthTable 1 } 1769 ComponentLinkBandwidthEntry ::= SEQUENCE { 1770 componentLinkBandwidthPriority TeLinkPriority, 1771 componentLinkBandwidthUnreserved TeLinkBandwidth, 1772 componentLinkBandwidthRowStatus RowStatus, 1773 componentLinkBandwidthStorageType StorageType 1774 } 1776 componentLinkBandwidthPriority OBJECT-TYPE 1777 SYNTAX TeLinkPriority 1778 MAX-ACCESS not-accessible 1779 STATUS current 1780 DESCRIPTION 1781 "This attribute specifies the priority. A value of 0 is valid 1782 as specified in the 'Traffic Engineering Extensions to OSPF 1783 Version 2' document." 1784 REFERENCE 1785 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1786 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1787 -- RFC Editor to fill in RFC number that will be assigned to 1788 -- [GMPLS-OSPF] and [OSPF] 1789 ::= { componentLinkBandwidthEntry 1 } 1791 componentLinkBandwidthUnreserved OBJECT-TYPE 1792 SYNTAX TeLinkBandwidth 1793 UNITS "bps" 1794 MAX-ACCESS read-only 1795 STATUS current 1796 DESCRIPTION 1797 "This attribute specifies the component link unreserved 1798 bandwidth at priority p." 1799 REFERENCE 1800 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1801 -- RFC Editor to fill in RFC number that will be assigned to 1802 -- [GMPLS-OSPF] 1803 ::= { componentLinkBandwidthEntry 2 } 1805 componentLinkBandwidthRowStatus OBJECT-TYPE 1806 SYNTAX RowStatus 1807 MAX-ACCESS read-create 1808 STATUS current 1809 DESCRIPTION 1810 "This variable is used to create, modify, and/or 1811 delete a row in this table. No read-create object can 1812 be modified when componentLinkBandwidthRowStatus is 1813 active(1)." 1815 ::= { componentLinkBandwidthEntry 4 } 1817 componentLinkBandwidthStorageType OBJECT-TYPE 1818 SYNTAX StorageType 1819 MAX-ACCESS read-create 1820 STATUS current 1821 DESCRIPTION 1822 "The storage type for this conceptual row in the 1823 componentLinkBandwidthTable. Conceptual rows 1824 having the value 'permanent' need not allow write-access 1825 to any columnar object in the row." 1826 ::= { componentLinkBandwidthEntry 5 } 1828 -- End of componentLinkBandwidthTable 1830 -- Module compliance 1832 teLinkCompliances 1833 OBJECT IDENTIFIER ::= { teLinkConformance 1 } 1835 teLinkGroups 1836 OBJECT IDENTIFIER ::= { teLinkConformance 2 } 1838 teLinkModuleFullCompliance MODULE-COMPLIANCE 1839 STATUS current 1840 DESCRIPTION 1841 "Compliance statement for agents that support read-create 1842 so that both configuration and monitoring of TE links can 1843 be accomplished via this MIB module." 1844 MODULE -- this module 1846 MANDATORY-GROUPS { teLinkGroup, 1847 teLinkBandwidthGroup, 1848 componentLinkBandwidthGroup } 1850 GROUP teLinkSrlgGroup 1851 DESCRIPTION 1852 "This group is mandatory for G-MPLS enabled devices." 1854 GROUP teLinkPscGroup 1855 DESCRIPTION 1856 "This group is mandatory for devices that support 1857 packet switching capability." 1859 GROUP teLinkTdmGroup 1860 DESCRIPTION 1861 "This group is mandatory for devices that support TDM 1862 switching capability." 1864 -- teLinkTable 1866 OBJECT teLinkAddressType 1867 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1868 DESCRIPTION 1869 "Only ipv4(1) and ipv6(2) address types need to be 1870 supported for numbered links. For unnumbered links, the 1871 unknown(0) address type needs to be supported." 1873 OBJECT teLinkLocalIpAddr 1874 SYNTAX InetAddress (SIZE(0|4|16)) 1875 DESCRIPTION 1876 "Size of TE link IP address depends on type of TE link. 1877 TE link IP address size is zero if link is unnumbered, 1878 four if link IP address is IPv4 and sixteen if link IP 1879 address is IPv6." 1881 OBJECT teLinkRemoteIpAddr 1882 SYNTAX InetAddress (SIZE(0|4|16)) 1883 DESCRIPTION 1884 "Size of TE link IP address depends on type of TE link. 1885 TE link IP address size is zero if link is unnumbered, 1886 four if link IP address is IPv4 and sixteen if link IP 1887 address is IPv6." 1889 OBJECT teLinkRowStatus 1890 SYNTAX RowStatus { active(1), notInService(2) } 1891 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1892 createAndGo(4), destroy(6) } 1893 DESCRIPTION 1894 "Support for notReady(3) and createAndWait(5) is 1895 not required." 1897 -- teLinkDescriptorTable 1899 OBJECT teLinkDescrRowStatus 1900 SYNTAX RowStatus { active(1), notInService(2) } 1901 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1902 createAndGo(4), destroy(6) } 1903 DESCRIPTION 1904 "Support for notReady(3) and createAndWait(5) is 1905 not required." 1907 -- teLinkSrlgTable 1909 OBJECT teLinkSrlgRowStatus 1910 SYNTAX RowStatus { active(1), notInService(2) } 1911 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1912 createAndGo(4), destroy(6) } 1913 DESCRIPTION 1914 "Support for notReady(3) and createAndWait(5) is 1915 not required." 1917 -- teLinkBandwidthTable 1919 OBJECT teLinkBandwidthRowStatus 1920 SYNTAX RowStatus { active(1), notInService(2) } 1921 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1922 createAndGo(4), destroy(6) } 1923 DESCRIPTION 1924 "Support for notReady(3) and createAndWait(5) is 1925 not required." 1927 -- componentLinkTable 1929 OBJECT componentLinkRowStatus 1930 SYNTAX RowStatus { active(1), notInService(2) } 1931 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1932 createAndGo(4), destroy(6) } 1933 DESCRIPTION 1934 "Support for notReady(3) and createAndWait(5) is 1935 not required." 1937 -- componentLinkDescriptorTable 1939 OBJECT componentLinkDescrRowStatus 1940 SYNTAX RowStatus { active(1), notInService(2) } 1941 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1942 createAndGo(4), destroy(6) } 1943 DESCRIPTION 1944 "Support for notReady(3) and createAndWait(5) is 1945 not required." 1947 -- componentLinkBandwidthTable 1949 OBJECT componentLinkBandwidthRowStatus 1950 SYNTAX RowStatus { active(1), notInService(2) } 1951 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1952 createAndGo(4), destroy(6) } 1953 DESCRIPTION 1954 "Support for notReady(3) and createAndWait(5) is 1955 not required." 1957 ::= { teLinkCompliances 1 } 1959 teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE 1960 STATUS current 1961 DESCRIPTION 1962 "Compliance statement for agents that support the 1963 monitoring of TE link MIB module." 1964 MODULE -- this module 1966 MANDATORY-GROUPS { teLinkGroup, 1967 teLinkBandwidthGroup, 1968 componentLinkBandwidthGroup } 1970 GROUP teLinkSrlgGroup 1971 DESCRIPTION 1972 "This group is mandatory for G-MPLS enabled devices." 1974 GROUP teLinkPscGroup 1975 DESCRIPTION 1976 "This group is mandatory for devices that support 1977 packet switching capability." 1979 GROUP teLinkTdmGroup 1980 DESCRIPTION 1981 "This group is mandatory for devices that support TDM 1982 switching capability." 1984 -- teLinkTable 1986 OBJECT teLinkAddressType 1987 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1988 MIN-ACCESS read-only 1989 DESCRIPTION 1990 "Only ipv4(1) and ipv6(2) address types need to be 1991 supported for numbered links. For unnumbered links, the 1992 unknown(0) address type needs to be supported." 1994 OBJECT teLinkLocalIpAddr 1995 SYNTAX InetAddress (SIZE(0|4|16)) 1996 MIN-ACCESS read-only 1997 DESCRIPTION 1998 "Size of TE link IP address depends on type of TE link. 1999 TE link IP address size is zero if link is unnumbered, 2000 four if link IP address is IPv4 and sixteen if link IP 2001 address is IPv6." 2003 OBJECT teLinkRemoteIpAddr 2004 SYNTAX InetAddress (SIZE(0|4|16)) 2005 MIN-ACCESS read-only 2006 DESCRIPTION 2007 "Size of TE link IP address depends on type of TE link. 2008 TE link IP address size is zero if link is unnumbered, 2009 four if link IP address is IPv4 and sixteen if link IP 2010 address is IPv6." 2012 OBJECT teLinkProtectionType 2013 MIN-ACCESS read-only 2014 DESCRIPTION 2015 "Write access is not required." 2017 OBJECT teLinkWorkingPriority 2018 MIN-ACCESS read-only 2019 DESCRIPTION 2020 "Write access is not required." 2022 OBJECT teLinkRowStatus 2023 SYNTAX RowStatus { active(1) } 2024 MIN-ACCESS read-only 2025 DESCRIPTION 2026 "Write access is not required and active(1) is the 2027 only status that needs to be supported." 2029 OBJECT teLinkStorageType 2030 MIN-ACCESS read-only 2031 DESCRIPTION 2032 "Write access is not required." 2034 -- teLinkDescriptorTable 2036 OBJECT teLinkDescrSwitchingCapability 2037 MIN-ACCESS read-only 2038 DESCRIPTION 2039 "Write access is not required." 2041 OBJECT teLinkDescrEncodingType 2042 MIN-ACCESS read-only 2043 DESCRIPTION 2044 "Write access is not required." 2046 OBJECT teLinkDescrMinLspBandwidth 2047 MIN-ACCESS read-only 2048 DESCRIPTION 2049 "Write access is not required." 2051 OBJECT teLinkDescrMaxLspBandwidthPrio0 2052 MIN-ACCESS read-only 2053 DESCRIPTION 2054 "Write access is not required." 2056 OBJECT teLinkDescrMaxLspBandwidthPrio1 2057 MIN-ACCESS read-only 2058 DESCRIPTION 2059 "Write access is not required." 2061 OBJECT teLinkDescrMaxLspBandwidthPrio2 2062 MIN-ACCESS read-only 2063 DESCRIPTION 2064 "Write access is not required." 2066 OBJECT teLinkDescrMaxLspBandwidthPrio3 2067 MIN-ACCESS read-only 2068 DESCRIPTION 2069 "Write access is not required." 2071 OBJECT teLinkDescrMaxLspBandwidthPrio4 2072 MIN-ACCESS read-only 2073 DESCRIPTION 2074 "Write access is not required." 2076 OBJECT teLinkDescrMaxLspBandwidthPrio5 2077 MIN-ACCESS read-only 2078 DESCRIPTION 2079 "Write access is not required." 2081 OBJECT teLinkDescrMaxLspBandwidthPrio6 2082 MIN-ACCESS read-only 2083 DESCRIPTION 2084 "Write access is not required." 2086 OBJECT teLinkDescrMaxLspBandwidthPrio7 2087 MIN-ACCESS read-only 2088 DESCRIPTION 2089 "Write access is not required." 2091 OBJECT teLinkDescrRowStatus 2092 SYNTAX RowStatus { active(1) } 2093 MIN-ACCESS read-only 2094 DESCRIPTION 2095 "Write access is not required and active(1) is the 2096 only status that needs to be supported." 2098 OBJECT teLinkDescrStorageType 2099 MIN-ACCESS read-only 2100 DESCRIPTION 2101 "Write access is not required." 2103 -- teLinkSrlgTable 2104 OBJECT teLinkSrlgRowStatus 2105 SYNTAX RowStatus { active(1) } 2106 MIN-ACCESS read-only 2107 DESCRIPTION 2108 "Write access is not required and active(1) is the 2109 only status that needs to be supported." 2111 OBJECT teLinkSrlgStorageType 2112 MIN-ACCESS read-only 2113 DESCRIPTION 2114 "Write access is not required." 2116 -- teLinkBandwidthTable 2118 OBJECT teLinkBandwidthRowStatus 2119 SYNTAX RowStatus { active(1) } 2120 MIN-ACCESS read-only 2121 DESCRIPTION 2122 "Write access is not required and active(1) is the 2123 only status that needs to be supported." 2125 OBJECT teLinkBandwidthStorageType 2126 MIN-ACCESS read-only 2127 DESCRIPTION 2128 "Write access is not required." 2130 -- componentLinkTable 2132 OBJECT componentLinkMaxResBandwidth 2133 MIN-ACCESS read-only 2134 DESCRIPTION 2135 "Write access is not required." 2137 OBJECT componentLinkPreferredProtection 2138 MIN-ACCESS read-only 2139 DESCRIPTION 2140 "Write access is not required." 2142 OBJECT componentLinkRowStatus 2143 SYNTAX RowStatus { active(1) } 2144 MIN-ACCESS read-only 2145 DESCRIPTION 2146 "Write access is not required and active(1) is the 2147 only status that needs to be supported." 2149 OBJECT componentLinkStorageType 2150 MIN-ACCESS read-only 2151 DESCRIPTION 2152 "Write access is not required." 2154 -- componentLinkDescriptorTable 2156 OBJECT componentLinkDescrSwitchingCapability 2157 MIN-ACCESS read-only 2158 DESCRIPTION 2159 "Write access is not required." 2161 OBJECT componentLinkDescrEncodingType 2162 MIN-ACCESS read-only 2163 DESCRIPTION 2164 "Write access is not required." 2166 OBJECT componentLinkDescrMinLspBandwidth 2167 MIN-ACCESS read-only 2168 DESCRIPTION 2169 "Write access is not required." 2171 OBJECT componentLinkDescrMaxLspBandwidthPrio0 2172 MIN-ACCESS read-only 2173 DESCRIPTION 2174 "Write access is not required." 2176 OBJECT componentLinkDescrMaxLspBandwidthPrio1 2177 MIN-ACCESS read-only 2178 DESCRIPTION 2179 "Write access is not required." 2181 OBJECT componentLinkDescrMaxLspBandwidthPrio2 2182 MIN-ACCESS read-only 2183 DESCRIPTION 2184 "Write access is not required." 2186 OBJECT componentLinkDescrMaxLspBandwidthPrio3 2187 MIN-ACCESS read-only 2188 DESCRIPTION 2189 "Write access is not required." 2191 OBJECT componentLinkDescrMaxLspBandwidthPrio4 2192 MIN-ACCESS read-only 2193 DESCRIPTION 2194 "Write access is not required." 2196 OBJECT componentLinkDescrMaxLspBandwidthPrio5 2197 MIN-ACCESS read-only 2198 DESCRIPTION 2199 "Write access is not required." 2201 OBJECT componentLinkDescrMaxLspBandwidthPrio6 2202 MIN-ACCESS read-only 2203 DESCRIPTION 2204 "Write access is not required." 2206 OBJECT componentLinkDescrMaxLspBandwidthPrio7 2207 MIN-ACCESS read-only 2208 DESCRIPTION 2209 "Write access is not required." 2211 OBJECT componentLinkDescrInterfaceMtu 2212 MIN-ACCESS read-only 2213 DESCRIPTION 2214 "Write access is not required." 2216 OBJECT componentLinkDescrIndication 2217 MIN-ACCESS read-only 2218 DESCRIPTION 2219 "Write access is not required." 2221 OBJECT componentLinkDescrRowStatus 2222 SYNTAX RowStatus { active(1) } 2223 MIN-ACCESS read-only 2224 DESCRIPTION 2225 "Write access is not required and active(1) is the 2226 only status that needs to be supported." 2228 OBJECT componentLinkDescrStorageType 2229 MIN-ACCESS read-only 2230 DESCRIPTION 2231 "Write access is not required." 2233 -- componentLinkBandwidthTable 2235 OBJECT componentLinkBandwidthRowStatus 2236 SYNTAX RowStatus { active(1) } 2237 MIN-ACCESS read-only 2238 DESCRIPTION 2239 "Write access is not required and active(1) is the 2240 only status that needs to be supported." 2242 OBJECT componentLinkBandwidthStorageType 2243 MIN-ACCESS read-only 2244 DESCRIPTION 2245 "Write access is not required." 2247 ::= { teLinkCompliances 2 } 2249 -- Units of conformance 2251 teLinkGroup OBJECT-GROUP 2252 OBJECTS { teLinkAddressType, 2253 teLinkLocalIpAddr, 2254 teLinkRemoteIpAddr, 2255 teLinkMetric, 2256 teLinkProtectionType, 2257 teLinkWorkingPriority, 2258 teLinkResourceClass, 2259 teLinkIncomingIfId, 2260 teLinkOutgoingIfId, 2261 teLinkRowStatus, 2262 teLinkStorageType, 2263 teLinkDescrSwitchingCapability, 2264 teLinkDescrEncodingType, 2265 teLinkDescrRowStatus, 2266 teLinkDescrStorageType, 2267 componentLinkPreferredProtection, 2268 componentLinkCurrentProtection, 2269 componentLinkRowStatus, 2270 componentLinkStorageType, 2271 componentLinkDescrSwitchingCapability, 2272 componentLinkDescrEncodingType, 2273 componentLinkDescrRowStatus, 2274 componentLinkDescrStorageType 2275 } 2277 STATUS current 2278 DESCRIPTION 2279 "Collection of objects needed for the management of 2280 resources associated with TE links." 2281 ::= { teLinkGroups 1 } 2283 teLinkSrlgGroup OBJECT-GROUP 2284 OBJECTS { teLinkSrlgRowStatus, 2285 teLinkSrlgStorageType 2286 } 2288 STATUS current 2289 DESCRIPTION 2290 "Collection of objects needed for the management of 2291 SRLG resources associated with TE links." 2292 ::= { teLinkGroups 2 } 2294 teLinkBandwidthGroup OBJECT-GROUP 2295 OBJECTS { teLinkMaximumReservableBandwidth, 2296 teLinkDescrMaxLspBandwidthPrio0, 2297 teLinkDescrMaxLspBandwidthPrio1, 2298 teLinkDescrMaxLspBandwidthPrio2, 2299 teLinkDescrMaxLspBandwidthPrio3, 2300 teLinkDescrMaxLspBandwidthPrio4, 2301 teLinkDescrMaxLspBandwidthPrio5, 2302 teLinkDescrMaxLspBandwidthPrio6, 2303 teLinkDescrMaxLspBandwidthPrio7, 2304 teLinkBandwidthUnreserved, 2305 teLinkBandwidthRowStatus, 2306 teLinkBandwidthStorageType 2307 } 2309 STATUS current 2310 DESCRIPTION 2311 "Collection of objects needed for the management of 2312 the bandwidth resources associated with TE links and 2313 component links." 2314 ::= { teLinkGroups 3 } 2316 componentLinkBandwidthGroup OBJECT-GROUP 2317 OBJECTS { componentLinkMaxResBandwidth, 2318 componentLinkDescrMaxLspBandwidthPrio0, 2319 componentLinkDescrMaxLspBandwidthPrio1, 2320 componentLinkDescrMaxLspBandwidthPrio2, 2321 componentLinkDescrMaxLspBandwidthPrio3, 2322 componentLinkDescrMaxLspBandwidthPrio4, 2323 componentLinkDescrMaxLspBandwidthPrio5, 2324 componentLinkDescrMaxLspBandwidthPrio6, 2325 componentLinkDescrMaxLspBandwidthPrio7, 2326 componentLinkBandwidthUnreserved, 2327 componentLinkBandwidthRowStatus, 2328 componentLinkBandwidthStorageType 2329 } 2331 STATUS current 2332 DESCRIPTION 2333 "Collection of objects needed for the management of the 2334 bandwidth parameters associated with component links." 2335 ::= { teLinkGroups 4 } 2337 teLinkPscGroup OBJECT-GROUP 2338 OBJECTS { teLinkDescrMinLspBandwidth, 2339 teLinkDescrInterfaceMtu, 2340 componentLinkDescrMinLspBandwidth, 2341 componentLinkDescrInterfaceMtu 2342 } 2344 STATUS current 2345 DESCRIPTION 2346 "Collection of objects needed for devices that are 2347 packet switch capable." 2348 ::= { teLinkGroups 5 } 2350 teLinkTdmGroup OBJECT-GROUP 2351 OBJECTS { teLinkDescrMinLspBandwidth, 2352 teLinkDescrIndication, 2353 componentLinkDescrMinLspBandwidth, 2354 componentLinkDescrIndication 2355 } 2357 STATUS current 2358 DESCRIPTION 2359 "Collection of objects needed for devices that are 2360 TDM switching capable." 2361 ::= { teLinkGroups 6 } 2363 -- End of TE-LINK-STD-MIB 2364 END 2366 10. Intellectual Property Considerations 2368 The IETF takes no position regarding the validity or scope of any 2369 intellectual property or other rights that might be claimed to 2370 pertain to the implementation or use of the technology described in 2371 this document or the extent to which any license under such rights 2372 might or might not be available; neither does it represent that it 2373 has made any effort to identify any such rights. Information on the 2374 IETF's procedures with respect to rights in standards-track and 2375 standards-related documentation can be found in BCP-11. Copies of 2376 claims of rights made available for publication and any assurances of 2377 licenses to be made available, or the result of an attempt made to 2378 obtain a general license or permission for the use of such 2379 proprietary rights by implementers or users of this specification can 2380 be obtained from the IETF Secretariat. 2382 The IETF invites any interested party to bring to its attention any 2383 copyrights, patents or patent applications, or other proprietary 2384 rights which may cover technology that may be required to practice 2385 this standard. Please address the information to the IETF Executive 2386 Director. 2388 11. Security Considerations 2390 There are a number of management objects defined in this MIB module 2391 with a MAX-ACCESS clause of read-write and/or read-create. Such 2392 objects may be considered sensitive or vulnerable in some network 2393 environments. The support for SET operations in a non-secure 2394 environment without proper protection can have a negative effect on 2395 network operations. These are the tables and objects and their 2396 sensitivity/vulnerability: 2398 - All the tables in this MIB module have routing information in 2399 them and so they all have the same security attributes. 2400 Unauthorized changes to attributes of these tables can disrupt 2401 resource allocation in the network. 2403 Some of the readable objects in this MIB module (i.e., objects with a 2404 MAX-ACCESS other than not-accessible) may be considered sensitive or 2405 vulnerable in some network environments. It is thus important to 2406 control even GET and/or NOTIFY access to these objects and possibly 2407 to even encrypt the values of these objects when sending them over 2408 the network via SNMP. These are the tables and objects and their 2409 sensitivity/vulnerability: 2411 - IP address entries in the teLinkTable (teLinkLocalIpAddr and 2412 teLinkRemoteIpAddr) may reveal the internals of a network provider 2413 IP address space. 2415 SNMP versions prior to SNMPv3 did not include adequate security. 2416 Even if the network itself is secure (for example by using IPSec), 2417 even then, there is no control as to who on the secure network is 2418 allowed to access and GET/SET (read/change/create/delete) the objects 2419 in this MIB module. 2421 It is RECOMMENDED that implementers consider the security features as 2422 provided by the SNMPv3 framework (see [RFC3410], section 8), 2423 including full support for the SNMPv3 cryptographic mechanisms (for 2424 authentication and privacy). 2426 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2427 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2428 enable cryptographic security. It is then a customer/operator 2429 responsibility to ensure that the SNMP entity giving access to an 2430 instance of this MIB module is properly configured to give access to 2431 the objects only to those principals (users) that have legitimate 2432 rights to indeed GET or SET (change/create/delete) them. 2434 12. Acknowledgments 2436 The authors would like to acknowledge the contribution of Dmitry 2437 Ryumkin. 2439 13. References 2441 13.1. Normative References 2443 [IEEE] IEEE, "IEEE Standard for Binary Floating-Point 2444 Arithmetic", Standard 754-1985, 1985 2445 (ISBN 1-5593-7653-8). 2447 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2448 Requirement Levels", BCP 14, RFC 2119, March 1997. 2450 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2451 J., Rose, M., and S. Waldbusser, "Structure of 2452 Management Information Version 2 (SMIv2)", STD 58, 2453 RFC 2578, April 1999. 2455 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2456 J., Rose, M., and S. Waldbusser, "Textual Conventions 2457 for SMIv2", STD 58, RFC 2579, April 1999. 2459 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2460 J., Rose, M., and Waldbusser, S., "Conformance 2461 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2463 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2464 Group MIB", RFC 2863, June 2000. 2466 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 2467 Shoenwaelder, J., "Textual Conventions for Internet 2468 Network Addresses", RFC 3291, May 2002. 2470 [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., 2471 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2472 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2473 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2474 "Generalized MPLS Signaling Functional Description", 2475 RFC 3471, January 2003. 2477 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2478 "Link Bundling in MPLS Traffic Engineering", 2479 Internet Draft , 2480 July 2002. 2482 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2483 Extensions in Support of Generalized MPLS", Internet 2484 Draft , 2485 October 2003. 2487 [HIERARCHY] Kompella, K., Rekhter, Y., "LSP Hierarchy with 2488 Generalized MPLS TE", Internet Draft 2489 , 2490 September 2002. 2492 [IANAifType] "IANAifType MIB Module", 2493 http://www.iana.org/assignments/ianaiftype-mib. 2495 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2496 Rekhter, Y., Berger, L., Saha, D., 2497 Basak, D., Sandick, H., Zinin, A., 2498 Rajagopalan, B., and Ramamoorthi, S., 2499 "Link Management Protocol", 2500 Internet Draft , 2501 October 2003. 2503 [OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic 2504 Engineering Extensions to OSPF", Internet Draft 2505 , June 2003. 2507 [ROUTING] Kompella, K., Rekhter, Y., "Routing Extensions in 2508 Support of Generalized MPLS", Internet Draft 2509 , October 2003. 2511 13.2. Informative References 2513 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2514 "Introduction and Applicability Statements for 2515 Internet-Standard Management Framework", RFC 3410, 2516 December 2002. 2518 [GMPLS-ARCH] Ashwood-Smith, P., Awduche, D., 2519 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2520 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2521 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2522 Lang, J., Liaw, Mannie, E., F., Nadeau, T., Ong, L., 2523 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2524 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2525 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2526 Zinin, A., "Generalized Multi-Protocol Label Switching 2527 (GMPLS) Architecture", Internet Draft 2528 , 2529 May 2003. 2531 14. Authors' Addresses 2533 Martin Dubuc Thomas D. Nadeau 2534 Email: dubuc.consulting@rogers.com Cisco Systems, Inc. 2535 300 Apollo Drive 2536 Chelmsford, MA 01824 2537 Phone: +1-978-244-3051 2538 Email: tnadeau@cisco.com 2540 Sudheer Dharanikota Jonathan P. Lang 2541 Email: sudheer@ieee.org Rincon Networks, Inc. 2542 110 El Paseo 2543 Santa Barbara, CA 93101 2544 Email: jplang@ieee.org 2546 15. Full Copyright Statement 2548 Copyright (C) The Internet Society (2004). All Rights Reserved. 2550 This document and translations of it may be copied and furnished to 2551 others, and derivative works that comment on or otherwise explain it 2552 or assist in its implementation may be prepared, copied, published 2553 and distributed, in whole or in part, without restriction of any 2554 kind, provided that the above copyright notice and this paragraph are 2555 included on all such copies and derivative works. However, this 2556 document itself may not be modified in any way, such as by removing 2557 the copyright notice or references to the Internet Society or other 2558 Internet organizations, except as needed for the purpose of 2559 developing Internet standards in which case the procedures for 2560 copyrights defined in the Internet Standards process must be 2561 followed, or as required to translate it into languages other than 2562 English. 2564 The limited permissions granted above are perpetual and will not be 2565 revoked by the Internet Society or its successors or assigns. This 2566 document and the information contained herein is provided on an "AS 2567 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2568 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2569 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2570 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2571 OR FITNESS FOR A PARTICULAR PURPOSE.