idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2059. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2032. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2039. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2045. ** 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 6557 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 1914, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1918, but no explicit reference was found in the text == Unused Reference: 'RFC3443' is defined on line 1926, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 1930, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 1934, but no explicit reference was found in the text == Unused Reference: 'RFC3946' is defined on line 1953, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 1976, 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-12.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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-12.txt April 11, 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. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 646 DEFVAL { { rsvpGmpls } } 647 ::= { gmplsInterfaceEntry 1 } 648 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 650 gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE 651 SYNTAX Unsigned32 652 UNITS "milliseconds" 653 MAX-ACCESS read-create 654 STATUS current 655 DESCRIPTION 656 "Period, in milliseconds, between sending RSVP Hello messages on 657 this interface. A value of 0 indicates that no Hello messages 658 should be sent on this interface. 660 This object is only valid if gmplsInterfaceSignalingCaps has no 661 bits set or includes the rsvpGmpls bit." 662 REFERENCE 663 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 664 section 5. 665 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 666 section 9.3." 667 DEFVAL { 3000 } 668 ::= { gmplsInterfaceEntry 2 } 670 gmplsInSegmentTable OBJECT-TYPE 671 SYNTAX SEQUENCE OF GmplsInSegmentEntry 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "This table sparse augments the mplsInSegmentTable of the 676 MPLS-LSR-STD-MIB to provide GMPLS-specific information about 677 incoming segments to an LSR." 678 REFERENCE 679 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 680 Router Management Information Base (MIB), RFC 3813." 681 ::= { gmplsLsrObjects 2 } 683 gmplsInSegmentEntry OBJECT-TYPE 684 SYNTAX GmplsInSegmentEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "An entry in this table extends the representation of an incoming 689 segment represented by an entry in mplsInSegmentTable in the 690 MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be 691 created by a network administrator via SNMP SET commands, or in 692 response to signaling protocol events. 694 Note that the storage type for this entry is given by the value 695 of mplsInSegmentStorageType in the corresponding entry of the 696 mplsInSegmentTable." 697 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 699 REFERENCE 700 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 701 Router Management Information Base (MIB), RFC 3813." 703 INDEX { mplsInSegmentIndex } 704 ::= { gmplsInSegmentTable 1 } 706 GmplsInSegmentEntry ::= SEQUENCE { 707 gmplsInSegmentDirection GmplsSegmentDirectionTC, 708 gmplsInSegmentExtraParamsPtr RowPointer 709 } 711 gmplsInSegmentDirection OBJECT-TYPE 712 SYNTAX GmplsSegmentDirectionTC 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "This object indicates the direction of data flow on this 717 segment. This object cannot be modified if 718 mplsInSegmentRowStatus for the corresponding entry in the 719 mplsInSegmentTable is active(1)." 720 REFERENCE 721 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 722 Router Management Information Base (MIB), RFC 3813." 723 DEFVAL { forward } 724 ::= { gmplsInSegmentEntry 1 } 726 gmplsInSegmentExtraParamsPtr OBJECT-TYPE 727 SYNTAX RowPointer 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "Some Tunnels will run over transports that can usefully support 732 technology-specific additional parameters (for example, SONET 733 resource usage). Such can be supplied from an external table and 734 referenced from here. A value of zeroDotzero in this attribute 735 indicates that there is no such additional information." 736 DEFVAL { zeroDotZero } 737 ::= { gmplsInSegmentEntry 2 } 739 gmplsOutSegmentTable OBJECT-TYPE 740 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "This table sparse augments the mplsOutSegmentTable of the 745 MPLS-LSR-STD-MIB to provide GMPLS-specific information about 746 outgoing segments from an LSR." 747 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 749 REFERENCE 750 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 751 Router Management Information Base (MIB), RFC 3813." 752 ::= { gmplsLsrObjects 3 } 754 gmplsOutSegmentEntry OBJECT-TYPE 755 SYNTAX GmplsOutSegmentEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "An entry in this table extends the representation of an outgoing 760 segment represented by an entry in mplsOutSegmentTable of the 761 MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be 762 created by a network administrator via SNMP SET commands, or in 763 response to signaling protocol events. 765 Note that the storage type for this entry is given by the value 766 of mplsOutSegmentStorageType in the corresponding entry of the 767 mplsOutSegmentTable." 768 REFERENCE 769 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 770 Router Management Information Base (MIB), RFC 3813." 771 INDEX { mplsOutSegmentIndex } 772 ::= { gmplsOutSegmentTable 1 } 774 GmplsOutSegmentEntry ::= SEQUENCE { 775 gmplsOutSegmentDirection GmplsSegmentDirectionTC, 776 gmplsOutSegmentTTLDecrement Unsigned32, 777 gmplsOutSegmentExtraParamsPtr RowPointer 778 } 780 gmplsOutSegmentDirection OBJECT-TYPE 781 SYNTAX GmplsSegmentDirectionTC 782 MAX-ACCESS read-create 783 STATUS current 784 DESCRIPTION 785 "This object indicates the direction of data flow on this 786 segment. This object cannot be modified if 787 mplsOutSegmentRowStatus for the corresponding entry in the 788 mplsOutSegmentTable is active(1)." 789 REFERENCE 790 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 791 Router Management Information Base (MIB), RFC 3813." 792 DEFVAL { forward } 793 ::= { gmplsOutSegmentEntry 1 } 795 gmplsOutSegmentTTLDecrement OBJECT-TYPE 796 SYNTAX Unsigned32 797 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 799 MAX-ACCESS read-create 800 STATUS current 801 DESCRIPTION 802 "This object indicates the amount by which to decrement the TTL 803 of any payload packets forwarded on this segment if per-hop 804 decrementing is being done. 806 A value of zero indicates that no decrement should be made or 807 that per-hop decrementing is not in use. 809 See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable 810 of GMPLS-TE-STD-MIB for a value by which to decrement the TTL 811 for the whole of a tunnel. 813 This object cannot be modified if mplsOutSegmentRowStatus for 814 the associated entry in the mplsOutSegmentTable is active(1)." 815 REFERENCE 816 "1. Time To Live (TTL) Processing in Multi-Protocol Label 817 Switching (MPLS) Networks, RFC 3443. 818 2. Generalized Multiprotocol Label Switching (GMPLS) Traffic 819 Engineering Management Information Base, RFC XXX." 820 -- RFC Editor. Please insert the correct RFC number and remove this note 821 DEFVAL { 0 } 822 ::= { gmplsOutSegmentEntry 2 } 824 gmplsOutSegmentExtraParamsPtr OBJECT-TYPE 825 SYNTAX RowPointer 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "Some Tunnels will run over transports that can usefully support 830 technology-specific additional parameters (for example, SONET 831 resource usage). Such can be supplied from an external table and 832 referenced from here. 834 A value of zeroDotzero in this attribute indicates that there is 835 no such additional information." 836 DEFVAL { zeroDotZero } 837 ::= { gmplsOutSegmentEntry 3 } 839 gmplsLsrGroups 840 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 842 gmplsLsrCompliances 843 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 845 -- Compliance requirement for fully compliant implementations. 847 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 849 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 850 STATUS current 851 DESCRIPTION 852 "Compliance statement for agents that provide full support for 853 GMPLS-LSR-STD-MIB. 855 The mandatory group has to be implemented by all LSRs that 856 originate, terminate or act as transit for TE-LSPs/tunnels. 857 In addition, depending on the type of tunnels supported, other 858 groups become mandatory as explained below." 860 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 862 MANDATORY-GROUPS { 863 ifGeneralInformationGroup, 864 ifCounterDiscontinuityGroup 865 } 867 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 869 MANDATORY-GROUPS { 870 mplsInterfaceGroup, 871 mplsInSegmentGroup, 872 mplsOutSegmentGroup, 873 mplsXCGroup, 874 mplsPerfGroup, 875 mplsLsrNotificationGroup 876 } 878 MODULE -- this module 880 MANDATORY-GROUPS { 881 gmplsInterfaceGroup, 882 gmplsInSegmentGroup, 883 gmplsOutSegmentGroup 884 } 886 OBJECT gmplsInSegmentDirection 887 SYNTAX GmplsSegmentDirectionTC 888 MIN-ACCESS read-only 889 DESCRIPTION 890 "The only valid value for unidrectional LSPs is forward(1)." 892 OBJECT gmplsOutSegmentDirection 893 SYNTAX GmplsSegmentDirectionTC 894 MIN-ACCESS read-only 895 DESCRIPTION 896 "The only valid value for unidrectional LSPs is forward(1)." 897 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 899 OBJECT gmplsOutSegmentTTLDecrement 900 MIN-ACCESS read-only 901 DESCRIPTION 902 "Write access is not required." 904 OBJECT gmplsInSegmentExtraParamsPtr 905 MIN-ACCESS read-only 906 DESCRIPTION 907 "Write access is not required." 909 OBJECT gmplsOutSegmentExtraParamsPtr 910 MIN-ACCESS read-only 911 DESCRIPTION 912 "Write access is not required." 914 ::= { gmplsLsrCompliances 1 } 916 -- Compliance requirement for implementations that provide read-only 917 -- access. 919 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 920 STATUS current 921 DESCRIPTION 922 "Compliance requirement for implementations that only provide 923 read-only support for GMPLS-LSR-STD-MIB. Such devices can then 924 be monitored but cannot be configured using this MIB modules." 926 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 928 MANDATORY-GROUPS { 929 ifGeneralInformationGroup, 930 ifCounterDiscontinuityGroup 931 } 933 MODULE MPLS-LSR-STD-MIB 935 MANDATORY-GROUPS { 936 mplsInterfaceGroup, 937 mplsInSegmentGroup, 938 mplsOutSegmentGroup, 939 mplsXCGroup, 940 mplsPerfGroup 941 } 943 MODULE -- this module 945 MANDATORY-GROUPS { 946 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 948 gmplsInterfaceGroup, 949 gmplsInSegmentGroup, 950 gmplsOutSegmentGroup 951 } 953 OBJECT gmplsInterfaceSignalingCaps 954 MIN-ACCESS read-only 955 DESCRIPTION 956 "Write access is not required." 958 OBJECT gmplsInterfaceRsvpHelloPeriod 959 MIN-ACCESS read-only 960 DESCRIPTION 961 "Write access is not required." 963 OBJECT gmplsInSegmentDirection 964 SYNTAX GmplsSegmentDirectionTC 965 MIN-ACCESS read-only 966 DESCRIPTION 967 "The only valid value for unidrectional LSPs is forward(1)." 969 OBJECT gmplsInSegmentExtraParamsPtr 970 MIN-ACCESS read-only 971 DESCRIPTION 972 "Write access is not required." 974 OBJECT gmplsOutSegmentDirection 975 MIN-ACCESS read-only 976 DESCRIPTION 977 "The only valid value for unidrectional LSPs is forward(1)." 979 OBJECT gmplsOutSegmentTTLDecrement 980 MIN-ACCESS read-only 981 DESCRIPTION 982 "Write access is not required." 984 OBJECT gmplsOutSegmentExtraParamsPtr 985 MIN-ACCESS read-only 986 DESCRIPTION 987 "Write access is not required." 989 ::= { gmplsLsrCompliances 2 } 991 gmplsInterfaceGroup OBJECT-GROUP 992 OBJECTS { 993 gmplsInterfaceSignalingCaps, 994 gmplsInterfaceRsvpHelloPeriod 995 } 996 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 998 STATUS current 999 DESCRIPTION 1000 "Collection of objects needed for GMPLS interface configuration 1001 and performance information." 1002 ::= { gmplsLsrGroups 1 } 1004 gmplsInSegmentGroup OBJECT-GROUP 1005 OBJECTS { 1006 gmplsInSegmentDirection, 1007 gmplsInSegmentExtraParamsPtr 1008 } 1009 STATUS current 1010 DESCRIPTION 1011 "Collection of objects needed to implement a GMPLS 1012 in-segment." 1013 ::= { gmplsLsrGroups 2 } 1015 gmplsOutSegmentGroup OBJECT-GROUP 1016 OBJECTS { 1017 gmplsOutSegmentDirection, 1018 gmplsOutSegmentTTLDecrement, 1019 gmplsOutSegmentExtraParamsPtr 1020 } 1021 STATUS current 1022 DESCRIPTION 1023 "Collection of objects needed to implement a GMPLS out-segment." 1024 ::= { gmplsLsrGroups 3 } 1025 END 1027 8. GMPLS Label MIB Definitions 1029 This MIB module makes references to the following documents. 1030 [RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811], 1031 [RFC2863], [RFC3289] and [RFC3813]. 1033 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 1035 IMPORTS 1036 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32 1037 FROM SNMPv2-SMI -- RFC2578 1038 MODULE-COMPLIANCE, OBJECT-GROUP 1039 FROM SNMPv2-CONF -- RFC2580 1040 RowStatus, StorageType 1041 FROM SNMPv2-TC -- RFC2579 1042 InterfaceIndexOrZero 1043 FROM IF-MIB -- RFC2863 1044 IndexIntegerNextFree 1045 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1047 FROM DIFFSERV-MIB -- RFC3289 1048 MplsLabel, mplsStdMIB 1049 FROM MPLS-TC-STD-MIB -- RFC3811 1050 GmplsLabelTypeTC, GmplsFreeformLabelTC 1051 FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB 1052 -- RFC-Editor. Please resolve the reference above to GMPLSTCMIB 1053 -- to use the assigned RFC number and remove this note 1054 ; 1056 gmplsLabelStdMIB MODULE-IDENTITY 1057 LAST-UPDATED 1058 "200604060001Z" -- 06 April 2006 00:00:01 GMT 1059 ORGANIZATION 1060 "IETF Common Control And Measurement Plane (CCAMP) Working Group" 1061 CONTACT-INFO 1062 " Thomas D. Nadeau 1063 Cisco Systems, Inc. 1064 Email: tnadeau@cisco.com 1066 Adrian Farrel 1067 Old Dog Consulting 1068 Email: adrian@olddog.co.uk 1070 Comments about this document should be emailed direct to the 1071 CCAMP working group mailing list at ccamp@ops.ietf.org" 1073 DESCRIPTION 1074 "Copyright (C) The Internet Society (2006). This version of 1075 this MIB module is part of RFC XXX; see the RFC itself for 1076 full legal notices. 1077 -- RFC Editor. Please replace XXX above with the correct RFC number and 1078 -- remove this note. 1080 This MIB module contains managed object definitions for labels 1081 within GMPLS systems as defined in: 1082 Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1083 Functional Description, Berger, L. (Editor), RFC 3471, 1084 January 2003." 1086 REVISION 1087 "200604060001Z" -- 06 April 2006 00:00:01 GMT 1088 DESCRIPTION 1089 "Initial version issued as part of RFC XXX." 1090 ::= { mplsStdMIB XXX } 1091 -- RFC Editor. Please replace XXX above with the correct RFC number and 1092 -- remove this note. 1094 -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA 1095 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1097 -- and remove this note 1099 -- no notifications are currently defined. 1101 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 1102 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 1104 gmplsLabelIndexNext OBJECT-TYPE 1105 SYNTAX IndexIntegerNextFree 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "This object contains an unused value for gmplsLabelIndex, 1110 or a zero to indicate that no unused value exists or is 1111 available. 1113 A management application wishing to create a row in the 1114 gmplsLabelTable may read this object and then attempt to 1115 create a row in the table. If row creation fails (because 1116 another application has already created a row with the 1117 supplied index) the management application should read this 1118 object again to get a new index value. 1120 When a row is created in the gmplsLabelTable with the 1121 gmplsLabelIndex value held by this object, an implementation 1122 MUST change the value in this object." 1123 ::= { gmplsLabelObjects 1 } 1125 gmplsLabelTable OBJECT-TYPE 1126 SYNTAX SEQUENCE OF GmplsLabelEntry 1127 MAX-ACCESS not-accessible 1128 STATUS current 1129 DESCRIPTION 1130 "Table of GMPLS Labels. This table allows the representation 1131 of the more complex label forms required for GMPLS which cannot 1132 be held within the textual convention MplsLabel. That is labels 1133 that cannot be encoded within 32 bits. It is, nevertheless also 1134 capable of holding 32 bit labels or regular MPLS labels if 1135 desired. 1137 Each entry in this table represents an individual GMPLS label 1138 value. Labels in the tables in other MIB modules may be referred 1139 to using row pointer into this table. The indexing of this table 1140 provides for arbitrary indexing and also for concatenation of 1141 labels. 1143 For an example of label concatenation see RFC3945 section 7.1. 1144 In essence, a GMPLS label may be composite in order to identify 1145 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1147 a set of resources in the data plane. Practial examples are 1148 timeslots and wavelength sets (which are not contiguous like 1149 wavebands). 1151 The indexing mechanism allows multiple entries in this table to 1152 be seen as a sequence of labels that should be concatenated. 1153 Ordering is potentially very sensitive for concatenation." 1154 REFERENCE 1155 "1. Generalized Multiprotocol Label Switching (GMPLS) 1156 Architecture, RFC 3945, section 7.1," 1157 ::= { gmplsLabelObjects 2 } 1159 gmplsLabelEntry OBJECT-TYPE 1160 SYNTAX GmplsLabelEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "An entry in this table represents a single label value. There 1165 are three indexes into the table. 1166 - The interface index may be helpful to distinguish which 1167 labels are in use on which interfaces or to handle cases 1168 where there are a very large number of labels in use in the 1169 system. When label representation is desired to apply to the 1170 whole system or when it is not important to distinguish 1171 labels by their interfaces, this index MAY be set to zero. 1173 - The label index provides a way of identifying the label. 1174 - The label sub-index is only used for concatenated labels. It 1175 identifies each component label. When non-concatenated labels 1176 are used, this index SHOULD be set to zero. 1177 A storage type object is supplied to control the storage type 1178 for each entry, but implementations should note that the storage 1179 type of conceptual rows in other tables that include row 1180 pointers to an entry in this table SHOULD dictate the storage 1181 type of the rows in this table where the row in the other table 1182 is more persistent." 1184 INDEX { 1185 gmplsLabelInterface, 1186 gmplsLabelIndex, 1187 gmplsLabelSubindex } 1188 ::= { gmplsLabelTable 1 } 1190 GmplsLabelEntry ::= SEQUENCE { 1191 gmplsLabelInterface InterfaceIndexOrZero, 1192 gmplsLabelIndex Unsigned32, 1193 gmplsLabelSubindex Unsigned32, 1194 gmplsLabelType GmplsLabelTypeTC, 1195 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1197 gmplsLabelMplsLabel MplsLabel, 1198 gmplsLabelPortWavelength Unsigned32, 1199 gmplsLabelFreeform GmplsFreeformLabelTC, 1200 gmplsLabelSonetSdhSignalIndex Integer32, 1201 gmplsLabelSdhVc Integer32, 1202 gmplsLabelSdhVcBranch Integer32, 1203 gmplsLabelSonetSdhBranch Integer32, 1204 gmplsLabelSonetSdhGroupBranch Integer32, 1205 gmplsLabelWavebandId Unsigned32, 1206 gmplsLabelWavebandStart Unsigned32, 1207 gmplsLabelWavebandEnd Unsigned32, 1208 gmplsLabelStorageType StorageType, 1209 gmplsLabelRowStatus RowStatus 1210 } 1212 gmplsLabelInterface OBJECT-TYPE 1213 SYNTAX InterfaceIndexOrZero 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "The interface on which this label is used. If this object is set 1218 to zero, the label MUST have applicability across the 1219 whole system and is not limited to a single interface." 1220 ::= { gmplsLabelEntry 1 } 1222 gmplsLabelIndex OBJECT-TYPE 1223 SYNTAX Unsigned32 (0..4294967295) 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "An arbitrary index into the table to identify a label. 1229 Note that implementations that are representing 32 bit labels 1230 within this table MAY choose to align this index with the value 1231 of the label and this may result in the use of the value zero 1232 since it represents a valid label value. Such implementation 1233 should be aware of the implications of sparsely populated 1234 tables. 1236 A management application may read the gmplsLabelIndexNext 1237 object to find a suitable value for this object." 1238 ::= { gmplsLabelEntry 2 } 1240 gmplsLabelSubindex OBJECT-TYPE 1241 SYNTAX Unsigned32 (0..4294967295) 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1247 "In conjunction with gmplsLabelInterface and gmplsLabelIndex, 1248 this object uniquely identifies this row. This sub-index allows 1249 a single GMPLS label to be defined as a concatenation of labels. 1250 This is particularly useful in TDM. 1252 The ordering of sub-labels is strict with the sub-label with 1253 lowest gmplsLabelSubindex appearing first. Note that all 1254 sub-labels of a single GMPLS label must share the same 1255 gmplsLabelInterface and gmplsLabelIndex values. For labels that 1256 are not composed of concatenated sub-labels, this value SHOULD 1257 be set to zero." 1258 ::= { gmplsLabelEntry 3 } 1260 gmplsLabelType OBJECT-TYPE 1261 SYNTAX GmplsLabelTypeTC 1262 MAX-ACCESS read-create 1263 STATUS current 1264 DESCRIPTION 1265 "Identifies the type of this label. Note that this object does 1266 not determine whether MPLS or GMPLS signaling is in use: a value 1267 of gmplsMplsLabel (1) denotes that an MPLS packet label is 1268 present in the gmplsLabelMplsLabel object and encoded using the 1269 MplsLabel textual convention (may be a 20-bit MPLS label, a 10- 1270 or 23-bit Frame Relay label, or an ATM label), but does not 1271 describe whether this is signaled using MPLS or GMPLS. 1273 The value of this object helps determine which of the following 1274 objects are valid. This object cannot be modified if 1275 gmplsLabelRowStatus is active(1)." 1276 REFERENCE 1277 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1278 Functional Description, RFC 3471, section 3." 1279 ::= { gmplsLabelEntry 4 } 1281 gmplsLabelMplsLabel OBJECT-TYPE 1282 SYNTAX MplsLabel 1283 MAX-ACCESS read-create 1284 STATUS current 1285 DESCRIPTION 1286 "The value of an MPLS label (that is a packet label) if this 1287 table is used to store it. This may be used in MPLS systems even 1289 though the label values can be adequately stored in the MPLS MIB 1290 modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Further, in 1291 mixed MPLS and GMPLS systems it may be advantageous to store all 1292 labels in a single label table. Lastly, in GMPLS systems where 1293 packet labels are used (that is in systems that use GMPLS 1294 signaling and GMPLS labels for packet switching) it may be 1295 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1297 desirable to use this table. 1299 This object is only valid if gmplsLabelType is set 1300 to gmplsMplsLabel (1). This object cannot be modified if 1301 gmplsLabelRowStatus is active(1)." 1302 REFERENCE 1303 "1. MPLS Label Stack Encoding, RFC 3032." 1304 DEFVAL { 0 } 1305 ::= { gmplsLabelEntry 5 } 1307 gmplsLabelPortWavelength OBJECT-TYPE 1308 SYNTAX Unsigned32 1309 MAX-ACCESS read-create 1310 STATUS current 1311 DESCRIPTION 1312 "The value of a Port or Wavelength Label when carried as a 1313 Generalized Label. Only valid if gmplsLabelType is set to 1314 gmplsPortWavelengthLabel(2). This object cannot be modified if 1315 gmplsLabelRowStatus is active(1)." 1316 REFERENCE 1317 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1318 Functional Description, RFC 3471, section 3.2.1.1." 1319 DEFVAL { 0 } 1320 ::= { gmplsLabelEntry 6 } 1322 gmplsLabelFreeform OBJECT-TYPE 1323 SYNTAX GmplsFreeformLabelTC 1324 MAX-ACCESS read-create 1325 STATUS current 1326 DESCRIPTION 1327 "The value of a freeform Generalized Label that does not conform 1328 to one of the standardized label encoding or that an 1329 implementation chooses to represent as an octet string without 1330 further decoding. Only valid if gmplsLabelType is set to 1331 gmplsFreeformLabel(3). This object cannot be modified 1332 if gmplsLabelRowStatus is active(1)." 1333 REFERENCE 1334 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1335 Functional Description, RFC 3471, section 3.2." 1336 DEFVAL { '00'h } 1337 ::= { gmplsLabelEntry 7 } 1339 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 1340 SYNTAX Integer32 (0..4095) 1341 MAX-ACCESS read-create 1342 STATUS current 1343 DESCRIPTION 1344 "The Signal Index value (S) of a SONET or SDH Generalized Label. 1346 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1348 Zero indicates that this field is not significant. Only valid if 1349 gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1350 This object cannot be modified if gmplsLabelRowStatus is 1351 active(1)." 1352 REFERENCE 1353 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1354 for Synchronous Optical Network (SONET) and Synchronous 1355 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1356 DEFVAL { 0 } 1357 ::= { gmplsLabelEntry 8 } 1359 gmplsLabelSdhVc OBJECT-TYPE 1360 SYNTAX Integer32 (0..15) 1361 MAX-ACCESS read-create 1362 STATUS current 1363 DESCRIPTION 1364 "The VC Indicator (U) of an SDH Generalized Label. Zero indicates 1365 that this field is non-significant. 1366 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). 1367 This object cannot be modified if gmplsLabelRowStatus is 1368 active(1)." 1369 REFERENCE 1370 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1371 for Synchronous Optical Network (SONET) and Synchronous 1372 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1373 DEFVAL { 0 } 1374 ::= { gmplsLabelEntry 9 } 1376 gmplsLabelSdhVcBranch OBJECT-TYPE 1377 SYNTAX Integer32 (0..15) 1378 MAX-ACCESS read-create 1379 STATUS current 1380 DESCRIPTION 1381 "The VC Branch Indicator (K) of an SDH Generalized Label. Zero 1382 indicates that this field is non-significant. 1383 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This 1384 object cannot be modified if gmplsLabelRowStatus is active(1)." 1385 REFERENCE 1386 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1387 for Synchronous Optical Network (SONET) and Synchronous 1388 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1389 DEFVAL { 0 } 1390 ::= { gmplsLabelEntry 10 } 1392 gmplsLabelSonetSdhBranch OBJECT-TYPE 1393 SYNTAX Integer32 (0..15) 1394 MAX-ACCESS read-create 1395 STATUS current 1396 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1398 DESCRIPTION 1399 "The Branch Indicator (L) of a SONET or SDH Generalized Label. 1400 Zero indicates that this field is non-significant. 1401 Only valid gmplsLabelType is set to gmplsSonetLabel(4) or 1402 gmplsSdhLabel(5). This object cannot be modified if 1403 gmplsLabelRowStatus is active(1)." 1404 REFERENCE 1405 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1406 for Synchronous Optical Network (SONET) and Synchronous 1407 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1408 DEFVAL { 0 } 1409 ::= { gmplsLabelEntry 11 } 1411 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1412 SYNTAX Integer32 (0..15) 1413 MAX-ACCESS read-create 1414 STATUS current 1415 DESCRIPTION 1416 "The Group Branch Indicator (M) of a SONET or SDH Generalized 1417 Label. 1418 Zero indicates that this field is non-significant. 1419 Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or 1420 gmplsSdhLabel(5). This object cannot be modified if 1421 gmplsLabelRowStatus is active(1)." 1422 REFERENCE 1423 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1424 for Synchronous Optical Network (SONET) and Synchronous 1425 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1426 DEFVAL { 0 } 1427 ::= { gmplsLabelEntry 12 } 1429 gmplsLabelWavebandId OBJECT-TYPE 1430 SYNTAX Unsigned32 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "The waveband identifier component of a waveband label. Only 1435 valid if gmplsLabelType is set to gmplsWavebandLabel(6). This 1436 object cannot be modified if gmplsLabelRowStatus is active(1)." 1437 REFERENCE 1438 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1439 Functional Description, RFC 3471, section 3.3." 1440 DEFVAL { 0 } 1441 ::= { gmplsLabelEntry 13 } 1443 gmplsLabelWavebandStart OBJECT-TYPE 1444 SYNTAX Unsigned32 1445 MAX-ACCESS read-create 1446 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1448 STATUS current 1449 DESCRIPTION 1450 "The starting label component of a waveband label. 1451 Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). 1452 This object cannot be modified if 1453 gmplsLabelRowStatus is active(1)." 1454 REFERENCE 1455 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1456 Functional Description, RFC 3471, section 3.3." 1457 DEFVAL { 0 } 1458 ::= { gmplsLabelEntry 14 } 1460 gmplsLabelWavebandEnd OBJECT-TYPE 1461 SYNTAX Unsigned32 1462 MAX-ACCESS read-create 1463 STATUS current 1464 DESCRIPTION 1465 "The end label component of a waveband label. Only valid if 1466 gmplsLabelType is set to gmplsWavebandLabel(6). This object 1467 cannot be modified if gmplsLabelRowStatus is active(1)." 1468 REFERENCE 1469 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1470 Functional Description, RFC 3471, section 3.3." 1471 DEFVAL { 0 } 1472 ::= { gmplsLabelEntry 15 } 1474 gmplsLabelStorageType OBJECT-TYPE 1475 SYNTAX StorageType 1476 MAX-ACCESS read-create 1477 STATUS current 1478 DESCRIPTION 1479 "This variable indicates the storage type for this object. The 1480 agent MUST ensure that this object's value remains consistent 1481 with the storage type of any rows in other tables that contain 1482 pointers to this row. In particular, the storage type of this 1483 row must be at least as permanent as that of any row that point 1484 to it. 1486 Conceptual rows having the value 'permanent' need not 1487 allow write-access to any columnar objects in the row." 1488 REFERENCE 1489 "1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2." 1490 DEFVAL { volatile } 1491 ::= { gmplsLabelEntry 16 } 1493 gmplsLabelRowStatus OBJECT-TYPE 1494 SYNTAX RowStatus 1495 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1497 MAX-ACCESS read-create 1498 STATUS current 1499 DESCRIPTION 1500 "This variable is used to create, modify, and/or delete a row in 1501 this table. When a row in this table has a row in the active(1) 1502 state, no objects in this row can be modified except the 1503 gmplsLabelRowStatus and gmplsLabelStorageType. 1505 The gmplsLabelType object does not have a default and must be 1506 set before a row can become active. The corresponding label 1507 objects (dependent on the value of gmplsLabelType) should also 1508 be set unless they happen to need to use the specified default 1509 values as follows: 1511 gmplsLabelType setting objects to be set 1512 -------------------------------------------------------------- 1513 gmplsMplsLabel(1) gmplsLabelMplsLabel 1515 gmplsPortWavelengthLabel(2) gmplsLabelPortWavelength 1517 gmplsFreeformLabel(3) gmplsLabelFreeform 1519 gmplsSonetLabel(4) gmplsLabelSonetSdhSignalIndex 1520 gmplsLabelSdhVc 1521 gmplsLabelSdhVcBranch 1522 gmplsLabelSonetSdhBranch 1523 gmplsLabelSonetSdhGroupBranch 1525 gmplsSdhLabel(5) gmplsLabelSonetSdhSignalIndex 1526 gmplsLabelSdhVc 1527 gmplsLabelSdhVcBranch 1528 gmplsLabelSonetSdhBranch 1529 gmplsLabelSonetSdhGroupBranch 1531 gmplsWavebandLabel(6) gmplsLabelWavebandId 1532 gmplsLabelWavebandStart 1533 gmplsLabelWavebandEnd" 1534 ::= { gmplsLabelEntry 17 } 1536 gmplsLabelGroups 1537 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1539 gmplsLabelCompliances 1540 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1542 gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE 1543 STATUS current 1544 DESCRIPTION 1545 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1547 "Compliance requirement for implementations that only provide 1548 read-only support for GMPLS-LABEL-STD-MIB. Such devices can then 1549 be monitored but cannot be configured using this MIB module." 1551 MODULE -- this module 1553 -- The mandatory groups have to be implemented by LSRs claiming 1554 -- support for this MIB module. This MIB module is, however, not 1555 -- mandatory for a working implementation of a GMPLS LSR with full 1556 -- MIB support if the GMPLS labels in use can be represented within 1557 -- a 32 bit quantity. 1559 MANDATORY-GROUPS { 1560 gmplsLabelTableGroup 1561 } 1563 GROUP gmplsLabelPacketGroup 1564 DESCRIPTION 1565 "This group extends gmplsLabelTableGroup for implementations that 1566 support packet labels. It is optional for implementations that 1567 do not support packet labels." 1569 GROUP gmplsLabelPortWavelengthGroup 1570 DESCRIPTION 1571 "This group extends gmplsLabelTableGroup for implementations that 1572 support port and wavelength labels. It is optional for 1573 implementations that do not support wavelength labels." 1575 GROUP gmplsLabelFreeformGroup 1576 DESCRIPTION 1577 "This group extends gmplsLabelTableGroup for implementations that 1578 support freeform labels. It is optional for implementations that 1579 do not support freeform labels." 1581 GROUP gmplsLabelSonetSdhGroup 1582 DESCRIPTION 1583 "This group extends gmplsLabelTableGroup for implementations that 1584 support SONET or SDH labels. It is optional for implementations 1585 that do not support SONET or SDH labels." 1587 GROUP gmplsLabelWavebandGroup 1588 DESCRIPTION 1589 "This group extends gmplsLabelTableGroup for implementations that 1590 support Waveband labels. It is optional for implementations that 1591 do not support Waveband labels." 1593 OBJECT gmplsLabelType 1594 MIN-ACCESS read-only 1595 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1597 DESCRIPTION 1598 "Write access is not required." 1600 OBJECT gmplsLabelMplsLabel 1601 MIN-ACCESS read-only 1602 DESCRIPTION 1603 "Write access is not required." 1605 OBJECT gmplsLabelPortWavelength 1606 MIN-ACCESS read-only 1607 DESCRIPTION 1608 "Write access is not required." 1610 OBJECT gmplsLabelFreeform 1611 MIN-ACCESS read-only 1612 DESCRIPTION 1613 "Write access is not required." 1615 OBJECT gmplsLabelSonetSdhSignalIndex 1616 MIN-ACCESS read-only 1617 DESCRIPTION 1618 "Write access is not required." 1620 OBJECT gmplsLabelSdhVc 1621 MIN-ACCESS read-only 1622 DESCRIPTION 1623 "Write access is not required." 1625 OBJECT gmplsLabelSdhVcBranch 1626 MIN-ACCESS read-only 1627 DESCRIPTION 1628 "Write access is not required." 1630 OBJECT gmplsLabelSonetSdhBranch 1631 MIN-ACCESS read-only 1632 DESCRIPTION 1633 "Write access is not required." 1635 OBJECT gmplsLabelSonetSdhGroupBranch 1636 MIN-ACCESS read-only 1637 DESCRIPTION 1638 "Write access is not required." 1640 OBJECT gmplsLabelWavebandId 1641 MIN-ACCESS read-only 1642 DESCRIPTION 1643 "Write access is not required." 1644 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1646 OBJECT gmplsLabelWavebandStart 1647 MIN-ACCESS read-only 1648 DESCRIPTION 1649 "Write access is not required." 1651 OBJECT gmplsLabelWavebandEnd 1652 MIN-ACCESS read-only 1653 DESCRIPTION 1654 "Write access is not required." 1656 OBJECT gmplsLabelStorageType 1657 MIN-ACCESS read-only 1658 DESCRIPTION 1659 "Write access is not required." 1661 OBJECT gmplsLabelRowStatus 1662 SYNTAX RowStatus { active(1) } 1663 MIN-ACCESS read-only 1664 DESCRIPTION 1665 "Support for notInService, createAndWait and notReady is not 1666 required." 1668 ::= { gmplsLabelCompliances 1 } 1670 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1671 STATUS current 1672 DESCRIPTION 1673 "Compliance statement for agents that support the complete 1674 GMPLS-LABEL-STD-MIB module. 1676 The mandatory groups have to be implemented by GMPLS LSRs 1677 claiming support for this MIB module. This MIB module is, 1678 however, not mandatory for a working implementation of a GMPLS 1679 LSR with full MIB support if the GMPLS labels in use can be 1680 represented within a 32 bit quantity." 1682 MODULE -- this module 1684 MANDATORY-GROUPS { 1685 gmplsLabelTableGroup 1686 } 1688 OBJECT gmplsLabelRowStatus 1689 SYNTAX RowStatus { active(1), notInService(2) } 1690 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1691 createAndGo(4), destroy(6) } 1692 DESCRIPTION 1693 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1695 "Support for createAndWait and notReady is not required." 1696 ::= { gmplsLabelCompliances 2 } 1698 gmplsLabelTableGroup OBJECT-GROUP 1699 OBJECTS { 1700 gmplsLabelIndexNext, 1701 gmplsLabelType, 1702 gmplsLabelStorageType, 1703 gmplsLabelRowStatus 1704 } 1706 STATUS current 1707 DESCRIPTION 1708 "Necessary, but not sufficient, set of objects to implement label 1709 table support. In addition, depending on the type of labels 1710 supported (for example, wavelength labels), the following other 1711 groups defined below are mandatory: 1712 gmplsLabelPacketGroup and/or 1713 gmplsLabelPortWavelengthGroup and/or 1714 gmplsLabelFreeformGroup and/or 1715 gmplsLabelSonetSdhGroup." 1716 ::= { gmplsLabelGroups 1 } 1718 gmplsLabelPacketGroup OBJECT-GROUP 1719 OBJECTS { 1720 gmplsLabelMplsLabel 1721 } 1722 STATUS current 1723 DESCRIPTION 1724 "Object needed to implement Packet (MPLS) labels." 1725 ::= { gmplsLabelGroups 2 } 1727 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1728 OBJECTS { 1729 gmplsLabelPortWavelength 1730 } 1731 STATUS current 1732 DESCRIPTION 1733 "Object needed to implement Port and Wavelength labels." 1734 ::= { gmplsLabelGroups 3 } 1736 gmplsLabelFreeformGroup OBJECT-GROUP 1737 OBJECTS { 1738 gmplsLabelFreeform 1739 } 1740 STATUS current 1741 DESCRIPTION 1742 "Object needed to implement Freeform labels." 1743 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1745 ::= { gmplsLabelGroups 4 } 1747 gmplsLabelSonetSdhGroup OBJECT-GROUP 1748 OBJECTS { 1749 gmplsLabelSonetSdhSignalIndex, 1750 gmplsLabelSdhVc, 1751 gmplsLabelSdhVcBranch, 1752 gmplsLabelSonetSdhBranch, 1753 gmplsLabelSonetSdhGroupBranch 1754 } 1755 STATUS current 1756 DESCRIPTION 1757 "Object needed to implement SONET and SDH labels." 1758 ::= { gmplsLabelGroups 5 } 1760 gmplsLabelWavebandGroup OBJECT-GROUP 1761 OBJECTS { 1762 gmplsLabelWavebandId, 1763 gmplsLabelWavebandStart, 1764 gmplsLabelWavebandEnd 1765 } 1766 STATUS current 1767 DESCRIPTION 1768 "Object needed to implement Waveband labels." 1769 ::= { gmplsLabelGroups 6 } 1770 END 1772 9. Security Considerations 1774 It is clear that the MIB modules described in this document in 1775 association with the MPLS-LSR-STD-MIB [RFC3813] are potentially 1776 useful for monitoring of GMPLS LSRs. These MIB modules can also be 1777 used for configuration of certain objects, and anything that can be 1778 configured can be incorrectly configured, with potentially disastrous 1779 results. 1781 There are a number of management objects defined in these MIB modules 1782 with a MAX-ACCESS clause of read-write and/or read-create. Such 1783 objects may be considered sensitive or vulnerable in some network 1784 environments. The support for SET operations in a non-secure 1785 environment without proper protection can have a negative effect on 1786 network operations. These are the tables and objects and their 1787 sensitivity/vulnerability: 1789 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1790 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1792 and gmplsLabelTable collectively contain objects to provision 1793 GMPLS interfaces, LSPs and their associated parameters on a Label 1794 Switching Router (LSR). Unauthorized write access to objects in 1795 these tables, could result in disruption of traffic on the 1796 network. This is especially true if an LSP has already been 1797 established. 1799 Some of the readable objects in these MIB modules (i.e., objects with 1800 a MAX-ACCESS other than not-accessible) may be considered sensitive 1801 or vulnerable in some network environments. It is thus important to 1802 control even GET and/or NOTIFY access to these objects and possibly 1803 to even encrypt the values of these objects when sending them over 1804 the network via SNMP. These are the tables and objects and their 1805 sensitivity/vulnerability: 1807 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1808 and gmplsLabelTable collectively show the LSP network topology and 1809 its capabilities. If an Administrator does not want to reveal this 1810 information, then these tables should be considered 1811 sensitive/vulnerable. 1813 SNMP versions prior to SNMPv3 did not include adequate security. Even 1814 if the network itself is secure (for example by using IPSec), even 1815 then, there is no control as to who on the secure network is allowed 1816 to access and GET/SET (read/change/create/delete) the objects in 1817 these MIB modules. 1819 It is RECOMMENDED that implementers consider the security features as 1820 provided by the SNMPv3 framework (see [RFC3410], section 8), 1821 including full support for the SNMPv3 cryptographic mechanisms (for 1822 authentication and privacy). 1824 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1825 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1826 enable cryptographic security. It is then a customer/operator 1827 responsibility to ensure that the SNMP entity giving access to an 1828 instance of this MIB module, is properly configured to give access to 1829 the objects only to those principals (users) that have legitimate 1830 rights to indeed GET or SET (change/create/delete) them. 1832 10. Acknowledgments 1834 This document is a product of the CCAMP Working Group. 1836 This document extends [RFC3813]. The authors would like to express 1837 their gratitude to all those who worked on that earlier MIB document. 1839 The authors would like to express their thanks to Dan Joyle for his 1840 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 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 -- and remove this note 1886 12. References 1888 12.1. Normative References 1889 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1891 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1892 Requirements Levels", BCP 14, RFC 2119, March 1997. 1894 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1895 J., Rose, M., and S. Waldbusser, "Structure of 1896 Management Information Version 2 (SMIv2)", STD 58, RFC 1897 2578, April 1999. 1899 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1900 J., Rose, M., and S. Waldbusser, "Textual Conventions 1901 for SMIv2", STD 58, RFC 2579, April 1999. 1903 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1904 J., Rose, M., and S. Waldbusser, "Conformance Statements 1905 for SMIv2", STD 58, RFC 2580, April 1999. 1907 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1908 MIB", RFC 2863, June 2000. 1910 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1911 "Multiprotocol Label Switching Architecture", RFC 3031, 1912 January 2001. 1914 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 1915 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 1916 Encoding", RFC 3032, January 2001. 1918 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 1919 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 1920 Tunnels", RFC 3209, December 2001. 1922 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1923 Information Base for the Differentiated Services 1924 Architecture", RFC 3289, May 2002. 1926 [RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL) 1927 Processing in Multi-Protocol Label Switching (MPLS) 1928 Networks", RFC 3443, January 2003. 1930 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 1931 (GMPLS) Signaling Functional Description", RFC 3471, 1932 January 2003. 1934 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 1935 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1936 Engineering (RSVP-TE) Extensions", RFC 3473, January 1937 2003. 1939 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1941 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1942 Conventions and for Multiprotocol Label Switching (MPLS) 1943 Management", RFC 3811, June 2004. 1945 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1946 "Multiprotocol Label Switching (MPLS) Label Switching 1947 (LSR) Router Management Information Base (MIB)", RFC 1948 3813, June 2004. 1950 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 1951 Switching (GMPLS) Architecture", RFC 3945, October 2004. 1953 [RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi- 1954 Protocol Label Switching (GMPLS) Extensions for 1955 Synchronous Optical Network (SONET) and Synchronous 1956 Digital Hierarchy (SDH) Control", RFC 3946, October 1957 2004. 1959 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 1960 Conventions for Multiprotocol Label Switching (MPLS) 1961 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 1962 progress. 1964 [GMPLSTEMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 1965 Label Switching (GMPLS) Traffic Engineering Management 1966 Information Base", draft-ietf-ccamp-gmpls-te-mib, work 1967 in progress. 1969 12.2. Informative References 1971 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1972 "Introduction and Applicability Statements for 1973 Internet-Standard Management Framework", RFC 3410, 1974 December 2002. 1976 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 1977 Multi-Protocol Label Switching (MPLS) Signaling 1978 - Constraint-based Routed Label Distribution Protocol 1979 (CR-LDP) Extensions", RFC 3472, January 2003. 1981 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1982 "Multiprotocol Label Switching (MPLS) Traffic 1983 Engineering (TE) Management Information Base (MIB)", 1984 RFC 3812, June 2004. 1986 13. Contact Information 1988 Thomas D. Nadeau 1989 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 1991 Cisco Systems, Inc. 1992 1414 Massachusetts Ave. 1993 Boxborough, MA 01719 1994 Email: tnadeau@cisco.com 1996 Adrian Farrel 1997 Old Dog Consulting 1998 Phone: +44-(0)-1978-860944 1999 Email: adrian@olddog.co.uk 2001 Cheenu Srinivasan 2002 Bloomberg L.P. 2003 731 Lexington Ave. 2004 New York, NY 10022 2005 Phone: +1-212-617-3682 2006 Email: cheenu@bloomberg.net 2008 Tim Hall 2009 Data Connection Ltd. 2010 100 Church Street 2011 Enfield, Middlesex, EN2 6BQ, UK 2012 Phone: +44 20 8366 1177 2013 Email: tim.hall@dataconnection.com 2015 Ed Harrison 2016 Data Connection Ltd. 2017 100 Church Street 2018 Enfield, Middlesex, EN2 6BQ, UK 2019 Phone: +44 20 8366 1177 2020 Email: ed.harrison@dataconnection.com 2022 14. Intellectual Property Considerations 2023 draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006 2025 The IETF takes no position regarding the validity or scope of any 2026 Intellectual Property Rights or other rights that might be claimed to 2027 pertain to the implementation or use of the technology described in 2028 this document or the extent to which any license under such rights 2029 might or might not be available; nor does it represent that it has 2030 made any independent effort to identify any such rights. Information 2031 on the procedures with respect to rights in RFC documents can be 2032 found in BCP 78 and BCP 79. 2034 Copies of IPR disclosures made to the IETF Secretariat and any 2035 assurances of licenses to be made available, or the result of an 2036 attempt made to obtain a general license or permission for the use of 2037 such proprietary rights by implementers or users of this 2038 specification can be obtained from the IETF on-line IPR repository at 2039 http://www.ietf.org/ipr. 2041 The IETF invites any interested party to bring to its attention any 2042 copyrights, patents or patent applications, or other proprietary 2043 rights that may cover technology that may be required to implement 2044 this standard. Please address the information to the IETF at ietf- 2045 ipr@ietf.org. 2047 15. Full Copyright Statement 2049 Copyright (C) The Internet Society (2006). This document is subject 2050 to the rights, licenses and restrictions contained in BCP 78, and 2051 except as set forth therein, the authors retain all their rights. 2053 This document and the information contained herein are provided on an 2054 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2055 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2056 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2057 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2058 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2059 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.