idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-13.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 2823. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2796. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2803. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2809. ** 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 48) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: When an entry is present in gmplsTunnelTable for a tunnel, gmplsTunnelPathComp MUST be used and any corresponding mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable MUST be ignored and SHOULD not be set. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 2006) is 6617 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 482, but not defined == Missing Reference: 'RFC2434' is mentioned on line 2276, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2205' is defined on line 2654, but no explicit reference was found in the text Summary: 4 errors (**), 0 flaws (~~), 8 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: September 2006 Adrian Farrel, Ed. 5 Old Dog Consulting 7 March 2006 9 Generalized Multiprotocol Label Switching (GMPLS) Traffic 10 Engineering Management Information Base 12 draft-ietf-ccamp-gmpls-te-mib-13.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 ............................... 47 64 10. Acknowledgments ...................................... 48 65 11. IANA Considerations .................................. 48 66 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 49 67 11.2. Dependence on IANA MIB Modules ..................... 49 68 11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 49 69 12. References ........................................... 57 70 12.1. Normative References ............................... 57 71 12.2. Informative References ............................. 58 72 13. Contact Information .................................. 59 73 14. Intellectual Property Considerations ................. 59 74 15. Full Copyright Statement ............................. 60 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 gmplsTunnelSendPathNotifyRecipientType = ipv4(1), 386 gmplsTunnelSendPathNotifyRecipient = 'C0000201'H, 387 gmplsTunnelAdminStatusFlags = 0, 388 gmplsTunnelExtraParamsPtr = 0.0 389 } 390 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 391 gmplsTunnelHopTable are created and activated at this time. 393 In mplsTunnelResourceTable: 394 { 395 mplsTunnelResourceIndex = 6, 396 mplsTunnelResourceMaxRate = 0, 397 mplsTunnelResourceMeanRate = 0, 398 mplsTunnelResourceMaxBurstSize = 0, 399 mplsTunnelResourceRowStatus = createAndGo (4) 400 } 402 The next two instances of mplsTunnelHopEntry are used to denote the 403 hops this tunnel will take across the network. 405 The following denotes the beginning of the network, or the first hop. 406 We have used the fictitious LSR identified by "192.0.2.1" as our 407 example head-end router. 409 In mplsTunnelHopTable: 410 { 411 mplsTunnelHopListIndex = 1, 412 mplsTunnelPathOptionIndex = 1, 413 mplsTunnelHopIndex = 1, 414 mplsTunnelHopAddrType = ipV4 (1), 415 mplsTunnelHopIpv4Addr = 192.0.2.1, 416 mplsTunnelHopIpv4PrefixLen = 9, 417 mplsTunnelHopType = strict (1), 418 mplsTunnelHopRowStatus = createAndWait (5), 419 } 421 The following denotes the end of the network, or the last hop in our 422 example. We have used the fictitious LSR identified by 423 "192.0.2.2" as our tail end router. 425 In mplsTunnelHopTable: 426 { 427 mplsTunnelHopListIndex = 1, 428 mplsTunnelPathOptionIndex = 1, 429 mplsTunnelHopIndex = 2, 430 mplsTunnelHopAddrType = ipV4 (1), 431 mplsTunnelHopIpv4Addr = 192.0.2.2, 432 mplsTunnelHopIpv4PrefixLen = 9, 433 mplsTunnelHopType = loose (2), 434 mplsTunnelHopRowStatus = createAndGo (4) 435 } 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. 441 An entry in the gmplsLabelTable is created first to include the 442 explicit label. 444 In gmplsLabelTable: 445 { 446 gmplsLabelInterface = 2, 447 gmplsLabelIndex = 1, 448 gmplsLabelSubindex = 0, 449 gmplsLabelType = gmplsFreeformLabel(3), 450 gmplsLabelFreeform = 0xFEDCBA9876543210 451 gmplsLabelRowStatus = createAndGo(4) 452 } 454 In gmplsTunnelHopTable(1,1,1): 455 { 456 gmplsTunnelHopLabelStatuses = forwardPresent(0) 457 +reversePresent(1), 458 gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable (2, 1, 0) 459 gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable (2, 1, 0) 460 } 462 The first hop is now activated: 464 In mplsTunnelHopTable(1,1,1): 465 { 466 mplsTunnelHopRowStatus = active (1) 467 } 469 No gmplsTunnelHopEntry is created for the second hop as it contains 470 no special GMPLS features. 472 Finally the mplsTunnelEntry is activated: 474 In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2) 475 { 476 mplsTunnelRowStatus = active(1) 477 } 479 8. GMPLS Traffic Engineering MIB Module 481 This MIB module makes references to the following documents. 482 [RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], 483 [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202] 484 and [RFC4328]. 486 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 488 IMPORTS 489 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 490 Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32 491 FROM SNMPv2-SMI -- RFC2578 492 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 493 FROM SNMPv2-CONF -- RFC2580 494 TruthValue, TimeStamp, RowPointer 495 FROM SNMPv2-TC -- RFC2579 496 InetAddress, InetAddressType 497 FROM INET-ADDRESS-MIB -- RFC4001 498 SnmpAdminString 499 FROM SNMP-FRAMEWORK-MIB -- RFC3411 500 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 501 mplsTunnelEgressLSRId, mplsTunnelHopListIndex, 502 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, 503 mplsTunnelARHopListIndex, mplsTunnelARHopIndex, 504 mplsTunnelCHopListIndex, mplsTunnelCHopIndex, 505 mplsTunnelEntry, 506 mplsTunnelAdminStatus, mplsTunnelOperStatus 507 FROM MPLS-TE-STD-MIB -- RFC3812 508 IANAGmplsLSPEncodingType, IANAGmplsSwitchingType, 509 IANAGmplsGeneralizedPid, IANAGmplsAdminStatusInformation 510 FROM IANA-GMPLS-TC-MIB 511 mplsStdMIB 512 FROM MPLS-TC-STD-MIB -- RFC3811 513 ; 515 gmplsTeStdMIB MODULE-IDENTITY 516 LAST-UPDATED 517 "200603020001Z" -- 2 March 2006 00:00:01 GMT 518 ORGANIZATION 519 "IETF Common Control And Measurement Plane (CCAMP) Working 520 Group" 521 CONTACT-INFO 522 " Thomas D. Nadeau 523 Cisco Systems, Inc. 524 Email: tnadeau@cisco.com 526 Adrian Farrel 527 Old Dog Consulting 528 Email: adrian@olddog.co.uk 529 Comments about this document should be emailed direct to the 530 CCAMP working group mailing list at ccamp@ops.ietf.org" 532 DESCRIPTION 533 "Copyright (C) The Internet Society (2006). This version of 534 this MIB module is part of RFC xxxx; see the RFC itself for 535 full legal notices. 536 -- RFC Ed. Please replace xxxx above with the correct RFC number and 537 -- remove this note. 539 This MIB module contains managed object definitions 540 for GMPLS Traffic Engineering (TE) as defined in: 541 1. Generalized Multi-Protocol Label Switching (GMPLS) 542 Signaling Functional Description, Berger, L. (Editor), 543 RFC 3471, January 2003. 544 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 545 L. (Editor), RFC 3473, January 2003." 547 REVISION 548 "200603020001Z" -- 2 March 2006 00:00:01 GMT 549 DESCRIPTION 550 "Initial version issued as part of RFC xxxx." 551 ::= { mplsStdMIB XXX } 552 -- RFC Editor. Please replace xxxx above with the correct RFC number and 553 -- remove this note. 555 -- RFC Editor. Please replace XXX above with the OID assigned by IANA 556 -- and remove this note 558 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 559 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } 560 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } 561 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } 563 gmplsTunnelsConfigured OBJECT-TYPE 564 SYNTAX Gauge32 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "The number of GMPLS tunnels configured on this device. A GMPLS 569 tunnel is considered configured if an entry for the tunnel 570 exists in the gmplsTunnelTable and the associated 571 mplsTunnelRowStatus is active(1)." 572 ::= { gmplsTeScalars 1 } 573 gmplsTunnelsActive OBJECT-TYPE 574 SYNTAX Gauge32 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The number of GMPLS tunnels active on this device. A GMPLS 579 tunnel is considered active if there is an entry in the 580 gmplsTunnelTable and the associated mplsTunnelOperStatus for the 581 tunnel is up(1)." 582 ::= { gmplsTeScalars 2 } 584 gmplsTunnelTable OBJECT-TYPE 585 SYNTAX SEQUENCE OF GmplsTunnelEntry 586 MAX-ACCESS not-accessible 587 STATUS current 588 DESCRIPTION 589 "The gmplsTunnelTable sparse augments the mplsTunnelTable of 590 MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between 591 an LSR and a remote endpoint, and existing tunnels to be 592 reconfigured or removed. 594 Note that only point-to-point tunnel segments are supported, 595 although multi-point-to-point and point-to-multi-point 596 connections are supported by an LSR acting as a cross-connect. 597 Each tunnel can thus have one out-segment originating at this 598 LSR and/or one in-segment terminating at this LSR. 600 The row status of an entry in this table is controlled by 601 mplsTunnelRowStatus in the corresponding entry in 602 mplsTunnelTable. When the corresponding mplsTunnelRowStatus has 603 value active(1) a row in this table may not be created or 604 modified. 606 The exception to this rule is the 607 gmplsTunnelAdminStatusInformation object, which can be modified 608 whilst the tunnel is active." 609 REFERENCE 610 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 611 Management Information Base (MIB), RFC 3812." 612 ::= { gmplsTeObjects 1 } 613 gmplsTunnelEntry OBJECT-TYPE 614 SYNTAX GmplsTunnelEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "An entry in this table in association with the corresponding 619 entry in the mplsTunnelTable represents a GMPLS tunnel. 621 An entry can be created by a network administrator via SNMP SET 622 commands, or in response to signaling protocol events." 623 INDEX { 624 mplsTunnelIndex, 625 mplsTunnelInstance, 626 mplsTunnelIngressLSRId, 627 mplsTunnelEgressLSRId 628 } 629 ::= { gmplsTunnelTable 1 } 631 GmplsTunnelEntry ::= SEQUENCE { 632 gmplsTunnelUnnumIf TruthValue, 633 gmplsTunnelAttributes BITS, 634 gmplsTunnelLSPEncoding IANAGmplsLSPEncodingType, 635 gmplsTunnelSwitchingType IANAGmplsSwitchingType, 636 gmplsTunnelLinkProtection BITS, 637 gmplsTunnelGPid IANAGmplsGeneralizedPid, 638 gmplsTunnelSecondary TruthValue, 639 gmplsTunnelDirection INTEGER, 640 gmplsTunnelPathComp INTEGER, 641 gmplsTunnelUpstreamNotifyRecipientType InetAddressType, 642 gmplsTunnelUpstreamNotifyRecipient InetAddress, 643 gmplsTunnelSendResvNotifyRecipientType InetAddressType, 644 gmplsTunnelSendResvNotifyRecipient InetAddress, 645 gmplsTunnelDownstreamNotifyRecipientType InetAddressType, 646 gmplsTunnelDownstreamNotifyRecipient InetAddress, 647 gmplsTunnelSendPathNotifyRecipientType InetAddressType, 648 gmplsTunnelSendPathNotifyRecipient InetAddress, 649 gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformation, 650 gmplsTunnelExtraParamsPtr RowPointer 651 } 652 gmplsTunnelUnnumIf OBJECT-TYPE 653 SYNTAX TruthValue 654 MAX-ACCESS read-create 655 STATUS current 656 DESCRIPTION 657 "Denotes whether or not this tunnel corresponds to an unnumbered 658 interface represented by an entry in the interfaces group table 659 (the ifTable) with ifType set to mpls (166). 661 This object is only used if mplsTunnelIsIf is set to true(1). 663 If both this object and the mplsTunnelIsIf object are set to 664 true(1), the originating LSR adds an LSP_TUNNEL_INTERFACE_ID 665 object to the outgoing Path message. 667 This object contains information that is only used by the 668 terminating LSR." 669 REFERENCE 670 "1. Signalling Unnumbered Links in RSVP-TE, RFC 3477." 671 DEFVAL { false } 672 ::= { gmplsTunnelEntry 1 } 674 gmplsTunnelAttributes OBJECT-TYPE 675 SYNTAX BITS { 676 labelRecordingDesired (0) 677 } 678 MAX-ACCESS read-create 679 STATUS current 680 DESCRIPTION 681 "This bitmask indicates optional parameters for this tunnel. 682 These bits should be taken in addition to those defined in 683 mplsTunnelSessionAttributes in order to determine the full set 684 of options to be signaled (for example SESSION_ATTRIBUTES flags 685 in RSVP-TE). The following describes these bitfields: 687 labelRecordingDesired 688 This flag is set to indicate that label information should be 689 included when doing a route record. This bit is not valid 690 unless the recordRoute bit is set." 691 REFERENCE 692 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 693 sections 4.4.3, 4.7.1 and 4.7.2." 694 DEFVAL { { } } 695 ::= { gmplsTunnelEntry 2 } 696 gmplsTunnelLSPEncoding OBJECT-TYPE 697 SYNTAX IANAGmplsLSPEncodingType 698 MAX-ACCESS read-create 699 STATUS current 700 DESCRIPTION 701 "This object indicates the encoding of the LSP being requested. 703 A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is 704 not in use. Some objects in this MIB module may be of use for 705 MPLS signaling extensions that do not use GMPLS signaling. By 706 setting this object to 'tunnelLspNotGmpls', an application may 707 indicate that only those objects meaningful in MPLS should be 708 examined. 710 The values to use are defined in the textual convention 711 IANAGmplsLSPEncodingType found in the IANA-GMPLS-TC-MIB module." 712 DEFVAL { tunnelLspNotGmpls } 713 ::= { gmplsTunnelEntry 3 } 715 gmplsTunnelSwitchingType OBJECT-TYPE 716 SYNTAX IANAGmplsSwitchingType 717 MAX-ACCESS read-create 718 STATUS current 719 DESCRIPTION 720 "Indicates the type of switching that should be performed on 721 a particular link. This field is needed for links that 722 advertise more than one type of switching capability. 724 The values to use are defined in the textual convention 725 IANAGmplsSwitchingType found in the IANA-GMPLS-TC-MIB module. 727 This object is only meaningful if gmplsTunnelLSPEncoding is not 728 set to 'tunnelLspNotGmpls'." 729 DEFVAL { unknown } 730 ::= { gmplsTunnelEntry 4 } 731 gmplsTunnelLinkProtection OBJECT-TYPE 732 SYNTAX BITS { 733 extraTraffic(0), 734 unprotected(1), 735 shared (2), 736 dedicatedOneToOne (3), 737 dedicatedOnePlusOne(4), 738 enhanced(5) 739 } 740 MAX-ACCESS read-create 741 STATUS current 742 DESCRIPTION 743 "This bitmask indicates the level of link protection required. A 744 value of zero (no bits set) indicates that any protection may be 745 used. The following describes these bitfields: 747 extraTraffic 748 This flag is set to indicate that the LSP should use links 749 that are protecting other (primary) traffic. Such LSPs may be 750 preempted when the links carrying the (primary) traffic being 751 protected fail. 753 unprotected 754 This glag is set to indicate that the LSP should not use any 755 link layer protection. 757 shared 758 This flage is set to indicate that a shared link layer 759 protection scheme, such as 1:N protection, should be used to 760 support the LSP. 762 dedicatedOneToOne 763 This flag is set to indicate that a dedicated link layer 764 protection scheme, i.e., 1:1 protection, should be used to 765 support the LSP. 767 dedicatedOnePlusOne 768 This flag is set to indicate that a dedicated link layer 769 protection scheme, i.e., 1+1 protection, should be used to 770 support the LSP. 772 enhanced 773 This flag is set to indicate that a protection scheme that is 774 more reliable than Dedicated 1+1 should be used, e.g., 4 fiber 775 BLSR/MS-SPRING. 777 This object is only meaningful if gmplsTunnelLSPEncoding is 778 not set to 'tunnelLspNotGmpls'." 780 REFERENCE 781 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 782 Functional Description, RFC 3471, section 7.1." 783 DEFVAL { { } } 784 ::= { gmplsTunnelEntry 5 } 786 gmplsTunnelGPid OBJECT-TYPE 787 SYNTAX IANAGmplsGeneralizedPid 788 MAX-ACCESS read-create 789 STATUS current 790 DESCRIPTION 791 "This object indicates the payload carried by the LSP. It is only 792 required when GMPLS will be used for this LSP. 794 The values to use are defined in the textual convention 795 IANAGmplsGeneralizedPid found in the IANA-GMPLS-TC-MIB module. 797 This object is only meaningful if gmplsTunnelLSPEncoding is not 798 set to 'tunnelLspNotGmpls'." 799 DEFVAL { unknown } 800 ::= { gmplsTunnelEntry 6 } 802 gmplsTunnelSecondary OBJECT-TYPE 803 SYNTAX TruthValue 804 MAX-ACCESS read-create 805 STATUS current 806 DESCRIPTION 807 "Indicates that the requested LSP is a secondary LSP. 809 This object is only meaningful if gmplsTunnelLSPEncoding is not 810 set to 'tunnelLspNotGmpls'." 811 REFERENCE 812 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 813 Functional Description, RFC 3471, section 7.1." 814 DEFVAL { false } 815 ::= { gmplsTunnelEntry 7 } 817 gmplsTunnelDirection OBJECT-TYPE 818 SYNTAX INTEGER { 819 forward (0), 820 bidirectional (1) 821 } 822 MAX-ACCESS read-create 823 STATUS current 824 DESCRIPTION 825 "Whether this tunnel carries forward data only (is 826 unidirectional) or is bidirectional. 828 Values of this object other than 'forward' are meaningful 829 only if gmplsTunnelLSPEncoding is not set to 830 'tunnelLspNotGmpls'." 831 DEFVAL { forward } 832 ::= { gmplsTunnelEntry 8 } 834 gmplsTunnelPathComp OBJECT-TYPE 835 SYNTAX INTEGER { 836 dynamicFull(1), -- CSPF fully computed 837 explicit(2), -- fully specified path 838 dynamicPartial(3) -- CSPF partially computed 839 } 840 MAX-ACCESS read-create 841 STATUS current 842 DESCRIPTION 843 "This value instructs the source node on how to perform path 844 computation on the explicit route specified by the associated 845 entries in the gmplsTunnelHopTable. 847 dynamicFull 848 The user specifies at least the source and 849 destination of the path and expects that the CSPF 850 will calculate the remainder of the path. 852 explicit 853 The user specifies the entire path for the tunnel to 854 take. This path may contain strict or loose hops. 855 Evaluation of the explicit route will be performed 856 hop by hop through the network. 858 dynamicPartial 859 The user specifies at least the source and 860 destination of the path and expects that the CSPF 861 will calculate the remainder of the path. The path 862 computed by CSPF is allowed to be only partially 863 computed allowing the remainder of the path to be 864 filled in across the network. 866 When an entry is present in gmplsTunnelTable for a tunnel, 867 gmplsTunnelPathComp MUST be used and any corresponding 868 mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable 869 MUST be ignored and SHOULD not be set. 871 mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of 872 MPLS-TE-STD-MIB." 873 REFERENCE 874 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 875 Management Information Base (MIB), RFC 3812." 876 DEFVAL { dynamicFull } 877 ::= { gmplsTunnelEntry 9 } 878 gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE 879 SYNTAX InetAddressType 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "This object is used to aid in interpretation of 884 gmplsTunnelUpstreamNotifyRecipient." 885 DEFVAL { unknown } 886 ::= { gmplsTunnelEntry 10 } 888 gmplsTunnelUpstreamNotifyRecipient OBJECT-TYPE 889 SYNTAX InetAddress 890 MAX-ACCESS read-create 891 STATUS current 892 DESCRIPTION 893 "Indicates the address of the upstream recipient for Notify 894 messages relating to this tunnel and issued by this LSR. This 895 information is typically received from an upstream LSR in a Path 896 message. 898 This object is only valid when signaling a tunnel using RSVP. 900 It is also not valid at the head end of a tunnel since there are 901 no upstream LSRs to which to send a Notify message. 903 This object is interpreted in the context of the value of 904 gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0, 905 the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to 906 unknown(0)." 907 REFERENCE 908 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 909 section 4.2." 910 DEFVAL { '00000000'H } -- 0.0.0.0 911 ::= { gmplsTunnelEntry 11 } 913 gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE 914 SYNTAX InetAddressType 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "This object is used to aid in interpretation of 919 gmplsTunnelSendResvNotifyRecipient." 920 DEFVAL { unknown } 921 ::= { gmplsTunnelEntry 12 } 922 gmplsTunnelSendResvNotifyRecipient OBJECT-TYPE 923 SYNTAX InetAddress 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "Indicates to an upstream LSR the address to which it should send 928 downstream Notify messages relating to this tunnel. 930 This object is only valid when signaling a tunnel using RSVP. 932 It is also not valid at the head end of the tunnel since no Resv 933 messages are sent from that LSR for this tunnel. 935 If set to 0, no Notify Request object will be included in the 936 outgoing Resv messages. 938 This object is interpreted in the context of the value of 939 gmplsTunnelSendResvNotifyRecipientType. If this object is set to 940 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be 941 set to unknown(0)." 942 REFERENCE 943 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 944 section 4.2." 945 DEFVAL { '00000000'H } -- 0.0.0.0 946 ::= { gmplsTunnelEntry 13 } 948 gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE 949 SYNTAX InetAddressType 950 MAX-ACCESS read-create 951 STATUS current 952 DESCRIPTION 953 "This object is used to aid in interpretation of 954 gmplsTunnelDownstreamNotifyRecipient." 955 DEFVAL { unknown } 956 ::= { gmplsTunnelEntry 14 } 958 gmplsTunnelDownstreamNotifyRecipient OBJECT-TYPE 959 SYNTAX InetAddress 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "Indicates the address of the downstream recipient for Notify 964 messages relating to this tunnel and issued by this LSR. This 965 information is typically received from an upstream LSR in a Resv 966 message. This object is only valid when signaling a tunnel using 967 RSVP. 969 It is also not valid at the tail end of a tunnel since there are 970 no downstream LSRs to which to send a Notify message. 972 This object is interpreted in the context of the value of 973 gmplsTunnelDownstreamNotifyRecipient. If this object is set to 974 0, the value of gmplsTunnelDownstreamNotifyRecipient MUST be set 975 to unknown(0)." 976 REFERENCE 977 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 978 section 4.2." 979 DEFVAL { '00000000'H } -- 0.0.0.0 980 ::= { gmplsTunnelEntry 15 } 982 gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE 983 SYNTAX InetAddressType 984 MAX-ACCESS read-create 985 STATUS current 986 DESCRIPTION 987 "This object is used to aid in interpretation of 988 gmplsTunnelSendPathNotifyRecipient." 989 DEFVAL { unknown } 990 ::= { gmplsTunnelEntry 16 } 992 gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE 993 SYNTAX InetAddress 994 MAX-ACCESS read-create 995 STATUS current 996 DESCRIPTION 997 "Indicates to a downstream LSR the address to which it should 998 send upstream Notify messages relating to this tunnel. 1000 This object is only valid when signaling a tunnel using RSVP. 1002 It is also not valid at the tail end of the tunnel since no Path 1003 messages are sent from that LSR for this tunnel. 1005 If set to 0, no Notify Request object will be included in the 1006 outgoing Path messages. 1008 This object is interpreted in the context of the value of 1009 gmplsTunnelSendPathNotifyRecipientType. If this object is set to 1010 0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be 1011 set to unknown(0)." 1013 REFERENCE 1014 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1015 section 4.2." 1016 DEFVAL { '00000000'H } -- 0.0.0.0 1017 ::= { gmplsTunnelEntry 17 } 1018 gmplsTunnelAdminStatusFlags OBJECT-TYPE 1019 SYNTAX IANAGmplsAdminStatusInformation 1020 MAX-ACCESS read-create 1021 STATUS current 1022 DESCRIPTION 1023 "Determines the setting of the Admin Status flags in the 1024 Admin Status object or TLV, as described in RFC 3471. Setting 1025 this field to a non-zero value will result in the inclusion of 1026 the admin status object on signaling messages. 1028 The values to use are defined in the textual convention 1029 IANAGmplsAdminStatusInformation found in the IANA-GMPLS-TC-MIB 1030 module. 1032 This value of this object can be modified when the 1033 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 1034 is active(1). By doing so, a new signaling message will be 1035 triggered including the requested Admin Status object or 1036 TLV." 1037 REFERENCE 1038 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1039 Functional Description, RFC 3471, section 8." 1040 DEFVAL { { } } 1041 ::= { gmplsTunnelEntry 18 } 1043 gmplsTunnelExtraParamsPtr OBJECT-TYPE 1044 SYNTAX RowPointer 1045 MAX-ACCESS read-create 1046 STATUS current 1047 DESCRIPTION 1048 "Some Tunnels will run over transports that can usefully support 1049 technology-specific additional parameters (for example, SONET 1050 resource usage). Such parameters can be supplied in an external 1051 table and referenced from here. 1053 A value of zeroDotzero in this attribute indicates that there 1054 is no such additional information." 1055 DEFVAL { zeroDotZero } 1056 ::= { gmplsTunnelEntry 19 } 1058 gmplsTunnelHopTable OBJECT-TYPE 1059 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "The gmplsTunnelHopTable sparse augments the mplsTunnelHopTable 1064 of MPLS-TE-STD-MIB. It is used to indicate the explicit labels 1065 to be used in an explicit path for a GMPLS tunnel defined in 1066 mplsTunnelTable and gmplsTunnelTable, when it is established 1067 using signaling. It does not insert new hops, but does define 1068 new values for hops defined in mplsTunnelHopTable. 1070 Each row in this table is indexed by the same indexes as 1071 mplsTunnelHopTable. It is acceptable for some rows in 1072 mplsTunnelHopTable to have corresponding entries in this table 1073 and some to have no corresponding entry in this table. 1075 The storage type for this entry is given by the value 1076 of mplsTunnelHopStorageType in the corresponding entry in the 1077 mplsTunnelHopTable. 1079 The row status of an entry in this table is controlled by 1080 mplsTunnelHopRowStatus in the corresponding entry in 1081 mplsTunnelHopTable. That is, it is not permitted to create a row 1082 in this table, nor to modify an existing row, when the 1083 corresponding mplsTunnelHopRowStatus has value active(1)." 1084 REFERENCE 1085 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1086 Management Information Base (MIB), RFC 3812. 1087 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 1088 ::= { gmplsTeObjects 2 } 1090 gmplsTunnelHopEntry OBJECT-TYPE 1091 SYNTAX GmplsTunnelHopEntry 1092 MAX-ACCESS not-accessible 1093 STATUS current 1094 DESCRIPTION 1095 "An entry in this table represents additions to a tunnel hop 1096 defined in mplsTunnelHopEntry. At an ingress to a tunnel an 1097 entry in this table is created by a network administrator for an 1098 ERLSP to be set up by a signaling protocol. At transit and 1099 egress nodes an entry in this table may be used to represent the 1100 explicit path instructions received using the signaling 1101 protocol." 1102 INDEX { 1103 mplsTunnelHopListIndex, 1104 mplsTunnelHopPathOptionIndex, 1105 mplsTunnelHopIndex 1106 } 1107 ::= { gmplsTunnelHopTable 1 } 1109 GmplsTunnelHopEntry ::= SEQUENCE { 1110 gmplsTunnelHopLabelStatuses BITS, 1111 gmplsTunnelHopExplicitForwardLabel Unsigned32, 1112 gmplsTunnelHopExplicitForwardLabelPtr RowPointer, 1113 gmplsTunnelHopExplicitReverseLabel Unsigned32, 1114 gmplsTunnelHopExplicitReverseLabelPtr RowPointer 1115 } 1116 gmplsTunnelHopLabelStatuses OBJECT-TYPE 1117 SYNTAX BITS { 1118 forwardPresent (0), 1119 reversePresent (1) 1120 } 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "This bitmask indicates the presence of labels indicated by the 1125 gmplsTunnelHopExplicitForwardLabel or 1126 gmplsTunnelHopExplicitForwardLabelPtr, and 1127 gmplsTunnelHopExplicitReverseLabel or 1128 gmplsTunnelHopExplicitReverseLabel objects. 1130 For the Present bits, a set bit indicates that a label is 1131 present for this hop in the route. This allows zero to be a 1132 valid label value." 1133 DEFVAL { { } } 1134 ::= { gmplsTunnelHopEntry 1 } 1136 gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE 1137 SYNTAX Unsigned32 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "If gmplsTunnelHopLabelStatuses object indicates that a forward 1142 label is present and gmplsTunnelHopExplicitForwardLabelPtr 1143 contains the value zeroDotZero, then the label to use on this 1144 hop is represented by the value of this object." 1145 ::= { gmplsTunnelHopEntry 2 } 1147 gmplsTunnelHopExplicitForwardLabelPtr OBJECT-TYPE 1148 SYNTAX RowPointer 1149 MAX-ACCESS read-create 1150 STATUS current 1151 DESCRIPTION 1152 "If the gmplsTunnelHopLabelStatuses object indicates that a 1153 forward label is present, this object contains a pointer to a 1154 row in another MIB table (such as the gmplsLabelTable of 1155 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1156 in the forward direction. 1158 If the gmplsTunnelHopLabelStatuses object indicates that a 1159 forward label is present and this object contains the value 1160 zeroDotZero, then the label to use on this hop is found in the 1161 gmplsTunnelHopExplicitForwardLabel object." 1162 DEFVAL { zeroDotZero } 1163 ::= { gmplsTunnelHopEntry 3 } 1164 gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE 1165 SYNTAX Unsigned32 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "If the gmplsTunnelHopLabelStatuses object indicates that a 1170 reverse label is present and 1171 gmplsTunnelHopExplicitReverseLabelPtr contains the value 1172 zeroDotZero, then the label to use on this this hop is found in 1173 this object encoded as a 32-bit integer." 1174 ::= { gmplsTunnelHopEntry 4 } 1176 gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE 1177 SYNTAX RowPointer 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "If the gmplsTunnelHopLabelStatuses object indicates that a 1182 reverse label is present, this object contains a pointer to a 1183 row in another MIB table (such as the gmplsLabelTable of the 1184 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1185 in the reverse direction. 1187 If the gmplsTunnelHopLabelStatuses object indicates that a 1188 reverse label is present and this object contains the value 1189 zeroDotZero, then the label to use on this hop is found in the 1190 gmplsTunnelHopExplicitReverseLabel object." 1191 DEFVAL { zeroDotZero } 1192 ::= { gmplsTunnelHopEntry 5 } 1194 gmplsTunnelARHopTable OBJECT-TYPE 1195 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 1196 MAX-ACCESS not-accessible 1197 STATUS current 1198 DESCRIPTION 1199 "The gmplsTunnelARHopTable sparse augments the 1200 mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate 1201 the labels currently in use for a GMPLS tunnel defined in 1202 mplsTunnelTable and gmplsTunnelTable, as reported by the 1203 signaling protocol. It does not insert new hops, but does define 1204 new values for hops defined in mplsTunnelARHopTable. 1206 Each row in this table is indexed by the same indexes as 1207 mplsTunnelARHopTable. It is acceptable for some rows in 1208 mplsTunnelARHopTable to have corresponding entries in this table 1209 and some to have no corresponding entry in this table. 1211 Note that since the information necessary to build entries 1212 within this table is not provided by some signaling protocols 1213 and might not be returned in all cases of other signaling 1214 protocols, implementation of this table and mplsTunnelARHopTable 1215 is optional. Furthermore, since the information in this table is 1216 actually provided by the signaling protocol after the path has 1217 been set-up, the entries in this table are provided only for 1218 observation, and hence, all variables in this table are 1219 accessible exclusively as read-only." 1221 REFERENCE 1222 "1. Extensions to RSVP for LSP Tunnels, RFC 3209. 1223 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 1224 3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1225 Management Information Base (MIB), RFC 3812. 1226 ::= { gmplsTeObjects 3 } 1228 gmplsTunnelARHopEntry OBJECT-TYPE 1229 SYNTAX GmplsTunnelARHopEntry 1230 MAX-ACCESS not-accessible 1231 STATUS current 1232 DESCRIPTION 1233 "An entry in this table represents additions to a tunnel hop 1234 visible in mplsTunnelARHopEntry. An entry is created by the 1235 signaling protocol for a signaled ERLSP set up by the signaling 1236 protocol. 1238 At any node on the LSP (ingress, transit or egress), this table 1239 and mplsTunnelARHopTable (if the tables are supported and if the 1240 signaling protocol is recording actual route information) 1241 contain the actual route of the whole tunnel. If the signaling 1242 protocol is not recording the actual route, this table MAY 1243 report the information from the gmplsTunnelHopTable or the 1244 gmplsTunnelCHopTable. 1246 Note that the recording of actual labels is distinct from the 1247 recording of the actual route in some signaling protocols. This 1248 feature is enabled using the gmplsTunnelAttributes object." 1249 INDEX { 1250 mplsTunnelARHopListIndex, 1251 mplsTunnelARHopIndex 1252 } 1253 ::= { gmplsTunnelARHopTable 1 } 1255 GmplsTunnelARHopEntry ::= SEQUENCE { 1256 gmplsTunnelARHopLabelStatuses BITS, 1257 gmplsTunnelARHopExplicitForwardLabel Unsigned32, 1258 gmplsTunnelARHopExplicitForwardLabelPtr RowPointer, 1259 gmplsTunnelARHopExplicitReverseLabel Unsigned32, 1260 gmplsTunnelARHopExplicitReverseLabelPtr RowPointer, 1261 gmplsTunnelARHopProtection BITS 1262 } 1263 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1264 SYNTAX BITS { 1265 forwardPresent (0), 1266 reversePresent (1), 1267 forwardGlobal (2), 1268 reverseGlobal (3) 1269 } 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "This bitmask indicates the presence and status of labels 1274 indicated by the gmplsTunnelARHopExplicitForwardLabel or 1275 gmplsTunnelARHopExplicitForwardLabelPtr, and 1276 gmplsTunnelARHopExplicitReverseLabel or 1277 gmplsTunnelARHopExplicitReverseLabelPtr objects. 1279 For the Present bits, a set bit indicates that a label is 1280 present for this hop in the route. For the Global bits, a set 1281 bit indicates that the label comes from the Global Label Space. 1282 A clear bit indicates that this is a Per-Interface label. A 1283 Global bit only has meaning if the corresponding Present bit is 1284 set." 1285 ::= { gmplsTunnelARHopEntry 1 } 1287 gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE 1288 SYNTAX Unsigned32 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1293 forward label is present and 1294 gmplsTunnelARHopExplicitForwardLabelPtr contains the value 1295 zeroDotZero, then the label in use on this hop is found in this 1296 object encoded within a 32-bit integer." 1297 ::= { gmplsTunnelARHopEntry 2 } 1299 gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE 1300 SYNTAX RowPointer 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1305 forward label is present, this object contains a pointer to a 1306 row in another MIB table (such as the gmplsLabelTable of the 1307 GMPLS-LABEL-STD-MIB) that contains the label in use on this hop 1308 in the forward direction. 1310 If the gmplsTunnelARHopLabelStatuses object indicates that a 1311 forward label is present and this object contains the value 1312 zeroDotZero, then the label in use on this hop is found in the 1313 gmplsTunnelARHopExplicitForwardLabel object." 1314 ::= { gmplsTunnelARHopEntry 3 } 1316 gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE 1317 SYNTAX Unsigned32 1318 MAX-ACCESS read-only 1319 STATUS current 1320 DESCRIPTION 1321 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1322 reverse label is present and 1323 gmplsTunnelARHopExplicitReverseLabelPtr contains the value 1324 zeroDotZero, then the label in use on this hop is found in this 1325 object encoded as a 32-bit integer." 1326 ::= { gmplsTunnelARHopEntry 4 } 1328 gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE 1329 SYNTAX RowPointer 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "If the gmplsTunnelARHopLabelStatuses object indicates that a 1334 reverse label is present, this object contains a pointer to a 1335 row in another MIB table (such as the gmplsLabelTable of the 1336 GMPLS-LABEL-STD-MIB) that contains the label in use on this hop 1337 in the reverse direction. 1339 If the gmplsTunnelARHopLabelStatuses object indicates that a 1340 reverse label is present and this object contains the value 1341 zeroDotZero, then the label in use on this hop is found in the 1342 gmplsTunnelARHopExplicitReverseLabel object." 1343 ::= { gmplsTunnelARHopEntry 5 } 1345 gmplsTunnelARHopProtection OBJECT-TYPE 1346 SYNTAX BITS { 1347 localAvailable (0), 1348 localInUse (1) 1349 } 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "Availability and usage of protection on the reported link. 1355 localAvailable 1356 This flag is set to indicate that the link downstream of this 1357 node is protected via a local repair mechanism. 1359 localInUse 1360 This flag is set to indicate that a local repair mechanism is 1361 in use to maintain this tunnel (usually in the face of an 1362 outage of the link it was previously routed over)." 1364 REFERENCE 1365 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1366 section 4.4.1." 1367 ::= { gmplsTunnelARHopEntry 6 } 1369 gmplsTunnelCHopTable OBJECT-TYPE 1370 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "The gmplsTunnelCHopTable sparse augments the mplsTunnelCHopTable 1375 of MPLS-TE-STD-MIB. It is used to indicate additional 1376 information about the hops of a GMPLS tunnel defined in 1377 mplsTunnelTable and gmplsTunnelTable, as computed by a 1378 constraint-based routing protocol, based on the 1379 mplsTunnelHopTable and the gmplsTunnelHopTable. 1381 Each row in this table is indexed by the same indexes as 1382 mplsTunnelCHopTable. It is acceptable for some rows in 1383 mplsTunnelCHopTable to have corresponding entries in this table 1384 and some to have no corresponding entry in this table. 1386 Please note that since the information necessary to build 1387 entries within this table may not be supported by some LSRs, 1388 implementation of this table is optional. 1390 Furthermore, since the information in this table is actually 1391 provided by a path computation component after the path has been 1392 computed, the entries in this table are provided only for 1393 observation, and hence, all objects in this table are accessible 1394 exclusively as read-only." 1396 REFERENCE 1397 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1398 Management Information Base (MIB), RFC 3812. 1399 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 1400 ::= { gmplsTeObjects 4 } 1402 gmplsTunnelCHopEntry OBJECT-TYPE 1403 SYNTAX GmplsTunnelCHopEntry 1404 MAX-ACCESS not-accessible 1405 STATUS current 1406 DESCRIPTION 1407 "An entry in this table represents additions to a computed tunnel 1408 hop visible in mplsTunnelCHopEntry. An entry is created by a 1409 path computation component based on the hops specified in the 1410 corresponding mplsTunnelHopTable and gmplsTunnelHopTable. 1412 At a transit LSR this table (if the table is supported) MAY 1413 contain the path computed by path computation engine on (or on 1414 behalf of) the transit LSR." 1415 INDEX { 1416 mplsTunnelCHopListIndex, 1417 mplsTunnelCHopIndex 1418 } 1419 ::= { gmplsTunnelCHopTable 1 } 1421 GmplsTunnelCHopEntry ::= SEQUENCE { 1422 gmplsTunnelCHopLabelStatuses BITS, 1423 gmplsTunnelCHopExplicitForwardLabel Unsigned32, 1424 gmplsTunnelCHopExplicitForwardLabelPtr RowPointer, 1425 gmplsTunnelCHopExplicitReverseLabel Unsigned32, 1426 gmplsTunnelCHopExplicitReverseLabelPtr RowPointer 1427 } 1429 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1430 SYNTAX BITS { 1431 forwardPresent (0), 1432 reversePresent (1) 1433 } 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "This bitmask indicates the presence of labels indicated by the 1438 gmplsTunnelCHopExplicitForwardLabel or 1439 gmplsTunnelCHopExplicitForwardLabelPtr and 1440 gmplsTunnelCHopExplicitReverseLabel or 1441 gmplsTunnelCHopExplicitReverseLabelPtr objects. 1442 A set bit indicates that a label is present for this hop in the 1443 route thus allowing zero to be a valid label value." 1444 ::= { gmplsTunnelCHopEntry 1 } 1446 gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE 1447 SYNTAX Unsigned32 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1452 forward label is present and 1453 gmplsTunnelCHopExplicitForwardLabelPtr contains the value 1454 zeroDotZero, then the label to use on this hop is found in this 1455 object encoded within a 32-bit integer." 1456 ::= { gmplsTunnelCHopEntry 2 } 1457 gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE 1458 SYNTAX RowPointer 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1463 forward label is present, this object contains a pointer to a 1464 row in another MIB table (such as the gmplsLabelTable of the 1465 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1466 in the forward direction. 1468 If the gmplsTunnelCHopLabelStatuses object indicates that a 1469 forward label is present and this object contains the value 1470 zeroDotZero, then the label to use on this hop is found in the 1471 gmplsTunnelCHopExplicitForwardLabel object." 1472 ::= { gmplsTunnelCHopEntry 3 } 1474 gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE 1475 SYNTAX Unsigned32 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1480 reverse label is present and 1481 gmplsTunnelCHopExplicitReverseLabelPtr contains the value 1482 zeroDotZero, then the label to use on this hop is found in this 1483 object encoded as a 32-bit integer." 1484 ::= { gmplsTunnelCHopEntry 4 } 1486 gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE 1487 SYNTAX RowPointer 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "If the gmplsTunnelCHopLabelStatuses object indicates that a 1492 reverse label is present, this object contains a pointer to a 1493 row in another MIB table (such as the gmplsLabelTable of the 1494 GMPLS-LABEL-STD-MIB) that contains the label to use on this hop 1495 in the reverse direction. 1497 If the gmplsTunnelCHopLabelStatuses object indicates that a 1498 reverse label is present and this object contains the value 1499 zeroDotZero, then the label to use on this hop is found in the 1500 gmplsTunnelCHopExplicitReverseLabel object." 1501 ::= { gmplsTunnelCHopEntry 5 } 1502 gmplsTunnelReversePerfTable OBJECT-TYPE 1503 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1504 MAX-ACCESS not-accessible 1505 STATUS current 1506 DESCRIPTION 1507 "This table 'augments' the gmplsTunnelTable to provides 1508 per-tunnel packet performance information for the reverse 1509 direction of a bidirectional tunnel. It can be seen as 1510 supplementing the mplsTunnelPerfTable which augments the 1511 mplsTunnelTable. 1513 For links that do not transport packets, these packet counters 1514 cannot be maintained. For such links, attempts to read the 1515 objects in this table will return noSuchInstance. 1517 A tunnel can be known to be bidirectional by inspecting the 1518 gmplsTunnelDirection object." 1519 REFERENCE 1520 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1521 Management Information Base (MIB), RFC 3812." 1522 ::= { gmplsTeObjects 5 } 1524 gmplsTunnelReversePerfEntry OBJECT-TYPE 1525 SYNTAX GmplsTunnelReversePerfEntry 1526 MAX-ACCESS not-accessible 1527 STATUS current 1528 DESCRIPTION 1529 "An entry in this table is created by the LSR for every 1530 bidirectional GMPLS tunnel where packets are visible to the 1531 LSR." 1532 AUGMENTS { gmplsTunnelEntry } 1533 ::= { gmplsTunnelReversePerfTable 1 } 1535 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1536 gmplsTunnelReversePerfPackets Counter32, 1537 gmplsTunnelReversePerfHCPackets Counter64, 1538 gmplsTunnelReversePerfErrors Counter32, 1539 gmplsTunnelReversePerfBytes Counter32, 1540 gmplsTunnelReversePerfHCBytes Counter64 1541 } 1543 gmplsTunnelReversePerfPackets OBJECT-TYPE 1544 SYNTAX Counter32 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "Number of packets forwarded on the tunnel in the reverse 1549 direction if it is bidirectional. 1551 This object should represents the 32-bit value of the least 1552 significant part of the 64-bit value if both 1553 gmplsTunnelReversePerfHCPackets and this object are returned. 1555 For links that do not transport packets, this packet counter 1556 cannot be maintained. For such links, this value will return a 1557 noSuchInstance." 1558 ::= { gmplsTunnelReversePerfEntry 1 } 1560 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1561 SYNTAX Counter64 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "High capacity counter for number of packets forwarded on the 1566 tunnel in the reverse direction if it is bidirectional. 1568 For links that do not transport packets, this packet counter 1569 cannot be maintained. For such links, this value will return a 1570 noSuchInstance." 1571 ::= { gmplsTunnelReversePerfEntry 2 } 1573 gmplsTunnelReversePerfErrors OBJECT-TYPE 1574 SYNTAX Counter32 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "Number of errored packets received on the tunnel in the reverse 1579 direction if it is bidirectional. For links that do not 1580 transport packets, this packet counter cannot be maintained. For 1581 such links, this value will return a noSuchInstance." 1582 ::= { gmplsTunnelReversePerfEntry 3 } 1584 gmplsTunnelReversePerfBytes OBJECT-TYPE 1585 SYNTAX Counter32 1586 MAX-ACCESS read-only 1587 STATUS current 1588 DESCRIPTION 1589 "Number of bytes forwarded on the tunnel in the reverse direction 1590 if it is bidirectional. 1592 This object should represents the 32-bit value of the least 1593 significant part of the 64-bit value if both 1594 gmplsTunnelReversePerfHCBytes and this object are returned. 1596 For links that do not transport packets, this packet counter 1597 cannot be maintained. For such links, this value will return a 1598 noSuchInstance." 1599 ::= { gmplsTunnelReversePerfEntry 4 } 1600 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1601 SYNTAX Counter64 1602 MAX-ACCESS read-only 1603 STATUS current 1605 DESCRIPTION 1606 "High capacity counter for number of bytes forwarded on the 1607 tunnel in the reverse direction if it is bidirectional. 1609 For links that do not transport packets, this packet counter 1610 cannot be maintained. For such links, this value will return a 1611 noSuchInstance." 1612 ::= { gmplsTunnelReversePerfEntry 5 } 1614 gmplsTunnelErrorTable OBJECT-TYPE 1615 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "This table 'augments' the mplsTunnelTable 1620 This table provides per-tunnel information about errors. Errors 1621 may be detected locally or reported through the signaling 1622 protocol. Error reporting is not exclusive to GMPLS and this 1623 table may be applied in MPLS systems. 1625 Entries in this table are not persistent over system resets 1626 or re-initializations of the management system." 1627 REFERENCE 1628 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) 1629 Management Information Base (MIB), RFC 3812." 1630 ::= { gmplsTeObjects 6 } 1632 gmplsTunnelErrorEntry OBJECT-TYPE 1633 SYNTAX GmplsTunnelErrorEntry 1634 MAX-ACCESS not-accessible 1635 STATUS current 1636 DESCRIPTION 1637 "An entry in this table is created by the LSR for every tunnel 1638 where error information is visible to the LSR. 1640 Note that systems which read the objects in this table one at a 1641 time may experience a discontinuity as the result of a new error 1642 occurring in between object reads. Systems that are vulnerable 1643 to this should read gmplsTunnelErrorLastTime before and after 1644 reading the other objects." 1645 AUGMENTS { mplsTunnelEntry } 1646 ::= { gmplsTunnelErrorTable 1 } 1647 GmplsTunnelErrorEntry ::= SEQUENCE { 1648 gmplsTunnelErrorLastErrorType INTEGER, 1649 gmplsTunnelErrorLastTime TimeStamp, 1650 gmplsTunnelErrorReporterType InetAddressType, 1651 gmplsTunnelErrorReporter InetAddress, 1652 gmplsTunnelErrorCode Unsigned32, 1653 gmplsTunnelErrorSubcode Unsigned32, 1654 gmplsTunnelErrorTLVs OCTET STRING, 1655 gmplsTunnelErrorHelpString SnmpAdminString 1656 } 1658 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1659 SYNTAX INTEGER { 1660 noError (0), 1661 unknown (1), 1662 protocol (2), 1663 pathComputation (3), 1664 localConfiguration (4), 1665 localResources (5), 1666 localOther (6) 1667 } 1668 MAX-ACCESS read-only 1669 STATUS current 1670 DESCRIPTION 1671 "The nature of the last error. Provides interpretation context 1672 for gmplsTunnelErrorProtocolCode and 1673 gmplsTunnelErrorProtocolSubcode. 1675 A value of noError (0) shows that there is no error associated 1676 with this tunnel and means that the other objects in this table 1677 entry have no meaning. 1679 A value of unknown (1) shows that there is an error but that no 1680 additional information about the cause is known. The error may 1681 have been received in a signaled message or generated locally. 1683 A value of protocol (2) or pathComputation (3) indicates the 1684 cause of an error and identifies an error that has been received 1685 through signaling or will itself be signaled. 1687 A value of localConfiguration (4), localResources (5) or 1688 localOther (6) identifies an error which has been detected 1689 by the local node, but which will not be reported through 1690 signaling." 1691 ::= { gmplsTunnelErrorEntry 1 } 1692 gmplsTunnelErrorLastTime OBJECT-TYPE 1693 SYNTAX TimeStamp 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "The time at which the last error occurred. This is presented as 1698 the value of SysUpTime when the error occurred or was reported 1699 to this node. 1701 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1702 this object is ignored. 1704 Note that entries in this table are not persistent over system 1705 resets or re-initializations of the management system." 1706 ::= { gmplsTunnelErrorEntry 2 } 1708 gmplsTunnelErrorReporterType OBJECT-TYPE 1709 SYNTAX InetAddressType 1710 MAX-ACCESS read-only 1711 STATUS current 1712 DESCRIPTION 1713 "The address type of the error reported. 1715 This object is used to aid in interpretation of 1716 gmplsTunnelErrorReporter." 1717 ::= { gmplsTunnelErrorEntry 3 } 1719 gmplsTunnelErrorReporter OBJECT-TYPE 1720 SYNTAX InetAddress 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "The address of the node reporting the last error, or the address 1725 of the resource (such as an interface) associated with the 1726 error. 1728 If gmplsTunnelErrorLastErrorType has the value noError (0), then 1729 this object is ignored. 1731 If gmplsTunnelErrorLastErrorType has the value unknown (1), 1732 localConfiguration (4), localResources (5), or localOther (6) 1733 this object MAY contain a zero value. 1735 This object should be interpreted in the context of the value of 1736 the object gmplsTunnelErrorReporterType." 1737 REFERENCE 1738 "1. Textual Conventions for Internet Network Addresses, RFC 4001, 1739 section 4, Usage Hints." 1740 ::= { gmplsTunnelErrorEntry 4 } 1741 gmplsTunnelErrorCode OBJECT-TYPE 1742 SYNTAX Unsigned32 1743 MAX-ACCESS read-only 1744 STATUS current 1745 DESCRIPTION 1746 "The primary error code associated with the last error. 1747 The interpretation of this error code depends on the value of 1748 gmplsTunnelErrorLastErrorType. If the value of 1749 gmplsTunnelErrorLastErrorType is noError (0) the value of this 1750 object should be 0 and should be ignored. If the value of 1751 gmplsTunnelErrorLastErrorType is protocol (2) the error should 1752 be interpreted in the context of the signling protocol 1753 identified by the mplsTunnelSignallingProto object." 1754 REFERENCE 1755 "1. Resource ReserVation Protocol -- Version 1 Functional 1756 Specification, RFC 2205, section B. 1757 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1758 section 7.3. 1759 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1760 section 13.1." 1761 ::= { gmplsTunnelErrorEntry 5 } 1763 gmplsTunnelErrorSubcode OBJECT-TYPE 1764 SYNTAX Unsigned32 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "The secondary error code associated with the last error and the 1769 protocol used to signal this tunnel. This value is interpreted 1770 in the context of the value of gmplsTunnelErrorCode. 1771 If the value of gmplsTunnelErrorLastErrorType is noError (0) the 1772 value of this object should be 0 and should be ignored." 1773 REFERENCE 1774 "1. Resource ReserVation Protocol -- Version 1 Functional 1775 Specification, RFC 2205, section B. 1776 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 1777 section 7.3. 1778 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1779 section 13.1." 1780 ::= { gmplsTunnelErrorEntry 6 } 1781 gmplsTunnelErrorTLVs OBJECT-TYPE 1782 SYNTAX OCTET STRING (SIZE(0..65535)) 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "The sequence of interface identifier TLVs reported with the 1787 error by the protocol code. The interpretation of the TLVs and 1788 the encoding within the protocol are described in the 1789 references. A value of zero in the first octet indicates that no 1790 TLVs are present." 1791 REFERENCE 1792 "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 1793 section 8.2." 1794 ::= { gmplsTunnelErrorEntry 7 } 1796 gmplsTunnelErrorHelpString OBJECT-TYPE 1797 SYNTAX SnmpAdminString 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "A textual string containing information about the last error, 1802 recovery actions and support advice. If there is no help string 1803 this object contains a zero length string. 1804 If the value of gmplsTunnelErrorLastErrorType is noError (0) 1805 this object should contain a zero length string, but may contain 1806 a help string indicating that there is no error." 1807 ::= { gmplsTunnelErrorEntry 8 } 1809 -- 1810 -- Notifications 1811 -- 1813 gmplsTunnelDown NOTIFICATION-TYPE 1814 OBJECTS { 1815 mplsTunnelAdminStatus, 1816 mplsTunnelOperStatus, 1817 gmplsTunnelErrorLastErrorType, 1818 gmplsTunnelErrorReporterType, 1819 gmplsTunnelErrorReporter, 1820 gmplsTunnelErrorCode, 1821 gmplsTunnelErrorSubcode 1822 } 1823 STATUS current 1825 DESCRIPTION 1826 "This notification is generated when a mplsTunnelOperStatus 1827 object for a tunnel in the gmplsTunnelTable is about to enter 1828 the down state from some other state (but not from the 1829 notPresent state). This other state is indicated by the 1830 included value of mplsTunnelOperStatus. 1832 The objects in this notification provide additional error 1833 information that indicates the reason why the tunnel has 1834 transitioned down. 1836 Note that an implementation MUST only issue one of 1837 mplsTunnelDown and gmplsTunnelDown for any single event on a 1838 single tunnel. If the tunnel has an entry in gmplsTunnelTable 1839 an implementation SHOULD use gmplsTunnelDown for all tunnel 1840 down events and SHOULD NOT use mplsTunnelDown. 1842 This notification is subject to the control of the 1843 mplsTunnelNotificationEnable. When that object is set to 1844 false(2) then the notification must not be issued. 1846 Further, this notification is also subject to 1847 mplsTunnelNotificationMaxRate. That object indicates the 1848 maximum number of notifications issued per second. If events 1849 occur more rapidly, the implementation may simply fail to emit 1850 some notifications during that period, or may queue them until 1851 an appropriate time. The notification rate applies to the sum 1852 of all notificaitons in the MPLS-TE-STD-MIB and 1853 GMPLS-TE-STD-MIB modules applied across the whole of the 1854 reporting device. 1856 mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, 1857 mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate 1858 objects are found in MPLS-TE-STD-MIB." 1859 REFERENCE 1860 "1. Multiprotocol Label Switching (MPLS) Traffic Engineering 1861 (TE) Management Information Base (MIB), RFC 3812." 1862 ::= { gmplsTeNotifications 1 } 1864 gmplsTeGroups 1865 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1867 gmplsTeCompliances 1868 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1870 -- Compliance requirement for fully compliant implementations. 1872 gmplsTeModuleFullCompliance MODULE-COMPLIANCE 1873 STATUS current 1874 DESCRIPTION 1875 "Compliance statement for agents that provide full support for 1876 GMPLS-TE-STD-MIB. Such devices can then be monitored and also 1877 be configured using this MIB module. 1879 The mandatory group has to be implemented by all LSRs that 1880 originate, terminate or act as transit for TE-LSPs/tunnels. 1882 In addition, depending on the type of tunnels supported, other 1883 groups become mandatory as explained below." 1885 MODULE -- this module 1886 MANDATORY-GROUPS { 1887 gmplsTunnelGroup, 1888 gmplsTunnelScalarGroup, 1889 gmplsTunnelSignaledGroup 1890 } 1891 ::= { gmplsTeCompliances 1 } 1893 -- Compliance requirement for read-only compliant implementations. 1895 gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 1896 STATUS current 1897 DESCRIPTION 1898 "Compliance requirement for implementations that only provide 1899 read-only support for GMPLS-TE-STD-MIB. Such devices can then be 1900 monitored but cannot be configured using this MIB module." 1902 MODULE -- this module 1904 -- The mandatory group has to be implemented by all LSRs that 1905 -- originate, terminate or act as transit for TE-LSPs/tunnels. 1906 -- In addition, depending on the type of tunnels supported, other 1907 -- groups become mandatory as explained below. 1909 MANDATORY-GROUPS { 1910 gmplsTunnelGroup, 1911 gmplsTunnelScalarGroup, 1912 gmplsTunnelUnnumIf 1913 } 1915 GROUP gmplsTunnelSignaledGroup 1916 DESCRIPTION 1917 "This group is mandatory for devices which support signaled 1918 tunnel set up, in addition to gmplsTunnelGroup. The following 1919 constraints apply: 1920 mplsTunnelSignallingProto should be at least read-only 1921 returning a value of ldp(2), or rsvp(3)." 1923 GROUP gmplsTunnelIsIntfcGroup 1924 DESCRIPTION 1925 "This group is mandatory for devices which support tunnels that 1926 are interfaces, in addition to gmplsTunnelGroup." 1928 GROUP gmplsTunnelOptionalGroup 1929 DESCRIPTION 1930 "Objects in this group are optional." 1932 GROUP gmplsTeNotificationGroup 1933 DESCRIPTION 1934 "This group is mandatory for those implementations which can 1935 implement the notifications contained in this group." 1937 -- All scalars have max access read-only 1939 OBJECT gmplsTunnelAttributes 1940 MIN-ACCESS read-only 1941 DESCRIPTION 1942 "Write access is not required." 1944 OBJECT gmplsTunnelLSPEncoding 1945 SYNTAX IANAGmplsLSPEncodingType 1946 MIN-ACCESS read-only 1947 DESCRIPTION 1948 "Write access is not required." 1950 OBJECT gmplsTunnelSwitchingType 1951 SYNTAX IANAGmplsSwitchingType 1952 MIN-ACCESS read-only 1953 DESCRIPTION 1954 "Write access is not required." 1956 OBJECT gmplsTunnelLinkProtection 1957 MIN-ACCESS read-only 1958 DESCRIPTION 1959 "Write access is not required." 1961 OBJECT gmplsTunnelGPid 1962 SYNTAX IANAGmplsGeneralizedPid 1963 MIN-ACCESS read-only 1964 DESCRIPTION 1965 "Write access is not required." 1967 OBJECT gmplsTunnelSecondary 1968 SYNTAX TruthValue 1969 MIN-ACCESS read-only 1970 DESCRIPTION 1971 "Write access is not required." 1973 OBJECT gmplsTunnelDirection 1974 MIN-ACCESS read-only 1975 DESCRIPTION 1976 "Only forward (0) is required." 1978 OBJECT gmplsTunnelPathComp 1979 MIN-ACCESS read-only 1980 DESCRIPTION 1981 "Only explicit (2) is required." 1983 OBJECT gmplsTunnelUpstreamNotifyRecipientType 1984 SYNTAX InetAddressType 1985 MIN-ACCESS read-only 1986 DESCRIPTION 1987 "Write access is not required." 1989 OBJECT gmplsTunnelUpstreamNotifyRecipient 1990 SYNTAX InetAddress 1991 MIN-ACCESS read-only 1992 DESCRIPTION 1993 "Write access is not required." 1995 OBJECT gmplsTunnelSendResvNotifyRecipientType 1996 SYNTAX InetAddressType 1997 MIN-ACCESS read-only 1998 DESCRIPTION 1999 "Write access is not required." 2001 OBJECT gmplsTunnelSendResvNotifyRecipient 2002 SYNTAX InetAddress 2003 MIN-ACCESS read-only 2004 DESCRIPTION 2005 "Write access is not required." 2007 OBJECT gmplsTunnelDownstreamNotifyRecipientType 2008 SYNTAX InetAddressType 2009 MIN-ACCESS read-only 2010 DESCRIPTION 2011 "Write access is not required." 2013 OBJECT gmplsTunnelDownstreamNotifyRecipient 2014 SYNTAX InetAddress 2015 MIN-ACCESS read-only 2016 DESCRIPTION 2017 "Write access is not required." 2019 OBJECT gmplsTunnelSendPathNotifyRecipientType 2020 SYNTAX InetAddressType 2021 MIN-ACCESS read-only 2022 DESCRIPTION 2023 "Write access is not required." 2025 OBJECT gmplsTunnelSendPathNotifyRecipient 2026 SYNTAX InetAddress 2027 MIN-ACCESS read-only 2028 DESCRIPTION 2029 "Write access is not required." 2031 OBJECT gmplsTunnelAdminStatusFlags 2032 SYNTAX IANAGmplsAdminStatusInformation 2033 MIN-ACCESS read-only 2034 DESCRIPTION 2035 "Write access is not required." 2037 OBJECT gmplsTunnelExtraParamsPtr 2038 MIN-ACCESS read-only 2039 DESCRIPTION 2040 "Write access is not required." 2042 -- gmplsTunnelHopLabelStatuses has max access read-only 2044 OBJECT gmplsTunnelHopExplicitForwardLabel 2045 MIN-ACCESS read-only 2046 DESCRIPTION 2047 "Write access is not required." 2049 OBJECT gmplsTunnelHopExplicitForwardLabelPtr 2050 MIN-ACCESS read-only 2051 DESCRIPTION 2052 "Write access is not required." 2054 OBJECT gmplsTunnelHopExplicitReverseLabel 2055 MIN-ACCESS read-only 2056 DESCRIPTION 2057 "Write access is not required." 2059 OBJECT gmplsTunnelHopExplicitReverseLabelPtr 2060 MIN-ACCESS read-only 2061 DESCRIPTION 2062 "Write access is not required." 2064 -- gmplsTunnelARHopTable 2065 -- all objects have max access read-only 2067 -- glmpsTunnelCHopTable 2068 -- all objects have max access read-only 2070 -- gmplsTunnelReversePerfTable 2071 -- all objects have max access read-only 2073 -- gmplsTunnelErrorTable 2074 -- all objects have max access read-only 2076 ::= { gmplsTeCompliances 2 } 2077 gmplsTunnelGroup OBJECT-GROUP 2078 OBJECTS { 2079 gmplsTunnelDirection, 2080 gmplsTunnelReversePerfPackets, 2081 gmplsTunnelReversePerfHCPackets, 2082 gmplsTunnelReversePerfErrors, 2083 gmplsTunnelReversePerfBytes, 2084 gmplsTunnelReversePerfHCBytes, 2085 gmplsTunnelErrorLastErrorType, 2086 gmplsTunnelErrorLastTime, 2087 gmplsTunnelErrorReporterType, 2088 gmplsTunnelErrorReporter, 2089 gmplsTunnelErrorCode, 2090 gmplsTunnelErrorSubcode, 2091 gmplsTunnelErrorTLVs, 2092 gmplsTunnelErrorHelpString 2093 } 2094 STATUS current 2095 DESCRIPTION 2096 "Necessary, but not sufficient, set of objects to implement 2097 tunnels. In addition, depending on the type of the tunnels 2098 supported (for example, manually configured or signaled, 2099 persistent or non-persistent, etc.), the following other 2100 groups defined below are mandatory: 2102 - gmplsTunnelSignaledGroup 2103 - gmplsTunnelIsIntfcGroup." 2104 ::= { gmplsTeGroups 1 } 2106 gmplsTunnelSignaledGroup OBJECT-GROUP 2107 OBJECTS { 2108 gmplsTunnelAttributes, 2109 gmplsTunnelLSPEncoding, 2110 gmplsTunnelSwitchingType, 2111 gmplsTunnelLinkProtection, 2112 gmplsTunnelGPid, 2113 gmplsTunnelSecondary, 2114 gmplsTunnelPathComp, 2115 gmplsTunnelUpstreamNotifyRecipientType, 2116 gmplsTunnelUpstreamNotifyRecipient, 2117 gmplsTunnelSendResvNotifyRecipientType, 2118 gmplsTunnelSendResvNotifyRecipient, 2119 gmplsTunnelDownstreamNotifyRecipientType, 2120 gmplsTunnelDownstreamNotifyRecipient, 2121 gmplsTunnelSendPathNotifyRecipientType, 2122 gmplsTunnelSendPathNotifyRecipient, 2123 gmplsTunnelAdminStatusFlags, 2124 gmplsTunnelHopLabelStatuses, 2125 gmplsTunnelHopExplicitForwardLabel, 2126 gmplsTunnelHopExplicitForwardLabelPtr, 2127 gmplsTunnelHopExplicitReverseLabel, 2128 gmplsTunnelHopExplicitReverseLabelPtr 2129 } 2130 STATUS current 2131 DESCRIPTION 2132 "Objects needed to implement signaled tunnels." 2133 ::= { gmplsTeGroups 2 } 2135 gmplsTunnelScalarGroup OBJECT-GROUP 2136 OBJECTS { 2137 gmplsTunnelsConfigured, 2138 gmplsTunnelsActive 2139 } 2140 STATUS current 2141 DESCRIPTION 2142 "Scalar objects needed to implement MPLS tunnels." 2143 ::= { gmplsTeGroups 3 } 2145 gmplsTunnelIsIntfcGroup OBJECT-GROUP 2146 OBJECTS { 2147 gmplsTunnelUnnumIf 2148 } 2149 STATUS current 2150 DESCRIPTION 2151 "Objects needed to implement tunnels that are interfaces." 2152 ::= { gmplsTeGroups 4 } 2154 gmplsTunnelOptionalGroup OBJECT-GROUP 2155 OBJECTS { 2156 gmplsTunnelExtraParamsPtr, 2157 gmplsTunnelARHopLabelStatuses, 2158 gmplsTunnelARHopExplicitForwardLabel, 2159 gmplsTunnelARHopExplicitForwardLabelPtr, 2160 gmplsTunnelARHopExplicitReverseLabel, 2161 gmplsTunnelARHopExplicitReverseLabelPtr, 2162 gmplsTunnelARHopProtection, 2163 gmplsTunnelCHopLabelStatuses, 2164 gmplsTunnelCHopExplicitForwardLabel, 2165 gmplsTunnelCHopExplicitForwardLabelPtr, 2166 gmplsTunnelCHopExplicitReverseLabel, 2167 gmplsTunnelCHopExplicitReverseLabelPtr 2168 } 2169 STATUS current 2170 DESCRIPTION 2171 "The objects in this group are optional." 2172 ::= { gmplsTeGroups 5 } 2173 gmplsTeNotificationGroup NOTIFICATION-GROUP 2174 NOTIFICATIONS { 2175 gmplsTunnelDown 2176 } 2177 STATUS current 2178 DESCRIPTION 2179 "Set of notifications implemented in this module. None is 2180 mandatory." 2181 ::= { gmplsTeGroups 6 } 2183 END 2185 9. Security Considerations 2187 It is clear that the MIB modules described in this document in 2188 association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful 2189 for monitoring of MPLS and GMPLS tunnels. These MIB modules can also 2190 be used for configuration of certain objects, and anything that can 2191 be configured can be incorrectly configured, with potentially 2192 disastrous results. 2194 There are a number of management objects defined in these MIB modules 2195 with a MAX-ACCESS clause of read-write and/or read-create. Such 2196 objects may be considered sensitive or vulnerable in some network 2197 environments. The support for SET operations in a non-secure 2198 environment without proper protection can have a negative effect on 2199 network operations. These are the tables and objects and their 2200 sensitivity/vulnerability: 2202 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 2203 objects to provision GMPLS tunnels interfaces at their ingress 2204 LSRs. Unauthorized write access to objects in these tables, could 2205 result in disruption of traffic on the network. This is especially 2206 true if a tunnel has already been established. 2208 Some of the readable objects in these MIB modules (i.e., objects with 2209 a MAX-ACCESS other than not-accessible) may be considered sensitive 2210 or vulnerable in some network environments. It is thus important to 2211 control even GET and/or NOTIFY access to these objects and possibly 2212 to even encrypt the values of these objects when sending them over 2213 the network via SNMP. These are the tables and objects and their 2214 sensitivity/vulnerability: 2216 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 2217 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, 2218 gmplsTunnelErrorTable collectively show the tunnel network 2219 topology and status. If an Administrator does not want to reveal 2220 this information, then these tables should be considered 2221 sensitive/vulnerable. 2223 SNMP versions prior to SNMPv3 did not include adequate security. Even 2224 if the network itself is secure (for example by using IPSec), even 2225 then, there is no control as to who on the secure network is allowed 2226 to access and GET/SET (read/change/create/delete) the objects in 2227 these MIB modules. 2229 It is RECOMMENDED that implementers consider the security features as 2230 provided by the SNMPv3 framework (see [RFC3410], section 8), 2231 including full support for the SNMPv3 cryptographic mechanisms (for 2232 authentication and privacy). 2234 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2235 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2236 enable cryptographic security. It is then a customer/operator 2237 responsibility to ensure that the SNMP entity giving access to an 2238 instance of this MIB module, is properly configured to give access to 2239 the objects only to those principals (users) that have legitimate 2240 rights to indeed GET or SET (change/create/delete) them. 2242 10. Acknowledgments 2244 This document is a product of the CCAMP Working Group. 2246 This document extends [RFC3812]. The authors would like to express 2247 their gratitude to all those who worked on that earlier MIB document. 2248 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 2249 contributions during an early implementation, and to Baktha 2250 Muralidharan, Tom Petch, Dave Thaler and Bert Wijnen for their review 2251 comments. 2253 Special thanks to Joan Cucchiara and Len Nieman for their help with 2254 compilation issues. 2256 Joan Cucchiara provided a helpful and very thorough MIB Doctor 2257 review. 2259 11. IANA Considerations 2261 -- (Note to RFC-Editor:) 2262 -- We request that you assign contiguous RFC numbers to the three GMPLS 2263 -- MIB documents. 2264 -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to 2265 -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to 2266 -- draft-ietf-ccamp-gmpls-te-mib. 2267 -- (Please remove this note prior to publication.) 2269 IANA is requested to root MIB objects in the MIB module contained in 2270 this document under the mplsStdMIB subtree. 2272 In the future, GMPLS related standards track MIB modules should be 2273 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to 2274 manage that namespace in the SMI Numbers registry [RFC3811]. New 2275 assignments can only be made via a Standards Action as specified in 2276 [RFC2434]. 2278 11.1. IANA Considerations for GMPLS-TE-STD-MIB 2280 The IANA is requested to assign { mplsStdMIB XXX } to the 2281 GMPLS-TE-STD-MIB module specified in this document, and to record 2282 the assignment in the SMI Numbers registry. 2284 -- RFC Editor. Please replace XXX above with assigned OID and remove 2285 -- this note 2287 11.2. Dependence on IANA MIB Modules 2289 Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, 2290 gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual 2291 conventions imported from the IANA-GMPLS-TC-MIB. The purpose of 2292 defining these textual conventions in a separate MIB module is to 2293 allow additional values to be defined without having to issue a new 2294 version of this document. The Internet Assigned Numbers Authority 2295 (IANA) is responsible for the assignment of all Internet numbers; it 2296 will administer the values associated with these textual conventions. 2298 The rules for additions or changes to the IANA-GMPLS-TC-MIB are 2299 outlined in the DESCRIPTION clause associated with its 2300 MODULE-IDENTITY statement. 2302 The current versions of the IANA-GMPLS-TC-MIB can be accessed from 2303 the IANA home page at: "http://www.iana.org/". 2305 11.2.1. IANA-GMPLS-TC-MIB Definition 2307 This is a temporary section intended to supply the base definition of 2308 an IANA MIB module. The normal procedure is that this MIB module is 2309 moved into the direct control of IANA, at which time this section 2310 should be deleted from this document. 2312 IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module 2313 specified in this document as { transmission YYY }. 2315 -- RFC Editor. 2316 -- Please replace YYY above with assigned OID and remove this note. 2318 IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN 2320 IMPORTS 2321 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 2322 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 2324 ianaGmpls MODULE-IDENTITY 2325 LAST-UPDATED "200603020001Z" -- 2 March 2006 00:00:01 GMT 2326 ORGANIZATION "IANA" 2327 CONTACT-INFO 2328 " Internet Assigned Numbers Authority 2329 Postal: USC/Information Sciences Institute 2330 4676 Admiralty Way, Marina del Rey, CA 90292 2331 Tel: +1 310 822 1511 2332 E-Mail: iana@isi.edu" 2333 DESCRIPTION 2334 "Copyright (C) The Internet Society (2006). The initial version 2335 of this MIB module was published in RFC XXX. For full legal 2336 notices see the RFC itself. Supplementary information 2337 may be available on: 2338 http://www.ietf.org/copyrights/ianamib.html" 2339 -- RFC Editor. Please replace XXX above with the correct RFC number 2340 -- Your actions may vary depending on how IANA chooses to handle 2341 -- this IANA MIB. 2342 -- Please remove this note. 2344 REVISION 2345 "200603020001Z" -- 2 March 2006 00:00:01 GMT 2346 DESCRIPTION 2347 "Initial version issued as part of RFC XXX." 2348 ::= { transmission YYY } 2349 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 2350 -- Please replace XXX with the real RFC number. 2351 -- Please remove this note. 2353 IANAGmplsLSPEncodingType ::= TEXTUAL-CONVENTION 2354 STATUS current 2355 DESCRIPTION 2356 "This data type is used as the syntax of the 2357 gmplsTunnelLSPEncoding object in the definition of 2358 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2360 gmplsTunnelLSPEncoding is used to represent and control 2361 the LSP encoding type of an LSP signaled by a GMPLS 2362 signaling protocol. 2364 This textual convention is strongly tied to the LSP 2365 Encoding Types sub-registry of the GMPLS Signaling 2366 Parameters registry managed by IANA. Values should be 2367 assigned by IANA in step with the LSP Encoding Types 2368 sub-registry and using the same registry management rules. 2369 However, the actual values used in this textual convention 2370 are solely within the purview of IANA and do not 2371 necessarily match the values in the values in the LSP 2372 Encoding Types sub-registry. 2374 The definition of this textual convention with the 2375 addition of newly assigned values is published 2376 periodically by the IANA, in either the Assigned 2377 Numbers RFC, or some derivative of it specific to 2378 Internet Network Management number assignments. (The 2379 latest arrangements can be obtained by contacting the 2380 IANA.) 2382 Requests for new values should be made to IANA via 2383 email (iana@isi.edu)." 2384 REFERENCE 2385 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2386 Signaling Functional Description, RFC 3471, section 2387 3.1.1. 2388 2. Generalized MPLS Signalling Extensions for G.709 Optical 2389 Transport Networks Control, RFC 4328, section 3.1.1." 2390 -- RFC Editor. Please update this reference to the RFC before 2391 -- publication and remove this note 2392 SYNTAX INTEGER { 2393 tunnelLspNotGmpls (0), -- GMPLS is not in use 2394 -- This is not part of the LSP 2395 -- Encoding Type registry, but 2396 -- is needed for the correct 2397 -- functioning of the 2398 -- GMPLS-TE-STD-MIB 2399 tunnelLspPacket (1), -- Packet 2400 tunnelLspEthernet (2), -- Ethernet 2401 tunnelLspAnsiEtsiPdh (3), -- PDH 2402 -- the value 4 is deprecated 2403 tunnelLspSdhSonet (5), -- SDH or SONET 2404 -- the value 6 is deprecated 2405 tunnelLspDigitalWrapper (7), -- Digital Wrapper 2406 tunnelLspLambda (8), -- Lambda 2407 tunnelLspFiber (9), -- Fiber 2408 -- the value 10 is deprecated 2409 tunnelLspFiberChannel (11), -- Fiber Channel 2410 tunnelDigitalPath (12), -- Digital Path 2411 tunnelOpticalChannel (13) -- Optical Channel 2412 } 2414 IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION 2415 STATUS current 2416 DESCRIPTION 2417 "This data type is used as the syntax of the 2418 gmplsTunnelSwitchingType object in the definition of 2419 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2421 gmplsTunnelSwitchingType is used to represent and 2422 control the LSP switching type of an LSP signaled by a 2423 GMPLS signaling protocol. 2425 This textual convention is strongly tied to the Switching 2426 Types sub-registry of the GMPLS Signaling Parameters 2427 registry managed by IANA. Values should be assigned by IANA 2428 in step with the Switching Types sub-registry and using the 2429 same registry management rules. However, the actual values 2430 used in this textual convention are solely within the 2431 purview of IANA and do not necessarily match the values in 2432 the values in the Switching Types sub-registry. 2434 The definition of this textual convention with the 2435 addition of newly assigned values is published 2436 periodically by the IANA, in either the Assigned 2437 Numbers RFC, or some derivative of it specific to 2438 Internet Network Management number assignments. (The 2439 latest arrangements can be obtained by contacting the 2440 IANA.) 2442 Requests for new values should be made to IANA via 2443 email (iana@isi.edu)." 2444 REFERENCE 2445 "1. Routing Extensions in Support of Generalized 2446 Multi-Protocol Label Switching, RFC 4202, section 2.4. 2447 2. Generalized Multi-Protocol Label Switching (GMPLS) 2448 Signaling Functional Description, RFC 3471, section 2449 3.1.1." 2450 SYNTAX INTEGER { 2451 unknown (0), -- none of the following, or not known 2452 psc1 (1), -- Packet-Switch-Capable 1 2453 psc2 (2), -- Packet-Switch-Capable 2 2454 psc3 (3), -- Packet-Switch-Capable 3 2455 psc4 (4), -- Packet-Switch-Capable 4 2456 l2sc (51), -- Layer-2-Switch-Capable 2457 tdm (100), -- Time-Division-Multiplex 2458 lsc (150), -- Lambda-Switch-Capable 2459 fsc (200) -- Fiber-Switch-Capable 2460 } 2462 IANAGmplsGeneralizedPid ::= TEXTUAL-CONVENTION 2463 STATUS current 2464 DESCRIPTION 2465 "This data type is used as the syntax of the 2466 gmplsTunnelGPid object in the definition of 2467 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2469 gmplsTunnelGPid is used to represent and control the LSP 2470 Generalized Protocol Identifier (G-PID) of an LSP 2471 signaled by a GMPLS signaling protocol. 2473 This textual convention is strongly tied to the Generalized 2474 PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters 2475 registry managed by IANA. Values should be assigned by IANA 2476 in step with the Generalized PIDs (G-PID) sub-registry and 2477 using the same registry management rules. However, the 2478 actual values used in this textual convention are solely 2479 within the purview of IANA and do not necessarily match the 2480 values in the values in the Generalized PIDs (G-PID) 2481 sub-registry. 2483 The definition of this textual convention with the 2484 addition of newly assigned values is published 2485 periodically by the IANA, in either the Assigned 2486 Numbers RFC, or some derivative of it specific to 2487 Internet Network Management number assignments. (The 2488 latest arrangements can be obtained by contacting the 2489 IANA.) 2491 Requests for new values should be made to IANA via 2492 email (iana@isi.edu)." 2493 REFERENCE 2494 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2495 Signaling Functional Description, RFC 3471, section 2496 3.1.1. 2497 2. Generalized MPLS Signalling Extensions for G.709 Optical 2498 Transport Networks Control, RFC 4328, section 3.1.3." 2499 -- RFC Editor. Please update this reference to the RFC before 2500 -- publication and remove this note 2501 SYNTAX INTEGER { 2502 unknown(0), -- unknown or none of the following 2503 -- the values 1, 2, 3 and 4 are reserved in RFC 3471 2504 asynchE4(5), 2505 asynchDS3T3(6), 2506 asynchE3(7), 2507 bitsynchE3(8), 2508 bytesynchE3(9), 2509 asynchDS2T2(10), 2510 bitsynchDS2T2(11), 2511 -- the value 12 is reserved in RFC 3471 2512 asynchE1(13), 2513 bytesynchE1(14), 2514 bytesynch31ByDS0(15), 2515 asynchDS1T1(16), 2516 bitsynchDS1T1(17), 2517 bytesynchDS1T1(18), 2518 vc1vc12(19), 2519 -- the values 20 and 21 are reserved in RFC 3471 2520 ds1SFAsynch(22), 2521 ds1ESFAsynch(23), 2522 ds3M23Asynch(24), 2523 ds3CBitParityAsynch(25), 2524 vtLovc(26), 2525 stsSpeHovc(27), 2526 posNoScramble16BitCrc(28), 2527 posNoScramble32BitCrc(29), 2528 posScramble16BitCrc(30), 2529 posScramble32BitCrc(31), 2530 atm(32), 2531 ethernet(33), 2532 sdhSonet(34), 2533 digitalwrapper(36), 2534 lambda(37), 2535 ansiEtsiPdh (38), 2536 lapsSdh (40), 2537 fddi (41), 2538 dqdb (42), 2539 fiberChannel3 (43), 2540 hdlc (44), 2541 ethernetV2DixOnly (45), 2542 ethernet802dot3Only (46), 2543 g709ODUj (47), 2544 g709OTUk (48), 2545 g709CBRorCBRa (49), 2546 g709CBRb (50), 2547 g709BSOT (51), 2548 g709BSNT (52), 2549 gfpIPorPPP (53), 2550 gfpEthernetMAC (54), 2551 gfpEthernetPHY (55), 2552 g709ESCON (56), 2553 g709FICON (57), 2554 g709FiberChannel (58) 2555 } 2557 IANAGmplsAdminStatusInformation ::= TEXTUAL-CONVENTION 2558 STATUS current 2559 DESCRIPTION 2560 "This data type is used as the syntax of the 2561 gmplsTunnelAdminStatusFlags object in the definition of 2562 GMPLS-TE-STD-MIB's gmplsTunnelTable. 2564 gmplsTunnelAdminStatusFlags determines the setting of the 2565 Admin Status flags in the Admin Status object or TLV, as 2566 described in RFC 3471. Setting this object to a non-zero 2567 value will result in the inclusion of the Admin Status 2568 object or TLV on signaling messages. 2570 This textual convention is strongly tied to the Admin 2571 Status Flags sub-registry of the GMPLS Signaling Parameters 2572 registry managed by IANA. Values should be assigned by IANA 2573 in step with the Admin Status Flags sub-registry and using 2574 the same registry management rules. However, the actual 2575 values used in this textual convention are solely within 2576 the purview of IANA and do not necessarily match the values 2577 in the values in the Admin Status Flags sub-registry. 2578 -- RFC Editor / IANA note 2579 -- At the time of writing, the referenced Admin Status Flags 2580 -- sub-registry has not been created. 2581 -- It is not requested in RFC 3471 (the base reference for this protocol 2582 -- element). But it is requested in two I-Ds that are ahead of this MIB 2583 -- module in the IETF process 2584 -- draft-ietf-ccamp-gmpls-recovery-e2e-signaling 2585 -- draft-ietf-ccamp-gmpls-alarm-spec 2586 -- Note, however, that at this stage no request is made to IANA for the 2587 -- definition of values in the textual convention to match any of the 2588 -- Admin Status bits except those defined in RFC 3471. IANA is free to 2589 -- define additional values but these will not be used by this MIB 2590 -- module (although future MIB modules will doubtless use them). 2591 -- 2592 -- RFC Editor. Please update the previous paragraph to use the correct 2593 -- name for the new sub-registry as defined by IANA, and delete this 2594 -- note. 2596 The definition of this textual convention with the 2597 addition of newly assigned values is published 2598 periodically by the IANA, in either the Assigned 2599 Numbers RFC, or some derivative of it specific to 2600 Internet Network Management number assignments. (The 2601 latest arrangements can be obtained by contacting the 2602 IANA.) 2604 Requests for new values should be made to IANA via 2605 email (iana@isi.edu)." 2607 REFERENCE 2608 "1. Generalized Multi-Protocol Label Switching (GMPLS) 2609 Signaling Functional Description, RFC 3471, section 8." 2610 SYNTAX BITS { 2611 reflect (0), -- Reflect bit (RFC 3471) 2612 reserved1 (1), -- reserved 2613 reserved2 (2), -- reserved 2614 reserved3 (3), -- reserved 2615 reserved4 (4), -- reserved 2616 reserved5 (5), -- reserved 2617 reserved6 (6), -- reserved 2618 reserved7 (7), -- reserved 2619 reserved8 (8), -- reserved 2620 reserved9 (9), -- reserved 2621 reserved10 (10), -- reserved 2622 reserved11 (11), -- reserved 2623 reserved12 (12), -- reserved 2624 reserved13 (13), -- reserved 2625 reserved14 (14), -- reserved 2626 reserved15 (15), -- reserved 2627 reserved16 (16), -- reserved 2628 reserved17 (17), -- reserved 2629 reserved18 (18), -- reserved 2630 reserved19 (19), -- reserved 2631 reserved20 (20), -- reserved 2632 reserved21 (21), -- reserved 2633 reserved22 (22), -- reserved 2634 reserved23 (23), -- reserved 2635 reserved24 (24), -- reserved 2636 reserved25 (25), -- reserved 2637 reserved26 (26), -- reserved 2638 reserved27 (27), -- reserved 2639 reserved28 (28), -- reserved 2640 testing (29), -- Testing bit (RFC 3473) 2641 administrativelyDown (30), -- Admin down (RFC 3473) 2642 deleteInProgress (31) -- Delete bit (RFC 3473) 2643 } 2645 END 2647 12. References 2649 12.1. Normative References 2651 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2652 Requirements Levels", BCP 14, RFC 2119, March 1997. 2654 [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. 2655 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 2656 1 Functional Specification", RFC 2205, September 1997. 2658 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2659 J., Rose, M., and S. Waldbusser, "Structure of 2660 Management Information Version 2 (SMIv2)", STD 58, RFC 2661 2578, April 1999. 2663 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2664 J., Rose, M., and S. Waldbusser, "Textual Conventions 2665 for SMIv2", STD 58, RFC 2579, April 1999. 2667 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2668 J., Rose, M., and S. Waldbusser, "Conformance Statements 2669 for SMIv2", STD 58, RFC 2580, April 1999. 2671 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2672 "Multiprotocol Label Switching Architecture", RFC 3031, 2673 January 2001. 2675 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 2676 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 2677 Tunnels", RFC 3209, December 2001. 2679 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2680 Architecture for Describing Simple Network Management 2681 Protocol (SNMP) Management Frameworks", STD 62, RFC 2682 3411, December 2002. 2684 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 2685 (GMPLS) Signaling Functional Description", RFC 3471, 2686 January 2003. 2688 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 2689 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 2690 Engineering (RSVP-TE) Extensions", RFC 3473, January 2691 2003. 2693 [RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered 2694 Links in Resource ReSerVation Protocol - Traffic 2695 Engineering (RSVP-TE)", RFC 3477, January 2003. 2697 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 2698 Conventions and for Multiprotocol Label Switching (MPLS) 2699 Management", RFC 3811, June 2004. 2701 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2702 "Multiprotocol Label Switching (MPLS) Traffic 2703 Engineering (TE) Management Information Base (MIB)", 2704 RFC 3812, June 2004. 2706 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2707 "Multiprotocol Label Switching (MPLS) Label Switching 2708 (LSR) Router Management Information Base (MIB)", RFC 2709 3813, June 2004. 2711 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 2712 Switching (GMPLS) Architecture", RFC 3945, October 2004. 2714 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2715 Schoenwaelder, "Textual Conventions for Internet Network 2716 Addresses", RFC 4001, February 2005. 2718 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in 2719 Support of Generalized Multi-Protocol Label Switching", 2720 RFC 4202, October 2005. 2722 [RFC4328] Papadimitriou, D., Ed., "Generalized MPLS Signalling 2723 Extensions for G.709 Optical Transport Networks 2724 Control", draft-ietf-ccamp-gmpls-g709, work in progress. 2726 [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 2727 Label Switching (GMPLS) Label Switching Router (LSR) 2728 Management Information Base", 2729 draft-ietf-ccamp-gmpls-lsr-mib, work in progress. 2731 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 2732 Conventions for Multiprotocol Label Switching (MPLS) 2733 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 2734 progress. 2736 12.2. Informative References 2738 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2739 MIB", RFC 2863, June 2000. 2741 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2742 "Introduction and Applicability Statements for 2743 Internet-Standard Management Framework", RFC 3410, 2744 December 2002. 2746 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 2747 Multi-Protocol Label Switching (MPLS) Signaling 2748 - Constraint-based Routed Label Distribution Protocol 2749 (CR-LDP) Extensions", RFC 3472, January 2003. 2751 13. Contact Information 2753 Thomas D. Nadeau 2754 Cisco Systems, Inc. 2755 1414 Massachusetts Ave. 2756 Boxborough, MA 01719 2757 Email: tnadeau@cisco.com 2759 Cheenu Srinivasan 2760 Bloomberg L.P. 2761 731 Lexington Ave. 2762 New York, NY 10022 2763 Phone: +1-212-617-3682 2764 Email: cheenu@bloomberg.net 2766 Adrian Farrel 2767 Old Dog Consulting 2768 Phone: +44-(0)-1978-860944 2769 Email: adrian@olddog.co.uk 2771 Tim Hall 2772 Data Connection Ltd. 2773 100 Church Street 2774 Enfield, Middlesex 2775 EN2 6BQ, UK 2776 Phone: +44 20 8366 1177 2777 Email: tim.hall@dataconnection.com 2779 Ed Harrison 2780 Data Connection Ltd. 2781 100 Church Street 2782 Enfield, Middlesex 2783 EN2 6BQ, UK 2784 Phone: +44 20 8366 1177 2785 Email: ed.harrison@dataconnection.com 2787 14. Intellectual Property Considerations 2789 The IETF takes no position regarding the validity or scope of any 2790 Intellectual Property Rights or other rights that might be claimed to 2791 pertain to the implementation or use of the technology described in 2792 this document or the extent to which any license under such rights 2793 might or might not be available; nor does it represent that it has 2794 made any independent effort to identify any such rights. Information 2795 on the procedures with respect to rights in RFC documents can be 2796 found in BCP 78 and BCP 79. 2798 Copies of IPR disclosures made to the IETF Secretariat and any 2799 assurances of licenses to be made available, or the result of an 2800 attempt made to obtain a general license or permission for the use of 2801 such proprietary rights by implementers or users of this 2802 specification can be obtained from the IETF on-line IPR repository at 2803 http://www.ietf.org/ipr. 2805 The IETF invites any interested party to bring to its attention any 2806 copyrights, patents or patent applications, or other proprietary 2807 rights that may cover technology that may be required to implement 2808 this standard. Please address the information to the IETF at 2809 ietf-ipr@ietf.org. 2811 15. Full Copyright Statement 2813 Copyright (C) The Internet Society (2006). This document is subject 2814 to the rights, licenses and restrictions contained in BCP 78, and 2815 except as set forth therein, the authors retain all their rights. 2817 This document and the information contained herein are provided on an 2818 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2819 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2820 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2821 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2822 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2823 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.