idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-15.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 2952. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2923. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2930. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2936. ** 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 6585 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 2404, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2205' is defined on line 2778, but no explicit reference was found in the text == Unused Reference: 'GMPLSTCMIB' is defined on line 2856, but no explicit reference was found in the text 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-15.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-15.txt April 20, 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-15.txt April 20, 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 the 131 IANA-GMPLS-TC-MIB MIB module. 133 2. Terminology 135 This document uses terminology from the MPLS architecture document 136 [RFC3031], from the GMPLS architecture document [RFC3945], and from 137 the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used 138 terms are described next. 140 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 141 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 142 LSRs, each segment being associated with one GMPLS enabled interface. 143 These are also referred to as tunnel segments. 145 Additionally, at an intermediate LSR, we model a connection as 146 consisting of one or more in-segments and/or one or more 147 out-segments. The binding or interconnection between in-segments and 148 out-segments in performed using a cross-connect. 150 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 152 These segment and cross-connect objects are defined in the MPLS Label 153 Switch Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the 154 GMPLS Label Switching Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] 155 for the GMPLS-specific extensions to these objects. 157 3. The Internet-Standard Management Framework 159 For a detailed overview of the documents that describe the current 160 Internet-Standard Management Framework, please refer to section 7 of 161 RFC 3410 [RFC3410]. 163 Managed objects are accessed via a virtual information store, termed 164 the Management Information Base or MIB. MIB objects are generally 165 accessed through the Simple Network Management Protocol (SNMP). 166 Objects in the MIB are defined using the mechanisms defined in the 167 Structure of Management Information (SMI). This memo specifies a MIB 168 module that is compliant to the SMIv2, which is described in STD 58, 169 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 170 [RFC2580]. 172 4. Outline 174 Support for GMPLS traffic-engineered tunnels requires the following 175 configuration. 177 - Setting up tunnels with appropriate MPLS configuration parameters 178 using [RFC3812]. 179 - Extending the tunnels with GMPLS configuration parameters. 180 - Configuring tunnel loose and strict source routed hops. 182 These actions may need to be accompanied with corresponding actions 183 using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel 184 segments, if this is done manually. Also, the in-segment and 185 out-segment performance tables, mplsInSegmentPerfTable and 186 mplsOutSegmentPerfTable [RFC3813], should be used to determine 187 performance of the tunnels and tunnel segments although it should be 188 noted that those tables may not be appropriate for measuring 189 performance on some types of GMPLS links. 191 4.1. Summary of GMPLS Traffic Engineering MIB Module 193 The following tables contain MIB objects for performing the actions 194 listed above when they cannot be performed solely using MIB objects 195 defined in MPLS-TE-STD-MIB [RFC3812]. 197 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 198 tunnel configuration parameters. 200 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 202 - Tunnel specified, actual, and computed hop tables 203 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 204 gmplsTunnelCHopTable) for providing additional configuration of 205 strict and loose source routed tunnel hops. 206 - Performance and error reporting tables (gmplsTunnelReversePerfTable 207 and gmplsTunnelErrorTable). 209 These tables are described in the subsequent sections. 211 Additionally, the GMPLS-TE-STD-MIB module contains a new 212 notification. 214 - The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be used 215 for all GMPLS tunnels in place of the mplsTunnelDown notification 216 defined in [RFC3812]. An implementation must not issue both the 217 gmplsTunnelDown and the mplsTunnelDown notifications for the same 218 event. As well as indicating that a tunnel has transitioned to 219 operational down state, this new notification indicates the cause 220 of the failure. 222 5. Brief Description of GMPLS TE MIB Objects 224 The objects described in this section support the functionality 225 described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables 226 support both manually configured and signaled tunnels. 228 5.1. gmplsTunnelTable 230 The gmplsTunnelTable extends the MPLS traffic engineering MIB module 231 (MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created 232 between an LSR and a remote endpoint, and existing GMPLS tunnels to 233 be reconfigured or removed. 235 Note that we only support point-to-point tunnel segments, although 236 multi-point-to-point and point-to-multi-point connections are 237 supported by an LSR acting as a cross-connect. 239 Each tunnel can thus have one out-segment originating at an LSR 240 and/or one in-segment terminating at that LSR. 242 Three objects within this table utilize enumerations in order to map 243 to enumerations that are used in GMPLS signaling. In order to protect 244 the GMPLS-TE-STD-MIB module from changes (in particular, extensions) 245 to the range of enumerations supported by the signaling protocols, 246 these MIB objects use Textual Conventions with values maintained by 247 IANA. For further details, see the IANA Considerations section of 248 this document. 250 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 252 5.2. gmplsTunnelHopTable 254 The gmplsTunnelHopTable is used to indicate additional parameters for 255 the hops, strict or loose, of a GMPLS tunnel defined in 256 gmplsTunnelTable, when it is established using signaling. Multiple 257 tunnels may share hops by pointing to the same entry in this table. 259 5.3. gmplsTunnelARHopTable 261 The gmplsTunnelARHopTable is used to indicate the actual hops 262 traversed by a tunnel as reported by the signaling protocol after the 263 tunnel is setup. The support of this table is optional since not all 264 GMPLS signaling protocols support this feature. 266 5.4. gmplsTunnelCHopTable 268 The gmplsTunnelCHopTable lists the actual hops computed by a 269 constraint-based routing algorithm based on the gmplsTunnelHopTable. 270 The support of this table is optional since not all implementations 271 support computation of hop lists using a constraint-based routing 272 protocol. 274 5.5. gmplsTunnelErrorTable 276 The gmplsTunnelErrorTable provides access to information about the 277 last error that occurred on each tunnel known about by the MIB. It 278 indicates the nature of the error, when and how it was reported and 279 can give recovery advice through an admin string. 281 5.6. gmplsTunnelReversePerfTable 283 gmplsTunnelReversePerfTable provides additional counters to measure 284 the performance of bidirectional GMPLS tunnels in which packets are 285 visible. It supplements the counters in mplsTunnelPerfTable and 286 augments gmplsTunnelTable. 288 Note that not all counters may be appropriate or available for some 289 types of tunnel. 291 5.7. Use of 32-bit and 64-bit Counters 293 64-bit counters are provided in the GMPLS-TE-STD-MIB module for 294 high-speed interfaces where the use of 32-bit counters might be 295 impractical. The requirements on the use of 32-bit and 64-bit 296 counters (copied verbatim from [RFC2863]) are as follows: 298 For interfaces that operate at 20,000,000 (20 million) bits per 299 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 301 second or less, 32-bit byte and packet counters MUST be supported. 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-15.txt April 20, 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 400 gmplsTunnelPathComp = explicit(2), 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 450 mplsTunnelHopIpv4Addr = 192.0.2.2, 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-15.txt April 20, 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], and 504 [RFC4202]. 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-15.txt April 20, 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. 570 " 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 598 SYNTAX Gauge32 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 648 An entry can be created by a network administrator via SNMP SET 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 697 This object contains information that is only used by the 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 747 ::= { gmplsTunnelEntry 3 } 749 gmplsTunnelSwitchingType OBJECT-TYPE 750 SYNTAX IANAGmplsSwitchingTypeTC 751 MAX-ACCESS read-create 752 STATUS current 753 DESCRIPTION 754 "Indicates the type of switching that should be performed on 755 a particular link. This field is needed for links that 756 advertise more than one type of switching capability. 758 The values to use are defined in the textual convention 759 IANAGmplsSwitchingTypeTC found in the IANA-GMPLS-TC-MIB module. 761 This object is only meaningful if gmplsTunnelLSPEncoding is not 762 set to 'tunnelLspNotGmpls'." 763 DEFVAL { unknown } 764 ::= { gmplsTunnelEntry 4 } 766 gmplsTunnelLinkProtection OBJECT-TYPE 767 SYNTAX BITS { 768 extraTraffic(0), 769 unprotected(1), 770 shared (2), 771 dedicatedOneToOne (3), 772 dedicatedOnePlusOne(4), 773 enhanced(5) 774 } 775 MAX-ACCESS read-create 776 STATUS current 777 DESCRIPTION 778 "This bitmask indicates the level of link protection required. A 779 value of zero (no bits set) indicates that any protection may be 780 used. The following describes these bitfields: 782 extraTraffic 783 This flag is set to indicate that the LSP should use links 784 that are protecting other (primary) traffic. Such LSPs may be 785 preempted when the links carrying the (primary) traffic being 786 protected fail. 788 unprotected 789 This flag is set to indicate that the LSP should not use any 790 link layer protection. 792 shared 793 This flag is set to indicate that a shared link layer 794 protection scheme, such as 1:N protection, should be used to 795 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 797 support the LSP. 799 dedicatedOneToOne 800 This flag is set to indicate that a dedicated link layer 801 protection scheme, i.e., 1:1 protection, should be used to 802 support the LSP. 804 dedicatedOnePlusOne 805 This flag is set to indicate that a dedicated link layer 806 protection scheme, i.e., 1+1 protection, should be used to 807 support the LSP. 809 enhanced 810 This flag is set to indicate that a protection scheme that is 811 more reliable than Dedicated 1+1 should be used, e.g., 4 fiber 812 BLSR/MS-SPRING. 814 This object is only meaningful if gmplsTunnelLSPEncoding is 815 not set to 'tunnelLspNotGmpls'." 817 REFERENCE 818 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 819 Functional Description, RFC 3471, section 7.1." 820 DEFVAL { { } } 821 ::= { gmplsTunnelEntry 5 } 823 gmplsTunnelGPid OBJECT-TYPE 824 SYNTAX IANAGmplsGeneralizedPidTC 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "This object indicates the payload carried by the LSP. It is only 829 required when GMPLS will be used for this LSP. 831 The values to use are defined in the textual convention 832 IANAGmplsGeneralizedPidTC found in the IANA-GMPLS-TC-MIB module. 834 This object is only meaningful if gmplsTunnelLSPEncoding is not 835 set to 'tunnelLspNotGmpls'." 836 DEFVAL { unknown } 837 ::= { gmplsTunnelEntry 6 } 839 gmplsTunnelSecondary OBJECT-TYPE 840 SYNTAX TruthValue 841 MAX-ACCESS read-create 842 STATUS current 843 DESCRIPTION 844 "Indicates that the requested LSP is a secondary LSP. 846 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 848 This object is only meaningful if gmplsTunnelLSPEncoding is not 849 set to 'tunnelLspNotGmpls'." 850 REFERENCE 851 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 852 Functional Description, RFC 3471, section 7.1." 853 DEFVAL { false } 854 ::= { gmplsTunnelEntry 7 } 856 gmplsTunnelDirection OBJECT-TYPE 857 SYNTAX INTEGER { 858 forward (0), 859 bidirectional (1) 860 } 861 MAX-ACCESS read-create 862 STATUS current 863 DESCRIPTION 864 "Whether this tunnel carries forward data only (is 865 unidirectional) or is bidirectional. 867 Values of this object other than 'forward' are meaningful 868 only if gmplsTunnelLSPEncoding is not set to 869 'tunnelLspNotGmpls'." 870 DEFVAL { forward } 871 ::= { gmplsTunnelEntry 8 } 873 gmplsTunnelPathComp OBJECT-TYPE 874 SYNTAX INTEGER { 875 dynamicFull(1), -- CSPF fully computed 876 explicit(2), -- fully specified path 877 dynamicPartial(3) -- CSPF partially computed 878 } 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "This value instructs the source node on how to perform path 883 computation on the explicit route specified by the associated 884 entries in the gmplsTunnelHopTable. 886 dynamicFull 887 The user specifies at least the source and 888 destination of the path and expects that the CSPF 889 will calculate the remainder of the path. 891 explicit 892 The user specifies the entire path for the tunnel to 893 take. This path may contain strict or loose hops. 894 Evaluation of the explicit route will be performed 895 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 897 hop by hop through the network. 899 dynamicPartial 900 The user specifies at least the source and 901 destination of the path and expects that the CSPF 902 will calculate the remainder of the path. The path 903 computed by CSPF is allowed to be only partially 904 computed allowing the remainder of the path to be 905 filled in across the network. 907 When an entry is present in gmplsTunnelTable for a tunnel, 908 gmplsTunnelPathComp MUST be used and any corresponding 909 mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable 910 MUST be ignored and SHOULD not be set. 912 mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of 913 MPLS-TE-STD-MIB. 915 This object should be ignored if value of gmplsTunnelLSPEncoding 916 is 'tunnelLspNotGmpls'." 917 REFERENCE 918 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 919 Management Information Base (MIB), RFC 3812." 920 DEFVAL { dynamicFull } 921 ::= { gmplsTunnelEntry 9 } 923 gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE 924 SYNTAX InetAddressType 925 MAX-ACCESS read-create 926 STATUS current 927 DESCRIPTION 928 "This object is used to aid in interpretation of 929 gmplsTunnelUpstreamNotifyRecipient." 930 DEFVAL { unknown } 931 ::= { gmplsTunnelEntry 10 } 933 gmplsTunnelUpstreamNotifyRecipient OBJECT-TYPE 934 SYNTAX InetAddress 935 MAX-ACCESS read-create 936 STATUS current 937 DESCRIPTION 938 "Indicates the address of the upstream recipient for Notify 939 messages relating to this tunnel and issued by this LSR. This 940 information is typically received from an upstream LSR in a Path 941 message. 943 This object is only valid when signaling a tunnel using RSVP. 945 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 947 It is also not valid at the head end of a tunnel since there are 948 no upstream LSRs to which to send a Notify message. 950 This object is interpreted in the context of the value of 951 gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0, 952 the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to 953 unknown(0)." 954 REFERENCE 955 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 956 section 4.2. " 957 DEFVAL { '00000000'H } -- 0.0.0.0 958 ::= { gmplsTunnelEntry 11 } 960 gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE 961 SYNTAX InetAddressType 962 MAX-ACCESS read-create 963 STATUS current 964 DESCRIPTION 965 "This object is used to aid in interpretation of 966 gmplsTunnelSendResvNotifyRecipient." 967 DEFVAL { unknown } 968 ::= { gmplsTunnelEntry 12 } 970 gmplsTunnelSendResvNotifyRecipient OBJECT-TYPE 971 SYNTAX InetAddress 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "Indicates to an upstream LSR the address to which it should send 976 downstream Notify messages relating to this tunnel. 978 This object is only valid when signaling a tunnel using RSVP. 980 It is also not valid at the head end of the tunnel since no Resv 981 messages are sent from that LSR for this tunnel. 983 If set to 0, no Notify Request object will be included in the 984 outgoing Resv messages. 986 This object is interpreted in the context of the value of 987 gmplsTunnelSendResvNotifyRecipientType. If this object is set to 988 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be 989 set to unknown(0)." 990 REFERENCE 991 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 992 section 4.2. " 993 DEFVAL { '00000000'H } -- 0.0.0.0 994 ::= { gmplsTunnelEntry 13 } 995 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 997 gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE 998 SYNTAX InetAddressType 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "This object is used to aid in interpretation of 1003 gmplsTunnelDownstreamNotifyRecipient." 1004 DEFVAL { unknown } 1005 ::= { gmplsTunnelEntry 14 } 1007 gmplsTunnelDownstreamNotifyRecipient OBJECT-TYPE 1008 SYNTAX InetAddress 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "Indicates the address of the downstream recipient for Notify 1013 messages relating to this tunnel and issued by this LSR. This 1014 information is typically received from an upstream LSR in a Resv 1015 message. This object is only valid when signaling a tunnel using 1016 RSVP. 1018 It is also not valid at the tail end of a tunnel since there are 1019 no downstream LSRs to which to send a Notify message. 1020 This object is interpreted in the context of the value of 1021 gmplsTunnelDownstreamNotifyRecipient. If this object is set to 1022 0, the value of gmplsTunnelDownstreamNotifyRecipient MUST be set 1023 to unknown(0)." 1024 REFERENCE 1025 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1026 section 4.2. 1027 " 1028 DEFVAL { '00000000'H } -- 0.0.0.0 1029 ::= { gmplsTunnelEntry 15 } 1031 gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE 1032 SYNTAX InetAddressType 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "This object is used to aid in interpretation of 1037 gmplsTunnelSendPathNotifyRecipient." 1038 DEFVAL { unknown } 1039 ::= { gmplsTunnelEntry 16 } 1041 gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE 1042 SYNTAX InetAddress 1043 MAX-ACCESS read-create 1044 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1046 STATUS current 1047 DESCRIPTION 1048 "Indicates to a downstream LSR the address to which it should 1049 send upstream Notify messages relating to this tunnel. 1051 This object is only valid when signaling a tunnel using RSVP. 1053 It is also not valid at the tail end of the tunnel since no Path 1054 messages are sent from that LSR for this tunnel. 1056 If set to 0, no Notify Request object will be included in the 1057 outgoing Path messages. 1059 This object is interpreted in the context of the value of 1060 gmplsTunnelSendPathNotifyRecipientType. If this object is set to 1061 0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be 1062 set to unknown(0)." 1064 REFERENCE 1065 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1066 section 4.2. " 1067 DEFVAL { '00000000'H } -- 0.0.0.0 1068 ::= { gmplsTunnelEntry 17 } 1070 gmplsTunnelAdminStatusFlags OBJECT-TYPE 1071 SYNTAX IANAGmplsAdminStatusInformationTC 1072 MAX-ACCESS read-create 1073 STATUS current 1074 DESCRIPTION 1075 "Determines the setting of the Admin Status flags in the 1076 Admin Status object or TLV, as described in RFC 3471. Setting 1077 this field to a non-zero value will result in the inclusion of 1078 the admin status object on signaling messages. 1080 The values to use are defined in the textual convention 1081 IANAGmplsAdminStatusInformationTC found in the 1082 IANA-GMPLS-TC-MIB module. 1084 This value of this object can be modified when the 1085 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 1086 is active(1). By doing so, a new signaling message will be 1087 triggered including the requested Admin Status object or 1088 TLV." 1089 REFERENCE 1090 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1091 Functional Description, RFC 3471, section 8." 1092 DEFVAL { { } } 1093 ::= { gmplsTunnelEntry 18 } 1094 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1096 gmplsTunnelExtraParamsPtr OBJECT-TYPE 1097 SYNTAX RowPointer 1098 MAX-ACCESS read-create 1099 STATUS current 1100 DESCRIPTION 1101 "Some Tunnels will run over transports that can usefully support 1102 technology-specific additional parameters (for example, SONET 1103 resource usage). Such parameters can be supplied in an external 1104 table and referenced from here. 1106 A value of zeroDotzero in this attribute indicates that there 1107 is no such additional information." 1108 DEFVAL { zeroDotZero } 1109 ::= { gmplsTunnelEntry 19 } 1111 gmplsTunnelHopTable OBJECT-TYPE 1112 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 1113 MAX-ACCESS not-accessible 1114 STATUS current 1115 DESCRIPTION 1116 "The gmplsTunnelHopTable sparsely extends the mplsTunnelHopTable 1117 of MPLS-TE-STD-MIB. It is used to indicate the explicit labels 1118 to be used in an explicit path for a GMPLS tunnel defined in 1119 mplsTunnelTable and gmplsTunnelTable, when it is established 1120 using signaling. It does not insert new hops, but does define 1121 new values for hops defined in mplsTunnelHopTable. 1123 Each row in this table is indexed by the same indexes as 1124 mplsTunnelHopTable. It is acceptable for some rows in 1125 mplsTunnelHopTable to have corresponding entries in this table 1126 and some to have no corresponding entry in this table. 1128 The storage type for this entry is given by the value 1129 of mplsTunnelHopStorageType in the corresponding entry in the 1130 mplsTunnelHopTable. 1132 The row status of an entry in this table is controlled by 1133 mplsTunnelHopRowStatus in the corresponding entry in 1134 mplsTunnelHopTable. That is, it is not permitted to create a row 1135 in this table, nor to modify an existing row, when the 1136 corresponding mplsTunnelHopRowStatus has value active(1)." 1137 REFERENCE 1138 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1139 Management Information Base (MIB), RFC 3812. 1140 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 1141 " 1142 ::= { gmplsTeObjects 2 } 1143 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1145 gmplsTunnelHopEntry OBJECT-TYPE 1146 SYNTAX GmplsTunnelHopEntry 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "An entry in this table represents additions to a tunnel hop 1151 defined in mplsTunnelHopEntry. At an ingress to a tunnel an 1152 entry in this table is created by a network administrator for an 1153 ERLSP to be set up by a signaling protocol. At transit and 1154 egress nodes an entry in this table may be used to represent the 1155 explicit path instructions received using the signaling 1156 protocol." 1157 INDEX { 1158 mplsTunnelHopListIndex, 1159 mplsTunnelHopPathOptionIndex, 1160 mplsTunnelHopIndex 1161 } 1162 ::= { gmplsTunnelHopTable 1 } 1164 GmplsTunnelHopEntry ::= SEQUENCE { 1165 gmplsTunnelHopLabelStatuses BITS, 1166 gmplsTunnelHopExplicitForwardLabel Unsigned32, 1167 gmplsTunnelHopExplicitForwardLabelPtr RowPointer, 1168 gmplsTunnelHopExplicitReverseLabel Unsigned32, 1169 gmplsTunnelHopExplicitReverseLabelPtr RowPointer 1170 } 1172 gmplsTunnelHopLabelStatuses OBJECT-TYPE 1173 SYNTAX BITS { 1174 forwardPresent (0), 1175 reversePresent (1) 1176 } 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "This bitmask indicates the presence of labels indicated by the 1181 gmplsTunnelHopExplicitForwardLabel or 1182 gmplsTunnelHopExplicitForwardLabelPtr, and 1183 gmplsTunnelHopExplicitReverseLabel or 1184 gmplsTunnelHopExplicitReverseLabel objects. 1186 For the Present bits, a set bit indicates that a label is 1187 present for this hop in the route. This allows zero to be a 1188 valid label value." 1189 DEFVAL { { } } 1190 ::= { gmplsTunnelHopEntry 1 } 1191 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1193 gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE 1194 SYNTAX Unsigned32 1195 MAX-ACCESS read-create 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1243 row in another MIB table (such as the gmplsLabelTable of the 1244 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1245 in the reverse direction. 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1293 STATUS current 1294 DESCRIPTION 1295 "An entry in this table represents additions to a tunnel hop 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1344 For the Present bits, a set bit indicates that a label is 1345 present for this hop in the route. For the Global bits, a set 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1393 ::= { gmplsTunnelARHopEntry 4 } 1395 gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1443 mplsTunnelCHopTable 1444 of MPLS-TE-STD-MIB. It is used to indicate additional 1445 information about the hops of a GMPLS tunnel defined in 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1493 gmplsTunnelCHopLabelStatuses BITS, 1494 gmplsTunnelCHopExplicitForwardLabel Unsigned32, 1495 gmplsTunnelCHopExplicitForwardLabelPtr RowPointer, 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1543 forward label is present and this object contains the value 1544 zeroDotZero, then the label to use on this hop is found in the 1545 gmplsTunnelCHopExplicitForwardLabel object." 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1594 A tunnel can be known to be bidirectional by inspecting the 1595 gmplsTunnelDirection object." 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1643 DESCRIPTION 1644 "High capacity counter for number of packets forwarded on the 1645 tunnel in the reverse direction if it is bidirectional. 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1693 noSuchInstance." 1694 ::= { gmplsTunnelReversePerfEntry 5 } 1696 gmplsTunnelErrorTable OBJECT-TYPE 1697 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1698 MAX-ACCESS not-accessible 1699 STATUS current 1700 DESCRIPTION 1701 "This table augments the mplsTunnelTable 1702 This table provides per-tunnel information about errors. Errors 1703 may be detected locally or reported through the signaling 1704 protocol. Error reporting is not exclusive to GMPLS and this 1705 table may be applied in MPLS systems. 1707 Entries in this table are not persistent over system resets 1708 or re-initializations of the management system." 1709 REFERENCE 1710 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1711 Management Information Base (MIB), RFC 3812." 1712 ::= { gmplsTeObjects 6 } 1714 gmplsTunnelErrorEntry OBJECT-TYPE 1715 SYNTAX GmplsTunnelErrorEntry 1716 MAX-ACCESS not-accessible 1717 STATUS current 1718 DESCRIPTION 1719 "An entry in this table is created by the LSR for every tunnel 1720 where error information is visible to the LSR. 1722 Note that systems which read the objects in this table one 1723 at a time should read gmplsTunnelErrorLastTime prior to 1724 the first object and after reading the last object of this 1725 table to ensure that no additional errors occurred." 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1743 SYNTAX INTEGER { 1744 noError (0), 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 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1793 ::= { gmplsTunnelErrorEntry 2 } 1795 gmplsTunnelErrorReporterType OBJECT-TYPE 1796 SYNTAX InetAddressType 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The address type of the error reported. 1802 This object is used to aid in interpretation of 1803 gmplsTunnelErrorReporter." 1804 ::= { gmplsTunnelErrorEntry 3 } 1806 gmplsTunnelErrorReporter OBJECT-TYPE 1807 SYNTAX InetAddress 1808 MAX-ACCESS read-only 1809 STATUS current 1810 DESCRIPTION 1811 "The address of the node reporting the last error, or the address 1812 of the resource (such as an interface) associated with the 1813 error. 1815 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1816 this object is ignored. 1818 If gmplsTunnelErrorLastErrorType has the value unknown (1), 1819 localConfiguration (4), localResources (5), or localOther (6) 1820 this object MAY contain a zero value. 1822 This object should be interpreted in the context of the value of 1823 the object gmplsTunnelErrorReporterType." 1824 REFERENCE 1825 "1. Textual Conventions for Internet Network Addresses, RFC 4001, 1826 section 4, Usage Hints." 1827 ::= { gmplsTunnelErrorEntry 4 } 1829 gmplsTunnelErrorCode OBJECT-TYPE 1830 SYNTAX Unsigned32 1831 MAX-ACCESS read-only 1832 STATUS current 1833 DESCRIPTION 1834 "The primary error code associated with the last error. 1835 The interpretation of this error code depends on the value of 1836 gmplsTunnelErrorLastErrorType. If the value of 1837 gmplsTunnelErrorLastErrorType is noError (0) the value of this 1838 object should be 0 and should be ignored. If the value of 1839 gmplsTunnelErrorLastErrorType is protocol (2) the error should 1840 be interpreted in the context of the signling protocol 1841 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1843 identified by the mplsTunnelSignallingProto object." 1844 REFERENCE 1845 "1. Resource ReserVation Protocol -- Version 1 Functional 1846 Specification, RFC 2205, section B. 1847 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1848 section 7.3. 1849 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1850 section 13.1." 1851 ::= { gmplsTunnelErrorEntry 5 } 1853 gmplsTunnelErrorSubcode OBJECT-TYPE 1854 SYNTAX Unsigned32 1855 MAX-ACCESS read-only 1856 STATUS current 1857 DESCRIPTION 1858 "The secondary error code associated with the last error and the 1859 protocol used to signal this tunnel. This value is interpreted 1860 in the context of the value of gmplsTunnelErrorCode. 1861 If the value of gmplsTunnelErrorLastErrorType is noError (0) the 1862 value of this object should be 0 and should be ignored." 1863 REFERENCE 1864 "1. Resource ReserVation Protocol -- Version 1 Functional 1865 Specification, RFC 2205, section B. 1867 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1868 section 7.3. 1869 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1870 section 13.1. " 1871 ::= { gmplsTunnelErrorEntry 6 } 1873 gmplsTunnelErrorTLVs OBJECT-TYPE 1874 SYNTAX OCTET STRING (SIZE(0..65535)) 1875 MAX-ACCESS read-only 1876 STATUS current 1877 DESCRIPTION 1878 "The sequence of interface identifier TLVs reported with the 1879 error by the protocol code. The interpretation of the TLVs and 1880 the encoding within the protocol are described in the 1881 references. A value of zero in the first octet indicates that no 1882 TLVs are present." 1883 REFERENCE 1884 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1885 section 8.2." 1886 ::= { gmplsTunnelErrorEntry 7 } 1888 gmplsTunnelErrorHelpString OBJECT-TYPE 1889 SYNTAX SnmpAdminString 1890 MAX-ACCESS read-only 1891 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1893 STATUS current 1894 DESCRIPTION 1895 "A textual string containing information about the last error, 1896 recovery actions and support advice. If there is no help string 1897 this object contains a zero length string. 1898 If the value of gmplsTunnelErrorLastErrorType is noError (0) 1899 this object should contain a zero length string, but may contain 1900 a help string indicating that there is no error." 1901 ::= { gmplsTunnelErrorEntry 8 } 1903 -- 1904 -- Notifications 1905 -- 1907 gmplsTunnelDown NOTIFICATION-TYPE 1908 OBJECTS { 1909 mplsTunnelAdminStatus, 1910 mplsTunnelOperStatus, 1911 gmplsTunnelErrorLastErrorType, 1912 gmplsTunnelErrorReporterType, 1913 gmplsTunnelErrorReporter, 1914 gmplsTunnelErrorCode, 1915 gmplsTunnelErrorSubcode 1916 } 1917 STATUS current 1918 DESCRIPTION 1919 "This notification is generated when a mplsTunnelOperStatus 1920 object for a tunnel in the gmplsTunnelTable is about to enter 1921 the down state from some other state (but not from the 1922 notPresent state). This other state is indicated by the 1923 included value of mplsTunnelOperStatus. 1925 The objects in this notification provide additional error 1926 information that indicates the reason why the tunnel has 1927 transitioned down. 1929 Note that an implementation MUST only issue one of 1930 mplsTunnelDown and gmplsTunnelDown for any single event on a 1931 single tunnel. If the tunnel has an entry in gmplsTunnelTable 1932 an implementation SHOULD use gmplsTunnelDown for all tunnel 1933 down events and SHOULD NOT use mplsTunnelDown. 1935 This notification is subject to the control of the 1936 mplsTunnelNotificationEnable. When that object is set to 1937 false(2) then the notification must not be issued. 1939 Further, this notification is also subject to 1940 mplsTunnelNotificationMaxRate. That object indicates the 1941 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1943 maximum number of notifications issued per second. If events 1944 occur more rapidly, the implementation may simply fail to emit 1945 some notifications during that period, or may queue them until 1946 an appropriate time. The notification rate applies to the sum 1947 of all notificaitons in the MPLS-TE-STD-MIB and 1948 GMPLS-TE-STD-MIB modules applied across the whole of the 1949 reporting device. 1951 mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, 1952 mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate 1953 objects are found in MPLS-TE-STD-MIB." 1954 REFERENCE 1955 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering 1956 (TE) Management Information Base (MIB), RFC 3812." 1957 ::= { gmplsTeNotifications 1 } 1959 gmplsTeGroups 1960 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1962 gmplsTeCompliances 1963 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1965 -- Compliance requirement for fully compliant implementations. 1967 gmplsTeModuleFullCompliance MODULE-COMPLIANCE 1968 STATUS current 1969 DESCRIPTION 1970 "Compliance statement for agents that provide full support for 1971 GMPLS-TE-STD-MIB. Such devices can then be monitored and also 1972 be configured using this MIB module. 1974 The mandatory group has to be implemented by all LSRs that 1975 originate, terminate or act as transit for TE-LSPs/tunnels. 1976 In addition, depending on the type of tunnels supported, other 1977 groups become mandatory as explained below." 1979 MODULE MPLS-TE-STD-MIB -- The MPLS-TE-STD-MIB, RFC3812 1981 MANDATORY-GROUPS { 1982 mplsTunnelGroup, 1983 mplsTunnelScalarGroup 1984 } 1986 MODULE -- this module 1988 MANDATORY-GROUPS { 1989 gmplsTunnelGroup, 1990 gmplsTunnelScalarGroup 1991 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 1993 } 1995 GROUP gmplsTunnelSignaledGroup 1996 DESCRIPTION 1997 "This group is mandatory for devices which support signaled 1998 tunnel set up, in addition to gmplsTunnelGroup. The following 1999 constraints apply: 2000 mplsTunnelSignallingProto should be at least read-only 2001 returning a value of ldp(2), or rsvp(3)." 2003 GROUP gmplsTunnelOptionalGroup 2004 DESCRIPTION 2005 "Objects in this group are optional." 2007 GROUP gmplsTeNotificationGroup 2008 DESCRIPTION 2009 "This group is mandatory for those implementations which can 2010 implement the notifications contained in this group." 2012 ::= { gmplsTeCompliances 1 } 2014 -- Compliance requirement for read-only compliant implementations. 2016 gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 2017 STATUS current 2018 DESCRIPTION 2019 "Compliance requirement for implementations that only provide 2020 read-only support for GMPLS-TE-STD-MIB. Such devices can then be 2021 monitored but cannot be configured using this MIB module." 2023 MODULE -- this module 2025 -- The mandatory group has to be implemented by all LSRs that 2026 -- originate, terminate or act as transit for TE-LSPs/tunnels. 2027 -- In addition, depending on the type of tunnels supported, other 2028 -- groups become mandatory as explained below. 2030 MANDATORY-GROUPS { 2031 gmplsTunnelGroup, 2032 gmplsTunnelScalarGroup 2033 } 2035 GROUP gmplsTunnelSignaledGroup 2036 DESCRIPTION 2037 "This group is mandatory for devices which support signaled 2038 tunnel set up, in addition to gmplsTunnelGroup. The following 2039 constraints apply: 2040 mplsTunnelSignallingProto should be at least read-only 2042 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2044 returning a value of ldp(2), or rsvp(3)." 2046 GROUP gmplsTunnelOptionalGroup 2047 DESCRIPTION 2048 "Objects in this group are optional." 2050 GROUP gmplsTeNotificationGroup 2051 DESCRIPTION 2052 "This group is mandatory for those implementations which can 2053 implement the notifications contained in this group." 2055 OBJECT gmplsTunnelUnnumIf 2056 MIN-ACCESS read-only 2057 DESCRIPTION 2058 "Write access is not required." 2060 OBJECT gmplsTunnelAttributes 2061 MIN-ACCESS read-only 2062 DESCRIPTION 2063 "Write access is not required." 2065 OBJECT gmplsTunnelLSPEncoding 2066 MIN-ACCESS read-only 2067 DESCRIPTION 2068 "Write access is not required." 2070 OBJECT gmplsTunnelSwitchingType 2071 MIN-ACCESS read-only 2072 DESCRIPTION 2073 "Write access is not required." 2075 OBJECT gmplsTunnelLinkProtection 2076 MIN-ACCESS read-only 2077 DESCRIPTION 2078 "Write access is not required." 2080 OBJECT gmplsTunnelGPid 2081 MIN-ACCESS read-only 2082 DESCRIPTION 2083 "Write access is not required." 2085 OBJECT gmplsTunnelSecondary 2086 MIN-ACCESS read-only 2087 DESCRIPTION 2088 "Write access is not required." 2090 OBJECT gmplsTunnelDirection 2091 MIN-ACCESS read-only 2092 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2094 DESCRIPTION 2095 "Only forward (0) is required." 2097 OBJECT gmplsTunnelPathComp 2098 MIN-ACCESS read-only 2099 DESCRIPTION 2100 "Only explicit (2) is required." 2102 OBJECT gmplsTunnelUpstreamNotifyRecipientType 2103 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2104 MIN-ACCESS read-only 2105 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2106 is required." 2108 OBJECT gmplsTunnelUpstreamNotifyRecipient 2109 SYNTAX InetAddress (SIZE(0|4|16)) 2110 MIN-ACCESS read-only 2111 DESCRIPTION "An implementation is only required to support 2112 unknown(0), ipv4(1) and ipv6(2) sizes." 2114 OBJECT gmplsTunnelSendResvNotifyRecipientType 2115 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2116 MIN-ACCESS read-only 2117 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2118 is required." 2120 OBJECT gmplsTunnelSendResvNotifyRecipient 2121 SYNTAX InetAddress (SIZE(0|4|16)) 2122 MIN-ACCESS read-only 2123 DESCRIPTION "An implementation is only required to support 2124 unknown(0), ipv4(1) and ipv6(2) sizes." 2126 OBJECT gmplsTunnelDownstreamNotifyRecipientType 2127 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2128 MIN-ACCESS read-only 2129 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2130 is required." 2132 OBJECT gmplsTunnelDownstreamNotifyRecipient 2133 SYNTAX InetAddress (SIZE(0|4|16)) 2134 MIN-ACCESS read-only 2135 DESCRIPTION "An implementation is only required to support 2136 unknown(0), ipv4(1) and ipv6(2) sizes." 2138 OBJECT gmplsTunnelSendPathNotifyRecipientType 2139 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2140 MIN-ACCESS read-only 2141 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2142 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2144 is required." 2146 OBJECT gmplsTunnelSendPathNotifyRecipient 2147 SYNTAX InetAddress (SIZE(0|4|16)) 2148 MIN-ACCESS read-only 2149 DESCRIPTION "An implementation is only required to support 2150 unknown(0), ipv4(1) and ipv6(2) sizes." 2152 OBJECT gmplsTunnelAdminStatusFlags 2153 MIN-ACCESS read-only 2154 DESCRIPTION 2155 "Write access is not required." 2157 OBJECT gmplsTunnelExtraParamsPtr 2158 MIN-ACCESS read-only 2159 DESCRIPTION 2160 "Write access is not required." 2162 -- gmplsTunnelHopLabelStatuses has max access read-only 2164 OBJECT gmplsTunnelHopExplicitForwardLabel 2165 MIN-ACCESS read-only 2166 DESCRIPTION 2167 "Write access is not required." 2169 OBJECT gmplsTunnelHopExplicitForwardLabelPtr 2170 MIN-ACCESS read-only 2171 DESCRIPTION 2172 "Write access is not required." 2174 OBJECT gmplsTunnelHopExplicitReverseLabel 2175 MIN-ACCESS read-only 2176 DESCRIPTION 2177 "Write access is not required." 2179 OBJECT gmplsTunnelHopExplicitReverseLabelPtr 2180 MIN-ACCESS read-only 2181 DESCRIPTION 2182 "Write access is not required." 2184 -- gmplsTunnelARHopTable 2185 -- all objects have max access read-only 2187 -- gmplsTunnelCHopTable 2188 -- all objects have max access read-only 2190 -- gmplsTunnelReversePerfTable 2191 -- all objects have max access read-only 2192 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2194 -- gmplsTunnelErrorTable 2195 -- all objects have max access read-only 2197 OBJECT gmplsTunnelErrorReporterType 2198 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2199 DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support 2200 is required." 2202 OBJECT gmplsTunnelErrorReporter 2203 SYNTAX InetAddress (SIZE(0|4|16)) 2204 DESCRIPTION "An implementation is only required to support 2205 unknown(0), ipv4(1) and ipv6(2)." 2206 ::= { gmplsTeCompliances 2 } 2208 gmplsTunnelGroup OBJECT-GROUP 2209 OBJECTS { 2210 gmplsTunnelDirection, 2211 gmplsTunnelReversePerfPackets, 2212 gmplsTunnelReversePerfHCPackets, 2213 gmplsTunnelReversePerfErrors, 2214 gmplsTunnelReversePerfBytes, 2215 gmplsTunnelReversePerfHCBytes, 2216 gmplsTunnelErrorLastErrorType, 2217 gmplsTunnelErrorLastTime, 2218 gmplsTunnelErrorReporterType, 2219 gmplsTunnelErrorReporter, 2220 gmplsTunnelErrorCode, 2221 gmplsTunnelErrorSubcode, 2222 gmplsTunnelErrorTLVs, 2223 gmplsTunnelErrorHelpString, 2224 gmplsTunnelUnnumIf 2225 } 2226 STATUS current 2227 DESCRIPTION 2228 "Necessary, but not sufficient, set of objects to implement 2229 tunnels. In addition, depending on the type of the tunnels 2230 supported (for example, manually configured or signaled, 2231 persistent or non-persistent, etc.), the 2232 gmplsTunnelSignaledGroup group is mandatory." 2233 ::= { gmplsTeGroups 1 } 2235 gmplsTunnelSignaledGroup OBJECT-GROUP 2236 OBJECTS { 2237 gmplsTunnelAttributes, 2238 gmplsTunnelLSPEncoding, 2239 gmplsTunnelSwitchingType, 2240 gmplsTunnelLinkProtection, 2241 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2243 gmplsTunnelGPid, 2244 gmplsTunnelSecondary, 2245 gmplsTunnelPathComp, 2246 gmplsTunnelUpstreamNotifyRecipientType, 2247 gmplsTunnelUpstreamNotifyRecipient, 2248 gmplsTunnelSendResvNotifyRecipientType, 2249 gmplsTunnelSendResvNotifyRecipient, 2250 gmplsTunnelDownstreamNotifyRecipientType, 2251 gmplsTunnelDownstreamNotifyRecipient, 2252 gmplsTunnelSendPathNotifyRecipientType, 2253 gmplsTunnelSendPathNotifyRecipient, 2254 gmplsTunnelAdminStatusFlags, 2255 gmplsTunnelHopLabelStatuses, 2256 gmplsTunnelHopExplicitForwardLabel, 2257 gmplsTunnelHopExplicitForwardLabelPtr, 2258 gmplsTunnelHopExplicitReverseLabel, 2259 gmplsTunnelHopExplicitReverseLabelPtr 2260 } 2261 STATUS current 2262 DESCRIPTION 2263 "Objects needed to implement signaled tunnels." 2264 ::= { gmplsTeGroups 2 } 2266 gmplsTunnelScalarGroup OBJECT-GROUP 2267 OBJECTS { 2268 gmplsTunnelsConfigured, 2269 gmplsTunnelsActive 2270 } 2271 STATUS current 2272 DESCRIPTION 2273 "Scalar objects needed to implement MPLS tunnels." 2274 ::= { gmplsTeGroups 3 } 2276 gmplsTunnelOptionalGroup OBJECT-GROUP 2277 OBJECTS { 2278 gmplsTunnelExtraParamsPtr, 2279 gmplsTunnelARHopLabelStatuses, 2280 gmplsTunnelARHopExplicitForwardLabel, 2281 gmplsTunnelARHopExplicitForwardLabelPtr, 2282 gmplsTunnelARHopExplicitReverseLabel, 2283 gmplsTunnelARHopExplicitReverseLabelPtr, 2284 gmplsTunnelARHopProtection, 2285 gmplsTunnelCHopLabelStatuses, 2286 gmplsTunnelCHopExplicitForwardLabel, 2287 gmplsTunnelCHopExplicitForwardLabelPtr, 2288 gmplsTunnelCHopExplicitReverseLabel, 2289 gmplsTunnelCHopExplicitReverseLabelPtr 2290 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2292 } 2293 STATUS current 2294 DESCRIPTION 2295 "The objects in this group are optional." 2296 ::= { gmplsTeGroups 4 } 2298 gmplsTeNotificationGroup NOTIFICATION-GROUP 2299 NOTIFICATIONS { 2300 gmplsTunnelDown 2301 } 2302 STATUS current 2303 DESCRIPTION 2304 "Set of notifications implemented in this module. None is 2305 mandatory." 2306 ::= { gmplsTeGroups 5 } 2308 END 2310 9. Security Considerations 2312 It is clear that the MIB modules described in this document in 2313 association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful 2314 for monitoring of MPLS and GMPLS tunnels. These MIB modules can also 2315 be used for configuration of certain objects, and anything that can 2316 be configured can be incorrectly configured, with potentially 2317 disastrous results. 2319 There are a number of management objects defined in these MIB modules 2320 with a MAX-ACCESS clause of read-write and/or read-create. Such 2321 objects may be considered sensitive or vulnerable in some network 2322 environments. The support for SET operations in a non-secure 2323 environment without proper protection can have a negative effect on 2324 network operations. These are the tables and objects and their 2325 sensitivity/vulnerability: 2327 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 2328 objects to provision GMPLS tunnels interfaces at their ingress 2329 LSRs. Unauthorized write access to objects in these tables, could 2330 result in disruption of traffic on the network. This is especially 2331 true if a tunnel has already been established. 2333 Some of the readable objects in these MIB modules (i.e., objects with 2334 a MAX-ACCESS other than not-accessible) may be considered sensitive 2335 or vulnerable in some network environments. It is thus important to 2336 control even GET and/or NOTIFY access to these objects and possibly 2337 to even encrypt the values of these objects when sending them over 2338 the network via SNMP. These are the tables and objects and their 2339 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2341 sensitivity/vulnerability: 2343 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 2344 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and the 2345 gmplsTunnelErrorTable collectively show the tunnel network 2346 topology and status. If an Administrator does not want to reveal 2347 this information, then these tables should be considered 2348 sensitive/vulnerable. 2350 SNMP versions prior to SNMPv3 did not include adequate security. Even 2351 if the network itself is secure (for example by using IPSec), even 2352 then, there is no control as to who on the secure network is allowed 2353 to access and GET/SET (read/change/create/delete) the objects in 2354 these MIB modules. 2356 It is RECOMMENDED that implementers consider the security features as 2357 provided by the SNMPv3 framework (see [RFC3410], section 8), 2358 including full support for the SNMPv3 cryptographic mechanisms (for 2359 authentication and privacy). 2361 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2362 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2363 enable cryptographic security. It is then a customer/operator 2364 responsibility to ensure that the SNMP entity giving access to an 2365 instance of this MIB module, is properly configured to give access to 2366 the objects only to those principals (users) that have legitimate 2367 rights to indeed GET or SET (change/create/delete) them. 2369 10. Acknowledgments 2371 This document is a product of the CCAMP Working Group. 2373 This document extends [RFC3812]. The authors would like to express 2374 their gratitude to all those who worked on that earlier MIB document. 2375 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 2376 contributions during an early implementation, and to Baktha 2377 Muralidharan, Tom Petch, Dave Thaler and Bert Wijnen for their review 2378 comments. 2380 Special thanks to Joan Cucchiara and Len Nieman for their help with 2381 compilation issues. 2383 Joan Cucchiara provided a helpful and very thorough MIB Doctor 2384 review. 2386 11. IANA Considerations 2388 -- (Note to RFC-Editor:) 2389 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2391 -- We request that you assign contiguous RFC numbers to the three GMPLS 2392 -- MIB documents. 2393 -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to 2394 -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to 2395 -- draft-ietf-ccamp-gmpls-te-mib. 2396 -- (Please remove this note prior to publication.) 2398 IANA is requested to root MIB objects in the MIB module contained in 2399 this document under the mplsStdMIB subtree. 2400 In the future, GMPLS related standards track MIB modules should be 2401 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to 2402 manage that namespace in the SMI Numbers registry [RFC3811]. New 2403 assignments can only be made via a Standards Action as specified in 2404 [RFC2434]. 2406 11.1. IANA Considerations for GMPLS-TE-STD-MIB 2408 The IANA is requested to assign { mplsStdMIB XXX } to the 2409 GMPLS-TE-STD-MIB module specified in this document, and to record 2410 the assignment in the SMI Numbers registry. 2412 -- RFC Editor. Please replace XXX above with assigned OID and remove 2413 -- this note 2415 11.2. Dependence on IANA MIB Modules 2417 Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, 2418 gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual 2419 conventions imported from the IANA-GMPLS-TC-MIB. The purpose of 2420 defining these textual conventions in a separate MIB module is to 2421 allow additional values to be defined without having to issue a new 2422 version of this document. The Internet Assigned Numbers Authority 2423 (IANA) is responsible for the assignment of all Internet numbers; it 2424 will administer the values associated with these textual conventions. 2426 The rules for additions or changes to the IANA-GMPLS-TC-MIB are 2427 outlined in the DESCRIPTION clause associated with its 2428 MODULE-IDENTITY statement. 2430 The current versions of the IANA-GMPLS-TC-MIB can be accessed from 2431 the IANA home page at: "http://www.iana.org/". 2433 11.2.1. IANA-GMPLS-TC-MIB Definition 2435 This is a temporary section intended to supply the base definition of 2436 an IANA MIB module. The normal procedure is that this MIB module is 2437 moved into the direct control of IANA, at which time this section 2438 should be deleted from this document. 2440 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2442 IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module 2443 specified in this document as { transmission YYY }. 2445 -- RFC Editor. 2446 -- Please replace YYY above with assigned OID and remove this note. 2448 IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN 2450 IMPORTS 2451 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 2452 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 2454 ianaGmpls MODULE-IDENTITY 2455 LAST-UPDATED 2456 "200604060001Z" -- 06 April 2006 00:00:01 GMT 2457 ORGANIZATION 2458 "IANA" 2459 CONTACT-INFO 2460 " Internet Assigned Numbers Authority 2461 Postal: USC/Information Sciences Institute 2462 4676 Admiralty Way, Marina del Rey, CA 90292 2463 Tel: +1 310 822 1511 2464 E-Mail: iana@isi.edu" 2465 DESCRIPTION 2466 "Copyright (C) The Internet Society (2006). The initial version 2467 of this MIB module was published in RFC YYY. For full legal 2468 notices see the RFC itself. Supplementary information 2469 may be available on: 2470 http://www.ietf.org/copyrights/ianamib.html" 2471 -- RFC Editor. Please replace YYY above with the correct RFC number 2472 -- Your actions may vary depending on how IANA chooses to handle 2473 -- this IANA MIB. 2474 -- Please remove this note. 2476 REVISION 2477 "200604060001Z" -- 06 April 2006 00:00:01 GMT 2478 DESCRIPTION 2479 "Initial version issued as part of RFC YYY." 2480 ::= { transmission YYY } 2481 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 2482 -- Please remove this note. 2484 IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION 2485 STATUS current 2486 DESCRIPTION 2487 "This type is used to represent and control 2488 the LSP encoding type of an LSP signaled by a GMPLS 2490 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2492 signaling protocol. 2494 This textual convention is strongly tied to the LSP 2495 Encoding Types sub-registry of the GMPLS Signaling 2496 Parameters registry managed by IANA. Values should be 2497 assigned by IANA in step with the LSP Encoding Types 2498 sub-registry and using the same registry management rules. 2499 However, the actual values used in this textual convention 2500 are solely within the purview of IANA and do not 2501 necessarily match the values in the values in the LSP 2502 Encoding Types sub-registry. 2504 The definition of this textual convention with the 2505 addition of newly assigned values is published 2506 periodically by the IANA, in either the Assigned 2507 Numbers RFC, or some derivative of it specific to 2508 Internet Network Management number assignments. (The 2509 latest arrangements can be obtained by contacting the 2510 IANA.) 2512 Requests for new values should be made to IANA via 2513 email (iana@isi.edu)." 2514 REFERENCE 2515 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2516 Signaling Functional Description, RFC 3471, section 2517 3.1.1." 2518 -- RFC Editor. Please update this reference to the RFC before 2519 -- publication and remove this note 2520 SYNTAX INTEGER { 2521 tunnelLspNotGmpls (0), -- GMPLS is not in use 2522 tunnelLspPacket (1), -- Packet 2523 tunnelLspEthernet (2), -- Ethernet 2524 tunnelLspAnsiEtsiPdh (3), -- PDH 2525 -- the value 4 is deprecated 2526 tunnelLspSdhSonet (5), -- SDH or SONET 2527 -- the value 6 is deprecated 2528 tunnelLspDigitalWrapper (7), -- Digital Wrapper 2529 tunnelLspLambda (8), -- Lambda 2530 tunnelLspFiber (9), -- Fiber 2531 -- the value 10 is deprecated 2532 tunnelLspFiberChannel (11), -- Fiber Channel 2533 tunnelDigitalPath (12), -- Digital Path 2534 tunnelOpticalChannel (13) -- Optical Channel 2535 } 2537 IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION 2538 STATUS current 2539 DESCRIPTION 2540 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2542 "This type is used to represent and 2543 control the LSP switching type of an LSP signaled by a 2544 GMPLS signaling protocol. 2546 This textual convention is strongly tied to the Switching 2547 Types sub-registry of the GMPLS Signaling Parameters 2548 registry managed by IANA. Values should be assigned by IANA 2549 in step with the Switching Types sub-registry and using the 2550 same registry management rules. However, the actual values 2551 used in this textual convention are solely within the 2552 purview of IANA and do not necessarily match the values in 2553 the values in the Switching Types sub-registry. 2555 The definition of this textual convention with the 2556 addition of newly assigned values is published 2557 periodically by the IANA, in either the Assigned 2558 Numbers RFC, or some derivative of it specific to 2559 Internet Network Management number assignments. (The 2560 latest arrangements can be obtained by contacting the 2561 IANA.) 2563 Requests for new values should be made to IANA via 2564 email (iana@isi.edu)." 2565 REFERENCE 2566 "1. Routing Extensions in Support of Generalized 2567 Multi-Protocol Label Switching, RFC 4202, section 2.4. 2568 2. Generalized Multi-Protocol Label Switching (GMPLS) 2569 Signaling Functional Description, RFC 3471, section 2570 3.1.1." 2571 SYNTAX INTEGER { 2572 unknown (0), -- none of the following, or not known 2573 psc1 (1), -- Packet-Switch-Capable 1 2574 psc2 (2), -- Packet-Switch-Capable 2 2575 psc3 (3), -- Packet-Switch-Capable 3 2576 psc4 (4), -- Packet-Switch-Capable 4 2577 l2sc (51), -- Layer-2-Switch-Capable 2578 tdm (100), -- Time-Division-Multiplex 2579 lsc (150), -- Lambda-Switch-Capable 2580 fsc (200) -- Fiber-Switch-Capable 2581 } 2583 IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION 2584 STATUS current 2585 DESCRIPTION 2586 "This data type is used to represent and control the LSP 2587 Generalized Protocol Identifier (G-PID) of an LSP 2588 signaled by a GMPLS signaling protocol. 2590 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2592 This textual convention is strongly tied to the Generalized 2593 PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters 2594 registry managed by IANA. Values should be assigned by IANA 2595 in step with the Generalized PIDs (G-PID) sub-registry and 2596 using the same registry management rules. However, the 2597 actual values used in this textual convention are solely 2598 within the purview of IANA and do not necessarily match the 2599 values in the values in the Generalized PIDs (G-PID) 2600 sub-registry. 2602 The definition of this textual convention with the 2603 addition of newly assigned values is published 2604 periodically by the IANA, in either the Assigned 2605 Numbers RFC, or some derivative of it specific to 2606 Internet Network Management number assignments. (The 2607 latest arrangements can be obtained by contacting the 2608 IANA.) 2610 Requests for new values should be made to IANA via 2611 email (iana@isi.edu)." 2612 REFERENCE 2613 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2614 Signaling Functional Description, RFC 3471, section 2615 3.1.1. 2616 " 2617 -- RFC Editor. Please update this reference to the RFC before 2618 -- publication and remove this note 2619 SYNTAX INTEGER { 2620 unknown(0), -- unknown or none of the following 2621 -- the values 1, 2, 3 and 4 are reserved in RFC 3471 2622 asynchE4(5), 2623 asynchDS3T3(6), 2624 asynchE3(7), 2625 bitsynchE3(8), 2626 bytesynchE3(9), 2627 asynchDS2T2(10), 2628 bitsynchDS2T2(11), 2629 reservedByRFC3471first(12), 2630 asynchE1(13), 2631 bytesynchE1(14), 2632 bytesynch31ByDS0(15), 2633 asynchDS1T1(16), 2634 bitsynchDS1T1(17), 2635 bytesynchDS1T1(18), 2636 vc1vc12(19), 2637 reservedByRFC3471second(20), 2638 reservedByRFC3471third(21), 2639 ds1SFAsynch(22), 2641 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2643 ds1ESFAsynch(23), 2644 ds3M23Asynch(24), 2645 ds3CBitParityAsynch(25), 2646 vtLovc(26), 2647 stsSpeHovc(27), 2648 posNoScramble16BitCrc(28), 2649 posNoScramble32BitCrc(29), 2650 posScramble16BitCrc(30), 2651 posScramble32BitCrc(31), 2652 atm(32), 2653 ethernet(33), 2654 sdhSonet(34), 2655 digitalwrapper(36), 2656 lambda(37), 2657 ansiEtsiPdh (38), 2658 lapsSdh (40), 2659 fddi (41), 2660 dqdb (42), 2661 fiberChannel3 (43), 2662 hdlc (44), 2663 ethernetV2DixOnly (45), 2664 ethernet802dot3Only (46), 2665 g709ODUj (47), 2666 g709OTUk (48), 2667 g709CBRorCBRa (49), 2668 g709CBRb (50), 2669 g709BSOT (51), 2670 g709BSNT (52), 2671 gfpIPorPPP (53), 2672 gfpEthernetMAC (54), 2673 gfpEthernetPHY (55), 2674 g709ESCON (56), 2675 g709FICON (57), 2676 g709FiberChannel (58) 2677 } 2679 IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION 2680 STATUS current 2681 DESCRIPTION 2682 "This data type determines the setting of the 2683 Admin Status flags in the Admin Status object or TLV, as 2684 described in RFC 3471. Setting this object to a non-zero 2685 value will result in the inclusion of the Admin Status 2686 object or TLV on signaling messages. 2688 This textual convention is strongly tied to the Admin 2689 Status Flags sub-registry of the GMPLS Signaling Parameters 2690 registry managed by IANA. Values should be assigned by IANA 2692 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2694 in step with the Admin Status Flags sub-registry and using 2695 the same registry management rules. However, the actual 2696 values used in this textual convention are solely within 2697 the purview of IANA and do not necessarily match the values 2698 in the values in the Admin Status Flags sub-registry. 2699 -- RFC Editor / IANA note 2700 -- At the time of writing, the referenced Admin Status Flags 2701 -- sub-registry has not been created. 2702 -- It is not requested in RFC 3471 (the base reference for this protocol 2703 -- element). But it is requested in two I-Ds that are ahead of this MIB 2704 -- module in the IETF process 2705 -- draft-ietf-ccamp-gmpls-recovery-e2e-signaling 2706 -- draft-ietf-ccamp-gmpls-alarm-spec 2707 -- Note, however, that at this stage no request is made to IANA for the 2708 -- definition of values in the textual convention to match any of the 2709 -- Admin Status bits except those defined in RFC 3471. IANA is free to 2710 -- define additional values but these will not be used by this MIB 2711 -- module (although future MIB modules will doubtless use them). 2712 -- 2713 -- RFC Editor. Please update the previous paragraph to use the correct 2714 -- name for the new sub-registry as defined by IANA, and delete this 2715 -- note. 2717 The definition of this textual convention with the 2718 addition of newly assigned values is published 2719 periodically by the IANA, in either the Assigned 2720 Numbers RFC, or some derivative of it specific to 2721 Internet Network Management number assignments. (The 2722 latest arrangements can be obtained by contacting the 2723 IANA.) 2725 Requests for new values should be made to IANA via 2726 email (iana@isi.edu)." 2728 REFERENCE 2729 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2730 Signaling Functional Description, RFC 3471, section 8." 2731 SYNTAX BITS { 2732 reflect (0), -- Reflect bit (RFC 3471) 2733 reserved1 (1), -- reserved 2734 reserved2 (2), -- reserved 2735 reserved3 (3), -- reserved 2736 reserved4 (4), -- reserved 2737 reserved5 (5), -- reserved 2738 reserved6 (6), -- reserved 2739 reserved7 (7), -- reserved 2740 reserved8 (8), -- reserved 2741 reserved9 (9), -- reserved 2743 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2745 reserved10 (10), -- reserved 2746 reserved11 (11), -- reserved 2747 reserved12 (12), -- reserved 2748 reserved13 (13), -- reserved 2749 reserved14 (14), -- reserved 2750 reserved15 (15), -- reserved 2751 reserved16 (16), -- reserved 2752 reserved17 (17), -- reserved 2753 reserved18 (18), -- reserved 2754 reserved19 (19), -- reserved 2755 reserved20 (20), -- reserved 2756 reserved21 (21), -- reserved 2757 reserved22 (22), -- reserved 2758 reserved23 (23), -- reserved 2759 reserved24 (24), -- reserved 2760 reserved25 (25), -- reserved 2761 reserved26 (26), -- reserved 2762 reserved27 (27), -- reserved 2763 reserved28 (28), -- reserved 2764 testing (29), -- Testing bit (RFC 3473) 2765 administrativelyDown (30), -- Admin down (RFC 3473) 2766 deleteInProgress (31) -- Delete bit (RFC 3473) 2767 } 2769 END 2771 12. References 2773 12.1. Normative References 2775 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2776 Requirements Levels", BCP 14, RFC 2119, March 1997. 2778 [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. 2779 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 2780 1 Functional Specification", RFC 2205, September 1997. 2782 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2783 J., Rose, M., and S. Waldbusser, "Structure of 2784 Management Information Version 2 (SMIv2)", STD 58, RFC 2785 2578, April 1999. 2787 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2788 J., Rose, M., and S. Waldbusser, "Textual Conventions 2789 for SMIv2", STD 58, RFC 2579, April 1999. 2791 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2793 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2794 J., Rose, M., and S. Waldbusser, "Conformance Statements 2795 for SMIv2", STD 58, RFC 2580, April 1999. 2797 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2798 "Multiprotocol Label Switching Architecture", RFC 3031, 2799 January 2001. 2801 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 2802 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 2803 Tunnels", RFC 3209, December 2001. 2805 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2806 Architecture for Describing Simple Network Management 2807 Protocol (SNMP) Management Frameworks", STD 62, RFC 2808 3411, December 2002. 2810 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 2811 (GMPLS) Signaling Functional Description", RFC 3471, 2812 January 2003. 2814 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 2815 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 2816 Engineering (RSVP-TE) Extensions", RFC 3473, January 2817 2003. 2819 [RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered 2820 Links in Resource ReSerVation Protocol - Traffic 2821 Engineering (RSVP-TE)", RFC 3477, January 2003. 2823 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 2824 Conventions and for Multiprotocol Label Switching (MPLS) 2825 Management", RFC 3811, June 2004. 2827 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2828 "Multiprotocol Label Switching (MPLS) Traffic 2829 Engineering (TE) Management Information Base (MIB)", 2830 RFC 3812, June 2004. 2832 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2833 "Multiprotocol Label Switching (MPLS) Label Switching 2834 (LSR) Router Management Information Base (MIB)", RFC 2835 3813, June 2004. 2837 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 2838 Switching (GMPLS) Architecture", RFC 3945, October 2004. 2840 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2842 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2844 Schoenwaelder, "Textual Conventions for Internet Network 2845 Addresses", RFC 4001, February 2005. 2847 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in 2848 Support of Generalized Multi-Protocol Label Switching", 2849 RFC 4202, October 2005. 2851 [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 2852 Label Switching (GMPLS) Label Switching Router (LSR) 2853 Management Information Base", 2854 draft-ietf-ccamp-gmpls-lsr-mib, work in progress. 2856 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 2857 Conventions for Multiprotocol Label Switching (MPLS) 2858 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 2859 progress. 2861 12.2. Informative References 2863 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2864 MIB", RFC 2863, June 2000. 2866 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2867 "Introduction and Applicability Statements for 2868 Internet-Standard Management Framework", RFC 3410, 2869 December 2002. 2871 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 2872 Multi-Protocol Label Switching (MPLS) Signaling 2873 - Constraint-based Routed Label Distribution Protocol 2874 (CR-LDP) Extensions", RFC 3472, January 2003. 2876 13. Contact Information 2878 Thomas D. Nadeau 2879 Cisco Systems, Inc. 2880 1414 Massachusetts Ave. 2881 Boxborough, MA 01719 2882 Email: tnadeau@cisco.com 2884 Cheenu Srinivasan 2885 Bloomberg L.P. 2886 731 Lexington Ave. 2887 New York, NY 10022 2888 Phone: +1-212-617-3682 2889 Email: cheenu@bloomberg.net 2891 Adrian Farrel 2892 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2894 Old Dog Consulting 2895 Phone: +44-(0)-1978-860944 2896 Email: adrian@olddog.co.uk 2898 Tim Hall 2899 Data Connection Ltd. 2900 100 Church Street 2901 Enfield, Middlesex 2902 EN2 6BQ, UK 2903 Phone: +44 20 8366 1177 2904 Email: tim.hall@dataconnection.com 2906 Ed Harrison 2907 Data Connection Ltd. 2908 100 Church Street 2909 Enfield, Middlesex 2910 EN2 6BQ, UK 2911 Phone: +44 20 8366 1177 2912 Email: ed.harrison@dataconnection.com 2914 14. Intellectual Property Considerations 2916 The IETF takes no position regarding the validity or scope of any 2917 Intellectual Property Rights or other rights that might be claimed to 2918 pertain to the implementation or use of the technology described in 2919 this document or the extent to which any license under such rights 2920 might or might not be available; nor does it represent that it has 2921 made any independent effort to identify any such rights. Information 2922 on the procedures with respect to rights in RFC documents can be 2923 found in BCP 78 and BCP 79. 2925 Copies of IPR disclosures made to the IETF Secretariat and any 2926 assurances of licenses to be made available, or the result of an 2927 attempt made to obtain a general license or permission for the use of 2928 such proprietary rights by implementers or users of this 2929 specification can be obtained from the IETF on-line IPR repository at 2930 http://www.ietf.org/ipr. 2932 The IETF invites any interested party to bring to its attention any 2933 copyrights, patents or patent applications, or other proprietary 2934 rights that may cover technology that may be required to implement 2935 this standard. Please address the information to the IETF at 2936 ietf-ipr@ietf.org. 2938 draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 2940 15. Full Copyright Statement 2942 Copyright (C) The Internet Society (2006). This document is subject 2943 to the rights, licenses and restrictions contained in BCP 78, and 2944 except as set forth therein, the authors retain all their rights. 2946 This document and the information contained herein are provided on an 2947 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2948 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2949 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2950 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2951 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2952 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.