idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2507. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2480. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2487. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2493. ** 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 : ---------------------------------------------------------------------------- == 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 2005) is 6880 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 2338, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 2343, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 2351, but no explicit reference was found in the text == Unused Reference: 'RFC3477' is defined on line 2362, but no explicit reference was found in the text == Unused Reference: 'RFC3480' is defined on line 2365, but no explicit reference was found in the text == Unused Reference: 'RFC4001' is defined on line 2387, but no explicit reference was found in the text == Unused Reference: 'GMPLSOSPF' is defined on line 2398, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 2410, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 2417, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 2425, but no explicit reference was found in the text == Unused Reference: 'GMPLS-G709' is defined on line 2430, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 3 errors (**), 0 flaws (~~), 15 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Working Group Thomas D. Nadeau, Ed. 2 Internet Draft Cisco Systems, Inc. 3 Proposed Status: Standards Track 4 Expires: December 2005 Adrian Farrel, Ed. 5 Old Dog Consulting 7 June 2005 9 Generalized Multiprotocol Label Switching (GMPLS) Traffic 10 Engineering Management Information Base 12 draft-ietf-ccamp-gmpls-te-mib-09.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects for Generalized 42 Multiprotocol Label Switching (GMPLS) based traffic engineering. 44 Table of Contents 46 1. Introduction ........................................... 2 47 1.1. Migration Strategy ................................... 3 48 2. Terminology ............................................ 3 49 3. The SNMP Management Framework .......................... 3 50 4. Outline ................................................ 4 51 4.1. Summary of GMPLS Traffic Engineering MIB Module ...... 4 52 5. Brief Description of GMPLS TE MIB Objects .............. 5 53 5.1. gmplsTunnelTable ..................................... 5 54 5.2. gmplsTunnelHopTable .................................. 5 55 5.3. gmplsTunnelARHopTable ................................ 5 56 5.4. gmplsTunnelCHopTable ................................. 5 57 5.5. gmplsTunnelErrorTable ................................ 6 58 5.6. gmplsTunnelReversePerfTable .......................... 6 59 6. Cross-referencing to the mplsLabelTable ................ 6 60 7. Example of GMPLS Tunnel Setup .......................... 7 61 8. GMPLS Traffic Engineering MIB Module .... ............. 10 62 9. Security Considerations ............................... 43 63 10. Acknowledgments ...................................... 44 64 11. IANA Considerations .................................. 44 65 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 44 66 11.2. Dependence on IANA MIB Modules ..................... 44 67 11.2.1. IANA-GMPLS-MIB Definition ........................ 45 68 12. References ........................................... 51 69 12.1. Normative Refenerces ............................... 51 70 12.2. Informational References ........................... 52 71 13. Authors' Addresses ................................... 53 72 14. Intellectual Property Notice ......................... 54 73 15. Full Copyright Statement ............................. 54 75 1. Introduction 77 This memo defines a portion of the Management Information Base (MIB) 78 for use with network management protocols in the Internet community. 79 In particular, it describes managed objects for modeling 80 Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based 81 traffic engineering. The tables and objects defined in this document 82 extend those defined in the equivalent document for MPLS traffic 83 engineering [RFC3812], and management of GMPLS traffic engineering is 84 built on management of MPLS traffic engineering. 86 This MIB module should be used in conjunction with the companion 87 document [GMPLSLSRMIB] for GMPLS based traffic engineering 88 configuration and management. 90 Comments should be made direct to the CCAMP mailing list at 91 ccamp@ops.ietf.org. 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in BCP 14, RFC 2119, 96 reference [RFC2119]. 98 1.1. Migration Strategy 100 This MIB module extends the traffic engineering MIB module defined 101 for use with MPLS [RFC3812]. It provides additions for support of 102 GMPLS tunnels. 104 The companion document for modeling and managing GMPLS based LSRs 105 [GMPLSLSRMIB] extends MPLS LSR MIB [RFC3813] with the same 106 intentions. 108 Textual conventions and OBJECT-IDENTIFIERS are defined in [RFC3811] 109 and [GMPLSTCMIB]. 111 2. Terminology 113 This document uses terminology from the MPLS architecture document 114 [RFC3031], from the GMPLS architecture document [RFC3945], and from 115 the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used 116 terms are described next. 118 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 119 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 120 LSRs, each segment being associated with one GMPLS enabled interface. 121 These are also referred to as tunnel segments. 123 Additionally, at an intermediate LSR, we model a connection as 124 consisting of one or more in-segments and/or one or more 125 out-segments. The binding or interconnection between in-segments and 126 out-segments in performed using a cross-connect. 128 These segment and cross-connect objects are defined in the MPLS Label 129 Switch Router MIB [RFC3813], but see also the GMPLS Label Switch 130 Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these 131 objects. 133 3. The SNMP Management Framework 135 For a detailed overview of the documents that describe the current 136 Internet-Standard Management Framework, please refer to section 7 of 137 RFC 3410 [RFC3410]. 139 Managed objects are accessed via a virtual information store, termed 140 the Management Information Base or MIB. MIB objects are generally 141 accessed through the Simple Network Management Protocol (SNMP). 142 Objects in the MIB are defined using the mechanisms defined in the 143 Structure of Management Information (SMI). This memo specifies a MIB 144 module that is compliant to the SMIv2, which is described in STD 58, 145 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 146 [RFC2580]. 148 4. Outline 150 Support for GMPLS traffic-engineered tunnels requires the following 151 configuration. 153 - Setting up tunnels with appropriate MPLS configuration parameters 154 using [RFC3812]. 155 - Extending the tunnels with GMPLS configuration parameters. 156 - Configuring tunnel loose and strict source routed hops. 158 These actions may need to be accompanied with corresponding actions 159 using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel 160 segments, if this is done manually. Also, the in-segment and 161 out-segment performance tables, mplsInSegmentPerfTable and 162 mplsOutSegmentPerfTable [RFC3813], should be used to determine 163 performance of the tunnels and tunnel segments although it should be 164 noted that those tables may not be appropriate for measuring 165 performance on some types of GMPLS links. 167 4.1. Summary of GMPLS Traffic Engineering MIB Module 169 The MIB objects for performing the actions listed above that cannot 170 be performed solely using the MIB objects defined in [RFC3812] 171 consist of the following tables. 173 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 174 tunnel configuration parameters. 175 - Tunnel specified, actual, and computed hop tables 176 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 177 gmplsTunnelCHopTable) for providing additional configuration of 178 strict and loose source routed tunnel hops. 179 - Performance and error reporting tables (gmplsTunnelReversePerfTable 180 and gmplsTunnelErrorTable). 182 These tables are described in the subsequent sections. 184 Additionally, this MIB module contains a new Notification. 186 - The GMPLS Tunnel Down Notification (gmplsTunnelDown) is intended to 187 be used in place of the mplsTunnelDown Notification defined in 188 [RFC3812]. As well as indicating that a tunnel has transitioned to 189 operational down state, this new Notificaiton indicates the cause 190 of the failure. 192 5. Brief Description of GMPLS TE MIB Objects 194 The objects described in this section support the functionality 195 described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables 196 support both manually configured and signaled tunnels. 198 5.1. gmplsTunnelTable 200 The gmplsTunnelTable extends the MPLS traffic engineering MIB module 201 to allow GMPLS tunnels to be created between an LSR and a remote 202 endpoint, and existing GMPLS tunnels to be reconfigured or removed. 204 Note that we only support point-to-point tunnel segments, although 205 multi-point-to-point and point-to-multi-point connections are 206 supported by an LSR acting as a cross-connect. 208 Each tunnel can thus have one out-segment originating at an LSR 209 and/or one in-segment terminating at that LSR. 211 Three objects within this table utilize enumerations in order to map 212 to enumerations that are used in GMPLS signaling. In order to protect 213 this MIB module from changes (in particular, extensions) to the range 214 of enumerations supported by the signaling protocols, these MIB 215 objects use Textual Conventions defined by IANA. For further details, 216 see the IANA Considerations section of this document. 218 5.2. gmplsTunnelHopTable 220 The gmplsTunnelHopTable is used to indicate additional parameters for 221 the hops, strict or loose, of a GMPLS tunnel defined in 222 gmplsTunnelTable, when it is established using signaling. Multiple 223 tunnels may share hops by pointing to the same entry in this table. 225 5.3. gmplsTunnelARHopTable 227 The gmplsTunnelARHopTable is used to indicate the actual hops 228 traversed by a tunnel as reported by the signaling protocol after the 229 tunnel is setup. The support of this table is optional since not all 230 GMPLS signaling protocols support this feature. 232 5.4. gmplsTunnelCHoptable 234 The gmplsTunnelCHopTable lists the actual hops computed by a 235 constraint-based routing algorithm based on the gmplsTunnelHopTable. 236 The support of this table is optional since not all implementations 237 support computation of hop lists using a constraint-based routing 238 protocol. 240 5.5. gmplsTunnelErrorTable 242 The gmplsTunnelErrorTable provides access to information about the 243 last error that occurred on each tunnel known about by the MIB. It 244 indicates the nature of the error, when and how it was reported and 245 can give recovery advice through a display string. 247 5.6. gmplsTunnelReversePerfTable 249 gmplsTunnelReversePerfTable provides additional counters to measure 250 the performance of bidirectional GMPLS tunnels in which packets are 251 visible. It supplements the counters in mplsTunnelPerfTable and 252 augments gmplsTunnelTable. 254 Note that not all counters may be appropriate or available for some 255 types of tunnel. 257 6. Cross-referencing to the gmplsLabelTable 259 The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and 260 provides a way to model labels in a GMPLS system where labels might 261 not be simple 32 bit integers. 263 The hop tables in this document (gmplsHopTable, gmplsCHopTable and 264 gmplsARHopTable) and the segment tables in the [RFC3813] 265 (mplsInSegmentTable and mplsOutSegmentTable) contain objects with 266 syntax MplsLabel. 268 MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable 269 of representing any MPLS label and most GMPLS labels. However, some 270 GMPLS labels are larger than 32 bits and may be of arbitrary length. 271 Further, some labels that may be safely encoded in 32 bits are 272 constructed from multiple sub-fields. Additionally, some GMPLS 273 technologies support the concatenation of individual labels to 274 represent a data flow carried as multiple sub-flows. 276 These GMPLS cases require that something other than a simple 32-bit 277 integer is made available to represent the labels. This is achieved 278 through the gmplsLabelTable contained in [GMPLSLSRMIB]. 280 The tables in this document and [RFC3813] that include objects with 281 syntax MplsLabel also include companion objects that are row 282 pointers. If the row pointer is set to zeroDotZero (0.0) then object 283 of syntax MplsLabel contains the label encoded as a 32-bit integer. 284 But otherwise the row pointer indicates a row in another MIB table 285 that includes the label. In these cases, the row pointer may indicate 286 a row in the gmplsLabelTable. 288 This provides both a good way to support legacy systems that 289 implement the previous version of this MIB module [RFC3812], and a 290 significant simplification in GMPLS systems that are limited to a 291 single, simple label type. 293 Note that gmplsLabelTable supports concatenated labels through the 294 use of a label sub-index (gmplsLabelSubindex). 296 7. Example of GMPLS Tunnel Setup 298 This section contains an example of which MIB objects should be 299 modified to create a GMPLS tunnel. This example shows a best effort, 300 loosely routed, bidirectional traffic engineered tunnel, which spans 301 two hops of a simple network, uses Generalized Label requests with 302 Lambda encoding, has label recording and shared link layer 303 protection. Note that these objects should be created on the 304 "head-end" LSR. 306 First in the mplsTunnelTable: 307 { 308 mplsTunnelIndex = 1, 309 mplsTunnelInstance = 1, 310 mplsTunnelIngressLSRId = 123.123.125.1, 311 mplsTunnelEgressLSRId = 123.123.126.1, 312 mplsTunnelName = "My first tunnel", 313 mplsTunnelDescr = "Here to there and back again", 314 mplsTunnelIsIf = true (1), 315 mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, 316 mplsTunnelSignallingProto = none (1), 317 mplsTunnelSetupPrio = 0, 318 mplsTunnelHoldingPrio = 0, 319 mplsTunnelSessionAttributes = recordRoute (4), 320 mplsTunnelOwner = snmp (2), 321 mplsTunnelLocalProtectInUse = false (2), 322 mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, 323 mplsTunnelInstancePriority = 1, 324 mplsTunnelHopTableIndex = 1, 326 mplsTunnelPrimaryInstance = 0, 327 mplsTunnelIncludeAnyAffinity = 0, 328 mplsTunnelIncludeAllAffinity = 0, 329 mplsTunnelExcludeAnyAffinity = 0, 330 mplsTunnelPathInUse = 1, 331 mplsTunnelRole = head(1), 332 mplsTunnelRowStatus = createAndWait (5), 333 } 335 In gmplsTunnelTable(1,1,123.123.125.1,123.123.126.1): 336 { 337 gmplsTunnelUnnumIf = true (1), 338 gmplsTunnelAttributes = labelRecordingRequired (1), 339 gmplsTunnelLSPEncoding = tunnelLspLambda, 340 gmplsTunnelSwitchingType = lsc, 341 gmplsTunnelLinkProtection = shared (2), 342 gmplsTunnelGPid = lambda, 343 gmplsTunnelSecondary = false (2), 344 gmplsTunnelDirection = bidirectional (1) 345 gmplsTunnelPathComp = explicit(2), 346 gmplsTunnelUpNotRecip = 0x7B7B7D01, 347 gmplsTunnelDownNotRecip = 0x00000000, 348 gmplsTunnelAdminStatusFlags = 0, 349 gmplsTunnelExtraParamsPtr = 0.0 350 } 352 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 353 gmplsTunnelHopTable are created and activated at this time. 355 In mplsTunnelResourceTable: 356 { 357 mplsTunnelResourceIndex = 6, 358 mplsTunnelResourceMaxRate = 0, 359 mplsTunnelResourceMeanRate = 0, 360 mplsTunnelResourceMaxBurstSize = 0, 361 mplsTunnelResourceRowStatus = createAndGo (4) 362 } 364 The next two instances of mplsTunnelHopEntry are used to denote the 365 hops this tunnel will take across the network. 367 The following denotes the beginning of the network, or the first hop. 368 We have used the fictitious LSR identified by "123.123.125.1" as our 369 example head-end router. 371 In mplsTunnelHopTable: 372 { 373 mplsTunnelHopListIndex = 1, 374 mplsTunnelPathOptionIndex = 1, 375 mplsTunnelHopIndex = 1, 376 mplsTunnelHopAddrType = ipV4 (1), 377 mplsTunnelHopIpv4Addr = 123.123.125.1, 378 mplsTunnelHopIpv4PrefixLen = 9, 379 mplsTunnelHopType = strict (1), 380 mplsTunnelHopRowStatus = createAndWait (5), 381 } 383 The following denotes the end of the network, or the last hop in our 384 example. We have used the fictitious LSR identified by 385 "123.123.126.1" as our end router. 387 In mplsTunnelHopTable: 388 { 389 mplsTunnelHopListIndex = 1, 390 mplsTunnelPathOptionIndex = 1, 391 mplsTunnelHopIndex = 2, 392 mplsTunnelHopAddrType = ipV4 (1), 393 mplsTunnelHopIpv4Addr = 123.123.126.1, 394 mplsTunnelHopIpv4PrefixLen = 9, 395 mplsTunnelHopType = loose (2), 396 mplsTunnelHopRowStatus = createAndGo (4) 397 } 399 Now an associated entry in the gmplsTunnelHopTable is created to 400 provide additional GMPLS hop configuration indicating that the first 401 hop is an unnumbered link using explicit forward and reverse labels. 402 An entry in the gmplsLabelTable is created first to include the 403 explicit label. 405 In gmplsLabelTable: 406 { 407 gmplsLabelInterface = 2, 408 gmplsLabelIndex = 1, 409 gmplsLabelSubindex = 0, 410 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 411 gmplsLabelFreeform = 0xFEDCBA9876543210 412 gmplsLabelRowStatus = createAndGo(4) 413 } 415 In gmplsTunnelHopTable(1,1,1): 416 { 417 gmplsTunnelHopLabelStatuses = forwardPresent(0) 418 +reversePresent(1), 419 gmplsTunnelHopExpLabelPtr = gmplsLabelTable (2, 1, 0) 420 gmplsTunnelHopExpRvrsLabelPtr = gmplsLabelTable (2, 1, 0) 421 } 423 The first hop is now activated: 425 In mplsTunnelHopTable(1,1,1): 426 { 427 mplsTunnelHopRowStatus = active (1) 428 } 430 No gmplsTunnelHopEntry is created for the second hop as it contains 431 no special GMPLS features. 433 Finally the mplsTunnelEntry is activated: 435 In mplsTunnelTable(1,1,123.123.125.1,123.123.126.1) 436 { 437 mplsTunnelRowStatus = active(1) 438 } 440 8. GMPLS Traffic Engineering MIB Module 442 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 444 IMPORTS 445 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 446 Unsigned32, Counter32, 447 Counter64, IpAddress, zeroDotZero 448 FROM SNMPv2-SMI -- RFC2578 449 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 450 FROM SNMPv2-CONF -- RFC2580 451 TruthValue, TimeStamp, DisplayString, RowPointer 452 FROM SNMPv2-TC -- RFC2579 453 InetAddress, InetAddressType 454 FROM INET-ADDRESS-MIB -- RFC4001 455 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 456 mplsTunnelEgressLSRId, mplsTunnelHopListIndex, 457 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, 458 mplsTunnelARHopListIndex, mplsTunnelARHopIndex, 459 mplsTunnelCHopListIndex, mplsTunnelCHopIndex, 460 mplsTunnelEntry, 461 mplsTunnelAdminStatus, mplsTunnelOperStatus 462 FROM MPLS-TE-STD-MIB -- RFC3812 463 mplsStdMIB 464 FROM MPLS-TC-STD-MIB -- RFC3811 465 IANAGmplsLSPEncoding, IANAGmplsSwitchingType, IANAGmplsGPid, 466 IANAGmplsAdminStatusFlags 467 FROM IANA-GMPLS-MIB 468 ; 470 gmplsTeStdMIB MODULE-IDENTITY 471 LAST-UPDATED 472 "200505200001Z" -- 20 May 2005 00:00:01 GMT 473 ORGANIZATION 474 "Common Control And Measurement Plane (CCAMP) Working Group" 475 CONTACT-INFO 476 " Thomas D. Nadeau 477 Cisco Systems, Inc. 478 Email: tnadeau@cisco.com 480 Adrian Farrel 481 Old Dog Consulting 482 Email: adrian@olddog.co.uk 484 Comments about this document should be emailed direct to the 485 CCAMP working group mailing list at ccamp@ops.ietf.org" 487 DESCRIPTION 488 "Copyright (C) The Internet Society (2005). The 489 initial version of this MIB module was published 490 in RFC xxxx. For full legal notices see the RFC 491 itself or see: http://www.ietf.org/copyrights/ianamib.html 493 This MIB module contains managed object definitions 494 for GMPLS Traffic Engineering (TE) as defined in: 495 1. Generalized Multi-Protocol Label Switching (GMPLS) 496 Signaling Functional Description, Berger, L. (Editor), 497 RFC 3471, January 2003. 498 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 499 L. (Editor), RFC 3473, January 2003." 501 -- Revision history. 502 REVISION 503 "200505200001Z" -- 20 May 2005 00:00:01 GMT 504 DESCRIPTION 505 -- RFC Editor: Please see the IANA Considerations Section. 506 -- RFC-editor please fill in XXXX 507 "Initial version issued as part of RFC XXXX." 508 ::= { mplsStdMIB XXX } 510 -- Top level components of this MIB. 512 -- Notifications 514 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 516 -- tables, scalars 518 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } 519 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } 521 -- conformance 523 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } 525 -- GMPLS Tunnel scalars. 527 gmplsTunnelsConfigured OBJECT-TYPE 528 SYNTAX Unsigned32 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The number of GMPLS tunnels configured on this device. A GMPLS 533 tunnel is considered configured if an entry for the tunnel 534 exists in the gmplsTunnelTable and the associated 535 mplsTunnelRowStatus is active(1)." 536 ::= { gmplsTeScalars 1 } 537 gmplsTunnelsActive OBJECT-TYPE 538 SYNTAX Unsigned32 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "The number of GMPLS tunnels active on this device. A GMPLS 543 tunnel is considered active if there is an entry in the 544 gmplsTunnelTable and the associated mplsTunnelOperStatus for the 545 tunnel is up(1)." 546 ::= { gmplsTeScalars 2 } 548 -- End of GMPLS Tunnel scalars. 550 -- GMPLS tunnel table. 552 gmplsTunnelTable OBJECT-TYPE 553 SYNTAX SEQUENCE OF GmplsTunnelEntry 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "The gmplsTunnelTable 'extends' the mplsTunnelTable. It allows 558 GMPLS tunnels to be created between an LSR and a remote 559 endpoint, and existing tunnels to be reconfigured or removed. 561 Note that only point-to-point tunnel segments are supported, 562 although multi-point-to-point and point-to-multi-point 563 connections are supported by an LSR acting as a cross-connect. 564 Each tunnel can thus have one out-segment originating at this 565 LSR and/or one in-segment terminating at this LSR. 567 The row status of an entry in this table is controlled by 568 mplsTunnelRowStatus in the corresponding entry in 569 mplsTunnelTable. That is, it is not permitted to create a row in 570 this table, nor to modify an existing row, when the 571 corresponding mplsTunnelRowStatus has value active(1). 573 The exception to this rule is the gmplsTunnelAdminStatusFlags 574 object, which can be modified whilst the tunnel is active." 575 ::= { 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 corresponding 582 entry in the mplsTunnelTable represents a GMPLS tunnel. 584 An entry can be created by a network administrator or by an SNMP 585 agent as instructed by a signaling protocol." 586 INDEX { 587 mplsTunnelIndex, 588 mplsTunnelInstance, 589 mplsTunnelIngressLSRId, 590 mplsTunnelEgressLSRId 591 } 592 ::= { gmplsTunnelTable 1 } 594 GmplsTunnelEntry ::= SEQUENCE { 595 gmplsTunnelUnnumIf TruthValue, 596 gmplsTunnelAttributes BITS, 597 gmplsTunnelLSPEncoding IANAGmplsLSPEncoding, 598 gmplsTunnelSwitchingType IANAGmplsSwitchingType, 599 gmplsTunnelLinkProtection BITS, 600 gmplsTunnelGPid IANAGmplsGPid, 601 gmplsTunnelSecondary TruthValue, 602 gmplsTunnelDirection INTEGER, 603 gmplsTunnelPathComp INTEGER, 604 gmplsTunnelUpNotRecip IpAddress, 605 gmplsTunnelDownNotRecip IpAddress, 606 gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusFlags, 607 gmplsTunnelExtraParamsPtr RowPointer 608 } 609 gmplsTunnelUnnumIf OBJECT-TYPE 610 SYNTAX TruthValue 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "Denotes whether or not this tunnel corresponds to an unnumbered 615 interface represented in the interfaces group table. 617 This object is only used if mplsTunnelIsIf is set to 'true'. 619 If both this object and the mplsTunnelIsIf object are set to 620 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID 621 object to the outgoing Path message. 623 This object contains information that is only used by the 624 terminating LSR." 625 REFERENCE 626 "Signalling Unnumbered Links in RSVP-TE, Kompella, K. 627 and Rekhter, Y., RFC 3477, January 2003." 628 DEFVAL { false } 629 ::= { gmplsTunnelEntry 1 } 631 gmplsTunnelAttributes OBJECT-TYPE 632 SYNTAX BITS { 633 labelRecordingDesired (0) 634 } 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "This bitmask indicates optional parameters for this tunnel. 639 These bits should be taken in addition to those defined in 640 mplsTunnelSessionAttributes in order to determine the full set 641 of options to be signaled (for example SESSION_ATTRIBUTES flags 642 in RSVP-TE). The following describes these bitfields: 644 labelRecordingDesired 645 This flag indicates that label information should be included 646 when doing a route record. This bit is not valid unless the 647 recordRoute bit is set." 648 REFERENCE 649 "RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., 650 RFC 3209, December 2001." 651 DEFVAL { { } } 652 ::= { gmplsTunnelEntry 2 } 653 gmplsTunnelLSPEncoding OBJECT-TYPE 654 SYNTAX IANAGmplsLSPEncoding 655 MAX-ACCESS read-create 656 STATUS current 657 DESCRIPTION 658 "This object indicates the encoding of the LSP being requested. 660 A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is 661 not in use. Some objects in this MIB module may be of use for 662 MPLS signaling extensions that do not use GMPLS signaling. By 663 setting this object to 'tunnelLspNotGmpls', an application may 664 indicate that only those objects meaningful in MPLS should be 665 examined. 667 The values to use are defined in the textual convention 668 IANAGmplsLSPEncoding found in the IANA-GMPLS-MIB MIB module." 669 DEFVAL { tunnelLspNotGmpls } 670 ::= { gmplsTunnelEntry 3 } 672 gmplsTunnelSwitchingType OBJECT-TYPE 673 SYNTAX IANAGmplsSwitchingType 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "Indicates the type of switching that should be performed on 678 a particular link. This field is needed for links that 679 advertise more than one type of switching capability. 681 The values to use are defined in the textual convention 682 IANAGmplsSwitchingType found in the IANA-GMPLS-MIB MIB module. 684 This object is only meaningful if gmplsTunnelLSPEncoding is not 685 set to 'tunnelLspNotGmpls'." 686 DEFVAL { unknown } 687 ::= { gmplsTunnelEntry 4 } 688 gmplsTunnelLinkProtection OBJECT-TYPE 689 SYNTAX BITS { 690 extraTraffic(0), 691 unprotected(1), 692 shared (2), 693 dedicatedOneToOne (3), 694 dedicatedOnePlusOne(4), 695 enhanced(5) 696 } 697 MAX-ACCESS read-create 698 STATUS current 699 DESCRIPTION 700 "This bitmask indicates the level of link protection required. A 701 value of zero (no bits set) indicates that any protection may be 702 used. The following describes these bitfields: 704 extraTraffic 705 Indicates that the LSP should use links that are protecting 706 other (primary) traffic. Such LSPs may be preempted when the 707 links carrying the (primary) traffic being protected fail. 709 unprotected 710 Indicates that the LSP should not use any link layer 711 protection. 713 shared 714 Indicates that a shared link layer protection scheme, such as 715 1:N protection, should be used to support the LSP. 717 dedicatedOneToOne 718 Indicates that a dedicated link layer protection scheme, 719 i.e., 1:1 protection, should be used to support the LSP. 721 dedicatedOnePlusOne 722 Indicates that a dedicated link layer protection scheme, 723 i.e., 1+1 protection, should be used to support the LSP. 725 enhanced 726 Indicates that a protection scheme that is more reliable than 727 Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. 729 This object is only meaningful if gmplsTunnelLSPEncoding is 730 not set to 'tunnelLspNotGmpls'." 731 REFERENCE 732 "Berger, L., et al., Generalized Multi-Protocol 733 Label Switching (GMPLS) Signaling Functional 734 Description, RFC 3471, January 2003." 735 DEFVAL { { } } 736 ::= { gmplsTunnelEntry 5 } 737 gmplsTunnelGPid OBJECT-TYPE 738 SYNTAX IANAGmplsGPid 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "This object indicates the payload carried by the LSP. It is only 743 required when GMPLS will be used for this LSP. 745 The values to use are defined in the textual convention 746 IANAGmplsGPid found in the IANA-GMPLS-MIB MIB module. 748 This object is only meaningful if gmplsTunnelLSPEncoding is not 749 set to 'tunnelLspNotGmpls'." 750 DEFVAL { unknown } 751 ::= { gmplsTunnelEntry 6 } 753 gmplsTunnelSecondary OBJECT-TYPE 754 SYNTAX TruthValue 755 MAX-ACCESS read-create 756 STATUS current 757 DESCRIPTION 758 "Indicates that the requested LSP is a secondary LSP. 760 This object is only meaningful if gmplsTunnelLSPEncoding is not 761 set to 'tunnelLspNotGmpls'." 762 REFERENCE 763 "Berger, L., et al., Generalized Multi-Protocol 764 Label Switching (GMPLS) Signaling Functional 765 Description, RFC 3471, January 2003." 766 DEFVAL { false } 767 ::= { gmplsTunnelEntry 7 } 769 gmplsTunnelDirection OBJECT-TYPE 770 SYNTAX INTEGER { 771 forward (0), 772 bidirectional (1) 773 } 774 MAX-ACCESS read-create 775 STATUS current 776 DESCRIPTION 777 "Whether this tunnel carries forward data only (is 778 unidirectional) or is bidirectional. 780 Values of this object other than 'forward' are meaningful 781 only if gmplsTunnelLSPEncoding is not set to 782 'tunnelLspNotGmpls'." 783 DEFVAL { forward } 784 ::= { gmplsTunnelEntry 8 } 785 gmplsTunnelPathComp OBJECT-TYPE 786 SYNTAX INTEGER { 787 dynamicFull(1), -- CSPF fully computed 788 explicit(2), -- fully specified path 789 dynamicPartial(3) -- CSPF partially computed 790 } 791 MAX-ACCESS read-create 792 STATUS current 793 DESCRIPTION 794 "This value instructs the source node on how to perform path 795 computation on the explicit route specified by the associated 796 entries in the gmplsTunnelHopTable. 798 dynamicFull 799 The user specifies at least the source and 800 destination of the path and expects that the CSPF 801 will calculate the remainder of the path. 803 explicit 804 The user specifies the entire path for the tunnel to 805 take. This path may contain strict or loose hops. 806 Evaluation of the explicit route will be performed 807 hop by hop through the network. 809 dynamicPartial 810 The user specifies at least the source and 811 destination of the path and expects that the CSPF 812 will calculate the remainder of the path. The path 813 computed by CSPF is allowed to be only partially 814 computed allowing the remainder of the path to be 815 filled in across the network. 817 This object deprecates mplsTunnelHopEntryPathComp." 818 DEFVAL { dynamicFull } 819 ::= { gmplsTunnelEntry 9 } 821 gmplsTunnelUpNotRecip OBJECT-TYPE 822 SYNTAX IpAddress 823 MAX-ACCESS read-create 824 STATUS current 825 DESCRIPTION 826 "Indicates the address of the upstream recipient for Notify 827 messages relating to this tunnel. This object is only valid when 828 signaling a tunnel using RSVP. It is also not valid at the tail 829 end of the tunnel. If set to 0, no Notify Request object will be 830 included in outgoing Path messages." 831 REFERENCE 832 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 833 L. (Editor), RFC 3473, January 2003." 834 DEFVAL { '00000000'H } -- 0.0.0.0 835 ::= { gmplsTunnelEntry 10 } 836 gmplsTunnelDownNotRecip OBJECT-TYPE 837 SYNTAX IpAddress 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "Indicates the address of the downstream recipient for Notify 842 messages relating to this tunnel. 844 This object is only valid when signaling a tunnel using RSVP. It 845 is also not valid at the head end of the tunnel. 847 If set to 0, no Notify Request object will be included in 848 outgoing Resv messages." 849 REFERENCE 850 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 851 (Editor), RFC 3473, January 2003." 852 DEFVAL { '00000000'H } -- 0.0.0.0 853 ::= { gmplsTunnelEntry 11 } 855 gmplsTunnelAdminStatusFlags OBJECT-TYPE 856 SYNTAX IANAGmplsAdminStatusFlags 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "Determines the setting of the Admin Status flags in the 861 Admin Status object or TLV, as described in RFC 3471. Setting 862 this field to a non-zero value will result in the inclusion of 863 the admin status object on signaling messages. 865 The values to use are defined in the textual convention 866 IANAGmplsAdminStatusFlags found in the IANA-GMPLS-MIB MIB 867 module. 869 This value of this object can be modified when the 870 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 871 is active(1). By doing so, a new signaling message will be 872 triggered including the requested Admin Status object or 873 TLV." 874 REFERENCE 875 "Berger, L., et al., Generalized Multi-Protocol Label Switching 876 (GMPLS) Signaling Functional Description, RFC 3471, 877 January 2003." 878 DEFVAL { { } } 879 ::= { gmplsTunnelEntry 12 } 881 gmplsTunnelExtraParamsPtr OBJECT-TYPE 882 SYNTAX RowPointer 883 MAX-ACCESS read-create 884 STATUS current 885 DESCRIPTION 886 "Some Tunnels will run over transports that can usefully support 887 technology-specific additional parameters (for example, SONET 888 resource usage). Such parameters can be supplied in an external 889 table and referenced from here. 891 A value of zeroDotzero in this attribute indicates that there 892 is no such additional information." 893 DEFVAL { zeroDotZero } 894 ::= { gmplsTunnelEntry 13 } 896 -- End of gmplsTunnelTable 898 -- Begin gmplsTunnelHopTable 900 gmplsTunnelHopTable OBJECT-TYPE 901 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 902 MAX-ACCESS not-accessible 903 STATUS current 904 DESCRIPTION 905 "The gmplsTunnelHopTable 'extends' the mplsTunnelHopTable. It is 906 used to indicate the explicit labels to be used in an explicit 907 path for a GMPLS tunnel defined in mplsTunnelTable and 908 gmplsTunnelTable, when it is established using signaling. It 909 does not insert new hops, but does define new values for hops 910 defined in mplsTunnelHopTable. 912 Each row in this table is indexed by the same indexes as 913 mplsTunnelHopTable. It is acceptable for some rows in 914 mplsTunnelHopTable to have corresponding entries in this table 915 and some to have no corresponding entry in this table. 917 The storage type for an entry in this table is inherited from 918 mplsTunnelHopStorageType in the corresponding entry in 919 mplsTunnelHopTable. 921 The row status of an entry in this table is controlled by 922 mplsTunnelHopRowStatus in the corresponding entry in 923 mplsTunnelHopTable. That is, it is not permitted to create a row 924 in this table, nor to modify an existing row, when the 925 corresponding mplsTunnelHopRowStatus has value active(1)." 926 REFERENCE 927 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 928 (Editor), RFC 3473, January 2003." 929 ::= { gmplsTeObjects 2 } 930 gmplsTunnelHopEntry OBJECT-TYPE 931 SYNTAX GmplsTunnelHopEntry 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "An entry in this table represents additions to a tunnel hop 936 defined in mplsTunnelHopEntry. At an ingress to a tunnel an 937 entry in this table is created by a network administrator for an 938 ERLSP to be set up by a signaling protocol. At transit and 939 egress nodes an entry in this table may be used to represent the 940 explicit path instructions received using the signaling 941 protocol." 942 INDEX { 943 mplsTunnelHopListIndex, 944 mplsTunnelHopPathOptionIndex, 945 mplsTunnelHopIndex 946 } 947 ::= { gmplsTunnelHopTable 1 } 949 GmplsTunnelHopEntry ::= SEQUENCE { 950 gmplsTunnelHopLabelStatuses BITS, 951 gmplsTunnelHopExpLabel Unsigned32, 952 gmplsTunnelHopExpLabelPtr RowPointer, 953 gmplsTunnelHopExpRvrsLabel Unsigned32, 954 gmplsTunnelHopExpRvrsLabelPtr RowPointer 955 } 957 gmplsTunnelHopLabelStatuses OBJECT-TYPE 958 SYNTAX BITS { 959 forwardPresent (0), 960 reversePresent (1) 961 } 962 MAX-ACCESS read-only 963 STATUS current 964 DESCRIPTION 965 "This bitmask indicates the presence of labels indicated by the 966 gmplsTunnelHopExpLabel or gmplsTunnelHopExpLabelPtr, and 967 gmplsTunnelHopExpRvrsLabel or gmplsTunnelHopExpRvrsLabel 968 objects. 970 For the Present bits, a set bit indicates that a label is 971 present for this hop in the route. This allows zero to be a 972 valid label value." 973 DEFVAL { { } } 974 ::= { gmplsTunnelHopEntry 1 } 975 gmplsTunnelHopExpLabel OBJECT-TYPE 976 SYNTAX Unsigned32 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "If gmplsTunnelHopLabelStatuses object indicates that a forward 981 label is present and gmplsTunnelHopExpLabelPtr contains the 982 value zeroDotZero, then the label to use on this hop is found in 983 object encoded within a 32-bit integer." 984 ::= { gmplsTunnelHopEntry 2 } 986 gmplsTunnelHopExpLabelPtr OBJECT-TYPE 987 SYNTAX RowPointer 988 MAX-ACCESS read-create 989 STATUS current 990 DESCRIPTION 991 "If the gmplsTunnelHopLabelStatuses object indicates that a 992 forward label is present, this object contains a pointer to a 993 row in another MIB table (such as the gmplsLabelTable) that 994 contains the label to use on this hop in the forward direction. 995 If the gmplsTunnelHopLabelStatuses object indicates that a 996 forward label is present and this object contains the value 997 zeroDotZero, then the label to use on this hop is found in the 998 gmplsTunnelHopExpLabel object." 999 DEFVAL { zeroDotZero } 1000 ::= { gmplsTunnelHopEntry 3 } 1002 gmplsTunnelHopExpRvrsLabel OBJECT-TYPE 1003 SYNTAX Unsigned32 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "If the gmplsTunnelHopLabelStatuses object indicates that a 1008 reverse label is present and gmplsTunnelHopExpRvrsLabelPtr 1009 contains the value zeroDotZero, then the label to use on this 1010 this hop is found in this object encoded as a 32-bit integer." 1011 ::= { gmplsTunnelHopEntry 4 } 1012 gmplsTunnelHopExpRvrsLabelPtr OBJECT-TYPE 1013 SYNTAX RowPointer 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "If the gmplsTunnelHopLabelStatuses object indicates that a 1018 reverse label is present, this object contains a pointer to a 1019 row in another MIB table (such as the gmplsLabelTable) that 1020 contains the label to use on this hop in the reverse direction. 1022 If the gmplsTunnelHopLabelStatuses object indicates that a 1023 reverse label is present and this object contains the value 1024 zeroDotZero, then the label to use on this hop is found in the 1025 gmplsTunnelHopExpRvrsLabel object." 1026 DEFVAL { zeroDotZero } 1027 ::= { gmplsTunnelHopEntry 5 } 1029 -- End of gmplsTunnelHopTable 1031 -- Tunnel Actual Route Hop table. 1033 gmplsTunnelARHopTable OBJECT-TYPE 1034 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "The gmplsTunnelARHopTable 'extends' the mplsTunnelARHopTable. It 1039 is used to indicate the labels currently in use for a GMPLS 1040 tunnel defined in mplsTunnelTable and gmplsTunnelTable, as 1041 reported by the signaling protocol. It does not insert new hops, 1042 but does define new values for hops defined in 1043 mplsTunnelARHopTable. 1045 Each row in this table is indexed by the same indexes as 1046 mplsTunnelARHopTable. It is acceptable for some rows in 1047 mplsTunnelARHopTable to have corresponding entries in this table 1048 and some to have no corresponding entry in this table. 1050 Note that since the information necessary to build entries 1051 within this table is not provided by some signaling protocols 1052 and might not be returned in all cases of other signaling 1053 protocols, implementation of this table and mplsTunnelARHopTable 1054 is optional. Furthermore, since the information in this table is 1055 actually provided by the signaling protocol after the path has 1056 been set-up, the entries in this table are provided only for 1057 observation, and hence, all variables in this table are 1058 accessible exclusively as read-only." 1060 REFERENCE 1061 "1. Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, 1062 December 2001 1063 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 1064 (Editor), RFC 3473, January 2003." 1065 ::= { gmplsTeObjects 3 } 1067 gmplsTunnelARHopEntry OBJECT-TYPE 1068 SYNTAX GmplsTunnelARHopEntry 1069 MAX-ACCESS not-accessible 1070 STATUS current 1071 DESCRIPTION 1072 "An entry in this table represents additions to a tunnel hop 1073 visible in mplsTunnelARHopEntry. An entry is created by the 1074 signaling protocol for a signaled ERLSP set up by the signaling 1075 protocol. 1077 At any node on the LSP (ingress, transit or egress) Thus at this 1078 table and mplsTunnelARHopTable (if the tables are supported and 1079 if the signaling protocol is recording actual route information) 1080 contains the actual route of the whole tunnel. If the signaling 1081 protocol is not recording the actual route, this table MAY 1082 report the information from the gmplsTunnelHopTable or the 1083 gmplsTunnelCHopTable. 1085 Note that the recording of actual labels is distinct from the 1086 recording of the actual route in some signaling protocols. This 1087 feature is enabled using the gmplsTunnelAttributes object." 1088 INDEX { 1089 mplsTunnelARHopListIndex, 1090 mplsTunnelARHopIndex 1091 } 1092 ::= { gmplsTunnelARHopTable 1 } 1094 GmplsTunnelARHopEntry ::= SEQUENCE { 1095 gmplsTunnelARHopLabelStatuses BITS, 1096 gmplsTunnelARHopExpLabel Unsigned32, 1097 gmplsTunnelARHopExpLabelPtr RowPointer, 1098 gmplsTunnelARHopExpRvrsLabel Unsigned32, 1099 gmplsTunnelARHopExpRvrsLabelPtr RowPointer, 1100 gmplsTunnelARHopProtection BITS 1101 } 1102 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1103 SYNTAX BITS { 1104 forwardPresent (0), 1105 reversePresent (1), 1106 forwardGlobal (2), 1107 reverseGlobal (3) 1108 } 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "This bitmask indicates the presence and status of labels 1113 indicated by the gmplsTunnelARHopExpLabel or 1114 gmplsTunnelARHopExpLabelPtr, and gmplsTunnelARHopExpRvrsLabel or 1115 gmplsTunnelARHopExpRvrsLabelPtr objects. 1117 For the Present bits, a set bit indicates that a label is 1118 present for this hop in the route. For the Global bits, a set 1119 bit indicates that the label comes from the Global Label Space. 1120 A clear bit indicates that this is a Per-Interface label. A 1121 Global bit only has meaning if the corresponding Present bit is 1122 set." 1123 ::= { gmplsTunnelARHopEntry 1 } 1125 gmplsTunnelARHopExpLabel OBJECT-TYPE 1126 SYNTAX Unsigned32 1127 MAX-ACCESS read-only 1128 STATUS current 1129 DESCRIPTION 1130 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1131 forward label is present and gmplsTunnelARHopExpLabelPtr 1132 contains the value zeroDotZero, then the label in use on this 1133 hop is found in this object encoded within a 32-bit integer." 1134 ::= { gmplsTunnelARHopEntry 2 } 1136 gmplsTunnelARHopExpLabelPtr OBJECT-TYPE 1137 SYNTAX RowPointer 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1142 forward label is present, this object contains a pointer to a 1143 row in another MIB table (such as the gmplsLabelTable) that 1144 contains the label in use on this hop in the forward direction. 1145 If the gmplsTunnelARHopLabelStatuses object indicates that a 1146 forward label is present and this object contains the value 1147 zeroDotZero, then the label in use on this hop is found in the 1148 gmplsTunnelARHopExpLabel object." 1149 ::= { gmplsTunnelARHopEntry 3 } 1150 gmplsTunnelARHopExpRvrsLabel OBJECT-TYPE 1151 SYNTAX Unsigned32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1156 reverse label is present and gmplsTunnelARHopExpRvrsLabelPtr 1157 contains the value zeroDotZero, then the label in use on this 1158 hop is found in this object encoded as a 32-bit integer." 1159 ::= { gmplsTunnelARHopEntry 4 } 1161 gmplsTunnelARHopExpRvrsLabelPtr OBJECT-TYPE 1162 SYNTAX RowPointer 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1167 reverse label is present, this object contains a pointer to a 1168 row in another MIB table (such as the gmplsLabelTable) that 1169 contains the label in use on this hop in the reverse direction. 1170 If the gmplsTunnelARHopLabelStatuses object indicates that a 1171 reverse label is present and this object contains the value 1172 zeroDotZero, then the label in use on this hop is found in the 1173 gmplsTunnelARHopExpRvrsLabel object." 1174 ::= { gmplsTunnelARHopEntry 5 } 1176 gmplsTunnelARHopProtection OBJECT-TYPE 1177 SYNTAX BITS { 1178 localAvailable (0), 1179 localInUse (1) 1180 } 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "Availability and usage of protection on the reported link. 1186 localAvailable 1187 Indicates that the link downstream of this node is protected 1188 via a local repair mechanism. 1190 localInUse 1191 Indicates that a local repair mechanism is in use to maintain 1192 this tunnel (usually in the face of an outage of the link it 1193 was previously routed over)." 1194 ::= { gmplsTunnelARHopEntry 6 } 1196 -- End of mplsTunnelARHopTable 1197 -- Tunnel Computed Hop table. 1199 gmplsTunnelCHopTable OBJECT-TYPE 1200 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "The gmplsTunnelCHopTable 'extends' the mplsTunnelCHopTable. It 1205 is used to indicate additional information about the hops of a 1206 GMPLS tunnel defined in mplsTunnelTable and gmplsTunnelTable, as 1207 computed by a constraint-based routing protocol, based on the 1208 mplsTunnelHopTable and the gmplsTunnelHopTable. 1210 Each row in this table is indexed by the same indexes as 1211 mplsTunnelCHopTable. It is acceptable for some rows in 1212 mplsTunnelCHopTable to have corresponding entries in this table 1213 and some to have no corresponding entry in this table. 1215 Please note that since the information necessary to build 1216 entries within this table may not be supported by some LSRs, 1217 implementation of this table is optional. 1219 Furthermore, since the information in this table is actually 1220 provided by a path computation component after the path has been 1221 computed, the entries in this table are provided only for 1222 observation, and hence, all objects in this table are accessible 1223 exclusively as read-only." 1224 REFERENCE 1225 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 1226 (Editor), RFC 3473, January 2003." 1227 ::= { gmplsTeObjects 4 } 1229 gmplsTunnelCHopEntry OBJECT-TYPE 1230 SYNTAX GmplsTunnelCHopEntry 1231 MAX-ACCESS not-accessible 1232 STATUS current 1233 DESCRIPTION 1234 "An entry in this table represents additions to a computed tunnel 1235 hop visible in mplsTunnelCHopEntry. An entry is created by a 1236 path computation component based on the hops specified in the 1237 corresponding mplsTunnelHopTable and gmplsTunnelHopTable. 1239 At a transit LSR this table (if the table is supported) MAY 1240 contain the path computed by path computation engine on (or on 1241 behalf of) the transit LSR." 1242 INDEX { 1243 mplsTunnelCHopListIndex, 1244 mplsTunnelCHopIndex 1245 } 1246 ::= { gmplsTunnelCHopTable 1 } 1247 GmplsTunnelCHopEntry ::= SEQUENCE { 1248 gmplsTunnelCHopLabelStatuses BITS, 1249 gmplsTunnelCHopExpLabel Unsigned32, 1250 gmplsTunnelCHopExpLabelPtr RowPointer, 1251 gmplsTunnelCHopExpRvrsLabel Unsigned32, 1252 gmplsTunnelCHopExpRvrsLabelPtr RowPointer 1253 } 1255 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1256 SYNTAX BITS { 1257 forwardPresent (0), 1258 reversePresent (1) 1259 } 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "This bitmask indicates the presence of labels indicated by the 1264 gmplsTunnelCHopExpLabel or gmplsTunnelCHopExpLabelPtr and 1265 gmplsTunnelCHopExpRvrsLabel or gmplsTunnelCHopExpRvrsLabelPtr 1266 objects. 1267 A set bit indicates that a label is present for this hop in the 1268 route thus allowing zero to be a valid label value." 1269 ::= { gmplsTunnelCHopEntry 1 } 1271 gmplsTunnelCHopExpLabel OBJECT-TYPE 1272 SYNTAX Unsigned32 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1277 forward label is present and gmplsTunnelCHopExpLabelPtr contains 1278 the value zeroDotZero, then the label to use on this hop is 1279 found in this object encoded within a 32-bit integer." 1280 ::= { gmplsTunnelCHopEntry 2 } 1282 gmplsTunnelCHopExpLabelPtr OBJECT-TYPE 1283 SYNTAX RowPointer 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1288 forward label is present, this object contains a pointer to a 1289 row in another MIB table (such as the gmplsLabelTable) that 1290 contains the label to use on this hop in the forward direction. 1291 If the gmplsTunnelCHopLabelStatuses object indicates that a 1292 forward label is present and this object contains the value 1293 zeroDotZero, then the label to use on this hop is found in the 1294 gmplsTunnelCHopExpLabel object." 1295 ::= { gmplsTunnelCHopEntry 3 } 1296 gmplsTunnelCHopExpRvrsLabel OBJECT-TYPE 1297 SYNTAX Unsigned32 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1302 reverse label is present and gmplsTunnelCHopExpRvrsLabelPtr 1303 contains the value zeroDotZero, then the label to use on this 1304 hop is found in this object encoded as a 32-bit integer." 1305 ::= { gmplsTunnelCHopEntry 4 } 1307 gmplsTunnelCHopExpRvrsLabelPtr OBJECT-TYPE 1308 SYNTAX RowPointer 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1313 reverse label is present, this object contains a pointer to a 1314 row in another MIB table (such as the gmplsLabelTable) that 1315 contains the label to use on this hop in the reverse direction. 1317 If the gmplsTunnelCHopLabelStatuses object indicates that a 1318 reverse label is present and this object contains the value 1319 zeroDotZero, then the label to use on this hop is found in the 1320 gmplsTunnelCHopExpRvrsLabel object." 1321 ::= { gmplsTunnelCHopEntry 5 } 1323 -- End of gmplsTunnelCHopTable 1325 -- GMPLS Tunnel Reverse Direction Performance Table. 1327 gmplsTunnelReversePerfTable OBJECT-TYPE 1328 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1329 MAX-ACCESS not-accessible 1330 STATUS current 1331 DESCRIPTION 1332 "This table 'augments' the gmplsTunnelTable to provides 1333 per-tunnel packet performance information for the reverse 1334 direction of a bidirectional tunnel. It can be seen as 1335 supplementing the mplsTunnelPerfTable which augments the 1336 mplsTunnelTable." 1337 REFERENCE 1338 "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1339 Management Information Base (MIB), Srinivasan, C., Viswanathan, 1340 A., Nadeau, T., RFC 3812, June 2004." 1341 ::= { gmplsTeObjects 5 } 1342 gmplsTunnelReversePerfEntry OBJECT-TYPE 1343 SYNTAX GmplsTunnelReversePerfEntry 1344 MAX-ACCESS not-accessible 1345 STATUS current 1346 DESCRIPTION 1347 "An entry in this table is created by the LSR for every 1348 bidirectional GMPLS tunnel where packets are visible to the 1349 LSR." 1350 AUGMENTS { gmplsTunnelEntry } 1351 ::= { gmplsTunnelReversePerfTable 1 } 1353 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1354 gmplsTunnelReversePerfPackets Counter32, 1355 gmplsTunnelReversePerfHCPackets Counter64, 1356 gmplsTunnelReversePerfErrors Counter32, 1357 gmplsTunnelReversePerfBytes Counter32, 1358 gmplsTunnelReversePerfHCBytes Counter64 1359 } 1361 gmplsTunnelReversePerfPackets OBJECT-TYPE 1362 SYNTAX Counter32 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "Number of packets forwarded on the tunnel in the reverse 1367 direction if it is bidirectional." 1368 ::= { gmplsTunnelReversePerfEntry 1 } 1370 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1371 SYNTAX Counter64 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "High capacity counter for number of packets forwarded on the 1376 tunnel in the reverse direction if it is bidirectional." 1377 ::= { gmplsTunnelReversePerfEntry 2 } 1379 gmplsTunnelReversePerfErrors OBJECT-TYPE 1380 SYNTAX Counter32 1381 MAX-ACCESS read-only 1382 STATUS current 1383 DESCRIPTION 1384 "Number of errored packets received on the tunnel in the reverse 1385 direction if it is bidirectional." 1386 ::= { gmplsTunnelReversePerfEntry 3 } 1387 gmplsTunnelReversePerfBytes OBJECT-TYPE 1388 SYNTAX Counter32 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "Number of bytes forwarded on the tunnel in the reverse direction 1393 if it is bidirectional." 1394 ::= { gmplsTunnelReversePerfEntry 4 } 1396 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1397 SYNTAX Counter64 1398 MAX-ACCESS read-only 1399 STATUS current 1401 DESCRIPTION 1402 "High capacity counter for number of bytes forwarded on the 1403 tunnel in the reverse direction if it is bidirectional." 1404 ::= { gmplsTunnelReversePerfEntry 5 } 1406 -- End of gmplsTunnelReversePerfTable 1408 -- GMPLS Tunnel Error Table. 1410 gmplsTunnelErrorTable OBJECT-TYPE 1411 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "This table 'augments' the mplsTunnelTable 1416 This table provides per-tunnel information about errors. Errors 1417 may be detected locally or reported through the signaling 1418 protocol. Error reporting is not exclusive to GMPLS and this 1419 table may be applied in MPLS systems." 1420 REFERENCE 1421 "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1422 Management Information Base (MIB), Srinivasan, C., Viswanathan, 1423 A., Nadeau, T., RFC 3812, June 2004." 1424 ::= { gmplsTeObjects 6 } 1425 gmplsTunnelErrorEntry OBJECT-TYPE 1426 SYNTAX GmplsTunnelErrorEntry 1427 MAX-ACCESS not-accessible 1428 STATUS current 1429 DESCRIPTION 1430 "An entry in this table is created by the LSR for every tunnel 1431 where error information is visible to the LSR. 1432 Note that systems which read the objects in this table one at a 1433 time may experience a discontinuity as the result of a new error 1434 occurring in between object reads. Systems that are vulnerable 1435 to this should read gmplsTunnelErrorLastTime before and after 1436 reading the other objects." 1437 AUGMENTS { mplsTunnelEntry } 1438 ::= { gmplsTunnelErrorTable 1 } 1440 GmplsTunnelErrorEntry ::= SEQUENCE { 1441 gmplsTunnelErrorLastErrorType INTEGER, 1442 gmplsTunnelErrorLastTime TimeStamp, 1443 gmplsTunnelErrorReporterType InetAddressType, 1444 gmplsTunnelErrorReporter InetAddress, 1445 gmplsTunnelErrorCode Unsigned32, 1446 gmplsTunnelErrorSubcode Unsigned32, 1447 gmplsTunnelErrorTLVs OCTET STRING, 1448 gmplsTunnelErrorHelpString DisplayString 1449 } 1451 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1452 SYNTAX INTEGER { 1453 noError (0), 1454 unknown (1), 1455 protocol (2), 1456 pathComputation (3), 1457 localConfiguration (4), 1458 localResources (5), 1459 localOther (6) 1460 } 1461 MAX-ACCESS read-only 1462 STATUS current 1463 DESCRIPTION 1464 "The nature of the last error. Provides interpretation context 1465 for gmplsTunnelErrorProtocolCode and 1466 gmplsTunnelErrorProtocolSubcode. 1468 A value of noError (0) shows that there is no error associated 1469 with this tunnel and means that the other objects in this table 1470 entry have no meaning. 1472 A value of unknown (1) shows that there is an error but that no 1473 additional information about the cause is known. The error may 1474 have been received in a signaled message or generated locally. 1476 A value of protocol (2) or pathComputation (3) indicates that 1477 the cause of an error and identifies an error that has been 1478 received through signaling or will itself be signaled. 1480 A value of localConfiguration (4), localResources (5) or 1481 localOther (6) identifies an error which has been detected 1482 by the local node, but which will not be reported through 1483 signaling." 1484 ::= { gmplsTunnelErrorEntry 1 } 1486 gmplsTunnelErrorLastTime OBJECT-TYPE 1487 SYNTAX TimeStamp 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The time at which the last error occurred. This is presented as 1492 the value of SysUpTime when the error occurred or was reported 1493 to this node. 1495 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1496 this object is ignored." 1497 ::= { gmplsTunnelErrorEntry 2 } 1499 gmplsTunnelErrorReporterType OBJECT-TYPE 1500 SYNTAX InetAddressType 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "The address type of the error reported. 1506 This object is used to aid in interpretation of 1507 gmplsTunnelErrorReporter." 1508 ::= { gmplsTunnelErrorEntry 3 } 1510 gmplsTunnelErrorReporter OBJECT-TYPE 1511 SYNTAX InetAddress 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "The address of the node reporting the last error, or the address 1516 of the resource (such as an interface) associated with the 1517 error. 1519 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1520 this object is ignored. 1522 If gmplsTunnelErrorLastErrorType has the value unknown (1), 1523 localConfiguration (4), localResources (5), or localOther (6) 1524 this object MAY contain a zero value. 1526 This object should be interpreted in the context of the value of 1527 the object gmplsTunnelErrorReporterType." 1528 REFERENCE 1529 "RFC4001, Textual Conventions for Internet Network Addresses, 1530 Section 4. Usage Hints." 1531 ::= { gmplsTunnelErrorEntry 4 } 1533 gmplsTunnelErrorCode OBJECT-TYPE 1534 SYNTAX Unsigned32 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "The primary error code associated with the last error. 1539 The interpretation of this error code depends on the value of 1540 gmplsTunnelErrorLastErrorType. If the value of 1541 gmplsTunnelErrorLastErrorType is noError (0) the value of this 1542 object should be 0 and should be ignored. If the value of 1543 gmplsTunnelErrorLastErrorType is protocol (2) the error should 1544 be interpreted in the context of the signling protocol 1545 identified by the mplsTunnelSignallingProto object. 1547 Values in excess 32767 of are not used by signaling protocols 1548 and may safely be used as implementation-specific error codes." 1549 REFERENCE 1550 "1. Braden, R. (Ed.) et al., Resource ReserVation Protocol -- 1551 Version 1 Functional Specification, RFC 2205, September 1997. 1552 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., 1553 RFC 3209, December 2001. 1554 3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 1555 (Editor), RFC 3473, January 2003." 1556 ::= { gmplsTunnelErrorEntry 5 } 1558 gmplsTunnelErrorSubcode OBJECT-TYPE 1559 SYNTAX Unsigned32 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "The secondary error code associated with the last error and the 1564 protocol used to signal this tunnel. This value is interpreted 1565 in the context of the value of gmplsTunnelErrorCode. 1566 If the value of gmplsTunnelErrorLastErrorType is noError (0) the 1567 value of this object should be 0 and should be ignored." 1568 REFERENCE 1569 "1. Braden, R. (Ed.) et al., Resource ReserVation Protocol -- 1570 Version 1 Functional Specification, RFC 2205, September 1997. 1571 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., 1572 RFC 3209, December 2001. 1573 3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 1574 (Editor), RFC 3473, January 2003." 1575 ::= { gmplsTunnelErrorEntry 6 } 1576 gmplsTunnelErrorTLVs OBJECT-TYPE 1577 SYNTAX OCTET STRING 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION 1581 "The sequence of interface identifier TLVs reported with the 1582 error by the protocol code. The interpretation of the TLVs and 1583 the encoding within the protocol are described in the 1584 references. A value of zero in the first octet indicates that no 1585 TLVs are present." 1586 REFERENCE 1587 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 1588 (Editor), RFC 3473, January 2003." 1589 ::= { gmplsTunnelErrorEntry 7 } 1591 gmplsTunnelErrorHelpString OBJECT-TYPE 1592 SYNTAX DisplayString 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "A textual string containing information about the last error, 1597 recovery actions and support advice. If there is no help string 1598 this object contains a zero length string. 1599 If the value of gmplsTunnelErrorLastErrorType is noError (0) 1600 this object should contain a zero length string, but may contain 1601 a help string indicating that there is no error." 1602 ::= { gmplsTunnelErrorEntry 8 } 1604 -- GMPLS Notifications. 1606 gmplsTunnelDown NOTIFICATION-TYPE 1607 OBJECTS { 1608 mplsTunnelAdminStatus, 1609 mplsTunnelOperStatus, 1610 gmplsTunnelErrorLastErrorType, 1611 gmplsTunnelErrorReporterType, 1612 gmplsTunnelErrorReporter, 1613 gmplsTunnelErrorCode, 1614 gmplsTunnelErrorSubcode 1615 } 1616 STATUS current 1617 DESCRIPTION 1618 "This notification is generated when a mplsTunnelOperStatus 1619 object for one of the configured tunnels is about to enter the 1620 down state from some other state (but not from the notPresent 1621 state). This other state is indicated by the included value of 1622 mplsTunnelOperStatus. 1624 The objects in this notification provide additional error 1625 information that indicates the reason why the tunnel has 1626 transitioned down. 1628 Note that an implementation SHOULD only issue one of 1629 mplsTunnelDown and gmplsTunnelDown for a single event on a 1630 single tunnel." 1631 ::= { gmplsTeNotifications 1 } 1633 -- End of notifications. 1635 -- Module compliance. 1637 gmplsTeGroups 1638 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1640 gmplsTeCompliances 1641 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1643 -- Compliance requirement for fully compliant implementations. 1644 -- The mandatory group has to be implemented by all LSRs that 1645 -- originate, terminate or act as transit for TE-LSPs/tunnels. 1646 -- In addition, depending on the type of tunnels supported, other 1647 -- groups become mandatory as explained below. 1649 gmplsTeModuleFullCompliance MODULE-COMPLIANCE 1650 STATUS current 1651 DESCRIPTION 1652 "Compliance statement for agents that provide full support for 1653 GMPLS-TE-STD-MIB. Such devices can then be monitored and also 1654 be configured using this MIB module." 1656 MODULE -- this module 1657 MANDATORY-GROUPS { 1658 gmplsTunnelGroup, 1659 gmplsTunnelScalarGroup, 1660 gmplsTunnelSignaledGroup 1661 } 1662 ::= { gmplsTeCompliances 1 } 1664 -- Compliance requirement for read-only compliant implementations. 1666 gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 1667 STATUS current 1668 DESCRIPTION 1669 "Compliance requirement for implementations that only provide 1670 read-only support for GMPLS-TE-STD-MIB. Such devices can then be 1671 monitored but cannot be configured using this MIB module." 1673 MODULE -- this module 1675 -- The mandatory group has to be implemented by all LSRs that 1676 -- originate, terminate or act as transit for TE-LSPs/tunnels. 1677 -- In addition, depending on the type of tunnels supported, other 1678 -- groups become mandatory as explained below. 1680 MANDATORY-GROUPS { 1681 gmplsTunnelGroup, 1682 gmplsTunnelScalarGroup 1683 } 1685 GROUP gmplsTunnelSignaledGroup 1686 DESCRIPTION 1687 "This group is mandatory for devices which support signaled 1688 tunnel set up, in addition to gmplsTunnelGroup. The following 1689 constraints apply: 1691 mplsTunnelSignallingProto should be at least read-only returning 1692 a value of ldp(2), or rsvp(3)." 1694 GROUP gmplsTunnelIsNotIntfcGroup 1695 DESCRIPTION 1696 "This group is mandatory for devices which support tunnels that 1697 are not interfaces, in addition to gmplsTunnelGroup. The 1698 following constraints apply: 1699 gmplsTunnelIsIf must at least be read-only returning no(0)." 1701 GROUP gmplsTunnelIsIntfcGroup 1702 DESCRIPTION 1703 "This group is mandatory for devices which support tunnels that 1704 are interfaces, in addition to gmplsTunnelGroup." 1706 GROUP gmplsTunnelOptionalGroup 1707 DESCRIPTION 1708 "Objects in this group are optional." 1710 GROUP gmplsTeNotificationGroup 1711 DESCRIPTION 1712 "This group is mandatory for those implementations which can 1713 implement the notifications contained in this group." 1715 -- GMPLS Tunnel scalars. 1716 -- All scalars have max access read-only 1718 -- gmplsTunnelTable 1720 OBJECT gmplsTunnelAttributes 1721 MIN-ACCESS read-only 1722 DESCRIPTION 1723 "Write access is not required." 1725 OBJECT gmplsTunnelLSPEncoding 1726 SYNTAX IANAGmplsLSPEncoding 1727 MIN-ACCESS read-only 1728 DESCRIPTION 1729 "Write access is not required." 1731 OBJECT gmplsTunnelSwitchingType 1732 SYNTAX IANAGmplsSwitchingType 1733 MIN-ACCESS read-only 1734 DESCRIPTION 1735 "Write access is not required." 1737 OBJECT gmplsTunnelLinkProtection 1738 MIN-ACCESS read-only 1739 DESCRIPTION 1740 "Write access is not required." 1742 OBJECT gmplsTunnelGPid 1743 SYNTAX IANAGmplsGPid 1744 MIN-ACCESS read-only 1745 DESCRIPTION 1746 "Write access is not required." 1748 OBJECT gmplsTunnelSecondary 1749 SYNTAX TruthValue 1750 MIN-ACCESS read-only 1751 DESCRIPTION 1752 "Write access is not required." 1754 OBJECT gmplsTunnelDirection 1755 SYNTAX INTEGER { 1756 forward (0), 1757 bidirectional (1) 1758 } 1759 MIN-ACCESS read-only 1760 DESCRIPTION 1761 "Only forward (0) is required." 1763 OBJECT gmplsTunnelPathComp 1764 SYNTAX INTEGER { 1765 dynamicFull(1), -- CSPF fully computed 1766 explicit(2), -- fully specified path 1767 dynamicPartial(3) -- CSPF partially computed 1768 } 1770 MIN-ACCESS read-only 1771 DESCRIPTION 1772 "Only explicit (2) is required." 1774 OBJECT gmplsTunnelUpNotRecip 1775 SYNTAX IpAddress 1776 MIN-ACCESS read-only 1777 DESCRIPTION 1778 "Write access is not required." 1780 OBJECT gmplsTunnelDownNotRecip 1781 SYNTAX IpAddress 1782 MIN-ACCESS read-only 1783 DESCRIPTION 1784 "Write access is not required." 1786 OBJECT gmplsTunnelAdminStatusFlags 1787 SYNTAX IANAGmplsAdminStatusFlags 1788 MIN-ACCESS read-only 1789 DESCRIPTION 1790 "Write access is not required." 1792 OBJECT gmplsTunnelExtraParamsPtr 1793 SYNTAX RowPointer 1794 MIN-ACCESS read-only 1795 DESCRIPTION 1796 "Write access is not required." 1798 -- gmplsTunnelHopTable 1800 -- gmplsTunnelHopLabelStatuses has max access read-only 1802 OBJECT gmplsTunnelHopExpLabel 1803 MIN-ACCESS read-only 1804 DESCRIPTION 1805 "Write access is not required." 1807 OBJECT gmplsTunnelHopExpLabelPtr 1808 MIN-ACCESS read-only 1809 DESCRIPTION 1810 "Write access is not required." 1812 OBJECT gmplsTunnelHopExpRvrsLabel 1813 MIN-ACCESS read-only 1814 DESCRIPTION 1815 "Write access is not required." 1817 OBJECT gmplsTunnelHopExpRvrsLabelPtr 1818 MIN-ACCESS read-only 1819 DESCRIPTION 1820 "Write access is not required." 1822 -- gmplsTunnelARHopTable 1823 -- all objects have max access read-only 1825 -- glmpsTunnelCHopTable 1826 -- all objects have max access read-only 1828 -- gmplsTunnelReversePerfTable 1829 -- all objects have max access read-only 1830 -- gmplsTunnelErrorTable 1831 -- all objects have max access read-only 1833 ::= { gmplsTeCompliances 2 } 1835 -- Units of conformance. 1837 gmplsTunnelGroup OBJECT-GROUP 1838 OBJECTS { 1839 gmplsTunnelDirection, 1840 gmplsTunnelReversePerfPackets, 1841 gmplsTunnelReversePerfHCPackets, 1842 gmplsTunnelReversePerfErrors, 1843 gmplsTunnelReversePerfBytes, 1844 gmplsTunnelReversePerfHCBytes, 1845 gmplsTunnelErrorLastErrorType, 1846 gmplsTunnelErrorLastTime, 1847 gmplsTunnelErrorReporterType, 1848 gmplsTunnelErrorReporter, 1849 gmplsTunnelErrorCode, 1850 gmplsTunnelErrorSubcode, 1851 gmplsTunnelErrorTLVs, 1852 gmplsTunnelErrorHelpString 1853 } 1854 STATUS current 1855 DESCRIPTION 1856 "Necessary, but not sufficient, set of objects to implement 1857 tunnels. In addition, depending on the type of the tunnels 1858 supported (for example, manually configured or signaled, 1859 persistent or non-persistent, etc.), the following other 1860 groups defined below are mandatory: 1862 gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup 1863 and/or gmplsTunnelIsIntfcGroup." 1864 ::= { gmplsTeGroups 1 } 1865 gmplsTunnelSignaledGroup OBJECT-GROUP 1866 OBJECTS { 1867 gmplsTunnelAttributes, 1868 gmplsTunnelLSPEncoding, 1869 gmplsTunnelSwitchingType, 1870 gmplsTunnelLinkProtection, 1871 gmplsTunnelGPid, 1872 gmplsTunnelSecondary, 1873 gmplsTunnelPathComp, 1874 gmplsTunnelUpNotRecip, 1875 gmplsTunnelDownNotRecip, 1876 gmplsTunnelAdminStatusFlags, 1877 gmplsTunnelHopLabelStatuses, 1878 gmplsTunnelHopExpLabel, 1879 gmplsTunnelHopExpLabelPtr, 1880 gmplsTunnelHopExpRvrsLabel, 1881 gmplsTunnelHopExpRvrsLabelPtr 1882 } 1884 STATUS current 1885 DESCRIPTION 1886 "Objects needed to implement signaled tunnels." 1887 ::= { gmplsTeGroups 3 } 1889 gmplsTunnelScalarGroup OBJECT-GROUP 1890 OBJECTS { 1891 gmplsTunnelsConfigured, 1892 gmplsTunnelsActive 1893 } 1894 STATUS current 1895 DESCRIPTION 1896 "Scalar objects needed to implement MPLS tunnels." 1897 ::= { gmplsTeGroups 4 } 1899 gmplsTunnelIsIntfcGroup OBJECT-GROUP 1900 OBJECTS { 1901 gmplsTunnelUnnumIf 1902 } 1903 STATUS current 1904 DESCRIPTION 1905 "Objects needed to implement tunnels that are interfaces." 1906 ::= { gmplsTeGroups 5 } 1908 gmplsTunnelIsNotIntfcGroup OBJECT-GROUP 1909 OBJECTS { 1910 gmplsTunnelUnnumIf 1911 } 1912 STATUS current 1913 DESCRIPTION 1914 "Objects needed to implement tunnels that are not interfaces." 1915 ::= { gmplsTeGroups 6 } 1916 gmplsTunnelOptionalGroup OBJECT-GROUP 1917 OBJECTS { 1918 gmplsTunnelExtraParamsPtr, 1919 gmplsTunnelARHopLabelStatuses, 1920 gmplsTunnelARHopExpLabel, 1921 gmplsTunnelARHopExpLabelPtr, 1922 gmplsTunnelARHopExpRvrsLabel, 1923 gmplsTunnelARHopExpRvrsLabelPtr, 1924 gmplsTunnelARHopProtection, 1925 gmplsTunnelCHopLabelStatuses, 1926 gmplsTunnelCHopExpLabel, 1927 gmplsTunnelCHopExpLabelPtr, 1928 gmplsTunnelCHopExpRvrsLabel, 1929 gmplsTunnelCHopExpRvrsLabelPtr 1930 } 1931 STATUS current 1932 DESCRIPTION 1933 "The objects in this group are optional." 1934 ::= { gmplsTeGroups 7 } 1936 gmplsTeNotificationGroup NOTIFICATION-GROUP 1937 NOTIFICATIONS { 1938 gmplsTunnelDown 1939 } 1940 STATUS current 1941 DESCRIPTION 1942 "Set of notifications implemented in this module. None is 1943 mandatory." 1944 ::= { gmplsTeGroups 8 } 1946 END 1948 9. Security Considerations 1950 It is clear that the MIB modules described in this document in 1951 association with the MPLS-TE-STD-MIB are potentially useful for 1952 monitoring of MPLS and GMPLS tunnels. These MIB modules can also be 1953 used for configuration of certain objects, and anything that can be 1954 configured can be incorrectly configured, with potentially disastrous 1955 results. 1957 There are a number of management objects defined in these MIB modules 1958 with a MAX-ACCESS clause of read-write and/or read-create. Such 1959 objects may be considered sensitive or vulnerable in some network 1960 environments. The support for SET operations in a non-secure 1961 environment without proper protection can have a negative effect on 1962 network operations. These are the tables and objects and their 1963 sensitivity/vulnerability: 1965 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 1966 objects to provision GMPLS tunnels interfaces at their ingress 1967 LSRs. Unauthorized write access to objects in these tables, could 1968 result in disruption of traffic on the network. This is especially 1969 true if a tunnel has already been established. The use of stronger 1970 mechanisms such as SNMPv3 security should be considered where 1971 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 1972 SNMPv3 agent which implements these MIB modules. 1974 Some of the readable objects in these MIB modules "i.e., objects with 1975 a MAX-ACCESS other than not-accessible" may be considered sensitive 1976 or vulnerable in some network environments. It is thus important to 1977 control even GET and/or NOTIFY access to these objects and possibly 1978 to even encrypt the values of these objects when sending them over 1979 the network via SNMP. These are the tables and objects and their 1980 sensitivity/vulnerability: 1982 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 1983 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, 1984 gmplsTunnelErrorTable collectively show the tunnel network 1985 topology and status. If an Administrator does not want to reveal 1986 this information, then these tables should be considered 1987 sensitive/vulnerable. 1989 SNMP versions prior to SNMPv3 did not include adequate security. Even 1990 if the network itself is secure "for example by using IPSec", even 1991 then, there is no control as to who on the secure network is allowed 1992 to access and GET/SET "read/change/create/delete" the objects in 1993 these MIB modules. It is RECOMMENDED that implementers consider the 1994 security features as provided by the SNMPv3 framework "see [RFC3410], 1995 section 8", including full support for the SNMPv3 cryptographic 1996 mechanisms "for authentication and privacy". 1998 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1999 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2000 enable cryptographic security. It is then a customer/operator 2001 responsibility to ensure that the SNMP entity giving access to an 2002 instance of this MIB module, is properly configured to give access to 2003 the objects only to those principals "users" that have legitimate 2004 rights to indeed GET or SET "change/create/delete" them. 2006 10. Acknowledgments 2008 This draft is the work of the five authors listed in the Authors' 2009 Addresses section. 2011 This document extends [RFC3812]. The authors would like to express 2012 their gratitude to all those who worked on that earlier MIB document. 2013 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 2014 contributions during an early implementation, and to Baktha 2015 Muralidharan and Tom Petch for their review comments. 2017 Special thanks to Joan Cucchiara and Len Nieman for their help with 2018 compilation issues. 2020 11. IANA Considerations 2022 As requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB], GMPLS related 2023 standards track MIB modules should be rooted under the mplsStdMIB 2024 subtree. There is one GMPLS MIB Module contained in this document, 2025 and the following "IANA Considerations" subsection requests IANA for 2026 a new assignment under the mplsStdMIB subtree. New assignments in 2027 the mplsStdMIB subtree can only be made via a Standards Action as 2028 specified in [RFC2434]. 2030 11.1. IANA Considerations for GMPLS-TE-STD-MIB 2032 IANA is requested to assign an OID to the GMPLS-TE-STD-MIB module 2033 specified in this document as { mplsStdMIB XXX }. 2035 11.2. Dependence on IANA MIB Modules 2037 Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, 2038 gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual 2039 conventions imported from the IANA-GMPLS-MIB. The purpose of 2040 defining these textual conventions in a separate MIB module is to 2041 allow additional values to be defined without having to issue a new 2042 version of this document. The Internet Assigned Numbers Authority 2043 (IANA) is responsible for the assignment of all Internet numbers; it 2044 will administer the values associated with these textual conventions. 2046 The rules for additions or changes to the IANA-GMPLS-MIB are outlined 2047 in the DESCRIPTION clause associated with its MODULE-IDENTITY 2048 statement. 2050 The current versions of the IANA-GMPLS-MIB can be accessed from the 2051 IANA home page at: "http://www.iana.org/". 2053 11.2.1. IANA-GMPLS-MIB Definition 2055 This is a temporary section intended to supply the base definition of 2056 an IANA MIB module. The normal procedure is that this MIB module is 2057 moved into the direct control of IANA, at which time this section 2058 should be deleted from this document. 2060 IANA is requested to assign an OID to the IANA-GMPLS-MIB module 2061 specified in this document as { transmission YYY }. 2063 IANA-GMPLS-MIB DEFINITIONS ::= BEGIN 2065 IMPORTS 2066 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 2067 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 2069 ianaGmpls MODULE-IDENTITY 2070 LAST-UPDATED "200505200001Z" -- 20 May 2005 00:00:01 GMT 2071 ORGANIZATION "IANA" 2072 CONTACT-INFO 2073 " Internet Assigned Numbers Authority 2074 Postal: USC/Information Sciences Institute 2075 4676 Admiralty Way, Marina del Rey, CA 90292 2076 Tel: +1 310 822 1511 2077 E-Mail: iana@isi.edu" 2078 DESCRIPTION 2079 "The MIB module which defines the GMPLS textual 2080 conventions for use as enumerations within GMPLS MIB 2081 modules, thus protecting those MIB modules from changes 2082 to the enumerations." 2083 -- Revision history. 2084 REVISION 2085 "200505200001Z" -- 20 May 2005 00:00:01 GMT 2086 DESCRIPTION 2087 -- RFC Editor: Please see the IANA Considerations Section. 2088 -- RFC-editor please fill in XXXX 2089 "Initial version issued as part of RFC XXXX." 2090 ::= { transmission YYY } 2092 IANAGmplsLSPEncoding ::= TEXTUAL-CONVENTION 2093 STATUS current 2094 DESCRIPTION 2095 "This data type is used as the syntax of the 2096 gmplsTunnelLSPEncoding object in the definition of 2097 GMPLS-TE-MIB's gmplsTunnelTable. 2099 The definition of this textual convention with the 2100 addition of newly assigned values is published 2101 periodically by the IANA, in either the Assigned 2102 Numbers RFC, or some derivative of it specific to 2103 Internet Network Management number assignments. (The 2104 latest arrangements can be obtained by contacting the 2105 IANA.) 2107 Requests for new values should be made to IANA via 2108 email (iana@isi.edu). 2110 gmplsTunnelLSPEncoding is used to represent and control 2111 the LSP encoding type of an LSP signaled by a GMPLS 2112 signaling protocol. The relationship between the 2113 assignment of gmplsTunnelLSPEncoding values and of the 2114 values used to represent LSP encoding types within the 2115 GMPLS signaling protocols is solely the purview of IANA 2116 and is subject to change without notice." 2117 REFERENCE 2118 "1. Berger, L., et al., Generalized Multi-Protocol 2119 Label Switching (GMPLS) Signaling Functional 2120 Description, RFC 3471, January 2003. 2121 2. D. Papadimitriou (Editor), Generalized MPLS 2122 Signalling Extensions for G.709 Optical Transport 2123 Networks Control, draft-ietf-ccamp-gmpls-g709, 2124 work in progress." 2125 SYNTAX INTEGER { 2126 tunnelLspNotGmpls (0), -- GMPLS is not in use 2127 tunnelLspPacket (1), -- Packet 2128 tunnelLspEthernet (2), -- Ethernet 2129 tunnelLspAnsiEtsiPdh (3), -- PDH 2130 -- the value 4 is deprecated 2131 tunnelLspSdhSonet (5), -- SDH or SONET 2132 -- the value 6 is deprecated 2133 tunnelLspDigitalWrapper (7), -- Digital Wrapper 2134 tunnelLspLambda (8), -- Lambda 2135 tunnelLspFiber (9), -- Fiber 2136 -- the value 10 is deprecated 2137 tunnelLspFiberChannel (11), -- Fiber Channel 2138 tunnelDigitalPath (12), -- Digital Path 2139 tunnelOpticalChannel (13) -- Optical Channel 2140 } 2142 IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION 2143 STATUS current 2144 DESCRIPTION 2145 "This data type is used as the syntax of the 2146 gmplsTunnelSwitchingType object in the definition of 2147 GMPLS-TE-MIB's gmplsTunnelTable. 2149 The definition of this textual convention with the 2150 addition of newly assigned values is published 2151 periodically by the IANA, in either the Assigned 2152 Numbers RFC, or some derivative of it specific to 2153 Internet Network Management number assignments. (The 2154 latest arrangements can be obtained by contacting the 2155 IANA.) 2157 Requests for new values should be made to IANA via 2158 email (iana@isi.edu). 2160 gmplsTunnelSwitchingType is used to represent and 2161 control the LSP switching type of an LSP signaled by a 2162 GMPLS signaling protocol. The relationship between the 2163 assignment of gmplsTunnelSwitchingType values and of the 2164 values used to represent LSP switching types within the 2165 GMPLS signaling protocols is solely the purview of IANA 2166 and is subject to change without notice." 2167 REFERENCE 2168 "1. Kompella, K., Rekhter, Y. (Editors), Routing Extensions 2169 in Support of Generalized Multi-Protocol Label Switching 2170 draft-ietf-ccamp-gmpls-routing, work in progress. 2171 2. Berger, L., et al., Generalized Multi-Protocol 2172 Label Switching (GMPLS) Signaling Functional 2173 Description, RFC 3471, January 2003." 2174 SYNTAX INTEGER { 2175 unknown (0), -- none of the following, or not known 2176 psc1 (1), -- Packet-Switch-Capable 1 2177 psc2 (2), -- Packet-Switch-Capable 2 2178 psc3 (3), -- Packet-Switch-Capable 3 2179 psc4 (4), -- Packet-Switch-Capable 4 2180 l2sc (51), -- Layer-2-Switch-Capable 2181 tdm (100), -- Time-Division-Multiplex 2182 lsc (150), -- Lambda-Switch-Capable 2183 fsc (200) -- Fiber-Switch-Capable 2184 } 2186 IANAGmplsGPid ::= TEXTUAL-CONVENTION 2187 STATUS current 2188 DESCRIPTION 2189 "This data type is used as the syntax of the 2190 gmplsTunnelGPid object in the definition of 2191 GMPLS-TE-MIB's gmplsTunnelTable. 2192 The definition of this textual convention with the 2193 addition of newly assigned values is published 2194 periodically by the IANA, in either the Assigned 2195 Numbers RFC, or some derivative of it specific to 2196 Internet Network Management number assignments. (The 2197 latest arrangements can be obtained by contacting the 2198 IANA.) 2200 Requests for new values should be made to IANA via 2201 email (iana@isi.edu). 2203 gmplsTunnelGPid is used to represent and control the LSP 2204 Generalized Protocol Identifier (G-PID) of an LSP 2205 signaled by a GMPLS signaling protocol. The relationship 2206 between the assignment of gmplsTunnelGPid values and of 2207 the values used to represent G-PIDs within the GMPLS 2208 signaling protocols is solely the purview of IANA and is 2209 subject to change without notice." 2210 REFERENCE 2211 "1. Berger, L., et al., Generalized Multi-Protocol 2212 Label Switching (GMPLS) Signaling Functional 2213 Description, RFC 3471, January 2003. 2214 2. D. Papadimitriou (Editor), Generalized MPLS 2215 Signalling Extensions for G.709 Optical Transport 2216 Networks Control, draft-ietf-ccamp-gmpls-g709, 2217 work in progress." 2218 SYNTAX INTEGER { 2219 unknown(0), -- unknown or none of the following 2220 asynchE4(5), 2221 asynchDS3T3(6), 2222 asynchE3(7), 2223 bitsynchE3(8), 2224 bytesynchE3(9), 2225 asynchDS2T2(10), 2226 bitsynchDS2T2(11), 2227 asynchE1(13), 2228 bytesynchE1(14), 2229 bytesynch31ByDS0(15), 2230 asynchDS1T1(16), 2231 bitsynchDS1T1(17), 2232 bytesynchDS1T1(18), 2233 vc1vc12(19), 2234 ds1SFAsynch(22), 2235 ds1ESFAsynch(23), 2236 ds3M23Asynch(24), 2237 ds3CBitParityAsynch(25), 2238 vtLovc(26), 2239 stsSpeHovc(27), 2240 posNoScramble16BitCrc(28), 2241 posNoScramble32BitCrc(29), 2242 posScramble16BitCrc(30), 2243 posScramble32BitCrc(31), 2244 atm(32), 2245 ethernet(33), 2246 sdhSonet(34), 2247 digitalwrapper(36), 2248 lambda(37), 2249 ansiEtsiPdh (38), 2250 lapsSdh (40), 2251 fddi (41), 2252 dqdb (42), 2253 fiberChannel3 (43), 2254 hdlc (44), 2255 ethernetV2DixOnly (45), 2256 ethernet802dot3Only (46), 2257 g709ODUj (47), 2258 g709OTUk (48), 2259 g709CBRorCBRa (49), 2260 g709CBRb (50), 2261 g709BSOT (51), 2262 g709BSNT (52), 2263 gfpIPorPPP (53), 2264 gfpEthernetMAC (54), 2265 gfpEthernetPHY (55), 2266 g709ESCON (56), 2267 g709FICON (57), 2268 g709FiberChannel (58) 2269 } 2271 IANAGmplsAdminStatusFlags ::= TEXTUAL-CONVENTION 2272 STATUS current 2273 DESCRIPTION 2274 "This data type is used as the syntax of the 2275 gmplsTunnelAdminStatusFlags object in the definition of 2276 GMPLS-TE-MIB's gmplsTunnelTable. 2278 The definition of this textual convention with the 2279 addition of newly assigned values is published 2280 periodically by the IANA, in either the Assigned 2281 Numbers RFC, or some derivative of it specific to 2282 Internet Network Management number assignments. (The 2283 latest arrangements can be obtained by contacting the 2284 IANA.) 2286 Requests for new values should be made to IANA via 2287 email (iana@isi.edu). 2289 gmplsTunnelAdminStatusFlags determines the setting of the 2290 Admin Status flags in the Admin Status object or TLV, as 2291 described in RFC 3471. Setting this object to a non-zero 2292 value will result in the inclusion of the Admin Status 2293 object or TLV on signaling messages. 2295 The relationship between the assignment of 2296 gmplsTunnelAdminStatusFlags values and of the bit flags 2297 in the Admin Status object or TLV within the GMPLS 2298 signaling protocols is solely the purview of IANA and is 2299 subject to change without notice." 2300 REFERENCE 2301 "Berger, L., et al., Generalized Multi-Protocol Label 2302 Switching (GMPLS) Signaling Functional Description, 2303 RFC 3471, January 2003." 2304 SYNTAX BITS { 2305 delInProgress (0), 2306 adminDown (1), 2307 testing (2), 2308 reflect (31) 2309 } 2311 END 2313 12. References 2315 12.1. Normative References 2317 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2318 Requirement Levels", BCP 14, RFC 2119, March 1997. 2320 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2321 Case, J., Rose, M., and S. Waldbusser, "Structure 2322 of Management Information Version 2 (SMIv2)", STD 2323 58, RFC 2578, April 1999. 2325 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2326 Case, J., Rose, M., and S. Waldbusser, "Textual 2327 Conventions for SMIv2", STD 58, RFC 2579, April 2328 1999. 2330 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2331 Case, J., Rose, M., and S. Waldbusser, "Conformance 2332 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2334 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2335 "Multiprotocol Label Switching Architecture", RFC 2336 3031, January 2001. 2338 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 2339 Srinivasan, V., and G. Swallow, "RSVP-TE: 2340 Extensions to RSVP for LSP Tunnels", RFC 3209, 2341 December 2001. 2343 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 2344 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 2345 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 2346 T., Feldman, N., Fredette, A., Girish, M., Gray, 2347 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 2348 A., and P. Vaananen, "Constraint-Based LSP Setup 2349 using LDP", RFC 3212, December 2001. 2351 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 2352 Label Switching (GMPLS) Signaling Functional 2353 Description", RFC 3471, January 2003. 2355 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 2356 "Generalized MPLS Signaling - CR-LDP Extensions", 2357 RFC 3472, January 2003. 2359 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 2360 RSVP-TE Extensions", RFC 3473, January 2003. 2362 [RFC3477] Kompella, K. and Rekhter, Y., "Signalling Unnumbered 2363 Links in RSVP-TE", RFC 3477, January 2003. 2365 [RFC3480] Kompella, K., Rekhter, Y. and Kullberg, A., 2366 "Signalling Unnumbered Links in CR-LDP", RFC 3480, 2367 February 2003. 2369 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 2370 Conventions and for Multiprotocol Label Switching 2371 (MPLS) Management", RFC 3811, June 2004. 2373 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2374 "Multiprotocol Label Switching (MPLS) Traffic 2375 Engineering (TE) Management Information Base (MIB)", 2376 RFC 3812, June 2004. 2378 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2379 "Multiprotocol Label Switching (MPLS) Label 2380 Switching (LSR) Router Management Information Base 2381 (MIB)", RFC 3813, June 2004. 2383 [RFC3945] Mannie, E. (Editor), "Generalized Multiprotocol 2384 Label Switching (GMPLS) Architecture", RFC 3945, 2385 October 2004. 2387 [RFC4001] Daniele, M., Haberman, B., Routhier, S., 2388 Schoenwaelder, J., and Braunschweig, TU, "Textual 2389 Conventions for Internet Network Addresses", 2390 RFC 4001, February 2005. 2392 [GMPLSLSRMIB] Nadeau, T., Farrel, A., (Editors) "Generalized 2393 Multiprotocol Label Switching (GMPLS) Label 2394 Switching Router (LSR) Management Information 2395 Base", draft-ietf-ccamp-gmpls-lsr-mib, work in 2396 progress. 2398 [GMPLSOSPF] Kompella, K., et al., "OSPF Extensions in Support 2399 of Generalized MPLS", 2400 draft-ietf-ccamp-ospf-gmpls-extensions, work in 2401 progress. 2403 [GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of 2404 Textual Conventions for Multiprotocol Label 2405 Switching (MPLS) Management", 2406 draft-ietf-ccamp-gmpls-te-mib, work in progress. 2408 12.2. Informational References 2410 [RFC2026] S. Bradner, "The Internet Standards Process -- 2411 Revision 3", RFC 2026, October 1996. 2413 [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for 2414 Writing an IANA Considerations Section in RFCs", 2415 BCP 26, RFC 2434, October 1998. 2417 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 2418 Applications", RFC 3413, December 2002. 2420 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2421 "Introduction and Applicability Statements for 2422 Internet-Standard Management Framework", RFC 3410, 2423 December 2002. 2425 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2426 Architecture for Describing Simple Network 2427 Management Protocol (SNMP) Management Frameworks", 2428 RFC 3411, December 2002. 2430 [GMPLS-G709] D. Papadimitriou (Editor), "Generalized MPLS 2431 Signalling Extensions for G.709 Optical Transport 2432 Networks Control", draft-ietf-ccamp-gmpls-g709, 2433 work in progress. 2435 13. Authors' Addresses 2437 Thomas D. Nadeau 2438 Cisco Systems, Inc. 2439 300 Apollo Drive 2440 Chelmsford, MA 01824 2441 Phone: +1-978-244-3051 2442 Email: tnadeau@cisco.com 2444 Cheenu Srinivasan 2445 Bloomberg L.P. 2446 731 Lexington Ave. 2447 New York, NY 10022 2448 Phone: +1-212-617-3682 2449 Email: cheenu@bloomberg.net 2451 Adrian Farrel 2452 Old Dog Consulting 2453 Phone: +44-(0)-1978-860944 2454 Email: adrian@olddog.co.uk 2456 Tim Hall 2457 Data Connection Ltd. 2458 100 Church Street 2459 Enfield, Middlesex 2460 EN2 6BQ, UK 2461 Phone: +44 20 8366 1177 2462 Email: tim.hall@dataconnection.com 2463 Ed Harrison 2464 Data Connection Ltd. 2465 100 Church Street 2466 Enfield, Middlesex 2467 EN2 6BQ, UK 2468 Phone: +44 20 8366 1177 2469 Email: ed.harrison@dataconnection.com 2471 14. Intellectual Property Considerations 2473 The IETF takes no position regarding the validity or scope of any 2474 Intellectual Property Rights or other rights that might be claimed to 2475 pertain to the implementation or use of the technology described in 2476 this document or the extent to which any license under such rights 2477 might or might not be available; nor does it represent that it has 2478 made any independent effort to identify any such rights. Information 2479 on the procedures with respect to rights in RFC documents can be 2480 found in BCP 78 and BCP 79. 2482 Copies of IPR disclosures made to the IETF Secretariat and any 2483 assurances of licenses to be made available, or the result of an 2484 attempt made to obtain a general license or permission for the use of 2485 such proprietary rights by implementers or users of this 2486 specification can be obtained from the IETF on-line IPR repository at 2487 http://www.ietf.org/ipr. 2489 The IETF invites any interested party to bring to its attention any 2490 copyrights, patents or patent applications, or other proprietary 2491 rights that may cover technology that may be required to implement 2492 this standard. Please address the information to the IETF at 2493 ietf-ipr@ietf.org. 2495 15. Full Copyright Statement 2497 Copyright (C) The Internet Society (2005). This document is subject 2498 to the rights, licenses and restrictions contained in BCP 78, and 2499 except as set forth therein, the authors retain all their rights. 2501 This document and the information contained herein are provided on an 2502 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2503 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2504 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2505 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2506 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2507 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.