idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by 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 81 longer pages, the longest (page 2) being 61 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 15 instances of too long lines in the document, the longest one being 6 characters in excess of 72. == 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 (November 2003) is 7467 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 4307, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 4311, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 4288, but no explicit reference was found in the text == Unused Reference: 'RFC3477' is defined on line 1990, but no explicit reference was found in the text == Unused Reference: 'RFC3480' is defined on line 1993, but no explicit reference was found in the text == Unused Reference: 'GMPLSOSPF' is defined on line 2009, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 3871, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 3905, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 3900, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 3831, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 4326, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSArch' == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-lsr-mib-03 == Outdated reference: A later version (-12) exists of draft-ietf-ccamp-ospf-gmpls-extensions-11 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-03 -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSonetSDH' == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-03 -- Duplicate reference: draft-ietf-ccamp-gmpls-te-mib, mentioned in 'GMPLSTEMIB', was also mentioned in 'GMPLSTCMIB'. -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 2 errors (**), 0 flaws (~~), 20 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 CCAMP Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: May 2004 4 Cheenu Srinivasan 5 Bloomberg L.P. 7 Adrian Farrel 8 Old Dog Consulting 10 Tim Hall 11 Ed Harrison 12 Data Connection Ltd. 14 November 2003 16 Generalized Multiprotocol Label Switching (GMPLS) Traffic 17 Engineering Management Information Base 19 draft-ietf-ccamp-gmpls-te-mib-03.txt 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance with 24 all provisions of Section 10 of RFC2026. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt. 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 Abstract 44 This memo defines an experimental portion of the Management 45 Information Base (MIB) for use with network management protocols in 46 the Internet community. In particular, it describes managed objects 47 for Generalized Multiprotocol Label Switching (GMPLS) based traffic 48 engineering. 50 Table of Contents 52 1. Introduction 2 53 1.1. Migration Strategy 3 54 2. Terminology 3 55 3. The SNMP Management Framework 3 56 4. Outline 4 57 4.1. Summary of GMPLS Traffic Engineering MIB Module 4 58 5. Brief Description of GMPLS TE MIB Objects 4 59 5.1. gmplsTunnelTable 4 60 5.2. gmplsTunnelHopTable 5 61 5.3. gmplsTunnelARHopTable 5 62 5.4. gmplsTunnelCHopTable 5 63 5.5. gmplsTunnelErrorTable 5 64 5.6. gmplsTunnelPerfTable 5 65 6. Cross-referencing to the mplsLabelTable 5 66 7. Example of GMPLS Tunnel Setup 6 67 8. GMPLS Traffic Engineering MIB Definitions 8 68 9. Security Considerations 36 69 10. Acknowledgments 37 70 11. References 37 71 11.1. Normative Refenerces 37 72 11.2. Informational References 39 73 12. Authors' Addresses 39 74 13. Full Copyright Statement 40 75 14. Intellectual Property Notice 41 76 15. Changes and Pending Work 41 77 15.1. Pending Work 41 79 1. Introduction 81 This memo defines a portion of the Management Information Base (MIB) 82 for use with network management protocols in the Internet community. 83 In particular, it describes managed objects for modeling a 84 Generalized Multi-Protocol Label Switching (GMPLS) [GMPLSArch] based 85 traffic engineering. The tables and objects defined in this document 86 extend those defined in the equivalent document for MPLS traffic 87 engineering [TEMIB], and management of GMPLS traffic engineering is 88 built on management of MPLS traffic engineering. 90 This MIB module should be used in conjunction with the companion 91 document [GMPLSLSRMIB] for GMPLS based traffic engineering 92 configuration and management. 94 Comments should be made direct to the CCAMP mailing list at 95 ccamp@ops.ietf.org. 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119, reference 100 [RFC2119]. 102 1.1. Migration Strategy 104 This MIB extends the traffic engineering MIB defined for use with 105 MPLS [TEMIB]. It provides additions for support of GMPLS tunnels. 107 The companion document modeling and managing GMPLS based LSRs 108 [GMPLSLSRMIB] extends MPLS LSR MIB [LSRMIB] with the same intentions. 110 Textual conventions and OBJECT-IDENTIFIERS are defined in [TCMIB] and 111 [GMPLSTCMIB]. 113 2. Terminology 115 This document uses terminology from the MPLS architecture document 116 [RFC3031], from the GMPLS architecture document [GMPLSArch], and from 117 the MPLS Label Switch Router MIB [LSRMIB]. Some frequently used terms 118 are described next. 120 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 121 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 122 LSRs, each segment being associated with one GMPLS enabled interface. 123 These are also referred to as tunnel segments. 125 Additionally, at an intermediate LSR, we model a connection as 126 consisting of one or more in-segments and/or one or more out- 127 segments. The binding or interconnection between in-segments and out- 128 segments in performed using a cross-connect. 130 These segment and cross-connect objects are defined in the MPLS Label 131 Switch Router MIB [LSRMIB], but see also the GMPLS Label Switch 132 Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these 133 objects. 135 3. The SNMP Management Framework 137 For a detailed overview of the documents that describe the current 138 Internet-Standard Management Framework, please refer to section 7 of 139 RFC 3410 [RFC3410]. 141 Managed objects are accessed via a virtual information store, termed 142 the Management Information Base or MIB. MIB objects are generally 143 accessed through the Simple Network Management Protocol (SNMP). 144 Objects in the MIB are defined using the mechanisms defined in the 145 Structure of Management Information (SMI). This memo specifies a 146 MIB module that is compliant to the SMIv2, which is described in STD 147 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 148 2580 [RFC2580]. 150 4. Outline 152 Support for GMPLS traffic-engineered tunnels requires the following 153 configuration. 155 - Setting up tunnels with appropriate MPLS configuration parameters 156 using [TEMIB]. 157 - Extending the tunnels with GMPLS configuration parameters. 158 - Configuring tunnel loose and strict source routed hops. 160 These actions may need to be accompanied with corresponding actions 161 using [LSRMIB] and [GMPLSLSRMIB] to establish and configure tunnel 162 segments, if this is done manually. Also, the in-segment and out- 163 segment performance tables, mplsInSegmentPerfTable and 164 mplsOutSegmentPerfTable [LSRMIB], should be used to determine 165 performance of the tunnels and tunnel segments although it should be 166 noted that those tables may not be appropriate for measuring 167 performance on some times of GMPLS links. 169 4.1. Summary of GMPLS Traffic Engineering MIB Module 171 The MIB objects for performing the actions listed above that cannot 172 be performed solely using the MIB objects defined in [TEMIB] consist 173 of the following tables. 175 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 176 tunnel configuration parameters. 177 - Tunnel specified, actual, and computed hop tables 178 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 179 gmplsTunnelCHopTable) for providing additional configuration of 180 strict and loose source routed tunnel hops. 181 - Performance and error reporting tables (gmplsTunnelPerfTable and 182 gmplsTunnelErrorTable). 184 These tables are described in the subsequent sections. 186 5. Brief Description of GMPLS TE MIB Objects 188 The objects described in this section support the functionality 189 described in [RFC3473] and [RFC3472] for GMPLS tunnels. 190 The tables support both manually configured and signaled tunnels. 192 5.1. gmplsTunnelTable 194 The gmplsTunnelTable extends the MPLS traffic engineering MIB to 195 allow GMPLS tunnels to be created between an LSR and a remote 196 endpoint, and existing GMPLS tunnels to be reconfigured or removed. 198 Note that we only support point-to-point tunnel segments, although 199 multi-point-to-point and point-to-multi-point connections are 200 supported by an LSR acting as a cross-connect. 202 Each tunnel can thus have one out-segment originating at an LSR 203 and/or one in-segment terminating at that LSR. 205 5.2. gmplsTunnelHopTable 207 The gmplsTunnelHopTable is used to indicate additional parameters for 208 the hops, strict or loose, of a GMPLS tunnel defined in 209 gmplsTunnelTable, when it is established using signaling. Multiple 210 tunnels may share the same hops by pointing to the same entry in this 211 table. 213 5.3. gmplsTunnelARHopTable 215 The gmplsTunnelARHopTable is used to indicate the actual hops 216 traversed by a tunnel as reported by the signaling protocol after the 217 tunnel is setup. The support of this table is optional since not all 218 GMPLS signaling protocols support this feature. 220 5.4. gmplsTunnelCHoptable 222 The gmplsTunnelCHopTable lists the actual hops computed by a 223 constraint-based routing algorithm based on the gmplsTunnelHopTable. 224 The support of this table is optional since not all implementations 225 support computation of hop list using a constraint-based routing 226 protocol. 228 5.5. gmplsTunnelErrorTable 230 The gmplsTunnelErrorTable provides access to information about the 231 last error that occurred on each tunnel known about by the MIB. It 232 indicates the nature of the error, when and how it was reported and 233 can give recovery advice through a display string. 235 5.6. gmplsTunnelPerfTable 237 gmplsTunnelPerfTable provides additional counters to measure the 238 performance of GMPLS tunnels in which packets are visible. It 239 supplements the counters in mplsTunnelPerfTable and augments 240 gmplsTunnelTable. 242 Note that not all counters may be appropriate or available for some 243 types of tunnel. 245 6. Cross-referencing to the mplsLabelTable 247 The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and 248 provides a way to model labels in a GMPLS system where labels might 249 not be simple 32 bit integers. 251 The hop tables in this document (gmplsHopTable, gmplsCHopTable and 252 gmplsARHopTable) use arbitrary indexes to point to entries in the 253 mplsLabelTable to indicate specific label values. 255 Since the primary indexes into gmplsLabelTable are the interface 256 index and a simple 32 bit integer (gmplsLabelIndex), in systems where 257 the nature of a label is well-known, and where the label can safely 258 be encoded as a 32 bit integer (for example a conventional MPLS 259 system), the gmplsLabelTable does not need to be supported in the 260 code implementation and the index pointers to the gmplsLabelTable 261 (gmplsTunnelHopExplicitLabel, gmplsTunnelHopExpRvrsLabel, 262 gmplsTunnelCHopExplicitLabel, gmplsTunnelCHopExpRvrsLabel, 263 gmplsTunnelARHopExplicitLabel, gmplsTunnelARHopExpRvrsLabel) 264 may be replaced with the direct label values. 266 This provides both a good way to support legacy systems that 267 implement the previous version of this MIB [TEMIB], and a significant 268 simplification in GMPLS systems that are limited to a single, simple 269 label type. 271 Note that gmplsLabelTable supports concatenated labels through the 272 use of a label sub-index (gmplsLabelSubindex). 274 7. Example of GMPLS Tunnel Setup 276 This section contains an example of which MIB objects should be 277 modified to create a GMPLS tunnel. This example shows a best effort, 278 loosely routed, bidirectional traffic engineered tunnel, which spans 279 two hops of a simple network, uses Generalized Label requests with 280 Lambda encoding, has label recording and shared link layer 281 protection. Note that these objects should be created on the "head- 282 end" LSR. 284 First in the mplsTunnelTable: 285 { 286 mplsTunnelIndex = 1, 287 mplsTunnelInstance = 1, 288 mplsTunnelIngressLSRId = 123.123.125.1, 289 mplsTunnelEgressLSRId = 123.123.126.1, 290 mplsTunnelName = "My first tunnel", 291 mplsTunnelDescr = "Here to there and back again", 292 mplsTunnelIsIf = true (1), 293 mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, 294 mplsTunnelSignallingProto = none (1), 295 mplsTunnelSetupPrio = 0, 296 mplsTunnelHoldingPrio = 0, 297 mplsTunnelSessionAttributes = recordRoute (4), 298 mplsTunnelOwner = snmp (2), 299 mplsTunnelLocalProtectInUse = false (0), 300 mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, 301 mplsTunnelInstancePriority = 1, 302 mplsTunnelHopTableIndex = 1, 303 mplsTunnelPrimaryInstance = 0, 304 mplsTunnelIncludeAnyAffinity = 0, 305 mplsTunnelIncludeAllAffinity = 0, 306 mplsTunnelExcludeAnyAffinity = 0, 307 mplsTunnelPathInUse = 1, 308 mplsTunnelRole = head(1), 309 mplsTunnelRowStatus = createAndWait (5), 310 } 311 In gmplsTunnelTable(1,1,123.123.125.1,123.123.126.1): 312 { 313 gmplsTunnelUnnumIf = true (1), 314 gmplsTunnelAttributes = labelRecordingRequired (1), 315 gmplsTunnelLSPEncoding = tunnelLspLambda (8), 316 gmplsTunnelSwitchingType = lsc (150), 317 gmplsTunnelLinkProtection = shared (2), 318 gmplsTunnelGPid = lambda (37), 319 gmplsTunnelDirection = bidirectional (1) 320 gmplsTunnelSecondary = false(0), 321 gmplsTunnelPathComp = explicit(2), 322 gmplsTunnelUpNotRecip = 0x7B7B7D01, 323 gmplsTunnelDownNotRecip = 0x00000000, 324 gmplsTunnelAdminStatusFlags = 0 325 } 327 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 328 gmplsTunnelHopTable are created and activated at this time. 330 In mplsTunnelResourceTable: 331 { 332 mplsTunnelResourceIndex = 6, 333 mplsTunnelResourceMaxRate = 0, 334 mplsTunnelResourceMeanRate = 0, 335 mplsTunnelResourceMaxBurstSize = 0, 336 mplsTunnelResourceRowStatus = createAndGo (4) 337 } 339 The next two instances of mplsTunnelHopEntry are used to denote the 340 hops this tunnel will take across the network. 342 The following denotes the beginning of the network, or the first hop. 343 We have used the fictitious LSR identified by "123.123.125.1" as our 344 example head-end router. 346 In mplsTunnelHopTable: 347 { 348 mplsTunnelHopListIndex = 1, 349 mplsTunnelPathOptionIndex = 1, 350 mplsTunnelHopIndex = 1, 351 mplsTunnelHopAddrType = ipV4 (1), 352 mplsTunnelHopIpv4Addr = 123.123.125.1, 353 mplsTunnelHopIpv4PrefixLen = 9, 354 mplsTunnelHopType = strict (1), 355 mplsTunnelHopRowStatus = createAndWait (5), 356 } 357 The following denotes the end of the network, or the last hop in our 358 example. We have used the fictitious LSR identified by 359 "123.123.126.1" as our end router. 361 In mplsTunnelHopTable: 362 { 363 mplsTunnelHopListIndex = 1, 364 mplsTunnelPathOptionIndex = 1, 365 mplsTunnelHopIndex = 2, 366 mplsTunnelHopAddrType = ipV4 (1), 367 mplsTunnelHopIpv4Addr = 123.123.126.1, 368 mplsTunnelHopIpv4PrefixLen = 9, 369 mplsTunnelHopType = loose (2), 370 mplsTunnelHopRowStatus = createAndGo (4) 371 } 373 Now an associated entry in the gmplsTunnelHopTable is created to 374 provide additional GMPLS hop configuration indicating that the first 375 hop is an unnumbered link using explicit forward and reverse labels. 377 In gmplsTunnelHopTable(1,1,1): 378 { 379 gmplsTunnelHopLabelStatuses = forwardPresent(0) 380 +reversePresent(1), 381 gmplsTunnelHopExplicitLabel = gmplsLabelInterface.1, 382 gmplsTunnelHopExpRvrsLabel = gmplsLabelInterface.2 383 } 385 The first hop is now activated: 387 In mplsTunnelHopTable(1,1,1): 388 { 389 mplsTunnelHopRowStatus = active (1) 390 } 392 No gmplsTunnelHopEntry is created for the second hop as it contains 393 no special GMPLS features. 395 Finally the mplsTunnelEntry is activated: 397 In mplsTunnelTable(1,1,123.123.125.1,123.123.126.1) 398 { 399 mplsTunnelRowStatus = active(1) 400 } 402 8. GMPLS Traffic Engineering MIB Definitions 404 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 406 IMPORTS 407 MODULE-IDENTITY, OBJECT-TYPE 408 Integer32, Unsigned32, Counter32, 409 Counter64, IpAddress 410 FROM SNMPv2-SMI 411 MODULE-COMPLIANCE, OBJECT-GROUP 412 FROM SNMPv2-CONF 413 TruthValue, TimeStamp, DisplayString 414 FROM SNMPv2-TC 415 InetAddressIPv4, InetAddressIPv6 416 FROM INET-ADDRESS-MIB 417 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 418 mplsTunnelEgressLSRId, mplsTunnelHopListIndex, 419 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, 420 mplsTunnelARHopListIndex, mplsTunnelARHopIndex, 421 mplsTunnelCHopListIndex, mplsTunnelCHopIndex, 422 mplsTunnelEntry, mplsTunnelSignallingProto 423 FROM MPLS-TE-STD-MIB 424 gmplsStdMIB 425 FROM GMPLS-TC-STD-MIB 426 ; 428 gmplsTeStdMIB MODULE-IDENTITY 429 LAST-UPDATED 430 "200310300900Z" -- 30 October 2003 9:00:00 GMT" 431 ORGANIZATION 432 "Common Control And Management Protocols (CCAMP) 433 Working Group" 434 CONTACT-INFO 435 " Thomas D. Nadeau 436 Cisco Systems, Inc. 437 Email: tnadeau@cisco.com 439 Cheenu Srinivasan 440 Bloomberg L.P. 441 Email: cheenu@bloomberg.net 443 Adrian Farrel 444 Old Dog Consulting 445 Email: adrian@olddog.co.uk 447 Ed Harrison 448 Data Connection Ltd. 449 Email: ed.harrison@dataconnection.com 451 Tim Hall 452 Data Connection Ltd. 453 Email: timhall@dataconnection.com 455 Comments about this document should be emailed direct to the 456 CCAMP working group mailing list at ccamp@ops.ietf.org" 458 DESCRIPTION 459 "This MIB module contains managed object definitions 460 for GMPLS Traffic Engineering (TE). 462 Copyright (C) The Internet Society (2003). This 463 version of this MIB module is part of RFCXXX; see 464 the RFC itself for full legal notices." 466 -- Revision history. 467 REVISION 468 "200310300900Z" -- 30 October 2003 09:00:00 GMT 469 DESCRIPTION 470 "Initial revision, published as part of RFC XXXX." 471 ::= { gmplsStdMIB xx } 473 -- Top level components of this MIB. 475 -- Notifications 476 -- no notifications are currently defined. 477 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 479 -- tables, scalars 480 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } 481 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } 483 -- conformance 484 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } 486 -- GMPLS Tunnel scalars. 488 gmplsTunnelsConfigured OBJECT-TYPE 489 SYNTAX Unsigned32 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The number of GMPLS tunnels configured on this 494 device. A GMPLS tunnel is considered configured if 495 an entry for the tunnel exists in the 496 gmplsTunnelTable and the associated 497 mplsTunnelRowStatusis active(1)." 498 ::= { gmplsTeScalars 1 } 500 gmplsTunnelsActive OBJECT-TYPE 501 SYNTAX Unsigned32 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "The number of GMPLS tunnels active on this device. 506 A GMPLS tunnel is considered active if there is an 507 entry in the gmplsTunnelTable and the associated 508 mplsTunnelOperStatus for the tunnel is up(1)." 509 ::= { gmplsTeScalars 2 } 511 -- End of GMPLS Tunnel scalars. 513 -- GMPLS tunnel table. 515 gmplsTunnelTable OBJECT-TYPE 516 SYNTAX SEQUENCE OF GmplsTunnelEntry 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "The gmplsTunnelTable 'extends' the mplsTunnelTable. 521 It allows GMPLS tunnels to be created between an LSR 522 and a remote endpoint, and existing tunnels to be 523 reconfigured or removed. 524 Note that only point-to-point tunnel segments are 525 supported, although multi-point-to-point and point- 526 to-multi-point connections are supported by an LSR 527 acting as a cross-connect. Each tunnel can thus have 528 one out-segment originating at this LSR and/or one 529 in-segment terminating at this LSR. 531 The row status of an entry in this table is 532 controlled by mplsTunnelRowStatus in the 533 corresponding entry in mplsTunnelTable. That is, 534 it is not permitted to create a row in this table, 535 nor to modify an existing row, when the 536 corresponding mplsTunnelRowStatus has value 537 active(1). 539 The exception to this rule is the gmplsTunnelAdminStatusFlags 540 object, which can be modified whilst the tunnel is active." 541 ::= { gmplsTeObjects 1 } 543 gmplsTunnelEntry OBJECT-TYPE 544 SYNTAX GmplsTunnelEntry 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "An entry in this table in association with the 549 corresponding entry in the mplsTunnelTable 550 represents a GMPLS tunnel. 551 An entry can be created by a network administrator 552 or by an SNMP agent as instructed by a signaling 553 protocol." 554 INDEX { 555 mplsTunnelIndex, 556 mplsTunnelInstance, 557 mplsTunnelIngressLSRId, 558 mplsTunnelEgressLSRId 559 } 560 ::= { gmplsTunnelTable 1 } 562 GmplsTunnelEntry ::= SEQUENCE { 563 gmplsTunnelUnnumIf TruthValue, 564 gmplsTunnelAttributes BITS, 565 gmplsTunnelLSPEncoding Integer32, 566 gmplsTunnelSwitchingType Integer32, 567 gmplsTunnelLinkProtection BITS, 568 gmplsTunnelGPid Integer32, 569 gmplsTunnelSecondary TruthValue, 570 gmplsTunnelDirection INTEGER, 571 gmplsTunnelPathComp INTEGER, 572 gmplsTunnelUpNotRecip IpAddress, 573 gmplsTunnelDownNotRecip IpAddress, 574 gmplsTunnelAdminStatusFlags BITS 575 } 577 gmplsTunnelUnnumIf OBJECT-TYPE 578 SYNTAX TruthValue 579 MAX-ACCESS read-create 580 STATUS current 581 DESCRIPTION 582 "Denotes whether or not this tunnel corresponds to an 583 unnumbered interface represented in the interfaces 584 group table. 585 This object is only used if mplsTunnelIsIf is set to 586 'true'. 587 If both this object and the mplsTunnelIsIf object 588 are set to 'true', the originating LSR adds an 589 LSP_TUNNEL_INTERFACE_ID object to the outgoing Path 590 message. 591 This object contains information that is only used 592 by the terminating LSR." 593 REFERENCE 594 "1. draft-ietf-mpls-crldp-unnum-06.txt - Signalling 595 Unnumbered Links in CR-LDP, Kompella, K., Rekhter, Y. 596 and Kullberg, A., June 2002. 597 2. Signalling Unnumbered Links in RSVP-TE, Kompella, K. 598 and Rekhter, Y., RFC 3477, January 2003." 599 DEFVAL { false } 600 ::= { gmplsTunnelEntry 1 } 602 gmplsTunnelAttributes OBJECT-TYPE 603 SYNTAX BITS { 604 labelRecordingDesired (0) 605 } 606 MAX-ACCESS read-create 607 STATUS current 608 DESCRIPTION 609 "This bitmask indicates optional parameters for this 610 tunnel. These bits should be taken in addition to 611 those defined in mplsTunnelSessionAttributes in 612 order to determine the full set of options to be 613 signaled (for example SESSION_ATTRIBUTES flags in 614 RSVP-TE). 615 The following describes these bitfields: 617 labelRecordingDesired 618 This flag indicates that label information should be 619 included when doing a route record. This bit is not 620 valid unless the recordRoute bit is set." 622 REFERENCE 623 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 624 Awduche et al, RFC 3209, December 2001." 625 DEFVAL { { } } 626 ::= { gmplsTunnelEntry 2 } 627 gmplsTunnelLSPEncoding OBJECT-TYPE 628 SYNTAX Integer32 (0..255) 629 MAX-ACCESS read-create 630 STATUS current 631 DESCRIPTION 632 "This object indicates the encoding of the LSP being 633 requested. 634 A value of zero indicates that GMPLS signaling is 635 not in use. Some objects in this MIB module may be 636 of use for MPLS signaling extensions that do not use 637 GMPLS signaling. By setting this object to zero, an 638 application may indicate that only those objects 639 meaningful in MPLS should be examined. 640 The values to use are currently defined in 641 Generalized Multi-Protocol Label Switching (GMPLS) 642 Signaling Functional Description, RFC 3471. Further 643 values may be defined in future RFCs. 644 tunnelLspPacket (1), 645 tunnelLspEthernet (2), 646 tunnelLspAnsiEtsiPdh (3), 647 -- the value 4 is deprecated 648 tunnelLspSdhSonet (5), 649 -- the value 6 is deprecated 650 tunnelLspDigitalWrapper (7), 651 tunnelLspLambda (8), 652 tunnelLspFiber (9), 653 -- the value 10 is deprecated 654 tunnelLspFiberChannel (11)" 655 REFERENCE 656 "1. Berger, L., et al., Generalized Multi-Protocol 657 Label Switching (GMPLS) Signaling Functional 658 Description, RFC 3471, January 2003." 659 DEFVAL { 0 } 660 ::= { gmplsTunnelEntry 3 } 662 gmplsTunnelSwitchingType OBJECT-TYPE 663 SYNTAX Integer32 (0..255) 664 MAX-ACCESS read-create 665 STATUS current 666 DESCRIPTION 667 "Indicates the type of switching that should be performed on 668 a particular link. This field is needed for links that 669 advertise more than one type of switching capability. Values 670 of this object are as the Switching Capability field defined 671 in Internet Draft OSPF Extensions in Support of Generalized 672 MPLS. Further values may be defined in future RFCs. 673 unknown (0), 674 psc1 (1), 675 psc2 (2), 676 psc3 (3), 677 psc4 (4), 678 l2sc (51), 679 tdm (100), 680 lsc (150), 681 fsc (200) 682 This object is only meaningful if 683 gmplsTunnelLSPEncoding is not set to 0." 685 REFERENCE 686 "1. Kompella, K., et al., OSPF Extensions in Support 687 of Generalized MPLS, draft-ietf-ccamp-ospf-gmpls- 688 extensions-07.txt, May 2002, work in progress. 689 2. Berger, L., et al., Generalized Multi-Protocol 690 Label Switching (GMPLS) Signaling Functional 691 Description, RFC 3471, January 2003." 692 DEFVAL { 0 } 693 ::= { gmplsTunnelEntry 4 } 695 gmplsTunnelLinkProtection OBJECT-TYPE 696 SYNTAX BITS { 697 extraTraffic(0), 698 unprotected(1), 699 shared (2), 700 dedicatedOneToOne (3), 701 dedicatedOnePlusOne(4), 702 enhanced(5) 703 } 704 MAX-ACCESS read-create 705 STATUS current 706 DESCRIPTION 707 "This bitmask indicates the level of link protection 708 required. A value of zero (no bits set) indicates 709 that any protection may be used. 710 The following describes these bitfields: 712 extraTraffic 713 Indicates that the LSP should use links that are 714 protecting other (primary) traffic. Such LSPs may 715 be preempted when the links carrying the (primary) 716 traffic being protected fail. 718 unprotected 719 Indicates that the LSP should not use any link layer 720 protection. 722 shared 723 Indicates that a shared link layer protection scheme, 724 such as 1:N protection, should be used to support the LSP. 726 dedicatedOneToOne 727 Indicates that a dedicated link layer protection scheme, 728 i.e., 1:1 protection, should be used to support the LSP. 730 dedicatedOnePlusOne 731 Indicates that a dedicated link layer protection scheme, 732 i.e., 1+1 protection, should be used to support the LSP. 734 enhanced 735 Indicates that a protection scheme that is more reliable than 736 Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. 738 This object is only meaningful if 739 gmplsTunnelLSPEncoding is not set to 0." 740 DEFVAL { { } } 741 ::= { gmplsTunnelEntry 5 } 742 gmplsTunnelGPid OBJECT-TYPE 743 SYNTAX Integer32 (0..65535) 744 MAX-ACCESS read-create 745 STATUS current 746 DESCRIPTION 747 "This object indicates the payload carried by the 748 LSP. It is only required when GMPLS will be used for 749 this LSP. 751 The values to use are currently defined in 752 Generalized Multi-Protocol Label Switching (GMPLS) 753 Signaling Functional Description, RFC 3471. Further 754 values may be defined in future RFCs. 756 unknown(0), 757 asynchE4(5), 758 asynchDS3T3(6), 759 asynchE3(7), 760 bitsynchE3(8), 761 bytesynchE3(9), 762 asynchDS2T2(10), 763 bitsynchDS2T2(11), 764 asynchE1(13), 765 bytesynchE1(14), 766 bytesynch31ByDS0(15), 767 asynchDS1T1(16), 768 bitsynchDS1T1(17), 769 bytesynchDS1T1(18), 770 VC11VC12(19), 771 ds1SFAsynch(22), 772 ds1ESFAsynch(23), 773 ds3M23Asynch(24), 774 ds3CBitParityAsynch(25), 775 vtLovc(26), 776 stsSpeHovc(27), 777 posNoScramble16BitCrc(28), 778 posNoScramble32BitCrc(29), 779 posScramble16BitCrc(30), 780 posScramble32BitCrc(31), 781 atm(32) 782 ethernet(33), 783 sdhSonet(34), 784 digitalwrapper(36), 785 lambda(37), 786 ansiEtsiPdh (38), 787 lapsSdh (40), 788 fddi (41), 789 dqdb (42), 790 fiberChannel3 (43), 791 hdlc (44), 792 ethernetV2DixOnly (45), 793 ethernet802dot3Only (46) 795 This object is only meaningful if 796 gmplsTunnelLSPEncoding is not set to 0." 798 REFERENCE 799 "1. Berger, L., et al., Generalized Multi-Protocol 800 Label Switching (GMPLS) Signaling Functional 801 Description, RFC 3471, January 2003." 802 DEFVAL { 0 } 803 ::= { gmplsTunnelEntry 6 } 805 gmplsTunnelSecondary OBJECT-TYPE 806 SYNTAX TruthValue 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "Indicates that the requested LSP is a secondary LSP. 812 This object is only meaningful if 813 gmplsTunnelLSPEncoding is not set to 0." 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 (is 826 unidirectional) or is bidirectional. 827 Values of this object other than 'forward' are meaningful 828 only if gmplsTunnelLSPEncoding is not set to 0." 829 DEFVAL { forward } 830 ::= { gmplsTunnelEntry 8 } 832 gmplsTunnelPathComp OBJECT-TYPE 833 SYNTAX INTEGER { 834 dynamicFull(1),-- CSPF fully computed 835 explicit(2),-- fully specified path 836 dynamicPartial(3) -- CSPF partially computed 837 } 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "This value instructs the source node on how to perform 842 path computation on the explicit route specified by the 843 associated entries in the gmplsTunnelHopTable. 845 dynamicFull 846 The user specifies at least the source and 847 destination of the path and expects that the CSPF 848 will calculate the remainder of the path. 850 explicit 851 The user specifies the entire path for the tunnel to 852 take. This path may contain strict or loose hops. 853 Evaluation of the explicit route will be performed 854 hop by hop through the network. 856 dynamicPartial 857 The user specifies at least the source and 858 destination of the path and expects that the CSPF 859 will calculate the remainder of the path. The path 860 computed by CSPF is allowed to be only partially 861 computed allowing the remainder of the path to be 862 filled in across the network. 864 This object deprecates gmplsTunnelHopEntryPathComp." 865 DEFVAL { dynamicFull } 866 ::= { gmplsTunnelEntry 9 } 868 gmplsTunnelUpNotRecip OBJECT-TYPE 869 SYNTAX IpAddress 870 MAX-ACCESS read-create 871 STATUS current 872 DESCRIPTION 873 "Indicates the address of the upstream recipient for Notify 874 messages relating to this tunnel. 876 This object is only valid when signaling a tunnel using 877 RSVP. It is also not valid at the tail end of the tunnel. 879 If set to 0, no Notify Request object will be included in 880 outgoing Path messages." 882 DEFVAL { '00000000'H } -- 0.0.0.0 883 ::= { gmplsTunnelEntry 10 } 885 gmplsTunnelDownNotRecip OBJECT-TYPE 886 SYNTAX IpAddress 887 MAX-ACCESS read-create 888 STATUS current 889 DESCRIPTION 890 "Indicates the address of the upstream recipient for Notify 891 messages relating to this tunnel. 893 This object is only valid when signaling a tunnel using 894 RSVP. It is also not valid at the head end of the tunnel. 896 If set to 0, no Notify Request object will be included in 897 outgoing Resv messages." 899 DEFVAL { '00000000'H } -- 0.0.0.0 900 ::= { gmplsTunnelEntry 11 } 902 gmplsTunnelAdminStatusFlags OBJECT-TYPE 903 SYNTAX BITS { 904 delInProgress (0), 905 adminDown (1), 906 testing (2), 907 reflect (31) 908 } 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "Determines the setting of the Admin Status flags in the 913 Admin Status object or TLV, as described in 914 RFC 3471. Setting this field to a non-zero value will 915 result in the inclusion of the admin status object on 916 signaling messages. 918 This value of this object can be modified when the 919 corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus 920 is active(1). By doing so, a new signaling message will be 921 triggered including the requested Admin Status object or 922 TLV." 924 ::= { gmplsTunnelEntry 12 } 926 -- End of gmplsTunnelTable 928 -- Begin gmplsTunnelHopTable 930 gmplsTunnelHopTable OBJECT-TYPE 931 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "The gmplsTunnelHopTable 'extends' the 936 mplsTunnelHopTable. It is used to indicate the 937 explicit labels to be used in an explicit path for a 938 GMPLS tunnel defined in mplsTunnelTable and 939 gmplsTunnelTable, when it is established using 940 signaling. It does not insert new hops, but does 941 define new values for hops defined in 942 mplsTunnelHopTable. 944 Each row in this table is indexed by the same 945 indexes as mplsTunnelHopTable. It is acceptable for 946 some rows in mplsTunnelHopTable to have 947 corresponding entries in this table and some to have 948 no corresponding entry in this table. 950 The storage type for an entry in this table is 951 inherited from mplsTunnelHopStorageType in the 952 corresponding entry in mplsTunnelHopTable. 954 The row status of an entry in this table is 955 controlled by mplsTunnelHopRowStatus in the 956 corresponding entry in mplsTunnelHopTable. That is, 957 it is not permitted to create a row in this table, 958 nor to modify an existing row, when the 959 corresponding mplsTunnelHopRowStatus has value 960 active(1)." 961 ::= { gmplsTeObjects 2 } 963 gmplsTunnelHopEntry OBJECT-TYPE 964 SYNTAX GmplsTunnelHopEntry 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION 968 "An entry in this table represents additions to a 969 tunnel hop defined in mplsTunnelHopEntry. At an 970 ingress to a tunnel an entry in this table is 971 created by a network administrator for an ERLSP to 972 be set up by a signaling protocol. At transit and 973 egress nodes an entry in this table may be used to 974 represent the explicit path instructions received 975 using the signaling protocol." 977 INDEX { 978 mplsTunnelHopListIndex, 979 mplsTunnelHopPathOptionIndex, 980 mplsTunnelHopIndex 981 } 982 ::= { gmplsTunnelHopTable 1 } 984 GmplsTunnelHopEntry ::= SEQUENCE { 985 gmplsTunnelHopLabelStatuses BITS, 986 gmplsTunnelHopExplicitLabel Unsigned32, 987 gmplsTunnelHopExpRvrsLabel Unsigned32 988 } 990 gmplsTunnelHopLabelStatuses OBJECT-TYPE 991 SYNTAX BITS { 992 forwardPresent (0), 993 reversePresent (1) 994 } 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "This bitmask indicates the presence of labels 999 indicated by the gmplsTunnelHopExplicitLabel and 1000 gmplsTunnelHopExpRvrsLabel objects. 1002 For the Present bits, a set bit indicates that a 1003 label is present for this hop in the route. This 1004 allows zero to be a valid label value." 1005 ::= { gmplsTunnelHopEntry 1 } 1007 gmplsTunnelHopExplicitLabel OBJECT-TYPE 1008 SYNTAX Unsigned32 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "Indicates the row entry in the gmplsLabelTable that 1013 defines the explicit label to use in the explicit 1014 route as the forward path label at this point. This 1015 value only has meaning if the forwardPresent bit of 1016 gmplsTunnelHopLabelStatuses is set. 1017 Note that the other indexes in the gmplsLabelTable 1018 should be interpreted as follows: 1019 - The gmplsLabelInterface should be zero because 1020 this label is not tied to any specific interface 1021 on this LSR 1022 - The gmplsLabelSubindex is used to represent label 1023 concatenations. The first (or only) component 1024 label SHOULD have gmplsLabelSubindex set to zero. 1026 This variable is only valid for settings of 1027 mplsTunnelHopAddrType which may be associated with a 1028 forward path label. 1029 Note that in implementations where the label may be 1030 encoded within a 32 bit integer and where 1031 gmplsLabelTable is not implemented, this object may 1032 directly contain the label value to use." 1033 ::= { gmplsTunnelHopEntry 2 } 1035 gmplsTunnelHopExpRvrsLabel OBJECT-TYPE 1036 SYNTAX Unsigned32 1037 MAX-ACCESS read-create 1038 STATUS current 1039 DESCRIPTION 1040 "Indicates the row entry in the gmplsLabelTable that 1041 defines the explicit label to use in the explicit 1042 route as the reverse path label at this point. This 1043 value only has meaning if the reversePresent bit of 1044 gmplsTunnelHopLabelStatuses is set. 1045 The same rules and notes apply as set out for 1046 gmplsTunnelHopExplicitLabel." 1047 ::= { gmplsTunnelHopEntry 3 } 1049 -- End of gmplsTunnelHopTable 1051 -- Tunnel Actual Route Hop table. 1053 gmplsTunnelARHopTable OBJECT-TYPE 1054 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 1055 MAX-ACCESS not-accessible 1056 STATUS current 1057 DESCRIPTION 1058 "The gmplsTunnelARHopTable 'extends' the 1059 mplsTunnelARHopTable. It is used to indicate the 1060 labels currently in use for a GMPLS tunnel defined 1061 in mplsTunnelTable and gmplsTunnelTable, as reported 1062 by the signaling protocol. It does not insert new 1063 hops, but does define new values for hops defined in 1064 mplsTunnelARHopTable. 1066 Each row in this table is indexed by the same indexes as 1067 mplsTunnelARHopTable. It is acceptable for some rows in 1068 mplsTunnelARHopTable to have corresponding entries in this 1069 table and some to have no corresponding entry in this table. 1071 Note that since the information necessary to build 1072 entries within this table is not provided by some 1073 signaling protocols and might not be returned in all 1074 cases of other signaling protocols, implementation 1075 of this table and mplsTunnelARHopTable is optional. 1076 Furthermore, since the information in this table is 1077 actually provided by the signaling protocol after 1078 the path has been set-up, the entries in this table 1079 are provided only for observation, and hence, all 1080 variables in this table are accessible exclusively 1081 as read-only." 1082 ::= { gmplsTeObjects 3 } 1083 gmplsTunnelARHopEntry OBJECT-TYPE 1084 SYNTAX GmplsTunnelARHopEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "An entry in this table represents additions to a 1089 tunnel hop visible in mplsTunnelARHopEntry. An entry 1090 is created by the signaling protocol for a signaled 1091 ERLSP set up by the signaling protocol. 1093 At any node on the LSP (ingress, transit or egress) 1094 Thus at this table and mplsTunnelARHopTable (if the 1095 tables are supported and if the signaling protocol 1096 is recording actual route information) contains the 1097 actual route of the whole tunnel. If the signaling 1098 protocol is not recording the actual route, this 1099 table MAY report the information from the 1100 gmplsTunnelHopTable or the gmplsTunnelCHopTable. 1102 Note that the recording of actual labels is distinct 1103 from the recording of the actual route in some 1104 signaling protocols. This feature is enabled using 1105 the gmplsTunnelAttributes object." 1107 INDEX { 1108 mplsTunnelARHopListIndex, 1109 mplsTunnelARHopIndex 1110 } 1111 ::= { gmplsTunnelARHopTable 1 } 1113 GmplsTunnelARHopEntry ::= SEQUENCE { 1114 gmplsTunnelARHopLabelStatuses BITS, 1115 gmplsTunnelARHopExplicitLabel Unsigned32, 1116 gmplsTunnelARHopExpRvrsLabel Unsigned32, 1117 gmplsTunnelARHopProtection BITS 1118 } 1120 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1121 SYNTAX BITS { 1122 forwardPresent (0), 1123 reversePresent (1), 1124 forwardGlobal (2), 1125 reverseGlobal (3) 1126 } 1127 MAX-ACCESS read-only 1128 STATUS current 1129 DESCRIPTION 1130 "This bitmask indicates the presence and status of 1131 labels indicated by the 1132 gmplsTunnelARHopExplicitLabel and 1133 gmplsTunnelARHopExpRvrsLabel objects. 1134 For the Present bits, a set bit indicates that a label 1135 is present for this hop in the route. For the Global bits, 1136 a set bit indicates that the label comes from the Global 1137 Label Space. A clear bit indicates that this is a Per- 1138 Interface label. A Global bit only has meaning if the 1139 corresponding Present bit is set." 1141 ::= { gmplsTunnelARHopEntry 1 } 1143 gmplsTunnelARHopExplicitLabel OBJECT-TYPE 1144 SYNTAX Unsigned32 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "Indicates the row entry in the gmplsLabelTable that 1149 defines the label in use as the forward path label 1150 on the path at this point. 1151 This value only has meaning if the forwardPresent 1152 bit of gmplsTunnelARHopLabelStatuses is set. 1154 Note that the other indexes in the gmplsLabelTable 1155 should be interpreted as follows: 1156 - The gmplsLabelInterface should be zero because 1157 this label is not tied to any specific interface 1158 on this LSR 1159 - The gmplsLabelSubindex is used to represent label 1160 concatenations. The first (or only) component 1161 label SHOULD have gmplsLabelSubindex set to zero. 1163 This variable is only valid for settings of 1164 mplsTunnelARHopAddrType which may be associated with 1165 a forward path label. 1167 Note that in implementations where the label may be 1168 encoded within a 32 bit integer and where 1169 gmplsLabelTable is not implemented, this object may 1170 directly contain the label value to use." 1171 ::= { gmplsTunnelARHopEntry 2 } 1173 gmplsTunnelARHopExpRvrsLabel OBJECT-TYPE 1174 SYNTAX Unsigned32 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "Indicates the row entry in the gmplsLabelTable that 1179 defines the label used in the path as reverse path 1180 at this point. 1181 This value only has meaning if the reversePresent 1182 bit of gmplsTunnelARHopLabelStatuses is set. 1183 The same rules and notes apply as set out for 1184 gmplsTunnelARHopExplicitLabel." 1185 ::= { gmplsTunnelARHopEntry 3 } 1187 gmplsTunnelARHopProtection OBJECT-TYPE 1188 SYNTAX BITS { 1189 localAvailable (0), 1190 localInUse (1) 1191 } 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "Availability and usage of protection on the reported link. 1197 localAvailable 1198 Indicates that the link downstream of this node 1199 is protected via a local repair mechanism. 1200 localInUse 1201 Indicates that a local repair mechanism is in 1202 use to maintain this tunnel (usually in the 1203 face of an outage of the link it was previously 1204 routed over)." 1205 ::= { gmplsTunnelARHopEntry 4 } 1207 -- End of mplsTunnelARHopTable 1209 -- Tunnel Computed Hop table. 1211 gmplsTunnelCHopTable OBJECT-TYPE 1212 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION 1216 "The gmplsTunnelCHopTable 'extends' the 1217 mplsTunnelCHopTable. It is used to indicate 1218 additional information about the hops of a GMPLS 1219 tunnel defined in mplsTunnelTable and 1220 gmplsTunnelTable, as computed by a constraint-based 1221 routing protocol, based on the mplsTunnelHopTable 1222 and the gmplsTunnelHopTable. 1224 Each row in this table is indexed by the same indexes as 1225 mplsTunnelCHopTable. It is acceptable for some rows in 1226 mplsTunnelCHopTable to have corresponding entries in this 1227 table and some to have no corresponding entry in this table. 1229 Please note that since the information necessary to 1230 build entries within this table may not be supported 1231 by some LSRs, implementation of this table is optional. 1233 Furthermore, since the information in this table is actually 1234 provided by a path computation component after the path has 1235 been computed, the entries in this table are provided only 1236 for observation, and hence, all objects in this table are 1237 accessible exclusively as read-only." 1238 ::= { gmplsTeObjects 4 } 1240 gmplsTunnelCHopEntry OBJECT-TYPE 1241 SYNTAX GmplsTunnelCHopEntry 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 "An entry in this table represents additions to a 1246 computed tunnel hop visible in mplsTunnelCHopEntry. 1247 An entry is created by a path computation component 1248 based on the hops specified in the corresponding 1249 mplsTunnelHopTable and gmplsTunnelHopTable. 1251 At a transit LSR this table (if the table is 1252 supported) MAY contain the path computed by path 1253 computation engine on (or on behalf of) the transit LSR." 1255 INDEX { 1256 mplsTunnelCHopListIndex, 1257 mplsTunnelCHopIndex 1258 } 1259 ::= { gmplsTunnelCHopTable 1 } 1261 GmplsTunnelCHopEntry ::= SEQUENCE { 1262 gmplsTunnelCHopLabelStatuses BITS, 1263 gmplsTunnelCHopExplicitLabel Unsigned32, 1264 gmplsTunnelCHopExpRvrsLabel Unsigned32 1265 } 1267 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1268 SYNTAX BITS { 1269 forwardPresent (0), 1270 reversePresent (1) 1271 } 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "This bitmask indicates the presence indicated by the 1276 gmplsTunnelCHopExplicitLabel and 1277 gmplsTunnelCHopExpRvrsLabel objects. 1278 A set bit indicates that a label is present for this 1279 hop in the route thus allowing zero to be a valid 1280 label value." 1281 ::= { gmplsTunnelCHopEntry 1 } 1283 gmplsTunnelCHopExplicitLabel OBJECT-TYPE 1284 SYNTAX Unsigned32 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "Indicates the row entry in the gmplsLabelTable that 1289 defines the label to use as the forward path label 1290 on the path at this point. 1291 This value only has meaning if the forwardPresent 1292 bit of gmplsTunnelCHopLabelStatuses is set. 1294 Note that the other indexes in the gmplsLabelTable 1295 should be interpreted as follows: 1296 - The gmplsLabelInterface should be zero because 1297 this label is not tied to any specific interface 1298 on this LSR 1299 - The gmplsLabelSubindex is used to represent label 1300 concatenations. The first (or only) component 1301 label SHOULD have gmplsLabelSubindex set to zero. 1302 This variable is only valid for settings of 1303 mplsTunnelCHopAddrType which may be associated with 1304 a forward path label. 1306 Note that in implementations where the label may be 1307 encoded within a 32 bit integer and where 1308 gmplsLabelTable is not implemented, this object may 1309 directly contain the label value to use." 1310 ::= { gmplsTunnelCHopEntry 2 } 1311 gmplsTunnelCHopExpRvrsLabel OBJECT-TYPE 1312 SYNTAX Unsigned32 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "Indicates the row entry in the gmplsLabelTable that 1317 defines the label to use in the path as reverse path 1318 at this point. 1319 This value only has meaning if the reversePresent 1320 bit of gmplsTunnelCHopLabelStatuses is set. 1321 The same rules and notes apply as set out for 1322 gmplsTunnelCHopExplicitLabel." 1323 ::= { gmplsTunnelCHopEntry 3 } 1325 -- End of gmplsTunnelCHopTable 1327 -- GMPLS Tunnel Reverse Direction Performance Table. 1329 gmplsTunnelReversePerfTable OBJECT-TYPE 1330 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1331 MAX-ACCESS not-accessible 1332 STATUS current 1333 DESCRIPTION 1334 "This table 'augments' the gmplsTunnelTable to provides 1335 per-tunnel packet performance information for the 1336 reverse direction of a bidirectional tunnel. It can be 1337 seen as supplementing the mplsTunnelPerfTable which 1338 augments the mplsTunnelTable." 1339 ::= { gmplsTeObjects 5 } 1341 gmplsTunnelReversePerfEntry OBJECT-TYPE 1342 SYNTAX GmplsTunnelReversePerfEntry 1343 MAX-ACCESS not-accessible 1344 STATUS current 1345 DESCRIPTION 1346 "An entry in this table is created by the LSR for 1347 every bidirectional GMPLS tunnel where packets are 1348 visible to the LSR." 1349 AUGMENTS { gmplsTunnelEntry } 1350 ::= { gmplsTunnelReversePerfTable 1 } 1352 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1353 gmplsTunnelReversePerfPackets Counter32, 1354 gmplsTunnelReversePerfHCPackets Counter64, 1355 gmplsTunnelReversePerfErrors Counter32, 1356 gmplsTunnelReversePerfBytes Counter32, 1357 gmplsTunnelReversePerfHCBytes Counter64 1358 } 1360 gmplsTunnelReversePerfPackets OBJECT-TYPE 1361 SYNTAX Counter32 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "Number of packets forwarded on the tunnel in the 1366 reverse direction if it is bidirectional." 1367 ::= { gmplsTunnelReversePerfEntry 1 } 1368 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1369 SYNTAX Counter64 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "High capacity counter for number of packets 1374 forwarded on the tunnel in the reverse direction if 1375 it is bidirectional." 1376 ::= { gmplsTunnelReversePerfEntry 2 } 1378 gmplsTunnelReversePerfErrors OBJECT-TYPE 1379 SYNTAX Counter32 1380 MAX-ACCESS read-only 1381 STATUS current 1382 DESCRIPTION 1383 "Number of errored packets received on the tunnel in 1384 the reverse direction if it is bidirectional." 1385 ::= { gmplsTunnelReversePerfEntry 3 } 1387 gmplsTunnelReversePerfBytes OBJECT-TYPE 1388 SYNTAX Counter32 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "Number of bytes forwarded on the tunnel in the 1393 reverse direction if it is bidirectional." 1394 ::= { gmplsTunnelReversePerfEntry 4 } 1396 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1397 SYNTAX Counter64 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "High capacity counter for number of bytes forwarded 1402 on the tunnel in the reverse direction if it is 1403 bidirectional." 1404 ::= { gmplsTunnelReversePerfEntry 5 } 1406 -- End of gmplsTunnelReversePerfTable 1408 -- GMPLS Tunnel Error Table. 1410 gmplsTunnelErrorTable OBJECT-TYPE 1411 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "This table 'augments' the mplsTunnelTable 1417 This table provides per-tunnel information about 1418 errors. Errors may be detected locally or reported 1419 through the signaling protocol. 1421 Error reporting is not exclusive to GMPLS and this 1422 table may be applied in MPLS systems." 1423 ::= { gmplsTeObjects 6 } 1424 gmplsTunnelErrorEntry OBJECT-TYPE 1425 SYNTAX GmplsTunnelErrorEntry 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "An entry in this table is created by the LSR for 1430 every tunnel where error information is visible to 1431 the LSR. 1432 Note that systems which read the objects in this table 1433 one at a time may experience a discontinuity as the 1434 result of a new error occurring in between object reads. 1435 Systems that are vulnerable to this should read 1436 gmplsTunnelErrorLastTime before and after reading the 1437 other objects." 1438 AUGMENTS { mplsTunnelEntry } 1439 ::= { gmplsTunnelErrorTable 1 } 1441 GmplsTunnelErrorEntry ::= SEQUENCE { 1442 gmplsTunnelErrorLastErrorType INTEGER, 1443 gmplsTunnelErrorLastTime TimeStamp, 1444 gmplsTunnelErrorReporterType INTEGER, 1445 gmplsTunnelErrorReporterIpv4Addr InetAddressIPv4, 1446 gmplsTunnelErrorReporterIpv6Addr InetAddressIPv6, 1447 gmplsTunnelErrorCode Unsigned32, 1448 gmplsTunnelErrorSubcode Unsigned32, 1449 gmplsTunnelErrorHelpString DisplayString 1450 } 1452 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1453 SYNTAX INTEGER { 1454 noError (0), 1455 unknown (1), 1456 localProtocol (2), 1457 remoteProtocol (3), 1458 configuration (4), 1459 pathComputation (5), 1460 localResources (6) 1461 } 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "The nature of the last error. Provides 1466 interpretation context for 1467 gmplsTunnelErrorProtocolCode and 1468 gmplsTunnelErrorProtocolSubcode. A value of noError 1469 (0) shows that there is no error associated with 1471 this tunnel and means that the other objects in this 1472 entry have no meaning." 1473 ::= { gmplsTunnelErrorEntry 1 } 1475 gmplsTunnelErrorLastTime OBJECT-TYPE 1476 SYNTAX TimeStamp 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "The time at which the last error occurred. This is 1481 presented as the value of SysUpTime when the error 1482 occurred or was reported to this node. 1483 If gmplsTunnelErrorLastErrorType has the value 1484 noError (0), then this object is ignored." 1485 ::= { gmplsTunnelErrorEntry 2 } 1487 gmplsTunnelErrorReporterType OBJECT-TYPE 1488 SYNTAX INTEGER { 1489 unknown (0), 1490 localNode (1), 1491 localIpV4 (2), 1492 remoteIpV4 (3), 1493 localIpV6 (4), 1494 remoteIpV6 (5) 1495 } 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "The reporter of the last error recorded. 1500 This object is used principally to aid in 1501 interpretation of gmplsTunnelErrorReporterIpv4Addr 1502 and gmplsTunnelErrorReporterIpv6Addr. Where the 1503 error has been locally generated and there is no 1504 requirement to associate the error with any specific 1505 local address (such as an interface), the value 1506 localNode (2) may be used. 1507 If gmplsTunnelErrorLastError has the value noError 1508 (0), then this object is ignored." 1509 ::= { gmplsTunnelErrorEntry 3 } 1511 gmplsTunnelErrorReporterIpv4Addr OBJECT-TYPE 1512 SYNTAX InetAddressIPv4 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "The address of the node reporting the last error, or 1517 the address of the resource (such as an interface) 1518 associated with the error. 1519 If gmplsTunnelErrorLastErrorType has the value 1520 noError (0), then this object is ignored. 1521 This object only has meaning if the object 1522 gmplsTunnelErrorReporterType has value localIpV4 (2) 1523 or remoteIpV4 (3). Otherwise the object should 1524 contain the value zero and should be ignored." 1525 ::= { gmplsTunnelErrorEntry 4 } 1527 gmplsTunnelErrorReporterIpv6Addr OBJECT-TYPE 1528 SYNTAX InetAddressIPv6 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "The address of the node reporting the last error, or 1533 the address of the resource (such as an interface) 1534 associated with the error. 1535 If gmplsTunnelErrorLastErrorType has the value 1536 noError (0), then this object is ignored. 1537 This object only has meaning if the object 1538 gmplsTunnelErrorReporterType has value localIpV6 (4) 1539 or remoteIpV4 (5). Otherwise the object should 1540 contain the value zero and should be ignored." 1541 ::= { gmplsTunnelErrorEntry 5 } 1543 gmplsTunnelErrorCode OBJECT-TYPE 1544 SYNTAX Unsigned32 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The primary error code associated with the last 1549 error. 1551 The interpretation of this error code depends on the 1552 value of gmplsTunnelErrorLastErrorType. If the value 1553 of gmplsTunnelErrorLastErrorType is noError (0) the 1554 value of this object should be 0 and should be 1555 ignored. If the value of 1556 gmplsTunnelErrorLastErrorType is localProtocol (2) 1557 or remoteProtocol (3) the error should be 1558 interpreted in the context of the signling protocol 1559 identified by the mplsTunnelSignallingProto object. 1561 Values in excess 32767 of are not used by signaling 1562 protocols and may safely be used as implementation- 1563 specific error codes. " 1564 ::= { gmplsTunnelErrorEntry 6 } 1566 gmplsTunnelErrorSubcode OBJECT-TYPE 1567 SYNTAX Unsigned32 1568 MAX-ACCESS read-only 1569 STATUS current 1570 DESCRIPTION 1571 "The secondary error code associated with the last 1572 error and the protocol used to signal this tunnel. 1573 This value is interprettd in the context of the 1574 value of gmplsTunnelErrorCode. 1575 If the value of gmplsTunnelErrorLastErrorType is 1576 noError (0) the value of this object should be 0 and 1577 should be ignored." 1578 ::= { gmplsTunnelErrorEntry 7 } 1580 gmplsTunnelErrorHelpString OBJECT-TYPE 1581 SYNTAX DisplayString 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "A textual string containing information about the 1586 last error, recovery actions and support advice. If 1587 there is no help string this object contains a zero 1588 length string. 1589 If the value of gmplsTunnelErrorLastErrorType is 1590 noError (0) this object should contain a zero length 1591 string, but may contain a help string indicating 1592 that there is no error." 1593 ::= { gmplsTunnelErrorEntry 8 } 1594 -- Module compliance. 1596 gmplsTeGroups 1597 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1599 gmplsTeCompliances 1600 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1602 gmplsTeModuleCompliance MODULE-COMPLIANCE 1603 STATUS current 1604 DESCRIPTION 1605 "Compliance statement for agents that support the 1606 GMPLS TE MIB." 1607 MODULE -- this module 1609 -- The mandatory group has to be implemented by all 1610 -- LSRs that originate/terminate ESLSPs/tunnels. 1611 -- In addition, depending on the type of tunnels 1612 -- supported, other groups become mandatory as 1613 -- explained below. 1615 MANDATORY-GROUPS { 1616 gmplsTunnelGroup, 1617 gmplsTunnelScalarGroup 1618 } 1620 -- GROUP gmplsTunnelManualGroup 1621 -- DESCRIPTION 1622 -- "This group is mandatory for devices which support 1623 -- manual configuration of tunnels, in addition to 1624 -- gmplsTunnelGroup. The following constraints apply: 1625 -- mplsTunnelSignallingProto should be at least read- 1626 -- only with a value of none(1)." 1628 GROUP gmplsTunnelSignaledGroup 1629 DESCRIPTION 1630 "This group is mandatory for devices which support 1631 signaled tunnel set up, in addition to 1632 gmplsTunnelGroup. The following constraints apply: 1634 mplsTunnelSignallingProto should be at least read- 1635 only returning a value of ldp(2), or rsvp(3)." 1637 GROUP gmplsTunnelIsNotIntfcGroup 1638 DESCRIPTION 1639 "This group is mandatory for devices which support 1640 tunnels that are not interfaces, in addition to 1641 gmplsTunnelGroup. The following constraints apply: 1643 gmplsTunnelIsIf must at least be read-only returning 1644 no(0)." 1646 GROUP gmplsTunnelIsIntfcGroup 1647 DESCRIPTION 1648 "This group is mandatory for devices which support 1649 tunnels that are interfaces, in addition to 1650 gmplsTunnelGroup." 1652 GROUP gmplsTunnelOptionalGroup 1653 DESCRIPTION 1654 "Objects in this group are optional." 1656 -- GMPLS Tunnel scalars. 1657 -- All scalars have max access read-only 1659 -- gmplsTunnelTable 1661 OBJECT gmplsTunnelAttributes 1662 MIN-ACCESS read-only 1663 DESCRIPTION 1664 "Write access is not required." 1666 OBJECT gmplsTunnelLSPEncoding 1667 SYNTAX Integer32 1668 MIN-ACCESS read-only 1669 DESCRIPTION 1670 "Write access is not required." 1672 OBJECT gmplsTunnelSwitchingType 1673 SYNTAX Integer32 1674 MIN-ACCESS read-only 1675 DESCRIPTION 1676 "Write access is not required." 1678 OBJECT gmplsTunnelLinkProtection 1679 MIN-ACCESS read-only 1680 DESCRIPTION 1681 "Write access is not required." 1683 OBJECT gmplsTunnelGPid 1684 MIN-ACCESS read-only 1685 DESCRIPTION 1686 "Write access is not required." 1688 OBJECT gmplsTunnelSecondary 1689 SYNTAX TruthValue 1690 MIN-ACCESS read-only 1691 DESCRIPTION 1692 "Write access is not required." 1694 OBJECT gmplsTunnelDirection 1695 SYNTAX INTEGER { 1696 forward (0), 1697 bidirectional (1) 1698 } 1699 MIN-ACCESS read-only 1700 DESCRIPTION 1701 "Only forward (0) is required." 1703 OBJECT gmplsTunnelPathComp 1704 SYNTAX INTEGER { 1705 dynamicFull(1), -- CSPF fully computed 1706 explicit(2), -- fully 1707 dynamicPartial(3) -- CSPF partially computed 1708 } 1709 MIN-ACCESS read-only 1710 DESCRIPTION 1711 "Only explicit (2) is required." 1713 OBJECT gmplsTunnelUpNotRecip 1714 SYNTAX IpAddress 1715 MIN-ACCESS read-only 1716 DESCRIPTION 1717 "Write access is not required." 1719 OBJECT gmplsTunnelDownNotRecip 1720 SYNTAX IpAddress 1721 MIN-ACCESS read-only 1722 DESCRIPTION 1723 "Write access is not required." 1725 OBJECT gmplsTunnelAdminStatusFlags 1726 SYNTAX BITS { 1727 delInProgress (0), 1728 adminDown (1), 1729 testing (2), 1730 reflect (31) 1731 } 1732 MIN-ACCESS read-only 1733 DESCRIPTION 1734 "Write access is not required." 1736 -- gmplsTunnelHopTable 1738 -- gmplsTunnelHopLabelStatuses has max access read-only 1740 OBJECT gmplsTunnelHopExplicitLabel 1741 MIN-ACCESS read-only 1742 DESCRIPTION 1743 "Write access is not required." 1745 OBJECT gmplsTunnelHopExpRvrsLabel 1746 MIN-ACCESS read-only 1747 DESCRIPTION 1748 "Write access is not required." 1750 -- gmplsTunnelARHopTable 1751 -- all objects have max access read-only 1753 -- glmpsTunnelCHopTable 1754 -- all objects have max access read-only 1756 -- gmplsTunnelReversePerfTable 1757 -- all objects have max access read-only 1759 -- gmplsTunnelErrorTable 1760 -- all objects have max access read-only 1762 ::= { gmplsTeCompliances 1 } 1763 -- Units of conformance. 1765 gmplsTunnelGroup OBJECT-GROUP 1766 OBJECTS { 1767 gmplsTunnelDirection, 1768 gmplsTunnelReversePerfPackets, 1769 gmplsTunnelReversePerfHCPackets, 1770 gmplsTunnelReversePerfErrors, 1771 gmplsTunnelReversePerfBytes, 1772 gmplsTunnelReversePerfHCBytes, 1773 gmplsTunnelErrorLastErrorType, 1774 gmplsTunnelErrorLastTime, 1775 gmplsTunnelErrorReporterType, 1776 gmplsTunnelErrorReporterIpv4Addr, 1777 gmplsTunnelErrorReporterIpv6Addr, 1778 gmplsTunnelErrorCode, 1779 gmplsTunnelErrorSubcode, 1780 gmplsTunnelErrorHelpString 1781 } 1782 STATUS current 1783 DESCRIPTION 1784 "Necessary, but not sufficient, set of objects to implement 1785 tunnels. In addition, depending on the type of the tunnels 1786 supported (for example, manually configured or signaled, 1787 persistent or non-persistent, etc.), the following other 1788 groups defined below are mandatory: gmplsTunnelManualGroup 1789 and/or gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup 1790 and/or gmplsTunnelIsIntfcGroup." 1791 ::= { gmplsTeGroups 1 } 1793 -- gmplsTunnelManualGroup OBJECT-GROUP 1794 -- OBJECTS { 1795 -- mplsTunnelSignallingProto 1796 -- } 1797 -- STATUS current 1798 -- DESCRIPTION 1799 -- "Object(s) needed to implement manually configured 1800 -- tunnels." 1801 -- ::= { gmplsTeGroups 2 } 1803 gmplsTunnelSignaledGroup OBJECT-GROUP 1804 OBJECTS { 1805 gmplsTunnelAttributes, 1806 gmplsTunnelLSPEncoding, 1807 gmplsTunnelSwitchingType, 1808 gmplsTunnelLinkProtection, 1809 gmplsTunnelGPid, 1810 gmplsTunnelSecondary, 1811 gmplsTunnelPathComp, 1812 gmplsTunnelUpNotRecip, 1813 gmplsTunnelDownNotRecip, 1814 gmplsTunnelAdminStatusFlags, 1815 gmplsTunnelHopLabelStatuses, 1816 gmplsTunnelHopExplicitLabel, 1817 gmplsTunnelHopExpRvrsLabel 1818 } 1819 STATUS current 1820 DESCRIPTION 1821 "Objects needed to implement signaled tunnels." 1822 ::= { gmplsTeGroups 3 } 1824 gmplsTunnelScalarGroup OBJECT-GROUP 1825 OBJECTS { 1826 gmplsTunnelsConfigured, 1827 gmplsTunnelsActive 1828 } 1829 STATUS current 1830 DESCRIPTION 1831 "Scalar objects needed to implement MPLS tunnels." 1832 ::= { gmplsTeGroups 4 } 1834 gmplsTunnelIsIntfcGroup OBJECT-GROUP 1835 OBJECTS { 1836 gmplsTunnelUnnumIf 1837 } 1838 STATUS current 1839 DESCRIPTION 1840 "Objects needed to implement tunnels that are 1841 interfaces." 1842 ::= { gmplsTeGroups 5 } 1844 gmplsTunnelIsNotIntfcGroup OBJECT-GROUP 1845 OBJECTS { 1846 gmplsTunnelUnnumIf 1847 } 1848 STATUS current 1849 DESCRIPTION 1850 "Objects needed to implement tunnels that are not 1851 interfaces." 1852 ::= { gmplsTeGroups 6 } 1854 gmplsTunnelOptionalGroup OBJECT-GROUP 1855 OBJECTS { 1856 gmplsTunnelARHopLabelStatuses, 1857 gmplsTunnelARHopExplicitLabel, 1858 gmplsTunnelARHopExpRvrsLabel, 1859 gmplsTunnelARHopProtection, 1860 gmplsTunnelCHopLabelStatuses, 1861 gmplsTunnelCHopExplicitLabel, 1862 gmplsTunnelCHopExpRvrsLabel 1863 } 1864 STATUS current 1865 DESCRIPTION 1866 "The objects in this group are optional." 1867 ::= { gmplsTeGroups 7 } 1869 END 1871 9. Security Considerations 1873 It is clear that the MIB modules described in this document in 1874 association with the MPLS-TE-STD-MIB are potentially useful for 1875 monitoring of MPLS and GMPLS tunnels. These MIB modules can also be 1876 used for configuration of certain objects, and anything that can be 1877 configured can be incorrectly configured, with potentially disastrous 1878 results. 1880 There are a number of management objects defined in these MIB modules 1881 with a MAX-ACCESS clause of read-write and/or read-create. Such 1882 objects may be considered sensitive or vulnerable in some network 1883 environments. The support for SET operations in a non-secure 1884 environment without proper protection can have a negative effect on 1885 network operations. These are the tables and objects and their 1886 sensitivity/vulnerability: 1888 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 1889 objects to provision GMPLS tunnels interfaces at their ingress 1890 LSRs. Unauthorized write access to objects in these tables, could 1891 result in disruption of traffic on the network. This is especially 1892 true if a tunnel has already been established. The use of stronger 1893 mechanisms such as SNMPv3 security should be considered where 1894 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 1895 SNMPv3 agent which implements these MIB modules. 1897 Some of the readable objects in these MIB modules "i.e., objects with 1898 a MAX-ACCESS other than not-accessible" may be considered sensitive 1899 or vulnerable in some network environments. It is thus important to 1900 control even GET and/or NOTIFY access to these objects and possibly 1901 to even encrypt the values of these objects when sending them over 1902 the network via SNMP. These are the tables and objects and their 1903 sensitivity/vulnerability: 1905 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 1906 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, 1907 gmplsTunnelErrorTable collectively show the tunnel network 1908 topology and status. If an Administrator does not want to reveal 1909 this information, then these tables should be considered 1910 sensitive/vulnerable. 1912 SNMP versions prior to SNMPv3 did not include adequate security. Even 1913 if the network itself is secure "for example by using IPSec", even 1914 then, there is no control as to who on the secure network is allowed 1915 to access and GET/SET "read/change/create/delete" the objects in 1916 these MIB modules. It is RECOMMENDED that implementers consider the 1917 security features as provided by the SNMPv3 framework "see [RFC3410], 1918 section 8", including full support for the SNMPv3 cryptographic 1919 mechanisms "for authentication and privacy". 1921 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1922 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1923 enable cryptographic security. It is then a customer/operator 1924 responsibility to ensure that the SNMP entity giving access to an 1925 instance of this MIB module, is properly configured to give access to 1926 the objects only to those principals "users" that have legitimate 1927 rights to indeed GET or SET "change/create/delete" them. 1929 10. Acknowledgments 1931 This draft extends [TEMIB]. The authors would like to express their 1932 gratitude to all those who worked on that earlier MIB document. 1933 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 1934 contributions during an early implementation, and to Baktha 1935 Muralidharan for his review. 1937 Special thanks to Joan Cucchiara and Len Nieman for their help with 1938 compilation issues. 1940 11. References 1942 11.1. Normative References 1944 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1945 Requirement Levels", BCP 14, RFC 2119, March 1997. 1947 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1948 Case, J., Rose, M., and S. Waldbusser, "Structure 1949 of Management Information Version 2 (SMIv2)", STD 1950 58, RFC 2578, April 1999. 1952 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1953 Case, J., Rose, M., and S. Waldbusser, "Textual 1954 Conventions for SMIv2", STD 58, RFC 2579, April 1955 1999. 1957 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1958 Case, J., Rose, M., and S. Waldbusser, "Conformance 1959 Statements for SMIv2", STD 58, RFC 2580, April 1960 1999. 1962 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1963 "Multiprotocol Label Switching Architecture", RFC 1964 3031, January 2001. 1966 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 1967 Srinivasan, V., and G. Swallow, "RSVP-TE: 1968 Extensions to RSVP for LSP Tunnels", RFC 3209, 1969 December 2001. 1971 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 1972 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 1973 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 1974 T., Feldman, N., Fredette, A., Girish, M., Gray, 1975 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 1976 A., and P. Vaananen, "Constraint-Based LSP Setup 1977 using LDP", RFC 3212, December 2001." 1979 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 1980 Label Switching (GMPLS) Signaling Functional 1981 Description", RFC 3471, January 2003. 1983 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 1984 "Generalized MPLS Signaling - CR-LDP Extensions", 1985 RFC 3472, January 2003. 1987 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 1988 RSVP-TE Extensions", RFC 3473, January 2003. 1990 [RFC3477] Kompella, K. and Rekhter, Y., "Signalling Unnumbered 1991 Links in RSVP-TE", RFC 3477, January 2003. 1993 [RFC3480] Kompella, K., Rekhter, Y. and Kullberg, A., 1994 "Signalling Unnumbered Links in CR-LDP", RFC 3480, 1995 February 2003. 1997 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 1998 Label Switching (GMPLS) Architecture", Internet 1999 Draft , May 2000 2003, work in progress. 2002 [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., A., Farrel, A., Hall, 2003 T., and Harrison, E., "Generalized Multiprotocol 2004 Label Switching (GMPLS) Label Switching Router 2005 (LSR) Management Information Base", draft-ietf- 2006 ccamp-gmpls-lsr-mib-03.txt, November 2003, work in 2007 progress. 2009 [GMPLSOSPF] Kompella, K., et al., "OSPF Extensions in Support 2010 of Generalized MPLS", draft-ietf-ccamp-ospf-gmpls- 2011 extensions-11.txt, October 2002, work in progress. 2013 [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 2014 and Harrison, E., "Definitions of Textual 2015 Conventions for Multiprotocol Label Switching 2016 (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib- 2017 03.txt, November 2003, work in progress. 2019 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, 2020 "Multiprotocol Label Switching (MPLS) Label 2021 Switching Router (LSR) Management Information 2022 Base", Internet Draft , August 2003, work in progress. 2025 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of 2026 Textual Conventions for Multiprotocol Label 2027 Switching (MPLS) Management", Internet Draft 2028 , August 2003, work 2029 in progress. 2031 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 2032 "Multiprotocol Label Switching (MPLS) Traffic 2033 Engineering Management Information Base", Internet 2034 Draft , August 2003, 2035 work in progress. 2037 11.2. Informational References 2039 [RFC2026] S. Bradner, "The Internet Standards Process -- 2040 Revision 3", RFC 2026, October 1996. 2042 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 2043 Applications", RFC 3413, December 2002. 2045 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2046 "Introduction and Applicability Statements for 2047 Internet-Standard Management Framework", RFC 3410, 2048 December 2002. 2050 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2051 Architecture for Describing Simple Network 2052 Management Protocol (SNMP) Management Frameworks", 2053 RFC 3411, December 2002. 2055 12. Authors' Addresses 2057 Thomas D. Nadeau 2058 Cisco Systems, Inc. 2059 300 Apollo Drive 2060 Chelmsford, MA 01824 2061 Phone: +1-978-244-3051 2062 Email: tnadeau@cisco.com 2064 Cheenu Srinivasan 2065 Bloomberg L.P. 2066 499 Park Ave., 2067 New York, NY 10022 2068 Phone: +1-212-893-3682 2069 Email: cheenu@bloomberg.net 2071 Adrian Farrel 2072 Old Dog Consulting 2073 Phone: +44-(0)-1978-860944 2074 Email: adrian@olddog.co.uk 2076 Tim Hall 2077 Data Connection Ltd. 2078 100 Church Street 2079 Enfield, Middlesex 2080 EN2 6BQ, UK 2081 Phone: +44 20 8366 1177 2082 Email: timhall@dataconnection.com 2084 Ed Harrison 2085 Data Connection Ltd. 2086 100 Church Street 2087 Enfield, Middlesex 2088 EN2 6BQ, UK 2089 Phone: +44 20 8366 1177 2090 Email: ed.harrison@dataconnection.com 2092 13. Full Copyright Statement 2094 Copyright (C) The Internet Society (2003). All Rights Reserved. 2095 This document and translations of it may be copied and furnished to 2096 others, and derivative works that comment on or otherwise explain it 2097 or assist in its implementation may be prepared, copied, published 2098 and distributed, in whole or in part, without restriction of any 2099 kind, provided that the above copyright notice and this paragraph are 2100 included on all such copies and derivative works. However, this 2101 document itself may not be modified in any way, such as by removing 2102 the copyright notice or references to the Internet Society or other 2103 Internet organizations, except as needed for the purpose of 2104 developing Internet standards in which case the procedures for 2105 copyrights defined in the Internet Standards process must be 2106 followed, or as required to translate it into languages other than 2107 English. 2109 The limited permissions granted above are perpetual and will not be 2110 revoked by the Internet Society or its successors or assigns. This 2111 document and the information contained herein is provided on an "AS 2112 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2113 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2114 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2115 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2116 OR FITNESS FOR A PARTICULAR PURPOSE. 2118 14. Intellectual Property Notice 2120 The IETF takes no position regarding the validity or scope of any 2121 intellectual property or other rights that might be claimed to 2122 pertain to the implementation or use of the technology described in 2123 this document or the extent to which any license under such rights 2124 might or might not be available; neither does it represent that it 2125 has made any effort to identify any such rights. Information on the 2126 IETF's procedures with respect to rights in standards-track and 2127 standards-related documentation can be found in BCP-11 [RFC2028]. 2128 Copies of claims of rights made available for publication and any 2129 assurances of licenses to be made available, or the result of an 2130 attempt made to obtain a general license or permission for the use 2131 of such proprietary rights by implementers or users of this 2132 specification can be obtained from the IETF Secretariat. 2134 The IETF invites any interested party to bring to its attention any 2135 copyrights, patents or patent applications, or other proprietary 2136 rights that may cover technology that may be required to practice 2137 this standard. Please address the information to the IETF Executive 2138 Director. 2140 15. Changes and Pending Work 2142 This section to be removed before the draft progresses to RFC. 2144 15.1. Pending Work 2146 The following work items have been identified for this draft. They 2147 will be addressed in a future version. 2149 - Expand conformance statements to give one for monitoring only, 2150 and one for monitoring and control. 2151 - Consider a way to expose tunnel head, tunnel tail, and tunnel 2152 transit entries through distinct indexing or tables. 2153 - Provide support for configuring tunnel resources in GMPLS 2154 systems. For example, SONET/SDH or G.709. This might be done 2155 through an arbitrary RowPointer to an external MIB. 2156 - Crankback request and reported information. 2157 - Add support for IF_ID control and error reporting. 2158 - Add LSR or interface config for Hellos and restart options. 2159 - Update enumerated types in line with latest GMPLS drafts. Examine 2160 how these can be managed by IANA. 2161 - Resolve ownership of enumerated types that are also defined in 2162 GMPLS or routing drafts. These could be owned by IANA, imported 2163 from another MIB, or manually kept in step here. If they are not 2164 maintained externally then they are likely to diverge and MIB 2165 implementations will need to provide mappings. 2166 - Update MIB description in section 5. 2168 15.2. Changes from version 2 to version 3 2170 - Work on basic compilation issues. 2171 - Resolve defaults for objects with syntax BITS. 2172 - Update references. 2173 - Clarify which objects can be modified when rowStatus and 2174 adminStatus are set to active. 2175 - Control and reporting of upstream and downstream Notify 2176 Recipients. 2177 - Add support for control and reporting of GMPLS Administrative 2178 Status object. 2179 - Update examples. 2181 Network Working Group Thomas D. Nadeau 2182 Internet Draft Cisco Systems, Inc. 2183 Expires: May 2004 2184 Cheenu Srinivasan 2185 Bloomberg L.P. 2187 Adrian Farrel 2188 Old Dog Consulting 2190 Tim Hall 2191 Ed Harrison 2192 Data Connection Ltd. 2194 November 2003 2196 Generalized Multiprotocol Label Switching (GMPLS) 2197 Label Switching Router (LSR) Management Information Base 2199 draft-ietf-ccamp-gmpls-lsr-mib-03.txt 2201 Status of this Memo 2203 This document is an Internet-Draft and is in full conformance with 2204 all provisions of Section 10 of RFC 2026. 2206 Internet-Drafts are working documents of the Internet Engineering 2207 Task Force (IETF), its areas, and its working groups. Note that 2208 other groups may also distribute working documents as Internet- 2209 Drafts. 2211 Internet-Drafts are draft documents valid for a maximum of six 2212 months and may be updated, replaced, or obsoleted by other documents 2213 at any time. It is inappropriate to use Internet-Drafts as 2214 reference material or to cite them other than as "work in progress." 2216 The list of current Internet-Drafts can be accessed at 2217 http://www.ietf.org/ietf/1id-abstracts.txt. 2219 Abstract 2221 This memo defines a portion of the Management Information Base (MIB) 2222 for use with network management protocols in the Internet community. 2223 In particular, it describes managed objects to configure and/or 2224 monitor a Generalized Multiprotocol Label Switching (GMPLS) Label 2225 Switching Router (LSRs). 2227 Table of Contents 2229 1. Introduction 2 2230 1.1. Migration Strategy 2 2231 2. Terminology 3 2232 3. The SNMP Management Framework 3 2233 4. Outline 3 2234 4.1. Summary of the GMPLS LSR MIB Module 4 2235 5. Bidirectional LSPs 4 2236 6. Example of LSP Setup 5 2237 7. GMPLS Label Switching Router MIB Definitions 6 2238 8. GMPLS Label MIB Definitions 14 2239 9. Security Considerations 25 2240 10. Acknowledgments 26 2241 11. IANA Considerations 27 2242 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 27 2243 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB 27 2244 12. References 27 2245 12.1. Normative References 27 2246 12.2. Informational References 28 2247 13. Authors' Addresses 29 2248 14. Full Copyright Statement 30 2249 15. Intellectual Property Notice 30 2250 16. Changes and Pending Work 31 2251 16.1. Pending Work 31 2253 1. Introduction 2255 This memo defines a portion of the Management Information Base (MIB) 2256 for use with network management protocols in the Internet community. 2257 In particular, it describes managed objects for modeling a 2258 Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label 2259 Switching Router (LSR). 2261 Comments should be made directly to the CCAMP mailing list at 2262 ccamp@ops.ietf.org. 2264 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 2265 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 2266 document are to be interpreted as described in RFC 2119, reference 2267 [RFC2119]. 2269 1.1. Migration Strategy 2271 This MIB module extends the Label Switching Router MIB module defined 2272 for use with MPLS [LSRMIB]. The only changes made are additions for 2273 support of GMPLS or changes that are necessary to support the 2274 increased complexity of a GMPLS system. 2276 The companion document modeling and managing GMPLS based traffic 2277 engineering [GMPLSTEMIB] extends the MPLS TE MIB module [TEMIB] with 2278 the same intentions. 2280 Textual conventions and OBJECT-IDENTIFIERS are defined in 2281 [GMPLSTCMIB] which extends the set of textual conventions originally 2282 defined in [TCMIB]. 2284 2. Terminology 2286 This document uses terminology from the document describing the MPLS 2287 architecture [RFC3031] and the GMPLS architecture [GMPLSArch]. 2289 A label switched path (LSP) is modeled as a connection consisting of 2290 one or more incoming segments (in-segments) and/or one or more 2291 outgoing segments (out-segments) at an LSR. The association or 2292 interconnection of the in-segments and out-segments is accomplished 2293 by using a cross-connect. We use the terminology "connection" and 2294 "LSP" interchangeably where the meaning is clear from the context. 2296 in-segment This is analogous to a GMPLS label on an interface. 2297 out-segment This is analogous to a GMPLS label on an interface. 2298 cross-connect This describes the conceptual connection between a 2299 set of in-segments and out-segments. 2300 Note that either set may be 0; that is, a cross- 2301 connect may connect only out-segments together with 2302 no in-segments in the case where an LSP is 2303 originating on an LSR. 2305 3. The SNMP Management Framework 2307 For a detailed overview of the documents that describe the current 2308 Internet-Standard Management Framework, please refer to section 7 of 2309 RFC 3410 [RFC3410]. 2311 Managed objects are accessed via a virtual information store, termed 2312 the Management Information Base or MIB. MIB objects are generally 2313 accessed through the Simple Network Management Protocol (SNMP). 2314 Objects in the MIB are defined using the mechanisms defined in the 2315 Structure of Management Information (SMI). This memo specifies a 2316 MIB module that is compliant to the SMIv2, which is described in STD 2317 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2318 2580 [RFC2580]. 2320 4. Outline 2322 Configuring statically provisioned GMPLS LSPs through an LSR involves 2323 the following steps: 2325 - Configuring an interface using the MPLS LSR MIB module. 2327 - Enabling GMPLS on GMPLS capable interfaces using this MIB module. 2329 - Configuring in-segments and out-segments using the MPLS LSR MIB 2330 module. 2332 - Configuring GMPLS extensions to the in-segments and out-segments 2333 using this MIB module. 2335 - Setting up the cross-connect table in the MPLS LSR MIB module to 2336 associate segments and/or to indicate connection origination and 2337 termination. 2339 - Optionally setting up labels in the label table in this MIB module 2340 if the textual convention 2341 MplsLabel is not capable of holding the required label (for 2342 example, if the label requires more than 32 bits to encode it), or 2343 if the operator wishes to disambiguate GMPLS label types. 2345 - Optionally specifying label stack actions in the MPLS LSR MIB 2346 module. 2348 - Optionally specifying segment traffic parameters in the MPLS LSR 2349 MIB module. 2351 4.1. Summary of the GMPLS LSR MIB Module 2353 The MIB tables in this MIB module are as follows. 2355 - The interface configuration table (gmplsInterfaceTable), which 2356 extends mplsInterfaceTable to enable the GMPLS protocol on MPLS- 2357 capable interfaces. 2359 - The in-segment (gmplsInSegmentTable) and out-segment 2360 (gmplsOutSegmentTable) tables extend mplsInSegmentTable and 2361 mplsOutSegmentTable to configuring GMPLS-specific parameters for 2362 LSP segments at an LSR. 2364 - The gmplsLabelTable extends mplsLabelTable and allows Generalized 2365 Labels to be defined and managed in a central location. 2366 Generalized Labels can be of variable length and have distinct 2367 bit-by-bit interpretations according to the use that is made of 2368 them. 2370 These tables are described in the subsequent sections. 2372 5. Bidirectional LSPs 2374 This MIB supports bidirectional LSPs as required for GMPLS. 2375 A single value of mplsXCIndex is shared by all of the segments for 2376 the entire bidirectional LSP. This facilitates a simple reference 2377 from [TEMIB] and [GMPLSTEMIB], and makes fate-sharing more obvious. 2379 It is, however, important that the direction of segments is 2380 understood to avoid connecting all in-segments to all out-segments. 2381 This is achieved by an object in each segment that indicates the 2382 direction of the segment with respect to data flow. 2384 A segment that is marked as 'forward' carries data from the 'head' of 2385 the LSP to the 'tail'. A segment marked as 'reverse' carries data in 2386 the reverse direction. 2388 Where an LSP is signaled using a conventional signaling protocol, the 2389 'head' of the LSP is the source of the signaling (also known as the 2390 ingress) and the 'tail' is the destination (also known as the 2391 egress). For manually configured LSPs an arbitrary decision must be 2392 made about which segments are 'forward' and which 'reverse'. For 2393 consistency this decision should be made across all LSRs that 2394 participate in the LSP by assigning 'head' and 'tail' ends to the 2395 LSP. 2397 6. Example of LSP Setup 2399 In this section we provide a brief example of using the MIB objects 2400 described in section 9 to set up an LSP. While this example is not 2401 meant to illustrate every nuance of the MIB, it is intended as an aid 2402 to understanding some of the key concepts. It is meant to be read 2403 after going through the MIB itself. A prerequisite is an 2404 understanding of [LSRMIB]. 2406 Suppose that one would like to manually create a best-effort, bi- 2407 directional LSP. Assume that, in the forward direction, the LSP 2408 enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR 2409 via MPLS interface B with ifIndex 13. For the reverse direction, we 2410 assume the LSP enters via interface B and leaves via interface A 2411 (i.e. the forward and reverse directions use the same bi-directional 2412 interfaces). Let us also assume that we do not wish to have a label 2413 stack beneath the top label on the outgoing labeled packets. The 2414 following example illustrates which rows and corresponding objects 2415 might be created to accomplish this. 2417 We must first create rows in the gmplsLabelTable corresponding to the 2418 labels required for each of the forward and reverse direction in- and out- 2419 segments. For the purpose of this example the forward and reverse labels 2420 on each interface will be the same, hence we need to create just two 2421 rows in the gmplsLabelTable - one for each interface. 2423 In gmplsLabelTable: 2424 { 2425 gmplsLabelInterface = 12, 2426 gmplsLabelIndex = 1, 2427 gmplsLabelSubindex = 1, 2428 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 2429 gmplsLabelMplsLabel = 0, 2430 gmplsLabelPortWavelength = 0, 2431 gmplsLabelFreeformLength = 8, 2432 gmplsLabelFreeform = 0x123456789ABCDEF0 2433 gmplsLabelSonetSdhSignalIndex = 0, 2434 gmplsLabelSdhVc = 0, 2435 gmplsLabelSdhVcBranch = 0, 2436 gmplsLabelSonetSdhBranch = 0, 2437 gmplsLabelSonetSdhGroupBranch = 0, 2438 gmplsLabelWavebandId = 0, 2439 gmplsLabelWavebandStartLabel = 0, 2440 gmplsLabelWavebandEndLabel = 0, 2441 gmplsLabelRowStatus = createAndGo(4), 2442 gmplsLabelStorageType = 0 2443 } 2444 In gmplsLabelTable: 2445 { 2446 gmplsLabelInterface = 13, 2447 gmplsLabelIndex = 1, 2448 gmplsLabelSubindex = 1, 2449 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 2450 gmplsLabelMplsLabel = 0, 2451 gmplsLabelPortWavelength = 0, 2452 gmplsLabelFreeformLength = 8, 2453 gmplsLabelFreeform = 0xFEDCBA9876543210 2454 gmplsLabelSonetSdhSignalIndex = 0, 2455 gmplsLabelSdhVc = 0, 2456 gmplsLabelSdhVcBranch = 0, 2457 gmplsLabelSonetSdhBranch = 0, 2458 gmplsLabelSonetSdhGroupBranch = 0, 2459 gmplsLabelWavebandId = 0, 2460 gmplsLabelWavebandStartLabel = 0, 2461 gmplsLabelWavebandEndLabel = 0, 2462 gmplsLabelRowStatus = createAndGo(4), 2463 gmplsLabelStorageType = 0 2464 } 2466 We must next create the appropriate in-segment and out-segment entries. 2467 These are done in [LSRMIB] using the mplsInSegmentTable and 2468 mplsOutSegmentTable. Note that we use a row pointer to the two rows in the 2469 gmplsLableTable rather than specifying the labels explicitly in the 2470 in- and out-segment tables. Also note that the row status for each row 2471 is set to createAndWait(5) to allow corresponding entries in the 2472 gmplsInSegmentTable and gmplsOutSegmentTable to be created. 2474 For the forward direction. 2476 In mplsInSegmentTable: 2477 { 2478 mplsInSegmentIndex = 0x00000015 2479 mplsInSegmentLabel = 0, -- incoming label in label table 2480 mplsInSegmentNPop = 1, 2481 mplsInSegmentInterface = 12, -- incoming interface 2483 -- RowPointer MUST point to the first accesible column. 2484 mplsInSegmentLabelPtr = gmplsLabelInterface.1, 2485 mplsInSegmentTrafficParamPtr = 0.0, 2486 mplsInSegmentRowStatus = createAndWait(5) 2487 } 2489 In mplsOutSegmentTable: 2490 { 2491 mplsOutSegmentIndex = 0x00000012, 2492 mplsOutSegmentInterface = 13, -- outgoing interface 2493 mplsOutSegmentPushTopLabel = true(1), 2494 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 2496 -- RowPointer MUST point to the first accesible column. 2497 mplsOutSegmentTrafficParamPtr = 0.0, 2498 mplsOutSegmentLabelPtr = gmplsLabelInterface.2, 2499 mplsOutSegmentRowStatus = createAndWait(5) 2500 } 2501 For the reverse direction. 2503 In mplsInSegmentTable: 2504 { 2505 mplsInSegmentIndex = 0x00000016 2507 mplsInSegmentLabel = 0, -- incoming label in label table 2508 mplsInSegmentNPop = 1, 2509 mplsInSegmentInterface = 13, -- incoming interface 2511 -- RowPointer MUST point to the first accesible column. 2512 mplsInSegmentLabelPtr = gmplsLabelInterface.2, 2513 mplsInSegmentTrafficParamPtr = 0.0, 2515 mplsInSegmentRowStatus = createAndWait(5) 2516 } 2518 In mplsOutSegmentTable: 2519 { 2520 mplsOutSegmentIndex = 0x00000013, 2521 mplsOutSegmentInterface = 12, -- outgoing interface 2522 mplsOutSegmentPushTopLabel = true(1), 2523 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 2525 -- RowPointer MUST point to the first accesible column. 2526 mplsOutSegmentTrafficParamPtr = 0.0, 2527 mplsOutSegmentLabelPtr = gmplsLabelInterface.1, 2529 mplsOutSegmentRowStatus = createAndWait(5) 2530 } 2532 These table entries are extended by entries in gmplsInSegmentTable 2533 and gmplsOutSegmentTable. Note that the nature of the 'extends' 2534 relationship is that the entry in gmplsInSegmentTable has the same 2535 index values as the entry in mplsInSegmentTable. Similarly, the entry 2536 in gmplsOutSegmentTable has the same index values as the entry in 2537 mplsOutSegmentTable. 2539 First for the forward direction: 2541 In gmplsInSegmentTable(0x00000015) 2542 { 2543 gmplsInSegmentDirection = forward (1) 2544 } 2545 In gmplsOutSegmentTable(0x00000012) 2546 { 2547 gmplsOutSegmentDirection = forward (1), 2548 gmplsOutSegmentTTLDecrement = 1 2549 } 2551 Next for the reverse direction: 2553 In gmplsInSegmentTable(0x00000016) 2554 { 2555 gmplsInSegmentDirection = reverse (2) 2556 } 2557 In gmplsOutSegmentTable(0x00000013) 2558 { 2559 gmplsOutSegmentDirection = reverse (2), 2560 gmplsOutSegmentTTLDecrement = 1 2561 } 2563 Next, two cross-connect entries are created in the mplsXCTable of the 2564 MPLS LSR MIB, thereby associating the newly created segments 2565 together. 2567 In mplsXCTable: 2568 { 2569 mplsXCIndex = 0x01, 2570 mplsXCInSegmentIndex = 0x00000015, 2571 mplsXCOutSegmentIndex = 0x00000012, 2573 mplsXCLspId = 0x0102 -- unique ID 2574 mplsXCLabelStackIndex = 0x00, -- only a single 2575 -- outgoing label 2576 mplsXCRowStatus = createAndGo(4) 2577 } 2579 In mplsXCTable: 2580 { 2581 mplsXCIndex = 0x02, 2582 mplsXCInSegmentIndex = 0x00000016, 2583 mplsXCOutSegmentIndex = 0x00000013, 2585 mplsXCLspId = 0x0102 -- unique ID 2586 mplsXCLabelStackIndex = 0x00, -- only a single 2587 -- outgoing label 2588 mplsXCRowStatus = createAndGo(4) 2589 } 2591 Finally, the in-segments and out-segments are activated. 2593 In mplsInSegmentTable(0x00000015): 2594 { 2595 mplsInSegmentRowStatus = active(1) 2596 } 2598 In mplsInSegmentTable(0x00000016): 2599 { 2600 mplsInSegmentRowStatus = active(1) 2601 } 2603 In mplsOutSegmentTable(0x00000012): 2604 { 2605 mplsOutSegmentRowStatus = active(1) 2606 } 2608 In mplsOutSegmentTable(0x00000013): 2609 { 2610 mplsOutSegmentRowStatus = active(1) 2611 } 2613 7. GMPLS Label Switching Router MIB Definitions 2615 GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN 2617 IMPORTS 2618 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32 2619 FROM SNMPv2-SMI 2620 MODULE-COMPLIANCE, OBJECT-GROUP 2621 FROM SNMPv2-CONF 2622 GmplsSegmentDirection, gmplsStdMIB 2623 FROM GMPLS-TC-STD-MIB 2624 mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex 2625 FROM MPLS-LSR-STD-MIB 2626 ; 2628 gmplsLsrStdMIB MODULE-IDENTITY 2629 LAST-UPDATED 2630 "200310300900Z" -- 30 October 2003 9:00:00 GMT" 2631 ORGANIZATION 2632 "Common Control And Management Protocols (CCAMP) 2633 Working Group" 2634 CONTACT-INFO 2635 " Thomas D. Nadeau 2636 Cisco Systems, Inc. 2637 Email: tnadeau@cisco.com 2639 Cheenu Srinivasan 2640 Bloomberg L.P. 2641 Email: cheenu@bloomberg.net 2643 Adrian Farrel 2644 Old Dog Consulting 2645 Email: adrian@olddog.co.uk 2647 Ed Harrison 2648 Data Connection Ltd. 2649 Email: ed.harrison@dataconnection.com 2651 Tim Hall 2652 Data Connection Ltd. 2653 Email: timhall@dataconnection.com 2655 Comments about this document should be emailed direct to the 2656 CCAMP working group mailing list at ccamp@ops.ietf.org" 2657 DESCRIPTION 2658 "This MIB module contains managed object definitions 2659 for the Generalized Multiprotocol Label Switching 2660 (GMPLS) Router as defined in: Ashwood-Smith et al., 2661 Generalized Multiprotocol Label Switching (GMPLS) 2662 Architecture, Internet Draft , March 2001, work in progress. 2665 Copyright (C) The Internet Society (2003). This 2666 version of this MIB module is part of RFCXXX; see 2667 the RFC itself for full legal notices." 2669 -- Revision history. 2670 REVISION 2671 "200310300900Z" -- 30 October 2003 09:00:00 GMT 2673 DESCRIPTION 2674 "Initial revision, published as part of RFC XXXX." 2675 ::= { gmplsStdMIB xx } 2677 -- Top level components of this MIB module. 2679 -- Notifications 2680 -- no notifications are currently defined. 2681 gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 } 2683 -- Tables, Scalars 2684 gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } 2686 -- Conformance 2687 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } 2689 -- GMPLS Interface Table. 2691 gmplsInterfaceTable OBJECT-TYPE 2692 SYNTAX SEQUENCE OF GmplsInterfaceEntry 2693 MAX-ACCESS not-accessible 2694 STATUS current 2695 DESCRIPTION 2696 "This table specifies per-interface GMPLS capability 2697 and associated information. It extends the 2698 information in mplsInterfaceTable." 2699 ::= { gmplsLsrObjects 1 } 2701 gmplsInterfaceEntry OBJECT-TYPE 2702 SYNTAX GmplsInterfaceEntry 2703 MAX-ACCESS not-accessible 2704 STATUS current 2705 DESCRIPTION 2706 "A conceptual row in this table is created 2707 automatically by an LSR for every interface capable 2708 of supporting GMPLS and which is configured to do 2709 so. A conceptual row in this table will exist if and 2710 only if a corresponding entry in mplsInterfaceTable 2711 exists, and a corresponding entry in ifTable exists 2712 with ifType = mpls(166). If the associated entry in 2713 ifTable is operationally disabled (thus removing the 2714 GMPLS capabilities on the interface) or the entry in 2715 mplsInterfaceTable is deleted, the corresponding 2716 entry in this table MUST be deleted shortly 2717 thereafter. 2719 The indexing is the same as that for mplsInterfaceTable. 2720 Thus, the entry with index 0 represents the per-platform 2721 label space and contains parameters that apply to all 2722 interfaces that participate in the per-platform label space." 2723 INDEX { mplsInterfaceIndex } 2724 ::= { gmplsInterfaceTable 1 } 2725 GmplsInterfaceEntry ::= SEQUENCE { 2726 gmplsInterfaceSignalingCaps BITS 2727 } 2729 gmplsInterfaceSignalingCaps OBJECT-TYPE 2730 SYNTAX BITS { 2731 unknown (0), 2732 rsvpGmpls (1), 2733 crldpGmpls (2), -- note the use of CR-LDP is deprecated 2734 otherGmpls (3) 2735 } 2736 MAX-ACCESS read-create 2737 STATUS current 2738 DESCRIPTION 2739 "Defines the signaling capabilities on this 2740 interface. Multiple bits may legitimately be set at 2741 once. Setting no bits implies that GMPLS signaling 2742 cannot be performed on this interface and all LSPs 2743 must be manually provisioned." 2744 ::= { gmplsInterfaceEntry 1 } 2746 -- End of gmplsInterfaceTable 2748 -- In-segment table. 2750 gmplsInSegmentTable OBJECT-TYPE 2751 SYNTAX SEQUENCE OF GmplsInSegmentEntry 2752 MAX-ACCESS not-accessible 2753 STATUS current 2754 DESCRIPTION 2755 "This table extends the mplsInSegmentTable to provide 2756 GMPLS-specific information about incoming segments 2757 to an LSR." 2758 ::= { gmplsLsrObjects 2 } 2760 gmplsInSegmentEntry OBJECT-TYPE 2761 SYNTAX GmplsInSegmentEntry 2762 MAX-ACCESS not-accessible 2763 STATUS current 2764 DESCRIPTION 2765 "An entry in this table extends the representation of 2766 an incoming segment represented by an entry in 2767 mplsInSegmentTable. An entry can be created by a 2768 network administrator or an SNMP agent, or a GMPLS 2769 signaling protocol. 2771 Note that the storage type for this entry SHOULD be 2772 inherited from the corresponding entry in the 2773 mplsInSegmentTable given by the value of the 2774 mplsInSegmentStorageType object." 2775 INDEX { mplsInSegmentIndex } 2776 ::= { gmplsInSegmentTable 1 } 2778 GmplsInSegmentEntry ::= SEQUENCE { 2779 gmplsInSegmentDirection GmplsSegmentDirection 2780 } 2781 gmplsInSegmentDirection OBJECT-TYPE 2782 SYNTAX GmplsSegmentDirection 2783 MAX-ACCESS read-create 2784 STATUS current 2785 DESCRIPTION 2786 "This object indicates the direction of data flow on 2787 this segment. This object cannot be modified if 2788 mplsInSegmentRowStatus for the associated entry in 2789 the mplsInSegmentTable is active(1)." 2790 DEFVAL { forward } 2791 ::= { gmplsInSegmentEntry 1 } 2793 -- End of gmplsInSegmentTable 2795 -- Out-segment table. 2797 gmplsOutSegmentTable OBJECT-TYPE 2798 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 2799 MAX-ACCESS not-accessible 2800 STATUS current 2801 DESCRIPTION 2802 "This table extends the mplsOutSegmentTable to 2803 provide GMPLS-specific information about outgoing 2804 segments from an LSR." 2805 ::= { gmplsLsrObjects 3 } 2807 gmplsOutSegmentEntry OBJECT-TYPE 2808 SYNTAX GmplsOutSegmentEntry 2809 MAX-ACCESS not-accessible 2810 STATUS current 2811 DESCRIPTION 2812 "An entry in this table extends the representation of 2813 an outgoing segment represented by an entry in 2814 mplsOutSegmentTable. An entry can be created by a 2815 network administrator or an SNMP agent, or a GMPLS 2816 signaling protocol. 2817 Note that the storage type for this entry SHOULD be 2818 inherited from the corresponding entry in the 2819 mplsOutSegmentTable given by the value of the 2820 mplsOutSegmentStorageType object." 2821 INDEX { mplsOutSegmentIndex } 2822 ::= { gmplsOutSegmentTable 1 } 2824 GmplsOutSegmentEntry ::= SEQUENCE { 2825 gmplsOutSegmentDirection GmplsSegmentDirection, 2826 gmplsOutSegmentTTLDecrement Unsigned32 2827 } 2829 gmplsOutSegmentDirection OBJECT-TYPE 2830 SYNTAX GmplsSegmentDirection 2831 MAX-ACCESS read-create 2832 STATUS current 2833 DESCRIPTION 2834 "This object indicates the direction of data flow on 2835 this segment. This object cannot be modified if 2836 mplsOutSegmentRowStatus for the associated entry in 2837 the mplsOutSegmentTable is active(1)." 2839 DEFVAL { forward } 2840 ::= { gmplsOutSegmentEntry 1 } 2842 gmplsOutSegmentTTLDecrement OBJECT-TYPE 2843 SYNTAX Unsigned32 (0..255) 2844 MAX-ACCESS read-create 2845 STATUS current 2846 DESCRIPTION 2847 "This object indicates the amount by which to 2848 decrement the TTL of any payload packets forwarded 2849 on this segment if per-hop decrementing is being 2850 done. 2852 A value of zero indicates that no decrement should 2853 be made or that per-hop decrementing is not in 2854 force. 2856 See the gmplsTunnelTTLDecrement object in the 2857 gmplsTunnelTable of [GMPLSTEMIB] for a value by 2858 which to decrement the TTL for the whole of a 2859 tunnel. 2861 This object cannot be modified if 2862 mplsOutSegmentRowStatus for the associated entry in 2863 the mplsOutSegmentTable is active(1)." 2864 DEFVAL { 0 } 2865 ::= { gmplsOutSegmentEntry 2 } 2867 -- End of gmplsOutSegmentTable 2869 -- Module compliance. 2871 gmplsLsrGroups 2872 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 2874 gmplsLsrCompliances 2875 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 2877 -- Compliance requirement for fully compliant implementations. 2879 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 2880 STATUS current 2881 DESCRIPTION 2882 "Compliance statement for agents that provide full 2883 support for GMPLS-LSR-STD-MIB." 2885 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 2887 MANDATORY-GROUPS { 2888 ifGeneralInformationGroup, 2889 ifCounterDiscontinuityGroup 2890 } 2891 MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB 2893 MANDATORY-GROUPS { 2894 mplsInterfaceGroup, 2895 mplsInSegmentGroup, 2896 mplsOutSegmentGroup, 2897 mplsXCGroup, 2898 mplsPerfGroup, 2899 mplsLsrNotificationGroup 2900 } 2902 MODULE -- this module 2904 MANDATORY-GROUPS { 2905 gmplsInterfaceGroup, 2906 gmplsInSegmentGroup, 2907 gmplsOutSegmentGroup 2908 } 2910 -- gmplsInSegmentTable 2912 OBJECT gmplsInSegmentDirection 2913 SYNTAX GmplsSegmentDirection 2914 MIN-ACCESS read-write 2915 DESCRIPTION 2916 "Only forward(1) needs to be supported by 2917 implementations that only support unidirectional 2918 LSPs." 2920 -- gmplsOutSegmentTable 2922 OBJECT gmplsOutSegmentDirection 2923 SYNTAX GmplsSegmentDirection 2924 MIN-ACCESS read-write 2925 DESCRIPTION 2926 "Only forward(1) needs to be supported by 2927 implementations that only support unidirectional 2928 LSPs." 2930 OBJECT gmplsOutSegmentTTLDecrement 2931 SYNTAX Unsigned32 (0..255) 2932 MIN-ACCESS read-only 2933 DESCRIPTION 2934 "Write access is not required." 2936 ::= { gmplsLsrCompliances 1 } 2938 -- Compliance requirement for implementations that provide read-only 2939 -- access. 2941 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 2942 STATUS current 2943 DESCRIPTION 2944 "Compliance requirement for implementations that only 2945 provide read-only support for GMPLS-LSR-STD-MIB. Such 2946 devices can then be monitored but cannot be configured 2947 using this MIB modules." 2949 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 2951 MANDATORY-GROUPS { 2952 ifGeneralInformationGroup, 2953 ifCounterDiscontinuityGroup 2954 } 2956 MODULE MPLS-LSR-STD-MIB 2958 MANDATORY-GROUPS { 2959 mplsInterfaceGroup, 2960 mplsInSegmentGroup, 2961 mplsOutSegmentGroup, 2962 mplsXCGroup, 2963 mplsPerfGroup 2964 } 2966 MODULE -- this module 2968 MANDATORY-GROUPS { 2969 gmplsInterfaceGroup, 2970 gmplsInSegmentGroup, 2971 gmplsOutSegmentGroup 2972 } 2974 -- gmplsInterfaceGroup 2976 OBJECT gmplsInterfaceSignalingCaps 2977 SYNTAX BITS { 2978 unknown (0), 2979 rsvpGmpls (1), 2980 crldpGmpls (2), 2981 otherGmpls (3) 2982 } 2983 MIN-ACCESS read-only 2984 DESCRIPTION 2985 "Write access is not required." 2987 -- gmplsInSegmentTable 2989 OBJECT gmplsInSegmentDirection 2990 SYNTAX GmplsSegmentDirection 2991 MIN-ACCESS read-only 2992 DESCRIPTION 2993 "Write access is not required. Only forward(1) needs 2994 to be supported by implementations that only support 2995 unidirectional LSPs." 2997 -- gmplsOutSegmentTable 2999 OBJECT gmplsOutSegmentDirection 3000 SYNTAX GmplsSegmentDirection 3001 MIN-ACCESS read-only 3002 DESCRIPTION 3003 "Write access is not required. Only forward(1) needs 3004 to be supported by implementations that only support 3005 unidirectional LSPs." 3007 OBJECT gmplsOutSegmentTTLDecrement 3008 SYNTAX Unsigned32 (0..255) 3009 MIN-ACCESS read-only 3010 DESCRIPTION 3011 "Write access is not required." 3013 ::= { gmplsLsrCompliances 2 } 3015 -- Units of conformance. 3017 gmplsInterfaceGroup OBJECT-GROUP 3018 OBJECTS { 3019 gmplsInterfaceSignalingCaps 3020 } 3021 STATUS current 3022 DESCRIPTION 3023 "Collection of objects needed for GMPLS interface 3024 configuration and performance information." 3025 ::= { gmplsLsrGroups 1 } 3027 gmplsInSegmentGroup OBJECT-GROUP 3028 OBJECTS { 3029 gmplsInSegmentDirection 3030 } 3031 STATUS current 3032 DESCRIPTION 3033 "Collection of objects needed to implement a GMPLS 3034 in-segment." 3035 ::= { gmplsLsrGroups 2 } 3037 gmplsOutSegmentGroup OBJECT-GROUP 3038 OBJECTS { 3039 gmplsOutSegmentDirection, 3040 gmplsOutSegmentTTLDecrement 3041 } 3042 STATUS current 3043 DESCRIPTION 3044 "Collection of objects needed to implement a GMPLS 3045 out-segment." 3046 ::= { gmplsLsrGroups 3 } 3048 END 3050 8. GMPLS Label MIB Definitions 3052 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 3054 IMPORTS 3055 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, 3056 Integer32 3057 FROM SNMPv2-SMI 3058 MODULE-COMPLIANCE, OBJECT-GROUP 3059 FROM SNMPv2-CONF 3060 RowStatus, StorageType 3061 FROM SNMPv2-TC 3063 InterfaceIndexOrZero 3064 FROM IF-MIB 3065 IndexIntegerNextFree 3066 FROM DIFFSERV-MIB 3067 MplsLabel 3068 FROM MPLS-TC-STD-MIB 3069 GmplsGeneralizedLabelTypes, GmplsFreeformLabel, 3070 gmplsStdMIB 3071 FROM GMPLS-TC-STD-MIB 3072 ; 3074 gmplsLabelStdMIB MODULE-IDENTITY 3075 LAST-UPDATED 3076 "200310300900Z" -- 30 October 2003 9:00:00 GMT" 3077 ORGANIZATION 3078 "Common Control And Management Protocols (CCAMP) 3079 Working Group" 3080 CONTACT-INFO 3081 " Thomas D. Nadeau 3082 Cisco Systems, Inc. 3083 Email: tnadeau@cisco.com 3085 Cheenu Srinivasan 3086 Bloomberg L.P. 3087 Email: cheenu@bloomberg.net 3089 Adrian Farrel 3090 Old Dog Consulting 3091 Email: adrian@olddog.co.uk 3093 Ed Harrison 3094 Data Connection Ltd. 3095 Email: ed.harrison@dataconnection.com 3097 Tim Hall 3098 Data Connection Ltd. 3099 Email: timhall@dataconnection.com 3101 Comments about this document should be emailed direct to the 3102 CCAMP working group mailing list at ccamp@ops.ietf.org" 3103 DESCRIPTION 3104 "This MIB module contains managed object definitions 3105 for labels within GMPLS systems." 3107 -- Revision history. 3108 REVISION 3109 "200310300900Z" -- 30 October 2003 09:00:00 GMT 3110 DESCRIPTION 3111 "Initial revision, published as part of RFC XXXX." 3112 ::= { gmplsStdMIB xx } 3114 -- Top level components of this MIB module. 3116 -- Notifications 3117 -- no notifications are currently defined. 3118 gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 } 3119 -- Tables, Scalars 3120 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 3122 -- Conformance 3123 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 3125 -- GMPLS Label Table. 3127 gmplsLabelIndexNext OBJECT-TYPE 3128 SYNTAX IndexIntegerNextFree 3129 MAX-ACCESS read-only 3130 STATUS current 3131 DESCRIPTION 3132 "This object contains an unused value for 3133 gmplsLabelIndex, or a zero to indicate 3134 that no unused value exists or is available. 3136 An management application wishing to create 3137 a row in the gmplsLabelTable may read this 3138 object and then attempt to create a row in 3139 the table. If row creation fails (because 3140 another application has already created a row 3141 with the supplied index) the management 3142 application should read this object again 3143 to get a new index value. 3145 When a row is created in the gmplsLabelTable 3146 with the gmplsLabelIndex value held by this 3147 object, an implementation MUST change the value 3148 in this object. 3149 " 3150 ::= { gmplsLabelObjects 1 } 3152 gmplsLabelTable OBJECT-TYPE 3153 SYNTAX SEQUENCE OF GmplsLabelEntry 3154 MAX-ACCESS not-accessible 3155 STATUS current 3156 DESCRIPTION 3157 "Table of GMPLS Labels. This table allows the 3158 representation of the more complex label forms 3159 required for GMPLS which cannot be held within the 3160 textual convention MplsLabel. That is labels that 3161 cannot be encoded within 32 bits. It is, 3162 nevertheless also capable of holding 32 bit labels 3163 or regular MPLS labels if desired. 3165 Each entry in this table represents an individual 3166 GMPLS label value. Labels in the tables in other 3167 MIBs are referred to using row pointer into this 3168 table. The indexing of this table provides for 3169 arbitrary indexing and also for concatenation of 3170 labels." 3171 ::= { gmplsLabelObjects 2 } 3172 gmplsLabelEntry OBJECT-TYPE 3173 SYNTAX GmplsLabelEntry 3174 MAX-ACCESS not-accessible 3175 STATUS current 3176 DESCRIPTION 3177 "An entry in this table represents a single label 3178 value. There are three indexes into the table. 3179 - The interface index may be helpful to distinguish 3180 which labels are in use on which interfaces or to 3181 handle cases where there are a very large number 3182 of labels in use in the system. When label 3183 representation is desired to apply to the whole 3184 system or when it is not important to distinguish 3185 labels by their interfaces, this index MAY be set 3186 to zero. 3187 - The label index provides a way of identifying the 3188 label. 3189 - The label sub-index is only used for concatenated 3190 labels. It identifies each component label. When 3191 non-concatenated labels are used, this index 3192 SHOULD be set to zero. 3194 A storage type object is supplied to control the 3195 storage type for each entry, but implementations 3196 should note that the storage type of conceptual rows 3197 in other tables that include row pointers to an 3198 entry in this table SHOULD dictate the storage type 3199 of the rows in this table where the row in the other 3200 table is more persistent." 3201 INDEX { 3202 gmplsLabelInterface, 3203 gmplsLabelIndex, 3204 gmplsLabelSubindex } 3205 ::= { gmplsLabelTable 1 } 3207 GmplsLabelEntry ::= SEQUENCE { 3208 gmplsLabelInterface InterfaceIndexOrZero, 3209 gmplsLabelIndex Unsigned32, 3210 gmplsLabelSubindex Unsigned32, 3211 gmplsLabelType GmplsGeneralizedLabelTypes, 3212 gmplsLabelMplsLabel MplsLabel, 3213 gmplsLabelPortWavelength Unsigned32, 3214 gmplsLabelFreeformLength Integer32, 3215 gmplsLabelFreeform GmplsFreeformLabel, 3216 gmplsLabelSonetSdhSignalIndex Integer32, 3217 gmplsLabelSdhVc Integer32, 3218 gmplsLabelSdhVcBranch Integer32, 3219 gmplsLabelSonetSdhBranch Integer32, 3220 gmplsLabelSonetSdhGroupBranch Integer32, 3221 gmplsLabelWavebandId Unsigned32, 3222 gmplsLabelWavebandStart Unsigned32, 3223 gmplsLabelWavebandEnd Unsigned32, 3224 gmplsLabelRowStatus RowStatus, 3225 gmplsLabelStorageType StorageType 3226 } 3227 gmplsLabelInterface OBJECT-TYPE 3228 SYNTAX InterfaceIndexOrZero 3229 MAX-ACCESS not-accessible 3230 STATUS current 3231 DESCRIPTION 3232 "The interface on which this label is used. If the 3233 label has or could have applicability across the 3234 whole system, this object SHOULD be set to zero." 3235 ::= { gmplsLabelEntry 1 } 3237 gmplsLabelIndex OBJECT-TYPE 3238 SYNTAX Unsigned32 (0..4294967295) 3239 MAX-ACCESS not-accessible 3240 STATUS current 3241 DESCRIPTION 3242 "An arbitrary index into the table to identify a 3243 label. 3244 Note that implementations that are representing 32 3245 bit labels within this table MAY choose to align 3246 this index with the value of the label, but should 3247 be aware of the implications of sparsely populated 3248 tables. 3249 A management application may read the gmplsLabelIndexNext 3250 object to find a suitable value for this object." 3251 ::= { gmplsLabelEntry 2 } 3253 gmplsLabelSubindex OBJECT-TYPE 3254 SYNTAX Unsigned32 (0..4294967295) 3255 MAX-ACCESS not-accessible 3256 STATUS current 3257 DESCRIPTION 3258 "In conjunction with gmplsLabelInterface and 3259 gmplsLabelIndex, this object uniquely identifies 3260 this row. This sub-index allows a single GMPLS label 3261 to be defined as a concatenation of labels. This is 3262 particularly useful in TDM. 3263 The ordering of sub-labels is strict with the sub- 3264 label with lowest gmplsLabelSubindex appearing 3265 first. Note that all sub-labels of a single GMPLS 3266 label must share the same gmplsLabelInterface and 3267 gmplsLabelIndex values. For labels that are not 3268 composed of concatenated sub-labels, this value 3269 SHOULD be set to zero." 3270 ::= { gmplsLabelEntry 3 } 3272 gmplsLabelType OBJECT-TYPE 3273 SYNTAX GmplsGeneralizedLabelTypes 3274 MAX-ACCESS read-create 3275 STATUS current 3276 DESCRIPTION 3277 "Identifies the type of this label. Note that this 3278 object does not determine whether MPLS or GMPLS 3279 signaling is in use: a value of gmplsMplsLabel (1) 3280 denotes that a 23 bit MPLS packet label is present, 3281 but does not describe whether this is signaled using 3282 MPLS or GMPLS. 3284 The value of this object helps determine which of 3285 the following objects are valid. 3286 This object cannot be modified if 3287 gmplsLabelRowStatus is active(1)." 3288 ::= { gmplsLabelEntry 4 } 3290 gmplsLabelMplsLabel OBJECT-TYPE 3291 SYNTAX MplsLabel 3292 MAX-ACCESS read-create 3293 STATUS current 3294 DESCRIPTION 3295 "The value of an MPLS label (that is a packet label) 3296 if this table is used to store it. This may be used 3297 in MPLS systems even though the label values can be 3298 adequately stored in the MPLS MIB modules. Further, 3299 in mixed MPLS and GMPLS systems it may be 3300 advantageous to store all labels in a single label 3301 table. Lastly, in GMPLS systems where packet labels 3302 are used (that is in systems that use GMPLS 3303 signaling and GMPLS labels for packet switching) it 3304 may be desirable to use this table. 3305 This object is only valid if gmplsLabelType is set 3306 to gmplsMplsLabel (1). 3307 This object cannot be modified if 3308 gmplsLabelRowStatus is active(1)." 3309 ::= { gmplsLabelEntry 6 } 3311 gmplsLabelPortWavelength OBJECT-TYPE 3312 SYNTAX Unsigned32 3313 MAX-ACCESS read-create 3314 STATUS current 3315 DESCRIPTION 3316 "The value of a Port or Wavelength Label when carried 3317 as a Generalized Label. Only valid if gmplsLabelType 3318 is set to gmplsPortWavelengthLabel(2). 3319 This object cannot be modified if 3320 gmplsLabelRowStatus is active(1)." 3321 ::= { gmplsLabelEntry 7 } 3323 gmplsLabelFreeformLength OBJECT-TYPE 3324 SYNTAX Integer32 (1..64) 3325 MAX-ACCESS read-create 3326 STATUS current 3327 DESCRIPTION 3328 "The length of a freeform Generalized Label indicated 3330 in the gmplsFreeformLabel object. Only valid if 3331 gmplsLabelType is set to 3332 gmplsFreeformGeneralizedLabel(3). 3333 This object cannot be modified if 3334 gmplsLabelRowStatus is active(1)." 3335 ::= { gmplsLabelEntry 8 } 3337 gmplsLabelFreeform OBJECT-TYPE 3338 SYNTAX GmplsFreeformLabel 3339 MAX-ACCESS read-create 3340 STATUS current 3341 DESCRIPTION 3342 "The value of a freeform Generalized Label that does 3343 not conform to one of the standardized label 3344 encoding or that an implementation chooses to 3346 represent as an octet string without further 3347 decoding. The length of this object is given by the 3348 value of gmplsFreeformLength. Only valid if 3349 gmplsLabelType is set to 3350 gmplsFreeformGeneralizedLabel(3). 3351 This object cannot be modified if 3352 gmplsLabelRowStatus is active(1)." 3353 ::= { gmplsLabelEntry 9 } 3355 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 3356 SYNTAX Integer32 (0..4095) 3357 MAX-ACCESS read-create 3358 STATUS current 3359 DESCRIPTION 3360 "The Signal Index value (S) of a SONET or SDH 3361 Generalized Label. Zero indicates that this field is 3362 not significant. Only valid if gmplsLabelType is set 3363 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 3364 This object cannot be modified if 3365 gmplsLabelRowStatus is active(1)." 3366 ::= { gmplsLabelEntry 10 } 3368 gmplsLabelSdhVc OBJECT-TYPE 3369 SYNTAX Integer32 (0..15) 3370 MAX-ACCESS read-create 3371 STATUS current 3372 DESCRIPTION 3373 "The VC Indicator (U) of an SDH Generalized Label. 3374 Zero indicates that this field is non-significant. 3375 Only valid if gmplsLabelType is set to 3376 gmplsSdhLabel(5). 3377 This object cannot be modified if 3378 gmplsLabelRowStatus is active(1)." 3379 ::= { gmplsLabelEntry 11 } 3381 gmplsLabelSdhVcBranch OBJECT-TYPE 3382 SYNTAX Integer32 (0..15) 3383 MAX-ACCESS read-create 3384 STATUS current 3385 DESCRIPTION 3386 "The VC Branch Indicator (K) of an SDH Generalized 3387 Label. Zero indicates that this field is non- 3388 significant. Only valid if gmplsLabelType is set to 3389 gmplsSdhLabel(5). 3390 This object cannot be modified if 3391 gmplsLabelRowStatus is active(1)." 3392 ::= { gmplsLabelEntry 12 } 3394 gmplsLabelSonetSdhBranch OBJECT-TYPE 3395 SYNTAX Integer32 (0..15) 3396 MAX-ACCESS read-create 3397 STATUS current 3398 DESCRIPTION 3399 "The Branch Indicator (L) of a SONET or SDH 3400 Generalized Label. Zero indicates that this field is 3401 non-significant. Only valid gmplsLabelType is set to 3402 gmplsSonetLabel(4) or gmplsSdhLabel(5). 3403 This object cannot be modified if 3404 gmplsLabelRowStatus is active(1)." 3405 ::= { gmplsLabelEntry 13 } 3407 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 3408 SYNTAX Integer32 (0..15) 3409 MAX-ACCESS read-create 3410 STATUS current 3411 DESCRIPTION 3412 "The Group Branch Indicator (M) of a SONET or SDH 3413 Generalized Label. Zero indicates that this field is 3414 non-significant. Only valid if gmplsLabelType is set 3415 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 3416 This object cannot be modified if 3417 gmplsLabelRowStatus is active(1)." 3418 ::= { gmplsLabelEntry 14 } 3420 gmplsLabelWavebandId OBJECT-TYPE 3421 SYNTAX Unsigned32 3422 MAX-ACCESS read-create 3423 STATUS current 3424 DESCRIPTION 3425 "The waveband identifier component of a waveband 3426 label. Only valid if gmplsLabelType is set to 3427 gmplsWavebandLabel(6). 3428 This object cannot be modified if 3429 gmplsLabelRowStatus is active(1)." 3430 ::= { gmplsLabelEntry 15 } 3432 gmplsLabelWavebandStart OBJECT-TYPE 3433 SYNTAX Unsigned32 3434 MAX-ACCESS read-create 3435 STATUS current 3436 DESCRIPTION 3437 "The starting label component of a waveband label. 3438 Only valid if gmplsLabelType is set to 3439 gmplsWavebandLabel(6). 3440 This object cannot be modified if 3441 gmplsLabelRowStatus is active(1)." 3442 ::= { gmplsLabelEntry 16 } 3444 gmplsLabelWavebandEnd OBJECT-TYPE 3445 SYNTAX Unsigned32 3446 MAX-ACCESS read-create 3447 STATUS current 3448 DESCRIPTION 3449 "The end label component of a waveband label. Only 3450 valid if gmplsLabelType is set to 3451 gmplsWavebandLabel(6). 3452 This object cannot be modified if 3453 gmplsLabelRowStatus is active(1)." 3454 ::= { gmplsLabelEntry 17 } 3455 gmplsLabelRowStatus OBJECT-TYPE 3456 SYNTAX RowStatus 3457 MAX-ACCESS read-create 3458 STATUS current 3459 DESCRIPTION 3460 "This variable is used to create, modify, and/or 3461 delete a row in this table. When a row in this 3462 table has a row in the active(1) state, no 3463 objects in this row can be modified except the 3464 gmplsLabelRowStatus and gmplsLabelStorageType." 3465 ::= { gmplsLabelEntry 18 } 3467 gmplsLabelStorageType OBJECT-TYPE 3468 SYNTAX StorageType 3469 MAX-ACCESS read-create 3470 STATUS current 3471 DESCRIPTION 3472 "This variable indicates the storage type for this 3473 object. 3475 The agent MUST ensure that this object's value 3476 remains consistent with the storage type of any rows 3477 in other tables that contain pointers to this row. 3478 In particular, the storage type of this row must be 3479 at least as permanent as that of any row that point 3480 to it. 3482 Conceptual rows having the value 'permanent' need 3483 not allow write-access to any columnar objects in 3484 the row." 3485 REFERENCE 3486 "See RFC2579." 3487 DEFVAL { volatile } 3488 ::= { gmplsLabelEntry 19 } 3490 -- End of GMPLS Label Table 3492 -- Module compliance. 3494 gmplsLabelGroups 3495 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 3497 gmplsLabelCompliances 3498 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 3500 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 3501 STATUS current 3502 DESCRIPTION 3503 "Compliance statement for agents that support 3504 the GMPLS Label MIB module." 3506 MODULE -- this module 3508 -- The mandatory groups have to be implemented by 3509 -- LSRs claiming support for this MIB module. This MIB module is, 3510 -- however, not mandatory for a working implementation of a GMPLS 3511 -- LSR with full MIB support if the GMPLS labels in use can be 3512 -- represented within a 32 bit quantity. 3514 MANDATORY-GROUPS { 3515 gmplsLabelTableGroup 3516 } 3518 -- Units of conformance. 3520 GROUP gmplsLabelTableGroup 3521 DESCRIPTION 3522 "This group is mandatory for devices which support 3523 the gmplsLabelTable." 3525 GROUP gmplsLabelPacketGroup 3526 DESCRIPTION 3527 "This group extends gmplsLabelTableGroup for 3528 implementations that support packet labels." 3530 GROUP gmplsLabelPortWavelengthGroup 3531 DESCRIPTION 3532 "This group extends gmplsLabelTableGroup for 3533 implementations that support port and wavelength 3534 labels." 3536 GROUP gmplsLabelFreeformGroup 3537 DESCRIPTION 3538 "This group extends gmplsLabelTableGroup for 3539 implementations that support freeform labels." 3541 GROUP gmplsLabelSonetSdhGroup 3542 DESCRIPTION 3543 "This group extends gmplsLabelTableGroup for 3544 implementations that support SONET or SDH labels." 3546 GROUP gmplsLabelWavebandGroup 3547 DESCRIPTION 3548 "This group extends gmplsLabelTableGroup for 3549 implementations that support Waveband labels." 3551 -- gmplsLabelTable 3553 OBJECT gmplsLabelType 3554 MIN-ACCESS read-only 3555 DESCRIPTION 3556 "Write access is not required." 3558 OBJECT gmplsLabelMplsLabel 3559 MIN-ACCESS read-only 3560 DESCRIPTION 3561 "Write access is not required." 3563 OBJECT gmplsLabelPortWavelength 3564 MIN-ACCESS read-only 3565 DESCRIPTION 3566 "Write access is not required." 3568 OBJECT gmplsLabelFreeformLength 3569 MIN-ACCESS read-only 3570 DESCRIPTION 3571 "Write access is not required." 3573 OBJECT gmplsLabelFreeform 3574 MIN-ACCESS read-only 3575 DESCRIPTION 3576 "Write access is not required." 3578 OBJECT gmplsLabelSonetSdhSignalIndex 3579 MIN-ACCESS read-only 3580 DESCRIPTION 3581 "Write access is not required." 3583 OBJECT gmplsLabelSdhVc 3584 MIN-ACCESS read-only 3585 DESCRIPTION 3586 "Write access is not required." 3588 OBJECT gmplsLabelSdhVcBranch 3589 MIN-ACCESS read-only 3590 DESCRIPTION 3591 "Write access is not required." 3593 OBJECT gmplsLabelSonetSdhBranch 3594 MIN-ACCESS read-only 3595 DESCRIPTION 3596 "Write access is not required." 3598 OBJECT gmplsLabelSonetSdhGroupBranch 3599 MIN-ACCESS read-only 3600 DESCRIPTION 3601 "Write access is not required." 3603 OBJECT gmplsLabelWavebandId 3604 MIN-ACCESS read-only 3605 DESCRIPTION 3606 "Write access is not required." 3608 OBJECT gmplsLabelWavebandStart 3609 MIN-ACCESS read-only 3610 DESCRIPTION 3611 "Write access is not required." 3613 OBJECT gmplsLabelWavebandEnd 3614 MIN-ACCESS read-only 3615 DESCRIPTION 3616 "Write access is not required." 3618 OBJECT gmplsLabelRowStatus 3619 SYNTAX RowStatus { 3620 active(1), 3621 notInService(2) 3622 } 3623 WRITE-SYNTAX RowStatus { 3624 active(1), 3625 notInService(2), 3626 createAndGo(4), 3627 destroy(6) 3628 } 3629 DESCRIPTION 3630 "Support for notInService, createAndWait and notReady 3631 is not required." 3633 OBJECT gmplsLabelStorageType 3634 MIN-ACCESS read-only 3635 DESCRIPTION 3636 "Write access is not required." 3638 ::= { gmplsLabelCompliances 1 } 3640 -- Units of conformance. 3642 gmplsLabelTableGroup OBJECT-GROUP 3643 OBJECTS { 3644 gmplsLabelIndexNext, 3645 gmplsLabelType, 3646 gmplsLabelRowStatus, 3647 gmplsLabelStorageType 3648 } 3649 STATUS current 3650 DESCRIPTION 3651 "Necessary, but not sufficient, set of objects to 3652 implement label table support. In addition, 3653 depending on the type of labels supported (for 3654 example, wavelength labels), the following other 3655 groups defined below are mandatory: 3656 gmplsLabelPacketGroup and/or 3657 gmplsLabelPortWavelengthGroup and/or 3658 gmplsLabelFreeformGroup and/or 3659 gmplsLabelSonetSdhGroup." 3660 ::= { gmplsLabelGroups 1 } 3662 gmplsLabelPacketGroup OBJECT-GROUP 3663 OBJECTS { 3664 gmplsLabelMplsLabel 3665 } 3666 STATUS current 3667 DESCRIPTION 3668 "Object needed to implement Packet (MPLS) labels." 3669 ::= { gmplsLabelGroups 2 } 3670 gmplsLabelPortWavelengthGroup OBJECT-GROUP 3671 OBJECTS { 3672 gmplsLabelPortWavelength 3673 } 3674 STATUS current 3675 DESCRIPTION 3676 "Object needed to implement Port and Wavelength 3677 labels." 3678 ::= { gmplsLabelGroups 3 } 3680 gmplsLabelFreeformGroup OBJECT-GROUP 3681 OBJECTS { 3682 gmplsLabelFreeformLength, 3683 gmplsLabelFreeform 3684 } 3685 STATUS current 3686 DESCRIPTION 3687 "Object needed to implement Freeform labels." 3688 ::= { gmplsLabelGroups 4 } 3690 gmplsLabelSonetSdhGroup OBJECT-GROUP 3691 OBJECTS { 3692 gmplsLabelSonetSdhSignalIndex, 3693 gmplsLabelSdhVc, 3694 gmplsLabelSdhVcBranch, 3695 gmplsLabelSonetSdhBranch, 3696 gmplsLabelSonetSdhGroupBranch 3697 } 3698 STATUS current 3699 DESCRIPTION 3700 "Object needed to implement SONET and SDH labels." 3701 ::= { gmplsLabelGroups 5 } 3703 gmplsLabelWavebandGroup OBJECT-GROUP 3704 OBJECTS { 3705 gmplsLabelWavebandId, 3706 gmplsLabelWavebandStart, 3707 gmplsLabelWavebandEnd 3708 } 3709 STATUS current 3710 DESCRIPTION 3711 "Object needed to implement Waveband labels." 3712 ::= { gmplsLabelGroups 6 } 3714 END 3716 9. Security Considerations 3718 It is clear that the MIB modules described in this document in 3719 association with the MPLS-LSR-STD-MIB are potentially useful for 3720 monitoring of GMPLS LSRs. These MIB modules can also be used for 3721 configuration of certain objects, and anything that can be configured 3722 can be incorrectly configured, with potentially disastrous results. 3724 There are a number of management objects defined in these MIB modules 3725 with a MAX-ACCESS clause of read-write and/or read-create. Such 3726 objects may be considered sensitive or vulnerable in some network 3727 environments. The support for SET operations in a non-secure 3728 environment without proper protection can have a negative effect on 3729 network operations. These are the tables and objects and their 3730 sensitivity/vulnerability: 3732 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 3733 and gmplsLabelTable collectively contain objects to provision 3734 GMPLS interfaces, LSPs and their associated parameters on a Label 3735 Switching Router (LSR). Unauthorized write access to objects in 3736 these tables, could result in disruption of traffic on the 3737 network. This is especially true if an LSP has already been 3738 established. The use of stronger mechanisms such as SNMPv3 3739 security should be considered where possible. Specifically, SNMPv3 3740 VACM and USM MUST be used with any SNMPv3 agent which implements 3741 these MIB modules. 3743 Some of the readable objects in these MIB modules "i.e., objects with 3744 a MAX-ACCESS other than not-accessible" may be considered sensitive 3745 or vulnerable in some network environments. It is thus important to 3746 control even GET and/or NOTIFY access to these objects and possibly 3747 to even encrypt the values of these objects when sending them over 3748 the network via SNMP. These are the tables and objects and their 3749 sensitivity/vulnerability: 3751 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 3752 and gmplsLabelTable collectively show the LSP network topology and 3753 its capabilities. If an Administrator does not want to reveal this 3754 information, then these tables should be considered 3755 sensitive/vulnerable. 3757 SNMP versions prior to SNMPv3 did not include adequate security. Even 3758 if the network itself is secure "for example by using IPSec", even 3759 then, there is no control as to who on the secure network is allowed 3760 to access and GET/SET "read/change/create/delete" the objects in 3761 these MIB modules. It is RECOMMENDED that implementers consider the 3762 security features as provided by the SNMPv3 framework "see [RFC3410], 3763 section 8", including full support for the SNMPv3 cryptographic 3764 mechanisms "for authentication and privacy". 3766 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3767 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3768 enable cryptographic security. It is then a customer/operator 3769 responsibility to ensure that the SNMP entity giving access to an 3770 instance of this MIB module, is properly configured to give access to 3771 the objects only to those principals "users" that have legitimate 3772 rights to indeed GET or SET "change/create/delete" them. 3774 10. Acknowledgments 3776 This draft extends [LSRMIB]. The authors would like to express their 3777 gratitude to all those who worked on that earlier MIB document. 3779 The authors would like to express their thanks to Dan Joyle for his 3780 careful review and comments on early versions of the Label Table. 3781 Special thanks to Joan Cucchiara and Len Nieman for their help with 3782 compilation issues. 3784 11. IANA Considerations 3786 MPLS related standards track MIB modules are rooted under the 3787 mplsStdMIB subtree. 3789 One of the MIB modules contained in this document extends tables 3790 contained in MPLS MIB modules. 3792 As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the 3793 two MIB modules contained in this document should be placed in the 3794 mplsStdMIB subtree as well. 3796 New assignments can only be made via a Standards Action as specified 3797 in [RFC2434]. 3799 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 3801 The IANA is requested to assign { mplsStdMIB xx } to the 3802 GMPLS-LSR-STD-MIB module specified in this document. 3804 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 3806 The IANA is requested to assign { mplsStdMIB xx } to the 3807 GMPLS-LABEL-STD-MIB module specified in this document. 3809 12. References 3811 12.1. Normative References 3813 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3814 Requirement Levels", BCP 14, RFC 2119, March 1997. 3816 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 3817 Case, J., Rose, M., and S. Waldbusser, "Structure 3818 of Management Information Version 2 (SMIv2)", STD 3819 58, RFC 2578, April 1999. 3821 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 3822 Case, J., Rose, M., and S. Waldbusser, "Textual 3823 Conventions for SMIv2", STD 58, RFC 2579, April 3824 1999. 3826 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 3827 Case, J., Rose, M., and S. Waldbusser, "Conformance 3828 Statements for SMIv2", STD 58, RFC 2580, April 3829 1999. 3831 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces 3832 Group MIB", RFC 2863, June 2000. 3834 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 3835 Label Switching (GMPLS) Architecture", Internet 3836 Draft , May 3837 2003, work in progress. 3839 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 3840 "Generalized Multi-Protocol Label Switching 3841 Extensions for SONET and SDH Control", Internet 3842 Draft , 3843 February 2003, work in progress. 3845 [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 3846 and Harrison, E., "Definitions of Textual 3847 Conventions for Multiprotocol Label Switching 3848 (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib- 3849 03.txt, November 2003, work in progress. 3851 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 3852 and Harrison, E., "Generalized Multiprotocol Label 3853 Switching (GMPLS) Traffic Engineering Management 3854 Information Base", draft-ietf-ccamp-gmpls-te-mib- 3855 03.txt, November 2003, work in progress. 3857 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of 3858 Textual Conventions for Multiprotocol Label 3859 Switching (MPLS) Management", Internet Draft 3860 , August 2003, work 3861 in progress. 3863 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, 3864 "Multiprotocol Label Switching (MPLS) Label 3865 Switching Router (LSR) Management Information 3866 Base", Internet Draft , August 2003, work in progress. 3869 12.2. Informational References 3871 [RFC2026] S. Bradner, "The Internet Standards Process -- 3872 Revision 3", RFC 2026, October 1996. 3874 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 3875 Writing an IANA Considerations Section in RFCs", 3876 BCP: 26, RFC 2434, October 1998. 3878 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 3879 "Multiprotocol Label Switching Architecture", RFC 3880 3031, January 2001. 3882 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 3883 Srinivasan, V., and G. Swallow, "RSVP-TE: 3884 Extensions to RSVP for LSP Tunnels", RFC 3209, 3885 December 2001. 3887 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 3888 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 3889 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 3890 T., Feldman, N., Fredette, A., Girish, M., Gray, 3891 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 3892 A., and P. Vaananen, "Constraint-Based LSP Setup 3893 using LDP", RFC 3212, December 2001." 3895 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3896 "Introduction and Applicability Statements for 3897 Internet-Standard Management Framework", RFC 3410, 3898 December 2002. 3900 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3901 Architecture for Describing Simple Network 3902 Management Protocol (SNMP) Management Frameworks", 3903 RFC 3411, December 2002. 3905 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 3906 Applications", RFC 3413, December 2002. 3908 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 3909 Label Switching (GMPLS) Signaling Functional 3910 Description", RFC 3471, January 2003. 3912 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 3913 "Generalized MPLS Signaling - CR-LDP Extensions", 3914 RFC 3472, January 2003. 3916 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 3917 RSVP-TE Extensions", RFC 3473 January 2003. 3919 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 3920 "Multiprotocol Label Switching (MPLS) Traffic 3921 Engineering Management Information Base", Internet 3922 Draft , August 2003, 3923 work in progress. 3925 13. Authors' Addresses 3927 Thomas D. Nadeau 3928 Cisco Systems, Inc. 3929 300 Apollo Drive 3930 Chelmsford, MA 01824 3931 Phone: +1-978-244-3051 3932 Email: tnadeau@cisco.com 3934 Cheenu Srinivasan 3935 Bloomberg L.P. 3936 499 Park Ave., 3937 New York, NY 10022 3938 Phone: +1-212-893-3682 3939 Email: cheenu@bloomberg.net 3941 Adrian Farrel 3942 Old Dog Consulting 3943 Phone: +44-(0)-1978-860944 3944 Email: adrian@olddog.co.uk 3946 Tim Hall 3947 Data Connection Ltd. 3948 100 Church Street 3949 Enfield, Middlesex, EN2 6BQ, UK 3950 Phone: +44 20 8366 1177 3951 Email: timhall@dataconnection.com 3952 Ed Harrison 3953 Data Connection Ltd. 3954 100 Church Street 3955 Enfield, Middlesex, EN2 6BQ, UK 3956 Phone: +44 20 8366 1177 3957 Email: ed.harrison@dataconnection.com 3959 14. Full Copyright Statement 3961 Copyright (C) The Internet Society (2003). All Rights Reserved. 3963 This document and translations of it may be copied and furnished to 3964 others, and derivative works that comment on or otherwise explain it 3965 or assist in its implementation may be prepared, copied, published 3966 and distributed, in whole or in part, without restriction of any 3967 kind, provided that the above copyright notice and this paragraph 3968 are included on all such copies and derivative works. However, this 3969 document itself may not be modified in any way, such as by removing 3970 the copyright notice or references to the Internet Society or other 3971 Internet organizations, except as needed for the purpose of 3972 developing Internet standards in which case the procedures for 3973 copyrights defined in the Internet Standards process must be 3974 followed, or as required to translate it into languages other than 3975 English. 3977 The limited permissions granted above are perpetual and will not be 3978 revoked by the Internet Society or its successors or assigns. This 3979 document and the information contained herein is provided on an "AS 3980 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 3981 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3982 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 3983 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3984 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3986 15. Intellectual Property Notice 3988 The IETF takes no position regarding the validity or scope of any 3989 intellectual property or other rights that might be claimed to 3990 pertain to the implementation or use of the technology described in 3991 this document or the extent to which any license under such rights 3992 might or might not be available; neither does it represent that it 3993 has made any effort to identify any such rights. Information on the 3994 IETF's procedures with respect to rights in standards-track and 3995 standards-related documentation can be found in BCP-11 [RFC2028]. 3997 Copies of claims of rights made available for publication and any 3998 assurances of licenses to be made available, or the result of an 3999 attempt made to obtain a general license or permission for the use 4000 of such proprietary rights by implementers or users of this 4001 specification can be obtained from the IETF Secretariat. 4003 The IETF invites any interested party to bring to its attention any 4004 copyrights, patents or patent applications, or other proprietary 4005 rights that may cover technology that may be required to practice 4006 this standard. Please address the information to the IETF Executive 4007 Director. 4009 16. Changes and Pending Work 4011 This section must be removed before the draft progresses to RFC. 4013 16.1. Pending Work 4015 The following work items have been identified for this draft. They 4016 will be addressed in a future version. 4018 - Expand conformance statements to give one for monitoring only, 4019 and one for monitoring and control. 4020 - Provide support for monitoring tunnel resources in GMPLS systems. 4021 For example, SONET/SDH or G.709. This might be done through an 4022 arbitrary RowPointer to an external MIB. 4023 - Extend the performance tables from the MPLS-LSR-MIB for 4024 technology-specific GMPLS LSPs. 4025 - Determine whether the 'discriminated union' in the Label Table is 4026 good MIB. 4028 16.1. Changes from version 2 to version 3 4030 - Work on basic compilation issues. 4031 - Provide a next index object to supply the next available 4032 arbitrary index into the Label Table. 4033 - Update references. 4034 - Update examples. 4036 Network Working Group Thomas D. Nadeau 4037 Internet Draft Cisco Systems, Inc. 4038 Expires: May 2004 4039 Cheenu Srinivasan 4040 Bloomberg L.P. 4042 Adrian Farrel 4043 Old Dog Consulting 4045 Tim Hall 4046 Ed Harrison 4047 Data Connection Ltd. 4049 November 2003 4051 Definitions of Textual Conventions for Generalized Multi-Protocol 4052 Label Switching (GMPLS) Management 4054 draft-ietf-ccamp-gmpls-tc-mib-03.txt 4056 Status of this Memo 4058 This document is an Internet-Draft and is in full conformance with 4059 all provisions of Section 10 of RFC 2026. 4061 Internet-Drafts are working documents of the Internet Engineering 4062 Task Force (IETF), its areas, and its working groups. Note that 4063 other groups may also distribute working documents as Internet- 4064 Drafts. 4066 Internet-Drafts are draft documents valid for a maximum of six months 4067 and may be updated, replaced, or obsoleted by other documents at any 4068 time. It is inappropriate to use Internet-Drafts as reference 4069 material or to cite them other than as "work in progress." 4071 The list of current Internet-Drafts can be accessed at 4072 http://www.ietf.org/ietf/1id-abstracts.txt. 4074 Abstract 4076 This document defines a Management Information Base (MIB) module 4077 which contains Textual Conventions to represent commonly used 4078 Generalized Multi-Protocol Label Switching (GMPLS) management 4079 information. The intent is that these TEXTUAL CONVENTIONS (TCs) will 4080 be imported and used in GMPLS related MIB modules that would 4081 otherwise define their own representations. 4083 Table of Contents 4085 1. Introduction 2 4086 2. The SNMP Management Framework 2 4087 3. GMPLS Textual Conventions MIB Definitions 3 4088 4. Security Considerations 5 4089 5. IANA Considerations 5 4090 6. References 5 4091 6.1. Normative References 5 4092 6.2. Informational References 6 4093 7. Authors' Addresses 7 4094 8. Full Copyright Statement 7 4095 9. Intellectual Property Notice 8 4097 1. Introduction 4099 This document defines a MIB module which contains Textual Conventions 4100 for Generalized Multi-Protocol Label Switching (GMPLS) networks. 4101 These Textual Conventions should be imported by MIB modules which 4102 manage GMPLS networks. 4104 This MIB module supplements the MIB module in [TCMIB] that defines 4105 Textual Conventions for Multiprotocol Label Switching (MPLS) 4106 Management. [TCMIB] may continue to be used without this MIB module 4107 in networks that support only MPLS. 4109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 4110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 4111 document are to be interpreted as described in RFC 2119 [RFC2119]. 4113 Comments should be made directly to the CCAMP mailing list at 4114 ccamp@ops.ietf.org. 4116 For an introduction to the concepts of GMPLS, see [GMPLSArch]. 4118 2. The SNMP Management Framework 4120 For a detailed overview of the documents that describe the current 4121 Internet-Standard Management Framework, please refer to section 7 of 4122 RFC 3410 [RFC3410]. 4124 Managed objects are accessed via a virtual information store, termed 4125 the Management Information Base or MIB. MIB objects are generally 4126 accessed through the Simple Network Management Protocol (SNMP). 4127 Objects in the MIB are defined using the mechanisms defined in the 4128 Structure of Management Information (SMI). This memo specifies a MIB 4129 module that is compliant to the SMIv2, which is described in STD 58, 4130 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 4131 [RFC2580]. 4133 3. GMPLS Textual Conventions MIB Definitions 4135 GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN 4137 IMPORTS 4138 MODULE-IDENTITY 4139 FROM SNMPv2-SMI 4140 transmission 4141 FROM SNMPv2-SMI 4142 TEXTUAL-CONVENTION 4143 FROM SNMPv2-TC 4144 ; 4146 gmplsTCStdMIB MODULE-IDENTITY 4147 LAST-UPDATED 4148 "200310300900Z" -- 30 October 2003 9:00:00 GMT" 4149 ORGANIZATION "Common Control And Management Protocols (CCAMP) 4150 Working Group" 4151 CONTACT-INFO 4152 " Thomas D. Nadeau 4153 Cisco Systems, Inc. 4154 Email: tnadeau@cisco.com 4156 Cheenu Srinivasan 4157 Bloomberg L.P. 4158 Email: cheenu@bloomberg.net 4160 Adrian Farrel 4161 Old Dog Consulting 4162 Email: adrian@olddog.co.uk 4164 Ed Harrison 4165 Data Connection Ltd. 4166 Email: ed.harrison@dataconnection.com 4168 Tim Hall 4169 Data Connection Ltd. 4170 Email: timhall@dataconnection.com 4172 Comments about this document should be emailed direct to the 4173 CCAMP working group mailing list at ccamp@ops.ietf.org" 4174 DESCRIPTION 4175 "Copyright (C) The Internet Society (2003). This version of this 4176 MIB module is part of RFCXXX; see the RFC itself for full legal 4177 notices. 4179 This MIB module defines Textual Conventions for concepts used in 4180 Generalized Multi-Protocol Label Switching (GMPLS) networks." 4182 -- Revision history. 4183 REVISION 4184 "200310300900Z" -- 30 October 2003 09:00:00 GMT 4185 DESCRIPTION 4186 "Initial version published as part of RFC XXXX." 4187 -- Please see the IANA Considerations Section. 4188 -- The requested gmplsStdMIB subId is xx, i.e. 4189 ::= { gmplsStdMIB xx } 4190 gmplsStdMIB OBJECT IDENTIFIER 4191 -- This object identifier needs to be assigned by IANA. 4192 -- Since mpls has been assigned an ifType of 166 we recommend 4193 -- that this OID be 166 as well, i.e. 4194 ::= { transmission XXX } 4196 -- Textual Conventions (sorted alphabetically). 4198 GmplsFreeformLabel ::= TEXTUAL-CONVENTION 4199 STATUS current 4200 DESCRIPTION 4201 "This value represents a freeform generalized MPLS Label. This 4202 can be used to represent label types which are not standard 4203 in the drafts. It may also be used by systems that do not 4204 wish to represent the labels using the specific label types." 4205 SYNTAX OCTET STRING (SIZE (0..64)) 4207 GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION 4208 STATUS current 4209 DESCRIPTION 4210 "Determines the interpretation that should be applied to a 4211 label." 4212 SYNTAX INTEGER { 4213 gmplsMplsLabel(1), 4214 gmplsPortWavelengthLabel(2), 4215 gmplsFreeformGeneralizedLabel(3), 4216 gmplsSonetLabel(4), 4217 gmplsSdhLabel(5), 4218 gmplsWavebandLabel(6) 4219 } 4221 GmplsSegmentDirection ::= TEXTUAL-CONVENTION 4222 STATUS current 4223 DESCRIPTION 4224 "The direction of data flow on an LSP segment with respect to the 4225 head of the LSP. 4227 Where an LSP is signaled using a conventional signaling 4228 protocol, the 'head' of the LSP is the source of the signaling 4229 (also known as the ingress) and the 'tail' is the destination 4230 (also known as the egress). 4232 For manually configured LSPs an arbitrary decision must be made 4233 about which LER is the 'head'." 4234 SYNTAX INTEGER { 4235 forward(1), 4236 reverse(2) 4237 } 4239 END 4241 4. Security Considerations 4243 This module does not define any management objects. Instead, it 4244 defines a set of textual conventions which may be used by other GMPLS 4245 MIB modules to define management objects. 4247 Meaningful security considerations can only be written in the MIB 4248 modules that define management objects. Therefore, this document has 4249 no impact on the security of the Internet. 4251 5. IANA Considerations 4253 IANA is requested to make a MIB OID assignment under the transmission 4254 branch, that is, assign the gmplsStdMIB under { transmission 166 }. 4256 This sub-id is requested because 166 is the ifType for mpls(166) and 4257 is available under transmission. 4259 In the future, GMPLS related standards track MIB modules should be 4260 rooted under the mplsStdMIB (sic) subtree. IANA is requested to 4261 manage that namespace. New assignments can only be made via a 4262 Standards Action as specified in [RFC2434]. 4264 This document also requests IANA to assign { gmplsStdMIB xx } to the 4265 GMPLS-TC-STD-MIB specified in this document. 4267 6. References 4269 6.1. Normative References 4271 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 4272 Requirement Levels", BCP 14, RFC 2119, March 1997. 4274 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 4275 Case, J., Rose, M. and S. Waldbusser, "Structure of 4276 Management Information Version 2 (SMIv2)", STD 58, 4277 RFC 2578, April 1999. 4279 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 4280 Case, J., Rose, M. and S. Waldbusser, "Textual 4281 Conventions for SMIv2", STD 58, RFC 2579, April 4282 1999. 4284 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 4285 Case, J., Rose, M. and S. Waldbusser, "Conformance 4286 Statements for SMIv2", STD 58, RFC 2580, April 1999. 4288 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 4289 Label Switching (GMPLS) Signaling Functional 4290 Description", RFC 3471, January 2003. 4292 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 4293 Label Switching (GMPLS) Architecture", Internet 4294 Draft , May 4295 2003, work in progress. 4297 6.2. Informational References 4299 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 4300 Writing an IANA Considerations Section in RFCs", 4301 BCP: 26, RFC 2434, October 1998. 4303 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, 4304 Multiprotocol Label Switching Architecture", 4305 RFC 3031, January 2001. 4307 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 4308 Srinivasan, V., Swallow, G., "RSVP-TE: Extensions to 4309 RSVP for LSP Tunnels", RFC 3209, December 2001. 4311 [RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based 4312 LSP Setup using LDP", RFC 3212, January 2002. 4314 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 4315 "Introduction and Applicability Statements for 4316 Internet-Standard Management Framework", RFC 3410, 4317 December 2002. 4319 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 4320 "Generalized MPLS Signaling - CR-LDP Extensions", 4321 RFC 3472, January 2003. 4323 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 4324 RSVP-TE Extensions", RFC 3473 January 2003. 4326 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 4327 "Generalized Multi-Protocol Label Switching 4328 Extensions for SONET and SDH Control", Internet 4329 Draft , 4330 February 2003, work in progress. 4332 [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 4333 and Harrison, E., " Generalized Multiprotocol Label 4334 Switching (GMPLS) Label Switching Router (LSR) 4335 Management Information Base", draft-ietf-ccamp- 4336 gmpls-lsr-mib-03.txt, November 2003, work in 4337 progress. 4339 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 4340 and Harrison, E., "Generalized Multiprotocol Label 4341 Switching (GMPLS) Traffic Engineering Management 4342 Information Base", draft-ietf-ccamp-gmpls-te-mib- 4343 03.txt, November 2003, work in progress. 4345 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions 4346 of Textual Conventions for Multiprotocol Label 4347 Switching (MPLS) Management", Internet Draft 4348 , August 2003, 4349 work in progress. 4351 7. Acknowledgements 4353 Special thanks to Joan Cucchiara for her help with compilation 4354 issues. 4356 8. Authors' Addresses 4358 Thomas D. Nadeau 4359 Cisco Systems, Inc. 4360 300 Apollo Drive 4361 Chelmsford, MA 01824 4362 Phone: +1-978-244-3051 4363 Email: tnadeau@cisco.com 4365 Cheenu Srinivasan 4366 Bloomberg L.P. 4367 499 Park Ave., 4368 New York, NY 10022 4369 Phone: +1-212-893-3682 4370 Email: cheenu@bloomberg.net 4372 Adrian Farrel 4373 Old Dog Consulting 4374 Phone: +44-(0)-1978-860944 4375 Email: adrian@olddog.co.uk 4377 Tim Hall 4378 Data Connection Ltd. 4379 100 Church Street 4380 Enfield, Middlesex 4381 EN2 6BQ, UK 4382 Phone: +44 20 8366 1177 4383 Email: timhall@dataconnection.com 4385 Ed Harrison 4386 Data Connection Ltd. 4387 100 Church Street 4388 Enfield, Middlesex 4389 EN2 6BQ, UK 4390 Phone: +44 20 8366 1177 4391 Email: ed.harrison@dataconnection.com 4393 9. Full Copyright Statement 4395 Copyright (C) The Internet Society (2003). All Rights Reserved. 4397 This document and translations of it may be copied and furnished 4398 to others, and derivative works that comment on or otherwise explain 4399 it or assist in its implementation may be prepared, copied, published 4400 and distributed, in whole or in part, without restriction of any 4401 kind, provided that the above copyright notice and this paragraph are 4402 included on all such copies and derivative works. However, this 4403 document itself may not be modified in any way, such as by removing 4404 the copyright notice or references to the Internet Society or other 4405 Internet organizations, except as needed for the purpose of 4406 developing Internet standards in which case the procedures for 4407 copyrights defined in the Internet Standards process must be 4408 followed, or as required to translate it into languages other than 4409 English. 4411 The limited permissions granted above are perpetual and will not be 4412 revoked by the Internet Society or its successors or assigns. This 4413 document and the information contained herein is provided on an "AS 4414 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 4415 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 4416 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 4417 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 4418 OR FITNESS FOR A PARTICULAR PURPOSE. 4420 10. Intellectual Property Notice 4422 The IETF takes no position regarding the validity or scope of any 4423 intellectual property or other rights that might be claimed to 4424 pertain to the implementation or use of the technology described in 4425 this document or the extent to which any license under such rights 4426 might or might not be available; neither does it represent that it 4427 has made any effort to identify any such rights. Information on the 4428 IETF's procedures with respect to rights in standards-track and 4429 standards-related documentation can be found in BCP-11 [RFC2028]. 4431 Copies of claims of rights made available for publication and any 4432 assurances of licenses to be made available, or the result of an 4433 attempt made to obtain a general license or permission for the use of 4434 such proprietary rights by implementers or users of this 4435 specification can be obtained from the IETF Secretariat. 4437 The IETF invites any interested party to bring to its attention any 4438 copyrights, patents or patent applications, or other proprietary 4439 rights that may cover technology that may be required to practice 4440 this standard. Please address the information to the IETF Executive 4441 Director.