idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-14.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2065. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2038. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2045. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2051. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. 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 (April 2006) is 6586 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RCF3813' is mentioned on line 268, but not defined == Missing Reference: 'RFC2434' is mentioned on line 1867, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC3032' is defined on line 1915, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1919, but no explicit reference was found in the text == Unused Reference: 'RFC3443' is defined on line 1927, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 1937, but no explicit reference was found in the text == Unused Reference: 'RFC3946' is defined on line 1954, but no explicit reference was found in the text == Unused Reference: 'RFC3468' is defined on line 1977, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 1981, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3946 (Obsoleted by RFC 4606) Summary: 5 errors (**), 0 flaws (~~), 12 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau, Ed. 2 Internet Draft Cisco Systems, Inc. 3 Proposed Status: Standards Track 4 Expires: September 2006 Adrian Farrel, Ed. 5 Old Dog Consulting 7 April 2006 9 Generalized Multiprotocol Label Switching (GMPLS) 10 Label Switching Router (LSR) Management Information Base 12 draft-ietf-ccamp-gmpls-lsr-mib-14.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other documents 28 at any time. It is inappropriate to use Internet-Drafts as 29 reference material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects to configure and/or 42 monitor a Generalized Multiprotocol Label Switching (GMPLS) Label 43 Switching Router (LSR). 45 Table of Contents 47 1. Introduction ..................................... 2 48 1.1. Migration Strategy ............................. 3 49 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 51 2. Terminology ...................................... 3 52 3. The Internet-Standard Management Framework ....... 4 53 4. Outline .......................................... 5 54 4.1 MIB Modules ..................................... 5 55 4.1.1 Summary of the GMPLS-LSR-STD-MIB Module ....... 5 56 4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module ..... 5 57 4.2. Configuring Statically Provisioned LSPs ........ 6 58 5. Bidirectional LSPs ............................... 6 59 6. Example of LSP Setup ............................. 7 60 7. GMPLS Label Switching Router MIB Definitions .... 11 61 8. GMPLS Label MIB Definitions ..................... 22 62 9. Security Considerations ......................... 37 63 10. Acknowledgments ................................ 38 64 11. IANA Considerations ............................ 38 65 11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 38 66 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB .. 39 67 12. References ..................................... 39 68 12.1. Normative References ......................... 39 69 12.2. Informative References ....................... 40 70 13. Contact Information ............................ 41 71 14. Intellectual Property Considerations ........... 42 72 15. Full Copyright Statement ....................... 42 74 1. Introduction 76 This memo defines a portion of the Management Information Base (MIB) 77 for use with network management protocols in the Internet community. 78 In particular, it describes managed objects for modeling a 79 Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] Label 80 Switching Router (LSR). 82 Comments should be made directly to the CCAMP mailing list at 83 ccamp@ops.ietf.org. 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in BCP 14, RFC 2119, 88 reference [RFC2119]. 90 1.1. Migration Strategy 92 MPLS LSRs may be modeled and managed using the MPLS-LSR-STD-MIB 93 module [RFC3813]. 95 LSRs may be migrated to be modeled and managed using the MIB modules 96 in this document in order to migrate the LSRs to GMPLS support, or to 97 take advandtage of additional MIB objects defined in these MIB 98 modules that are applicable to MPLS-TE. 100 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 102 The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB) defined in this document 103 extends the MPLS-LSR-STD-MIB module [RFC3813] through a series of 104 sparse augmentations of the MIB tables. The only additions are for 105 support of GMPLS or to support the increased complexity of MPLS and 106 GMPLS systems. 108 In order to migrate from MPLS-LSR-STD-MIB support to 109 GMPLS-LSR-STD-MIB support an implementation needs only to add support 110 for the additional tables and objects defined in GMPLS-LSR-STD-MIB. 111 The gmplsInterfaceSignalingCaps object allows an implementation to 112 use the objects and tables of GMPLS-LSR-STD-MIB without supporting 113 the GMPLS protocols. 115 The GMPLS Label MIB module (GMPLS-LABEL-STD-MIB) also defined in this 116 document allows labels to be configured and examined, and supports 117 more varieties of label as appropriate for GMPLS. Labels may be 118 referenced using a row pointer from objects within the 119 GMPLS-LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may 120 also reference labels held in the GMPLS-LABEL-STD-MIB module through 121 the various label pointer objects in the MPLS-LSR-STD-MIB module 122 (such as mplsInSegmentLabelPtr), and may do so without implementing 123 the GMPLS-LSR-STD-MIB module. 125 The companion document modeling and managing GMPLS based traffic 126 engineering [GMPLSTEMIB] extends the MPLS-TE-STD-MIB module [RFC3812] 127 with the same intentions. 129 Textual conventions are defined in [GMPLSTCMIB] which extends the 130 set of textual conventions originally defined in [RFC3811]. 132 2. Terminology 134 This document uses terminology from the document describing the MPLS 135 architecture [RFC3031] and the GMPLS architecture [RFC3945]. 137 A label switched path (LSP) is modeled as a connection consisting of 138 one or more incoming segments (in-segments) and/or one or more 139 outgoing segments (out-segments) at an LSR. The association or 140 interconnection of the in-segments and out-segments is accomplished 141 by using a cross-connect. We use the terminology "connection" and 142 "LSP" interchangeably where the meaning is clear from the context. 144 in-segment This is analogous to a GMPLS label on an interface. 145 out-segment This is analogous to a GMPLS label on an interface. 146 cross-connect This describes the conceptual connection between a 147 set of in-segments and out-segments. Note that either 148 set may be empty; for example, a cross-connect may 150 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 152 connect only out-segments together with no in-segments 153 in the case where an LSP originates on an LSR. 155 The terms 'ingress' and 'head-end' (or 'head') are used in this 156 document to indicate the signaling source of an LSP. This is 157 sometimes also referred to as the 'sender'. 159 The terms 'egress' and 'tail-end' (or 'tail') are used in this 160 document to indicate the signaling destination of an LSP. 162 The term 'upstream' is used in this document to refer to the part of 163 an LSP closer to the ingress than the current point of reference. 165 The term 'downstream' is used in this document to refer to the part 166 of an LSP closer to the egress than the current point of reference. 168 The term 'forward' is used in this document to indicate the direction 169 of data flow from the ingress toward the egress. 171 The term 'reverse' is used in this document to indicate the direction 172 of data flow from the egress toward the ingress. 174 3. The Internet-Standard Management Framework 176 For a detailed overview of the documents that describe the current 177 Internet-Standard Management Framework, please refer to section 7 of 178 RFC 3410 [RFC3410]. 180 Managed objects are accessed via a virtual information store, termed 181 the Management Information Base or MIB. MIB objects are generally 182 accessed through the Simple Network Management Protocol (SNMP). 183 Objects in the MIB are defined using the mechanisms defined in the 184 Structure of Management Information (SMI). This memo specifies a MIB 185 module that is compliant to the SMIv2, which is described in STD 58, 186 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 187 [RFC2580]. 189 4. Outline 191 4.1 MIB Modules 193 There are two MIB modules defined in this document. 195 The GMPLS-LSR-STD-MIB module contains tables that sparse augment 196 tables defined in the MPLS-LSR-STD-MIB module [RFC3813]. This MIB 197 module is used in conjunction with the MPLS-LSR-STD-MIB module 198 [RFC3813] in systems that support GMPLS. 200 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 202 The GMPLS-LABEL-STD-MIB module contains objects for managing GMPLS 203 labels when they cannot be represented using the textual conventions 204 of the MPLS-TC-STD-MIB module [RFC3811], or when more detailed access 205 to the sub-fields of the labels is required. 207 4.1.1 Summary of the GMPLS-LSR-STD-MIB Module 209 The MIB tables in the GMPLS-LSR-STD-MIB module are as follows. 211 - The interface configuration table (gmplsInterfaceTable), which 212 sparse augments the mplsInterfaceTable [RFC3813] to enable the 213 GMPLS protocol on MPLS-capable interfaces. 215 - The in-segment (gmplsInSegmentTable) and out-segment 216 (gmplsOutSegmentTable) tables sparse augment mplsInSegmentTable and 217 mplsOutSegmentTable [RFC3813] to enable configuration of 218 GMPLS-specific parameters for LSP segments at an LSR. 220 These tables are described in the subsequent sections. 222 4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module 224 There is one MIB table in the GMPLS-LABEL-STD-MIB module as follows. 226 - The gmplsLabelTable allows Generalized 227 Labels to be defined and managed in a central location. 228 Generalized Labels can be of variable length and have distinct 229 bit-by-bit interpretations depending upon how they are defined 230 for the specific technology in which they are used. For example, 231 labels used for MPLS packet switching are different in length 232 and content from labels used in TDM timeslot switching. 234 4.2. Configuring Statically Provisioned LSPs 236 Configuring statically provisioned GMPLS LSPs through an LSR involves 237 the following steps: 239 - Configuring an interface using the MPLS-LSR-STD-MIB module 240 [RFC3813]. 242 - Enabling GMPLS on GMPLS capable interfaces using the 243 GMPLS-LSR-STD-MIB module in this document. 245 - Configuring in and out-segments using the MPLS-LSR-STD-MIB module 246 [RFC3813]. 248 - Configuring GMPLS extensions to the in-segments and out-segments 249 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 251 using the GMPLS-LSR-STD-MIB module in this document. 253 - Setting up the cross-connect table in the MPLS-LSR-STD-MIB module 254 [RFC3813] to associate segments and/or to indicate connection 255 origination and termination. 257 - Optionally setting up labels in the label table in the 258 GMPLS-LABEL-STD-MIB module in this document if the textual 259 convention MplsLabel [RFC3811] is not capable of holding the 260 required label (for example, if the label requires more than 32 261 bits to encode it), or if the operator wishes to disambiguate GMPLS 262 label types. 264 - Optionally specifying label stack actions in the MPLS-LSR-STD-MIB 265 module [RFC3813]. 267 - Optionally specifying segment traffic parameters in the 268 MPLS-LSR-STD-MIB module [RCF3813]. 270 5. Bidirectional LSPs 272 The GMPLS-LSR-STD-MIB module supports bidirectional LSPs as required 273 for GMPLS. A single value of mplsXCIndex is shared by all of the 274 segments for the entire bidirectional LSP. This facilitates a simple 275 reference from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing 276 more obvious. 278 It is, however, important that the direction of segments is 279 understood to avoid connecting all in-segments to all out-segments. 280 This is achieved by an object in each segment that indicates the 281 direction of the segment with respect to data flow. 283 A segment that is marked as 'forward' carries data from the 'head' of 284 the LSP to the 'tail'. A segment marked as 'reverse' carries data in 285 the reverse direction. 287 Where an LSP is signaled using a conventional signaling protocol, the 288 'head' of the LSP is the source of the signaling (also known as the 289 ingress) and the 'tail' is the destination (also known as the 290 egress). For manually configured LSPs an arbitrary decision must be 291 made about which segments are 'forward' and which 'reverse'. For 292 consistency this decision should be made across all LSRs that 293 participate in the LSP by assigning 'head' and 'tail' ends to the 294 LSP. 296 6. Example of LSP Setup 298 In this section we provide a brief example of using the MIB objects 299 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 301 described in sections 7 and 8 to set up an LSP. While this example is 302 not meant to illustrate every nuance of the MIB modules, it is 303 intended as an aid to understanding some of the key concepts. It is 304 meant to be read after going through the MIB modules themselves. A 305 prerequisite is an understanding of the MPLS-LSR-STD-MIB [RFC3813]. 307 Suppose that one would like to manually create a best-effort, 308 bi-directional LSP. Assume that, in the forward direction, the LSP 309 enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR 310 via MPLS interface B with ifIndex 13. For the reverse direction, we 311 assume the LSP enters via interface B and leaves via interface A 312 (i.e. the forward and reverse directions use the same bi-directional 313 interfaces). Let us also assume that we do not wish to have a label 314 stack beneath the top label on the outgoing labeled packets. The 315 following example illustrates which rows and corresponding objects 316 might be created to accomplish this. 318 We must first create rows in the gmplsLabelTable corresponding to the 319 labels required for each of the forward and reverse direction in- and 320 out-segments. For the purpose of this example the forward and 321 reverse labels on each interface will be the same, hence we need to 322 create just two rows in the gmplsLabelTable - one for each interface. 324 In gmplsLabelTable: 325 { 326 gmplsLabelInterface = 12, 327 gmplsLabelIndex = 1, 328 gmplsLabelSubindex = 0, 329 gmplsLabelType = gmplsFreeformLabel(3), 330 gmplsLabelFreeform = 0x123456789ABCDEF0 331 gmplsLabelRowStatus = createAndGo(4) 332 } 334 In gmplsLabelTable: 335 { 336 gmplsLabelInterface = 13, 337 gmplsLabelIndex = 1, 338 gmplsLabelSubindex = 0, 339 gmplsLabelType = gmplsFreeformLabel(3), 340 gmplsLabelFreeform = 0xFEDCBA9876543210 341 gmplsLabelRowStatus = createAndGo(4) 342 } 344 We must next create the appropriate in-segment and out-segment 345 entries. These are done in [RFC3813] using the mplsInSegmentTable and 346 mplsOutSegmentTable. Note that we use a row pointer to the two rows 347 in the gmplsLabelTable rather than specifying the labels explicitly 348 in the in- and out-segment tables. Also note that the row status for 349 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 351 each row is set to createAndWait(5) to allow corresponding entries in 352 the gmplsInSegmentTable and gmplsOutSegmentTable to be created. 354 For the forward direction. 356 In mplsInSegmentTable: 357 { 358 mplsInSegmentIndex = 0x00000015 359 mplsInSegmentLabel = 0, -- incoming label in label table 360 mplsInSegmentNPop = 1, 361 mplsInSegmentInterface = 12, -- incoming interface 362 -- RowPointer MUST point to the first accsesible column. 363 mplsInSegmentTrafficParamPtr = 0.0, 364 mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0) 365 mplsInSegmentRowStatus = createAndWait(5) 366 } 368 In mplsOutSegmentTable: 369 { 370 mplsOutSegmentIndex = 0x00000012, 371 mplsOutSegmentInterface = 13, -- outgoing interface 372 mplsOutSegmentPushTopLabel = true(1), 373 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 375 -- RowPointer MUST point to the first accessible column. 376 mplsOutSegmentTrafficParamPtr = 0.0, 377 mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0) 378 mplsOutSegmentRowStatus = createAndWait(5) 379 } 381 For the reverse direction. 383 In mplsInSegmentTable: 384 { 385 mplsInSegmentIndex = 0x00000016 387 mplsInSegmentLabel = 0, -- incoming label in label table 388 mplsInSegmentNPop = 1, 389 mplsInSegmentInterface = 13, -- incoming interface 391 -- RowPointer MUST point to the first accessible column. 392 mplsInSegmentTrafficParamPtr = 0.0, 393 mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0) 395 mplsInSegmentRowStatus = createAndWait(5) 396 } 398 In mplsOutSegmentTable: 400 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 402 { 403 mplsOutSegmentIndex = 0x00000013, 404 mplsOutSegmentInterface = 12, -- outgoing interface 405 mplsOutSegmentPushTopLabel = true(1), 406 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 408 -- RowPointer MUST point to the first accessible column. 409 mplsOutSegmentTrafficParamPtr = 0.0, 410 mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0) 412 mplsOutSegmentRowStatus = createAndWait(5) 413 } 415 These table entries are extended by entries in gmplsInSegmentTable 416 and gmplsOutSegmentTable. Note that the nature of the 'extends' 417 relationship is a sparse augmentation so that the entry in 418 gmplsInSegmentTable has the same index values as the entry in 419 mplsInSegmentTable. Similarly, the entry in gmplsOutSegmentTable has 420 the same index values as the entry in mplsOutSegmentTable. 422 First for the forward direction: 424 In gmplsInSegmentTable(0x00000015) 425 { 426 gmplsInSegmentDirection = forward (1) 427 } 429 In gmplsOutSegmentTable(0x00000012) 430 { 431 gmplsOutSegmentDirection = forward (1) 432 } 434 Next for the reverse direction: 436 In gmplsInSegmentTable(0x00000016) 437 { 438 gmplsInSegmentDirection = reverse (2) 439 } 441 In gmplsOutSegmentTable(0x00000013) 442 { 443 gmplsOutSegmentDirection = reverse (2) 444 } 446 Next, two cross-connect entries are created in the mplsXCTable of the 447 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 448 segments together. 450 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 452 In mplsXCTable: 453 { 454 mplsXCIndex = 0x01, 455 mplsXCInSegmentIndex = 0x00000015, 456 mplsXCOutSegmentIndex = 0x00000012, 457 mplsXCLspId = 0x0102 -- unique ID 458 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 459 mplsXCRowStatus = createAndGo(4) 460 } 462 In mplsXCTable: 463 { 464 mplsXCIndex = 0x02, 465 mplsXCInSegmentIndex = 0x00000016, 466 mplsXCOutSegmentIndex = 0x00000013, 467 mplsXCLspId = 0x0102 -- unique ID 468 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 469 mplsXCRowStatus = createAndGo(4) 470 } 472 Finally, the in-segments and out-segments are activated. 474 In mplsInSegmentTable(0x00000015): 475 { 476 mplsInSegmentRowStatus = active(1) 477 } 478 In mplsInSegmentTable(0x00000016): 479 { 480 mplsInSegmentRowStatus = active(1) 481 } 483 In mplsOutSegmentTable(0x00000012): 484 { 485 mplsOutSegmentRowStatus = active(1) 486 } 488 In mplsOutSegmentTable(0x00000013): 489 { 490 mplsOutSegmentRowStatus = active(1) 491 } 493 7. GMPLS Label Switching Router MIB Definitions 495 This MIB module makes references to the following documents. 496 [RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811], 497 [RFC2863] and [RFC3813]. 499 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 501 GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN 503 IMPORTS 504 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, zeroDotZero 505 FROM SNMPv2-SMI -- RFC2578 506 MODULE-COMPLIANCE, OBJECT-GROUP 507 FROM SNMPv2-CONF -- RFC2580 508 RowPointer 509 FROM SNMPv2-TC -- RFC2579 510 GmplsSegmentDirectionTC 511 FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB 512 -- RFC-Editor please resolve the reference above to GMPLSTCMIB 513 -- using the assigned RFC number and remove this note 514 mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex, 515 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 516 mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup 517 FROM MPLS-LSR-STD-MIB -- RFC3813 518 ifGeneralInformationGroup, ifCounterDiscontinuityGroup 519 FROM IF-MIB -- RFC2863 520 mplsStdMIB 521 FROM MPLS-TC-STD-MIB -- RFC3811 522 ; 524 gmplsLsrStdMIB MODULE-IDENTITY 525 LAST-UPDATED 526 "200604060001Z" -- 06 April 2006 00:00:01 GMT 527 ORGANIZATION 528 "IETF Common Control And Measurement Plane (CCAMP) Working Group" 529 CONTACT-INFO 530 " Thomas D. Nadeau 531 Cisco Systems, Inc. 532 Email: tnadeau@cisco.com 533 Adrian Farrel 534 Old Dog Consulting 535 Email: adrian@olddog.co.uk 536 Comments about this document should be emailed direct to the 537 CCAMP working group mailing list at ccamp@ops.ietf.org" 539 DESCRIPTION 540 "Copyright (C) The Internet Society (2006). This version of 541 this MIB module is part of RFC XXX; see the RFC itself for 542 full legal notices. 543 -- RFC Editor. Please replace XXX above with the correct RFC number and 544 -- remove this note. 546 This MIB module contains managed object definitions for the 547 Generalized Multiprotocol (GMPLS) Label Switching Router as 548 defined in: Generalized Multi-Protocol Label Switching (GMPLS) 549 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 551 Architecture, Mannie et al., RFC 3945, October 2004." 553 REVISION 554 "200604060001Z" -- 06 April 2006 00:00:01 GMT 555 DESCRIPTION 556 "Initial version issued as part of RFC XXX." 557 ::= { mplsStdMIB XXX } 558 -- RFC Editor. Please replace XXX above with the correct RFC number and 559 -- remove this note. 561 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 562 -- and remove this note 564 -- no notifications are currently defined. 565 gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } 566 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } 568 gmplsInterfaceTable OBJECT-TYPE 569 SYNTAX SEQUENCE OF GmplsInterfaceEntry 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION 573 "This table specifies per-interface GMPLS capability and 574 associated information. It extends the information in 575 mplsInterfaceTable of the MPLS-LSR-STD-MIB through a 576 sparse augmentation relationship." 577 REFERENCE 578 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 579 Router Management Information Base (MIB), RFC 3813." 580 ::= { gmplsLsrObjects 1 } 582 gmplsInterfaceEntry OBJECT-TYPE 583 SYNTAX GmplsInterfaceEntry 584 MAX-ACCESS not-accessible 585 STATUS current 586 DESCRIPTION 587 "A conceptual row in this table is created automatically by an 588 LSR for each interface that is both capable of supporting 589 GMPLS and that is configured to support GMPLS. Note that 590 support of GMPLS is not limited to control plane signaling, 591 but may include data-plane only function configured through 592 SNMP SET commands performed on this MIB module. 594 A conceptual row in this table may also be created via SNMP 595 SET commands or automatically by the LSR to supplement a 596 conceptual row in the mplsInterfaceTable where the interface 597 is not capable of GMPLS but where the other objects carried 598 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 600 in this row provide useful additional information for an 601 MPLS interface. 603 A conceptual row in this table will exist if and only if a 604 corresponding entry in mplsInterfaceTable exists, and a 605 corresponding entry in ifTable exists with ifType = mpls(166). 606 If the associated entry in ifTable is operationally disabled 607 (thus removing the GMPLS capabilities on the interface) or the 608 entry in mplsInterfaceTable is deleted, the corresponding entry 609 in this table MUST be deleted shortly thereafter. 611 The indexes are the same as for mplsInterfaceTable. Thus, the 612 entry with index 0 represents the per-platform label space and 613 contains parameters that apply to all interfaces that 614 participate in the per-platform label space." 615 REFERENCE 616 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 617 Router Management Information Base (MIB), RFC 3813." 618 INDEX { mplsInterfaceIndex } 619 ::= { gmplsInterfaceTable 1 } 621 GmplsInterfaceEntry ::= SEQUENCE { 622 gmplsInterfaceSignalingCaps BITS, 623 gmplsInterfaceRsvpHelloPeriod Unsigned32 624 } 626 gmplsInterfaceSignalingCaps OBJECT-TYPE 627 SYNTAX BITS { 628 unknown (0), 629 rsvpGmpls (1), 630 crldpGmpls (2), -- note the use of CR-LDP is deprecated 631 otherGmpls (3) 632 } 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "Defines the signaling capabilities on this interface. Multiple 637 bits may legitimately be set at once, but if 'unknown' is set 638 then no other bit may be set. Setting no bits implies that GMPLS 639 signaling cannot be performed on this interface and all LSPs 640 must be manually provisioned or that this table entry is only 641 present to supplement an entry in the mplsInterfaceTable by 642 providing the information carried in other objects in this row." 643 REFERENCE 644 "1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472. 645 2. The Multiprotocol Label Switching (MPLS) Working Group 646 decision on MPLS signaling protocols, RFC 3468. 647 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 649 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 651 " 652 DEFVAL { { rsvpGmpls } } 653 ::= { gmplsInterfaceEntry 1 } 655 gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE 656 SYNTAX Unsigned32 657 UNITS "milliseconds" 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "Period, in milliseconds, between sending RSVP Hello messages on 662 this interface. A value of 0 indicates that no Hello messages 663 should be sent on this interface. 665 This object is only valid if gmplsInterfaceSignalingCaps has no 666 bits set or includes the rsvpGmpls bit." 667 REFERENCE 668 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 669 section 5. 670 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 671 section 9.3." 672 DEFVAL { 3000 } 673 ::= { gmplsInterfaceEntry 2 } 675 gmplsInSegmentTable OBJECT-TYPE 676 SYNTAX SEQUENCE OF GmplsInSegmentEntry 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "This table sparse augments the mplsInSegmentTable of the 681 MPLS-LSR-STD-MIB to provide GMPLS-specific information about 682 incoming segments to an LSR." 683 REFERENCE 684 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 685 Router Management Information Base (MIB), RFC 3813." 686 ::= { gmplsLsrObjects 2 } 688 gmplsInSegmentEntry OBJECT-TYPE 689 SYNTAX GmplsInSegmentEntry 690 MAX-ACCESS not-accessible 691 STATUS current 692 DESCRIPTION 693 "An entry in this table extends the representation of an incoming 694 segment represented by an entry in mplsInSegmentTable in the 695 MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be 696 created by a network administrator via SNMP SET commands, or in 697 response to signaling protocol events. 699 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 701 Note that the storage type for this entry is given by the value 702 of mplsInSegmentStorageType in the corresponding entry of the 703 mplsInSegmentTable." 704 REFERENCE 705 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 706 Router Management Information Base (MIB), RFC 3813." 708 INDEX { mplsInSegmentIndex } 709 ::= { gmplsInSegmentTable 1 } 711 GmplsInSegmentEntry ::= SEQUENCE { 712 gmplsInSegmentDirection GmplsSegmentDirectionTC, 713 gmplsInSegmentExtraParamsPtr RowPointer 714 } 716 gmplsInSegmentDirection OBJECT-TYPE 717 SYNTAX GmplsSegmentDirectionTC 718 MAX-ACCESS read-create 719 STATUS current 720 DESCRIPTION 721 "This object indicates the direction of data flow on this 722 segment. This object cannot be modified if 723 mplsInSegmentRowStatus for the corresponding entry in the 724 mplsInSegmentTable is active(1)." 725 REFERENCE 726 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 727 Router Management Information Base (MIB), RFC 3813." 728 DEFVAL { forward } 729 ::= { gmplsInSegmentEntry 1 } 731 gmplsInSegmentExtraParamsPtr OBJECT-TYPE 732 SYNTAX RowPointer 733 MAX-ACCESS read-create 734 STATUS current 735 DESCRIPTION 736 "Some Tunnels will run over transports that can usefully support 737 technology-specific additional parameters (for example, SONET 738 resource usage). Such can be supplied from an external table and 739 referenced from here. A value of zeroDotzero in this attribute 740 indicates that there is no such additional information." 741 DEFVAL { zeroDotZero } 742 ::= { gmplsInSegmentEntry 2 } 744 gmplsOutSegmentTable OBJECT-TYPE 745 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 751 "This table sparse augments the mplsOutSegmentTable of the 752 MPLS-LSR-STD-MIB to provide GMPLS-specific information about 753 outgoing segments from an LSR." 754 REFERENCE 755 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 756 Router Management Information Base (MIB), RFC 3813." 757 ::= { gmplsLsrObjects 3 } 759 gmplsOutSegmentEntry OBJECT-TYPE 760 SYNTAX GmplsOutSegmentEntry 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "An entry in this table extends the representation of an outgoing 765 segment represented by an entry in mplsOutSegmentTable of the 766 MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be 767 created by a network administrator via SNMP SET commands, or in 768 response to signaling protocol events. 770 Note that the storage type for this entry is given by the value 771 of mplsOutSegmentStorageType in the corresponding entry of the 772 mplsOutSegmentTable." 773 REFERENCE 774 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 775 Router Management Information Base (MIB), RFC 3813." 776 INDEX { mplsOutSegmentIndex } 777 ::= { gmplsOutSegmentTable 1 } 779 GmplsOutSegmentEntry ::= SEQUENCE { 780 gmplsOutSegmentDirection GmplsSegmentDirectionTC, 781 gmplsOutSegmentTTLDecrement Unsigned32, 782 gmplsOutSegmentExtraParamsPtr RowPointer 783 } 785 gmplsOutSegmentDirection OBJECT-TYPE 786 SYNTAX GmplsSegmentDirectionTC 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "This object indicates the direction of data flow on this 791 segment. This object cannot be modified if 792 mplsOutSegmentRowStatus for the corresponding entry in the 793 mplsOutSegmentTable is active(1)." 794 REFERENCE 795 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 796 Router Management Information Base (MIB), RFC 3813." 797 DEFVAL { forward } 798 ::= { gmplsOutSegmentEntry 1 } 799 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 801 gmplsOutSegmentTTLDecrement OBJECT-TYPE 802 SYNTAX Unsigned32 803 MAX-ACCESS read-create 804 STATUS current 805 DESCRIPTION 806 "This object indicates the amount by which to decrement the TTL 807 of any payload packets forwarded on this segment if per-hop 808 decrementing is being done. 810 A value of zero indicates that no decrement should be made or 811 that per-hop decrementing is not in use. 813 See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable 814 of GMPLS-TE-STD-MIB for a value by which to decrement the TTL 815 for the whole of a tunnel. 817 This object cannot be modified if mplsOutSegmentRowStatus for 818 the associated entry in the mplsOutSegmentTable is active(1)." 819 REFERENCE 820 "1. Time To Live (TTL) Processing in Multi-Protocol Label 821 Switching (MPLS) Networks, RFC 3443. 822 2. Generalized Multiprotocol Label Switching (GMPLS) Traffic 823 Engineering Management Information Base, RFC XXX." 824 -- RFC Editor. Please insert the correct RFC number and remove this note 825 DEFVAL { 0 } 826 ::= { gmplsOutSegmentEntry 2 } 828 gmplsOutSegmentExtraParamsPtr OBJECT-TYPE 829 SYNTAX RowPointer 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 "Some Tunnels will run over transports that can usefully support 834 technology-specific additional parameters (for example, SONET 835 resource usage). Such can be supplied from an external table and 836 referenced from here. 838 A value of zeroDotzero in this attribute indicates that there is 839 no such additional information." 840 DEFVAL { zeroDotZero } 841 ::= { gmplsOutSegmentEntry 3 } 843 gmplsLsrGroups 844 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 846 gmplsLsrCompliances 847 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 848 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 850 -- Compliance requirement for fully compliant implementations. 852 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 853 STATUS current 854 DESCRIPTION 855 "Compliance statement for agents that provide full support for 856 GMPLS-LSR-STD-MIB. 858 The mandatory group has to be implemented by all LSRs that 859 originate, terminate or act as transit for TE-LSPs/tunnels. 860 In addition, depending on the type of tunnels supported, other 861 groups become mandatory as explained below." 863 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 865 MANDATORY-GROUPS { 866 ifGeneralInformationGroup, 867 ifCounterDiscontinuityGroup 868 } 870 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 872 MANDATORY-GROUPS { 873 mplsInterfaceGroup, 874 mplsInSegmentGroup, 875 mplsOutSegmentGroup, 876 mplsXCGroup, 877 mplsPerfGroup, 878 mplsLsrNotificationGroup 879 } 881 MODULE -- this module 883 MANDATORY-GROUPS { 884 gmplsInterfaceGroup, 885 gmplsInSegmentGroup, 886 gmplsOutSegmentGroup 887 } 889 OBJECT gmplsInSegmentDirection 890 SYNTAX GmplsSegmentDirectionTC 891 MIN-ACCESS read-only 892 DESCRIPTION 893 "The only valid value for unidrectional LSPs is forward(1)." 895 OBJECT gmplsOutSegmentDirection 896 SYNTAX GmplsSegmentDirectionTC 897 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 899 MIN-ACCESS read-only 900 DESCRIPTION 901 "The only valid value for unidrectional LSPs is forward(1)." 903 OBJECT gmplsOutSegmentTTLDecrement 904 MIN-ACCESS read-only 905 DESCRIPTION 906 "Write access is not required." 908 OBJECT gmplsInSegmentExtraParamsPtr 909 MIN-ACCESS read-only 910 DESCRIPTION 911 "Write access is not required." 913 OBJECT gmplsOutSegmentExtraParamsPtr 914 MIN-ACCESS read-only 915 DESCRIPTION 916 "Write access is not required." 918 ::= { gmplsLsrCompliances 1 } 920 -- Compliance requirement for implementations that provide read-only 921 -- access. 923 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 924 STATUS current 925 DESCRIPTION 926 "Compliance requirement for implementations that only provide 927 read-only support for GMPLS-LSR-STD-MIB. Such devices can then 928 be monitored but cannot be configured using this MIB module." 930 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 932 MANDATORY-GROUPS { 933 ifGeneralInformationGroup, 934 ifCounterDiscontinuityGroup 935 } 937 MODULE MPLS-LSR-STD-MIB 939 MANDATORY-GROUPS { 940 mplsInterfaceGroup, 941 mplsInSegmentGroup, 942 mplsOutSegmentGroup, 943 mplsXCGroup, 944 mplsPerfGroup 945 } 946 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 948 MODULE -- this module 950 MANDATORY-GROUPS { 951 gmplsInterfaceGroup, 952 gmplsInSegmentGroup, 953 gmplsOutSegmentGroup 954 } 956 OBJECT gmplsInterfaceSignalingCaps 957 MIN-ACCESS read-only 958 DESCRIPTION 959 "Write access is not required." 961 OBJECT gmplsInterfaceRsvpHelloPeriod 962 MIN-ACCESS read-only 963 DESCRIPTION 964 "Write access is not required." 966 OBJECT gmplsInSegmentDirection 967 SYNTAX GmplsSegmentDirectionTC 968 MIN-ACCESS read-only 969 DESCRIPTION 970 "The only valid value for unidrectional LSPs is forward(1)." 972 OBJECT gmplsInSegmentExtraParamsPtr 973 MIN-ACCESS read-only 974 DESCRIPTION 975 "Write access is not required." 977 OBJECT gmplsOutSegmentDirection 978 MIN-ACCESS read-only 979 DESCRIPTION 980 "The only valid value for unidrectional LSPs is forward(1)." 982 OBJECT gmplsOutSegmentTTLDecrement 983 MIN-ACCESS read-only 984 DESCRIPTION 985 "Write access is not required." 987 OBJECT gmplsOutSegmentExtraParamsPtr 988 MIN-ACCESS read-only 989 DESCRIPTION 990 "Write access is not required." 992 ::= { gmplsLsrCompliances 2 } 994 gmplsInterfaceGroup OBJECT-GROUP 995 OBJECTS { 996 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 998 gmplsInterfaceSignalingCaps, 999 gmplsInterfaceRsvpHelloPeriod 1000 } 1001 STATUS current 1002 DESCRIPTION 1003 "Collection of objects which provide additional 1004 information for an MPLS interface and are needed 1005 for GMPLS interface configuration and performance 1006 information." 1007 ::= { gmplsLsrGroups 1 } 1009 gmplsInSegmentGroup OBJECT-GROUP 1010 OBJECTS { 1011 gmplsInSegmentDirection, 1012 gmplsInSegmentExtraParamsPtr 1013 } 1014 STATUS current 1015 DESCRIPTION 1016 "Collection of objects which provide additional 1017 information for an MPLS in-segment and are needed 1018 for GMPLS in-segment configuration and performance 1019 information." 1020 ::= { gmplsLsrGroups 2 } 1022 gmplsOutSegmentGroup OBJECT-GROUP 1023 OBJECTS { 1024 gmplsOutSegmentDirection, 1025 gmplsOutSegmentTTLDecrement, 1026 gmplsOutSegmentExtraParamsPtr 1027 } 1028 STATUS current 1029 DESCRIPTION 1030 "Collection of objects which provide additional 1031 information for an MPLS out-segment and are needed 1032 for GMPLS out-segment configuration and performance 1033 information." 1034 ::= { gmplsLsrGroups 3 } 1035 END 1037 8. GMPLS Label MIB Definitions 1039 This MIB module makes references to the following documents. 1040 [RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811], 1041 [RFC2863], [RFC3289], [RFC3813], and [RFC3471]. 1043 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 1044 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1046 IMPORTS 1047 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32 1048 FROM SNMPv2-SMI -- RFC2578 1049 MODULE-COMPLIANCE, OBJECT-GROUP 1050 FROM SNMPv2-CONF -- RFC2580 1051 RowStatus, StorageType 1052 FROM SNMPv2-TC -- RFC2579 1053 InterfaceIndexOrZero 1054 FROM IF-MIB -- RFC2863 1055 IndexIntegerNextFree 1056 FROM DIFFSERV-MIB -- RFC3289 1057 MplsLabel, mplsStdMIB 1058 FROM MPLS-TC-STD-MIB -- RFC3811 1059 GmplsLabelTypeTC, GmplsFreeformLabelTC 1060 FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB 1061 -- RFC-Editor. Please resolve the reference above to GMPLSTCMIB 1062 -- to use the assigned RFC number and remove this note 1063 ; 1065 gmplsLabelStdMIB MODULE-IDENTITY 1066 LAST-UPDATED 1067 "200604060001Z" -- 06 April 2006 00:00:01 GMT 1068 ORGANIZATION 1069 "IETF Common Control And Measurement Plane (CCAMP) Working Group" 1070 CONTACT-INFO 1071 " Thomas D. Nadeau 1072 Cisco Systems, Inc. 1073 Email: tnadeau@cisco.com 1075 Adrian Farrel 1076 Old Dog Consulting 1077 Email: adrian@olddog.co.uk 1079 Comments about this document should be emailed direct to the 1080 CCAMP working group mailing list at ccamp@ops.ietf.org" 1082 DESCRIPTION 1083 "Copyright (C) The Internet Society (2006). This version of 1084 this MIB module is part of RFC XXX; see the RFC itself for 1085 full legal notices. 1086 -- RFC Editor. Please replace XXX above with the correct RFC number and 1087 -- remove this note. 1089 This MIB module contains managed object definitions for labels 1090 within GMPLS systems as defined in: 1091 Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1092 Functional Description, Berger, L. (Editor), RFC 3471, 1093 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1095 January 2003." 1096 REVISION 1097 "200604060001Z" -- 06 April 2006 00:00:01 GMT 1098 DESCRIPTION 1099 "Initial version issued as part of RFC XXX." 1100 ::= { mplsStdMIB XXX } 1101 -- RFC Editor. Please replace XXX above with the correct RFC number and 1102 -- remove this note. 1104 -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA 1105 -- and remove this note 1107 -- no notifications are currently defined. 1109 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 1110 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 1112 gmplsLabelIndexNext OBJECT-TYPE 1113 SYNTAX IndexIntegerNextFree 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "This object contains an unused value for gmplsLabelIndex, 1118 or a zero to indicate that no unused value exists or is 1119 available. 1121 A management application wishing to create a row in the 1122 gmplsLabelTable may read this object and then attempt to 1123 create a row in the table. If row creation fails (because 1124 another application has already created a row with the 1125 supplied index) the management application should read this 1126 object again to get a new index value. 1128 When a row is created in the gmplsLabelTable with the 1129 gmplsLabelIndex value held by this object, an implementation 1130 MUST change the value in this object." 1131 ::= { gmplsLabelObjects 1 } 1133 gmplsLabelTable OBJECT-TYPE 1134 SYNTAX SEQUENCE OF GmplsLabelEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "Table of GMPLS Labels. This table allows the representation 1139 of the more complex label forms required for GMPLS which cannot 1140 be held within the textual convention MplsLabel. That is labels 1141 that cannot be encoded within 32 bits. It is, nevertheless also 1142 capable of holding 32 bit labels or regular MPLS labels if 1143 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1145 desired. 1147 Each entry in this table represents an individual GMPLS label 1148 value. Labels in the tables in other MIB modules may be referred 1149 to using a row pointer into this table. The indexing of this 1150 table provides for arbitrary indexing and also for 1151 concatenation of labels. 1153 For an example of label concatenation see RFC3945 section 7.1. 1154 In essence, a GMPLS label may be composite in order to identify 1155 a set of resources in the data plane. Practical examples are 1156 timeslots and wavelength sets (which are not contiguous like 1157 wavebands). 1159 The indexing mechanism allows multiple entries in this table to 1160 be seen as a sequence of labels that should be concatenated. 1161 Ordering is potentially very sensitive for concatenation." 1162 REFERENCE 1163 "1. Generalized Multiprotocol Label Switching (GMPLS) 1164 Architecture, RFC 3945, section 7.1," 1165 ::= { gmplsLabelObjects 2 } 1167 gmplsLabelEntry OBJECT-TYPE 1168 SYNTAX GmplsLabelEntry 1169 MAX-ACCESS not-accessible 1170 STATUS current 1171 DESCRIPTION 1172 "An entry in this table represents a single label value. There 1173 are three indexes into the table. 1174 - The interface index may be helpful to distinguish which 1175 labels are in use on which interfaces or to handle cases 1176 where there are a very large number of labels in use in the 1177 system. When label representation is desired to apply to the 1178 whole system or when it is not important to distinguish 1179 labels by their interfaces, this index MAY be set to zero. 1181 - The label index provides a way of identifying the label. 1182 - The label sub-index is only used for concatenated labels. It 1183 identifies each component label. When non-concatenated labels 1184 are used, this index SHOULD be set to zero. 1185 A storage type object is supplied to control the storage type 1186 for each entry, but implementations should note that the storage 1187 type of conceptual rows in other tables that include row 1188 pointers to an entry in this table SHOULD dictate the storage 1189 type of the rows in this table where the row in the other table 1190 is more persistent." 1192 INDEX { 1193 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1195 gmplsLabelInterface, 1196 gmplsLabelIndex, 1197 gmplsLabelSubindex } 1198 ::= { gmplsLabelTable 1 } 1200 GmplsLabelEntry ::= SEQUENCE { 1201 gmplsLabelInterface InterfaceIndexOrZero, 1202 gmplsLabelIndex Unsigned32, 1203 gmplsLabelSubindex Unsigned32, 1204 gmplsLabelType GmplsLabelTypeTC, 1205 gmplsLabelMplsLabel MplsLabel, 1206 gmplsLabelPortWavelength Unsigned32, 1207 gmplsLabelFreeform GmplsFreeformLabelTC, 1208 gmplsLabelSonetSdhSignalIndex Integer32, 1209 gmplsLabelSdhVc Integer32, 1210 gmplsLabelSdhVcBranch Integer32, 1211 gmplsLabelSonetSdhBranch Integer32, 1212 gmplsLabelSonetSdhGroupBranch Integer32, 1213 gmplsLabelWavebandId Unsigned32, 1214 gmplsLabelWavebandStart Unsigned32, 1215 gmplsLabelWavebandEnd Unsigned32, 1216 gmplsLabelStorageType StorageType, 1217 gmplsLabelRowStatus RowStatus 1218 } 1220 gmplsLabelInterface OBJECT-TYPE 1221 SYNTAX InterfaceIndexOrZero 1222 MAX-ACCESS not-accessible 1223 STATUS current 1224 DESCRIPTION 1225 "The interface on which this label is used. If this object is set 1226 to zero, the label MUST have applicability across the 1227 whole system and is not limited to a single interface." 1228 ::= { gmplsLabelEntry 1 } 1230 gmplsLabelIndex OBJECT-TYPE 1231 SYNTAX Unsigned32 (0..4294967295) 1232 MAX-ACCESS not-accessible 1233 STATUS current 1234 DESCRIPTION 1235 "An arbitrary index into the table to identify a label. 1237 Note that implementations that are representing 32 bit labels 1238 within this table MAY choose to align this index with the value 1239 of the label and this may result in the use of the value zero 1240 since it represents a valid label value. Such implementation 1241 should be aware of the implications of sparsely populated 1242 tables. 1244 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1246 A management application may read the gmplsLabelIndexNext 1247 object to find a suitable value for this object." 1248 ::= { gmplsLabelEntry 2 } 1250 gmplsLabelSubindex OBJECT-TYPE 1251 SYNTAX Unsigned32 (0..4294967295) 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "In conjunction with gmplsLabelInterface and gmplsLabelIndex, 1256 this object uniquely identifies this row. This sub-index allows 1257 a single GMPLS label to be defined as a concatenation of labels. 1258 This is particularly useful in TDM. 1260 The ordering of sub-labels is strict with the sub-label with 1261 lowest gmplsLabelSubindex appearing first. Note that all 1262 sub-labels of a single GMPLS label must share the same 1263 gmplsLabelInterface and gmplsLabelIndex values. For labels that 1264 are not composed of concatenated sub-labels, this value SHOULD 1265 be set to zero." 1266 ::= { gmplsLabelEntry 3 } 1268 gmplsLabelType OBJECT-TYPE 1269 SYNTAX GmplsLabelTypeTC 1270 MAX-ACCESS read-create 1271 STATUS current 1272 DESCRIPTION 1273 "Identifies the type of this label. Note that this object does 1274 not determine whether MPLS or GMPLS signaling is in use: a value 1275 of gmplsMplsLabel (1) denotes that an MPLS packet label is 1276 present in the gmplsLabelMplsLabel object and encoded using the 1277 MplsLabel textual convention (may be a 20-bit MPLS label, a 10- 1278 or 23-bit Frame Relay label, or an ATM label), but does not 1279 describe whether this is signaled using MPLS or GMPLS. 1281 The value of this object helps determine which of the following 1282 objects are valid. This object cannot be modified if 1283 gmplsLabelRowStatus is active(1)." 1284 REFERENCE 1285 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1286 Functional Description, RFC 3471, section 3." 1287 ::= { gmplsLabelEntry 4 } 1289 gmplsLabelMplsLabel OBJECT-TYPE 1290 SYNTAX MplsLabel 1291 MAX-ACCESS read-create 1292 STATUS current 1293 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1295 DESCRIPTION 1296 "The value of an MPLS label (that is a packet label) if this 1297 table is used to store it. This may be used in MPLS systems even 1299 though the label values can be adequately stored in the MPLS MIB 1300 modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Further, in 1301 mixed MPLS and GMPLS systems it may be advantageous to store all 1302 labels in a single label table. Lastly, in GMPLS systems where 1303 packet labels are used (that is in systems that use GMPLS 1304 signaling and GMPLS labels for packet switching) it may be 1305 desirable to use this table. 1307 This object is only valid if gmplsLabelType is set 1308 to gmplsMplsLabel (1). This object cannot be modified if 1309 gmplsLabelRowStatus is active(1)." 1310 REFERENCE 1311 "1. MPLS Label Stack Encoding, RFC 3032." 1312 DEFVAL { 0 } 1313 ::= { gmplsLabelEntry 5 } 1315 gmplsLabelPortWavelength OBJECT-TYPE 1316 SYNTAX Unsigned32 1317 MAX-ACCESS read-create 1318 STATUS current 1319 DESCRIPTION 1320 "The value of a Port or Wavelength Label when carried as a 1321 Generalized Label. Only valid if gmplsLabelType is set to 1322 gmplsPortWavelengthLabel(2). This object cannot be modified if 1323 gmplsLabelRowStatus is active(1)." 1324 REFERENCE 1325 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1326 Functional Description, RFC 3471, section 3.2.1.1." 1327 DEFVAL { 0 } 1328 ::= { gmplsLabelEntry 6 } 1330 gmplsLabelFreeform OBJECT-TYPE 1331 SYNTAX GmplsFreeformLabelTC 1332 MAX-ACCESS read-create 1333 STATUS current 1334 DESCRIPTION 1335 "The value of a freeform Generalized Label that does not conform 1336 to one of the standardized label encoding or that an 1337 implementation chooses to represent as an octet string without 1338 further decoding. Only valid if gmplsLabelType is set to 1339 gmplsFreeformLabel(3). This object cannot be modified 1340 if gmplsLabelRowStatus is active(1)." 1341 REFERENCE 1342 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1343 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1345 Functional Description, RFC 3471, section 3.2." 1346 DEFVAL { '00'h } 1347 ::= { gmplsLabelEntry 7 } 1349 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 1350 SYNTAX Integer32 (0..4095) 1351 MAX-ACCESS read-create 1352 STATUS current 1353 DESCRIPTION 1354 "The Signal Index value (S) of a SONET or SDH Generalized Label. 1355 Zero indicates that this field is not significant. Only valid if 1356 gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1357 This object cannot be modified if gmplsLabelRowStatus is 1358 active(1)." 1359 REFERENCE 1360 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1361 for Synchronous Optical Network (SONET) and Synchronous 1362 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1363 DEFVAL { 0 } 1364 ::= { gmplsLabelEntry 8 } 1366 gmplsLabelSdhVc OBJECT-TYPE 1367 SYNTAX Integer32 (0..15) 1368 MAX-ACCESS read-create 1369 STATUS current 1370 DESCRIPTION 1371 "The VC Indicator (U) of an SDH Generalized Label. Zero indicates 1372 that this field is non-significant. 1373 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). 1374 This object cannot be modified if gmplsLabelRowStatus is 1375 active(1)." 1376 REFERENCE 1377 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1378 for Synchronous Optical Network (SONET) and Synchronous 1379 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1380 DEFVAL { 0 } 1381 ::= { gmplsLabelEntry 9 } 1383 gmplsLabelSdhVcBranch OBJECT-TYPE 1384 SYNTAX Integer32 (0..15) 1385 MAX-ACCESS read-create 1386 STATUS current 1387 DESCRIPTION 1388 "The VC Branch Indicator (K) of an SDH Generalized Label. Zero 1389 indicates that this field is non-significant. 1390 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This 1391 object cannot be modified if gmplsLabelRowStatus is active(1)." 1392 REFERENCE 1393 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1395 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1396 for Synchronous Optical Network (SONET) and Synchronous 1397 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1398 DEFVAL { 0 } 1399 ::= { gmplsLabelEntry 10 } 1401 gmplsLabelSonetSdhBranch OBJECT-TYPE 1402 SYNTAX Integer32 (0..15) 1403 MAX-ACCESS read-create 1404 STATUS current 1405 DESCRIPTION 1406 "The Branch Indicator (L) of a SONET or SDH Generalized Label. 1407 Zero indicates that this field is non-significant. 1408 Only valid gmplsLabelType is set to gmplsSonetLabel(4) or 1409 gmplsSdhLabel(5). This object cannot be modified if 1410 gmplsLabelRowStatus is active(1)." 1411 REFERENCE 1412 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1413 for Synchronous Optical Network (SONET) and Synchronous 1414 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1415 DEFVAL { 0 } 1416 ::= { gmplsLabelEntry 11 } 1418 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1419 SYNTAX Integer32 (0..15) 1420 MAX-ACCESS read-create 1421 STATUS current 1422 DESCRIPTION 1423 "The Group Branch Indicator (M) of a SONET or SDH Generalized 1424 Label. 1425 Zero indicates that this field is non-significant. 1426 Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or 1427 gmplsSdhLabel(5). This object cannot be modified if 1428 gmplsLabelRowStatus is active(1)." 1429 REFERENCE 1430 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1431 for Synchronous Optical Network (SONET) and Synchronous 1432 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1433 DEFVAL { 0 } 1434 ::= { gmplsLabelEntry 12 } 1436 gmplsLabelWavebandId OBJECT-TYPE 1437 SYNTAX Unsigned32 1438 MAX-ACCESS read-create 1439 STATUS current 1440 DESCRIPTION 1441 "The waveband identifier component of a waveband label. Only 1442 valid if gmplsLabelType is set to gmplsWavebandLabel(6). This 1443 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1445 object cannot be modified if gmplsLabelRowStatus is active(1)." 1446 REFERENCE 1447 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1448 Functional Description, RFC 3471, section 3.3." 1449 DEFVAL { 0 } 1450 ::= { gmplsLabelEntry 13 } 1452 gmplsLabelWavebandStart OBJECT-TYPE 1453 SYNTAX Unsigned32 1454 MAX-ACCESS read-create 1455 STATUS current 1456 DESCRIPTION 1457 "The starting label component of a waveband label. 1458 Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). 1459 This object cannot be modified if 1460 gmplsLabelRowStatus is active(1)." 1461 REFERENCE 1462 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1463 Functional Description, RFC 3471, section 3.3." 1464 DEFVAL { 0 } 1465 ::= { gmplsLabelEntry 14 } 1467 gmplsLabelWavebandEnd OBJECT-TYPE 1468 SYNTAX Unsigned32 1469 MAX-ACCESS read-create 1470 STATUS current 1471 DESCRIPTION 1472 "The end label component of a waveband label. Only valid if 1473 gmplsLabelType is set to gmplsWavebandLabel(6). This object 1474 cannot be modified if gmplsLabelRowStatus is active(1)." 1475 REFERENCE 1476 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1477 Functional Description, RFC 3471, section 3.3." 1478 DEFVAL { 0 } 1479 ::= { gmplsLabelEntry 15 } 1481 gmplsLabelStorageType OBJECT-TYPE 1482 SYNTAX StorageType 1483 MAX-ACCESS read-create 1484 STATUS current 1485 DESCRIPTION 1486 "This variable indicates the storage type for this object. The 1487 agent MUST ensure that this object's value remains consistent 1488 with the storage type of any rows in other tables that contain 1489 pointers to this row. In particular, the storage type of this 1490 row must be at least as permanent as that of any row that point 1491 to it. 1493 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1495 Conceptual rows having the value 'permanent' need not 1496 allow write-access to any columnar objects in the row." 1497 REFERENCE 1498 "1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2." 1499 DEFVAL { volatile } 1500 ::= { gmplsLabelEntry 16 } 1502 gmplsLabelRowStatus OBJECT-TYPE 1503 SYNTAX RowStatus 1504 MAX-ACCESS read-create 1505 STATUS current 1506 DESCRIPTION 1507 "This variable is used to create, modify, and/or delete a row in 1508 this table. When a row in this table has a row in the active(1) 1509 state, no objects in this row can be modified except the 1510 gmplsLabelRowStatus and gmplsLabelStorageType. 1512 The gmplsLabelType object does not have a default and must be 1513 set before a row can become active. The corresponding label 1514 objects (dependent on the value of gmplsLabelType) should also 1515 be set unless they happen to need to use the specified default 1516 values as follows: 1518 gmplsLabelType setting objects to be set 1519 -------------------------------------------------------------- 1520 gmplsMplsLabel(1) gmplsLabelMplsLabel 1522 gmplsPortWavelengthLabel(2) gmplsLabelPortWavelength 1524 gmplsFreeformLabel(3) gmplsLabelFreeform 1526 gmplsSonetLabel(4) gmplsLabelSonetSdhSignalIndex 1527 gmplsLabelSdhVc 1528 gmplsLabelSdhVcBranch 1529 gmplsLabelSonetSdhBranch 1530 gmplsLabelSonetSdhGroupBranch 1532 gmplsSdhLabel(5) gmplsLabelSonetSdhSignalIndex 1533 gmplsLabelSdhVc 1534 gmplsLabelSdhVcBranch 1535 gmplsLabelSonetSdhBranch 1536 gmplsLabelSonetSdhGroupBranch 1538 gmplsWavebandLabel(6) gmplsLabelWavebandId 1539 gmplsLabelWavebandStart 1540 gmplsLabelWavebandEnd" 1541 ::= { gmplsLabelEntry 17 } 1542 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1544 gmplsLabelGroups 1545 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1547 gmplsLabelCompliances 1548 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1550 gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE 1551 STATUS current 1552 DESCRIPTION 1553 "Compliance requirement for implementations that only provide 1554 read-only support for GMPLS-LABEL-STD-MIB. Such devices can then 1555 be monitored but cannot be configured using this MIB module." 1557 MODULE -- this module 1559 -- The mandatory groups have to be implemented by LSRs claiming 1560 -- support for this MIB module. This MIB module is, however, not 1561 -- mandatory for a working implementation of a GMPLS LSR with full 1562 -- MIB support if the GMPLS labels in use can be represented within 1563 -- a 32 bit quantity. 1565 MANDATORY-GROUPS { 1566 gmplsLabelTableGroup 1567 } 1569 GROUP gmplsLabelPacketGroup 1570 DESCRIPTION 1571 "This group extends gmplsLabelTableGroup for implementations that 1572 support packet labels. It is optional for implementations that 1573 do not support packet labels." 1575 GROUP gmplsLabelPortWavelengthGroup 1576 DESCRIPTION 1577 "This group extends gmplsLabelTableGroup for implementations that 1578 support port and wavelength labels. It is optional for 1579 implementations that do not support wavelength labels." 1581 GROUP gmplsLabelFreeformGroup 1582 DESCRIPTION 1583 "This group extends gmplsLabelTableGroup for implementations that 1584 support freeform labels. It is optional for implementations that 1585 do not support freeform labels." 1587 GROUP gmplsLabelSonetSdhGroup 1588 DESCRIPTION 1589 "This group extends gmplsLabelTableGroup for implementations that 1590 support SONET or SDH labels. It is optional for implementations 1591 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1593 that do not support SONET or SDH labels." 1595 GROUP gmplsLabelWavebandGroup 1596 DESCRIPTION 1597 "This group extends gmplsLabelTableGroup for implementations that 1598 support Waveband labels. It is optional for implementations that 1599 do not support Waveband labels." 1601 OBJECT gmplsLabelType 1602 MIN-ACCESS read-only 1603 DESCRIPTION 1604 "Write access is not required." 1606 OBJECT gmplsLabelMplsLabel 1607 MIN-ACCESS read-only 1608 DESCRIPTION 1609 "Write access is not required." 1611 OBJECT gmplsLabelPortWavelength 1612 MIN-ACCESS read-only 1613 DESCRIPTION 1614 "Write access is not required." 1616 OBJECT gmplsLabelFreeform 1617 MIN-ACCESS read-only 1618 DESCRIPTION 1619 "Write access is not required." 1621 OBJECT gmplsLabelSonetSdhSignalIndex 1622 MIN-ACCESS read-only 1623 DESCRIPTION 1624 "Write access is not required." 1626 OBJECT gmplsLabelSdhVc 1627 MIN-ACCESS read-only 1628 DESCRIPTION 1629 "Write access is not required." 1631 OBJECT gmplsLabelSdhVcBranch 1632 MIN-ACCESS read-only 1633 DESCRIPTION 1634 "Write access is not required." 1636 OBJECT gmplsLabelSonetSdhBranch 1637 MIN-ACCESS read-only 1638 DESCRIPTION 1639 "Write access is not required." 1640 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1642 OBJECT gmplsLabelSonetSdhGroupBranch 1643 MIN-ACCESS read-only 1644 DESCRIPTION 1645 "Write access is not required." 1647 OBJECT gmplsLabelWavebandId 1648 MIN-ACCESS read-only 1649 DESCRIPTION 1650 "Write access is not required." 1652 OBJECT gmplsLabelWavebandStart 1653 MIN-ACCESS read-only 1654 DESCRIPTION 1655 "Write access is not required." 1657 OBJECT gmplsLabelWavebandEnd 1658 MIN-ACCESS read-only 1659 DESCRIPTION 1660 "Write access is not required." 1662 OBJECT gmplsLabelStorageType 1663 MIN-ACCESS read-only 1664 DESCRIPTION 1665 "Write access is not required." 1667 OBJECT gmplsLabelRowStatus 1668 SYNTAX RowStatus { active(1) } 1669 MIN-ACCESS read-only 1670 DESCRIPTION 1671 "Write access is not required, and active(1) is 1672 the only status that needs to be supported." 1674 ::= { gmplsLabelCompliances 1 } 1676 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1677 STATUS current 1678 DESCRIPTION 1679 "Compliance statement for agents that support the complete 1680 GMPLS-LABEL-STD-MIB module. 1682 The mandatory groups have to be implemented by GMPLS LSRs 1683 claiming support for this MIB module. This MIB module is, 1684 however, not mandatory for a working implementation of a GMPLS 1685 LSR with full MIB support if the GMPLS labels in use can be 1686 represented within a 32 bit quantity." 1688 MODULE -- this module 1689 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1691 MANDATORY-GROUPS { 1692 gmplsLabelTableGroup 1693 } 1695 ::= { gmplsLabelCompliances 2 } 1697 gmplsLabelTableGroup OBJECT-GROUP 1698 OBJECTS { 1699 gmplsLabelIndexNext, 1700 gmplsLabelType, 1701 gmplsLabelStorageType, 1702 gmplsLabelRowStatus 1703 } 1705 STATUS current 1706 DESCRIPTION 1707 "Necessary, but not sufficient, set of objects to implement label 1708 table support. In addition, depending on the type of labels 1709 supported, the following other groups defined below are 1710 mandatory: 1712 gmplsLabelWavebandGroup and/or 1713 gmplsLabelPacketGroup and/or 1714 gmplsLabelPortWavelengthGroup and/or 1715 gmplsLabelFreeformGroup and/or 1716 gmplsLabelSonetSdhGroup." 1717 ::= { gmplsLabelGroups 1 } 1719 gmplsLabelPacketGroup OBJECT-GROUP 1720 OBJECTS { 1721 gmplsLabelMplsLabel 1722 } 1723 STATUS current 1724 DESCRIPTION 1725 "Object needed to implement Packet (MPLS) labels." 1726 ::= { gmplsLabelGroups 2 } 1728 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1729 OBJECTS { 1730 gmplsLabelPortWavelength 1731 } 1732 STATUS current 1733 DESCRIPTION 1734 "Object needed to implement Port and Wavelength labels." 1735 ::= { gmplsLabelGroups 3 } 1737 gmplsLabelFreeformGroup OBJECT-GROUP 1738 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1740 OBJECTS { 1741 gmplsLabelFreeform 1742 } 1743 STATUS current 1744 DESCRIPTION 1745 "Object needed to implement Freeform labels." 1746 ::= { gmplsLabelGroups 4 } 1748 gmplsLabelSonetSdhGroup OBJECT-GROUP 1749 OBJECTS { 1750 gmplsLabelSonetSdhSignalIndex, 1751 gmplsLabelSdhVc, 1752 gmplsLabelSdhVcBranch, 1753 gmplsLabelSonetSdhBranch, 1754 gmplsLabelSonetSdhGroupBranch 1755 } 1756 STATUS current 1757 DESCRIPTION 1758 "Object needed to implement SONET and SDH labels." 1759 ::= { gmplsLabelGroups 5 } 1761 gmplsLabelWavebandGroup OBJECT-GROUP 1762 OBJECTS { 1763 gmplsLabelWavebandId, 1764 gmplsLabelWavebandStart, 1765 gmplsLabelWavebandEnd 1766 } 1767 STATUS current 1768 DESCRIPTION 1769 "Object needed to implement Waveband labels." 1770 ::= { gmplsLabelGroups 6 } 1771 END 1773 9. Security Considerations 1775 It is clear that the MIB modules described in this document in 1776 association with the MPLS-LSR-STD-MIB [RFC3813] are potentially 1777 useful for monitoring of GMPLS LSRs. These MIB modules can also be 1778 used for configuration of certain objects, and anything that can be 1779 configured can be incorrectly configured, with potentially disastrous 1780 results. 1782 There are a number of management objects defined in these MIB modules 1783 with a MAX-ACCESS clause of read-write and/or read-create. Such 1784 objects may be considered sensitive or vulnerable in some network 1785 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1787 environments. The support for SET operations in a non-secure 1788 environment without proper protection can have a negative effect on 1789 network operations. These are the tables and objects and their 1790 sensitivity/vulnerability: 1792 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1793 and gmplsLabelTable collectively contain objects to provision 1794 GMPLS interfaces, LSPs and their associated parameters on a Label 1795 Switching Router (LSR). Unauthorized write access to objects in 1796 these tables, could result in disruption of traffic on the 1797 network. This is especially true if an LSP has already been 1798 established. 1800 Some of the readable objects in these MIB modules (i.e., objects with 1801 a MAX-ACCESS other than not-accessible) may be considered sensitive 1802 or vulnerable in some network environments. It is thus important to 1803 control even GET and/or NOTIFY access to these objects and possibly 1804 to even encrypt the values of these objects when sending them over 1805 the network via SNMP. These are the tables and objects and their 1806 sensitivity/vulnerability: 1808 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1809 and gmplsLabelTable collectively show the LSP network topology and 1810 its capabilities. If an Administrator does not want to reveal this 1811 information, then these tables should be considered 1812 sensitive/vulnerable. 1814 SNMP versions prior to SNMPv3 did not include adequate security. Even 1815 if the network itself is secure (for example by using IPSec), even 1816 then, there is no control as to who on the secure network is allowed 1817 to access and GET/SET (read/change/create/delete) the objects in 1818 these MIB modules. 1820 It is RECOMMENDED that implementers consider the security features as 1821 provided by the SNMPv3 framework (see [RFC3410], section 8), 1822 including full support for the SNMPv3 cryptographic mechanisms (for 1823 authentication and privacy). 1825 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1826 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1827 enable cryptographic security. It is then a customer/operator 1828 responsibility to ensure that the SNMP entity giving access to an 1829 instance of this MIB module, is properly configured to give access to 1830 the objects only to those principals (users) that have legitimate 1831 rights to indeed GET or SET (change/create/delete) them. 1833 10. Acknowledgments 1834 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1836 This document is a product of the CCAMP Working Group. 1838 This document extends [RFC3813]. The authors would like to express 1839 their gratitude to all those who worked on that earlier MIB document. 1841 The authors would like to express their thanks to Dan Joyle for his 1842 careful review and comments on early versions of the Label Table. 1843 Special thanks to Joan Cucchiara and Len Nieman for their help with 1844 compilation issues. Tom Petch and Bert Wijnen provided useful input 1845 in the final stages of review. 1847 Joan Cucchiara provided a helpful and very thorough MIB Doctor 1848 review. 1850 11. IANA Considerations 1852 -- (Note to RFC-Editor:) 1853 -- We request that you assign contiguous RFC numbers to the three GMPLS 1854 -- MIB documents. 1855 -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to 1856 -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to 1857 -- draft-ietf-ccamp-gmpls-te-mib. 1858 -- (Please remove this note prior to publication.) 1860 IANA is requested to root MIB objects in the two MIB modules 1861 contained in this document under the mplsStdMIB subtree. 1863 In the future, GMPLS related standards track MIB modules should be 1864 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to 1865 manage that namespace in the SMI Numbers registry [RFC3811]. New 1866 assignments can only be made via a Standards Action as specified in 1867 [RFC2434]. 1869 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 1871 The IANA is requested to assign { mplsStdMIB YYY } to the 1872 GMPLS-LSR-STD-MIB module specified in this document, and to record 1873 the assignment in the SMI Numbers registry. 1874 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 1875 -- and remove this note 1877 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 1879 The IANA is requested to assign { mplsStdMIB ZZZ } to the 1880 GMPLS-LABEL-STD-MIB module specified in this document, and to record 1881 the assignment in the SMI Numbers registry. 1883 -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA 1884 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1886 -- and remove this note 1888 12. References 1890 12.1. Normative References 1892 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1893 Requirements Levels", BCP 14, RFC 2119, March 1997. 1895 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1896 J., Rose, M., and S. Waldbusser, "Structure of 1897 Management Information Version 2 (SMIv2)", STD 58, RFC 1898 2578, April 1999. 1900 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1901 J., Rose, M., and S. Waldbusser, "Textual Conventions 1902 for SMIv2", STD 58, RFC 2579, April 1999. 1904 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1905 J., Rose, M., and S. Waldbusser, "Conformance Statements 1906 for SMIv2", STD 58, RFC 2580, April 1999. 1908 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1909 MIB", RFC 2863, June 2000. 1911 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1912 "Multiprotocol Label Switching Architecture", RFC 3031, 1913 January 2001. 1915 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 1916 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 1917 Encoding", RFC 3032, January 2001. 1919 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 1920 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 1921 Tunnels", RFC 3209, December 2001. 1923 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1924 Information Base for the Differentiated Services 1925 Architecture", RFC 3289, May 2002. 1927 [RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL) 1928 Processing in Multi-Protocol Label Switching (MPLS) 1929 Networks", RFC 3443, January 2003. 1931 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 1932 (GMPLS) Signaling Functional Description", RFC 3471, 1933 January 2003. 1935 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1937 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 1938 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1939 Engineering (RSVP-TE) Extensions", RFC 3473, January 1940 2003. 1942 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1943 Conventions and for Multiprotocol Label Switching (MPLS) 1944 Management", RFC 3811, June 2004. 1946 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1947 "Multiprotocol Label Switching (MPLS) Label Switching 1948 (LSR) Router Management Information Base (MIB)", RFC 1949 3813, June 2004. 1951 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 1952 Switching (GMPLS) Architecture", RFC 3945, October 2004. 1954 [RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi- 1955 Protocol Label Switching (GMPLS) Extensions for 1956 Synchronous Optical Network (SONET) and Synchronous 1957 Digital Hierarchy (SDH) Control", RFC 3946, October 1958 2004. 1960 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 1961 Conventions for Multiprotocol Label Switching (MPLS) 1962 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 1963 progress. 1965 [GMPLSTEMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 1966 Label Switching (GMPLS) Traffic Engineering Management 1967 Information Base", draft-ietf-ccamp-gmpls-te-mib, work 1968 in progress. 1970 12.2. Informative References 1972 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1973 "Introduction and Applicability Statements for 1974 Internet-Standard Management Framework", RFC 3410, 1975 December 2002. 1977 [RFC3468] Andersson, L., and Swallow, G., "The Multiprotocol 1978 Label Switching (MPLS) Working Group decision on 1979 MPLS signaling protocols", RFC 3468, February 2003. 1981 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 1982 Multi-Protocol Label Switching (MPLS) Signaling 1983 - Constraint-based Routed Label Distribution Protocol 1985 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 1987 (CR-LDP) Extensions", RFC 3472, January 2003. 1989 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1990 "Multiprotocol Label Switching (MPLS) Traffic 1991 Engineering (TE) Management Information Base (MIB)", 1992 RFC 3812, June 2004. 1994 13. Contact Information 1996 Thomas D. Nadeau 1997 Cisco Systems, Inc. 1998 1414 Massachusetts Ave. 1999 Boxborough, MA 01719 2000 Email: tnadeau@cisco.com 2002 Adrian Farrel 2003 Old Dog Consulting 2004 Phone: +44-(0)-1978-860944 2005 Email: adrian@olddog.co.uk 2007 Cheenu Srinivasan 2008 Bloomberg L.P. 2009 731 Lexington Ave. 2010 New York, NY 10022 2011 Phone: +1-212-617-3682 2012 Email: cheenu@bloomberg.net 2014 Tim Hall 2015 Data Connection Ltd. 2016 100 Church Street 2017 Enfield, Middlesex, EN2 6BQ, UK 2018 Phone: +44 20 8366 1177 2019 Email: tim.hall@dataconnection.com 2021 Ed Harrison 2022 Data Connection Ltd. 2023 100 Church Street 2024 Enfield, Middlesex, EN2 6BQ, UK 2025 Phone: +44 20 8366 1177 2026 Email: ed.harrison@dataconnection.com 2027 draft-ietf-ccamp-gmpls-lsr-mib-14.txt April 28, 2006 2029 14. Intellectual Property Considerations 2031 The IETF takes no position regarding the validity or scope of any 2032 Intellectual Property Rights or other rights that might be claimed to 2033 pertain to the implementation or use of the technology described in 2034 this document or the extent to which any license under such rights 2035 might or might not be available; nor does it represent that it has 2036 made any independent effort to identify any such rights. Information 2037 on the procedures with respect to rights in RFC documents can be 2038 found in BCP 78 and BCP 79. 2040 Copies of IPR disclosures made to the IETF Secretariat and any 2041 assurances of licenses to be made available, or the result of an 2042 attempt made to obtain a general license or permission for the use of 2043 such proprietary rights by implementers or users of this 2044 specification can be obtained from the IETF on-line IPR repository at 2045 http://www.ietf.org/ipr. 2047 The IETF invites any interested party to bring to its attention any 2048 copyrights, patents or patent applications, or other proprietary 2049 rights that may cover technology that may be required to implement 2050 this standard. Please address the information to the IETF at ietf- 2051 ipr@ietf.org. 2053 15. Full Copyright Statement 2055 Copyright (C) The Internet Society (2006). This document is subject 2056 to the rights, licenses and restrictions contained in BCP 78, and 2057 except as set forth therein, the authors retain all their rights. 2059 This document and the information contained herein are provided on an 2060 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2061 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2062 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2063 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2064 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2065 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.