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