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