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