idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-14.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2966. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2939. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2946. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2952. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: When an entry is present in gmplsTunnelTable for a tunnel, gmplsTunnelPathComp MUST be used and any corresponding mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable MUST be ignored and SHOULD not be set. -- 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 (April 2006) is 6580 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) == Missing Reference: 'RCF2205' is mentioned on line 502, but not defined == Missing Reference: 'RFC2434' is mentioned on line 2395, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2205' is defined on line 2792, but no explicit reference was found in the text == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-14 Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Working Group Thomas D. Nadeau, Ed. 2 Internet Draft Cisco Systems, Inc. 3 Proposed Status: Standards Track 4 Expires: September 2006 Adrian Farrel, Ed. 5 Old Dog Consulting 7 April 2006 9 Generalized Multiprotocol Label Switching (GMPLS) Traffic 10 Engineering Management Information Base 12 draft-ietf-ccamp-gmpls-te-mib-14.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 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 Generalized 42 Multiprotocol Label Switching (GMPLS) based traffic engineering. 44 Table of Contents 46 1. Introduction ........................................... 2 47 1.1. Migration Strategy ................................... 3 48 2. Terminology ............................................ 3 49 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 51 3. The Internet-Standard Management Framework ............. 4 52 4. Outline ................................................ 4 53 4.1. Summary of GMPLS Traffic Engineering MIB Module ...... 4 54 5. Brief Description of GMPLS TE MIB Objects .............. 5 55 5.1. gmplsTunnelTable ..................................... 5 56 5.2. gmplsTunnelHopTable .................................. 6 57 5.3. gmplsTunnelARHopTable ................................ 6 58 5.4. gmplsTunnelCHopTable ................................. 6 59 5.5. gmplsTunnelErrorTable ................................ 6 60 5.6. gmplsTunnelReversePerfTable .......................... 6 61 5.7. Use of 32-bit and 64-bit Counters ................... 6 62 6. Cross-referencing to the gmplsLabelTable ............... 7 63 7. Example of GMPLS Tunnel Setup .......................... 7 64 8. GMPLS Traffic Engineering MIB Module .................. 11 65 9. Security Considerations ............................... 47 66 10. Acknowledgments ...................................... 48 67 11. IANA Considerations .................................. 48 68 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 49 69 11.2. Dependence on IANA MIB Modules ..................... 49 70 11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 49 71 12. References ........................................... 57 72 12.1. Normative References ............................... 57 73 12.2. Informative References ............................. 58 74 13. Contact Information .................................. 59 75 14. Intellectual Property Considerations ................. 59 76 15. Full Copyright Statement ............................. 60 78 1. Introduction 80 This memo defines a portion of the Management Information Base (MIB) 81 for use with network management protocols in the Internet community. 82 In particular, it describes managed objects for modeling 83 Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based 84 traffic engineering. The tables and objects defined in this document 85 extend those defined in the equivalent document for MPLS traffic 86 engineering [RFC3812], and management of GMPLS traffic engineering is 87 built on management of MPLS traffic engineering. 89 The MIB modules in this document should be used in conjunction with 90 the companion document [GMPLSLSRMIB] for GMPLS based traffic 91 engineering configuration and management. 93 Comments should be made direct to the CCAMP mailing list at 94 ccamp@ops.ietf.org. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in BCP 14, RFC 2119, 99 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 101 reference [RFC2119]. 103 1.1. Migration Strategy 105 MPLS-TE LSPs may be modeled and managed using the MPLS-TE-STD-MIB 106 module [RFC3812]. 108 LSRs may be migrated to model and manage their TE LSPs using the MIB 109 modules in this document in order to migrate the LSRs to GMPLS 110 support, or to take advandtage of additional MIB objects defined in 111 these MIB modules that are applicable to MPLS-TE. 113 The GMPLS TE MIB module (GMPLS-TE-STD-MIB) defined in this document 114 extends the MPLS-TE-STD-MIB module [RFC3812] through a series of 115 augmentations and sparse augmentations of the MIB tables. The only 116 additions are for support of GMPLS or to support the increased 117 complexity of MPLS and GMPLS systems. 119 In order to migrate from MPLS-TE-STD-MIB support to GMPLS-TE-STD-MIB 120 support an implementation needs only to add support for the 121 additional tables and objects defined in GMPLS-TE-STD-MIB. The 122 gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an 123 MPLS-TE LSP tunnel to benefit from the additional objects and tables 124 of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols. 126 The companion document for modeling and managing GMPLS based LSRs 127 [GMPLSLSRMIB] extends the MPLS-LSR-STD-MIB module [RFC3813] with the 128 same intentions. 130 Textual conventions are defined in [RFC3811] and [GMPLSTCMIB]. 132 2. Terminology 134 This document uses terminology from the MPLS architecture document 135 [RFC3031], from the GMPLS architecture document [RFC3945], and from 136 the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used 137 terms are described next. 139 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 140 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 141 LSRs, each segment being associated with one GMPLS enabled interface. 142 These are also referred to as tunnel segments. 144 Additionally, at an intermediate LSR, we model a connection as 145 consisting of one or more in-segments and/or one or more 146 out-segments. The binding or interconnection between in-segments and 147 out-segments in performed using a cross-connect. 149 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 151 These segment and cross-connect objects are defined in the MPLS Label 152 Switch Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the 153 GMPLS Label Switch Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] for 154 the GMPLS-specific extensions to these objects. 156 3. The Internet-Standard Management Framework 158 For a detailed overview of the documents that describe the current 159 Internet-Standard Management Framework, please refer to section 7 of 160 RFC 3410 [RFC3410]. 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. MIB objects are generally 164 accessed through the Simple Network Management Protocol (SNMP). 165 Objects in the MIB are defined using the mechanisms defined in the 166 Structure of Management Information (SMI). This memo specifies a MIB 167 module that is compliant to the SMIv2, which is described in STD 58, 168 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 169 [RFC2580]. 171 4. Outline 173 Support for GMPLS traffic-engineered tunnels requires the following 174 configuration. 176 - Setting up tunnels with appropriate MPLS configuration parameters 177 using [RFC3812]. 178 - Extending the tunnels with GMPLS configuration parameters. 179 - Configuring tunnel loose and strict source routed hops. 181 These actions may need to be accompanied with corresponding actions 182 using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel 183 segments, if this is done manually. Also, the in-segment and 184 out-segment performance tables, mplsInSegmentPerfTable and 185 mplsOutSegmentPerfTable [RFC3813], should be used to determine 186 performance of the tunnels and tunnel segments although it should be 187 noted that those tables may not be appropriate for measuring 188 performance on some types of GMPLS links. 190 4.1. Summary of GMPLS Traffic Engineering MIB Module 192 The following tables contain MIB objects for performing the actions 193 listed above when they cannot be performed solely using MIB objects 194 defined in MPLS-TE-STD-MIB [RFC3812]. 196 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 197 tunnel configuration parameters. 199 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 201 - Tunnel specified, actual, and computed hop tables 202 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 203 gmplsTunnelCHopTable) for providing additional configuration of 204 strict and loose source routed tunnel hops. 205 - Performance and error reporting tables (gmplsTunnelReversePerfTable 206 and gmplsTunnelErrorTable). 208 These tables are described in the subsequent sections. 210 Additionally, the GMPLS-TE-STD-MIB module contains a new 211 notification. 213 - The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be used 214 for all GMPLS tunnels in place of the mplsTunnelDown notification 215 defined in [RFC3812]. An implementation must not issue both the 216 gmplsTunnelDown and the mplsTunnelDown notifications for the same 217 event. As well as indicating that a tunnel has transitioned to 218 operational down state, this new notification indicates the cause 219 of the failure. 221 5. Brief Description of GMPLS TE MIB Objects 223 The objects described in this section support the functionality 224 described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables 225 support both manually configured and signaled tunnels. 227 5.1. gmplsTunnelTable 229 The gmplsTunnelTable extends the MPLS traffic engineering MIB module 230 (MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created 231 between an LSR and a remote endpoint, and existing GMPLS tunnels to 232 be reconfigured or removed. 234 Note that we only support point-to-point tunnel segments, although 235 multi-point-to-point and point-to-multi-point connections are 236 supported by an LSR acting as a cross-connect. 238 Each tunnel can thus have one out-segment originating at an LSR 239 and/or one in-segment terminating at that LSR. 241 Three objects within this table utilize enumerations in order to map 242 to enumerations that are used in GMPLS signaling. In order to protect 243 the GMPLS-TE-STD-MIB module from changes (in particular, extensions) 244 to the range of enumerations supported by the signaling protocols, 245 these MIB objects use Textual Conventions with values maintained by 246 IANA. For further details, see the IANA Considerations section of 247 this document. 249 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 251 5.2. gmplsTunnelHopTable 253 The gmplsTunnelHopTable is used to indicate additional parameters for 254 the hops, strict or loose, of a GMPLS tunnel defined in 255 gmplsTunnelTable, when it is established using signaling. Multiple 256 tunnels may share hops by pointing to the same entry in this table. 258 5.3. gmplsTunnelARHopTable 260 The gmplsTunnelARHopTable is used to indicate the actual hops 261 traversed by a tunnel as reported by the signaling protocol after the 262 tunnel is setup. The support of this table is optional since not all 263 GMPLS signaling protocols support this feature. 265 5.4. gmplsTunnelCHopTable 267 The gmplsTunnelCHopTable lists the actual hops computed by a 268 constraint-based routing algorithm based on the gmplsTunnelHopTable. 269 The support of this table is optional since not all implementations 270 support computation of hop lists using a constraint-based routing 271 protocol. 273 5.5. gmplsTunnelErrorTable 275 The gmplsTunnelErrorTable provides access to information about the 276 last error that occurred on each tunnel known about by the MIB. It 277 indicates the nature of the error, when and how it was reported and 278 can give recovery advice through an admin string. 280 5.6. gmplsTunnelReversePerfTable 282 gmplsTunnelReversePerfTable provides additional counters to measure 283 the performance of bidirectional GMPLS tunnels in which packets are 284 visible. It supplements the counters in mplsTunnelPerfTable and 285 augments gmplsTunnelTable. 287 Note that not all counters may be appropriate or available for some 288 types of tunnel. 290 5.7. Use of 32-bit and 64-bit Counters 292 64-bit counters are provided in the GMPLS-TE-STD-MIB module for 293 high-speed interfaces where the use of 32-bit counters might be 294 impractical. The requirements on the use of 32-bit and 64-bit 295 counters (copied verbatim from [RFC2863]) are as follows: 297 For interfaces that operate at 20,000,000 (20 million) bits per 298 second or less, 32-bit byte and packet counters MUST be supported. 300 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 302 For interfaces that operate faster than 20,000,000 bits/second, and 303 slower than 650,000,000 bits/second, 32-bit packet counters MUST be 304 supported and 64-bit octet counters MUST be supported. For 305 interfaces that operate at 650,000,000 bits/second or faster, 64-bit 306 packet counters AND 64-bit octet counters MUST be supported. 308 6. Cross-referencing to the gmplsLabelTable 310 The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in 311 [GMPLSLSRMIB] and provides a way to model labels in a GMPLS system 312 where labels might not be simple 32 bit integers. 314 The hop tables in this document (gmplsTunnelHopTable, 315 gmplsTunnelCHopTable and gmplsTunnelARHopTable) and the segment 316 tables in the [RFC3813] (mplsInSegmentTable and mplsOutSegmentTable) 317 contain objects with syntax MplsLabel. 319 MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable 320 of representing any MPLS label and most GMPLS labels. However, some 321 GMPLS labels are larger than 32 bits and may be of arbitrary length. 322 Further, some labels that may be safely encoded in 32 bits are 323 constructed from multiple sub-fields. Additionally, some GMPLS 324 technologies support the concatenation of individual labels to 325 represent a data flow carried as multiple sub-flows. 327 These GMPLS cases require that something other than a simple 32-bit 328 integer is made available to represent the labels. This is achieved 329 through the gmplsLabelTable contained in the GMPLS-LABEL-STD-MIB 330 [GMPLSLSRMIB]. 332 The tables in this document and [RFC3813] that include objects with 333 syntax MplsLabel also include companion objects that are row 334 pointers. If the row pointer is set to zeroDotZero (0.0) then object 335 of syntax MplsLabel contains the label encoded as a 32-bit integer. 336 But otherwise the row pointer indicates a row in another MIB table 337 that includes the label. In these cases, the row pointer may indicate 338 a row in the gmplsLabelTable. 340 This provides both a good way to support legacy systems that 341 implement the MPLS-TE-STD-MIB [RFC3812], and a significant 342 simplification in GMPLS systems that are limited to a single, simple 343 label type. 345 Note that gmplsLabelTable supports concatenated labels through the 346 use of a label sub-index (gmplsLabelSubindex). 348 7. Example of GMPLS Tunnel Setup 349 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 351 This section contains an example of which MIB objects should be 352 modified to create a GMPLS tunnel. This example shows a best effort, 353 loosely routed, bidirectional traffic engineered tunnel, which spans 354 two hops of a simple network, uses Generalized Label requests with 355 Lambda encoding, has label recording and shared link layer 356 protection. Note that these objects should be created on the 357 "head-end" LSR. 359 First in the mplsTunnelTable: 361 { 362 mplsTunnelIndex = 1, 363 mplsTunnelInstance = 1, 364 mplsTunnelIngressLSRId = 192.0.2.1, 365 mplsTunnelEgressLSRId = 192.0.2.2, 366 mplsTunnelName = "My first tunnel", 367 mplsTunnelDescr = "Here to there and back again", 368 mplsTunnelIsIf = true (1), 369 mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, 370 mplsTunnelSignallingProto = none (1), 371 mplsTunnelSetupPrio = 0, 372 mplsTunnelHoldingPrio = 0, 373 mplsTunnelSessionAttributes = recordRoute (4), 374 mplsTunnelOwner = snmp (2), 375 mplsTunnelLocalProtectInUse = false (2), 376 mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, 377 mplsTunnelInstancePriority = 1, 378 mplsTunnelHopTableIndex = 1, 379 mplsTunnelPrimaryInstance = 0, 380 mplsTunnelIncludeAnyAffinity = 0, 381 mplsTunnelIncludeAllAffinity = 0, 382 mplsTunnelExcludeAnyAffinity = 0, 383 mplsTunnelPathInUse = 1, 384 mplsTunnelRole = head(1), 385 mplsTunnelRowStatus = createAndWait (5), 386 } 388 In gmplsTunnelTable(1,1,192.0.2.1,192.0.2.2): 389 { 390 gmplsTunnelUnnumIf = true (1), 391 gmplsTunnelAttributes = labelRecordingRequired (1), 392 gmplsTunnelLSPEncoding = tunnelLspLambda, 393 gmplsTunnelSwitchingType = lsc, 394 gmplsTunnelLinkProtection = shared (2), 395 gmplsTunnelGPid = lambda, 396 gmplsTunnelSecondary = false (2), 397 gmplsTunnelDirection = bidirectional (1) 398 gmplsTunnelPathComp = explicit(2), 399 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 401 gmplsTunnelSendPathNotifyRecipientType = ipv4(1), 402 gmplsTunnelSendPathNotifyRecipient = 'C0000201'H, 403 gmplsTunnelAdminStatusFlags = 0, 404 gmplsTunnelExtraParamsPtr = 0.0 405 } 407 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 408 gmplsTunnelHopTable are created and activated at this time. 410 In mplsTunnelResourceTable: 411 { 412 mplsTunnelResourceIndex = 6, 413 mplsTunnelResourceMaxRate = 0, 414 mplsTunnelResourceMeanRate = 0, 415 mplsTunnelResourceMaxBurstSize = 0, 416 mplsTunnelResourceRowStatus = createAndGo (4) 417 } 419 The next two instances of mplsTunnelHopEntry are used to denote the 420 hops this tunnel will take across the network. 422 The following denotes the beginning of the network, or the first hop. 423 We have used the fictitious LSR identified by "192.0.2.1" as our 424 example head-end router. 426 In mplsTunnelHopTable: 427 { 428 mplsTunnelHopListIndex = 1, 429 mplsTunnelPathOptionIndex = 1, 430 mplsTunnelHopIndex = 1, 431 mplsTunnelHopAddrType = ipV4 (1), 432 mplsTunnelHopIpv4Addr = 192.0.2.1, 433 mplsTunnelHopIpv4PrefixLen = 9, 434 mplsTunnelHopType = strict (1), 435 mplsTunnelHopRowStatus = createAndWait (5), 436 } 438 The following denotes the end of the network, or the last hop in our 439 example. We have used the fictitious LSR identified by 440 "192.0.2.2" as our tail end router. 442 In mplsTunnelHopTable: 443 { 444 mplsTunnelHopListIndex = 1, 445 mplsTunnelPathOptionIndex = 1, 446 mplsTunnelHopIndex = 2, 447 mplsTunnelHopAddrType = ipV4 (1), 448 mplsTunnelHopIpv4Addr = 192.0.2.2, 449 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 451 mplsTunnelHopIpv4PrefixLen = 9, 452 mplsTunnelHopType = loose (2), 453 mplsTunnelHopRowStatus = createAndGo (4) 454 } 456 Now an associated entry in the gmplsTunnelHopTable is created to 457 provide additional GMPLS hop configuration indicating that the first 458 hop is an unnumbered link using explicit forward and reverse labels. 460 An entry in the gmplsLabelTable is created first to include the 461 explicit label. 463 In gmplsLabelTable: 464 { 465 gmplsLabelInterface = 2, 466 gmplsLabelIndex = 1, 467 gmplsLabelSubindex = 0, 468 gmplsLabelType = gmplsFreeformLabel(3), 469 gmplsLabelFreeform = 0xFEDCBA9876543210 470 gmplsLabelRowStatus = createAndGo(4) 471 } 473 In gmplsTunnelHopTable(1,1,1): 474 { 475 gmplsTunnelHopLabelStatuses = forwardPresent(0) 476 +reversePresent(1), 477 gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable (2, 1, 0) 478 gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable (2, 1, 0) 479 } 481 The first hop is now activated: 483 In mplsTunnelHopTable(1,1,1): 484 { 485 mplsTunnelHopRowStatus = active (1) 486 } 488 No gmplsTunnelHopEntry is created for the second hop as it contains 489 no special GMPLS features. 491 Finally the mplsTunnelEntry is activated: 493 In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2) 494 { 495 mplsTunnelRowStatus = active(1) 496 } 497 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 499 8. GMPLS Traffic Engineering MIB Module 501 This MIB module makes references to the following documents. 502 [RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], 503 [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202] 504 and [RFC4328]. 506 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 508 IMPORTS 509 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 510 Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32 511 FROM SNMPv2-SMI -- RFC2578 512 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 513 FROM SNMPv2-CONF -- RFC2580 514 TruthValue, TimeStamp, RowPointer 515 FROM SNMPv2-TC -- RFC2579 516 InetAddress, InetAddressType 517 FROM INET-ADDRESS-MIB -- RFC4001 518 SnmpAdminString 519 FROM SNMP-FRAMEWORK-MIB -- RFC3411 520 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 521 mplsTunnelEgressLSRId, mplsTunnelHopListIndex, 522 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, 523 mplsTunnelARHopListIndex, mplsTunnelARHopIndex, 524 mplsTunnelCHopListIndex, mplsTunnelCHopIndex, 525 mplsTunnelEntry, 526 mplsTunnelAdminStatus, mplsTunnelOperStatus, 527 mplsTunnelGroup, mplsTunnelScalarGroup 528 FROM MPLS-TE-STD-MIB -- RFC3812 529 IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC, 530 IANAGmplsGeneralizedPidTC, IANAGmplsAdminStatusInformationTC 531 FROM IANA-GMPLS-TC-MIB 532 mplsStdMIB 533 FROM MPLS-TC-STD-MIB -- RFC3811 534 ; 536 gmplsTeStdMIB MODULE-IDENTITY 537 LAST-UPDATED 538 "200604060001Z" -- 06 April 2006 00:00:01 GMT 539 ORGANIZATION 540 "IETF Common Control And Measurement Plane (CCAMP) Working 541 Group" 542 CONTACT-INFO 543 " Thomas D. Nadeau 544 Cisco Systems, Inc. 545 Email: tnadeau@cisco.com 547 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 549 Adrian Farrel 550 Old Dog Consulting 551 Email: adrian@olddog.co.uk 553 Comments about this document should be emailed direct to the 554 CCAMP working group mailing list at ccamp@ops.ietf.org" 556 DESCRIPTION 557 "Copyright (C) The Internet Society (2006). This version of 558 this MIB module is part of RFC XXX; see the RFC itself for 559 full legal notices. 560 -- RFC Ed. Please replace XXX above with the correct RFC number and 561 -- remove this note. 563 This MIB module contains managed object definitions 564 for GMPLS Traffic Engineering (TE) as defined in: 565 1. Generalized Multi-Protocol Label Switching (GMPLS) 566 Signaling Functional Description, Berger, L. (Editor), 567 RFC 3471, January 2003. 568 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 569 L. (Editor), RFC 3473, January 2003." 571 REVISION 572 "200604060001Z" -- 06 April 2006 00:00:01 GMT 573 DESCRIPTION 574 "Initial version issued as part of RFC XXX." 575 ::= { mplsStdMIB XXX } 576 -- RFC Editor. Please replace XXX above with the OID assigned by IANA 577 -- and remove this note 579 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 580 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } 581 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } 582 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } 584 gmplsTunnelsConfigured OBJECT-TYPE 585 SYNTAX Gauge32 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The number of GMPLS tunnels configured on this device. A GMPLS 590 tunnel is considered configured if an entry for the tunnel 591 exists in the gmplsTunnelTable and the associated 592 mplsTunnelRowStatus is active(1)." 593 ::= { gmplsTeScalars 1 } 595 gmplsTunnelsActive OBJECT-TYPE 596 SYNTAX Gauge32 597 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The number of GMPLS tunnels active on this device. A GMPLS 603 tunnel is considered active if there is an entry in the 604 gmplsTunnelTable and the associated mplsTunnelOperStatus for the 605 tunnel is up(1)." 606 ::= { gmplsTeScalars 2 } 608 gmplsTunnelTable OBJECT-TYPE 609 SYNTAX SEQUENCE OF GmplsTunnelEntry 610 MAX-ACCESS not-accessible 611 STATUS current 612 DESCRIPTION 613 "The gmplsTunnelTable sparsely extends the mplsTunnelTable of 614 MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between 615 an LSR and a remote endpoint, and existing tunnels to be 616 reconfigured or removed. 618 Note that only point-to-point tunnel segments are supported, 619 although multi-point-to-point and point-to-multi-point 620 connections are supported by an LSR acting as a cross-connect. 621 Each tunnel can thus have one out-segment originating at this 622 LSR and/or one in-segment terminating at this LSR. 624 The row status of an entry in this table is controlled by 625 mplsTunnelRowStatus in the corresponding entry in 626 mplsTunnelTable. When the corresponding mplsTunnelRowStatus has 627 value active(1) a row in this table may not be created or 628 modified. 630 The exception to this rule is the 631 gmplsTunnelAdminStatusInformation object, which can be modified 632 whilst the tunnel is active." 633 REFERENCE 634 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 635 Management Information Base (MIB), RFC 3812." 636 ::= { gmplsTeObjects 1 } 638 gmplsTunnelEntry OBJECT-TYPE 639 SYNTAX GmplsTunnelEntry 640 MAX-ACCESS not-accessible 641 STATUS current 642 DESCRIPTION 643 "An entry in this table in association with the corresponding 644 entry in the mplsTunnelTable represents a GMPLS tunnel. 646 An entry can be created by a network administrator via SNMP SET 647 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 649 commands, or in response to signaling protocol events." 650 INDEX { 651 mplsTunnelIndex, 652 mplsTunnelInstance, 653 mplsTunnelIngressLSRId, 654 mplsTunnelEgressLSRId 655 } 656 ::= { gmplsTunnelTable 1 } 658 GmplsTunnelEntry ::= SEQUENCE { 659 gmplsTunnelUnnumIf TruthValue, 660 gmplsTunnelAttributes BITS, 661 gmplsTunnelLSPEncoding IANAGmplsLSPEncodingTypeTC, 662 gmplsTunnelSwitchingType IANAGmplsSwitchingTypeTC, 663 gmplsTunnelLinkProtection BITS, 664 gmplsTunnelGPid IANAGmplsGeneralizedPidTC, 665 gmplsTunnelSecondary TruthValue, 666 gmplsTunnelDirection INTEGER, 667 gmplsTunnelPathComp INTEGER, 668 gmplsTunnelUpstreamNotifyRecipientType InetAddressType, 669 gmplsTunnelUpstreamNotifyRecipient InetAddress, 670 gmplsTunnelSendResvNotifyRecipientType InetAddressType, 671 gmplsTunnelSendResvNotifyRecipient InetAddress, 672 gmplsTunnelDownstreamNotifyRecipientType InetAddressType, 673 gmplsTunnelDownstreamNotifyRecipient InetAddress, 674 gmplsTunnelSendPathNotifyRecipientType InetAddressType, 675 gmplsTunnelSendPathNotifyRecipient InetAddress, 676 gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformationTC, 677 gmplsTunnelExtraParamsPtr RowPointer 678 } 680 gmplsTunnelUnnumIf OBJECT-TYPE 681 SYNTAX TruthValue 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "Denotes whether or not this tunnel corresponds to an unnumbered 686 interface represented by an entry in the interfaces group table 687 (the ifTable) with ifType set to mpls (166). 689 This object is only used if mplsTunnelIsIf is set to 'true'. 691 If both this object and the mplsTunnelIsIf object are set to 692 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID 693 object to the outgoing Path message. 695 This object contains information that is only used by the 696 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 698 terminating LSR." 699 REFERENCE 700 "1. Signalling Unnumbered Links in RSVP-TE, RFC 3477." 701 DEFVAL { false } 702 ::= { gmplsTunnelEntry 1 } 704 gmplsTunnelAttributes OBJECT-TYPE 705 SYNTAX BITS { 706 labelRecordingDesired (0) 707 } 708 MAX-ACCESS read-create 709 STATUS current 710 DESCRIPTION 711 "This bitmask indicates optional parameters for this tunnel. 712 These bits should be taken in addition to those defined in 713 mplsTunnelSessionAttributes in order to determine the full set 714 of options to be signaled (for example SESSION_ATTRIBUTES flags 715 in RSVP-TE). The following describes these bitfields: 717 labelRecordingDesired 718 This flag is set to indicate that label information should be 719 included when doing a route record. This bit is not valid 720 unless the recordRoute bit is set." 721 REFERENCE 722 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 723 sections 4.4.3, 4.7.1 and 4.7.2." 724 DEFVAL { { } } 725 ::= { gmplsTunnelEntry 2 } 727 gmplsTunnelLSPEncoding OBJECT-TYPE 728 SYNTAX IANAGmplsLSPEncodingTypeTC 729 MAX-ACCESS read-create 730 STATUS current 731 DESCRIPTION 732 "This object indicates the encoding of the LSP being requested. 734 A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is 735 not in use. Some objects in this MIB module may be of use for 736 MPLS signaling extensions that do not use GMPLS signaling. By 737 setting this object to 'tunnelLspNotGmpls', an application may 738 indicate that only those objects meaningful in MPLS should be 739 examined. 741 The values to use are defined in the textual convention 742 IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB 743 module." 744 DEFVAL { tunnelLspNotGmpls } 745 ::= { gmplsTunnelEntry 3 } 746 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 748 gmplsTunnelSwitchingType OBJECT-TYPE 749 SYNTAX IANAGmplsSwitchingTypeTC 750 MAX-ACCESS read-create 751 STATUS current 752 DESCRIPTION 753 "Indicates the type of switching that should be performed on 754 a particular link. This field is needed for links that 755 advertise more than one type of switching capability. 757 The values to use are defined in the textual convention 758 IANAGmplsSwitchingTypeTC found in the IANA-GMPLS-TC-MIB module. 760 This object is only meaningful if gmplsTunnelLSPEncoding is not 761 set to 'tunnelLspNotGmpls'." 762 DEFVAL { unknown } 763 ::= { gmplsTunnelEntry 4 } 765 gmplsTunnelLinkProtection OBJECT-TYPE 766 SYNTAX BITS { 767 extraTraffic(0), 768 unprotected(1), 769 shared (2), 770 dedicatedOneToOne (3), 771 dedicatedOnePlusOne(4), 772 enhanced(5) 773 } 774 MAX-ACCESS read-create 775 STATUS current 776 DESCRIPTION 777 "This bitmask indicates the level of link protection required. A 778 value of zero (no bits set) indicates that any protection may be 779 used. The following describes these bitfields: 781 extraTraffic 782 This flag is set to indicate that the LSP should use links 783 that are protecting other (primary) traffic. Such LSPs may be 784 preempted when the links carrying the (primary) traffic being 785 protected fail. 787 unprotected 788 This glag is set to indicate that the LSP should not use any 789 link layer protection. 791 shared 792 This flage is set to indicate that a shared link layer 793 protection scheme, such as 1:N protection, should be used to 794 support the LSP. 796 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 798 dedicatedOneToOne 799 This flag is set to indicate that a dedicated link layer 800 protection scheme, i.e., 1:1 protection, should be used to 801 support the LSP. 803 dedicatedOnePlusOne 804 This flag is set to indicate that a dedicated link layer 805 protection scheme, i.e., 1+1 protection, should be used to 806 support the LSP. 808 enhanced 809 This flag is set to indicate that a protection scheme that is 810 more reliable than Dedicated 1+1 should be used, e.g., 4 fiber 811 BLSR/MS-SPRING. 813 This object is only meaningful if gmplsTunnelLSPEncoding is 814 not set to 'tunnelLspNotGmpls'." 816 REFERENCE 817 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 818 Functional Description, RFC 3471, section 7.1." 819 DEFVAL { { } } 820 ::= { gmplsTunnelEntry 5 } 822 gmplsTunnelGPid OBJECT-TYPE 823 SYNTAX IANAGmplsGeneralizedPidTC 824 MAX-ACCESS read-create 825 STATUS current 826 DESCRIPTION 827 "This object indicates the payload carried by the LSP. It is only 828 required when GMPLS will be used for this LSP. 830 The values to use are defined in the textual convention 831 IANAGmplsGeneralizedPidTC found in the IANA-GMPLS-TC-MIB module. 833 This object is only meaningful if gmplsTunnelLSPEncoding is not 834 set to 'tunnelLspNotGmpls'." 835 DEFVAL { unknown } 836 ::= { gmplsTunnelEntry 6 } 838 gmplsTunnelSecondary OBJECT-TYPE 839 SYNTAX TruthValue 840 MAX-ACCESS read-create 841 STATUS current 842 DESCRIPTION 843 "Indicates that the requested LSP is a secondary LSP. 845 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 847 This object is only meaningful if gmplsTunnelLSPEncoding is not 848 set to 'tunnelLspNotGmpls'." 849 REFERENCE 850 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 851 Functional Description, RFC 3471, section 7.1." 852 DEFVAL { false } 853 ::= { gmplsTunnelEntry 7 } 855 gmplsTunnelDirection OBJECT-TYPE 856 SYNTAX INTEGER { 857 forward (0), 858 bidirectional (1) 859 } 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "Whether this tunnel carries forward data only (is 864 unidirectional) or is bidirectional. 866 Values of this object other than 'forward' are meaningful 867 only if gmplsTunnelLSPEncoding is not set to 868 'tunnelLspNotGmpls'." 869 DEFVAL { forward } 870 ::= { gmplsTunnelEntry 8 } 872 gmplsTunnelPathComp OBJECT-TYPE 873 SYNTAX INTEGER { 874 dynamicFull(1), -- CSPF fully computed 875 explicit(2), -- fully specified path 876 dynamicPartial(3) -- CSPF partially computed 877 } 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "This value instructs the source node on how to perform path 882 computation on the explicit route specified by the associated 883 entries in the gmplsTunnelHopTable. 885 dynamicFull 886 The user specifies at least the source and 887 destination of the path and expects that the CSPF 888 will calculate the remainder of the path. 890 explicit 891 The user specifies the entire path for the tunnel to 892 take. This path may contain strict or loose hops. 893 Evaluation of the explicit route will be performed 894 hop by hop through the network. 896 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 898 dynamicPartial 899 The user specifies at least the source and 900 destination of the path and expects that the CSPF 901 will calculate the remainder of the path. The path 902 computed by CSPF is allowed to be only partially 903 computed allowing the remainder of the path to be 904 filled in across the network. 906 When an entry is present in gmplsTunnelTable for a tunnel, 907 gmplsTunnelPathComp MUST be used and any corresponding 908 mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable 909 MUST be ignored and SHOULD not be set. 911 mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of 912 MPLS-TE-STD-MIB. 914 This object should be ignored if value of gmplsTunnelLSPEncoding 915 is 'tunnelLspNotGmpls'." 916 REFERENCE 917 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 918 Management Information Base (MIB), RFC 3812." 919 DEFVAL { dynamicFull } 920 ::= { gmplsTunnelEntry 9 } 922 gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE 923 SYNTAX InetAddressType 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "This object is used to aid in interpretation of 928 gmplsTunnelUpstreamNotifyRecipient." 929 DEFVAL { unknown } 930 ::= { gmplsTunnelEntry 10 } 932 gmplsTunnelUpstreamNotifyRecipient OBJECT-TYPE 933 SYNTAX InetAddress 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "Indicates the address of the upstream recipient for Notify 938 messages relating to this tunnel and issued by this LSR. This 939 information is typically received from an upstream LSR in a Path 940 message. 942 This object is only valid when signaling a tunnel using RSVP. 944 It is also not valid at the head end of a tunnel since there are 945 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 947 no upstream LSRs to which to send a Notify message. 949 This object is interpreted in the context of the value of 950 gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0, 951 the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to 952 unknown(0)." 953 REFERENCE 954 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 955 section 4.2." 956 DEFVAL { '00000000'H } -- 0.0.0.0 957 ::= { gmplsTunnelEntry 11 } 959 gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE 960 SYNTAX InetAddressType 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "This object is used to aid in interpretation of 965 gmplsTunnelSendResvNotifyRecipient." 966 DEFVAL { unknown } 967 ::= { gmplsTunnelEntry 12 } 969 gmplsTunnelSendResvNotifyRecipient OBJECT-TYPE 970 SYNTAX InetAddress 971 MAX-ACCESS read-create 972 STATUS current 973 DESCRIPTION 974 "Indicates to an upstream LSR the address to which it should send 975 downstream Notify messages relating to this tunnel. 977 This object is only valid when signaling a tunnel using RSVP. 979 It is also not valid at the head end of the tunnel since no Resv 980 messages are sent from that LSR for this tunnel. 982 If set to 0, no Notify Request object will be included in the 983 outgoing Resv messages. 985 This object is interpreted in the context of the value of 986 gmplsTunnelSendResvNotifyRecipientType. If this object is set to 987 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be 988 set to unknown(0)." 989 REFERENCE 990 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 991 section 4.2." 992 DEFVAL { '00000000'H } -- 0.0.0.0 993 ::= { gmplsTunnelEntry 13 } 994 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 996 gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE 997 SYNTAX InetAddressType 998 MAX-ACCESS read-create 999 STATUS current 1000 DESCRIPTION 1001 "This object is used to aid in interpretation of 1002 gmplsTunnelDownstreamNotifyRecipient." 1003 DEFVAL { unknown } 1004 ::= { gmplsTunnelEntry 14 } 1006 gmplsTunnelDownstreamNotifyRecipient OBJECT-TYPE 1007 SYNTAX InetAddress 1008 MAX-ACCESS read-create 1009 STATUS current 1010 DESCRIPTION 1011 "Indicates the address of the downstream recipient for Notify 1012 messages relating to this tunnel and issued by this LSR. This 1013 information is typically received from an upstream LSR in a Resv 1014 message. This object is only valid when signaling a tunnel using 1015 RSVP. 1017 It is also not valid at the tail end of a tunnel since there are 1018 no downstream LSRs to which to send a Notify message. 1019 This object is interpreted in the context of the value of 1020 gmplsTunnelDownstreamNotifyRecipient. If this object is set to 1021 0, the value of gmplsTunnelDownstreamNotifyRecipient MUST be set 1022 to unknown(0)." 1023 REFERENCE 1024 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1025 section 4.2." 1026 DEFVAL { '00000000'H } -- 0.0.0.0 1027 ::= { gmplsTunnelEntry 15 } 1029 gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE 1030 SYNTAX InetAddressType 1031 MAX-ACCESS read-create 1032 STATUS current 1033 DESCRIPTION 1034 "This object is used to aid in interpretation of 1035 gmplsTunnelSendPathNotifyRecipient." 1036 DEFVAL { unknown } 1037 ::= { gmplsTunnelEntry 16 } 1039 gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE 1040 SYNTAX InetAddress 1041 MAX-ACCESS read-create 1042 STATUS current 1043 DESCRIPTION 1044 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1046 "Indicates to a downstream LSR the address to which it should 1047 send upstream Notify messages relating to this tunnel. 1049 This object is only valid when signaling a tunnel using RSVP. 1051 It is also not valid at the tail end of the tunnel since no Path 1052 messages are sent from that LSR for this tunnel. 1054 If set to 0, no Notify Request object will be included in the 1055 outgoing Path messages. 1057 This object is interpreted in the context of the value of 1058 gmplsTunnelSendPathNotifyRecipientType. If this object is set to 1059 0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be 1060 set to unknown(0)." 1062 REFERENCE 1063 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1064 section 4.2." 1065 DEFVAL { '00000000'H } -- 0.0.0.0 1066 ::= { gmplsTunnelEntry 17 } 1068 gmplsTunnelAdminStatusFlags OBJECT-TYPE 1069 SYNTAX IANAGmplsAdminStatusInformationTC 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "Determines the setting of the Admin Status flags in the 1074 Admin Status object or TLV, as described in RFC 3471. Setting 1075 this field to a non-zero value will result in the inclusion of 1076 the admin status object on signaling messages. 1078 The values to use are defined in the textual convention 1079 IANAGmplsAdminStatusInformationTC found in the 1080 IANA-GMPLS-TC-MIB module. 1082 This value of this object can be modified when the 1083 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 1084 is active(1). By doing so, a new signaling message will be 1085 triggered including the requested Admin Status object or 1086 TLV." 1087 REFERENCE 1088 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1089 Functional Description, RFC 3471, section 8." 1090 DEFVAL { { } } 1091 ::= { gmplsTunnelEntry 18 } 1093 gmplsTunnelExtraParamsPtr OBJECT-TYPE 1094 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1096 SYNTAX RowPointer 1097 MAX-ACCESS read-create 1098 STATUS current 1099 DESCRIPTION 1100 "Some Tunnels will run over transports that can usefully support 1101 technology-specific additional parameters (for example, SONET 1102 resource usage). Such parameters can be supplied in an external 1103 table and referenced from here. 1105 A value of zeroDotzero in this attribute indicates that there 1106 is no such additional information." 1107 DEFVAL { zeroDotZero } 1108 ::= { gmplsTunnelEntry 19 } 1110 gmplsTunnelHopTable OBJECT-TYPE 1111 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 1112 MAX-ACCESS not-accessible 1113 STATUS current 1114 DESCRIPTION 1115 "The gmplsTunnelHopTable sparsely extends the mplsTunnelHopTable 1116 of MPLS-TE-STD-MIB. It is used to indicate the explicit labels 1117 to be used in an explicit path for a GMPLS tunnel defined in 1118 mplsTunnelTable and gmplsTunnelTable, when it is established 1119 using signaling. It does not insert new hops, but does define 1120 new values for hops defined in mplsTunnelHopTable. 1122 Each row in this table is indexed by the same indexes as 1123 mplsTunnelHopTable. It is acceptable for some rows in 1124 mplsTunnelHopTable to have corresponding entries in this table 1125 and some to have no corresponding entry in this table. 1127 The storage type for this entry is given by the value 1128 of mplsTunnelHopStorageType in the corresponding entry in the 1129 mplsTunnelHopTable. 1131 The row status of an entry in this table is controlled by 1132 mplsTunnelHopRowStatus in the corresponding entry in 1133 mplsTunnelHopTable. That is, it is not permitted to create a row 1134 in this table, nor to modify an existing row, when the 1135 corresponding mplsTunnelHopRowStatus has value active(1)." 1136 REFERENCE 1137 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1138 Management Information Base (MIB), RFC 3812. 1139 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 1140 ::= { gmplsTeObjects 2 } 1142 gmplsTunnelHopEntry OBJECT-TYPE 1143 SYNTAX GmplsTunnelHopEntry 1144 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "An entry in this table represents additions to a tunnel hop 1150 defined in mplsTunnelHopEntry. At an ingress to a tunnel an 1151 entry in this table is created by a network administrator for an 1152 ERLSP to be set up by a signaling protocol. At transit and 1153 egress nodes an entry in this table may be used to represent the 1154 explicit path instructions received using the signaling 1155 protocol." 1156 INDEX { 1157 mplsTunnelHopListIndex, 1158 mplsTunnelHopPathOptionIndex, 1159 mplsTunnelHopIndex 1160 } 1161 ::= { gmplsTunnelHopTable 1 } 1163 GmplsTunnelHopEntry ::= SEQUENCE { 1164 gmplsTunnelHopLabelStatuses BITS, 1165 gmplsTunnelHopExplicitForwardLabel Unsigned32, 1166 gmplsTunnelHopExplicitForwardLabelPtr RowPointer, 1167 gmplsTunnelHopExplicitReverseLabel Unsigned32, 1168 gmplsTunnelHopExplicitReverseLabelPtr RowPointer 1169 } 1171 gmplsTunnelHopLabelStatuses OBJECT-TYPE 1172 SYNTAX BITS { 1173 forwardPresent (0), 1174 reversePresent (1) 1175 } 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "This bitmask indicates the presence of labels indicated by the 1180 gmplsTunnelHopExplicitForwardLabel or 1181 gmplsTunnelHopExplicitForwardLabelPtr, and 1182 gmplsTunnelHopExplicitReverseLabel or 1183 gmplsTunnelHopExplicitReverseLabel objects. 1185 For the Present bits, a set bit indicates that a label is 1186 present for this hop in the route. This allows zero to be a 1187 valid label value." 1188 DEFVAL { { } } 1189 ::= { gmplsTunnelHopEntry 1 } 1191 gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE 1192 SYNTAX Unsigned32 1193 MAX-ACCESS read-create 1194 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1196 STATUS current 1197 DESCRIPTION 1198 "If gmplsTunnelHopLabelStatuses object indicates that a forward 1199 label is present and gmplsTunnelHopExplicitForwardLabelPtr 1200 contains the value zeroDotZero, then the label to use on this 1201 hop is represented by the value of this object." 1202 ::= { gmplsTunnelHopEntry 2 } 1204 gmplsTunnelHopExplicitForwardLabelPtr OBJECT-TYPE 1205 SYNTAX RowPointer 1206 MAX-ACCESS read-create 1207 STATUS current 1208 DESCRIPTION 1209 "If the gmplsTunnelHopLabelStatuses object indicates that a 1210 forward label is present, this object contains a pointer to a 1211 row in another MIB table (such as the gmplsLabelTable of 1212 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1213 in the forward direction. 1215 If the gmplsTunnelHopLabelStatuses object indicates that a 1216 forward label is present and this object contains the value 1217 zeroDotZero, then the label to use on this hop is found in the 1218 gmplsTunnelHopExplicitForwardLabel object." 1219 DEFVAL { zeroDotZero } 1220 ::= { gmplsTunnelHopEntry 3 } 1222 gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE 1223 SYNTAX Unsigned32 1224 MAX-ACCESS read-create 1225 STATUS current 1226 DESCRIPTION 1227 "If the gmplsTunnelHopLabelStatuses object indicates that a 1228 reverse label is present and 1229 gmplsTunnelHopExplicitReverseLabelPtr contains the value 1230 zeroDotZero, then the label to use on this this hop is found in 1231 this object encoded as a 32-bit integer." 1232 ::= { gmplsTunnelHopEntry 4 } 1234 gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE 1235 SYNTAX RowPointer 1236 MAX-ACCESS read-create 1237 STATUS current 1238 DESCRIPTION 1239 "If the gmplsTunnelHopLabelStatuses object indicates that a 1240 reverse label is present, this object contains a pointer to a 1241 row in another MIB table (such as the gmplsLabelTable of the 1242 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1243 in the reverse direction. 1245 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1247 If the gmplsTunnelHopLabelStatuses object indicates that a 1248 reverse label is present and this object contains the value 1249 zeroDotZero, then the label to use on this hop is found in the 1250 gmplsTunnelHopExplicitReverseLabel object." 1251 DEFVAL { zeroDotZero } 1252 ::= { gmplsTunnelHopEntry 5 } 1254 gmplsTunnelARHopTable OBJECT-TYPE 1255 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 1256 MAX-ACCESS not-accessible 1257 STATUS current 1258 DESCRIPTION 1259 "The gmplsTunnelARHopTable sparsely extends the 1260 mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate 1261 the labels currently in use for a GMPLS tunnel defined in 1262 mplsTunnelTable and gmplsTunnelTable, as reported by the 1263 signaling protocol. It does not insert new hops, but does define 1264 new values for hops defined in mplsTunnelARHopTable. 1266 Each row in this table is indexed by the same indexes as 1267 mplsTunnelARHopTable. It is acceptable for some rows in 1268 mplsTunnelARHopTable to have corresponding entries in this table 1269 and some to have no corresponding entry in this table. 1271 Note that since the information necessary to build entries 1272 within this table is not provided by some signaling protocols 1273 and might not be returned in all cases of other signaling 1274 protocols, implementation of this table and mplsTunnelARHopTable 1275 is optional. Furthermore, since the information in this table is 1276 actually provided by the signaling protocol after the path has 1277 been set-up, the entries in this table are provided only for 1278 observation, and hence, all variables in this table are 1279 accessible exclusively as read-only." 1281 REFERENCE 1282 "1. Extensions to RSVP for LSP Tunnels, RFC 3209. 1283 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 1284 3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1285 Management Information Base (MIB), RFC 3812." 1286 ::= { gmplsTeObjects 3 } 1288 gmplsTunnelARHopEntry OBJECT-TYPE 1289 SYNTAX GmplsTunnelARHopEntry 1290 MAX-ACCESS not-accessible 1291 STATUS current 1292 DESCRIPTION 1293 "An entry in this table represents additions to a tunnel hop 1294 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1296 visible in mplsTunnelARHopEntry. An entry is created by the 1297 signaling protocol for a signaled ERLSP set up by the signaling 1298 protocol. 1300 At any node on the LSP (ingress, transit or egress), this table 1301 and mplsTunnelARHopTable (if the tables are supported and if the 1302 signaling protocol is recording actual route information) 1303 contain the actual route of the whole tunnel. If the signaling 1304 protocol is not recording the actual route, this table MAY 1305 report the information from the gmplsTunnelHopTable or the 1306 gmplsTunnelCHopTable. 1308 Note that the recording of actual labels is distinct from the 1309 recording of the actual route in some signaling protocols. This 1310 feature is enabled using the gmplsTunnelAttributes object." 1311 INDEX { 1312 mplsTunnelARHopListIndex, 1313 mplsTunnelARHopIndex 1314 } 1315 ::= { gmplsTunnelARHopTable 1 } 1317 GmplsTunnelARHopEntry ::= SEQUENCE { 1318 gmplsTunnelARHopLabelStatuses BITS, 1319 gmplsTunnelARHopExplicitForwardLabel Unsigned32, 1320 gmplsTunnelARHopExplicitForwardLabelPtr RowPointer, 1321 gmplsTunnelARHopExplicitReverseLabel Unsigned32, 1322 gmplsTunnelARHopExplicitReverseLabelPtr RowPointer, 1323 gmplsTunnelARHopProtection BITS 1324 } 1326 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1327 SYNTAX BITS { 1328 forwardPresent (0), 1329 reversePresent (1), 1330 forwardGlobal (2), 1331 reverseGlobal (3) 1332 } 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "This bitmask indicates the presence and status of labels 1337 indicated by the gmplsTunnelARHopExplicitForwardLabel or 1338 gmplsTunnelARHopExplicitForwardLabelPtr, and 1339 gmplsTunnelARHopExplicitReverseLabel or 1340 gmplsTunnelARHopExplicitReverseLabelPtr objects. 1342 For the Present bits, a set bit indicates that a label is 1343 present for this hop in the route. For the Global bits, a set 1344 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1346 bit indicates that the label comes from the Global Label Space. 1347 A clear bit indicates that this is a Per-Interface label. A 1348 Global bit only has meaning if the corresponding Present bit is 1349 set." 1350 ::= { gmplsTunnelARHopEntry 1 } 1352 gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE 1353 SYNTAX Unsigned32 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1358 forward label is present and 1359 gmplsTunnelARHopExplicitForwardLabelPtr contains the value 1360 zeroDotZero, then the label in use on this hop is found in this 1361 object encoded within a 32-bit integer." 1362 ::= { gmplsTunnelARHopEntry 2 } 1364 gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE 1365 SYNTAX RowPointer 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1370 forward label is present, this object contains a pointer to a 1371 row in another MIB table (such as the gmplsLabelTable of the 1372 GMPLS-LABEL-STD-MIB) that contains the label in use on this hop 1373 in the forward direction. 1375 If the gmplsTunnelARHopLabelStatuses object indicates that a 1376 forward label is present and this object contains the value 1377 zeroDotZero, then the label in use on this hop is found in the 1378 gmplsTunnelARHopExplicitForwardLabel object." 1379 ::= { gmplsTunnelARHopEntry 3 } 1381 gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE 1382 SYNTAX Unsigned32 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1387 reverse label is present and 1388 gmplsTunnelARHopExplicitReverseLabelPtr contains the value 1389 zeroDotZero, then the label in use on this hop is found in this 1390 object encoded as a 32-bit integer." 1391 ::= { gmplsTunnelARHopEntry 4 } 1393 gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE 1394 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1396 SYNTAX RowPointer 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1401 reverse label is present, this object contains a pointer to a 1402 row in another MIB table (such as the gmplsLabelTable of the 1403 GMPLS-LABEL-STD-MIB) that contains the label in use on this hop 1404 in the reverse direction. 1406 If the gmplsTunnelARHopLabelStatuses object indicates that a 1407 reverse label is present and this object contains the value 1408 zeroDotZero, then the label in use on this hop is found in the 1409 gmplsTunnelARHopExplicitReverseLabel object." 1410 ::= { gmplsTunnelARHopEntry 5 } 1412 gmplsTunnelARHopProtection OBJECT-TYPE 1413 SYNTAX BITS { 1414 localAvailable (0), 1415 localInUse (1) 1416 } 1417 MAX-ACCESS read-only 1418 STATUS current 1419 DESCRIPTION 1420 "Availability and usage of protection on the reported link. 1422 localAvailable 1423 This flag is set to indicate that the link downstream of this 1424 node is protected via a local repair mechanism. 1426 localInUse 1427 This flag is set to indicate that a local repair mechanism is 1428 in use to maintain this tunnel (usually in the face of an 1429 outage of the link it was previously routed over)." 1430 REFERENCE 1431 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1432 section 4.4.1." 1433 ::= { gmplsTunnelARHopEntry 6 } 1435 gmplsTunnelCHopTable OBJECT-TYPE 1436 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "The gmplsTunnelCHopTable sparsely extends the 1441 mplsTunnelCHopTable 1442 of MPLS-TE-STD-MIB. It is used to indicate additional 1443 information about the hops of a GMPLS tunnel defined in 1444 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1446 mplsTunnelTable and gmplsTunnelTable, as computed by a 1447 constraint-based routing protocol, based on the 1448 mplsTunnelHopTable and the gmplsTunnelHopTable. 1450 Each row in this table is indexed by the same indexes as 1451 mplsTunnelCHopTable. It is acceptable for some rows in 1452 mplsTunnelCHopTable to have corresponding entries in this table 1453 and some to have no corresponding entry in this table. 1455 Please note that since the information necessary to build 1456 entries within this table may not be supported by some LSRs, 1457 implementation of this table is optional. 1459 Furthermore, since the information in this table is actually 1460 provided by a path computation component after the path has been 1461 computed, the entries in this table are provided only for 1462 observation, and hence, all objects in this table are accessible 1463 exclusively as read-only." 1465 REFERENCE 1466 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1467 Management Information Base (MIB), RFC 3812. 1468 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 1469 ::= { gmplsTeObjects 4 } 1471 gmplsTunnelCHopEntry OBJECT-TYPE 1472 SYNTAX GmplsTunnelCHopEntry 1473 MAX-ACCESS not-accessible 1474 STATUS current 1475 DESCRIPTION 1476 "An entry in this table represents additions to a computed tunnel 1477 hop visible in mplsTunnelCHopEntry. An entry is created by a 1478 path computation component based on the hops specified in the 1479 corresponding mplsTunnelHopTable and gmplsTunnelHopTable. 1481 At a transit LSR this table (if the table is supported) MAY 1482 contain the path computed by path computation engine on (or on 1483 behalf of) the transit LSR." 1484 INDEX { 1485 mplsTunnelCHopListIndex, 1486 mplsTunnelCHopIndex 1487 } 1488 ::= { gmplsTunnelCHopTable 1 } 1490 GmplsTunnelCHopEntry ::= SEQUENCE { 1491 gmplsTunnelCHopLabelStatuses BITS, 1492 gmplsTunnelCHopExplicitForwardLabel Unsigned32, 1493 gmplsTunnelCHopExplicitForwardLabelPtr RowPointer, 1494 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1496 gmplsTunnelCHopExplicitReverseLabel Unsigned32, 1497 gmplsTunnelCHopExplicitReverseLabelPtr RowPointer 1498 } 1500 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1501 SYNTAX BITS { 1502 forwardPresent (0), 1503 reversePresent (1) 1504 } 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "This bitmask indicates the presence of labels indicated by the 1509 gmplsTunnelCHopExplicitForwardLabel or 1510 gmplsTunnelCHopExplicitForwardLabelPtr and 1511 gmplsTunnelCHopExplicitReverseLabel or 1512 gmplsTunnelCHopExplicitReverseLabelPtr objects. 1513 A set bit indicates that a label is present for this hop in the 1514 route thus allowing zero to be a valid label value." 1515 ::= { gmplsTunnelCHopEntry 1 } 1517 gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE 1518 SYNTAX Unsigned32 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1523 forward label is present and 1524 gmplsTunnelCHopExplicitForwardLabelPtr contains the value 1525 zeroDotZero, then the label to use on this hop is found in this 1526 object encoded within a 32-bit integer." 1527 ::= { gmplsTunnelCHopEntry 2 } 1529 gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE 1530 SYNTAX RowPointer 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1535 forward label is present, this object contains a pointer to a 1536 row in another MIB table (such as the gmplsLabelTable of the 1537 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1538 in the forward direction. 1540 If the gmplsTunnelCHopLabelStatuses object indicates that a 1541 forward label is present and this object contains the value 1542 zeroDotZero, then the label to use on this hop is found in the 1543 gmplsTunnelCHopExplicitForwardLabel object." 1544 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1546 ::= { gmplsTunnelCHopEntry 3 } 1548 gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE 1549 SYNTAX Unsigned32 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1554 reverse label is present and 1555 gmplsTunnelCHopExplicitReverseLabelPtr contains the value 1556 zeroDotZero, then the label to use on this hop is found in this 1557 object encoded as a 32-bit integer." 1558 ::= { gmplsTunnelCHopEntry 4 } 1560 gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE 1561 SYNTAX RowPointer 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1566 reverse label is present, this object contains a pointer to a 1567 row in another MIB table (such as the gmplsLabelTable of the 1568 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1569 in the reverse direction. 1571 If the gmplsTunnelCHopLabelStatuses object indicates that a 1572 reverse label is present and this object contains the value 1573 zeroDotZero, then the label to use on this hop is found in the 1574 gmplsTunnelCHopExplicitReverseLabel object." 1575 ::= { gmplsTunnelCHopEntry 5 } 1577 gmplsTunnelReversePerfTable OBJECT-TYPE 1578 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1579 MAX-ACCESS not-accessible 1580 STATUS current 1581 DESCRIPTION 1582 "This table augments the gmplsTunnelTable to provides 1583 per-tunnel packet performance information for the reverse 1584 direction of a bidirectional tunnel. It can be seen as 1585 supplementing the mplsTunnelPerfTable which augments the 1586 mplsTunnelTable. 1588 For links that do not transport packets, these packet counters 1589 cannot be maintained. For such links, attempts to read the 1590 objects in this table will return noSuchInstance. 1592 A tunnel can be known to be bidirectional by inspecting the 1593 gmplsTunnelDirection object." 1594 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1596 REFERENCE 1597 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1598 Management Information Base (MIB), RFC 3812." 1599 ::= { gmplsTeObjects 5 } 1601 gmplsTunnelReversePerfEntry OBJECT-TYPE 1602 SYNTAX GmplsTunnelReversePerfEntry 1603 MAX-ACCESS not-accessible 1604 STATUS current 1605 DESCRIPTION 1606 "An entry in this table is created by the LSR for every 1607 bidirectional GMPLS tunnel where packets are visible to the 1608 LSR." 1609 AUGMENTS { gmplsTunnelEntry } 1610 ::= { gmplsTunnelReversePerfTable 1 } 1612 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1613 gmplsTunnelReversePerfPackets Counter32, 1614 gmplsTunnelReversePerfHCPackets Counter64, 1615 gmplsTunnelReversePerfErrors Counter32, 1616 gmplsTunnelReversePerfBytes Counter32, 1617 gmplsTunnelReversePerfHCBytes Counter64 1618 } 1620 gmplsTunnelReversePerfPackets OBJECT-TYPE 1621 SYNTAX Counter32 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "Number of packets forwarded on the tunnel in the reverse 1626 direction if it is bidirectional. 1628 This object should represents the 32-bit value of the least 1629 significant part of the 64-bit value if both 1630 gmplsTunnelReversePerfHCPackets and this object are returned. 1632 For links that do not transport packets, this packet counter 1633 cannot be maintained. For such links, this value will return a 1634 noSuchInstance." 1635 ::= { gmplsTunnelReversePerfEntry 1 } 1637 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1638 SYNTAX Counter64 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "High capacity counter for number of packets forwarded on the 1643 tunnel in the reverse direction if it is bidirectional. 1645 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1647 For links that do not transport packets, this packet counter 1648 cannot be maintained. For such links, this value will return a 1649 noSuchInstance." 1650 ::= { gmplsTunnelReversePerfEntry 2 } 1652 gmplsTunnelReversePerfErrors OBJECT-TYPE 1653 SYNTAX Counter32 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "Number of errored packets received on the tunnel in the reverse 1658 direction if it is bidirectional. For links that do not 1659 transport packets, this packet counter cannot be maintained. For 1660 such links, this value will return a noSuchInstance." 1661 ::= { gmplsTunnelReversePerfEntry 3 } 1663 gmplsTunnelReversePerfBytes OBJECT-TYPE 1664 SYNTAX Counter32 1665 MAX-ACCESS read-only 1666 STATUS current 1667 DESCRIPTION 1668 "Number of bytes forwarded on the tunnel in the reverse direction 1669 if it is bidirectional. 1671 This object should represents the 32-bit value of the least 1672 significant part of the 64-bit value if both 1673 gmplsTunnelReversePerfHCBytes and this object are returned. 1675 For links that do not transport packets, this packet counter 1676 cannot be maintained. For such links, this value will return a 1677 noSuchInstance." 1678 ::= { gmplsTunnelReversePerfEntry 4 } 1680 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1681 SYNTAX Counter64 1682 MAX-ACCESS read-only 1683 STATUS current 1685 DESCRIPTION 1686 "High capacity counter for number of bytes forwarded on the 1687 tunnel in the reverse direction if it is bidirectional. 1689 For links that do not transport packets, this packet counter 1690 cannot be maintained. For such links, this value will return a 1691 noSuchInstance." 1692 ::= { gmplsTunnelReversePerfEntry 5 } 1693 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1695 gmplsTunnelErrorTable OBJECT-TYPE 1696 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1697 MAX-ACCESS not-accessible 1698 STATUS current 1699 DESCRIPTION 1700 "This table augments the mplsTunnelTable 1701 This table provides per-tunnel information about errors. Errors 1702 may be detected locally or reported through the signaling 1703 protocol. Error reporting is not exclusive to GMPLS and this 1704 table may be applied in MPLS systems. 1706 Entries in this table are not persistent over system resets 1707 or re-initializations of the management system." 1708 REFERENCE 1709 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1710 Management Information Base (MIB), RFC 3812." 1711 ::= { gmplsTeObjects 6 } 1713 gmplsTunnelErrorEntry OBJECT-TYPE 1714 SYNTAX GmplsTunnelErrorEntry 1715 MAX-ACCESS not-accessible 1716 STATUS current 1717 DESCRIPTION 1718 "An entry in this table is created by the LSR for every tunnel 1719 where error information is visible to the LSR. 1721 Note that systems which read the objects in this table one at a 1722 time may experience a discontinuity as the result of a new error 1723 occurring in between object reads. Systems that are vulnerable 1724 to this should read gmplsTunnelErrorLastTime before and after 1725 reading the other objects." 1726 AUGMENTS { mplsTunnelEntry } 1727 ::= { gmplsTunnelErrorTable 1 } 1729 GmplsTunnelErrorEntry ::= SEQUENCE { 1730 gmplsTunnelErrorLastErrorType INTEGER, 1731 gmplsTunnelErrorLastTime TimeStamp, 1732 gmplsTunnelErrorReporterType InetAddressType, 1733 gmplsTunnelErrorReporter InetAddress, 1734 gmplsTunnelErrorCode Unsigned32, 1735 gmplsTunnelErrorSubcode Unsigned32, 1736 gmplsTunnelErrorTLVs OCTET STRING, 1737 gmplsTunnelErrorHelpString SnmpAdminString 1738 } 1740 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1741 SYNTAX INTEGER { 1742 noError (0), 1743 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1745 unknown (1), 1746 protocol (2), 1747 pathComputation (3), 1748 localConfiguration (4), 1749 localResources (5), 1750 localOther (6) 1751 } 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "The nature of the last error. Provides interpretation context 1756 for gmplsTunnelErrorProtocolCode and 1757 gmplsTunnelErrorProtocolSubcode. 1759 A value of noError (0) shows that there is no error associated 1760 with this tunnel and means that the other objects in this table 1761 entry have no meaning. 1763 A value of unknown (1) shows that there is an error but that no 1764 additional information about the cause is known. The error may 1765 have been received in a signaled message or generated locally. 1767 A value of protocol (2) or pathComputation (3) indicates the 1768 cause of an error and identifies an error that has been received 1769 through signaling or will itself be signaled. 1771 A value of localConfiguration (4), localResources (5) or 1772 localOther (6) identifies an error which has been detected 1773 by the local node, but which will not be reported through 1774 signaling." 1775 ::= { gmplsTunnelErrorEntry 1 } 1777 gmplsTunnelErrorLastTime OBJECT-TYPE 1778 SYNTAX TimeStamp 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1782 "The time at which the last error occurred. This is presented as 1783 the value of SysUpTime when the error occurred or was reported 1784 to this node. 1786 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1787 this object is ignored. 1789 Note that entries in this table are not persistent over system 1790 resets or re-initializations of the management system." 1791 ::= { gmplsTunnelErrorEntry 2 } 1792 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1794 gmplsTunnelErrorReporterType OBJECT-TYPE 1795 SYNTAX InetAddressType 1796 MAX-ACCESS read-only 1797 STATUS current 1798 DESCRIPTION 1799 "The address type of the error reported. 1801 This object is used to aid in interpretation of 1802 gmplsTunnelErrorReporter." 1803 ::= { gmplsTunnelErrorEntry 3 } 1805 gmplsTunnelErrorReporter OBJECT-TYPE 1806 SYNTAX InetAddress 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "The address of the node reporting the last error, or the address 1811 of the resource (such as an interface) associated with the 1812 error. 1814 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1815 this object is ignored. 1817 If gmplsTunnelErrorLastErrorType has the value unknown (1), 1818 localConfiguration (4), localResources (5), or localOther (6) 1819 this object MAY contain a zero value. 1821 This object should be interpreted in the context of the value of 1822 the object gmplsTunnelErrorReporterType." 1823 REFERENCE 1824 "1. Textual Conventions for Internet Network Addresses, RFC 4001, 1825 section 4, Usage Hints." 1826 ::= { gmplsTunnelErrorEntry 4 } 1828 gmplsTunnelErrorCode OBJECT-TYPE 1829 SYNTAX Unsigned32 1830 MAX-ACCESS read-only 1831 STATUS current 1832 DESCRIPTION 1833 "The primary error code associated with the last error. 1834 The interpretation of this error code depends on the value of 1835 gmplsTunnelErrorLastErrorType. If the value of 1836 gmplsTunnelErrorLastErrorType is noError (0) the value of this 1837 object should be 0 and should be ignored. If the value of 1838 gmplsTunnelErrorLastErrorType is protocol (2) the error should 1839 be interpreted in the context of the signling protocol 1840 identified by the mplsTunnelSignallingProto object." 1841 REFERENCE 1842 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1844 "1. Resource ReserVation Protocol -- Version 1 Functional 1845 Specification, RFC 2205, section B. 1846 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1847 section 7.3. 1848 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1849 section 13.1." 1850 ::= { gmplsTunnelErrorEntry 5 } 1852 gmplsTunnelErrorSubcode OBJECT-TYPE 1853 SYNTAX Unsigned32 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "The secondary error code associated with the last error and the 1858 protocol used to signal this tunnel. This value is interpreted 1859 in the context of the value of gmplsTunnelErrorCode. 1860 If the value of gmplsTunnelErrorLastErrorType is noError (0) the 1861 value of this object should be 0 and should be ignored." 1862 REFERENCE 1863 "1. Resource ReserVation Protocol -- Version 1 Functional 1864 Specification, RFC 2205, section B. 1866 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1867 section 7.3. 1868 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1869 section 13.1." 1870 ::= { gmplsTunnelErrorEntry 6 } 1872 gmplsTunnelErrorTLVs OBJECT-TYPE 1873 SYNTAX OCTET STRING (SIZE(0..65535)) 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "The sequence of interface identifier TLVs reported with the 1878 error by the protocol code. The interpretation of the TLVs and 1879 the encoding within the protocol are described in the 1880 references. A value of zero in the first octet indicates that no 1881 TLVs are present." 1882 REFERENCE 1883 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1884 section 8.2." 1885 ::= { gmplsTunnelErrorEntry 7 } 1887 gmplsTunnelErrorHelpString OBJECT-TYPE 1888 SYNTAX SnmpAdminString 1889 MAX-ACCESS read-only 1890 STATUS current 1891 DESCRIPTION 1892 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1894 "A textual string containing information about the last error, 1895 recovery actions and support advice. If there is no help string 1896 this object contains a zero length string. 1897 If the value of gmplsTunnelErrorLastErrorType is noError (0) 1898 this object should contain a zero length string, but may contain 1899 a help string indicating that there is no error." 1900 ::= { gmplsTunnelErrorEntry 8 } 1902 -- 1903 -- Notifications 1904 -- 1906 gmplsTunnelDown NOTIFICATION-TYPE 1907 OBJECTS { 1908 mplsTunnelAdminStatus, 1909 mplsTunnelOperStatus, 1910 gmplsTunnelErrorLastErrorType, 1911 gmplsTunnelErrorReporterType, 1912 gmplsTunnelErrorReporter, 1913 gmplsTunnelErrorCode, 1914 gmplsTunnelErrorSubcode 1915 } 1916 STATUS current 1917 DESCRIPTION 1918 "This notification is generated when a mplsTunnelOperStatus 1919 object for a tunnel in the gmplsTunnelTable is about to enter 1920 the down state from some other state (but not from the 1921 notPresent state). This other state is indicated by the 1922 included value of mplsTunnelOperStatus. 1924 The objects in this notification provide additional error 1925 information that indicates the reason why the tunnel has 1926 transitioned down. 1928 Note that an implementation MUST only issue one of 1929 mplsTunnelDown and gmplsTunnelDown for any single event on a 1930 single tunnel. If the tunnel has an entry in gmplsTunnelTable 1931 an implementation SHOULD use gmplsTunnelDown for all tunnel 1932 down events and SHOULD NOT use mplsTunnelDown. 1934 This notification is subject to the control of the 1935 mplsTunnelNotificationEnable. When that object is set to 1936 false(2) then the notification must not be issued. 1938 Further, this notification is also subject to 1939 mplsTunnelNotificationMaxRate. That object indicates the 1940 maximum number of notifications issued per second. If events 1941 occur more rapidly, the implementation may simply fail to emit 1942 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1944 some notifications during that period, or may queue them until 1945 an appropriate time. The notification rate applies to the sum 1946 of all notificaitons in the MPLS-TE-STD-MIB and 1947 GMPLS-TE-STD-MIB modules applied across the whole of the 1948 reporting device. 1950 mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, 1951 mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate 1952 objects are found in MPLS-TE-STD-MIB." 1953 REFERENCE 1954 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering 1955 (TE) Management Information Base (MIB), RFC 3812." 1956 ::= { gmplsTeNotifications 1 } 1958 gmplsTeGroups 1959 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1961 gmplsTeCompliances 1962 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1964 -- Compliance requirement for fully compliant implementations. 1966 gmplsTeModuleFullCompliance MODULE-COMPLIANCE 1967 STATUS current 1968 DESCRIPTION 1969 "Compliance statement for agents that provide full support for 1970 GMPLS-TE-STD-MIB. Such devices can then be monitored and also 1971 be configured using this MIB module. 1973 The mandatory group has to be implemented by all LSRs that 1974 originate, terminate or act as transit for TE-LSPs/tunnels. 1975 In addition, depending on the type of tunnels supported, other 1976 groups become mandatory as explained below." 1978 MODULE MPLS-TE-STD-MIB -- The MPLS-TE-STD-MIB, RFC3812 1980 MANDATORY-GROUPS { 1981 mplsTunnelGroup, 1982 mplsTunnelScalarGroup 1983 } 1985 MODULE -- this module 1987 MANDATORY-GROUPS { 1988 gmplsTunnelGroup, 1989 gmplsTunnelScalarGroup 1990 } 1991 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 1993 GROUP gmplsTunnelSignaledGroup 1994 DESCRIPTION 1995 "This group is mandatory for devices which support signaled 1996 tunnel set up, in addition to gmplsTunnelGroup. The following 1997 constraints apply: 1998 mplsTunnelSignallingProto should be at least read-only 1999 returning a value of ldp(2), or rsvp(3)." 2001 GROUP gmplsTunnelOptionalGroup 2002 DESCRIPTION 2003 "Objects in this group are optional." 2005 GROUP gmplsTeNotificationGroup 2006 DESCRIPTION 2007 "This group is mandatory for those implementations which can 2008 implement the notifications contained in this group." 2010 ::= { gmplsTeCompliances 1 } 2012 -- Compliance requirement for read-only compliant implementations. 2014 gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 2015 STATUS current 2016 DESCRIPTION 2017 "Compliance requirement for implementations that only provide 2018 read-only support for GMPLS-TE-STD-MIB. Such devices can then be 2019 monitored but cannot be configured using this MIB module." 2021 MODULE -- this module 2023 -- The mandatory group has to be implemented by all LSRs that 2024 -- originate, terminate or act as transit for TE-LSPs/tunnels. 2025 -- In addition, depending on the type of tunnels supported, other 2026 -- groups become mandatory as explained below. 2028 MANDATORY-GROUPS { 2029 gmplsTunnelGroup, 2030 gmplsTunnelScalarGroup 2031 } 2033 GROUP gmplsTunnelSignaledGroup 2034 DESCRIPTION 2035 "This group is mandatory for devices which support signaled 2036 tunnel set up, in addition to gmplsTunnelGroup. The following 2037 constraints apply: 2038 mplsTunnelSignallingProto should be at least read-only 2039 returning a value of ldp(2), or rsvp(3)." 2041 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2043 GROUP gmplsTunnelOptionalGroup 2044 DESCRIPTION 2045 "Objects in this group are optional." 2047 GROUP gmplsTeNotificationGroup 2048 DESCRIPTION 2049 "This group is mandatory for those implementations which can 2050 implement the notifications contained in this group." 2052 OBJECT gmplsTunnelAttributes 2053 MIN-ACCESS read-only 2054 DESCRIPTION 2055 "Write access is not required." 2057 OBJECT gmplsTunnelLSPEncoding 2058 MIN-ACCESS read-only 2059 DESCRIPTION 2060 "Write access is not required." 2062 OBJECT gmplsTunnelSwitchingType 2063 MIN-ACCESS read-only 2064 DESCRIPTION 2065 "Write access is not required." 2067 OBJECT gmplsTunnelLinkProtection 2068 MIN-ACCESS read-only 2069 DESCRIPTION 2070 "Write access is not required." 2072 OBJECT gmplsTunnelGPid 2073 MIN-ACCESS read-only 2074 DESCRIPTION 2075 "Write access is not required." 2077 OBJECT gmplsTunnelSecondary 2078 MIN-ACCESS read-only 2079 DESCRIPTION 2080 "Write access is not required." 2082 OBJECT gmplsTunnelDirection 2083 MIN-ACCESS read-only 2084 DESCRIPTION 2085 "Only forward (0) is required." 2087 OBJECT gmplsTunnelPathComp 2088 MIN-ACCESS read-only 2089 DESCRIPTION 2090 "Only explicit (2) is required." 2091 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2093 OBJECT gmplsTunnelUpstreamNotifyRecipientType 2094 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2095 MIN-ACCESS read-only 2096 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2097 is required." 2099 OBJECT gmplsTunnelUpstreamNotifyRecipient 2100 SYNTAX InetAddress (SIZE(0|4|16)) 2101 MIN-ACCESS read-only 2102 DESCRIPTION "An implementation is only required to support 2103 unknown(0), ipv4(1) and ipv6(2) sizes." 2105 OBJECT gmplsTunnelSendResvNotifyRecipientType 2106 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2107 MIN-ACCESS read-only 2108 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2109 is required." 2111 OBJECT gmplsTunnelSendResvNotifyRecipient 2112 SYNTAX InetAddress (SIZE(0|4|16)) 2113 MIN-ACCESS read-only 2114 DESCRIPTION "An implementation is only required to support 2115 unknown(0), ipv4(1) and ipv6(2) sizes." 2117 OBJECT gmplsTunnelDownstreamNotifyRecipientType 2118 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2119 MIN-ACCESS read-only 2120 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2121 is required." 2123 OBJECT gmplsTunnelDownstreamNotifyRecipient 2124 SYNTAX InetAddress (SIZE(0|4|16)) 2125 MIN-ACCESS read-only 2126 DESCRIPTION "An implementation is only required to support 2127 unknown(0), ipv4(1) and ipv6(2) sizes." 2129 OBJECT gmplsTunnelSendPathNotifyRecipientType 2130 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2131 MIN-ACCESS read-only 2132 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2133 is required." 2135 OBJECT gmplsTunnelSendPathNotifyRecipient 2136 SYNTAX InetAddress (SIZE(0|4|16)) 2137 MIN-ACCESS read-only 2138 DESCRIPTION "An implementation is only required to support 2139 unknown(0), ipv4(1) and ipv6(2) sizes." 2141 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2143 OBJECT gmplsTunnelAdminStatusFlags 2144 MIN-ACCESS read-only 2145 DESCRIPTION 2146 "Write access is not required." 2148 OBJECT gmplsTunnelExtraParamsPtr 2149 MIN-ACCESS read-only 2150 DESCRIPTION 2151 "Write access is not required." 2153 -- gmplsTunnelHopLabelStatuses has max access read-only 2155 OBJECT gmplsTunnelHopExplicitForwardLabel 2156 MIN-ACCESS read-only 2157 DESCRIPTION 2158 "Write access is not required." 2160 OBJECT gmplsTunnelHopExplicitForwardLabelPtr 2161 MIN-ACCESS read-only 2162 DESCRIPTION 2163 "Write access is not required." 2165 OBJECT gmplsTunnelHopExplicitReverseLabel 2166 MIN-ACCESS read-only 2167 DESCRIPTION 2168 "Write access is not required." 2170 OBJECT gmplsTunnelHopExplicitReverseLabelPtr 2171 MIN-ACCESS read-only 2172 DESCRIPTION 2173 "Write access is not required." 2175 -- gmplsTunnelARHopTable 2176 -- all objects have max access read-only 2178 -- gmplsTunnelCHopTable 2179 -- all objects have max access read-only 2181 -- gmplsTunnelReversePerfTable 2182 -- all objects have max access read-only 2184 -- gmplsTunnelErrorTable 2185 -- all objects have max access read-only 2187 OBJECT gmplsTunnelErrorReporterType 2188 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2189 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2190 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2192 is required." 2194 OBJECT gmplsTunnelErrorReporter 2195 SYNTAX InetAddress (SIZE(0|4|16)) 2196 DESCRIPTION "An implementation is only required to support 2197 unknown(0), ipv4(1) and ipv6(2)." 2198 ::= { gmplsTeCompliances 2 } 2200 gmplsTunnelGroup OBJECT-GROUP 2201 OBJECTS { 2202 gmplsTunnelDirection, 2203 gmplsTunnelReversePerfPackets, 2204 gmplsTunnelReversePerfHCPackets, 2205 gmplsTunnelReversePerfErrors, 2206 gmplsTunnelReversePerfBytes, 2207 gmplsTunnelReversePerfHCBytes, 2208 gmplsTunnelErrorLastErrorType, 2209 gmplsTunnelErrorLastTime, 2210 gmplsTunnelErrorReporterType, 2211 gmplsTunnelErrorReporter, 2212 gmplsTunnelErrorCode, 2213 gmplsTunnelErrorSubcode, 2214 gmplsTunnelErrorTLVs, 2215 gmplsTunnelErrorHelpString, 2216 gmplsTunnelUnnumIf 2217 } 2218 STATUS current 2219 DESCRIPTION 2220 "Necessary, but not sufficient, set of objects to implement 2221 tunnels. In addition, depending on the type of the tunnels 2222 supported (for example, manually configured or signaled, 2223 persistent or non-persistent, etc.), the 2224 gmplsTunnelSignaledGroup group is mandatory." 2225 ::= { gmplsTeGroups 1 } 2227 gmplsTunnelSignaledGroup OBJECT-GROUP 2228 OBJECTS { 2229 gmplsTunnelAttributes, 2230 gmplsTunnelLSPEncoding, 2231 gmplsTunnelSwitchingType, 2232 gmplsTunnelLinkProtection, 2233 gmplsTunnelGPid, 2234 gmplsTunnelSecondary, 2235 gmplsTunnelPathComp, 2236 gmplsTunnelUpstreamNotifyRecipientType, 2237 gmplsTunnelUpstreamNotifyRecipient, 2238 gmplsTunnelSendResvNotifyRecipientType, 2239 gmplsTunnelSendResvNotifyRecipient, 2240 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2242 gmplsTunnelDownstreamNotifyRecipientType, 2243 gmplsTunnelDownstreamNotifyRecipient, 2244 gmplsTunnelSendPathNotifyRecipientType, 2245 gmplsTunnelSendPathNotifyRecipient, 2246 gmplsTunnelAdminStatusFlags, 2247 gmplsTunnelHopLabelStatuses, 2248 gmplsTunnelHopExplicitForwardLabel, 2249 gmplsTunnelHopExplicitForwardLabelPtr, 2250 gmplsTunnelHopExplicitReverseLabel, 2251 gmplsTunnelHopExplicitReverseLabelPtr 2252 } 2253 STATUS current 2254 DESCRIPTION 2255 "Objects needed to implement signaled tunnels." 2256 ::= { gmplsTeGroups 2 } 2258 gmplsTunnelScalarGroup OBJECT-GROUP 2259 OBJECTS { 2260 gmplsTunnelsConfigured, 2261 gmplsTunnelsActive 2262 } 2263 STATUS current 2264 DESCRIPTION 2265 "Scalar objects needed to implement MPLS tunnels." 2266 ::= { gmplsTeGroups 3 } 2268 gmplsTunnelOptionalGroup OBJECT-GROUP 2269 OBJECTS { 2270 gmplsTunnelExtraParamsPtr, 2271 gmplsTunnelARHopLabelStatuses, 2272 gmplsTunnelARHopExplicitForwardLabel, 2273 gmplsTunnelARHopExplicitForwardLabelPtr, 2274 gmplsTunnelARHopExplicitReverseLabel, 2275 gmplsTunnelARHopExplicitReverseLabelPtr, 2276 gmplsTunnelARHopProtection, 2277 gmplsTunnelCHopLabelStatuses, 2278 gmplsTunnelCHopExplicitForwardLabel, 2279 gmplsTunnelCHopExplicitForwardLabelPtr, 2280 gmplsTunnelCHopExplicitReverseLabel, 2281 gmplsTunnelCHopExplicitReverseLabelPtr 2282 } 2283 STATUS current 2284 DESCRIPTION 2285 "The objects in this group are optional." 2286 ::= { gmplsTeGroups 6 } 2288 gmplsTeNotificationGroup NOTIFICATION-GROUP 2289 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2291 NOTIFICATIONS { 2292 gmplsTunnelDown 2293 } 2294 STATUS current 2295 DESCRIPTION 2296 "Set of notifications implemented in this module. None is 2297 mandatory." 2298 ::= { gmplsTeGroups 7 } 2300 END 2302 9. Security Considerations 2304 It is clear that the MIB modules described in this document in 2305 association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful 2306 for monitoring of MPLS and GMPLS tunnels. These MIB modules can also 2307 be used for configuration of certain objects, and anything that can 2308 be configured can be incorrectly configured, with potentially 2309 disastrous results. 2311 There are a number of management objects defined in these MIB modules 2312 with a MAX-ACCESS clause of read-write and/or read-create. Such 2313 objects may be considered sensitive or vulnerable in some network 2314 environments. The support for SET operations in a non-secure 2315 environment without proper protection can have a negative effect on 2316 network operations. These are the tables and objects and their 2317 sensitivity/vulnerability: 2319 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 2320 objects to provision GMPLS tunnels interfaces at their ingress 2321 LSRs. Unauthorized write access to objects in these tables, could 2322 result in disruption of traffic on the network. This is especially 2323 true if a tunnel has already been established. 2325 Some of the readable objects in these MIB modules (i.e., objects with 2326 a MAX-ACCESS other than not-accessible) may be considered sensitive 2327 or vulnerable in some network environments. It is thus important to 2328 control even GET and/or NOTIFY access to these objects and possibly 2329 to even encrypt the values of these objects when sending them over 2330 the network via SNMP. These are the tables and objects and their 2331 sensitivity/vulnerability: 2333 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 2334 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and the 2335 gmplsTunnelErrorTable collectively show the tunnel network 2336 topology and status. If an Administrator does not want to reveal 2337 this information, then these tables should be considered 2338 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2340 sensitive/vulnerable. 2342 SNMP versions prior to SNMPv3 did not include adequate security. Even 2343 if the network itself is secure (for example by using IPSec), even 2344 then, there is no control as to who on the secure network is allowed 2345 to access and GET/SET (read/change/create/delete) the objects in 2346 these MIB modules. 2348 It is RECOMMENDED that implementers consider the security features as 2349 provided by the SNMPv3 framework (see [RFC3410], section 8), 2350 including full support for the SNMPv3 cryptographic mechanisms (for 2351 authentication and privacy). 2353 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2354 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2355 enable cryptographic security. It is then a customer/operator 2356 responsibility to ensure that the SNMP entity giving access to an 2357 instance of this MIB module, is properly configured to give access to 2358 the objects only to those principals (users) that have legitimate 2359 rights to indeed GET or SET (change/create/delete) them. 2361 10. Acknowledgments 2363 This document is a product of the CCAMP Working Group. 2365 This document extends [RFC3812]. The authors would like to express 2366 their gratitude to all those who worked on that earlier MIB document. 2367 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 2368 contributions during an early implementation, and to Baktha 2369 Muralidharan, Tom Petch, Dave Thaler and Bert Wijnen for their review 2370 comments. 2372 Special thanks to Joan Cucchiara and Len Nieman for their help with 2373 compilation issues. 2375 Joan Cucchiara provided a helpful and very thorough MIB Doctor 2376 review. 2378 11. IANA Considerations 2380 -- (Note to RFC-Editor:) 2381 -- We request that you assign contiguous RFC numbers to the three GMPLS 2382 -- MIB documents. 2383 -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to 2384 -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to 2385 -- draft-ietf-ccamp-gmpls-te-mib. 2386 -- (Please remove this note prior to publication.) 2387 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2389 IANA is requested to root MIB objects in the MIB module contained in 2390 this document under the mplsStdMIB subtree. 2391 In the future, GMPLS related standards track MIB modules should be 2392 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to 2393 manage that namespace in the SMI Numbers registry [RFC3811]. New 2394 assignments can only be made via a Standards Action as specified in 2395 [RFC2434]. 2397 11.1. IANA Considerations for GMPLS-TE-STD-MIB 2399 The IANA is requested to assign { mplsStdMIB XXX } to the 2400 GMPLS-TE-STD-MIB module specified in this document, and to record 2401 the assignment in the SMI Numbers registry. 2403 -- RFC Editor. Please replace XXX above with assigned OID and remove 2404 -- this note 2406 11.2. Dependence on IANA MIB Modules 2408 Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, 2409 gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual 2410 conventions imported from the IANA-GMPLS-TC-MIB. The purpose of 2411 defining these textual conventions in a separate MIB module is to 2412 allow additional values to be defined without having to issue a new 2413 version of this document. The Internet Assigned Numbers Authority 2414 (IANA) is responsible for the assignment of all Internet numbers; it 2415 will administer the values associated with these textual conventions. 2417 The rules for additions or changes to the IANA-GMPLS-TC-MIB are 2418 outlined in the DESCRIPTION clause associated with its 2419 MODULE-IDENTITY statement. 2421 The current versions of the IANA-GMPLS-TC-MIB can be accessed from 2422 the IANA home page at: "http://www.iana.org/". 2424 11.2.1. IANA-GMPLS-TC-MIB Definition 2426 This is a temporary section intended to supply the base definition of 2427 an IANA MIB module. The normal procedure is that this MIB module is 2428 moved into the direct control of IANA, at which time this section 2429 should be deleted from this document. 2431 IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module 2432 specified in this document as { transmission YYY }. 2434 -- RFC Editor. 2435 -- Please replace YYY above with assigned OID and remove this note. 2437 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2439 IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN 2441 IMPORTS 2442 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 2443 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 2445 ianaGmpls MODULE-IDENTITY 2446 LAST-UPDATED 2447 "200604060001Z" -- 06 April 2006 00:00:01 GMT 2448 ORGANIZATION 2449 "IANA" 2450 CONTACT-INFO 2451 " Internet Assigned Numbers Authority 2452 Postal: USC/Information Sciences Institute 2453 4676 Admiralty Way, Marina del Rey, CA 90292 2454 Tel: +1 310 822 1511 2455 E-Mail: iana@isi.edu" 2456 DESCRIPTION 2457 "Copyright (C) The Internet Society (2006). The initial version 2458 of this MIB module was published in RFC YYY. For full legal 2459 notices see the RFC itself. Supplementary information 2460 may be available on: 2461 http://www.ietf.org/copyrights/ianamib.html" 2462 -- RFC Editor. Please replace YYY above with the correct RFC number 2463 -- Your actions may vary depending on how IANA chooses to handle 2464 -- this IANA MIB. 2465 -- Please remove this note. 2467 REVISION 2468 "200604060001Z" -- 06 April 2006 00:00:01 GMT 2469 DESCRIPTION 2470 "Initial version issued as part of RFC YYY." 2471 ::= { transmission YYY } 2472 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 2473 -- Please remove this note. 2475 IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION 2476 STATUS current 2477 DESCRIPTION 2478 "This data type is used as the syntax of the 2479 gmplsTunnelLSPEncoding object in the definition of 2480 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2482 gmplsTunnelLSPEncoding is used to represent and control 2483 the LSP encoding type of an LSP signaled by a GMPLS 2484 signaling protocol. 2486 This textual convention is strongly tied to the LSP 2488 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2490 Encoding Types sub-registry of the GMPLS Signaling 2491 Parameters registry managed by IANA. Values should be 2492 assigned by IANA in step with the LSP Encoding Types 2493 sub-registry and using the same registry management rules. 2494 However, the actual values used in this textual convention 2495 are solely within the purview of IANA and do not 2496 necessarily match the values in the values in the LSP 2497 Encoding Types sub-registry. 2499 The definition of this textual convention with the 2500 addition of newly assigned values is published 2501 periodically by the IANA, in either the Assigned 2502 Numbers RFC, or some derivative of it specific to 2503 Internet Network Management number assignments. (The 2504 latest arrangements can be obtained by contacting the 2505 IANA.) 2507 Requests for new values should be made to IANA via 2508 email (iana@isi.edu)." 2509 REFERENCE 2510 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2511 Signaling Functional Description, RFC 3471, section 2512 3.1.1. 2513 2. Generalized MPLS Signalling Extensions for G.709 Optical 2514 Transport Networks Control, RFC 4328, section 3.1.1." 2515 -- RFC Editor. Please update this reference to the RFC before 2516 -- publication and remove this note 2517 SYNTAX INTEGER { 2518 tunnelLspNotGmpls (0), -- GMPLS is not in use 2519 -- This is not part of the LSP 2520 -- Encoding Type registry, but 2521 -- is needed for the correct 2522 -- functioning of the 2523 -- GMPLS-TE-STD-MIB 2524 tunnelLspPacket (1), -- Packet 2525 tunnelLspEthernet (2), -- Ethernet 2526 tunnelLspAnsiEtsiPdh (3), -- PDH 2527 -- the value 4 is deprecated 2528 tunnelLspSdhSonet (5), -- SDH or SONET 2529 -- the value 6 is deprecated 2530 tunnelLspDigitalWrapper (7), -- Digital Wrapper 2531 tunnelLspLambda (8), -- Lambda 2532 tunnelLspFiber (9), -- Fiber 2533 -- the value 10 is deprecated 2534 tunnelLspFiberChannel (11), -- Fiber Channel 2535 tunnelDigitalPath (12), -- Digital Path 2536 tunnelOpticalChannel (13) -- Optical Channel 2537 } 2539 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2541 IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION 2542 STATUS current 2543 DESCRIPTION 2544 "This data type is used as the syntax of the 2545 gmplsTunnelSwitchingType object in the definition of 2546 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2548 gmplsTunnelSwitchingType is used to represent and 2549 control the LSP switching type of an LSP signaled by a 2550 GMPLS signaling protocol. 2552 This textual convention is strongly tied to the Switching 2553 Types sub-registry of the GMPLS Signaling Parameters 2554 registry managed by IANA. Values should be assigned by IANA 2555 in step with the Switching Types sub-registry and using the 2556 same registry management rules. However, the actual values 2557 used in this textual convention are solely within the 2558 purview of IANA and do not necessarily match the values in 2559 the values in the Switching Types sub-registry. 2561 The definition of this textual convention with the 2562 addition of newly assigned values is published 2563 periodically by the IANA, in either the Assigned 2564 Numbers RFC, or some derivative of it specific to 2565 Internet Network Management number assignments. (The 2566 latest arrangements can be obtained by contacting the 2567 IANA.) 2569 Requests for new values should be made to IANA via 2570 email (iana@isi.edu)." 2571 REFERENCE 2572 "1. Routing Extensions in Support of Generalized 2573 Multi-Protocol Label Switching, RFC 4202, section 2.4. 2574 2. Generalized Multi-Protocol Label Switching (GMPLS) 2575 Signaling Functional Description, RFC 3471, section 2576 3.1.1." 2577 SYNTAX INTEGER { 2578 unknown (0), -- none of the following, or not known 2579 psc1 (1), -- Packet-Switch-Capable 1 2580 psc2 (2), -- Packet-Switch-Capable 2 2581 psc3 (3), -- Packet-Switch-Capable 3 2582 psc4 (4), -- Packet-Switch-Capable 4 2583 l2sc (51), -- Layer-2-Switch-Capable 2584 tdm (100), -- Time-Division-Multiplex 2585 lsc (150), -- Lambda-Switch-Capable 2586 fsc (200) -- Fiber-Switch-Capable 2587 } 2589 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2591 IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION 2592 STATUS current 2593 DESCRIPTION 2594 "This data type is used as the syntax of the 2595 gmplsTunnelGPid object in the definition of 2596 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2598 gmplsTunnelGPid is used to represent and control the LSP 2599 Generalized Protocol Identifier (G-PID) of an LSP 2600 signaled by a GMPLS signaling protocol. 2602 This textual convention is strongly tied to the Generalized 2603 PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters 2604 registry managed by IANA. Values should be assigned by IANA 2605 in step with the Generalized PIDs (G-PID) sub-registry and 2606 using the same registry management rules. However, the 2607 actual values used in this textual convention are solely 2608 within the purview of IANA and do not necessarily match the 2609 values in the values in the Generalized PIDs (G-PID) 2610 sub-registry. 2612 The definition of this textual convention with the 2613 addition of newly assigned values is published 2614 periodically by the IANA, in either the Assigned 2615 Numbers RFC, or some derivative of it specific to 2616 Internet Network Management number assignments. (The 2617 latest arrangements can be obtained by contacting the 2618 IANA.) 2620 Requests for new values should be made to IANA via 2621 email (iana@isi.edu)." 2622 REFERENCE 2623 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2624 Signaling Functional Description, RFC 3471, section 2625 3.1.1. 2626 2. Generalized MPLS Signalling Extensions for G.709 Optical 2627 Transport Networks Control, RFC 4328, section 3.1.3." 2628 -- RFC Editor. Please update this reference to the RFC before 2629 -- publication and remove this note 2630 SYNTAX INTEGER { 2631 unknown(0), -- unknown or none of the following 2632 -- the values 1, 2, 3 and 4 are reserved in RFC 3471 2633 asynchE4(5), 2634 asynchDS3T3(6), 2635 asynchE3(7), 2636 bitsynchE3(8), 2637 bytesynchE3(9), 2639 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2641 asynchDS2T2(10), 2642 bitsynchDS2T2(11), 2643 reservedByRFC3471first(12), 2644 asynchE1(13), 2645 bytesynchE1(14), 2646 bytesynch31ByDS0(15), 2647 asynchDS1T1(16), 2648 bitsynchDS1T1(17), 2649 bytesynchDS1T1(18), 2650 vc1vc12(19), 2651 reservedByRFC3471second(20), 2652 reservedByRFC3471third(21), 2653 ds1SFAsynch(22), 2654 ds1ESFAsynch(23), 2655 ds3M23Asynch(24), 2656 ds3CBitParityAsynch(25), 2657 vtLovc(26), 2658 stsSpeHovc(27), 2659 posNoScramble16BitCrc(28), 2660 posNoScramble32BitCrc(29), 2661 posScramble16BitCrc(30), 2662 posScramble32BitCrc(31), 2663 atm(32), 2664 ethernet(33), 2665 sdhSonet(34), 2666 digitalwrapper(36), 2667 lambda(37), 2668 ansiEtsiPdh (38), 2669 lapsSdh (40), 2670 fddi (41), 2671 dqdb (42), 2672 fiberChannel3 (43), 2673 hdlc (44), 2674 ethernetV2DixOnly (45), 2675 ethernet802dot3Only (46), 2676 g709ODUj (47), 2677 g709OTUk (48), 2678 g709CBRorCBRa (49), 2679 g709CBRb (50), 2680 g709BSOT (51), 2681 g709BSNT (52), 2682 gfpIPorPPP (53), 2683 gfpEthernetMAC (54), 2684 gfpEthernetPHY (55), 2685 g709ESCON (56), 2686 g709FICON (57), 2687 g709FiberChannel (58) 2688 } 2690 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2692 IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION 2693 STATUS current 2694 DESCRIPTION 2695 "This data type is used as the syntax of the 2696 gmplsTunnelAdminStatusFlags object in the definition of 2697 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2699 gmplsTunnelAdminStatusFlags determines the setting of the 2700 Admin Status flags in the Admin Status object or TLV, as 2701 described in RFC 3471. Setting this object to a non-zero 2702 value will result in the inclusion of the Admin Status 2703 object or TLV on signaling messages. 2705 This textual convention is strongly tied to the Admin 2706 Status Flags sub-registry of the GMPLS Signaling Parameters 2707 registry managed by IANA. Values should be assigned by IANA 2708 in step with the Admin Status Flags sub-registry and using 2709 the same registry management rules. However, the actual 2710 values used in this textual convention are solely within 2711 the purview of IANA and do not necessarily match the values 2712 in the values in the Admin Status Flags sub-registry. 2713 -- RFC Editor / IANA note 2714 -- At the time of writing, the referenced Admin Status Flags 2715 -- sub-registry has not been created. 2716 -- It is not requested in RFC 3471 (the base reference for this protocol 2717 -- element). But it is requested in two I-Ds that are ahead of this MIB 2718 -- module in the IETF process 2719 -- draft-ietf-ccamp-gmpls-recovery-e2e-signaling 2720 -- draft-ietf-ccamp-gmpls-alarm-spec 2721 -- Note, however, that at this stage no request is made to IANA for the 2722 -- definition of values in the textual convention to match any of the 2723 -- Admin Status bits except those defined in RFC 3471. IANA is free to 2724 -- define additional values but these will not be used by this MIB 2725 -- module (although future MIB modules will doubtless use them). 2726 -- 2727 -- RFC Editor. Please update the previous paragraph to use the correct 2728 -- name for the new sub-registry as defined by IANA, and delete this 2729 -- note. 2731 The definition of this textual convention with the 2732 addition of newly assigned values is published 2733 periodically by the IANA, in either the Assigned 2734 Numbers RFC, or some derivative of it specific to 2735 Internet Network Management number assignments. (The 2736 latest arrangements can be obtained by contacting the 2737 IANA.) 2739 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2741 Requests for new values should be made to IANA via 2742 email (iana@isi.edu)." 2744 REFERENCE 2745 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2746 Signaling Functional Description, RFC 3471, section 8." 2747 SYNTAX BITS { 2748 reflect (0), -- Reflect bit (RFC 3471) 2749 reserved1 (1), -- reserved 2750 reserved2 (2), -- reserved 2751 reserved3 (3), -- reserved 2752 reserved4 (4), -- reserved 2753 reserved5 (5), -- reserved 2754 reserved6 (6), -- reserved 2755 reserved7 (7), -- reserved 2756 reserved8 (8), -- reserved 2757 reserved9 (9), -- reserved 2758 reserved10 (10), -- reserved 2759 reserved11 (11), -- reserved 2760 reserved12 (12), -- reserved 2761 reserved13 (13), -- reserved 2762 reserved14 (14), -- reserved 2763 reserved15 (15), -- reserved 2764 reserved16 (16), -- reserved 2765 reserved17 (17), -- reserved 2766 reserved18 (18), -- reserved 2767 reserved19 (19), -- reserved 2768 reserved20 (20), -- reserved 2769 reserved21 (21), -- reserved 2770 reserved22 (22), -- reserved 2771 reserved23 (23), -- reserved 2772 reserved24 (24), -- reserved 2773 reserved25 (25), -- reserved 2774 reserved26 (26), -- reserved 2775 reserved27 (27), -- reserved 2776 reserved28 (28), -- reserved 2777 testing (29), -- Testing bit (RFC 3473) 2778 administrativelyDown (30), -- Admin down (RFC 3473) 2779 deleteInProgress (31) -- Delete bit (RFC 3473) 2780 } 2782 END 2784 12. References 2786 12.1. Normative References 2787 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2789 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2790 Requirements Levels", BCP 14, RFC 2119, March 1997. 2792 [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. 2793 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 2794 1 Functional Specification", RFC 2205, September 1997. 2796 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2797 J., Rose, M., and S. Waldbusser, "Structure of 2798 Management Information Version 2 (SMIv2)", STD 58, RFC 2799 2578, April 1999. 2801 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2802 J., Rose, M., and S. Waldbusser, "Textual Conventions 2803 for SMIv2", STD 58, RFC 2579, April 1999. 2805 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2806 J., Rose, M., and S. Waldbusser, "Conformance Statements 2807 for SMIv2", STD 58, RFC 2580, April 1999. 2809 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2810 "Multiprotocol Label Switching Architecture", RFC 3031, 2811 January 2001. 2813 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 2814 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 2815 Tunnels", RFC 3209, December 2001. 2817 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2818 Architecture for Describing Simple Network Management 2819 Protocol (SNMP) Management Frameworks", STD 62, RFC 2820 3411, December 2002. 2822 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 2823 (GMPLS) Signaling Functional Description", RFC 3471, 2824 January 2003. 2826 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 2827 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 2828 Engineering (RSVP-TE) Extensions", RFC 3473, January 2829 2003. 2831 [RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered 2832 Links in Resource ReSerVation Protocol - Traffic 2833 Engineering (RSVP-TE)", RFC 3477, January 2003. 2835 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 2836 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2838 Conventions and for Multiprotocol Label Switching (MPLS) 2839 Management", RFC 3811, June 2004. 2841 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2842 "Multiprotocol Label Switching (MPLS) Traffic 2843 Engineering (TE) Management Information Base (MIB)", 2844 RFC 3812, June 2004. 2846 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2847 "Multiprotocol Label Switching (MPLS) Label Switching 2848 (LSR) Router Management Information Base (MIB)", RFC 2849 3813, June 2004. 2851 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 2852 Switching (GMPLS) Architecture", RFC 3945, October 2004. 2854 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2855 Schoenwaelder, "Textual Conventions for Internet Network 2856 Addresses", RFC 4001, February 2005. 2858 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in 2859 Support of Generalized Multi-Protocol Label Switching", 2860 RFC 4202, October 2005. 2862 [RFC4328] Papadimitriou, D., Ed., "Generalized MPLS Signalling 2863 Extensions for G.709 Optical Transport Networks 2864 Control", RFC4328, January 2006. 2866 [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 2867 Label Switching (GMPLS) Label Switching Router (LSR) 2868 Management Information Base", 2869 draft-ietf-ccamp-gmpls-lsr-mib, work in progress. 2871 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 2872 Conventions for Multiprotocol Label Switching (MPLS) 2873 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 2874 progress. 2876 12.2. Informative References 2878 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2879 MIB", RFC 2863, June 2000. 2881 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2882 "Introduction and Applicability Statements for 2883 Internet-Standard Management Framework", RFC 3410, 2884 December 2002. 2886 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2888 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 2889 Multi-Protocol Label Switching (MPLS) Signaling 2890 - Constraint-based Routed Label Distribution Protocol 2891 (CR-LDP) Extensions", RFC 3472, January 2003. 2893 13. Contact Information 2895 Thomas D. Nadeau 2896 Cisco Systems, Inc. 2897 1414 Massachusetts Ave. 2898 Boxborough, MA 01719 2899 Email: tnadeau@cisco.com 2901 Cheenu Srinivasan 2902 Bloomberg L.P. 2903 731 Lexington Ave. 2904 New York, NY 10022 2905 Phone: +1-212-617-3682 2906 Email: cheenu@bloomberg.net 2908 Adrian Farrel 2909 Old Dog Consulting 2910 Phone: +44-(0)-1978-860944 2911 Email: adrian@olddog.co.uk 2913 Tim Hall 2914 Data Connection Ltd. 2915 100 Church Street 2916 Enfield, Middlesex 2917 EN2 6BQ, UK 2918 Phone: +44 20 8366 1177 2919 Email: tim.hall@dataconnection.com 2921 Ed Harrison 2922 Data Connection Ltd. 2923 100 Church Street 2924 Enfield, Middlesex 2925 EN2 6BQ, UK 2926 Phone: +44 20 8366 1177 2927 Email: ed.harrison@dataconnection.com 2929 14. Intellectual Property Considerations 2930 draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 2932 The IETF takes no position regarding the validity or scope of any 2933 Intellectual Property Rights or other rights that might be claimed to 2934 pertain to the implementation or use of the technology described in 2935 this document or the extent to which any license under such rights 2936 might or might not be available; nor does it represent that it has 2937 made any independent effort to identify any such rights. Information 2938 on the procedures with respect to rights in RFC documents can be 2939 found in BCP 78 and BCP 79. 2941 Copies of IPR disclosures made to the IETF Secretariat and any 2942 assurances of licenses to be made available, or the result of an 2943 attempt made to obtain a general license or permission for the use of 2944 such proprietary rights by implementers or users of this 2945 specification can be obtained from the IETF on-line IPR repository at 2946 http://www.ietf.org/ipr. 2948 The IETF invites any interested party to bring to its attention any 2949 copyrights, patents or patent applications, or other proprietary 2950 rights that may cover technology that may be required to implement 2951 this standard. Please address the information to the IETF at 2952 ietf-ipr@ietf.org. 2954 15. Full Copyright Statement 2956 Copyright (C) The Internet Society (2006). This document is subject 2957 to the rights, licenses and restrictions contained in BCP 78, and 2958 except as set forth therein, the authors retain all their rights. 2960 This document and the information contained herein are provided on an 2961 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2962 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2963 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2964 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2965 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2966 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.