idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-12.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 2845. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2818. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2825. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2831. ** 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 is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: When an entry is present in gmplsTunnelTable for a tunnel, gmplsTunnelPathComp MUST be used and any corresponding mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable MUST be ignored and SHOULD not be set. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 2005) is 6706 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RCF2205' is mentioned on line 481, but not defined == Missing Reference: 'RFC2434' is mentioned on line 2299, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2205' is defined on line 2676, but no explicit reference was found in the text Summary: 5 errors (**), 0 flaws (~~), 7 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: June 2006 Adrian Farrel, Ed. 5 Old Dog Consulting 7 December 2005 9 Generalized Multiprotocol Label Switching (GMPLS) Traffic 10 Engineering Management Information Base 12 draft-ietf-ccamp-gmpls-te-mib-12.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 .......................... 4 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 .................................. 6 55 5.3. gmplsTunnelARHopTable ................................ 6 56 5.4. gmplsTunnelCHopTable ................................. 6 57 5.5. gmplsTunnelErrorTable ................................ 6 58 5.6. gmplsTunnelReversePerfTable .......................... 6 59 5.7. Use of 32-bit and 64-bit Counters ................... 6 60 6. Cross-referencing to the gmplsLabelTable ............... 7 61 7. Example of GMPLS Tunnel Setup .......................... 7 62 8. GMPLS Traffic Engineering MIB Module .................. 11 63 9. Security Considerations ............................... 48 64 10. Acknowledgments ...................................... 49 65 11. IANA Considerations .................................. 49 66 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 50 67 11.2. Dependence on IANA MIB Modules ..................... 50 68 11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 50 69 12. References ........................................... 58 70 12.1. Normative References ............................... 59 71 12.2. Informative References ............................. 59 72 13. Contact Information .................................. 60 73 14. Intellectual Property Considerations ................. 60 74 15. Full Copyright Statement ............................. 61 76 1. Introduction 78 This memo defines a portion of the Management Information Base (MIB) 79 for use with network management protocols in the Internet community. 80 In particular, it describes managed objects for modeling 81 Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based 82 traffic engineering. The tables and objects defined in this document 83 extend those defined in the equivalent document for MPLS traffic 84 engineering [RFC3812], and management of GMPLS traffic engineering is 85 built on management of MPLS traffic engineering. 87 The MIB modules in this document should be used in conjunction with 88 the companion document [GMPLSLSRMIB] for GMPLS based traffic 89 engineering configuration and management. 91 Comments should be made direct to the CCAMP mailing list at 92 ccamp@ops.ietf.org. 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 96 document are to be interpreted as described in BCP 14, RFC 2119, 97 reference [RFC2119]. 99 1.1. Migration Strategy 101 MPLS-TE LSPs may be modeled and managed using the MPLS-TE-STD-MIB 102 module [RFC3812]. 104 LSRs may be migrated to model and manage their TE LSPs using the MIB 105 modules in this document in order to migrate the LSRs to GMPLS 106 support, or to take advandtage of additional MIB objects defined in 107 these MIB modules that are applicable to MPLS-TE. 109 The GMPLS TE MIB module (GMPLS-TE-STD-MIB) defined in this document 110 extends the MPLS-TE-STD-MIB module [RFC3812] through a series of 111 augmentations and sparse augmentations of the MIB tables. The only 112 additions are for support of GMPLS or to support the increased 113 complexity of MPLS and GMPLS systems. 115 In order to migrate from MPLS-TE-STD-MIB support to GMPLS-TE-STD-MIB 116 support an implementation needs only to add support for the 117 additional tables and objects defined in GMPLS-TE-STD-MIB. The 118 gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an 119 MPLS-TE LSP tunnel to benefit from the additional objects and tables 120 of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols. 122 The companion document for modeling and managing GMPLS based LSRs 123 [GMPLSLSRMIB] extends the MPLS-LSR-STD-MIB module [RFC3813] with the 124 same intentions. 126 Textual conventions are defined in [RFC3811] and [GMPLSTCMIB]. 128 2. Terminology 130 This document uses terminology from the MPLS architecture document 131 [RFC3031], from the GMPLS architecture document [RFC3945], and from 132 the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used 133 terms are described next. 135 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 136 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 137 LSRs, each segment being associated with one GMPLS enabled interface. 138 These are also referred to as tunnel segments. 140 Additionally, at an intermediate LSR, we model a connection as 141 consisting of one or more in-segments and/or one or more 142 out-segments. The binding or interconnection between in-segments and 143 out-segments in performed using a cross-connect. 145 These segment and cross-connect objects are defined in the MPLS Label 146 Switch Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the 147 GMPLS Label Switch Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] for 148 the GMPLS-specific extensions to these objects. 150 3. The SNMP Management Framework 152 For a detailed overview of the documents that describe the current 153 Internet-Standard Management Framework, please refer to section 7 of 154 RFC 3410 [RFC3410]. 156 Managed objects are accessed via a virtual information store, termed 157 the Management Information Base or MIB. MIB objects are generally 158 accessed through the Simple Network Management Protocol (SNMP). 159 Objects in the MIB are defined using the mechanisms defined in the 160 Structure of Management Information (SMI). This memo specifies a MIB 161 module that is compliant to the SMIv2, which is described in STD 58, 162 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 163 [RFC2580]. 165 4. Outline 167 Support for GMPLS traffic-engineered tunnels requires the following 168 configuration. 170 - Setting up tunnels with appropriate MPLS configuration parameters 171 using [RFC3812]. 172 - Extending the tunnels with GMPLS configuration parameters. 173 - Configuring tunnel loose and strict source routed hops. 175 These actions may need to be accompanied with corresponding actions 176 using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel 177 segments, if this is done manually. Also, the in-segment and 178 out-segment performance tables, mplsInSegmentPerfTable and 179 mplsOutSegmentPerfTable [RFC3813], should be used to determine 180 performance of the tunnels and tunnel segments although it should be 181 noted that those tables may not be appropriate for measuring 182 performance on some types of GMPLS links. 184 4.1. Summary of GMPLS Traffic Engineering MIB Module 186 The following tables contain MIB objects for performing the actions 187 listed above when they cannot be performed solely using MIB objects 188 defined in MPLS-TE-STD-MIB [RFC3812]. 190 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 191 tunnel configuration parameters. 193 - Tunnel specified, actual, and computed hop tables 194 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 195 gmplsTunnelCHopTable) for providing additional configuration of 196 strict and loose source routed tunnel hops. 197 - Performance and error reporting tables (gmplsTunnelReversePerfTable 198 and gmplsTunnelErrorTable). 200 These tables are described in the subsequent sections. 202 Additionally, the GMPLS-TE-STD-MIB module contains a new 203 notification. 205 - The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be used 206 for all GMPLS tunnels in place of the mplsTunnelDown notification 207 defined in [RFC3812]. An implementation must not issue both the 208 gmplsTunnelDown and the mplsTunnelDown notifications for the same 209 event. As well as indicating that a tunnel has transitioned to 210 operational down state, this new notification indicates the cause 211 of the failure. 213 5. Brief Description of GMPLS TE MIB Objects 215 The objects described in this section support the functionality 216 described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables 217 support both manually configured and signaled tunnels. 219 5.1. gmplsTunnelTable 221 The gmplsTunnelTable extends the MPLS traffic engineering MIB module 222 (MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created 223 between an LSR and a remote endpoint, and existing GMPLS tunnels to 224 be reconfigured or removed. 226 Note that we only support point-to-point tunnel segments, although 227 multi-point-to-point and point-to-multi-point connections are 228 supported by an LSR acting as a cross-connect. 230 Each tunnel can thus have one out-segment originating at an LSR 231 and/or one in-segment terminating at that LSR. 233 Three objects within this table utilize enumerations in order to map 234 to enumerations that are used in GMPLS signaling. In order to protect 235 the GMPLS-TE-STD-MIB module from changes (in particular, extensions) 236 to the range of enumerations supported by the signaling protocols, 237 these MIB objects use Textual Conventions with values maintained by 238 IANA. For further details, see the IANA Considerations section of 239 this document. 241 5.2. gmplsTunnelHopTable 243 The gmplsTunnelHopTable is used to indicate additional parameters for 244 the hops, strict or loose, of a GMPLS tunnel defined in 245 gmplsTunnelTable, when it is established using signaling. Multiple 246 tunnels may share hops by pointing to the same entry in this table. 248 5.3. gmplsTunnelARHopTable 250 The gmplsTunnelARHopTable is used to indicate the actual hops 251 traversed by a tunnel as reported by the signaling protocol after the 252 tunnel is setup. The support of this table is optional since not all 253 GMPLS signaling protocols support this feature. 255 5.4. gmplsTunnelCHopTable 257 The gmplsTunnelCHopTable lists the actual hops computed by a 258 constraint-based routing algorithm based on the gmplsTunnelHopTable. 259 The support of this table is optional since not all implementations 260 support computation of hop lists using a constraint-based routing 261 protocol. 263 5.5. gmplsTunnelErrorTable 265 The gmplsTunnelErrorTable provides access to information about the 266 last error that occurred on each tunnel known about by the MIB. It 267 indicates the nature of the error, when and how it was reported and 268 can give recovery advice through an admin string. 270 5.6. gmplsTunnelReversePerfTable 272 gmplsTunnelReversePerfTable provides additional counters to measure 273 the performance of bidirectional GMPLS tunnels in which packets are 274 visible. It supplements the counters in mplsTunnelPerfTable and 275 augments gmplsTunnelTable. 277 Note that not all counters may be appropriate or available for some 278 types of tunnel. 280 5.7. Use of 32-bit and 64-bit Counters 282 64-bit counters are provided in the GMPLS-TE-STD-MIB module for 283 high-speed interfaces where the use of 32-bit counters might be 284 impractical. The requirements on the use of 32-bit and 64-bit 285 counters (copied verbatim from [RFC2863]) are as follows: 287 For interfaces that operate at 20,000,000 (20 million) bits per 288 second or less, 32-bit byte and packet counters MUST be supported. 289 For interfaces that operate faster than 20,000,000 bits/second, and 290 slower than 650,000,000 bits/second, 32-bit packet counters MUST be 291 supported and 64-bit octet counters MUST be supported. For 292 interfaces that operate at 650,000,000 bits/second or faster, 64-bit 293 packet counters AND 64-bit octet counters MUST be supported. 295 6. Cross-referencing to the gmplsLabelTable 297 The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in 298 [GMPLSLSRMIB] and provides a way to model labels in a GMPLS system 299 where labels might not be simple 32 bit integers. 301 The hop tables in this document (gmplsHopTable, gmplsCHopTable and 302 gmplsARHopTable) and the segment tables in the [RFC3813] 303 (mplsInSegmentTable and mplsOutSegmentTable) contain objects with 304 syntax MplsLabel. 306 MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable 307 of representing any MPLS label and most GMPLS labels. However, some 308 GMPLS labels are larger than 32 bits and may be of arbitrary length. 309 Further, some labels that may be safely encoded in 32 bits are 310 constructed from multiple sub-fields. Additionally, some GMPLS 311 technologies support the concatenation of individual labels to 312 represent a data flow carried as multiple sub-flows. 314 These GMPLS cases require that something other than a simple 32-bit 315 integer is made available to represent the labels. This is achieved 316 through the gmplsLabelTable contained in the GMPLS-LABEL-STD-MIB 317 [GMPLSLSRMIB]. 319 The tables in this document and [RFC3813] that include objects with 320 syntax MplsLabel also include companion objects that are row 321 pointers. If the row pointer is set to zeroDotZero (0.0) then object 322 of syntax MplsLabel contains the label encoded as a 32-bit integer. 323 But otherwise the row pointer indicates a row in another MIB table 324 that includes the label. In these cases, the row pointer may indicate 325 a row in the gmplsLabelTable. 327 This provides both a good way to support legacy systems that 328 implement the MPLS-TE-STD-MIB [RFC3812], and a significant 329 simplification in GMPLS systems that are limited to a single, simple 330 label type. 332 Note that gmplsLabelTable supports concatenated labels through the 333 use of a label sub-index (gmplsLabelSubindex). 335 7. Example of GMPLS Tunnel Setup 337 This section contains an example of which MIB objects should be 338 modified to create a GMPLS tunnel. This example shows a best effort, 339 loosely routed, bidirectional traffic engineered tunnel, which spans 340 two hops of a simple network, uses Generalized Label requests with 341 Lambda encoding, has label recording and shared link layer 342 protection. Note that these objects should be created on the 343 "head-end" LSR. 345 First in the mplsTunnelTable: 347 { 348 mplsTunnelIndex = 1, 349 mplsTunnelInstance = 1, 350 mplsTunnelIngressLSRId = 192.0.2.1, 351 mplsTunnelEgressLSRId = 192.0.2.2, 352 mplsTunnelName = "My first tunnel", 353 mplsTunnelDescr = "Here to there and back again", 354 mplsTunnelIsIf = true (1), 355 mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, 356 mplsTunnelSignallingProto = none (1), 357 mplsTunnelSetupPrio = 0, 358 mplsTunnelHoldingPrio = 0, 359 mplsTunnelSessionAttributes = recordRoute (4), 360 mplsTunnelOwner = snmp (2), 361 mplsTunnelLocalProtectInUse = false (2), 362 mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, 363 mplsTunnelInstancePriority = 1, 364 mplsTunnelHopTableIndex = 1, 365 mplsTunnelPrimaryInstance = 0, 366 mplsTunnelIncludeAnyAffinity = 0, 367 mplsTunnelIncludeAllAffinity = 0, 368 mplsTunnelExcludeAnyAffinity = 0, 369 mplsTunnelPathInUse = 1, 370 mplsTunnelRole = head(1), 371 mplsTunnelRowStatus = createAndWait (5), 372 } 374 In gmplsTunnelTable(1,1,192.0.2.1,192.0.2.2): 375 { 376 gmplsTunnelUnnumIf = true (1), 377 gmplsTunnelAttributes = labelRecordingRequired (1), 378 gmplsTunnelLSPEncoding = tunnelLspLambda, 379 gmplsTunnelSwitchingType = lsc, 380 gmplsTunnelLinkProtection = shared (2), 381 gmplsTunnelGPid = lambda, 382 gmplsTunnelSecondary = false (2), 383 gmplsTunnelDirection = bidirectional (1) 384 gmplsTunnelPathComp = explicit(2), 385 gmplsTunnelRequestedUpstreamNotifyRecipientType = ipv4(1), 386 gmplsTunnelRequestedUpstreamNotifyRecipient = 'C0A86401'H, 387 gmplsTunnelAdminStatusFlags = 0, 388 gmplsTunnelExtraParamsPtr = 0.0 389 } 391 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 392 gmplsTunnelHopTable are created and activated at this time. 394 In mplsTunnelResourceTable: 395 { 396 mplsTunnelResourceIndex = 6, 397 mplsTunnelResourceMaxRate = 0, 398 mplsTunnelResourceMeanRate = 0, 399 mplsTunnelResourceMaxBurstSize = 0, 400 mplsTunnelResourceRowStatus = createAndGo (4) 401 } 403 The next two instances of mplsTunnelHopEntry are used to denote the 404 hops this tunnel will take across the network. 406 The following denotes the beginning of the network, or the first hop. 407 We have used the fictitious LSR identified by "192.0.2.1" as our 408 example head-end router. 410 In mplsTunnelHopTable: 411 { 412 mplsTunnelHopListIndex = 1, 413 mplsTunnelPathOptionIndex = 1, 414 mplsTunnelHopIndex = 1, 415 mplsTunnelHopAddrType = ipV4 (1), 416 mplsTunnelHopIpv4Addr = 192.0.2.1, 417 mplsTunnelHopIpv4PrefixLen = 9, 418 mplsTunnelHopType = strict (1), 419 mplsTunnelHopRowStatus = createAndWait (5), 420 } 422 The following denotes the end of the network, or the last hop in our 423 example. We have used the fictitious LSR identified by 424 "192.0.2.2" as our tail end router. 426 In mplsTunnelHopTable: 427 { 428 mplsTunnelHopListIndex = 1, 429 mplsTunnelPathOptionIndex = 1, 430 mplsTunnelHopIndex = 2, 431 mplsTunnelHopAddrType = ipV4 (1), 432 mplsTunnelHopIpv4Addr = 192.0.2.2, 433 mplsTunnelHopIpv4PrefixLen = 9, 434 mplsTunnelHopType = loose (2), 435 mplsTunnelHopRowStatus = createAndGo (4) 436 } 437 Now an associated entry in the gmplsTunnelHopTable is created to 438 provide additional GMPLS hop configuration indicating that the first 439 hop is an unnumbered link using explicit forward and reverse labels. 440 An entry in the gmplsLabelTable is created first to include the 441 explicit label. 443 In gmplsLabelTable: 444 { 445 gmplsLabelInterface = 2, 446 gmplsLabelIndex = 1, 447 gmplsLabelSubindex = 0, 448 gmplsLabelType = gmplsFreeformLabel(3), 449 gmplsLabelFreeform = 0xFEDCBA9876543210 450 gmplsLabelRowStatus = createAndGo(4) 451 } 453 In gmplsTunnelHopTable(1,1,1): 454 { 455 gmplsTunnelHopLabelStatuses = forwardPresent(0) 456 +reversePresent(1), 457 gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable (2, 1, 0) 458 gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable (2, 1, 0) 459 } 461 The first hop is now activated: 463 In mplsTunnelHopTable(1,1,1): 464 { 465 mplsTunnelHopRowStatus = active (1) 466 } 468 No gmplsTunnelHopEntry is created for the second hop as it contains 469 no special GMPLS features. 471 Finally the mplsTunnelEntry is activated: 473 In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2) 474 { 475 mplsTunnelRowStatus = active(1) 476 } 478 8. GMPLS Traffic Engineering MIB Module 480 This MIB module makes references to the following documents. 481 [RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], 482 [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202] 483 and [GMPLS-G709]. 485 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 487 IMPORTS 488 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 489 Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32 490 FROM SNMPv2-SMI -- RFC2578 491 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 492 FROM SNMPv2-CONF -- RFC2580 493 TruthValue, TimeStamp, RowPointer 494 FROM SNMPv2-TC -- RFC2579 495 InetAddress, InetAddressType 496 FROM INET-ADDRESS-MIB -- RFC4001 497 SnmpAdminString 498 FROM SNMP-FRAMEWORK-MIB -- RFC3411 499 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 500 mplsTunnelEgressLSRId, mplsTunnelHopListIndex, 501 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, 502 mplsTunnelARHopListIndex, mplsTunnelARHopIndex, 503 mplsTunnelCHopListIndex, mplsTunnelCHopIndex, 504 mplsTunnelEntry, 505 mplsTunnelAdminStatus, mplsTunnelOperStatus 506 FROM MPLS-TE-STD-MIB -- RFC3812 507 IANAGmplsLSPEncodingType, IANAGmplsSwitchingType, 508 IANAGmplsGeneralizedPid, IANAGmplsAdminStatusInformation 509 FROM IANA-GMPLS-TC-MIB 510 mplsStdMIB 511 FROM MPLS-TC-STD-MIB -- RFC3811 512 ; 514 gmplsTeStdMIB MODULE-IDENTITY 515 LAST-UPDATED 516 "200510130001Z" -- 13 October 2005 00:00:01 GMT 517 ORGANIZATION 518 "IETF Common Control And Measurement Plane (CCAMP) Working 519 Group" 520 CONTACT-INFO 521 " Thomas D. Nadeau 522 Cisco Systems, Inc. 523 Email: tnadeau@cisco.com 524 Adrian Farrel 525 Old Dog Consulting 526 Email: adrian@olddog.co.uk 528 Comments about this document should be emailed direct to the 529 CCAMP working group mailing list at ccamp@ops.ietf.org" 531 DESCRIPTION 532 "Copyright (C) The Internet Society (2005). This version of 533 this MIB module is part of RFC xxxx; see the RFC itself for 534 full legal notices. 535 -- RFC Ed. Please replace xxxx above with the correct RFC number and 536 -- remove this note. 538 This MIB module contains managed object definitions 539 for GMPLS Traffic Engineering (TE) as defined in: 540 1. Generalized Multi-Protocol Label Switching (GMPLS) 541 Signaling Functional Description, Berger, L. (Editor), 542 RFC 3471, January 2003. 543 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 544 L. (Editor), RFC 3473, January 2003." 546 REVISION 547 "200510130001Z" -- 13 October 2005 00:00:01 GMT 548 DESCRIPTION 549 "Initial version issued as part of RFC xxxx." 550 ::= { mplsStdMIB XXX } 551 -- RFC Editor. Please replace xxxx above with the correct RFC number and 552 -- remove this note. 554 -- RFC Editor. Please replace XXX above with the OID assigned by IANA 555 -- and remove this note 557 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 558 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } 559 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } 560 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } 562 gmplsTunnelsConfigured OBJECT-TYPE 563 SYNTAX Gauge32 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "The number of GMPLS tunnels configured on this device. A GMPLS 568 tunnel is considered configured if an entry for the tunnel 569 exists in the gmplsTunnelTable and the associated 570 mplsTunnelRowStatus is active(1)." 571 ::= { gmplsTeScalars 1 } 572 gmplsTunnelsActive OBJECT-TYPE 573 SYNTAX Gauge32 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "The number of GMPLS tunnels active on this device. A GMPLS 578 tunnel is considered active if there is an entry in the 579 gmplsTunnelTable and the associated mplsTunnelOperStatus for the 580 tunnel is up(1)." 581 ::= { gmplsTeScalars 2 } 583 gmplsTunnelTable OBJECT-TYPE 584 SYNTAX SEQUENCE OF GmplsTunnelEntry 585 MAX-ACCESS not-accessible 586 STATUS current 587 DESCRIPTION 588 "The gmplsTunnelTable sparse augments the mplsTunnelTable of 589 MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between 590 an LSR and a remote endpoint, and existing tunnels to be 591 reconfigured or removed. 593 Note that only point-to-point tunnel segments are supported, 594 although multi-point-to-point and point-to-multi-point 595 connections are supported by an LSR acting as a cross-connect. 596 Each tunnel can thus have one out-segment originating at this 597 LSR and/or one in-segment terminating at this LSR. 599 The row status of an entry in this table is controlled by 600 mplsTunnelRowStatus in the corresponding entry in 601 mplsTunnelTable. When the corresponding mplsTunnelRowStatus has 602 value active(1) a row in this table may not be created or 603 modified. 605 The exception to this rule is the 606 gmplsTunnelAdminStatusInformation object, which can be modified 607 whilst the tunnel is active." 608 REFERENCE 609 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 610 Management Information Base (MIB), RFC 3812." 611 ::= { gmplsTeObjects 1 } 612 gmplsTunnelEntry OBJECT-TYPE 613 SYNTAX GmplsTunnelEntry 614 MAX-ACCESS not-accessible 615 STATUS current 616 DESCRIPTION 617 "An entry in this table in association with the corresponding 618 entry in the mplsTunnelTable represents a GMPLS tunnel. 620 An entry can be created by a network administrator via SNMP SET 621 commands, or in response to signaling protocol events." 622 INDEX { 623 mplsTunnelIndex, 624 mplsTunnelInstance, 625 mplsTunnelIngressLSRId, 626 mplsTunnelEgressLSRId 627 } 628 ::= { gmplsTunnelTable 1 } 630 GmplsTunnelEntry ::= SEQUENCE { 631 gmplsTunnelUnnumIf TruthValue, 632 gmplsTunnelAttributes BITS, 633 gmplsTunnelLSPEncoding IANAGmplsLSPEncodingType, 634 gmplsTunnelSwitchingType IANAGmplsSwitchingType, 635 gmplsTunnelLinkProtection BITS, 636 gmplsTunnelGPid IANAGmplsGeneralizedPid, 637 gmplsTunnelSecondary TruthValue, 638 gmplsTunnelDirection INTEGER, 639 gmplsTunnelPathComp INTEGER, 640 gmplsTunnelUpstreamNotifyRecipientType InetAddressType, 641 gmplsTunnelUpstreamNotifyRecipient InetAddress, 642 gmplsTunnelSendResvNotifyRecipientType InetAddressType, 643 gmplsTunnelSendResvNotifyRecipient InetAddress, 644 gmplsTunnelDownstreamNotifyRecipientType InetAddressType, 645 gmplsTunnelDownstreamNotifyRecipient InetAddress, 646 gmplsTunnelSendPathNotifyRecipientType InetAddressType, 647 gmplsTunnelSendPathNotifyRecipient InetAddress, 648 gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformation, 649 gmplsTunnelExtraParamsPtr RowPointer 650 } 651 gmplsTunnelUnnumIf OBJECT-TYPE 652 SYNTAX TruthValue 653 MAX-ACCESS read-create 654 STATUS current 655 DESCRIPTION 656 "Denotes whether or not this tunnel corresponds to an unnumbered 657 interface represented by an entry in the interfaces group table 658 (the ifTable) with ifType set to mpls (166). 660 This object is only used if mplsTunnelIsIf is set to 'true'. 662 If both this object and the mplsTunnelIsIf object are set to 663 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID 664 object to the outgoing Path message. 666 This object contains information that is only used by the 667 terminating LSR." 668 REFERENCE 669 "1. Signalling Unnumbered Links in RSVP-TE, RFC 3477." 670 DEFVAL { false } 671 ::= { gmplsTunnelEntry 1 } 673 gmplsTunnelAttributes OBJECT-TYPE 674 SYNTAX BITS { 675 labelRecordingDesired (0) 676 } 677 MAX-ACCESS read-create 678 STATUS current 679 DESCRIPTION 680 "This bitmask indicates optional parameters for this tunnel. 681 These bits should be taken in addition to those defined in 682 mplsTunnelSessionAttributes in order to determine the full set 683 of options to be signaled (for example SESSION_ATTRIBUTES flags 684 in RSVP-TE). The following describes these bitfields: 686 labelRecordingDesired 687 This flag is set to indicate that label information should be 688 included when doing a route record. This bit is not valid 689 unless the recordRoute bit is set." 690 REFERENCE 691 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 692 sections 4.4.3, 4.7.1 and 4.7.2." 693 DEFVAL { { } } 694 ::= { gmplsTunnelEntry 2 } 695 gmplsTunnelLSPEncoding OBJECT-TYPE 696 SYNTAX IANAGmplsLSPEncodingType 697 MAX-ACCESS read-create 698 STATUS current 699 DESCRIPTION 700 "This object indicates the encoding of the LSP being requested. 702 A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is 703 not in use. Some objects in this MIB module may be of use for 704 MPLS signaling extensions that do not use GMPLS signaling. By 705 setting this object to 'tunnelLspNotGmpls', an application may 706 indicate that only those objects meaningful in MPLS should be 707 examined. 709 The values to use are defined in the textual convention 710 IANAGmplsLSPEncodingType found in the IANA-GMPLS-TC-MIB module." 711 DEFVAL { tunnelLspNotGmpls } 712 ::= { gmplsTunnelEntry 3 } 714 gmplsTunnelSwitchingType OBJECT-TYPE 715 SYNTAX IANAGmplsSwitchingType 716 MAX-ACCESS read-create 717 STATUS current 718 DESCRIPTION 719 "Indicates the type of switching that should be performed on 720 a particular link. This field is needed for links that 721 advertise more than one type of switching capability. 723 The values to use are defined in the textual convention 724 IANAGmplsSwitchingType found in the IANA-GMPLS-TC-MIB module. 726 This object is only meaningful if gmplsTunnelLSPEncoding is not 727 set to 'tunnelLspNotGmpls'." 728 DEFVAL { unknown } 729 ::= { gmplsTunnelEntry 4 } 730 gmplsTunnelLinkProtection OBJECT-TYPE 731 SYNTAX BITS { 732 extraTraffic(0), 733 unprotected(1), 734 shared (2), 735 dedicatedOneToOne (3), 736 dedicatedOnePlusOne(4), 737 enhanced(5) 738 } 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "This bitmask indicates the level of link protection required. A 743 value of zero (no bits set) indicates that any protection may be 744 used. The following describes these bitfields: 746 extraTraffic 747 This flag is set to indicate that the LSP should use links 748 that are protecting other (primary) traffic. Such LSPs may be 749 preempted when the links carrying the (primary) traffic being 750 protected fail. 752 unprotected 753 This glag is set to indicate that the LSP should not use any 754 link layer protection. 756 shared 757 This flage is set to indicate that a shared link layer 758 protection scheme, such as 1:N protection, should be used to 759 support the LSP. 761 dedicatedOneToOne 762 This flag is set to indicate that a dedicated link layer 763 protection scheme, i.e., 1:1 protection, should be used to 764 support the LSP. 766 dedicatedOnePlusOne 767 This flag is set to indicate that a dedicated link layer 768 protection scheme, i.e., 1+1 protection, should be used to 769 support the LSP. 771 enhanced 772 This flag is set to indicate that a protection scheme that is 773 more reliable than Dedicated 1+1 should be used, e.g., 4 fiber 774 BLSR/MS-SPRING. 776 This object is only meaningful if gmplsTunnelLSPEncoding is 777 not set to 'tunnelLspNotGmpls'." 779 REFERENCE 780 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 781 Functional Description, RFC 3471, section 7.1." 782 DEFVAL { { } } 783 ::= { gmplsTunnelEntry 5 } 785 gmplsTunnelGPid OBJECT-TYPE 786 SYNTAX IANAGmplsGeneralizedPid 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "This object indicates the payload carried by the LSP. It is only 791 required when GMPLS will be used for this LSP. 793 The values to use are defined in the textual convention 794 IANAGmplsGeneralizedPid found in the IANA-GMPLS-TC-MIB module. 796 This object is only meaningful if gmplsTunnelLSPEncoding is not 797 set to 'tunnelLspNotGmpls'." 798 DEFVAL { unknown } 799 ::= { gmplsTunnelEntry 6 } 801 gmplsTunnelSecondary OBJECT-TYPE 802 SYNTAX TruthValue 803 MAX-ACCESS read-create 804 STATUS current 805 DESCRIPTION 806 "Indicates that the requested LSP is a secondary LSP. 808 This object is only meaningful if gmplsTunnelLSPEncoding is not 809 set to 'tunnelLspNotGmpls'." 810 REFERENCE 811 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 812 Functional Description, RFC 3471, section 7.1." 813 DEFVAL { false } 814 ::= { gmplsTunnelEntry 7 } 816 gmplsTunnelDirection OBJECT-TYPE 817 SYNTAX INTEGER { 818 forward (0), 819 bidirectional (1) 820 } 821 MAX-ACCESS read-create 822 STATUS current 823 DESCRIPTION 824 "Whether this tunnel carries forward data only (is 825 unidirectional) or is bidirectional. 827 Values of this object other than 'forward' are meaningful 828 only if gmplsTunnelLSPEncoding is not set to 829 'tunnelLspNotGmpls'." 830 DEFVAL { forward } 831 ::= { gmplsTunnelEntry 8 } 833 gmplsTunnelPathComp OBJECT-TYPE 834 SYNTAX INTEGER { 835 dynamicFull(1), -- CSPF fully computed 836 explicit(2), -- fully specified path 837 dynamicPartial(3) -- CSPF partially computed 838 } 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "This value instructs the source node on how to perform path 843 computation on the explicit route specified by the associated 844 entries in the gmplsTunnelHopTable. 846 dynamicFull 847 The user specifies at least the source and 848 destination of the path and expects that the CSPF 849 will calculate the remainder of the path. 851 explicit 852 The user specifies the entire path for the tunnel to 853 take. This path may contain strict or loose hops. 854 Evaluation of the explicit route will be performed 855 hop by hop through the network. 857 dynamicPartial 858 The user specifies at least the source and 859 destination of the path and expects that the CSPF 860 will calculate the remainder of the path. The path 861 computed by CSPF is allowed to be only partially 862 computed allowing the remainder of the path to be 863 filled in across the network. 865 When an entry is present in gmplsTunnelTable for a tunnel, 866 gmplsTunnelPathComp MUST be used and any corresponding 867 mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable 868 MUST be ignored and SHOULD not be set. 870 mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of 871 MPLS-TE-STD-MIB." 872 REFERENCE 873 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 874 Management Information Base (MIB), RFC 3812." 875 DEFVAL { dynamicFull } 876 ::= { gmplsTunnelEntry 9 } 877 gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE 878 SYNTAX InetAddressType 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "This object is used to aid in interpretation of 883 gmplsTunnelUpstreamNotifyRecipient." 884 DEFVAL { unknown } 885 ::= { gmplsTunnelEntry 10 } 887 gmplsTunnelUpstreamNotifyRecipient OBJECT-TYPE 888 SYNTAX InetAddress 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "Indicates the address of the upstream recipient for Notify 893 messages relating to this tunnel and issued by this LSR. This 894 information is typically received from an upstream LSR in a Path 895 message. 897 This object is only valid when signaling a tunnel using RSVP. 899 It is also not valid at the head end of a tunnel since there are 900 no upstream LSRs to which to send a Notify message. 902 This object is interpreted in the context of the value of 903 gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0, 904 the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to 905 unknown(0)." 906 REFERENCE 907 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 908 section 4.2." 909 DEFVAL { '00000000'H } -- 0.0.0.0 910 ::= { gmplsTunnelEntry 11 } 912 gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE 913 SYNTAX InetAddressType 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "This object is used to aid in interpretation of 918 gmplsTunnelSendResvNotifyRecipient." 919 DEFVAL { unknown } 920 ::= { gmplsTunnelEntry 12 } 921 gmplsTunnelSendResvNotifyRecipient OBJECT-TYPE 922 SYNTAX InetAddress 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "Indicates to an upstream LSR the address to which it should send 927 downstream Notify messages relating to this tunnel. 929 This object is only valid when signaling a tunnel using RSVP. 931 It is also not valid at the head end of the tunnel since no Resv 932 messages are sent from that LSR for this tunnel. 934 If set to 0, no Notify Request object will be included in the 935 outgoing Resv messages. 937 This object is interpreted in the context of the value of 938 gmplsTunnelSendResvNotifyRecipientType. If this object is set to 939 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be 940 set to unknown(0)." 941 REFERENCE 942 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 943 section 4.2." 944 DEFVAL { '00000000'H } -- 0.0.0.0 945 ::= { gmplsTunnelEntry 13 } 947 gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE 948 SYNTAX InetAddressType 949 MAX-ACCESS read-create 950 STATUS current 951 DESCRIPTION 952 "This object is used to aid in interpretation of 953 gmplsTunnelDownstreamNotifyRecipient." 954 DEFVAL { unknown } 955 ::= { gmplsTunnelEntry 14 } 957 gmplsTunnelDownstreamNotifyRecipient OBJECT-TYPE 958 SYNTAX InetAddress 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "Indicates the address of the downstream recipient for Notify 963 messages relating to this tunnel and issued by this LSR. This 964 information is typically received from an upstream LSR in a Resv 965 message. This object is only valid when signaling a tunnel using 966 RSVP. 968 It is also not valid at the tail end of a tunnel since there are 969 no downstream LSRs to which to send a Notify message. 971 This object is interpreted in the context of the value of 972 gmplsTunnelDownstreamNotifyRecipient. If this object is set to 973 0, the value of gmplsTunnelDownstreamNotifyRecipient MUST be set 974 to unknown(0)." 975 REFERENCE 976 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 977 section 4.2." 978 DEFVAL { '00000000'H } -- 0.0.0.0 979 ::= { gmplsTunnelEntry 15 } 981 gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE 982 SYNTAX InetAddressType 983 MAX-ACCESS read-create 984 STATUS current 985 DESCRIPTION 986 "This object is used to aid in interpretation of 987 gmplsTunnelSendPathNotifyRecipient." 988 DEFVAL { unknown } 989 ::= { gmplsTunnelEntry 16 } 991 gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE 992 SYNTAX InetAddress 993 MAX-ACCESS read-create 994 STATUS current 995 DESCRIPTION 996 "Indicates to a downstream LSR the address to which it should 997 send upstream Notify messages relating to this tunnel. 999 This object is only valid when signaling a tunnel using RSVP. 1001 It is also not valid at the tail end of the tunnel since no Path 1002 messages are sent from that LSR for this tunnel. 1004 If set to 0, no Notify Request object will be included in the 1005 outgoing Path messages. 1007 This object is interpreted in the context of the value of 1008 gmplsTunnelSendPathNotifyRecipientType. If this object is set to 1009 0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be 1010 set to unknown(0)." 1012 REFERENCE 1013 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1014 section 4.2." 1015 DEFVAL { '00000000'H } -- 0.0.0.0 1016 ::= { gmplsTunnelEntry 17 } 1017 gmplsTunnelAdminStatusFlags OBJECT-TYPE 1018 SYNTAX IANAGmplsAdminStatusInformation 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION 1022 "Determines the setting of the Admin Status flags in the 1023 Admin Status object or TLV, as described in RFC 3471. Setting 1024 this field to a non-zero value will result in the inclusion of 1025 the admin status object on signaling messages. 1027 The values to use are defined in the textual convention 1028 IANAGmplsAdminStatusInformation found in the IANA-GMPLS-TC-MIB 1029 module. 1031 This value of this object can be modified when the 1032 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 1033 is active(1). By doing so, a new signaling message will be 1034 triggered including the requested Admin Status object or 1035 TLV." 1036 REFERENCE 1037 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1038 Functional Description, RFC 3471, section 8." 1039 DEFVAL { { } } 1040 ::= { gmplsTunnelEntry 18 } 1042 gmplsTunnelExtraParamsPtr OBJECT-TYPE 1043 SYNTAX RowPointer 1044 MAX-ACCESS read-create 1045 STATUS current 1046 DESCRIPTION 1047 "Some Tunnels will run over transports that can usefully support 1048 technology-specific additional parameters (for example, SONET 1049 resource usage). Such parameters can be supplied in an external 1050 table and referenced from here. 1052 A value of zeroDotzero in this attribute indicates that there 1053 is no such additional information." 1054 DEFVAL { zeroDotZero } 1055 ::= { gmplsTunnelEntry 19 } 1057 gmplsTunnelHopTable OBJECT-TYPE 1058 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "The gmplsTunnelHopTable sparse augments the mplsTunnelHopTable 1063 of MPLS-TE-STD-MIB. It is used to indicate the explicit labels 1064 to be used in an explicit path for a GMPLS tunnel defined in 1065 mplsTunnelTable and gmplsTunnelTable, when it is established 1066 using signaling. It does not insert new hops, but does define 1067 new values for hops defined in mplsTunnelHopTable. 1069 Each row in this table is indexed by the same indexes as 1070 mplsTunnelHopTable. It is acceptable for some rows in 1071 mplsTunnelHopTable to have corresponding entries in this table 1072 and some to have no corresponding entry in this table. 1074 The storage type for this entry is given by the value 1075 of mplsTunnelHopStorageType in the corresponding entry in the 1076 mplsTunnelHopTable. 1078 The row status of an entry in this table is controlled by 1079 mplsTunnelHopRowStatus in the corresponding entry in 1080 mplsTunnelHopTable. That is, it is not permitted to create a row 1081 in this table, nor to modify an existing row, when the 1082 corresponding mplsTunnelHopRowStatus has value active(1)." 1083 REFERENCE 1084 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1085 Management Information Base (MIB), RFC 3812. 1086 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 1087 ::= { gmplsTeObjects 2 } 1089 gmplsTunnelHopEntry OBJECT-TYPE 1090 SYNTAX GmplsTunnelHopEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "An entry in this table represents additions to a tunnel hop 1095 defined in mplsTunnelHopEntry. At an ingress to a tunnel an 1096 entry in this table is created by a network administrator for an 1097 ERLSP to be set up by a signaling protocol. At transit and 1098 egress nodes an entry in this table may be used to represent the 1099 explicit path instructions received using the signaling 1100 protocol." 1101 INDEX { 1102 mplsTunnelHopListIndex, 1103 mplsTunnelHopPathOptionIndex, 1104 mplsTunnelHopIndex 1105 } 1106 ::= { gmplsTunnelHopTable 1 } 1108 GmplsTunnelHopEntry ::= SEQUENCE { 1109 gmplsTunnelHopLabelStatuses BITS, 1110 gmplsTunnelHopExplicitForwardLabel Unsigned32, 1111 gmplsTunnelHopExplicitForwardLabelPtr RowPointer, 1112 gmplsTunnelHopExplicitReverseLabel Unsigned32, 1113 gmplsTunnelHopExplicitReverseLabelPtr RowPointer 1114 } 1115 gmplsTunnelHopLabelStatuses OBJECT-TYPE 1116 SYNTAX BITS { 1117 forwardPresent (0), 1118 reversePresent (1) 1119 } 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "This bitmask indicates the presence of labels indicated by the 1124 gmplsTunnelHopExplicitForwardLabel or 1125 gmplsTunnelHopExplicitForwardLabelPtr, and 1126 gmplsTunnelHopExplicitReverseLabel or 1127 gmplsTunnelHopExplicitReverseLabel objects. 1129 For the Present bits, a set bit indicates that a label is 1130 present for this hop in the route. This allows zero to be a 1131 valid label value." 1132 DEFVAL { { } } 1133 ::= { gmplsTunnelHopEntry 1 } 1135 gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE 1136 SYNTAX Unsigned32 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "If gmplsTunnelHopLabelStatuses object indicates that a forward 1141 label is present and gmplsTunnelHopExplicitForwardLabelPtr 1142 contains the value zeroDotZero, then the label to use on this 1143 hop is represented by the value of this object." 1144 ::= { gmplsTunnelHopEntry 2 } 1146 gmplsTunnelHopExplicitForwardLabelPtr OBJECT-TYPE 1147 SYNTAX RowPointer 1148 MAX-ACCESS read-create 1149 STATUS current 1150 DESCRIPTION 1151 "If the gmplsTunnelHopLabelStatuses object indicates that a 1152 forward label is present, this object contains a pointer to a 1153 row in another MIB table (such as the gmplsLabelTable of 1154 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1155 in the forward direction. 1157 If the gmplsTunnelHopLabelStatuses object indicates that a 1158 forward label is present and this object contains the value 1159 zeroDotZero, then the label to use on this hop is found in the 1160 gmplsTunnelHopExplicitForwardLabel object." 1161 DEFVAL { zeroDotZero } 1162 ::= { gmplsTunnelHopEntry 3 } 1163 gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE 1164 SYNTAX Unsigned32 1165 MAX-ACCESS read-create 1166 STATUS current 1167 DESCRIPTION 1168 "If the gmplsTunnelHopLabelStatuses object indicates that a 1169 reverse label is present and 1170 gmplsTunnelHopExplicitReverseLabelPtr contains the value 1171 zeroDotZero, then the label to use on this this hop is found in 1172 this object encoded as a 32-bit integer." 1173 ::= { gmplsTunnelHopEntry 4 } 1175 gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE 1176 SYNTAX RowPointer 1177 MAX-ACCESS read-create 1178 STATUS current 1179 DESCRIPTION 1180 "If the gmplsTunnelHopLabelStatuses object indicates that a 1181 reverse label is present, this object contains a pointer to a 1182 row in another MIB table (such as the gmplsLabelTable of the 1183 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1184 in the reverse direction. 1186 If the gmplsTunnelHopLabelStatuses object indicates that a 1187 reverse label is present and this object contains the value 1188 zeroDotZero, then the label to use on this hop is found in the 1189 gmplsTunnelHopExplicitReverseLabel object." 1190 DEFVAL { zeroDotZero } 1191 ::= { gmplsTunnelHopEntry 5 } 1193 gmplsTunnelARHopTable OBJECT-TYPE 1194 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 1195 MAX-ACCESS not-accessible 1196 STATUS current 1197 DESCRIPTION 1198 "The gmplsTunnelARHopTable sparse augments the 1199 mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate 1200 the labels currently in use for a GMPLS tunnel defined in 1201 mplsTunnelTable and gmplsTunnelTable, as reported by the 1202 signaling protocol. It does not insert new hops, but does define 1203 new values for hops defined in mplsTunnelARHopTable. 1205 Each row in this table is indexed by the same indexes as 1206 mplsTunnelARHopTable. It is acceptable for some rows in 1207 mplsTunnelARHopTable to have corresponding entries in this table 1208 and some to have no corresponding entry in this table. 1210 Note that since the information necessary to build entries 1211 within this table is not provided by some signaling protocols 1212 and might not be returned in all cases of other signaling 1213 protocols, implementation of this table and mplsTunnelARHopTable 1214 is optional. Furthermore, since the information in this table is 1215 actually provided by the signaling protocol after the path has 1216 been set-up, the entries in this table are provided only for 1217 observation, and hence, all variables in this table are 1218 accessible exclusively as read-only." 1220 REFERENCE 1221 "1. Extensions to RSVP for LSP Tunnels, RFC 3209. 1222 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 1223 3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1224 Management Information Base (MIB), RFC 3812. 1225 ::= { gmplsTeObjects 3 } 1227 gmplsTunnelARHopEntry OBJECT-TYPE 1228 SYNTAX GmplsTunnelARHopEntry 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "An entry in this table represents additions to a tunnel hop 1233 visible in mplsTunnelARHopEntry. An entry is created by the 1234 signaling protocol for a signaled ERLSP set up by the signaling 1235 protocol. 1237 At any node on the LSP (ingress, transit or egress), this table 1238 and mplsTunnelARHopTable (if the tables are supported and if the 1239 signaling protocol is recording actual route information) 1240 contain the actual route of the whole tunnel. If the signaling 1241 protocol is not recording the actual route, this table MAY 1242 report the information from the gmplsTunnelHopTable or the 1243 gmplsTunnelCHopTable. 1245 Note that the recording of actual labels is distinct from the 1246 recording of the actual route in some signaling protocols. This 1247 feature is enabled using the gmplsTunnelAttributes object." 1248 INDEX { 1249 mplsTunnelARHopListIndex, 1250 mplsTunnelARHopIndex 1251 } 1252 ::= { gmplsTunnelARHopTable 1 } 1253 GmplsTunnelARHopEntry ::= SEQUENCE { 1254 gmplsTunnelARHopLabelStatuses BITS, 1255 gmplsTunnelARHopExplicitForwardLabel Unsigned32, 1256 gmplsTunnelARHopExplicitForwardLabelPtr RowPointer, 1257 gmplsTunnelARHopExplicitReverseLabel Unsigned32, 1258 gmplsTunnelARHopExplicitReverseLabelPtr RowPointer, 1259 gmplsTunnelARHopProtection BITS 1260 } 1262 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1263 SYNTAX BITS { 1264 forwardPresent (0), 1265 reversePresent (1), 1266 forwardGlobal (2), 1267 reverseGlobal (3) 1268 } 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "This bitmask indicates the presence and status of labels 1273 indicated by the gmplsTunnelARHopExplicitForwardLabel or 1274 gmplsTunnelARHopExplicitForwardLabelPtr, and 1275 gmplsTunnelARHopExplicitReverseLabel or 1276 gmplsTunnelARHopExplicitReverseLabelPtr objects. 1278 For the Present bits, a set bit indicates that a label is 1279 present for this hop in the route. For the Global bits, a set 1280 bit indicates that the label comes from the Global Label Space. 1281 A clear bit indicates that this is a Per-Interface label. A 1282 Global bit only has meaning if the corresponding Present bit is 1283 set." 1284 ::= { gmplsTunnelARHopEntry 1 } 1286 gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE 1287 SYNTAX Unsigned32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1292 forward label is present and 1293 gmplsTunnelARHopExplicitForwardLabelPtr contains the value 1294 zeroDotZero, then the label in use on this hop is found in this 1295 object encoded within a 32-bit integer." 1296 ::= { gmplsTunnelARHopEntry 2 } 1297 gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE 1298 SYNTAX RowPointer 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1303 forward label is present, this object contains a pointer to a 1304 row in another MIB table (such as the gmplsLabelTable of the 1305 GMPLS-LABEL-STD-MIB) that contains the label in use on this hop 1306 in the forward direction. 1308 If the gmplsTunnelARHopLabelStatuses object indicates that a 1309 forward label is present and this object contains the value 1310 zeroDotZero, then the label in use on this hop is found in the 1311 gmplsTunnelARHopExplicitForwardLabel object." 1312 ::= { gmplsTunnelARHopEntry 3 } 1314 gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE 1315 SYNTAX Unsigned32 1316 MAX-ACCESS read-only 1317 STATUS current 1318 DESCRIPTION 1319 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1320 reverse label is present and 1321 gmplsTunnelARHopExplicitReverseLabelPtr contains the value 1322 zeroDotZero, then the label in use on this hop is found in this 1323 object encoded as a 32-bit integer." 1324 ::= { gmplsTunnelARHopEntry 4 } 1326 gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE 1327 SYNTAX RowPointer 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1332 reverse label is present, this object contains a pointer to a 1333 row in another MIB table (such as the gmplsLabelTable of the 1334 GMPLS-LABEL-STD-MIB) that contains the label in use on this hop 1335 in the reverse direction. 1337 If the gmplsTunnelARHopLabelStatuses object indicates that a 1338 reverse label is present and this object contains the value 1339 zeroDotZero, then the label in use on this hop is found in the 1340 gmplsTunnelARHopExplicitReverseLabel object." 1341 ::= { gmplsTunnelARHopEntry 5 } 1342 gmplsTunnelARHopProtection OBJECT-TYPE 1343 SYNTAX BITS { 1344 localAvailable (0), 1345 localInUse (1) 1346 } 1347 MAX-ACCESS read-only 1348 STATUS current 1349 DESCRIPTION 1350 "Availability and usage of protection on the reported link. 1352 localAvailable 1353 This flag is set to indicate that the link downstream of this 1354 node is protected via a local repair mechanism. 1356 localInUse 1357 This flag is set to indicate that a local repair mechanism is 1358 in use to maintain this tunnel (usually in the face of an 1359 outage of the link it was previously routed over)." 1360 REFERENCE 1361 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1362 section 4.4.1." 1363 ::= { gmplsTunnelARHopEntry 6 } 1365 gmplsTunnelCHopTable OBJECT-TYPE 1366 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1367 MAX-ACCESS not-accessible 1368 STATUS current 1369 DESCRIPTION 1370 "The gmplsTunnelCHopTable sparse augments the mplsTunnelCHopTable 1371 of MPLS-TE-STD-MIB. It is used to indicate additional 1372 information about the hops of a GMPLS tunnel defined in 1373 mplsTunnelTable and gmplsTunnelTable, as computed by a 1374 constraint-based routing protocol, based on the 1375 mplsTunnelHopTable and the gmplsTunnelHopTable. 1377 Each row in this table is indexed by the same indexes as 1378 mplsTunnelCHopTable. It is acceptable for some rows in 1379 mplsTunnelCHopTable to have corresponding entries in this table 1380 and some to have no corresponding entry in this table. 1382 Please note that since the information necessary to build 1383 entries within this table may not be supported by some LSRs, 1384 implementation of this table is optional. 1386 Furthermore, since the information in this table is actually 1387 provided by a path computation component after the path has been 1388 computed, the entries in this table are provided only for 1389 observation, and hence, all objects in this table are accessible 1390 exclusively as read-only." 1392 REFERENCE 1393 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1394 Management Information Base (MIB), RFC 3812. 1395 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 1396 ::= { gmplsTeObjects 4 } 1398 gmplsTunnelCHopEntry OBJECT-TYPE 1399 SYNTAX GmplsTunnelCHopEntry 1400 MAX-ACCESS not-accessible 1401 STATUS current 1402 DESCRIPTION 1403 "An entry in this table represents additions to a computed tunnel 1404 hop visible in mplsTunnelCHopEntry. An entry is created by a 1405 path computation component based on the hops specified in the 1406 corresponding mplsTunnelHopTable and gmplsTunnelHopTable. 1408 At a transit LSR this table (if the table is supported) MAY 1409 contain the path computed by path computation engine on (or on 1410 behalf of) the transit LSR." 1411 INDEX { 1412 mplsTunnelCHopListIndex, 1413 mplsTunnelCHopIndex 1414 } 1415 ::= { gmplsTunnelCHopTable 1 } 1417 GmplsTunnelCHopEntry ::= SEQUENCE { 1418 gmplsTunnelCHopLabelStatuses BITS, 1419 gmplsTunnelCHopExplicitForwardLabel Unsigned32, 1420 gmplsTunnelCHopExplicitForwardLabelPtr RowPointer, 1421 gmplsTunnelCHopExplicitReverseLabel Unsigned32, 1422 gmplsTunnelCHopExplicitReverseLabelPtr RowPointer 1423 } 1425 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1426 SYNTAX BITS { 1427 forwardPresent (0), 1428 reversePresent (1) 1429 } 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "This bitmask indicates the presence of labels indicated by the 1434 gmplsTunnelCHopExplicitForwardLabel or 1435 gmplsTunnelCHopExplicitForwardLabelPtr and 1436 gmplsTunnelCHopExplicitReverseLabel or 1437 gmplsTunnelCHopExplicitReverseLabelPtr objects. 1438 A set bit indicates that a label is present for this hop in the 1439 route thus allowing zero to be a valid label value." 1440 ::= { gmplsTunnelCHopEntry 1 } 1441 gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE 1442 SYNTAX Unsigned32 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1447 forward label is present and 1448 gmplsTunnelCHopExplicitForwardLabelPtr contains the value 1449 zeroDotZero, then the label to use on this hop is found in this 1450 object encoded within a 32-bit integer." 1451 ::= { gmplsTunnelCHopEntry 2 } 1453 gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE 1454 SYNTAX RowPointer 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1459 forward label is present, this object contains a pointer to a 1460 row in another MIB table (such as the gmplsLabelTable of the 1461 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1462 in the forward direction. 1464 If the gmplsTunnelCHopLabelStatuses object indicates that a 1465 forward label is present and this object contains the value 1466 zeroDotZero, then the label to use on this hop is found in the 1467 gmplsTunnelCHopExplicitForwardLabel object." 1468 ::= { gmplsTunnelCHopEntry 3 } 1470 gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE 1471 SYNTAX Unsigned32 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1476 reverse label is present and 1477 gmplsTunnelCHopExplicitReverseLabelPtr contains the value 1478 zeroDotZero, then the label to use on this hop is found in this 1479 object encoded as a 32-bit integer." 1480 ::= { gmplsTunnelCHopEntry 4 } 1481 gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE 1482 SYNTAX RowPointer 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1487 reverse label is present, this object contains a pointer to a 1488 row in another MIB table (such as the gmplsLabelTable of the 1489 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1490 in the reverse direction. 1492 If the gmplsTunnelCHopLabelStatuses object indicates that a 1493 reverse label is present and this object contains the value 1494 zeroDotZero, then the label to use on this hop is found in the 1495 gmplsTunnelCHopExplicitReverseLabel object." 1496 ::= { gmplsTunnelCHopEntry 5 } 1498 gmplsTunnelReversePerfTable OBJECT-TYPE 1499 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1500 MAX-ACCESS not-accessible 1501 STATUS current 1502 DESCRIPTION 1503 "This table 'augments' the gmplsTunnelTable to provides 1504 per-tunnel packet performance information for the reverse 1505 direction of a bidirectional tunnel. It can be seen as 1506 supplementing the mplsTunnelPerfTable which augments the 1507 mplsTunnelTable. 1509 For links that do not transport packets, these packet counters 1510 cannot be maintained. For such links, attempts to read the 1511 objects in this table will return noSuchInstance. 1513 A tunnel can be known to be bidirectional by inspecting the 1514 gmplsTunnelDirection object." 1515 REFERENCE 1516 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1517 Management Information Base (MIB), RFC 3812." 1518 ::= { gmplsTeObjects 5 } 1520 gmplsTunnelReversePerfEntry OBJECT-TYPE 1521 SYNTAX GmplsTunnelReversePerfEntry 1522 MAX-ACCESS not-accessible 1523 STATUS current 1524 DESCRIPTION 1525 "An entry in this table is created by the LSR for every 1526 bidirectional GMPLS tunnel where packets are visible to the 1527 LSR." 1528 AUGMENTS { gmplsTunnelEntry } 1529 ::= { gmplsTunnelReversePerfTable 1 } 1530 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1531 gmplsTunnelReversePerfPackets Counter32, 1532 gmplsTunnelReversePerfHCPackets Counter64, 1533 gmplsTunnelReversePerfErrors Counter32, 1534 gmplsTunnelReversePerfBytes Counter32, 1535 gmplsTunnelReversePerfHCBytes Counter64 1536 } 1538 gmplsTunnelReversePerfPackets OBJECT-TYPE 1539 SYNTAX Counter32 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "Number of packets forwarded on the tunnel in the reverse 1544 direction if it is bidirectional. 1546 This object should represents the 32-bit value of the least 1547 significant part of the 64-bit value if both 1548 gmplsTunnelReversePerfHCPackets and this object are returned. 1550 For links that do not transport packets, this packet counter 1551 cannot be maintained. For such links, this value will return a 1552 noSuchInstance." 1553 ::= { gmplsTunnelReversePerfEntry 1 } 1555 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1556 SYNTAX Counter64 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "High capacity counter for number of packets forwarded on the 1561 tunnel in the reverse direction if it is bidirectional. 1563 For links that do not transport packets, this packet counter 1564 cannot be maintained. For such links, this value will return a 1565 noSuchInstance." 1566 ::= { gmplsTunnelReversePerfEntry 2 } 1568 gmplsTunnelReversePerfErrors OBJECT-TYPE 1569 SYNTAX Counter32 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "Number of errored packets received on the tunnel in the reverse 1574 direction if it is bidirectional. For links that do not 1575 transport packets, this packet counter cannot be maintained. For 1576 such links, this value will return a noSuchInstance." 1577 ::= { gmplsTunnelReversePerfEntry 3 } 1578 gmplsTunnelReversePerfBytes OBJECT-TYPE 1579 SYNTAX Counter32 1580 MAX-ACCESS read-only 1581 STATUS current 1582 DESCRIPTION 1583 "Number of bytes forwarded on the tunnel in the reverse direction 1584 if it is bidirectional. 1586 This object should represents the 32-bit value of the least 1587 significant part of the 64-bit value if both 1588 gmplsTunnelReversePerfHCBytes and this object are returned. 1590 For links that do not transport packets, this packet counter 1591 cannot be maintained. For such links, this value will return a 1592 noSuchInstance." 1593 ::= { gmplsTunnelReversePerfEntry 4 } 1595 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1596 SYNTAX Counter64 1597 MAX-ACCESS read-only 1598 STATUS current 1600 DESCRIPTION 1601 "High capacity counter for number of bytes forwarded on the 1602 tunnel in the reverse direction if it is bidirectional. 1604 For links that do not transport packets, this packet counter 1605 cannot be maintained. For such links, this value will return a 1606 noSuchInstance." 1607 ::= { gmplsTunnelReversePerfEntry 5 } 1609 gmplsTunnelErrorTable OBJECT-TYPE 1610 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1611 MAX-ACCESS not-accessible 1612 STATUS current 1613 DESCRIPTION 1614 "This table 'augments' the mplsTunnelTable 1615 This table provides per-tunnel information about errors. Errors 1616 may be detected locally or reported through the signaling 1617 protocol. Error reporting is not exclusive to GMPLS and this 1618 table may be applied in MPLS systems. 1620 Entries in this table are not persistent over system resets 1621 or re-initializations of the management system." 1622 REFERENCE 1623 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1624 Management Information Base (MIB), RFC 3812." 1625 ::= { gmplsTeObjects 6 } 1626 gmplsTunnelErrorEntry OBJECT-TYPE 1627 SYNTAX GmplsTunnelErrorEntry 1628 MAX-ACCESS not-accessible 1629 STATUS current 1630 DESCRIPTION 1631 "An entry in this table is created by the LSR for every tunnel 1632 where error information is visible to the LSR. 1634 Note that systems which read the objects in this table one at a 1635 time may experience a discontinuity as the result of a new error 1636 occurring in between object reads. Systems that are vulnerable 1637 to this should read gmplsTunnelErrorLastTime before and after 1638 reading the other objects." 1639 AUGMENTS { mplsTunnelEntry } 1640 ::= { gmplsTunnelErrorTable 1 } 1642 GmplsTunnelErrorEntry ::= SEQUENCE { 1643 gmplsTunnelErrorLastErrorType INTEGER, 1644 gmplsTunnelErrorLastTime TimeStamp, 1645 gmplsTunnelErrorReporterType InetAddressType, 1646 gmplsTunnelErrorReporter InetAddress, 1647 gmplsTunnelErrorCode Unsigned32, 1648 gmplsTunnelErrorSubcode Unsigned32, 1649 gmplsTunnelErrorTLVs OCTET STRING, 1650 gmplsTunnelErrorHelpString SnmpAdminString 1651 } 1653 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1654 SYNTAX INTEGER { 1655 noError (0), 1656 unknown (1), 1657 protocol (2), 1658 pathComputation (3), 1659 localConfiguration (4), 1660 localResources (5), 1661 localOther (6) 1662 } 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "The nature of the last error. Provides interpretation context 1667 for gmplsTunnelErrorProtocolCode and 1668 gmplsTunnelErrorProtocolSubcode. 1670 A value of noError (0) shows that there is no error associated 1671 with this tunnel and means that the other objects in this table 1672 entry have no meaning. 1674 A value of unknown (1) shows that there is an error but that no 1675 additional information about the cause is known. The error may 1676 have been received in a signaled message or generated locally. 1678 A value of protocol (2) or pathComputation (3) indicates the 1679 cause of an error and identifies an error that has been received 1680 through signaling or will itself be signaled. 1682 A value of localConfiguration (4), localResources (5) or 1683 localOther (6) identifies an error which has been detected 1684 by the local node, but which will not be reported through 1685 signaling." 1686 ::= { gmplsTunnelErrorEntry 1 } 1688 gmplsTunnelErrorLastTime OBJECT-TYPE 1689 SYNTAX TimeStamp 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "The time at which the last error occurred. This is presented as 1694 the value of SysUpTime when the error occurred or was reported 1695 to this node. 1697 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1698 this object is ignored. 1700 Note that entries in this table are not persistent over system 1701 resets or re-initializations of the management system." 1702 ::= { gmplsTunnelErrorEntry 2 } 1704 gmplsTunnelErrorReporterType OBJECT-TYPE 1705 SYNTAX InetAddressType 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "The address type of the error reported. 1711 This object is used to aid in interpretation of 1712 gmplsTunnelErrorReporter." 1713 ::= { gmplsTunnelErrorEntry 3 } 1715 gmplsTunnelErrorReporter OBJECT-TYPE 1716 SYNTAX InetAddress 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "The address of the node reporting the last error, or the address 1721 of the resource (such as an interface) associated with the 1722 error. 1724 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1725 this object is ignored. 1727 If gmplsTunnelErrorLastErrorType has the value unknown (1), 1728 localConfiguration (4), localResources (5), or localOther (6) 1729 this object MAY contain a zero value. 1731 This object should be interpreted in the context of the value of 1732 the object gmplsTunnelErrorReporterType." 1733 REFERENCE 1734 "1. Textual Conventions for Internet Network Addresses, RFC 4001, 1735 section 4, Usage Hints." 1736 ::= { gmplsTunnelErrorEntry 4 } 1738 gmplsTunnelErrorCode OBJECT-TYPE 1739 SYNTAX Unsigned32 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1743 "The primary error code associated with the last error. 1744 The interpretation of this error code depends on the value of 1745 gmplsTunnelErrorLastErrorType. If the value of 1746 gmplsTunnelErrorLastErrorType is noError (0) the value of this 1747 object should be 0 and should be ignored. If the value of 1748 gmplsTunnelErrorLastErrorType is protocol (2) the error should 1749 be interpreted in the context of the signling protocol 1750 identified by the mplsTunnelSignallingProto object." 1751 REFERENCE 1752 "1. Resource ReserVation Protocol -- Version 1 Functional 1753 Specification, RFC 2205, section B. 1754 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1755 section 7.3. 1756 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1757 section 13.1." 1758 ::= { gmplsTunnelErrorEntry 5 } 1760 gmplsTunnelErrorSubcode OBJECT-TYPE 1761 SYNTAX Unsigned32 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "The secondary error code associated with the last error and the 1766 protocol used to signal this tunnel. This value is interpreted 1767 in the context of the value of gmplsTunnelErrorCode. 1768 If the value of gmplsTunnelErrorLastErrorType is noError (0) the 1769 value of this object should be 0 and should be ignored." 1770 REFERENCE 1771 "1. Resource ReserVation Protocol -- Version 1 Functional 1772 Specification, RFC 2205, section B. 1774 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1775 section 7.3. 1776 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1777 section 13.1." 1778 ::= { gmplsTunnelErrorEntry 6 } 1780 gmplsTunnelErrorTLVs OBJECT-TYPE 1781 SYNTAX OCTET STRING (SIZE(0..65535)) 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "The sequence of interface identifier TLVs reported with the 1786 error by the protocol code. The interpretation of the TLVs and 1787 the encoding within the protocol are described in the 1788 references. A value of zero in the first octet indicates that no 1789 TLVs are present." 1790 REFERENCE 1791 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1792 section 8.2." 1793 ::= { gmplsTunnelErrorEntry 7 } 1795 gmplsTunnelErrorHelpString OBJECT-TYPE 1796 SYNTAX SnmpAdminString 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "A textual string containing information about the last error, 1801 recovery actions and support advice. If there is no help string 1802 this object contains a zero length string. 1803 If the value of gmplsTunnelErrorLastErrorType is noError (0) 1804 this object should contain a zero length string, but may contain 1805 a help string indicating that there is no error." 1806 ::= { gmplsTunnelErrorEntry 8 } 1808 -- 1809 -- Notifications 1810 -- 1812 gmplsTunnelDown NOTIFICATION-TYPE 1813 OBJECTS { 1814 mplsTunnelAdminStatus, 1815 mplsTunnelOperStatus, 1816 gmplsTunnelErrorLastErrorType, 1817 gmplsTunnelErrorReporterType, 1818 gmplsTunnelErrorReporter, 1819 gmplsTunnelErrorCode, 1820 gmplsTunnelErrorSubcode 1821 } 1822 STATUS current 1823 DESCRIPTION 1824 "This notification is generated when a mplsTunnelOperStatus 1825 object for a tunnel in the gmplsTunnelTable is about to enter 1826 the down state from some other state (but not from the 1827 notPresent state). This other state is indicated by the 1828 included value of mplsTunnelOperStatus. 1830 The objects in this notification provide additional error 1831 information that indicates the reason why the tunnel has 1832 transitioned down. 1834 Note that an implementation MUST only issue one of 1835 mplsTunnelDown and gmplsTunnelDown for any single event on a 1836 single tunnel. If the tunnel has an entry in gmplsTunnelTable 1837 an implementation SHOULD use gmplsTunnelDown for all tunnel 1838 down events and SHOULD NOT use mplsTunnelDown. 1840 This notification is subject to the control of the 1841 mplsTunnelNotificationEnable. When that object is set to 1842 false(2) then the notification must not be issued. 1844 Further, this notification is also subject to 1845 mplsTunnelNotificationMaxRate. That object indicates the 1846 maximum number of notifications issued per second. If events 1847 occur more rapidly, the implementation may simply fail to emit 1848 some notifications during that period, or may queue them until 1849 an appropriate time. The notification rate applies to the sum 1850 of all notificaitons in the MPLS-TE-STD-MIB and 1851 GMPLS-TE-STD-MIB modules applied across the whole of the 1852 reporting device. 1854 mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, 1855 mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate 1856 objects are found in MPLS-TE-STD-MIB." 1857 REFERENCE 1858 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering 1859 (TE) Management Information Base (MIB), RFC 3812." 1860 ::= { gmplsTeNotifications 1 } 1862 gmplsTeGroups 1863 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1865 gmplsTeCompliances 1866 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1868 -- Compliance requirement for fully compliant implementations. 1869 -- The mandatory group has to be implemented by all LSRs that 1870 -- originate, terminate or act as transit for TE-LSPs/tunnels. 1871 -- In addition, depending on the type of tunnels supported, other 1872 -- groups become mandatory as explained below. 1874 gmplsTeModuleFullCompliance MODULE-COMPLIANCE 1875 STATUS current 1876 DESCRIPTION 1877 "Compliance statement for agents that provide full support for 1878 GMPLS-TE-STD-MIB. Such devices can then be monitored and also 1879 be configured using this MIB module." 1881 MODULE -- this module 1882 MANDATORY-GROUPS { 1883 gmplsTunnelGroup, 1884 gmplsTunnelScalarGroup, 1885 gmplsTunnelSignaledGroup 1886 } 1887 ::= { gmplsTeCompliances 1 } 1889 -- Compliance requirement for read-only compliant implementations. 1891 gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 1892 STATUS current 1893 DESCRIPTION 1894 "Compliance requirement for implementations that only provide 1895 read-only support for GMPLS-TE-STD-MIB. Such devices can then be 1896 monitored but cannot be configured using this MIB module." 1898 MODULE -- this module 1900 -- The mandatory group has to be implemented by all LSRs that 1901 -- originate, terminate or act as transit for TE-LSPs/tunnels. 1902 -- In addition, depending on the type of tunnels supported, other 1903 -- groups become mandatory as explained below. 1905 MANDATORY-GROUPS { 1906 gmplsTunnelGroup, 1907 gmplsTunnelScalarGroup 1908 } 1910 GROUP gmplsTunnelSignaledGroup 1911 DESCRIPTION 1912 "This group is mandatory for devices which support signaled 1913 tunnel set up, in addition to gmplsTunnelGroup. The following 1914 constraints apply: 1915 mplsTunnelSignallingProto should be at least read-only 1916 returning a value of ldp(2), or rsvp(3)." 1918 GROUP gmplsTunnelIsNotIntfcGroup 1919 DESCRIPTION 1920 "This group is mandatory for devices which support tunnels that 1921 are not interfaces, in addition to gmplsTunnelGroup. The 1922 following constraints apply: 1923 mplsTunnelIsIf must at least be read-only returning no(0)." 1925 GROUP gmplsTunnelIsIntfcGroup 1926 DESCRIPTION 1927 "This group is mandatory for devices which support tunnels that 1928 are interfaces, in addition to gmplsTunnelGroup." 1930 GROUP gmplsTunnelOptionalGroup 1931 DESCRIPTION 1932 "Objects in this group are optional." 1934 GROUP gmplsTeNotificationGroup 1935 DESCRIPTION 1936 "This group is mandatory for those implementations which can 1937 implement the notifications contained in this group." 1939 -- All scalars have max access read-only 1941 OBJECT gmplsTunnelAttributes 1942 MIN-ACCESS read-only 1943 DESCRIPTION 1944 "Write access is not required." 1946 OBJECT gmplsTunnelLSPEncoding 1947 SYNTAX IANAGmplsLSPEncodingType 1948 MIN-ACCESS read-only 1949 DESCRIPTION 1950 "Write access is not required." 1952 OBJECT gmplsTunnelSwitchingType 1953 SYNTAX IANAGmplsSwitchingType 1954 MIN-ACCESS read-only 1955 DESCRIPTION 1956 "Write access is not required." 1958 OBJECT gmplsTunnelLinkProtection 1959 MIN-ACCESS read-only 1960 DESCRIPTION 1961 "Write access is not required." 1963 OBJECT gmplsTunnelGPid 1964 SYNTAX IANAGmplsGeneralizedPid 1965 MIN-ACCESS read-only 1966 DESCRIPTION 1967 "Write access is not required." 1969 OBJECT gmplsTunnelSecondary 1970 SYNTAX TruthValue 1971 MIN-ACCESS read-only 1972 DESCRIPTION 1973 "Write access is not required." 1975 OBJECT gmplsTunnelDirection 1976 SYNTAX INTEGER { 1977 forward (0), 1978 bidirectional (1) 1979 } 1980 MIN-ACCESS read-only 1981 DESCRIPTION 1982 "Only forward (0) is required." 1984 OBJECT gmplsTunnelPathComp 1985 SYNTAX INTEGER { 1986 dynamicFull(1), -- CSPF fully computed 1987 explicit(2), -- fully specified path 1988 dynamicPartial(3) -- CSPF partially computed 1989 } 1991 MIN-ACCESS read-only 1992 DESCRIPTION 1993 "Only explicit (2) is required." 1995 OBJECT gmplsTunnelUpstreamNotifyRecipientType 1996 SYNTAX InetAddressType 1997 MIN-ACCESS read-only 1998 DESCRIPTION 1999 "Write access is not required." 2001 OBJECT gmplsTunnelUpstreamNotifyRecipient 2002 SYNTAX InetAddress 2003 MIN-ACCESS read-only 2004 DESCRIPTION 2005 "Write access is not required." 2007 OBJECT gmplsTunnelSendResvNotifyRecipientType 2008 SYNTAX InetAddressType 2009 MIN-ACCESS read-only 2010 DESCRIPTION 2011 "Write access is not required." 2013 OBJECT gmplsTunnelSendResvNotifyRecipient 2014 SYNTAX InetAddress 2015 MIN-ACCESS read-only 2016 DESCRIPTION 2017 "Write access is not required." 2019 OBJECT gmplsTunnelDownstreamNotifyRecipientType 2020 SYNTAX InetAddressType 2021 MIN-ACCESS read-only 2022 DESCRIPTION 2023 "Write access is not required." 2025 OBJECT gmplsTunnelDownstreamNotifyRecipient 2026 SYNTAX InetAddress 2027 MIN-ACCESS read-only 2028 DESCRIPTION 2029 "Write access is not required." 2031 OBJECT gmplsTunnelSendPathNotifyRecipientType 2032 SYNTAX InetAddressType 2033 MIN-ACCESS read-only 2034 DESCRIPTION 2035 "Write access is not required." 2037 OBJECT gmplsTunnelSendPathNotifyRecipient 2038 SYNTAX InetAddress 2039 MIN-ACCESS read-only 2040 DESCRIPTION 2041 "Write access is not required." 2043 OBJECT gmplsTunnelAdminStatusFlags 2044 SYNTAX IANAGmplsAdminStatusInformation 2045 MIN-ACCESS read-only 2046 DESCRIPTION 2047 "Write access is not required." 2049 OBJECT gmplsTunnelExtraParamsPtr 2050 SYNTAX RowPointer 2051 MIN-ACCESS read-only 2052 DESCRIPTION 2053 "Write access is not required." 2055 -- gmplsTunnelHopLabelStatuses has max access read-only 2057 OBJECT gmplsTunnelHopExplicitForwardLabel 2058 MIN-ACCESS read-only 2059 DESCRIPTION 2060 "Write access is not required." 2062 OBJECT gmplsTunnelHopExplicitForwardLabelPtr 2063 MIN-ACCESS read-only 2064 DESCRIPTION 2065 "Write access is not required." 2067 OBJECT gmplsTunnelHopExplicitReverseLabel 2068 MIN-ACCESS read-only 2069 DESCRIPTION 2070 "Write access is not required." 2072 OBJECT gmplsTunnelHopExplicitReverseLabelPtr 2073 MIN-ACCESS read-only 2074 DESCRIPTION 2075 "Write access is not required." 2077 -- gmplsTunnelARHopTable 2078 -- all objects have max access read-only 2080 -- glmpsTunnelCHopTable 2081 -- all objects have max access read-only 2083 -- gmplsTunnelReversePerfTable 2084 -- all objects have max access read-only 2086 -- gmplsTunnelErrorTable 2087 -- all objects have max access read-only 2089 ::= { gmplsTeCompliances 2 } 2091 gmplsTunnelGroup OBJECT-GROUP 2092 OBJECTS { 2093 gmplsTunnelDirection, 2094 gmplsTunnelReversePerfPackets, 2095 gmplsTunnelReversePerfHCPackets, 2096 gmplsTunnelReversePerfErrors, 2097 gmplsTunnelReversePerfBytes, 2098 gmplsTunnelReversePerfHCBytes, 2099 gmplsTunnelErrorLastErrorType, 2100 gmplsTunnelErrorLastTime, 2101 gmplsTunnelErrorReporterType, 2102 gmplsTunnelErrorReporter, 2103 gmplsTunnelErrorCode, 2104 gmplsTunnelErrorSubcode, 2105 gmplsTunnelErrorTLVs, 2106 gmplsTunnelErrorHelpString 2107 } 2108 STATUS current 2109 DESCRIPTION 2110 "Necessary, but not sufficient, set of objects to implement 2111 tunnels. In addition, depending on the type of the tunnels 2112 supported (for example, manually configured or signaled, 2113 persistent or non-persistent, etc.), the following other 2114 groups defined below are mandatory: 2116 gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup 2117 and/or gmplsTunnelIsIntfcGroup." 2118 ::= { gmplsTeGroups 1 } 2120 gmplsTunnelSignaledGroup OBJECT-GROUP 2121 OBJECTS { 2122 gmplsTunnelAttributes, 2123 gmplsTunnelLSPEncoding, 2124 gmplsTunnelSwitchingType, 2125 gmplsTunnelLinkProtection, 2126 gmplsTunnelGPid, 2127 gmplsTunnelSecondary, 2128 gmplsTunnelPathComp, 2129 gmplsTunnelUpstreamNotifyRecipientType, 2130 gmplsTunnelUpstreamNotifyRecipient, 2131 gmplsTunnelSendResvNotifyRecipientType, 2132 gmplsTunnelSendResvNotifyRecipient, 2133 gmplsTunnelDownstreamNotifyRecipientType, 2134 gmplsTunnelDownstreamNotifyRecipient, 2135 gmplsTunnelSendPathNotifyRecipientType, 2136 gmplsTunnelSendPathNotifyRecipient, 2137 gmplsTunnelAdminStatusFlags, 2138 gmplsTunnelHopLabelStatuses, 2139 gmplsTunnelHopExplicitForwardLabel, 2140 gmplsTunnelHopExplicitForwardLabelPtr, 2141 gmplsTunnelHopExplicitReverseLabel, 2142 gmplsTunnelHopExplicitReverseLabelPtr 2143 } 2144 STATUS current 2145 DESCRIPTION 2146 "Objects needed to implement signaled tunnels." 2147 ::= { gmplsTeGroups 2 } 2149 gmplsTunnelScalarGroup OBJECT-GROUP 2150 OBJECTS { 2151 gmplsTunnelsConfigured, 2152 gmplsTunnelsActive 2153 } 2154 STATUS current 2155 DESCRIPTION 2156 "Scalar objects needed to implement MPLS tunnels." 2157 ::= { gmplsTeGroups 3 } 2158 gmplsTunnelIsIntfcGroup OBJECT-GROUP 2159 OBJECTS { 2160 gmplsTunnelUnnumIf 2161 } 2162 STATUS current 2163 DESCRIPTION 2164 "Objects needed to implement tunnels that are interfaces." 2165 ::= { gmplsTeGroups 4 } 2167 gmplsTunnelIsNotIntfcGroup OBJECT-GROUP 2168 OBJECTS { 2169 gmplsTunnelUnnumIf 2170 } 2171 STATUS current 2172 DESCRIPTION 2173 "Objects needed to implement tunnels that are not interfaces." 2174 ::= { gmplsTeGroups 5 } 2176 gmplsTunnelOptionalGroup OBJECT-GROUP 2177 OBJECTS { 2178 gmplsTunnelExtraParamsPtr, 2179 gmplsTunnelARHopLabelStatuses, 2180 gmplsTunnelARHopExplicitForwardLabel, 2181 gmplsTunnelARHopExplicitForwardLabelPtr, 2182 gmplsTunnelARHopExplicitReverseLabel, 2183 gmplsTunnelARHopExplicitReverseLabelPtr, 2184 gmplsTunnelARHopProtection, 2185 gmplsTunnelCHopLabelStatuses, 2186 gmplsTunnelCHopExplicitForwardLabel, 2187 gmplsTunnelCHopExplicitForwardLabelPtr, 2188 gmplsTunnelCHopExplicitReverseLabel, 2189 gmplsTunnelCHopExplicitReverseLabelPtr 2190 } 2191 STATUS current 2192 DESCRIPTION 2193 "The objects in this group are optional." 2194 ::= { gmplsTeGroups 6 } 2196 gmplsTeNotificationGroup NOTIFICATION-GROUP 2197 NOTIFICATIONS { 2198 gmplsTunnelDown 2199 } 2200 STATUS current 2201 DESCRIPTION 2202 "Set of notifications implemented in this module. None is 2203 mandatory." 2204 ::= { gmplsTeGroups 7 } 2206 END 2208 9. Security Considerations 2210 It is clear that the MIB modules described in this document in 2211 association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful 2212 for monitoring of MPLS and GMPLS tunnels. These MIB modules can also 2213 be used for configuration of certain objects, and anything that can 2214 be configured can be incorrectly configured, with potentially 2215 disastrous results. 2217 There are a number of management objects defined in these MIB modules 2218 with a MAX-ACCESS clause of read-write and/or read-create. Such 2219 objects may be considered sensitive or vulnerable in some network 2220 environments. The support for SET operations in a non-secure 2221 environment without proper protection can have a negative effect on 2222 network operations. These are the tables and objects and their 2223 sensitivity/vulnerability: 2225 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 2226 objects to provision GMPLS tunnels interfaces at their ingress 2227 LSRs. Unauthorized write access to objects in these tables, could 2228 result in disruption of traffic on the network. This is especially 2229 true if a tunnel has already been established. 2231 Some of the readable objects in these MIB modules (i.e., objects with 2232 a MAX-ACCESS other than not-accessible) may be considered sensitive 2233 or vulnerable in some network environments. It is thus important to 2234 control even GET and/or NOTIFY access to these objects and possibly 2235 to even encrypt the values of these objects when sending them over 2236 the network via SNMP. These are the tables and objects and their 2237 sensitivity/vulnerability: 2239 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 2240 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, 2241 gmplsTunnelErrorTable collectively show the tunnel network 2242 topology and status. If an Administrator does not want to reveal 2243 this information, then these tables should be considered 2244 sensitive/vulnerable. 2246 SNMP versions prior to SNMPv3 did not include adequate security. Even 2247 if the network itself is secure (for example by using IPSec), even 2248 then, there is no control as to who on the secure network is allowed 2249 to access and GET/SET (read/change/create/delete) the objects in 2250 these MIB modules. 2252 It is RECOMMENDED that implementers consider the security features as 2253 provided by the SNMPv3 framework (see [RFC3410], section 8), 2254 including full support for the SNMPv3 cryptographic mechanisms (for 2255 authentication and privacy). 2257 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2258 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2259 enable cryptographic security. It is then a customer/operator 2260 responsibility to ensure that the SNMP entity giving access to an 2261 instance of this MIB module, is properly configured to give access to 2262 the objects only to those principals (users) that have legitimate 2263 rights to indeed GET or SET (change/create/delete) them. 2265 10. Acknowledgments 2267 This document is a product of the CCAMP Working Group. 2269 This document extends [RFC3812]. The authors would like to express 2270 their gratitude to all those who worked on that earlier MIB document. 2271 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 2272 contributions during an early implementation, and to Baktha 2273 Muralidharan, Tom Petch, Dave Thaler and Bert Wijnen for their review 2274 comments. 2276 Special thanks to Joan Cucchiara and Len Nieman for their help with 2277 compilation issues. 2279 Joan Cucchiara provided a helpful and very thorough MIB Doctor 2280 review. 2282 11. IANA Considerations 2284 -- (Note to RFC-Editor:) 2285 -- We request that you assign contiguous RFC numbers to the three GMPLS 2286 -- MIB documents. 2287 -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to 2288 -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to 2289 -- draft-ietf-ccamp-gmpls-te-mib. 2290 -- (Please remove this note prior to publication.) 2292 IANA is requested to root MIB objects in the MIB module contained in 2293 this document under the mplsStdMIB subtree. 2295 In the future, GMPLS related standards track MIB modules should be 2296 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to 2297 manage that namespace in the SMI Numbers registry [RFC3811]. New 2298 assignments can only be made via a Standards Action as specified in 2299 [RFC2434]. 2301 11.1. IANA Considerations for GMPLS-TE-STD-MIB 2303 The IANA is requested to assign { mplsStdMIB XXX } to the 2304 GMPLS-TE-STD-MIB module specified in this document, and to record 2305 the assignment in the SMI Numbers registry. 2307 -- RFC Editor. Please replace XXX above with assigned OID and remove 2308 -- this note 2310 11.2. Dependence on IANA MIB Modules 2312 Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, 2313 gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual 2314 conventions imported from the IANA-GMPLS-TC-MIB. The purpose of 2315 defining these textual conventions in a separate MIB module is to 2316 allow additional values to be defined without having to issue a new 2317 version of this document. The Internet Assigned Numbers Authority 2318 (IANA) is responsible for the assignment of all Internet numbers; it 2319 will administer the values associated with these textual conventions. 2321 The rules for additions or changes to the IANA-GMPLS-TC-MIB are 2322 outlined in the DESCRIPTION clause associated with its 2323 MODULE-IDENTITY statement. 2325 The current versions of the IANA-GMPLS-TC-MIB can be accessed from 2326 the IANA home page at: "http://www.iana.org/". 2328 11.2.1. IANA-GMPLS-TC-MIB Definition 2330 This is a temporary section intended to supply the base definition of 2331 an IANA MIB module. The normal procedure is that this MIB module is 2332 moved into the direct control of IANA, at which time this section 2333 should be deleted from this document. 2335 IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module 2336 specified in this document as { transmission YYY }. 2338 -- RFC Editor. 2339 -- Please replace YYY above with assigned OID and remove this note. 2341 IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN 2343 IMPORTS 2344 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 2345 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 2347 ianaGmpls MODULE-IDENTITY 2348 LAST-UPDATED "200510130001Z" -- 13 October 2005 00:00:01 GMT 2349 ORGANIZATION "IANA" 2350 CONTACT-INFO 2351 " Internet Assigned Numbers Authority 2352 Postal: USC/Information Sciences Institute 2353 4676 Admiralty Way, Marina del Rey, CA 90292 2354 Tel: +1 310 822 1511 2355 E-Mail: iana@isi.edu" 2356 DESCRIPTION 2357 "Copyright (C) The Internet Society (2005). The initial version 2358 of this MIB module was published in RFC XXX. For full legal 2359 notices see the RFC itself. Supplementary information 2360 may be available on: 2361 http://www.ietf.org/copyrights/ianamib.html" 2362 -- RFC Editor. Please replace XXX above with the correct RFC number 2363 -- Your actions may vary depending on how IANA chooses to handle 2364 -- this IANA MIB. 2365 -- Please remove this note. 2367 REVISION 2368 "200510130001Z" -- 13 October 2005 00:00:01 GMT 2369 DESCRIPTION 2370 "Initial version issued as part of RFC XXX." 2371 ::= { transmission YYY } 2372 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 2373 -- Please replace XXX with the real RFC number. 2374 -- Please remove this note. 2376 IANAGmplsLSPEncodingType ::= TEXTUAL-CONVENTION 2377 STATUS current 2378 DESCRIPTION 2379 "This data type is used as the syntax of the 2380 gmplsTunnelLSPEncoding object in the definition of 2381 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2383 gmplsTunnelLSPEncoding is used to represent and control 2384 the LSP encoding type of an LSP signaled by a GMPLS 2385 signaling protocol. 2387 This textual convention is strongly tied to the LSP 2388 Encoding Types sub-registry of the GMPLS Signaling 2389 Parameters registry managed by IANA. Values should be 2390 assigned by IANA in step with the LSP Encoding Types 2391 sub-registry and using the same registry management rules. 2392 However, the actual values used in this textual convention 2393 are solely within the purview of IANA and do not 2394 necessarily match the values in the values in the LSP 2395 Encoding Types sub-registry. 2397 The definition of this textual convention with the 2398 addition of newly assigned values is published 2399 periodically by the IANA, in either the Assigned 2400 Numbers RFC, or some derivative of it specific to 2401 Internet Network Management number assignments. (The 2402 latest arrangements can be obtained by contacting the 2403 IANA.) 2405 Requests for new values should be made to IANA via 2406 email (iana@isi.edu)." 2407 REFERENCE 2408 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2409 Signaling Functional Description, RFC 3471, section 2410 3.1.1. 2411 2. Generalized MPLS Signalling Extensions for G.709 Optical 2412 Transport Networks Control, draft-ietf-ccamp-gmpls-g709, 2413 work in progress, section 3.1.1." 2414 -- RFC Editor. Please update this reference to the RFC before 2415 -- publication and remove this note 2416 SYNTAX INTEGER { 2417 tunnelLspNotGmpls (0), -- GMPLS is not in use 2418 -- This is not part of the LSP 2419 -- Encoding Type registry, but 2420 -- is needed for the correct 2421 -- functioning of the 2422 -- GMPLS-TE-STD-MIB 2423 tunnelLspPacket (1), -- Packet 2424 tunnelLspEthernet (2), -- Ethernet 2425 tunnelLspAnsiEtsiPdh (3), -- PDH 2426 -- the value 4 is deprecated 2427 tunnelLspSdhSonet (5), -- SDH or SONET 2428 -- the value 6 is deprecated 2429 tunnelLspDigitalWrapper (7), -- Digital Wrapper 2430 tunnelLspLambda (8), -- Lambda 2431 tunnelLspFiber (9), -- Fiber 2432 -- the value 10 is deprecated 2433 tunnelLspFiberChannel (11), -- Fiber Channel 2434 tunnelDigitalPath (12), -- Digital Path 2435 tunnelOpticalChannel (13) -- Optical Channel 2436 } 2438 IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION 2439 STATUS current 2440 DESCRIPTION 2441 "This data type is used as the syntax of the 2442 gmplsTunnelSwitchingType object in the definition of 2443 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2445 gmplsTunnelSwitchingType is used to represent and 2446 control the LSP switching type of an LSP signaled by a 2447 GMPLS signaling protocol. 2449 This textual convention is strongly tied to the Switching 2450 Types sub-registry of the GMPLS Signaling Parameters 2451 registry managed by IANA. Values should be assigned by IANA 2452 in step with the Switching Types sub-registry and using the 2453 same registry management rules. However, the actual values 2454 used in this textual convention are solely within the 2455 purview of IANA and do not necessarily match the values in 2456 the values in the Switching Types sub-registry. 2458 The definition of this textual convention with the 2459 addition of newly assigned values is published 2460 periodically by the IANA, in either the Assigned 2461 Numbers RFC, or some derivative of it specific to 2462 Internet Network Management number assignments. (The 2463 latest arrangements can be obtained by contacting the 2464 IANA.) 2466 Requests for new values should be made to IANA via 2467 email (iana@isi.edu)." 2468 REFERENCE 2469 "1. Routing Extensions in Support of Generalized 2470 Multi-Protocol Label Switching, RFC 4202, section 2.4. 2471 2. Generalized Multi-Protocol Label Switching (GMPLS) 2472 Signaling Functional Description, RFC 3471, section 2473 3.1.1." 2474 SYNTAX INTEGER { 2475 unknown (0), -- none of the following, or not known 2476 psc1 (1), -- Packet-Switch-Capable 1 2477 psc2 (2), -- Packet-Switch-Capable 2 2478 psc3 (3), -- Packet-Switch-Capable 3 2479 psc4 (4), -- Packet-Switch-Capable 4 2480 l2sc (51), -- Layer-2-Switch-Capable 2481 tdm (100), -- Time-Division-Multiplex 2482 lsc (150), -- Lambda-Switch-Capable 2483 fsc (200) -- Fiber-Switch-Capable 2484 } 2486 IANAGmplsGeneralizedPid ::= TEXTUAL-CONVENTION 2487 STATUS current 2488 DESCRIPTION 2489 "This data type is used as the syntax of the 2490 gmplsTunnelGPid object in the definition of 2491 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2493 gmplsTunnelGPid is used to represent and control the LSP 2494 Generalized Protocol Identifier (G-PID) of an LSP 2495 signaled by a GMPLS signaling protocol. 2497 This textual convention is strongly tied to the Generalized 2498 PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters 2499 registry managed by IANA. Values should be assigned by IANA 2500 in step with the Generalized PIDs (G-PID) sub-registry and 2501 using the same registry management rules. However, the 2502 actual values used in this textual convention are solely 2503 within the purview of IANA and do not necessarily match the 2504 values in the values in the Generalized PIDs (G-PID) 2505 sub-registry. 2507 The definition of this textual convention with the 2508 addition of newly assigned values is published 2509 periodically by the IANA, in either the Assigned 2510 Numbers RFC, or some derivative of it specific to 2511 Internet Network Management number assignments. (The 2512 latest arrangements can be obtained by contacting the 2513 IANA.) 2515 Requests for new values should be made to IANA via 2516 email (iana@isi.edu)." 2517 REFERENCE 2518 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2519 Signaling Functional Description, RFC 3471, section 2520 3.1.1. 2521 2. Generalized MPLS Signalling Extensions for G.709 Optical 2522 Transport Networks Control, draft-ietf-ccamp-gmpls-g709, 2523 work in progress, section 3.1.3." 2524 -- RFC Editor. Please update this reference to the RFC before 2525 -- publication and remove this note 2526 SYNTAX INTEGER { 2527 unknown(0), -- unknown or none of the following 2528 asynchE4(5), 2529 asynchDS3T3(6), 2530 asynchE3(7), 2531 bitsynchE3(8), 2532 bytesynchE3(9), 2533 asynchDS2T2(10), 2534 bitsynchDS2T2(11), 2535 asynchE1(13), 2536 bytesynchE1(14), 2537 bytesynch31ByDS0(15), 2538 asynchDS1T1(16), 2539 bitsynchDS1T1(17), 2540 bytesynchDS1T1(18), 2541 vc1vc12(19), 2542 ds1SFAsynch(22), 2543 ds1ESFAsynch(23), 2544 ds3M23Asynch(24), 2545 ds3CBitParityAsynch(25), 2546 vtLovc(26), 2547 stsSpeHovc(27), 2548 posNoScramble16BitCrc(28), 2549 posNoScramble32BitCrc(29), 2550 posScramble16BitCrc(30), 2551 posScramble32BitCrc(31), 2552 atm(32), 2553 ethernet(33), 2554 sdhSonet(34), 2555 digitalwrapper(36), 2556 lambda(37), 2557 ansiEtsiPdh (38), 2558 lapsSdh (40), 2559 fddi (41), 2560 dqdb (42), 2561 fiberChannel3 (43), 2562 hdlc (44), 2563 ethernetV2DixOnly (45), 2564 ethernet802dot3Only (46), 2565 g709ODUj (47), 2566 g709OTUk (48), 2567 g709CBRorCBRa (49), 2568 g709CBRb (50), 2569 g709BSOT (51), 2570 g709BSNT (52), 2571 gfpIPorPPP (53), 2572 gfpEthernetMAC (54), 2573 gfpEthernetPHY (55), 2574 g709ESCON (56), 2575 g709FICON (57), 2576 g709FiberChannel (58) 2577 } 2579 IANAGmplsAdminStatusInformation ::= TEXTUAL-CONVENTION 2580 STATUS current 2581 DESCRIPTION 2582 "This data type is used as the syntax of the 2583 gmplsTunnelAdminStatusFlags object in the definition of 2584 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2586 gmplsTunnelAdminStatusFlags determines the setting of the 2587 Admin Status flags in the Admin Status object or TLV, as 2588 described in RFC 3471. Setting this object to a non-zero 2589 value will result in the inclusion of the Admin Status 2590 object or TLV on signaling messages. 2592 This textual convention is strongly tied to the Admin 2593 Status Flags sub-registry of the GMPLS Signaling Parameters 2594 registry managed by IANA. Values should be assigned by IANA 2595 in step with the Admin Status Flags sub-registry and using 2596 the same registry management rules. However, the actual 2597 values used in this textual convention are solely within 2598 the purview of IANA and do not necessarily match the values 2599 in the values in the Admin Status Flags sub-registry. 2600 -- RFC Editor / IANA note 2601 -- At the time of writing, the referenced Admin Status Flags 2602 -- sub-registry has not been created. 2603 -- It is not requested in RFC 3471 (the base reference for this protocol 2604 -- element). But it is requested in two I-Ds that are ahead of this MIB 2605 -- module in the IETF process 2606 -- draft-ietf-ccamp-gmpls-recovery-e2e-signaling 2607 -- draft-ietf-ccamp-gmpls-alarm-spec 2608 -- Note, however, that at this stage no request is made to IANA for the 2609 -- definition of values in the textual convention to match any of the 2610 -- Admin Status bits except those defined in RFC 3471. IANA is free to 2611 -- define additional values but these will not be used by this MIB 2612 -- module (although future MIB modules will doubtless use them). 2613 -- 2614 -- RFC Editor. Please update the previous paragraph to use the correct 2615 -- name for the new sub-registry as defined by IANA, and delete this 2616 -- note. 2618 The definition of this textual convention with the 2619 addition of newly assigned values is published 2620 periodically by the IANA, in either the Assigned 2621 Numbers RFC, or some derivative of it specific to 2622 Internet Network Management number assignments. (The 2623 latest arrangements can be obtained by contacting the 2624 IANA.) 2626 Requests for new values should be made to IANA via 2627 email (iana@isi.edu)." 2629 REFERENCE 2630 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2631 Signaling Functional Description, RFC 3471, section 8." 2632 SYNTAX BITS { 2633 reflect (0), -- Reflect bit (RFC 3471) 2634 reserved1 (1), -- reserved 2635 reserved2 (2), -- reserved 2636 reserved3 (3), -- reserved 2637 reserved4 (4), -- reserved 2638 reserved5 (5), -- reserved 2639 reserved6 (6), -- reserved 2640 reserved7 (7), -- reserved 2641 reserved8 (8), -- reserved 2642 reserved9 (9), -- reserved 2643 reserved10 (10), -- reserved 2644 reserved11 (11), -- reserved 2645 reserved12 (12), -- reserved 2646 reserved13 (13), -- reserved 2647 reserved14 (14), -- reserved 2648 reserved15 (15), -- reserved 2649 reserved16 (16), -- reserved 2650 reserved17 (17), -- reserved 2651 reserved18 (18), -- reserved 2652 reserved19 (19), -- reserved 2653 reserved20 (20), -- reserved 2654 reserved21 (21), -- reserved 2655 reserved22 (22), -- reserved 2656 reserved23 (23), -- reserved 2657 reserved24 (24), -- reserved 2658 reserved25 (25), -- reserved 2659 reserved26 (26), -- reserved 2660 reserved27 (27), -- reserved 2661 reserved28 (28), -- reserved 2662 testing (29), -- Testing bit (RFC 3473) 2663 administrativelyDown (30), -- Admin down (RFC 3473) 2664 deleteInProgress (31) -- Delete bit (RFC 3473) 2665 } 2667 END 2669 12. References 2671 12.1. Normative References 2673 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2674 Requirements Levels", BCP 14, RFC 2119, March 1997. 2676 [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. 2677 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 2678 1 Functional Specification", RFC 2205, September 1997. 2680 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2681 J., Rose, M., and S. Waldbusser, "Structure of 2682 Management Information Version 2 (SMIv2)", STD 58, RFC 2683 2578, April 1999. 2685 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2686 J., Rose, M., and S. Waldbusser, "Textual Conventions 2687 for SMIv2", STD 58, RFC 2579, April 1999. 2689 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2690 J., Rose, M., and S. Waldbusser, "Conformance Statements 2691 for SMIv2", STD 58, RFC 2580, April 1999. 2693 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2694 "Multiprotocol Label Switching Architecture", RFC 3031, 2695 January 2001. 2697 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 2698 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 2699 Tunnels", RFC 3209, December 2001. 2701 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2702 Architecture for Describing Simple Network Management 2703 Protocol (SNMP) Management Frameworks", STD 62, RFC 2704 3411, December 2002. 2706 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 2707 (GMPLS) Signaling Functional Description", RFC 3471, 2708 January 2003. 2710 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 2711 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 2712 Engineering (RSVP-TE) Extensions", RFC 3473, January 2713 2003. 2715 [RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered 2716 Links in Resource ReSerVation Protocol - Traffic 2717 Engineering (RSVP-TE)", RFC 3477, January 2003. 2719 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 2720 Conventions and for Multiprotocol Label Switching (MPLS) 2721 Management", RFC 3811, June 2004. 2723 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2724 "Multiprotocol Label Switching (MPLS) Traffic 2725 Engineering (TE) Management Information Base (MIB)", 2726 RFC 3812, June 2004. 2728 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2729 "Multiprotocol Label Switching (MPLS) Label Switching 2730 (LSR) Router Management Information Base (MIB)", RFC 2731 3813, June 2004. 2733 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 2734 Switching (GMPLS) Architecture", RFC 3945, October 2004. 2736 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2737 Schoenwaelder, "Textual Conventions for Internet Network 2738 Addresses", RFC 4001, February 2005. 2740 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in 2741 Support of Generalized Multi-Protocol Label Switching", 2742 RFC 4202, October 2005. 2744 [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 2745 Label Switching (GMPLS) Label Switching Router (LSR) 2746 Management Information Base", 2747 draft-ietf-ccamp-gmpls-lsr-mib, work in progress. 2749 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 2750 Conventions for Multiprotocol Label Switching (MPLS) 2751 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 2752 progress. 2754 [GMPLS-G709] Papadimitriou, D., Ed., "Generalized MPLS Signalling 2755 Extensions for G.709 Optical Transport Networks 2756 Control", draft-ietf-ccamp-gmpls-g709, work in progress. 2758 12.2. Informative References 2760 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2761 MIB", RFC 2863, June 2000. 2763 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2764 "Introduction and Applicability Statements for 2765 Internet-Standard Management Framework", RFC 3410, 2766 December 2002. 2768 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 2769 Multi-Protocol Label Switching (MPLS) Signaling 2770 - Constraint-based Routed Label Distribution Protocol 2771 (CR-LDP) Extensions", RFC 3472, January 2003. 2773 13. Contact Information 2775 Thomas D. Nadeau 2776 Cisco Systems, Inc. 2777 1414 Massachusetts Ave. 2778 Boxborough, MA 01719 2779 Email: tnadeau@cisco.com 2781 Cheenu Srinivasan 2782 Bloomberg L.P. 2783 731 Lexington Ave. 2784 New York, NY 10022 2785 Phone: +1-212-617-3682 2786 Email: cheenu@bloomberg.net 2788 Adrian Farrel 2789 Old Dog Consulting 2790 Phone: +44-(0)-1978-860944 2791 Email: adrian@olddog.co.uk 2793 Tim Hall 2794 Data Connection Ltd. 2795 100 Church Street 2796 Enfield, Middlesex 2797 EN2 6BQ, UK 2798 Phone: +44 20 8366 1177 2799 Email: tim.hall@dataconnection.com 2801 Ed Harrison 2802 Data Connection Ltd. 2803 100 Church Street 2804 Enfield, Middlesex 2805 EN2 6BQ, UK 2806 Phone: +44 20 8366 1177 2807 Email: ed.harrison@dataconnection.com 2809 14. Intellectual Property Considerations 2811 The IETF takes no position regarding the validity or scope of any 2812 Intellectual Property Rights or other rights that might be claimed to 2813 pertain to the implementation or use of the technology described in 2814 this document or the extent to which any license under such rights 2815 might or might not be available; nor does it represent that it has 2816 made any independent effort to identify any such rights. Information 2817 on the procedures with respect to rights in RFC documents can be 2818 found in BCP 78 and BCP 79. 2820 Copies of IPR disclosures made to the IETF Secretariat and any 2821 assurances of licenses to be made available, or the result of an 2822 attempt made to obtain a general license or permission for the use of 2823 such proprietary rights by implementers or users of this 2824 specification can be obtained from the IETF on-line IPR repository at 2825 http://www.ietf.org/ipr. 2827 The IETF invites any interested party to bring to its attention any 2828 copyrights, patents or patent applications, or other proprietary 2829 rights that may cover technology that may be required to implement 2830 this standard. Please address the information to the IETF at 2831 ietf-ipr@ietf.org. 2833 15. Full Copyright Statement 2835 Copyright (C) The Internet Society (2005). This document is subject 2836 to the rights, licenses and restrictions contained in BCP 78, and 2837 except as set forth therein, the authors retain all their rights. 2839 This document and the information contained herein are provided on an 2840 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2841 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2842 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2843 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2844 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2845 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.