idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-05.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 3667, Section 5.1 on line 2312. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2326. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2292. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2299. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2305. ** The document claims conformance with section 10 of RFC 2026, but uses some RFC 3978/3979 boilerplate. As RFC 3978/3979 replaces section 10 of RFC 2026, you should not claim conformance with it if you have changed to using RFC 3978/3979 boilerplate. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 42 longer pages, the longest (page 28) being 72 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 43 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) == There are 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. 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. -- 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 (June 2004) is 7247 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3209' is defined on line 2147, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 2152, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 2160, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 2165, but no explicit reference was found in the text == Unused Reference: 'RFC3477' is defined on line 2176, but no explicit reference was found in the text == Unused Reference: 'RFC3480' is defined on line 2179, but no explicit reference was found in the text == Unused Reference: 'GMPLSOSPF' is defined on line 2195, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 2225, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 2228, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 2236, but no explicit reference was found in the text == Unused Reference: 'GMPLS-G709' is defined on line 2241, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Unexpected draft version: The latest known version of draft-many-gmpls-architecture is -00, but you're referring to -07. -- Possible downref: Normative reference to a draft: ref. 'GMPLSArch' == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-lsr-mib-05 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-05 == Outdated reference: A later version (-09) exists of draft-ietf-ccamp-gmpls-g709-06 Summary: 8 errors (**), 0 flaws (~~), 20 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group Thomas D. Nadeau 3 Internet Draft Cisco Systems, Inc. 4 Proposed Status: Standards Track 5 Expires: December 2004 Cheenu Srinivasan 6 Bloomberg L.P. 8 Adrian Farrel 9 Old Dog Consulting 11 Tim Hall 12 Ed Harrison 13 Data Connection Ltd. 15 June 2004 17 Generalized Multiprotocol Label Switching (GMPLS) Traffic 18 Engineering Management Information Base 20 draft-ietf-ccamp-gmpls-te-mib-05.txt 22 Status of this Memo 24 This document is an Internet-Draft and is in full conformance with 25 all provisions of Section 10 of RFC2026. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 Abstract 45 This memo defines an experimental portion of the Management 46 Information Base (MIB) for use with network management protocols in 47 the Internet community. In particular, it describes managed objects 48 for Generalized Multiprotocol Label Switching (GMPLS) based traffic 49 engineering. 51 Table of Contents 53 1. Introduction 2 54 1.1. Migration Strategy 3 55 2. Terminology 3 56 3. The SNMP Management Framework 3 57 4. Outline 4 58 4.1. Summary of GMPLS Traffic Engineering MIB Module 4 59 5. Brief Description of GMPLS TE MIB Objects 4 60 5.1. gmplsTunnelTable 4 61 5.2. gmplsTunnelHopTable 5 62 5.3. gmplsTunnelARHopTable 5 63 5.4. gmplsTunnelCHopTable 5 64 5.5. gmplsTunnelErrorTable 5 65 5.6. gmplsTunnelReversePerfTable 5 66 6. Cross-referencing to the mplsLabelTable 5 67 7. Example of GMPLS Tunnel Setup 6 68 8. GMPLS Traffic Engineering MIB Definitions 9 69 9. Security Considerations 37 70 10. Acknowledgments 38 71 11. References 39 72 11.1. Normative Refenerces 39 73 11.2. Informational References 40 74 12. Authors' Addresses 41 75 13. Full Copyright Statement 41 76 14. Intellectual Property Notice 42 78 1. Introduction 80 This memo defines a portion of the Management Information Base (MIB) 81 for use with network management protocols in the Internet community. 82 In particular, it describes managed objects for modeling a 83 Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] based 84 traffic engineering. The tables and objects defined in this document 85 extend those defined in the equivalent document for MPLS traffic 86 engineering [TEMIB], and management of GMPLS traffic engineering is 87 built on management of MPLS traffic engineering. 89 This MIB module should be used in conjunction with the companion 90 document [GMPLSLSRMIB] for GMPLS based traffic engineering 91 configuration and management. 93 Comments should be made direct to the CCAMP mailing list at 94 ccamp@ops.ietf.org. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119, reference 99 [RFC2119]. 101 1.1. Migration Strategy 103 This MIB module extends the traffic engineering MIB module defined 104 for use with MPLS [TEMIB]. It provides additions for support of GMPLS 105 tunnels. 107 The companion document for modeling and managing GMPLS based LSRs 108 [GMPLSLSRMIB] extends MPLS LSR MIB [LSRMIB] with the same intentions. 110 Textual conventions and OBJECT-IDENTIFIERS are defined in [TCMIB] and 111 [GMPLSTCMIB]. 113 2. Terminology 115 This document uses terminology from the MPLS architecture document 116 [RFC3031], from the GMPLS architecture document [GMPLSArch], and from 117 the MPLS Traffic Engineering MIB [TEMIB]. Some frequently used terms 118 are described next. 120 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 121 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 122 LSRs, each segment being associated with one GMPLS enabled interface. 123 These are also referred to as tunnel segments. 125 Additionally, at an intermediate LSR, we model a connection as 126 consisting of one or more in-segments and/or one or more out- 127 segments. The binding or interconnection between in-segments and out- 128 segments in performed using a cross-connect. 130 These segment and cross-connect objects are defined in the MPLS Label 131 Switch Router MIB [LSRMIB], but see also the GMPLS Label Switch 132 Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these 133 objects. 135 3. The SNMP Management Framework 137 For a detailed overview of the documents that describe the current 138 Internet-Standard Management Framework, please refer to section 7 of 139 RFC 3410 [RFC3410]. 141 Managed objects are accessed via a virtual information store, termed 142 the Management Information Base or MIB. MIB objects are generally 143 accessed through the Simple Network Management Protocol (SNMP). 144 Objects in the MIB are defined using the mechanisms defined in the 145 Structure of Management Information (SMI). This memo specifies a 146 MIB module that is compliant to the SMIv2, which is described in STD 147 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 148 2580 [RFC2580]. 150 4. Outline 152 Support for GMPLS traffic-engineered tunnels requires the following 153 configuration. 155 - Setting up tunnels with appropriate MPLS configuration parameters 156 using [TEMIB]. 157 - Extending the tunnels with GMPLS configuration parameters. 158 - Configuring tunnel loose and strict source routed hops. 160 These actions may need to be accompanied with corresponding actions 161 using [LSRMIB] and [GMPLSLSRMIB] to establish and configure tunnel 162 segments, if this is done manually. Also, the in-segment and out- 163 segment performance tables, mplsInSegmentPerfTable and 164 mplsOutSegmentPerfTable [LSRMIB], should be used to determine 165 performance of the tunnels and tunnel segments although it should be 166 noted that those tables may not be appropriate for measuring 167 performance on some types of GMPLS links. 169 4.1. Summary of GMPLS Traffic Engineering MIB Module 171 The MIB objects for performing the actions listed above that cannot 172 be performed solely using the MIB objects defined in [TEMIB] consist 173 of the following tables. 175 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 176 tunnel configuration parameters. 177 - Tunnel specified, actual, and computed hop tables 178 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 179 gmplsTunnelCHopTable) for providing additional configuration of 180 strict and loose source routed tunnel hops. 181 - Performance and error reporting tables (gmplsTunnelReversePerfTable 182 and gmplsTunnelErrorTable). 184 These tables are described in the subsequent sections. 186 Additionally, this MIB module contains a new Notification. 188 - The GMPLS Tunnel Down Notification (gmplsTunnelDown) is intended to 189 be used in place of the mplsTunnelDown Notification defined in 190 [TEMIB]. As well as indicating that a tunnel has transitioned to 191 operational down state, this new Notificaiton indicates the cause 192 of the failure. 194 5. Brief Description of GMPLS TE MIB Objects 196 The objects described in this section support the functionality 197 described in [RFC3473] and [RFC3472] for GMPLS tunnels. 198 The tables support both manually configured and signaled tunnels. 200 5.1. gmplsTunnelTable 202 The gmplsTunnelTable extends the MPLS traffic engineering MIB to 203 allow GMPLS tunnels to be created between an LSR and a remote 204 endpoint, and existing GMPLS tunnels to be reconfigured or removed. 206 Note that we only support point-to-point tunnel segments, although 207 multi-point-to-point and point-to-multi-point connections are 208 supported by an LSR acting as a cross-connect. 210 Each tunnel can thus have one out-segment originating at an LSR 211 and/or one in-segment terminating at that LSR. 213 5.2. gmplsTunnelHopTable 215 The gmplsTunnelHopTable is used to indicate additional parameters for 216 the hops, strict or loose, of a GMPLS tunnel defined in 217 gmplsTunnelTable, when it is established using signaling. Multiple 218 tunnels may share the same hops by pointing to the same entry in this 219 table. 221 5.3. gmplsTunnelARHopTable 223 The gmplsTunnelARHopTable is used to indicate the actual hops 224 traversed by a tunnel as reported by the signaling protocol after the 225 tunnel is setup. The support of this table is optional since not all 226 GMPLS signaling protocols support this feature. 228 5.4. gmplsTunnelCHoptable 230 The gmplsTunnelCHopTable lists the actual hops computed by a 231 constraint-based routing algorithm based on the gmplsTunnelHopTable. 232 The support of this table is optional since not all implementations 233 support computation of hop lists using a constraint-based routing 234 protocol. 236 5.5. gmplsTunnelErrorTable 238 The gmplsTunnelErrorTable provides access to information about the 239 last error that occurred on each tunnel known about by the MIB. It 240 indicates the nature of the error, when and how it was reported and 241 can give recovery advice through a display string. 243 5.6. gmplsTunnelReversePerfTable 245 gmplsTunnelReversePerfTable provides additional counters to measure 246 the performance of bidirectional GMPLS tunnels in which packets are 247 visible. It supplements the counters in mplsTunnelPerfTable and 248 augments gmplsTunnelTable. 250 Note that not all counters may be appropriate or available for some 251 types of tunnel. 253 6. Cross-referencing to the gmplsLabelTable 255 The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and 256 provides a way to model labels in a GMPLS system where labels might 257 not be simple 32 bit integers. 259 The hop tables in this document (gmplsHopTable, gmplsCHopTable and 260 gmplsARHopTable) and the segment tables in the [LSRMIB] 261 (mplsInSegmentTable and mplsOutSegmentTable) contain objects with 262 syntax MplsLabel. 264 MplsLabel (defined in [TCMIB]) is a 32-bit integer that is capable of 265 representing any MPLS label and most GMPLS labels. However, some 266 GMPLS labels are larger than 32 bits and may be of arbitrary length. 267 Further, some labels that may be safely encoded in 32 bits are 268 constructed from multiple sub-fields. Additionally, some GMPLS 269 technologies support the concatenation of individual labels to 270 represent a data flow carried as multiple sub-flows. 272 These GMPLS cases require that something other than a simple 32-bit 273 integer is made available to represent the labels. This is achieved 274 through the gmplsLabelTable contained in [GMPLSLSRMIB]. 276 The tables in this document and [LSRMIB] that include objects with 277 syntax MplsLabel also include companion objects that are row 278 pointers. If the row pointer is set to zeroDotZero (0.0) then object 279 of syntax MplsLabel contains the label encoded as a 32-bit integer. 280 But otherwise the row pointer indicates a row in another MIB table 281 that includes the label. In these cases, the row pointer may indicate 282 a row in the gmplsLabelTable. 284 This provides both a good way to support legacy systems that 285 implement the previous version of this MIB [TEMIB], and a significant 286 simplification in GMPLS systems that are limited to a single, simple 287 label type. 289 Note that gmplsLabelTable supports concatenated labels through the 290 use of a label sub-index (gmplsLabelSubindex). 292 7. Example of GMPLS Tunnel Setup 294 This section contains an example of which MIB objects should be 295 modified to create a GMPLS tunnel. This example shows a best effort, 296 loosely routed, bidirectional traffic engineered tunnel, which spans 297 two hops of a simple network, uses Generalized Label requests with 298 Lambda encoding, has label recording and shared link layer 299 protection. Note that these objects should be created on the "head- 300 end" LSR. 302 First in the mplsTunnelTable: 303 { 304 mplsTunnelIndex = 1, 305 mplsTunnelInstance = 1, 306 mplsTunnelIngressLSRId = 123.123.125.1, 307 mplsTunnelEgressLSRId = 123.123.126.1, 308 mplsTunnelName = "My first tunnel", 309 mplsTunnelDescr = "Here to there and back again", 310 mplsTunnelIsIf = true (1), 311 mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, 312 mplsTunnelSignallingProto = none (1), 313 mplsTunnelSetupPrio = 0, 314 mplsTunnelHoldingPrio = 0, 315 mplsTunnelSessionAttributes = recordRoute (4), 316 mplsTunnelOwner = snmp (2), 317 mplsTunnelLocalProtectInUse = false (0), 318 mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, 319 mplsTunnelInstancePriority = 1, 320 mplsTunnelHopTableIndex = 1, 321 mplsTunnelPrimaryInstance = 0, 322 mplsTunnelIncludeAnyAffinity = 0, 323 mplsTunnelIncludeAllAffinity = 0, 324 mplsTunnelExcludeAnyAffinity = 0, 325 mplsTunnelPathInUse = 1, 326 mplsTunnelRole = head(1), 327 mplsTunnelRowStatus = createAndWait (5), 328 } 330 In gmplsTunnelTable(1,1,123.123.125.1,123.123.126.1): 331 { 332 gmplsTunnelUnnumIf = true (1), 333 gmplsTunnelAttributes = labelRecordingRequired (1), 334 gmplsTunnelLSPEncoding = tunnelLspLambda (8), 335 gmplsTunnelSwitchingType = lsc (150), 336 gmplsTunnelLinkProtection = shared (2), 337 gmplsTunnelGPid = lambda (37), 338 gmplsTunnelSecondary = false(0), 339 gmplsTunnelDirection = bidirectional (1) 340 gmplsTunnelPathComp = explicit(2), 341 gmplsTunnelUpNotRecip = 0x7B7B7D01, 342 gmplsTunnelDownNotRecip = 0x00000000, 343 gmplsTunnelAdminStatusFlags = 0, 344 gmplsTunnelExtraParamsPtr = 0.0 345 } 347 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 348 gmplsTunnelHopTable are created and activated at this time. 350 In mplsTunnelResourceTable: 351 { 352 mplsTunnelResourceIndex = 6, 353 mplsTunnelResourceMaxRate = 0, 354 mplsTunnelResourceMeanRate = 0, 355 mplsTunnelResourceMaxBurstSize = 0, 356 mplsTunnelResourceRowStatus = createAndGo (4) 357 } 359 The next two instances of mplsTunnelHopEntry are used to denote the 360 hops this tunnel will take across the network. 362 The following denotes the beginning of the network, or the first hop. 363 We have used the fictitious LSR identified by "123.123.125.1" as our 364 example head-end router. 366 In mplsTunnelHopTable: 367 { 368 mplsTunnelHopListIndex = 1, 369 mplsTunnelPathOptionIndex = 1, 370 mplsTunnelHopIndex = 1, 371 mplsTunnelHopAddrType = ipV4 (1), 372 mplsTunnelHopIpv4Addr = 123.123.125.1, 373 mplsTunnelHopIpv4PrefixLen = 9, 374 mplsTunnelHopType = strict (1), 375 mplsTunnelHopRowStatus = createAndWait (5), 376 } 377 The following denotes the end of the network, or the last hop in our 378 example. We have used the fictitious LSR identified by 379 "123.123.126.1" as our end router. 381 In mplsTunnelHopTable: 382 { 383 mplsTunnelHopListIndex = 1, 384 mplsTunnelPathOptionIndex = 1, 385 mplsTunnelHopIndex = 2, 386 mplsTunnelHopAddrType = ipV4 (1), 387 mplsTunnelHopIpv4Addr = 123.123.126.1, 388 mplsTunnelHopIpv4PrefixLen = 9, 389 mplsTunnelHopType = loose (2), 390 mplsTunnelHopRowStatus = createAndGo (4) 391 } 393 Now an associated entry in the gmplsTunnelHopTable is created to 394 provide additional GMPLS hop configuration indicating that the first 395 hop is an unnumbered link using explicit forward and reverse labels. 396 An entry in the gmplsLabelTable is created first to include the 397 explicit label. 399 In gmplsLabelTable: 400 { 401 gmplsLabelInterface = 2, 402 gmplsLabelIndex = 1, 403 gmplsLabelSubindex = 0, 404 gmplsLabelType = = 405 gmplsFreeformGeneralizedLabel(3), 406 gmplsLabelFreeform = 0xFEDCBA9876543210 407 gmplsLabelRowStatus = createAndGo(4) 408 } 410 In gmplsTunnelHopTable(1,1,1): 411 { 412 gmplsTunnelHopLabelStatuses = forwardPresent(0) 413 +reversePresent(1), 414 gmplsTunnelHopExpLabelPtr = gmplsLabelTable (2, 1, 0) 415 gmplsTunnelHopExpRvrsLabelPtr = gmplsLabelTable (2, 1, 0) 416 } 418 The first hop is now activated: 420 In mplsTunnelHopTable(1,1,1): 421 { 422 mplsTunnelHopRowStatus = active (1) 423 } 425 No gmplsTunnelHopEntry is created for the second hop as it contains 426 no special GMPLS features. 428 Finally the mplsTunnelEntry is activated: 430 In mplsTunnelTable(1,1,123.123.125.1,123.123.126.1) 431 { 432 mplsTunnelRowStatus = active(1) 433 } 435 8. GMPLS Traffic Engineering MIB Definitions 437 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 439 IMPORTS 440 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 441 Integer32, Unsigned32, Counter32, 442 Counter64, IpAddress, zeroDotZero 443 FROM SNMPv2-SMI 444 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 445 FROM SNMPv2-CONF 446 TruthValue, TimeStamp, DisplayString, RowPointer 447 FROM SNMPv2-TC 448 InetAddress 449 FROM INET-ADDRESS-MIB 450 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 451 mplsTunnelEgressLSRId, mplsTunnelHopListIndex, 452 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, 453 mplsTunnelARHopListIndex, mplsTunnelARHopIndex, 454 mplsTunnelCHopListIndex, mplsTunnelCHopIndex, 455 mplsTunnelEntry, mplsTunnelSignallingProto, 456 mplsTunnelAdminStatus, mplsTunnelOperStatus 457 FROM MPLS-TE-STD-MIB 458 gmplsStdMIB 459 FROM GMPLS-TC-STD-MIB 460 ; 462 gmplsTeStdMIB MODULE-IDENTITY 463 LAST-UPDATED 464 "200406010900Z" -- 1 June 2004 9:00:00 GMT 465 ORGANIZATION 466 "Common Control And Management Protocols (CCAMP) 467 Working Group" 468 CONTACT-INFO 469 " Thomas D. Nadeau 470 Cisco Systems, Inc. 471 Email: tnadeau@cisco.com 473 Cheenu Srinivasan 474 Bloomberg L.P. 475 Email: cheenu@bloomberg.net 477 Adrian Farrel 478 Old Dog Consulting 479 Email: adrian@olddog.co.uk 481 Ed Harrison 482 Data Connection Ltd. 483 Email: ed.harrison@dataconnection.com 485 Tim Hall 486 Data Connection Ltd. 487 Email: tim.hall@dataconnection.com 489 Comments about this document should be emailed direct to the 490 CCAMP working group mailing list at ccamp@ops.ietf.org" 492 DESCRIPTION 493 "This MIB module contains managed object definitions 494 for GMPLS Traffic Engineering (TE). 496 Copyright (C) The Internet Society (2004). This 497 version of this MIB module is part of RFCXXX; see 498 the RFC itself for full legal notices." 500 -- Revision history. 501 REVISION 502 "200406010900Z" -- 1 June 2004 09:00:00 GMT 503 DESCRIPTION 504 "Initial revision, published as part of RFC XXXX." 505 ::= { gmplsStdMIB xx } 507 -- Top level components of this MIB. 509 -- Notifications 510 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 512 -- tables, scalars 513 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } 514 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } 516 -- conformance 517 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } 519 -- GMPLS Tunnel scalars. 521 gmplsTunnelsConfigured OBJECT-TYPE 522 SYNTAX Unsigned32 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "The number of GMPLS tunnels configured on this 527 device. A GMPLS tunnel is considered configured if 528 an entry for the tunnel exists in the 529 gmplsTunnelTable and the associated 530 mplsTunnelRowStatusis active(1)." 531 ::= { gmplsTeScalars 1 } 533 gmplsTunnelsActive OBJECT-TYPE 534 SYNTAX Unsigned32 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "The number of GMPLS tunnels active on this device. 539 A GMPLS tunnel is considered active if there is an 540 entry in the gmplsTunnelTable and the associated 541 mplsTunnelOperStatus for the tunnel is up(1)." 542 ::= { gmplsTeScalars 2 } 544 -- End of GMPLS Tunnel scalars. 546 -- GMPLS tunnel table. 548 gmplsTunnelTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF GmplsTunnelEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "The gmplsTunnelTable 'extends' the mplsTunnelTable. 554 It allows GMPLS tunnels to be created between an LSR 555 and a remote endpoint, and existing tunnels to be 556 reconfigured or removed. 557 Note that only point-to-point tunnel segments are 558 supported, although multi-point-to-point and point- 559 to-multi-point connections are supported by an LSR 560 acting as a cross-connect. Each tunnel can thus have 561 one out-segment originating at this LSR and/or one 562 in-segment terminating at this LSR. 564 The row status of an entry in this table is 565 controlled by mplsTunnelRowStatus in the 566 corresponding entry in mplsTunnelTable. That is, 567 it is not permitted to create a row in this table, 568 nor to modify an existing row, when the 569 corresponding mplsTunnelRowStatus has value 570 active(1). 572 The exception to this rule is the gmplsTunnelAdminStatusFlags 573 object, which can be modified whilst the tunnel is active." 574 ::= { gmplsTeObjects 1 } 576 gmplsTunnelEntry OBJECT-TYPE 577 SYNTAX GmplsTunnelEntry 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "An entry in this table in association with the 582 corresponding entry in the mplsTunnelTable 583 represents a GMPLS tunnel. 584 An entry can be created by a network administrator 585 or by an SNMP agent as instructed by a signaling 586 protocol." 587 INDEX { 588 mplsTunnelIndex, 589 mplsTunnelInstance, 590 mplsTunnelIngressLSRId, 591 mplsTunnelEgressLSRId 592 } 593 ::= { gmplsTunnelTable 1 } 595 GmplsTunnelEntry ::= SEQUENCE { 596 gmplsTunnelUnnumIf TruthValue, 597 gmplsTunnelAttributes BITS, 598 gmplsTunnelLSPEncoding Integer32, 599 gmplsTunnelSwitchingType Integer32, 600 gmplsTunnelLinkProtection BITS, 601 gmplsTunnelGPid Integer32, 602 gmplsTunnelSecondary TruthValue, 603 gmplsTunnelDirection INTEGER, 604 gmplsTunnelPathComp INTEGER, 605 gmplsTunnelUpNotRecip IpAddress, 606 gmplsTunnelDownNotRecip IpAddress, 607 gmplsTunnelAdminStatusFlags BITS, 608 gmplsTunnelExtraParamsPtr RowPointer 609 } 611 gmplsTunnelUnnumIf OBJECT-TYPE 612 SYNTAX TruthValue 613 MAX-ACCESS read-create 614 STATUS current 615 DESCRIPTION 616 "Denotes whether or not this tunnel corresponds to an 617 unnumbered interface represented in the interfaces 618 group table. 619 This object is only used if mplsTunnelIsIf is set to 620 'true'. 621 If both this object and the mplsTunnelIsIf object 622 are set to 'true', the originating LSR adds an 623 LSP_TUNNEL_INTERFACE_ID object to the outgoing Path 624 message. 625 This object contains information that is only used 626 by the terminating LSR." 627 REFERENCE 628 "Signalling Unnumbered Links in RSVP-TE, Kompella, K. 629 and Rekhter, Y., RFC 3477, January 2003." 630 DEFVAL { false } 631 ::= { gmplsTunnelEntry 1 } 633 gmplsTunnelAttributes OBJECT-TYPE 634 SYNTAX BITS { 635 labelRecordingDesired (0) 636 } 637 MAX-ACCESS read-create 638 STATUS current 639 DESCRIPTION 640 "This bitmask indicates optional parameters for this 641 tunnel. These bits should be taken in addition to 642 those defined in mplsTunnelSessionAttributes in 643 order to determine the full set of options to be 644 signaled (for example SESSION_ATTRIBUTES flags in 645 RSVP-TE). 646 The following describes these bitfields: 648 labelRecordingDesired 649 This flag indicates that label information should be 650 included when doing a route record. This bit is not 651 valid unless the recordRoute bit is set." 653 REFERENCE 654 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 655 Awduche et al, RFC 3209, December 2001." 656 DEFVAL { { } } 657 ::= { gmplsTunnelEntry 2 } 658 gmplsTunnelLSPEncoding OBJECT-TYPE 659 SYNTAX Integer32 (0..255) 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "This object indicates the encoding of the LSP being 664 requested. 665 A value of zero indicates that GMPLS signaling is 666 not in use. Some objects in this MIB module may be 667 of use for MPLS signaling extensions that do not use 668 GMPLS signaling. By setting this object to zero, an 669 application may indicate that only those objects 670 meaningful in MPLS should be examined. 671 The values to use are currently defined in 672 Generalized Multi-Protocol Label Switching (GMPLS) 673 Signaling Functional Description, RFC 3471. Further 674 values may be defined in future RFCs. 675 tunnelLspPacket (1), 676 tunnelLspEthernet (2), 677 tunnelLspAnsiEtsiPdh (3), 678 -- the value 4 is deprecated 679 tunnelLspSdhSonet (5), 680 -- the value 6 is deprecated 681 tunnelLspDigitalWrapper (7), 682 tunnelLspLambda (8), 683 tunnelLspFiber (9), 684 -- the value 10 is deprecated 685 tunnelLspFiberChannel (11), 686 tunnelDigitalPath (12), 687 tunnelOpticalChannel (13)" 688 REFERENCE 689 "1. Berger, L., et al., Generalized Multi-Protocol 690 Label Switching (GMPLS) Signaling Functional 691 Description, RFC 3471, January 2003. 692 2. D. Papadimitriou (Editor), Generalized MPLS 693 Signalling Extensions for G.709 Optical Transport 694 Networks Control" 695 DEFVAL { 0 } 696 ::= { gmplsTunnelEntry 3 } 698 gmplsTunnelSwitchingType OBJECT-TYPE 699 SYNTAX Integer32 (0..255) 700 MAX-ACCESS read-create 701 STATUS current 702 DESCRIPTION 703 "Indicates the type of switching that should be performed on 704 a particular link. This field is needed for links that 705 advertise more than one type of switching capability. Values 706 of this object are as the Switching Capability field defined 707 in Internet Draft OSPF Extensions in Support of Generalized 708 MPLS. Further values may be defined in future RFCs. 709 unknown (0), 710 psc1 (1), 711 psc2 (2), 712 psc3 (3), 713 psc4 (4), 714 l2sc (51), 715 tdm (100), 716 lsc (150), 717 fsc (200) 718 This object is only meaningful if 719 gmplsTunnelLSPEncoding is not set to 0." 720 REFERENCE 721 "1. Kompella, K., et al., OSPF Extensions in Support 722 of Generalized MPLS, draft-ietf-ccamp-ospf-gmpls- 723 extensions-12.txt, October 2003, work in progress. 724 2. Berger, L., et al., Generalized Multi-Protocol 725 Label Switching (GMPLS) Signaling Functional 726 Description, RFC 3471, January 2003." 727 DEFVAL { 0 } 728 ::= { gmplsTunnelEntry 4 } 730 gmplsTunnelLinkProtection OBJECT-TYPE 731 SYNTAX BITS { 732 extraTraffic(0), 733 unprotected(1), 734 shared (2), 735 dedicatedOneToOne (3), 736 dedicatedOnePlusOne(4), 737 enhanced(5) 738 } 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "This bitmask indicates the level of link protection 743 required. A value of zero (no bits set) indicates 744 that any protection may be used. 745 The following describes these bitfields: 747 extraTraffic 748 Indicates that the LSP should use links that are 749 protecting other (primary) traffic. Such LSPs may 750 be preempted when the links carrying the (primary) 751 traffic being protected fail. 753 unprotected 754 Indicates that the LSP should not use any link layer 755 protection. 757 shared 758 Indicates that a shared link layer protection scheme, 759 such as 1:N protection, should be used to support the LSP. 761 dedicatedOneToOne 762 Indicates that a dedicated link layer protection scheme, 763 i.e., 1:1 protection, should be used to support the LSP. 765 dedicatedOnePlusOne 766 Indicates that a dedicated link layer protection scheme, 767 i.e., 1+1 protection, should be used to support the LSP. 769 enhanced 770 Indicates that a protection scheme that is more reliable than 771 Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. 773 This object is only meaningful if 774 gmplsTunnelLSPEncoding is not set to 0." 775 DEFVAL { { } } 776 ::= { gmplsTunnelEntry 5 } 778 gmplsTunnelGPid OBJECT-TYPE 779 SYNTAX Integer32 (0..65535) 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "This object indicates the payload carried by the 784 LSP. It is only required when GMPLS will be used for 785 this LSP. 787 The values to use are currently defined in 788 Generalized Multi-Protocol Label Switching (GMPLS) 789 Signaling Functional Description, RFC 3471. Further 790 values may be defined in future RFCs. 792 unknown(0), 793 asynchE4(5), 794 asynchDS3T3(6), 795 asynchE3(7), 796 bitsynchE3(8), 797 bytesynchE3(9), 798 asynchDS2T2(10), 799 bitsynchDS2T2(11), 800 asynchE1(13), 801 bytesynchE1(14), 802 bytesynch31ByDS0(15), 803 asynchDS1T1(16), 804 bitsynchDS1T1(17), 805 bytesynchDS1T1(18), 806 VC11VC12(19), 807 ds1SFAsynch(22), 808 ds1ESFAsynch(23), 809 ds3M23Asynch(24), 810 ds3CBitParityAsynch(25), 811 vtLovc(26), 812 stsSpeHovc(27), 813 posNoScramble16BitCrc(28), 814 posNoScramble32BitCrc(29), 815 posScramble16BitCrc(30), 816 posScramble32BitCrc(31), 817 atm(32) 818 ethernet(33), 819 sdhSonet(34), 820 digitalwrapper(36), 821 lambda(37), 822 ansiEtsiPdh (38), 823 lapsSdh (40), 824 fddi (41), 825 dqdb (42), 826 fiberChannel3 (43), 827 hdlc (44), 828 ethernetV2DixOnly (45), 829 ethernet802dot3Only (46), 830 g709ODUj (47), 831 g709OTUk (48), 832 g709CBRorCBRa (49), 833 g709CBRb (50), 834 g709BSOT (51), 835 g709BSNT (52), 836 gfpIPorPPP (53), 837 gfpEthernetMAC (54), 838 gfpEthernetPHY (55), 839 g709ESCON (56), 840 g709FICON (57), 841 g709FiberChannel (58) 843 This object is only meaningful if 844 gmplsTunnelLSPEncoding is not set to 0." 845 REFERENCE 846 "1. Berger, L., et al., Generalized Multi-Protocol 847 Label Switching (GMPLS) Signaling Functional 848 Description, RFC 3471, January 2003." 849 DEFVAL { 0 } 850 ::= { gmplsTunnelEntry 6 } 852 gmplsTunnelSecondary OBJECT-TYPE 853 SYNTAX TruthValue 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "Indicates that the requested LSP is a secondary LSP. 859 This object is only meaningful if 860 gmplsTunnelLSPEncoding is not set to 0." 861 DEFVAL { false } 862 ::= { gmplsTunnelEntry 7 } 864 gmplsTunnelDirection OBJECT-TYPE 865 SYNTAX INTEGER { 866 forward (0), 867 bidirectional (1) 868 } 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "Whether this tunnel carries forward data (is 873 unidirectional) or is bidirectional. 874 Values of this object other than 'forward' are meaningful 875 only if gmplsTunnelLSPEncoding is not set to 0." 876 DEFVAL { forward } 877 ::= { gmplsTunnelEntry 8 } 879 gmplsTunnelPathComp OBJECT-TYPE 880 SYNTAX INTEGER { 881 dynamicFull(1),-- CSPF fully computed 882 explicit(2),-- fully specified path 883 dynamicPartial(3) -- CSPF partially computed 884 } 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "This value instructs the source node on how to perform 889 path computation on the explicit route specified by the 890 associated entries in the gmplsTunnelHopTable. 892 dynamicFull 893 The user specifies at least the source and 894 destination of the path and expects that the CSPF 895 will calculate the remainder of the path. 896 explicit 897 The user specifies the entire path for the tunnel to 898 take. This path may contain strict or loose hops. 899 Evaluation of the explicit route will be performed 900 hop by hop through the network. 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 This object deprecates gmplsTunnelHopEntryPathComp." 910 DEFVAL { dynamicFull } 911 ::= { gmplsTunnelEntry 9 } 913 gmplsTunnelUpNotRecip OBJECT-TYPE 914 SYNTAX IpAddress 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "Indicates the address of the upstream recipient for Notify 919 messages relating to this tunnel. 921 This object is only valid when signaling a tunnel using 922 RSVP. It is also not valid at the tail end of the tunnel. 924 If set to 0, no Notify Request object will be included in 925 outgoing Path messages." 927 DEFVAL { '00000000'H } -- 0.0.0.0 928 ::= { gmplsTunnelEntry 10 } 930 gmplsTunnelDownNotRecip OBJECT-TYPE 931 SYNTAX IpAddress 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 "Indicates the address of the upstream recipient for Notify 936 messages relating to this tunnel. 938 This object is only valid when signaling a tunnel using 939 RSVP. It is also not valid at the head end of the tunnel. 941 If set to 0, no Notify Request object will be included in 942 outgoing Resv messages." 944 DEFVAL { '00000000'H } -- 0.0.0.0 945 ::= { gmplsTunnelEntry 11 } 947 gmplsTunnelAdminStatusFlags OBJECT-TYPE 948 SYNTAX BITS { 949 delInProgress (0), 950 adminDown (1), 951 testing (2), 952 reflect (31) 953 } 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "Determines the setting of the Admin Status flags in the 958 Admin Status object or TLV, as described in 959 RFC 3471. Setting this field to a non-zero value will 960 result in the inclusion of the admin status object on 961 signaling messages. 963 This value of this object can be modified when the 964 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 965 is active(1). By doing so, a new signaling message will be 966 triggered including the requested Admin Status object or 967 TLV." 969 ::= { gmplsTunnelEntry 12 } 971 gmplsTunnelExtraParamsPtr OBJECT-TYPE 972 SYNTAX RowPointer 973 MAX-ACCESS read-create 974 STATUS current 975 DESCRIPTION 976 "Some Tunnels will run over transports that can 977 usefully support technology-specific additional parameters 978 (for example, SONET resource usage). 979 Such can be supplied from an external table and referenced from 980 here. 981 A value of zeroDotzero in this attribute indicates that there 982 is no such additional information." 984 DEFVAL { zeroDotZero } 985 ::= { gmplsTunnelEntry 13 } 987 -- End of gmplsTunnelTable 989 -- Begin gmplsTunnelHopTable 991 gmplsTunnelHopTable OBJECT-TYPE 992 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "The gmplsTunnelHopTable 'extends' the 997 mplsTunnelHopTable. It is used to indicate the 998 explicit labels to be used in an explicit path for a 999 GMPLS tunnel defined in mplsTunnelTable and 1000 gmplsTunnelTable, when it is established using 1001 signaling. It does not insert new hops, but does 1002 define new values for hops defined in 1003 mplsTunnelHopTable. 1005 Each row in this table is indexed by the same 1006 indexes as mplsTunnelHopTable. It is acceptable for 1007 some rows in mplsTunnelHopTable to have 1008 corresponding entries in this table and some to have 1009 no corresponding entry in this table. 1011 The storage type for an entry in this table is 1012 inherited from mplsTunnelHopStorageType in the 1013 corresponding entry in mplsTunnelHopTable. 1015 The row status of an entry in this table is 1016 controlled by mplsTunnelHopRowStatus in the 1017 corresponding entry in mplsTunnelHopTable. That is, 1018 it is not permitted to create a row in this table, 1019 nor to modify an existing row, when the 1020 corresponding mplsTunnelHopRowStatus has value 1021 active(1)." 1022 ::= { gmplsTeObjects 2 } 1024 gmplsTunnelHopEntry OBJECT-TYPE 1025 SYNTAX GmplsTunnelHopEntry 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "An entry in this table represents additions to a 1030 tunnel hop defined in mplsTunnelHopEntry. At an 1031 ingress to a tunnel an entry in this table is 1032 created by a network administrator for an ERLSP to 1033 be set up by a signaling protocol. At transit and 1034 egress nodes an entry in this table may be used to 1035 represent the explicit path instructions received 1036 using the signaling protocol." 1038 INDEX { 1039 mplsTunnelHopListIndex, 1040 mplsTunnelHopPathOptionIndex, 1041 mplsTunnelHopIndex 1042 } 1043 ::= { gmplsTunnelHopTable 1 } 1045 GmplsTunnelHopEntry ::= SEQUENCE { 1046 gmplsTunnelHopLabelStatuses BITS, 1047 gmplsTunnelHopExpLabel Unsigned32, 1048 gmplsTunnelHopExpLabelPtr RowPointer, 1049 gmplsTunnelHopExpRvrsLabel Unsigned32, 1050 gmplsTunnelHopExpRvrsLabelPtr RowPointer 1051 } 1052 gmplsTunnelHopLabelStatuses OBJECT-TYPE 1053 SYNTAX BITS { 1054 forwardPresent (0), 1055 reversePresent (1) 1056 } 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "This bitmask indicates the presence of labels 1061 indicated by the gmplsTunnelHopExpLabel or 1062 gmplsTunnelHopExpLabelPtr and 1063 gmplsTunnelHopExpRvrsLabel or gmplsTunnelHopExpRvrsLabel 1064 objects. 1066 For the Present bits, a set bit indicates that a 1067 label is present for this hop in the route. This 1068 allows zero to be a valid label value." 1069 ::= { gmplsTunnelHopEntry 1 } 1071 gmplsTunnelHopExpLabel OBJECT-TYPE 1072 SYNTAX Unsigned32 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "If gmplsTunnelHopLabelStatuses object indicates that a 1077 forward label is present and gmplsTunnelHopExpLabelPtr 1078 contains the value zeroDotZero, then the label to use on this 1079 hop is found in this object encoded within a 32-bit integer." 1080 ::= { gmplsTunnelHopEntry 2 } 1082 gmplsTunnelHopExpLabelPtr OBJECT-TYPE 1083 SYNTAX RowPointer 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION 1087 "If the gmplsTunnelHopLabelStatuses object indicates 1088 that a forward label is present, this object contains 1089 a pointer to a row in another MIB table (such as the 1090 gmplsLabelTable) that contains the label to use on 1091 this hop in the forward direction. 1092 If the gmplsTunnelHopLabelStatuses object indicates that 1093 a forward label is present and this object contains the 1094 value zeroDotZero, then the label to use on this hop is 1095 found in the gmplsTunnelHopExpLabel object." 1096 DEFVAL { zeroDotZero } 1097 ::= { gmplsTunnelHopEntry 3 } 1099 gmplsTunnelHopExpRvrsLabel OBJECT-TYPE 1100 SYNTAX Unsigned32 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "If the gmplsTunnelHopLabelStatuses object indicates that a 1105 reverse label is present and gmplsTunnelHopExpRvrsLabelPtr 1106 contains the value zeroDotZero, then the label to use on 1107 this hop is found in this object encoded as a 32-bit integer." 1108 ::= { gmplsTunnelHopEntry 4 } 1109 gmplsTunnelHopExpRvrsLabelPtr OBJECT-TYPE 1110 SYNTAX RowPointer 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "If the gmplsTunnelHopLabelStatuses object indicates 1115 that a reverse label is present, this object contains 1116 a pointer to a row in another MIB table (such as the 1117 gmplsLabelTable) that contains the label to use on 1118 this hop in the reverse direction. 1119 If the gmplsTunnelHopLabelStatuses object indicates that 1120 a reverse label is present and this object contains the 1121 value zeroDotZero, then the label to use on this hop is 1122 found in the gmplsTunnelHopExpRvrsLabel object." 1123 DEFVAL { zeroDotZero } 1124 ::= { gmplsTunnelHopEntry 5 } 1126 -- End of gmplsTunnelHopTable 1128 -- Tunnel Actual Route Hop table. 1130 gmplsTunnelARHopTable OBJECT-TYPE 1131 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 1132 MAX-ACCESS not-accessible 1133 STATUS current 1134 DESCRIPTION 1135 "The gmplsTunnelARHopTable 'extends' the 1136 mplsTunnelARHopTable. It is used to indicate the 1137 labels currently in use for a GMPLS tunnel defined 1138 in mplsTunnelTable and gmplsTunnelTable, as reported 1139 by the signaling protocol. It does not insert new 1140 hops, but does define new values for hops defined in 1141 mplsTunnelARHopTable. 1143 Each row in this table is indexed by the same indexes as 1144 mplsTunnelARHopTable. It is acceptable for some rows in 1145 mplsTunnelARHopTable to have corresponding entries in this 1146 table and some to have no corresponding entry in this table. 1148 Note that since the information necessary to build 1149 entries within this table is not provided by some 1150 signaling protocols and might not be returned in all 1151 cases of other signaling protocols, implementation 1152 of this table and mplsTunnelARHopTable is optional. 1153 Furthermore, since the information in this table is 1154 actually provided by the signaling protocol after 1155 the path has been set-up, the entries in this table 1156 are provided only for observation, and hence, all 1157 variables in this table are accessible exclusively 1158 as read-only." 1159 ::= { gmplsTeObjects 3 } 1161 gmplsTunnelARHopEntry OBJECT-TYPE 1162 SYNTAX GmplsTunnelARHopEntry 1163 MAX-ACCESS not-accessible 1164 STATUS current 1165 DESCRIPTION 1166 "An entry in this table represents additions to a 1167 tunnel hop visible in mplsTunnelARHopEntry. An entry 1168 is created by the signaling protocol for a signaled 1169 ERLSP set up by the signaling protocol. 1171 At any node on the LSP (ingress, transit or egress) 1172 Thus at this table and mplsTunnelARHopTable (if the 1173 tables are supported and if the signaling protocol 1174 is recording actual route information) contains the 1175 actual route of the whole tunnel. If the signaling 1176 protocol is not recording the actual route, this 1177 table MAY report the information from the 1178 gmplsTunnelHopTable or the gmplsTunnelCHopTable. 1180 Note that the recording of actual labels is distinct 1181 from the recording of the actual route in some 1182 signaling protocols. This feature is enabled using 1183 the gmplsTunnelAttributes object." 1184 INDEX { 1185 mplsTunnelARHopListIndex, 1186 mplsTunnelARHopIndex 1187 } 1188 ::= { gmplsTunnelARHopTable 1 } 1190 GmplsTunnelARHopEntry ::= SEQUENCE { 1191 gmplsTunnelARHopLabelStatuses BITS, 1192 gmplsTunnelARHopExpLabel Unsigned32, 1193 gmplsTunnelARHopExpLabelPtr RowPointer, 1194 gmplsTunnelARHopExpRvrsLabel Unsigned32, 1195 gmplsTunnelARHopExpRvrsLabelPtr RowPointer, 1196 gmplsTunnelARHopProtection BITS 1197 } 1199 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1200 SYNTAX BITS { 1201 forwardPresent (0), 1202 reversePresent (1), 1203 forwardGlobal (2), 1204 reverseGlobal (3) 1205 } 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "This bitmask indicates the presence and status of 1210 labels indicated by the 1211 gmplsTunnelARHopExpLabel or gmplsTunnelARHopExpLabelPtr and 1212 gmplsTunnelARHopExpRvrsLabel or gmplsTunnelARHopExpRvrsLabelPtr 1213 objects. 1214 For the Present bits, a set bit indicates that a label 1215 is present for this hop in the route. For the Global bits, 1216 a set bit indicates that the label comes from the Global 1217 Label Space. A clear bit indicates that this is a Per- 1218 Interface label. A Global bit only has meaning if the 1219 corresponding Present bit is set." 1220 ::= { gmplsTunnelARHopEntry 1 } 1221 gmplsTunnelARHopExpLabel OBJECT-TYPE 1222 SYNTAX Unsigned32 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "If the gmplsTunnelARHopLabelStatuses object indicates 1227 that a forward label is present and 1228 gmplsTunnelARHopExpLabelPtr contains the value 1229 zeroDotZero, then the label in use on this hop is 1230 found in this object encoded within a 32-bit integer." 1231 ::= { gmplsTunnelARHopEntry 2 } 1233 gmplsTunnelARHopExpLabelPtr OBJECT-TYPE 1234 SYNTAX RowPointer 1235 MAX-ACCESS read-only 1236 STATUS current 1237 DESCRIPTION 1238 "If the gmplsTunnelARHopLabelStatuses object indicates 1239 that a forward label is present, this object contains 1240 a pointer to a row in another MIB table (such as the 1241 gmplsLabelTable) that contains the label in use on 1242 this hop in the forward direction. 1243 If the gmplsTunnelARHopLabelStatuses object indicates that 1244 a forward label is present and this object contains the 1245 value zeroDotZero, then the label in use on this hop is 1246 found in the gmplsTunnelARHopExpLabel object." 1247 ::= { gmplsTunnelARHopEntry 3 } 1249 gmplsTunnelARHopExpRvrsLabel OBJECT-TYPE 1250 SYNTAX Unsigned32 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "If the gmplsTunnelARHopLabelStatuses object indicates 1255 that a reverse label is present and 1256 gmplsTunnelARHopExpRvrsLabelPtr contains the value 1257 zeroDotZero, then the label in use on this hop is 1258 found in this object encoded as a 32-bit integer." 1259 ::= { gmplsTunnelARHopEntry 4 } 1261 gmplsTunnelARHopExpRvrsLabelPtr OBJECT-TYPE 1262 SYNTAX RowPointer 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "If the gmplsTunnelARHopLabelStatuses object indicates 1267 that a reverse label is present, this object contains 1268 a pointer to a row in another MIB table (such as the 1269 gmplsLabelTable) that contains the label in use on 1270 this hop in the reverse direction. 1271 If the gmplsTunnelARHopLabelStatuses object indicates that 1272 a reverse label is present and this object contains the 1273 value zeroDotZero, then the label in use on this hop is 1274 found in the gmplsTunnelARHopExpRvrsLabel object." 1275 ::= { gmplsTunnelARHopEntry 5 } 1276 gmplsTunnelARHopProtection OBJECT-TYPE 1277 SYNTAX BITS { 1278 localAvailable (0), 1279 localInUse (1) 1280 } 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "Availability and usage of protection on the reported link. 1286 localAvailable 1287 Indicates that the link downstream of this node 1288 is protected via a local repair mechanism. 1289 localInUse 1290 Indicates that a local repair mechanism is in use to 1291 maintain this tunnel (usually in the face of an outage 1292 of the link it was previously routed over)." 1293 ::= { gmplsTunnelARHopEntry 6 } 1295 -- End of mplsTunnelARHopTable 1297 -- Tunnel Computed Hop table. 1299 gmplsTunnelCHopTable OBJECT-TYPE 1300 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1301 MAX-ACCESS not-accessible 1302 STATUS current 1303 DESCRIPTION 1304 "The gmplsTunnelCHopTable 'extends' the mplsTunnelCHopTable. 1305 It is used to indicate additional information about the 1306 hops of a GMPLS tunnel defined in mplsTunnelTable and 1307 gmplsTunnelTable, as computed by a constraint-based 1308 routing protocol, based on the mplsTunnelHopTable 1309 and the gmplsTunnelHopTable. 1311 Each row in this table is indexed by the same indexes as 1312 mplsTunnelCHopTable. It is acceptable for some rows in 1313 mplsTunnelCHopTable to have corresponding entries in this 1314 table and some to have no corresponding entry in this table. 1316 Please note that since the information necessary to 1317 build entries within this table may not be supported 1318 by some LSRs, implementation of this table is optional. 1320 Furthermore, since the information in this table is actually 1321 provided by a path computation component after the path has 1322 been computed, the entries in this table are provided only 1323 for observation, and hence, all objects in this table are 1324 accessible exclusively as read-only." 1325 ::= { gmplsTeObjects 4 } 1327 gmplsTunnelCHopEntry OBJECT-TYPE 1328 SYNTAX GmplsTunnelCHopEntry 1329 MAX-ACCESS not-accessible 1330 STATUS current 1331 DESCRIPTION 1332 "An entry in this table represents additions to a 1333 computed tunnel hop visible in mplsTunnelCHopEntry. 1334 An entry is created by a path computation component 1335 based on the hops specified in the corresponding 1336 mplsTunnelHopTable and gmplsTunnelHopTable. 1338 At a transit LSR this table (if the table is 1339 supported) MAY contain the path computed by path 1340 computation engine on (or on behalf of) the transit LSR." 1341 INDEX { 1342 mplsTunnelCHopListIndex, 1343 mplsTunnelCHopIndex 1344 } 1345 ::= { gmplsTunnelCHopTable 1 } 1347 GmplsTunnelCHopEntry ::= SEQUENCE { 1348 gmplsTunnelCHopLabelStatuses BITS, 1349 gmplsTunnelCHopExpLabel Unsigned32, 1350 gmplsTunnelCHopExpLabelPtr RowPointer, 1351 gmplsTunnelCHopExpRvrsLabel Unsigned32, 1352 gmplsTunnelCHopExpRvrsLabelPtr RowPointer 1353 } 1355 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1356 SYNTAX BITS { 1357 forwardPresent (0), 1358 reversePresent (1) 1359 } 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "This bitmask indicates the presence of labels indicated by the 1364 gmplsTunnelCHopExpLabel or gmplsTunnelCHopExpLabelPtr and 1365 gmplsTunnelCHopExpRvrsLabel or gmplsTunnelCHopExpRvrsLabelPtr 1366 objects. 1367 A set bit indicates that a label is present for this hop in 1368 the route thus allowing zero to be a valid label value." 1369 ::= { gmplsTunnelCHopEntry 1 } 1371 gmplsTunnelCHopExpLabel OBJECT-TYPE 1372 SYNTAX Unsigned32 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "If the gmplsTunnelCHopLabelStatuses object indicates 1377 that a forward label is present and 1378 gmplsTunnelCHopExpLabelPtr contains the value 1379 zeroDotZero, then the label to use on this hop is 1380 found in this object encoded within a 32-bit integer." 1381 ::= { gmplsTunnelCHopEntry 2 } 1383 gmplsTunnelCHopExpLabelPtr OBJECT-TYPE 1384 SYNTAX RowPointer 1385 MAX-ACCESS read-only 1386 STATUS current 1387 DESCRIPTION 1388 "If the gmplsTunnelCHopLabelStatuses object indicates 1389 that a forward label is present, this object contains 1390 a pointer to a row in another MIB table (such as the 1391 gmplsLabelTable) that contains the label to use on 1392 this hop in the forward direction. 1393 If the gmplsTunnelCHopLabelStatuses object indicates that 1394 a forward label is present and this object contains the 1395 value zeroDotZero, then the label to use on this hop is 1396 found in the gmplsTunnelCHopExpLabel object." 1397 ::= { gmplsTunnelCHopEntry 3 } 1399 gmplsTunnelCHopExpRvrsLabel OBJECT-TYPE 1400 SYNTAX Unsigned32 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "If the gmplsTunnelCHopLabelStatuses object indicates 1405 that a reverse label is present and 1406 gmplsTunnelCHopExpRvrsLabelPtr contains the value 1407 zeroDotZero, then the label to use on this hop is 1408 found in this object encoded as a 32-bit integer." 1409 ::= { gmplsTunnelCHopEntry 4 } 1411 gmplsTunnelCHopExpRvrsLabelPtr OBJECT-TYPE 1412 SYNTAX RowPointer 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "If the gmplsTunnelCHopLabelStatuses object indicates 1417 that a reverse label is present, this object contains 1418 a pointer to a row in another MIB table (such as the 1419 gmplsLabelTable) that contains the label to use on 1420 this hop in the reverse direction. 1421 If the gmplsTunnelCHopLabelStatuses object indicates that 1422 a reverse label is present and this object contains the 1423 value zeroDotZero, then the label to use on this hop is 1424 found in the gmplsTunnelCHopExpRvrsLabel object." 1425 ::= { gmplsTunnelCHopEntry 5 } 1427 -- End of gmplsTunnelCHopTable 1429 -- GMPLS Tunnel Reverse Direction Performance Table. 1431 gmplsTunnelReversePerfTable OBJECT-TYPE 1432 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1433 MAX-ACCESS not-accessible 1434 STATUS current 1435 DESCRIPTION 1436 "This table 'augments' the gmplsTunnelTable to provides 1437 per-tunnel packet performance information for the 1438 reverse direction of a bidirectional tunnel. It can be 1439 seen as supplementing the mplsTunnelPerfTable which 1440 augments the mplsTunnelTable." 1441 ::= { gmplsTeObjects 5 } 1443 gmplsTunnelReversePerfEntry OBJECT-TYPE 1444 SYNTAX GmplsTunnelReversePerfEntry 1445 MAX-ACCESS not-accessible 1446 STATUS current 1447 DESCRIPTION 1448 "An entry in this table is created by the LSR for every 1449 bidirectional GMPLS tunnel where packets are visible to 1450 the LSR." 1451 AUGMENTS { gmplsTunnelEntry } 1452 ::= { gmplsTunnelReversePerfTable 1 } 1454 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1455 gmplsTunnelReversePerfPackets Counter32, 1456 gmplsTunnelReversePerfHCPackets Counter64, 1457 gmplsTunnelReversePerfErrors Counter32, 1458 gmplsTunnelReversePerfBytes Counter32, 1459 gmplsTunnelReversePerfHCBytes Counter64 1460 } 1462 gmplsTunnelReversePerfPackets OBJECT-TYPE 1463 SYNTAX Counter32 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "Number of packets forwarded on the tunnel in the 1468 reverse direction if it is bidirectional." 1469 ::= { gmplsTunnelReversePerfEntry 1 } 1471 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1472 SYNTAX Counter64 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "High capacity counter for number of packets forwarded on 1477 the tunnel in the reverse direction if it is bidirectional." 1478 ::= { gmplsTunnelReversePerfEntry 2 } 1480 gmplsTunnelReversePerfErrors OBJECT-TYPE 1481 SYNTAX Counter32 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "Number of errored packets received on the tunnel in 1486 the reverse direction if it is bidirectional." 1487 ::= { gmplsTunnelReversePerfEntry 3 } 1489 gmplsTunnelReversePerfBytes OBJECT-TYPE 1490 SYNTAX Counter32 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "Number of bytes forwarded on the tunnel in the 1495 reverse direction if it is bidirectional." 1496 ::= { gmplsTunnelReversePerfEntry 4 } 1498 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1499 SYNTAX Counter64 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "High capacity counter for number of bytes forwarded 1504 on the tunnel in the reverse direction if it is 1505 bidirectional." 1506 ::= { gmplsTunnelReversePerfEntry 5 } 1508 -- End of gmplsTunnelReversePerfTable 1510 -- GMPLS Tunnel Error Table. 1512 gmplsTunnelErrorTable OBJECT-TYPE 1513 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "This table 'augments' the mplsTunnelTable 1519 This table provides per-tunnel information about 1520 errors. Errors may be detected locally or reported 1521 through the signaling protocol. 1523 Error reporting is not exclusive to GMPLS and this 1524 table may be applied in MPLS systems." 1525 ::= { gmplsTeObjects 6 } 1527 gmplsTunnelErrorEntry OBJECT-TYPE 1528 SYNTAX GmplsTunnelErrorEntry 1529 MAX-ACCESS not-accessible 1530 STATUS current 1531 DESCRIPTION 1532 "An entry in this table is created by the LSR for 1533 every tunnel where error information is visible to 1534 the LSR. 1535 Note that systems which read the objects in this table 1536 one at a time may experience a discontinuity as the 1537 result of a new error occurring in between object reads. 1538 Systems that are vulnerable to this should read 1539 gmplsTunnelErrorLastTime before and after reading the 1540 other objects." 1541 AUGMENTS { mplsTunnelEntry } 1542 ::= { gmplsTunnelErrorTable 1 } 1544 GmplsTunnelErrorEntry ::= SEQUENCE { 1545 gmplsTunnelErrorLastErrorType INTEGER, 1546 gmplsTunnelErrorLastTime TimeStamp, 1547 gmplsTunnelErrorReporterType INTEGER, 1548 gmplsTunnelErrorReporter InetAddress, 1549 gmplsTunnelErrorCode Unsigned32, 1550 gmplsTunnelErrorSubcode Unsigned32, 1551 gmplsTunnelErrorTLVs OCTET STRING, 1552 gmplsTunnelErrorHelpString DisplayString 1553 } 1555 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1556 SYNTAX INTEGER { 1557 noError (0), 1558 unknown (1), 1559 localProtocol (2), 1560 remoteProtocol (3), 1561 configuration (4), 1562 pathComputation (5), 1563 localResources (6) 1564 } 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "The nature of the last error. Provides 1569 interpretation context for 1570 gmplsTunnelErrorProtocolCode and 1571 gmplsTunnelErrorProtocolSubcode. A value of noError 1572 (0) shows that there is no error associated with 1573 this tunnel and means that the other objects in this 1574 entry have no meaning." 1575 ::= { gmplsTunnelErrorEntry 1 } 1577 gmplsTunnelErrorLastTime OBJECT-TYPE 1578 SYNTAX TimeStamp 1579 MAX-ACCESS read-only 1580 STATUS current 1581 DESCRIPTION 1582 "The time at which the last error occurred. This is 1583 presented as the value of SysUpTime when the error 1584 occurred or was reported to this node. 1585 If gmplsTunnelErrorLastErrorType has the value 1586 noError (0), then this object is ignored." 1587 ::= { gmplsTunnelErrorEntry 2 } 1589 gmplsTunnelErrorReporterType OBJECT-TYPE 1590 SYNTAX INTEGER { 1591 unknown (0), 1592 localNode (1), 1593 localIpV4 (2), 1594 remoteIpV4 (3), 1595 localIpV6 (4), 1596 remoteIpV6 (5) 1597 } 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The reporter of the last error recorded. 1602 This object is used principally to aid in interpretation 1603 of gmplsTunnelErrorReporterIpv4Addr and 1604 gmplsTunnelErrorReporterIpv6Addr. Where the error has 1605 been locally generated and there is no requirement to 1606 associate the error with any specific local address (such 1607 as an interface), the value localNode (2) may be used. 1608 If gmplsTunnelErrorLastError has the value noError 1609 (0), then this object is ignored." 1610 ::= { gmplsTunnelErrorEntry 3 } 1612 gmplsTunnelErrorReporter OBJECT-TYPE 1613 SYNTAX InetAddress 1614 MAX-ACCESS read-only 1615 STATUS current 1616 DESCRIPTION 1617 "The address of the node reporting the last error, or 1618 the address of the resource (such as an interface) 1619 associated with the error. 1620 If gmplsTunnelErrorLastErrorType has the value 1621 noError (0), then this object is ignored. 1622 This object should be interpreted in the context of 1623 the value of the object gmplsTunnelErrorReporterType. 1624 If that object has value localIpV4 (2) or remoteIpV4 (3), 1625 this object should be viewed as having a syntax of 1626 InetAddressIPv4. If gmplsTunnelErrorReporterType has 1627 value localIpV6 (3) or remoteIpV6 (5), this object should be 1628 viewed as having a syntax of InetAddressIPv6. Otherwise the 1629 object should contain the value zero and should be ignored." 1630 REFERENCE 1631 "RFC3291, Textual Conventions for Internet Network 1632 Addresses, Section 4. Usage Hints." 1633 ::= { gmplsTunnelErrorEntry 4 } 1635 gmplsTunnelErrorCode OBJECT-TYPE 1636 SYNTAX Unsigned32 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "The primary error code associated with the last 1641 error. 1643 The interpretation of this error code depends on the 1644 value of gmplsTunnelErrorLastErrorType. If the value 1645 of gmplsTunnelErrorLastErrorType is noError (0) the 1646 value of this object should be 0 and should be 1647 ignored. If the value of 1648 gmplsTunnelErrorLastErrorType is localProtocol (2) 1649 or remoteProtocol (3) the error should be 1650 interpreted in the context of the signling protocol 1651 identified by the mplsTunnelSignallingProto object. 1653 Values in excess 32767 of are not used by signaling 1654 protocols and may safely be used as implementation- 1655 specific error codes. " 1656 ::= { gmplsTunnelErrorEntry 5 } 1658 gmplsTunnelErrorSubcode OBJECT-TYPE 1659 SYNTAX Unsigned32 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "The secondary error code associated with the last 1664 error and the protocol used to signal this tunnel. 1665 This value is interprettd in the context of the 1666 value of gmplsTunnelErrorCode. 1667 If the value of gmplsTunnelErrorLastErrorType is 1668 noError (0) the value of this object should be 0 and 1669 should be ignored." 1670 ::= { gmplsTunnelErrorEntry 6 } 1671 gmplsTunnelErrorTLVs OBJECT-TYPE 1672 SYNTAX OCTET STRING 1673 MAX-ACCESS read-only 1674 STATUS current 1675 DESCRIPTION 1676 "The sequence of interface identifier TLVs reported 1677 with the error by the protocol code. The interpretation 1678 of the TLVs and the encoding within the protocol are 1679 described in the references. 1680 A value of zero in the first octet indicates that no 1681 TLVs are present." 1682 REFERENCE 1683 "RFC3471, Generalized Multi-Protocol Label Switching 1684 (GMPLS) Signaling Functional Description, 1685 Section 9.1. Interface Identification. 1686 RFC3473, Generalized Multi-Protocol Label Switching 1687 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1688 Engineering (RSVP-TE) Extensions, Section 8.2. Errored 1689 Interface Identification" 1690 ::= { gmplsTunnelErrorEntry 7 } 1692 gmplsTunnelErrorHelpString OBJECT-TYPE 1693 SYNTAX DisplayString 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "A textual string containing information about the 1698 last error, recovery actions and support advice. If 1699 there is no help string this object contains a zero 1700 length string. 1701 If the value of gmplsTunnelErrorLastErrorType is 1702 noError (0) this object should contain a zero length 1703 string, but may contain a help string indicating 1704 that there is no error." 1705 ::= { gmplsTunnelErrorEntry 8 } 1707 -- GMPLS Notifications. 1709 gmplsTunnelDown NOTIFICATION-TYPE 1710 OBJECTS { 1711 mplsTunnelAdminStatus, 1712 mplsTunnelOperStatus, 1713 gmplsTunnelErrorLastErrorType, 1714 gmplsTunnelErrorReporterType, 1715 gmplsTunnelErrorReporter, 1716 gmplsTunnelErrorCode, 1717 gmplsTunnelErrorSubcode 1718 } 1719 STATUS current 1720 DESCRIPTION 1721 "This notification is generated when a 1722 mplsTunnelOperStatus object for one of the 1723 configured tunnels is about to enter the down state 1724 from some other state (but not from the notPresent 1725 state). This other state is indicated by the 1726 included value of mplsTunnelOperStatus. 1727 The objects in this notification provide additional 1728 error information that indicates the reason why the 1729 tunnel has transitioned down. 1730 Note that an implementation SHOULD only issue one of 1731 mplsTunnelDown and gmplsTunnelDown for a single event 1732 on a single tunnel." 1733 ::= { gmplsTeNotifications 1 } 1735 -- End of notifications. 1737 -- Module compliance. 1739 gmplsTeGroups 1740 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1742 gmplsTeCompliances 1743 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1745 gmplsTeModuleCompliance MODULE-COMPLIANCE 1746 STATUS current 1747 DESCRIPTION 1748 "Compliance statement for agents that support the 1749 GMPLS TE MIB." 1750 MODULE -- this module 1752 -- The mandatory group has to be implemented by all 1753 -- LSRs that originate/terminate ESLSPs/tunnels. 1754 -- In addition, depending on the type of tunnels 1755 -- supported, other groups become mandatory as 1756 -- explained below. 1758 MANDATORY-GROUPS { 1759 gmplsTunnelGroup, 1760 gmplsTunnelScalarGroup 1761 } 1763 -- GROUP gmplsTunnelManualGroup 1764 -- DESCRIPTION 1765 -- "This group is mandatory for devices which support 1766 -- manual configuration of tunnels, in addition to 1767 -- gmplsTunnelGroup. The following constraints apply: 1768 -- mplsTunnelSignallingProto should be at least read- 1769 -- only with a value of none(1)." 1771 GROUP gmplsTunnelSignaledGroup 1772 DESCRIPTION 1773 "This group is mandatory for devices which support 1774 signaled tunnel set up, in addition to 1775 gmplsTunnelGroup. The following constraints apply: 1777 mplsTunnelSignallingProto should be at least read- 1778 only returning a value of ldp(2), or rsvp(3)." 1780 GROUP gmplsTunnelIsNotIntfcGroup 1781 DESCRIPTION 1782 "This group is mandatory for devices which support 1783 tunnels that are not interfaces, in addition to 1784 gmplsTunnelGroup. The following constraints apply: 1786 gmplsTunnelIsIf must at least be read-only returning no(0)." 1788 GROUP gmplsTunnelIsIntfcGroup 1789 DESCRIPTION 1790 "This group is mandatory for devices which support 1791 tunnels that are interfaces, in addition to 1792 gmplsTunnelGroup." 1794 GROUP gmplsTunnelOptionalGroup 1795 DESCRIPTION 1796 "Objects in this group are optional." 1798 GROUP gmplsTeNotificationGroup 1799 DESCRIPTION "This group is mandatory for those implementations 1800 which can implement the notifications contained 1801 in this group." 1803 -- GMPLS Tunnel scalars. 1804 -- All scalars have max access read-only 1806 -- gmplsTunnelTable 1808 OBJECT gmplsTunnelAttributes 1809 MIN-ACCESS read-only 1810 DESCRIPTION 1811 "Write access is not required." 1813 OBJECT gmplsTunnelLSPEncoding 1814 SYNTAX Integer32 1815 MIN-ACCESS read-only 1816 DESCRIPTION 1817 "Write access is not required." 1819 OBJECT gmplsTunnelSwitchingType 1820 SYNTAX Integer32 1821 MIN-ACCESS read-only 1822 DESCRIPTION 1823 "Write access is not required." 1825 OBJECT gmplsTunnelLinkProtection 1826 MIN-ACCESS read-only 1827 DESCRIPTION 1828 "Write access is not required." 1830 OBJECT gmplsTunnelGPid 1831 MIN-ACCESS read-only 1832 DESCRIPTION 1833 "Write access is not required." 1835 OBJECT gmplsTunnelSecondary 1836 SYNTAX TruthValue 1837 MIN-ACCESS read-only 1838 DESCRIPTION 1839 "Write access is not required." 1841 OBJECT gmplsTunnelDirection 1842 SYNTAX INTEGER { 1843 forward (0), 1844 bidirectional (1) 1845 } 1846 MIN-ACCESS read-only 1847 DESCRIPTION 1848 "Only forward (0) is required." 1850 OBJECT gmplsTunnelPathComp 1851 SYNTAX INTEGER { 1852 dynamicFull(1), -- CSPF fully computed 1853 explicit(2), -- fully 1854 dynamicPartial(3) -- CSPF partially computed 1855 } 1857 MIN-ACCESS read-only 1858 DESCRIPTION 1859 "Only explicit (2) is required." 1861 OBJECT gmplsTunnelUpNotRecip 1862 SYNTAX IpAddress 1863 MIN-ACCESS read-only 1864 DESCRIPTION 1865 "Write access is not required." 1867 OBJECT gmplsTunnelDownNotRecip 1868 SYNTAX IpAddress 1869 MIN-ACCESS read-only 1870 DESCRIPTION 1871 "Write access is not required." 1873 OBJECT gmplsTunnelAdminStatusFlags 1874 SYNTAX BITS { 1875 delInProgress (0), 1876 adminDown (1), 1877 testing (2), 1878 reflect (31) 1879 } 1880 MIN-ACCESS read-only 1881 DESCRIPTION 1882 "Write access is not required." 1884 OBJECT gmplsTunnelExtraParamsPtr 1885 SYNTAX RowPointer 1886 MIN-ACCESS read-only 1887 DESCRIPTION 1888 "Write access is not required." 1890 -- gmplsTunnelHopTable 1892 -- gmplsTunnelHopLabelStatuses has max access read-only 1894 OBJECT gmplsTunnelHopExpLabel 1895 MIN-ACCESS read-only 1896 DESCRIPTION 1897 "Write access is not required." 1899 OBJECT gmplsTunnelHopExpLabelPtr 1900 MIN-ACCESS read-only 1901 DESCRIPTION 1902 "Write access is not required." 1904 OBJECT gmplsTunnelHopExpRvrsLabel 1905 MIN-ACCESS read-only 1906 DESCRIPTION 1907 "Write access is not required." 1909 OBJECT gmplsTunnelHopExpRvrsLabelPtr 1910 MIN-ACCESS read-only 1911 DESCRIPTION 1912 "Write access is not required." 1914 -- gmplsTunnelARHopTable 1915 -- all objects have max access read-only 1917 -- glmpsTunnelCHopTable 1918 -- all objects have max access read-only 1920 -- gmplsTunnelReversePerfTable 1921 -- all objects have max access read-only 1923 -- gmplsTunnelErrorTable 1924 -- all objects have max access read-only 1925 ::= { gmplsTeCompliances 1 } 1927 -- Units of conformance. 1929 gmplsTunnelGroup OBJECT-GROUP 1930 OBJECTS { 1931 gmplsTunnelDirection, 1932 gmplsTunnelReversePerfPackets, 1933 gmplsTunnelReversePerfHCPackets, 1934 gmplsTunnelReversePerfErrors, 1935 gmplsTunnelReversePerfBytes, 1936 gmplsTunnelReversePerfHCBytes, 1937 gmplsTunnelErrorLastErrorType, 1938 gmplsTunnelErrorLastTime, 1939 gmplsTunnelErrorReporterType, 1940 gmplsTunnelErrorReporter, 1941 gmplsTunnelErrorCode, 1942 gmplsTunnelErrorSubcode, 1943 gmplsTunnelErrorTLVs, 1944 gmplsTunnelErrorHelpString 1945 } 1946 STATUS current 1947 DESCRIPTION 1948 "Necessary, but not sufficient, set of objects to implement 1949 tunnels. In addition, depending on the type of the tunnels 1950 supported (for example, manually configured or signaled, 1951 persistent or non-persistent, etc.), the following other 1952 groups defined below are mandatory: gmplsTunnelManualGroup 1953 and/or gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup 1954 and/or gmplsTunnelIsIntfcGroup." 1955 ::= { gmplsTeGroups 1 } 1957 -- gmplsTunnelManualGroup OBJECT-GROUP 1958 -- OBJECTS { 1959 -- mplsTunnelSignallingProto 1960 -- } 1961 -- STATUS current 1962 -- DESCRIPTION 1963 -- "Object(s) needed to implement manually configured 1964 -- tunnels." 1965 -- ::= { gmplsTeGroups 2 } 1967 gmplsTunnelSignaledGroup OBJECT-GROUP 1968 OBJECTS { 1969 gmplsTunnelAttributes, 1970 gmplsTunnelLSPEncoding, 1971 gmplsTunnelSwitchingType, 1972 gmplsTunnelLinkProtection, 1973 gmplsTunnelGPid, 1974 gmplsTunnelSecondary, 1975 gmplsTunnelPathComp, 1976 gmplsTunnelUpNotRecip, 1977 gmplsTunnelDownNotRecip, 1978 gmplsTunnelAdminStatusFlags, 1979 gmplsTunnelHopLabelStatuses, 1980 gmplsTunnelHopExpLabel, 1981 gmplsTunnelHopExpLabelPtr, 1982 gmplsTunnelHopExpRvrsLabel, 1983 gmplsTunnelHopExpRvrsLabelPtr 1984 } 1986 STATUS current 1987 DESCRIPTION 1988 "Objects needed to implement signaled tunnels." 1989 ::= { gmplsTeGroups 3 } 1991 gmplsTunnelScalarGroup OBJECT-GROUP 1992 OBJECTS { 1993 gmplsTunnelsConfigured, 1994 gmplsTunnelsActive 1995 } 1996 STATUS current 1997 DESCRIPTION 1998 "Scalar objects needed to implement MPLS tunnels." 1999 ::= { gmplsTeGroups 4 } 2001 gmplsTunnelIsIntfcGroup OBJECT-GROUP 2002 OBJECTS { 2003 gmplsTunnelUnnumIf 2004 } 2005 STATUS current 2006 DESCRIPTION 2007 "Objects needed to implement tunnels that are 2008 interfaces." 2009 ::= { gmplsTeGroups 5 } 2010 gmplsTunnelIsNotIntfcGroup OBJECT-GROUP 2011 OBJECTS { 2012 gmplsTunnelUnnumIf 2013 } 2014 STATUS current 2015 DESCRIPTION 2016 "Objects needed to implement tunnels that are not 2017 interfaces." 2018 ::= { gmplsTeGroups 6 } 2020 gmplsTunnelOptionalGroup OBJECT-GROUP 2021 OBJECTS { 2022 gmplsTunnelExtraParamsPtr, 2023 gmplsTunnelARHopLabelStatuses, 2024 gmplsTunnelARHopExpLabel, 2025 gmplsTunnelARHopExpLabelPtr, 2026 gmplsTunnelARHopExpRvrsLabel, 2027 gmplsTunnelARHopExpRvrsLabelPtr, 2028 gmplsTunnelARHopProtection, 2029 gmplsTunnelCHopLabelStatuses, 2030 gmplsTunnelCHopExpLabel, 2031 gmplsTunnelCHopExpLabelPtr, 2032 gmplsTunnelCHopExpRvrsLabel, 2033 gmplsTunnelCHopExpRvrsLabelPtr 2034 } 2035 STATUS current 2036 DESCRIPTION 2037 "The objects in this group are optional." 2038 ::= { gmplsTeGroups 7 } 2040 gmplsTeNotificationGroup NOTIFICATION-GROUP 2041 NOTIFICATIONS { 2042 gmplsTunnelDown 2043 } 2044 STATUS current 2045 DESCRIPTION 2046 "Set of notifications implemented in this module. 2047 None is mandatory." 2048 ::= { gmplsTeGroups 8 } 2050 END 2052 9. Security Considerations 2054 It is clear that the MIB modules described in this document in 2055 association with the MPLS-TE-STD-MIB are potentially useful for 2056 monitoring of MPLS and GMPLS tunnels. These MIB modules can also be 2057 used for configuration of certain objects, and anything that can be 2058 configured can be incorrectly configured, with potentially disastrous 2059 results. 2061 There are a number of management objects defined in these MIB modules 2062 with a MAX-ACCESS clause of read-write and/or read-create. Such 2063 objects may be considered sensitive or vulnerable in some network 2064 environments. The support for SET operations in a non-secure 2065 environment without proper protection can have a negative effect on 2066 network operations. These are the tables and objects and their 2067 sensitivity/vulnerability: 2069 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 2070 objects to provision GMPLS tunnels interfaces at their ingress 2071 LSRs. Unauthorized write access to objects in these tables, could 2072 result in disruption of traffic on the network. This is especially 2073 true if a tunnel has already been established. The use of stronger 2074 mechanisms such as SNMPv3 security should be considered where 2075 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 2076 SNMPv3 agent which implements these MIB modules. 2078 Some of the readable objects in these MIB modules "i.e., objects with 2079 a MAX-ACCESS other than not-accessible" may be considered sensitive 2080 or vulnerable in some network environments. It is thus important to 2081 control even GET and/or NOTIFY access to these objects and possibly 2082 to even encrypt the values of these objects when sending them over 2083 the network via SNMP. These are the tables and objects and their 2084 sensitivity/vulnerability: 2086 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 2087 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, 2088 gmplsTunnelErrorTable collectively show the tunnel network 2089 topology and status. If an Administrator does not want to reveal 2090 this information, then these tables should be considered 2091 sensitive/vulnerable. 2093 SNMP versions prior to SNMPv3 did not include adequate security. Even 2094 if the network itself is secure "for example by using IPSec", even 2095 then, there is no control as to who on the secure network is allowed 2096 to access and GET/SET "read/change/create/delete" the objects in 2097 these MIB modules. It is RECOMMENDED that implementers consider the 2098 security features as provided by the SNMPv3 framework "see [RFC3410], 2099 section 8", including full support for the SNMPv3 cryptographic 2100 mechanisms "for authentication and privacy". 2102 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2103 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2104 enable cryptographic security. It is then a customer/operator 2105 responsibility to ensure that the SNMP entity giving access to an 2106 instance of this MIB module, is properly configured to give access to 2107 the objects only to those principals "users" that have legitimate 2108 rights to indeed GET or SET "change/create/delete" them. 2110 10. Acknowledgments 2112 This document extends [TEMIB]. The authors would like to express 2113 their gratitude to all those who worked on that earlier MIB document. 2114 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 2115 contributions during an early implementation, and to Baktha 2116 Muralidharan for his review. 2118 Special thanks to Joan Cucchiara and Len Nieman for their help with 2119 compilation issues. 2121 11. References 2123 11.1. Normative References 2125 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2126 Requirement Levels", BCP 14, RFC 2119, March 1997. 2128 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2129 Case, J., Rose, M., and S. Waldbusser, "Structure 2130 of Management Information Version 2 (SMIv2)", STD 2131 58, RFC 2578, April 1999. 2133 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2134 Case, J., Rose, M., and S. Waldbusser, "Textual 2135 Conventions for SMIv2", STD 58, RFC 2579, April 2136 1999. 2138 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2139 Case, J., Rose, M., and S. Waldbusser, "Conformance 2140 Statements for SMIv2", STD 58, RFC 2580, April 2141 1999. 2143 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2144 "Multiprotocol Label Switching Architecture", RFC 2145 3031, January 2001. 2147 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 2148 Srinivasan, V., and G. Swallow, "RSVP-TE: 2149 Extensions to RSVP for LSP Tunnels", RFC 3209, 2150 December 2001. 2152 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 2153 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 2154 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 2155 T., Feldman, N., Fredette, A., Girish, M., Gray, 2156 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 2157 A., and P. Vaananen, "Constraint-Based LSP Setup 2158 using LDP", RFC 3212, December 2001. 2160 [RFC3291] Daniele, M., Haberman, B., Routhier, S., 2161 Schoenwaelder, J., and Braunschweig, TU, "Textual 2162 Conventions for Internet Network Addresses", 2163 RFC3291, May 2002 2165 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 2166 Label Switching (GMPLS) Signaling Functional 2167 Description", RFC 3471, January 2003. 2169 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 2170 "Generalized MPLS Signaling - CR-LDP Extensions", 2171 RFC 3472, January 2003. 2173 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 2174 RSVP-TE Extensions", RFC 3473, January 2003. 2176 [RFC3477] Kompella, K. and Rekhter, Y., "Signalling Unnumbered 2177 Links in RSVP-TE", RFC 3477, January 2003. 2179 [RFC3480] Kompella, K., Rekhter, Y. and Kullberg, A., 2180 "Signalling Unnumbered Links in CR-LDP", RFC 3480, 2181 February 2003. 2183 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 2184 Label Switching (GMPLS) Architecture", 2185 draft-many-gmpls-architecture-07.txt, May 2186 2003, work in progress. 2188 [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., A., Farrel, A., Hall, 2189 T., and Harrison, E., "Generalized Multiprotocol 2190 Label Switching (GMPLS) Label Switching Router 2191 (LSR) Management Information Base", draft-ietf- 2192 ccamp-gmpls-lsr-mib-05.txt, June 2004, work in 2193 progress. 2195 [GMPLSOSPF] Kompella, K., et al., "OSPF Extensions in Support 2196 of Generalized MPLS", draft-ietf-ccamp-ospf-gmpls- 2197 extensions-12.txt, October 2003, work in progress. 2199 [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 2200 and Harrison, E., "Definitions of Textual 2201 Conventions for Multiprotocol Label Switching 2202 (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib- 2203 05.txt, June 2004, work in progress. 2205 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, 2206 "Multiprotocol Label Switching (MPLS) Label 2207 Switching Router (LSR) Management Information 2208 Base", draft-ietf-mpls-lsr-mib-14.txt, November 2209 2003, work in progress. 2211 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of 2212 Textual Conventions for Multiprotocol Label 2213 Switching (MPLS) Management", 2214 draft-ietf-mpls-tc-mib-10.txt, November 2003, work 2215 in progress. 2217 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 2218 "Multiprotocol Label Switching (MPLS) Traffic 2219 Engineering Management Information Base", 2220 draft-ietf-mpls-te-mib-14.txt, November 2003, 2221 work in progress. 2223 11.2. Informational References 2225 [RFC2026] S. Bradner, "The Internet Standards Process -- 2226 Revision 3", RFC 2026, October 1996. 2228 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 2229 Applications", RFC 3413, December 2002. 2231 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2232 "Introduction and Applicability Statements for 2233 Internet-Standard Management Framework", RFC 3410, 2234 December 2002. 2236 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2237 Architecture for Describing Simple Network 2238 Management Protocol (SNMP) Management Frameworks", 2239 RFC 3411, December 2002. 2241 [GMPLS-G709] D. Papadimitriou (Editor), "Generalized MPLS 2242 Signalling Extensions for G.709 Optical Transport 2243 Networks Control", draft-ietf-ccamp-gmpls-g709- 2244 06.txt, January 2004, work in progress. 2246 12. Authors' Addresses 2248 Thomas D. Nadeau 2249 Cisco Systems, Inc. 2250 300 Apollo Drive 2251 Chelmsford, MA 01824 2252 Phone: +1-978-244-3051 2253 Email: tnadeau@cisco.com 2255 Cheenu Srinivasan 2256 Bloomberg L.P. 2257 499 Park Ave., 2258 New York, NY 10022 2259 Phone: +1-212-893-3682 2260 Email: cheenu@bloomberg.net 2262 Adrian Farrel 2263 Old Dog Consulting 2264 Phone: +44-(0)-1978-860944 2265 Email: adrian@olddog.co.uk 2267 Tim Hall 2268 Data Connection Ltd. 2269 100 Church Street 2270 Enfield, Middlesex 2271 EN2 6BQ, UK 2272 Phone: +44 20 8366 1177 2273 Email: tim.hall@dataconnection.com 2275 Ed Harrison 2276 Data Connection Ltd. 2277 100 Church Street 2278 Enfield, Middlesex 2279 EN2 6BQ, UK 2280 Phone: +44 20 8366 1177 2281 Email: ed.harrison@dataconnection.com 2283 13. Intellectual Property Considerations 2285 The IETF takes no position regarding the validity or scope of any 2286 Intellectual Property Rights or other rights that might be claimed to 2287 pertain to the implementation or use of the technology described in 2288 this document or the extent to which any license under such rights 2289 might or might not be available; nor does it represent that it has 2290 made any independent effort to identify any such rights. Information 2291 on the procedures with respect to rights in RFC documents can be 2292 found in BCP 78 and BCP 79. 2294 Copies of IPR disclosures made to the IETF Secretariat and any 2295 assurances of licenses to be made available, or the result of an 2296 attempt made to obtain a general license or permission for the use of 2297 such proprietary rights by implementers or users of this 2298 specification can be obtained from the IETF on-line IPR repository at 2299 http://www.ietf.org/ipr. 2301 The IETF invites any interested party to bring to its attention any 2302 copyrights, patents or patent applications, or other proprietary 2303 rights that may cover technology that may be required to implement 2304 this standard. Please address the information to the IETF at 2305 ietf-ipr@ietf.org. 2307 13.1. IPR Disclosure Acknowledgement 2309 By submitting this Internet-Draft, I certify that any applicable 2310 patent or other IPR claims of which I am aware have been disclosed, 2311 and any of which I become aware will be disclosed, in accordance with 2312 RFC 3668. 2314 14. Full Copyright Statement 2316 Copyright (C) The Internet Society (2004). This document is subject 2317 to the rights, licenses and restrictions contained in BCP 78, and 2318 except as set forth therein, the authors retain all their rights. 2320 This document and the information contained herein are provided on an 2321 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2322 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2323 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2324 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2325 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2326 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2328 15. Changes and Pending Work 2330 This section to be removed before the draft progresses to RFC. 2332 15.1. Pending Work 2334 The following work items have been identified for this draft. They 2335 will be addressed in a future version. 2337 - Expand conformance statements to give one for monitoring only, 2338 and one for monitoring and control. 2339 - Resolve conformance statement from gmplsTunnelManualGroup. 2341 15.1. Changes from version 4 to version 5 2343 - New IPR and copyright boiler plate. 2344 - Correct typo in name of gmplsTunnelExtraParamsPtr 2345 - Add to list of encoding types and GPids for G.709 2346 - Add G.709 reference 2348 15.2. Changes from version 3 to version 4 2350 - Provide a way to configure additional tunnel parameters such as 2351 tunnel resources through an arbitrary row pointer. 2352 - Update references. 2353 - Change reporting IP addresses to use InetAddress syntax 2354 - Add support for IF_ID error reporting. 2355 - Add a new notification, gmplsTunnelDown, containing cause 2356 information. 2357 - Clarify relationship to the gmplsLabelTable. 2358 - Update descriptive text. 2359 - Bring usage of labels in line with latest [LSRMIB]. 2361 15.3. Changes from version 2 to version 3 2363 - Work on basic compilation issues. 2364 - Resolve defaults for objects with syntax BITS. 2365 - Update references. 2366 - Clarify which objects can be modified when rowStatus and 2367 adminStatus are set to active. 2368 - Control and reporting of upstream and downstream Notify 2369 Recipients. 2370 - Add support for control and reporting of GMPLS Administrative 2371 Status object. 2372 - Update examples.