idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 33 longer pages, the longest (page 30) being 79 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 33 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 14 instances of too long lines in the document, the longest one being 6 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2003) is 7462 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2863' is defined on line 1651, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 1659, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 1691, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1702, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 1707, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 1720, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 1725, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 1728, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 1732, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 1736, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSonetSDH' == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-03 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-03 -- Duplicate reference: draft-ietf-ccamp-gmpls-te-mib, mentioned in 'GMPLSTEMIB', was also mentioned in 'GMPLSTCMIB'. -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 3 errors (**), 0 flaws (~~), 17 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: May 2004 4 Cheenu Srinivasan 5 Bloomberg L.P. 7 Adrian Farrel 8 Old Dog Consulting 10 Tim Hall 11 Ed Harrison 12 Data Connection Ltd. 14 November 2003 16 Generalized Multiprotocol Label Switching (GMPLS) 17 Label Switching Router (LSR) Management Information Base 19 draft-ietf-ccamp-gmpls-lsr-mib-03.txt 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance with 24 all provisions of Section 10 of RFC 2026. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six 32 months and may be updated, replaced, or obsoleted by other documents 33 at any time. It is inappropriate to use Internet-Drafts as 34 reference material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt. 39 Abstract 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it describes managed objects to configure and/or 44 monitor a Generalized Multiprotocol Label Switching (GMPLS) Label 45 Switching Router (LSRs). 47 Table of Contents 49 1. Introduction 2 50 1.1. Migration Strategy 2 51 2. Terminology 3 52 3. The SNMP Management Framework 3 53 4. Outline 3 54 4.1. Summary of the GMPLS LSR MIB Module 4 55 5. Bidirectional LSPs 4 56 6. Example of LSP Setup 5 57 7. GMPLS Label Switching Router MIB Definitions 6 58 8. GMPLS Label MIB Definitions 14 59 9. Security Considerations 25 60 10. Acknowledgments 26 61 11. IANA Considerations 27 62 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 27 63 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB 27 64 12. References 27 65 12.1. Normative References 27 66 12.2. Informational References 28 67 13. Authors' Addresses 29 68 14. Full Copyright Statement 30 69 15. Intellectual Property Notice 30 70 16. Changes and Pending Work 31 71 16.1. Pending Work 31 73 1. Introduction 75 This memo defines a portion of the Management Information Base (MIB) 76 for use with network management protocols in the Internet community. 77 In particular, it describes managed objects for modeling a 78 Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label 79 Switching Router (LSR). 81 Comments should be made directly to the CCAMP mailing list at 82 ccamp@ops.ietf.org. 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in RFC 2119, reference 87 [RFC2119]. 89 1.1. Migration Strategy 91 This MIB module extends the Label Switching Router MIB module defined 92 for use with MPLS [LSRMIB]. The only changes made are additions for 93 support of GMPLS or changes that are necessary to support the 94 increased complexity of a GMPLS system. 96 The companion document modeling and managing GMPLS based traffic 97 engineering [GMPLSTEMIB] extends the MPLS TE MIB module [TEMIB] with 98 the same intentions. 100 Textual conventions and OBJECT-IDENTIFIERS are defined in 101 [GMPLSTCMIB] which extends the set of textual conventions originally 102 defined in [TCMIB]. 104 2. Terminology 106 This document uses terminology from the document describing the MPLS 107 architecture [RFC3031] and the GMPLS architecture [GMPLSArch]. 109 A label switched path (LSP) is modeled as a connection consisting of 110 one or more incoming segments (in-segments) and/or one or more 111 outgoing segments (out-segments) at an LSR. The association or 112 interconnection of the in-segments and out-segments is accomplished 113 by using a cross-connect. We use the terminology "connection" and 114 "LSP" interchangeably where the meaning is clear from the context. 116 in-segment This is analogous to a GMPLS label on an interface. 117 out-segment This is analogous to a GMPLS label on an interface. 118 cross-connect This describes the conceptual connection between a 119 set of in-segments and out-segments. 120 Note that either set may be 0; that is, a cross- 121 connect may connect only out-segments together with 122 no in-segments in the case where an LSP is 123 originating on an LSR. 125 3. The SNMP Management Framework 127 For a detailed overview of the documents that describe the current 128 Internet-Standard Management Framework, please refer to section 7 of 129 RFC 3410 [RFC3410]. 131 Managed objects are accessed via a virtual information store, termed 132 the Management Information Base or MIB. MIB objects are generally 133 accessed through the Simple Network Management Protocol (SNMP). 134 Objects in the MIB are defined using the mechanisms defined in the 135 Structure of Management Information (SMI). This memo specifies a 136 MIB module that is compliant to the SMIv2, which is described in STD 137 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 138 2580 [RFC2580]. 140 4. Outline 142 Configuring statically provisioned GMPLS LSPs through an LSR involves 143 the following steps: 145 - Configuring an interface using the MPLS LSR MIB module. 147 - Enabling GMPLS on GMPLS capable interfaces using this MIB module. 149 - Configuring in-segments and out-segments using the MPLS LSR MIB 150 module. 152 - Configuring GMPLS extensions to the in-segments and out-segments 153 using this MIB module. 155 - Setting up the cross-connect table in the MPLS LSR MIB module to 156 associate segments and/or to indicate connection origination and 157 termination. 159 - Optionally setting up labels in the label table in this MIB module 160 if the textual convention 161 MplsLabel is not capable of holding the required label (for 162 example, if the label requires more than 32 bits to encode it), or 163 if the operator wishes to disambiguate GMPLS label types. 165 - Optionally specifying label stack actions in the MPLS LSR MIB 166 module. 168 - Optionally specifying segment traffic parameters in the MPLS LSR 169 MIB module. 171 4.1. Summary of the GMPLS LSR MIB Module 173 The MIB tables in this MIB module are as follows. 175 - The interface configuration table (gmplsInterfaceTable), which 176 extends mplsInterfaceTable to enable the GMPLS protocol on MPLS- 177 capable interfaces. 179 - The in-segment (gmplsInSegmentTable) and out-segment 180 (gmplsOutSegmentTable) tables extend mplsInSegmentTable and 181 mplsOutSegmentTable to configuring GMPLS-specific parameters for 182 LSP segments at an LSR. 184 - The gmplsLabelTable extends mplsLabelTable and allows Generalized 185 Labels to be defined and managed in a central location. 186 Generalized Labels can be of variable length and have distinct 187 bit-by-bit interpretations according to the use that is made of 188 them. 190 These tables are described in the subsequent sections. 192 5. Bidirectional LSPs 194 This MIB supports bidirectional LSPs as required for GMPLS. 195 A single value of mplsXCIndex is shared by all of the segments for 196 the entire bidirectional LSP. This facilitates a simple reference 197 from [TEMIB] and [GMPLSTEMIB], and makes fate-sharing more obvious. 199 It is, however, important that the direction of segments is 200 understood to avoid connecting all in-segments to all out-segments. 201 This is achieved by an object in each segment that indicates the 202 direction of the segment with respect to data flow. 204 A segment that is marked as 'forward' carries data from the 'head' of 205 the LSP to the 'tail'. A segment marked as 'reverse' carries data in 206 the reverse direction. 208 Where an LSP is signaled using a conventional signaling protocol, the 209 'head' of the LSP is the source of the signaling (also known as the 210 ingress) and the 'tail' is the destination (also known as the 211 egress). For manually configured LSPs an arbitrary decision must be 212 made about which segments are 'forward' and which 'reverse'. For 213 consistency this decision should be made across all LSRs that 214 participate in the LSP by assigning 'head' and 'tail' ends to the 215 LSP. 217 6. Example of LSP Setup 219 In this section we provide a brief example of using the MIB objects 220 described in section 9 to set up an LSP. While this example is not 221 meant to illustrate every nuance of the MIB, it is intended as an aid 222 to understanding some of the key concepts. It is meant to be read 223 after going through the MIB itself. A prerequisite is an 224 understanding of [LSRMIB]. 226 Suppose that one would like to manually create a best-effort, bi- 227 directional LSP. Assume that, in the forward direction, the LSP 228 enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR 229 via MPLS interface B with ifIndex 13. For the reverse direction, we 230 assume the LSP enters via interface B and leaves via interface A 231 (i.e. the forward and reverse directions use the same bi-directional 232 interfaces). Let us also assume that we do not wish to have a label 233 stack beneath the top label on the outgoing labeled packets. The 234 following example illustrates which rows and corresponding objects 235 might be created to accomplish this. 237 We must first create rows in the gmplsLabelTable corresponding to the 238 labels required for each of the forward and reverse direction in- and out- 239 segments. For the purpose of this example the forward and reverse labels 240 on each interface will be the same, hence we need to create just two 241 rows in the gmplsLabelTable - one for each interface. 243 In gmplsLabelTable: 244 { 245 gmplsLabelInterface = 12, 246 gmplsLabelIndex = 1, 247 gmplsLabelSubindex = 1, 248 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 249 gmplsLabelMplsLabel = 0, 250 gmplsLabelPortWavelength = 0, 251 gmplsLabelFreeformLength = 8, 252 gmplsLabelFreeform = 0x123456789ABCDEF0 253 gmplsLabelSonetSdhSignalIndex = 0, 254 gmplsLabelSdhVc = 0, 255 gmplsLabelSdhVcBranch = 0, 256 gmplsLabelSonetSdhBranch = 0, 257 gmplsLabelSonetSdhGroupBranch = 0, 258 gmplsLabelWavebandId = 0, 259 gmplsLabelWavebandStartLabel = 0, 260 gmplsLabelWavebandEndLabel = 0, 261 gmplsLabelRowStatus = createAndGo(4), 262 gmplsLabelStorageType = 0 263 } 264 In gmplsLabelTable: 265 { 266 gmplsLabelInterface = 13, 267 gmplsLabelIndex = 1, 268 gmplsLabelSubindex = 1, 269 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 270 gmplsLabelMplsLabel = 0, 271 gmplsLabelPortWavelength = 0, 272 gmplsLabelFreeformLength = 8, 273 gmplsLabelFreeform = 0xFEDCBA9876543210 274 gmplsLabelSonetSdhSignalIndex = 0, 275 gmplsLabelSdhVc = 0, 276 gmplsLabelSdhVcBranch = 0, 277 gmplsLabelSonetSdhBranch = 0, 278 gmplsLabelSonetSdhGroupBranch = 0, 279 gmplsLabelWavebandId = 0, 280 gmplsLabelWavebandStartLabel = 0, 281 gmplsLabelWavebandEndLabel = 0, 282 gmplsLabelRowStatus = createAndGo(4), 283 gmplsLabelStorageType = 0 284 } 286 We must next create the appropriate in-segment and out-segment entries. 287 These are done in [LSRMIB] using the mplsInSegmentTable and 288 mplsOutSegmentTable. Note that we use a row pointer to the two rows in the 289 gmplsLableTable rather than specifying the labels explicitly in the 290 in- and out-segment tables. Also note that the row status for each row 291 is set to createAndWait(5) to allow corresponding entries in the 292 gmplsInSegmentTable and gmplsOutSegmentTable to be created. 294 For the forward direction. 296 In mplsInSegmentTable: 297 { 298 mplsInSegmentIndex = 0x00000015 299 mplsInSegmentLabel = 0, -- incoming label in label table 300 mplsInSegmentNPop = 1, 301 mplsInSegmentInterface = 12, -- incoming interface 303 -- RowPointer MUST point to the first accesible column. 304 mplsInSegmentLabelPtr = gmplsLabelInterface.1, 305 mplsInSegmentTrafficParamPtr = 0.0, 306 mplsInSegmentRowStatus = createAndWait(5) 307 } 309 In mplsOutSegmentTable: 310 { 311 mplsOutSegmentIndex = 0x00000012, 312 mplsOutSegmentInterface = 13, -- outgoing interface 313 mplsOutSegmentPushTopLabel = true(1), 314 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 316 -- RowPointer MUST point to the first accesible column. 317 mplsOutSegmentTrafficParamPtr = 0.0, 318 mplsOutSegmentLabelPtr = gmplsLabelInterface.2, 319 mplsOutSegmentRowStatus = createAndWait(5) 320 } 321 For the reverse direction. 323 In mplsInSegmentTable: 324 { 325 mplsInSegmentIndex = 0x00000016 327 mplsInSegmentLabel = 0, -- incoming label in label table 328 mplsInSegmentNPop = 1, 329 mplsInSegmentInterface = 13, -- incoming interface 331 -- RowPointer MUST point to the first accesible column. 332 mplsInSegmentLabelPtr = gmplsLabelInterface.2, 333 mplsInSegmentTrafficParamPtr = 0.0, 335 mplsInSegmentRowStatus = createAndWait(5) 336 } 338 In mplsOutSegmentTable: 339 { 340 mplsOutSegmentIndex = 0x00000013, 341 mplsOutSegmentInterface = 12, -- outgoing interface 342 mplsOutSegmentPushTopLabel = true(1), 343 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 345 -- RowPointer MUST point to the first accesible column. 346 mplsOutSegmentTrafficParamPtr = 0.0, 347 mplsOutSegmentLabelPtr = gmplsLabelInterface.1, 349 mplsOutSegmentRowStatus = createAndWait(5) 350 } 352 These table entries are extended by entries in gmplsInSegmentTable 353 and gmplsOutSegmentTable. Note that the nature of the 'extends' 354 relationship is that the entry in gmplsInSegmentTable has the same 355 index values as the entry in mplsInSegmentTable. Similarly, the entry 356 in gmplsOutSegmentTable has the same index values as the entry in 357 mplsOutSegmentTable. 359 First for the forward direction: 361 In gmplsInSegmentTable(0x00000015) 362 { 363 gmplsInSegmentDirection = forward (1) 364 } 365 In gmplsOutSegmentTable(0x00000012) 366 { 367 gmplsOutSegmentDirection = forward (1), 368 gmplsOutSegmentTTLDecrement = 1 369 } 371 Next for the reverse direction: 373 In gmplsInSegmentTable(0x00000016) 374 { 375 gmplsInSegmentDirection = reverse (2) 376 } 377 In gmplsOutSegmentTable(0x00000013) 378 { 379 gmplsOutSegmentDirection = reverse (2), 380 gmplsOutSegmentTTLDecrement = 1 381 } 383 Next, two cross-connect entries are created in the mplsXCTable of the 384 MPLS LSR MIB, thereby associating the newly created segments 385 together. 387 In mplsXCTable: 388 { 389 mplsXCIndex = 0x01, 390 mplsXCInSegmentIndex = 0x00000015, 391 mplsXCOutSegmentIndex = 0x00000012, 393 mplsXCLspId = 0x0102 -- unique ID 394 mplsXCLabelStackIndex = 0x00, -- only a single 395 -- outgoing label 396 mplsXCRowStatus = createAndGo(4) 397 } 399 In mplsXCTable: 400 { 401 mplsXCIndex = 0x02, 402 mplsXCInSegmentIndex = 0x00000016, 403 mplsXCOutSegmentIndex = 0x00000013, 405 mplsXCLspId = 0x0102 -- unique ID 406 mplsXCLabelStackIndex = 0x00, -- only a single 407 -- outgoing label 408 mplsXCRowStatus = createAndGo(4) 409 } 411 Finally, the in-segments and out-segments are activated. 413 In mplsInSegmentTable(0x00000015): 414 { 415 mplsInSegmentRowStatus = active(1) 416 } 418 In mplsInSegmentTable(0x00000016): 419 { 420 mplsInSegmentRowStatus = active(1) 421 } 423 In mplsOutSegmentTable(0x00000012): 424 { 425 mplsOutSegmentRowStatus = active(1) 426 } 428 In mplsOutSegmentTable(0x00000013): 429 { 430 mplsOutSegmentRowStatus = active(1) 431 } 433 7. GMPLS Label Switching Router MIB Definitions 435 GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN 437 IMPORTS 438 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32 439 FROM SNMPv2-SMI 440 MODULE-COMPLIANCE, OBJECT-GROUP 441 FROM SNMPv2-CONF 442 GmplsSegmentDirection, gmplsStdMIB 443 FROM GMPLS-TC-STD-MIB 444 mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex 445 FROM MPLS-LSR-STD-MIB 446 ; 448 gmplsLsrStdMIB MODULE-IDENTITY 449 LAST-UPDATED 450 "200310300900Z" -- 30 October 2003 9:00:00 GMT" 451 ORGANIZATION 452 "Common Control And Management Protocols (CCAMP) 453 Working Group" 454 CONTACT-INFO 455 " Thomas D. Nadeau 456 Cisco Systems, Inc. 457 Email: tnadeau@cisco.com 459 Cheenu Srinivasan 460 Bloomberg L.P. 461 Email: cheenu@bloomberg.net 463 Adrian Farrel 464 Old Dog Consulting 465 Email: adrian@olddog.co.uk 467 Ed Harrison 468 Data Connection Ltd. 469 Email: ed.harrison@dataconnection.com 471 Tim Hall 472 Data Connection Ltd. 473 Email: timhall@dataconnection.com 475 Comments about this document should be emailed direct to the 476 CCAMP working group mailing list at ccamp@ops.ietf.org" 477 DESCRIPTION 478 "This MIB module contains managed object definitions 479 for the Generalized Multiprotocol Label Switching 480 (GMPLS) Router as defined in: Ashwood-Smith et al., 481 Generalized Multiprotocol Label Switching (GMPLS) 482 Architecture, Internet Draft , March 2001, work in progress. 485 Copyright (C) The Internet Society (2003). This 486 version of this MIB module is part of RFCXXX; see 487 the RFC itself for full legal notices." 489 -- Revision history. 490 REVISION 491 "200310300900Z" -- 30 October 2003 09:00:00 GMT 493 DESCRIPTION 494 "Initial revision, published as part of RFC XXXX." 495 ::= { gmplsStdMIB xx } 497 -- Top level components of this MIB module. 499 -- Notifications 500 -- no notifications are currently defined. 501 gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 } 503 -- Tables, Scalars 504 gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } 506 -- Conformance 507 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } 509 -- GMPLS Interface Table. 511 gmplsInterfaceTable OBJECT-TYPE 512 SYNTAX SEQUENCE OF GmplsInterfaceEntry 513 MAX-ACCESS not-accessible 514 STATUS current 515 DESCRIPTION 516 "This table specifies per-interface GMPLS capability 517 and associated information. It extends the 518 information in mplsInterfaceTable." 519 ::= { gmplsLsrObjects 1 } 521 gmplsInterfaceEntry OBJECT-TYPE 522 SYNTAX GmplsInterfaceEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 "A conceptual row in this table is created 527 automatically by an LSR for every interface capable 528 of supporting GMPLS and which is configured to do 529 so. A conceptual row in this table will exist if and 530 only if a corresponding entry in mplsInterfaceTable 531 exists, and a corresponding entry in ifTable exists 532 with ifType = mpls(166). If the associated entry in 533 ifTable is operationally disabled (thus removing the 534 GMPLS capabilities on the interface) or the entry in 535 mplsInterfaceTable is deleted, the corresponding 536 entry in this table MUST be deleted shortly 537 thereafter. 539 The indexing is the same as that for mplsInterfaceTable. 540 Thus, the entry with index 0 represents the per-platform 541 label space and contains parameters that apply to all 542 interfaces that participate in the per-platform label space." 543 INDEX { mplsInterfaceIndex } 544 ::= { gmplsInterfaceTable 1 } 545 GmplsInterfaceEntry ::= SEQUENCE { 546 gmplsInterfaceSignalingCaps BITS 547 } 549 gmplsInterfaceSignalingCaps OBJECT-TYPE 550 SYNTAX BITS { 551 unknown (0), 552 rsvpGmpls (1), 553 crldpGmpls (2), -- note the use of CR-LDP is deprecated 554 otherGmpls (3) 555 } 556 MAX-ACCESS read-create 557 STATUS current 558 DESCRIPTION 559 "Defines the signaling capabilities on this 560 interface. Multiple bits may legitimately be set at 561 once. Setting no bits implies that GMPLS signaling 562 cannot be performed on this interface and all LSPs 563 must be manually provisioned." 564 ::= { gmplsInterfaceEntry 1 } 566 -- End of gmplsInterfaceTable 568 -- In-segment table. 570 gmplsInSegmentTable OBJECT-TYPE 571 SYNTAX SEQUENCE OF GmplsInSegmentEntry 572 MAX-ACCESS not-accessible 573 STATUS current 574 DESCRIPTION 575 "This table extends the mplsInSegmentTable to provide 576 GMPLS-specific information about incoming segments 577 to an LSR." 578 ::= { gmplsLsrObjects 2 } 580 gmplsInSegmentEntry OBJECT-TYPE 581 SYNTAX GmplsInSegmentEntry 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "An entry in this table extends the representation of 586 an incoming segment represented by an entry in 587 mplsInSegmentTable. An entry can be created by a 588 network administrator or an SNMP agent, or a GMPLS 589 signaling protocol. 591 Note that the storage type for this entry SHOULD be 592 inherited from the corresponding entry in the 593 mplsInSegmentTable given by the value of the 594 mplsInSegmentStorageType object." 595 INDEX { mplsInSegmentIndex } 596 ::= { gmplsInSegmentTable 1 } 598 GmplsInSegmentEntry ::= SEQUENCE { 599 gmplsInSegmentDirection GmplsSegmentDirection 600 } 601 gmplsInSegmentDirection OBJECT-TYPE 602 SYNTAX GmplsSegmentDirection 603 MAX-ACCESS read-create 604 STATUS current 605 DESCRIPTION 606 "This object indicates the direction of data flow on 607 this segment. This object cannot be modified if 608 mplsInSegmentRowStatus for the associated entry in 609 the mplsInSegmentTable is active(1)." 610 DEFVAL { forward } 611 ::= { gmplsInSegmentEntry 1 } 613 -- End of gmplsInSegmentTable 615 -- Out-segment table. 617 gmplsOutSegmentTable OBJECT-TYPE 618 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "This table extends the mplsOutSegmentTable to 623 provide GMPLS-specific information about outgoing 624 segments from an LSR." 625 ::= { gmplsLsrObjects 3 } 627 gmplsOutSegmentEntry OBJECT-TYPE 628 SYNTAX GmplsOutSegmentEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "An entry in this table extends the representation of 633 an outgoing segment represented by an entry in 634 mplsOutSegmentTable. An entry can be created by a 635 network administrator or an SNMP agent, or a GMPLS 636 signaling protocol. 637 Note that the storage type for this entry SHOULD be 638 inherited from the corresponding entry in the 639 mplsOutSegmentTable given by the value of the 640 mplsOutSegmentStorageType object." 641 INDEX { mplsOutSegmentIndex } 642 ::= { gmplsOutSegmentTable 1 } 644 GmplsOutSegmentEntry ::= SEQUENCE { 645 gmplsOutSegmentDirection GmplsSegmentDirection, 646 gmplsOutSegmentTTLDecrement Unsigned32 647 } 649 gmplsOutSegmentDirection OBJECT-TYPE 650 SYNTAX GmplsSegmentDirection 651 MAX-ACCESS read-create 652 STATUS current 653 DESCRIPTION 654 "This object indicates the direction of data flow on 655 this segment. This object cannot be modified if 656 mplsOutSegmentRowStatus for the associated entry in 657 the mplsOutSegmentTable is active(1)." 659 DEFVAL { forward } 660 ::= { gmplsOutSegmentEntry 1 } 662 gmplsOutSegmentTTLDecrement OBJECT-TYPE 663 SYNTAX Unsigned32 (0..255) 664 MAX-ACCESS read-create 665 STATUS current 666 DESCRIPTION 667 "This object indicates the amount by which to 668 decrement the TTL of any payload packets forwarded 669 on this segment if per-hop decrementing is being 670 done. 672 A value of zero indicates that no decrement should 673 be made or that per-hop decrementing is not in 674 force. 676 See the gmplsTunnelTTLDecrement object in the 677 gmplsTunnelTable of [GMPLSTEMIB] for a value by 678 which to decrement the TTL for the whole of a 679 tunnel. 681 This object cannot be modified if 682 mplsOutSegmentRowStatus for the associated entry in 683 the mplsOutSegmentTable is active(1)." 684 DEFVAL { 0 } 685 ::= { gmplsOutSegmentEntry 2 } 687 -- End of gmplsOutSegmentTable 689 -- Module compliance. 691 gmplsLsrGroups 692 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 694 gmplsLsrCompliances 695 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 697 -- Compliance requirement for fully compliant implementations. 699 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 700 STATUS current 701 DESCRIPTION 702 "Compliance statement for agents that provide full 703 support for GMPLS-LSR-STD-MIB." 705 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 707 MANDATORY-GROUPS { 708 ifGeneralInformationGroup, 709 ifCounterDiscontinuityGroup 710 } 711 MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB 713 MANDATORY-GROUPS { 714 mplsInterfaceGroup, 715 mplsInSegmentGroup, 716 mplsOutSegmentGroup, 717 mplsXCGroup, 718 mplsPerfGroup, 719 mplsLsrNotificationGroup 720 } 722 MODULE -- this module 724 MANDATORY-GROUPS { 725 gmplsInterfaceGroup, 726 gmplsInSegmentGroup, 727 gmplsOutSegmentGroup 728 } 730 -- gmplsInSegmentTable 732 OBJECT gmplsInSegmentDirection 733 SYNTAX GmplsSegmentDirection 734 MIN-ACCESS read-write 735 DESCRIPTION 736 "Only forward(1) needs to be supported by 737 implementations that only support unidirectional 738 LSPs." 740 -- gmplsOutSegmentTable 742 OBJECT gmplsOutSegmentDirection 743 SYNTAX GmplsSegmentDirection 744 MIN-ACCESS read-write 745 DESCRIPTION 746 "Only forward(1) needs to be supported by 747 implementations that only support unidirectional 748 LSPs." 750 OBJECT gmplsOutSegmentTTLDecrement 751 SYNTAX Unsigned32 (0..255) 752 MIN-ACCESS read-only 753 DESCRIPTION 754 "Write access is not required." 756 ::= { gmplsLsrCompliances 1 } 758 -- Compliance requirement for implementations that provide read-only 759 -- access. 761 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 762 STATUS current 763 DESCRIPTION 764 "Compliance requirement for implementations that only 765 provide read-only support for GMPLS-LSR-STD-MIB. Such 766 devices can then be monitored but cannot be configured 767 using this MIB modules." 769 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 771 MANDATORY-GROUPS { 772 ifGeneralInformationGroup, 773 ifCounterDiscontinuityGroup 774 } 776 MODULE MPLS-LSR-STD-MIB 778 MANDATORY-GROUPS { 779 mplsInterfaceGroup, 780 mplsInSegmentGroup, 781 mplsOutSegmentGroup, 782 mplsXCGroup, 783 mplsPerfGroup 784 } 786 MODULE -- this module 788 MANDATORY-GROUPS { 789 gmplsInterfaceGroup, 790 gmplsInSegmentGroup, 791 gmplsOutSegmentGroup 792 } 794 -- gmplsInterfaceGroup 796 OBJECT gmplsInterfaceSignalingCaps 797 SYNTAX BITS { 798 unknown (0), 799 rsvpGmpls (1), 800 crldpGmpls (2), 801 otherGmpls (3) 802 } 803 MIN-ACCESS read-only 804 DESCRIPTION 805 "Write access is not required." 807 -- gmplsInSegmentTable 809 OBJECT gmplsInSegmentDirection 810 SYNTAX GmplsSegmentDirection 811 MIN-ACCESS read-only 812 DESCRIPTION 813 "Write access is not required. Only forward(1) needs 814 to be supported by implementations that only support 815 unidirectional LSPs." 817 -- gmplsOutSegmentTable 819 OBJECT gmplsOutSegmentDirection 820 SYNTAX GmplsSegmentDirection 821 MIN-ACCESS read-only 822 DESCRIPTION 823 "Write access is not required. Only forward(1) needs 824 to be supported by implementations that only support 825 unidirectional LSPs." 827 OBJECT gmplsOutSegmentTTLDecrement 828 SYNTAX Unsigned32 (0..255) 829 MIN-ACCESS read-only 830 DESCRIPTION 831 "Write access is not required." 833 ::= { gmplsLsrCompliances 2 } 835 -- Units of conformance. 837 gmplsInterfaceGroup OBJECT-GROUP 838 OBJECTS { 839 gmplsInterfaceSignalingCaps 840 } 841 STATUS current 842 DESCRIPTION 843 "Collection of objects needed for GMPLS interface 844 configuration and performance information." 845 ::= { gmplsLsrGroups 1 } 847 gmplsInSegmentGroup OBJECT-GROUP 848 OBJECTS { 849 gmplsInSegmentDirection 850 } 851 STATUS current 852 DESCRIPTION 853 "Collection of objects needed to implement a GMPLS 854 in-segment." 855 ::= { gmplsLsrGroups 2 } 857 gmplsOutSegmentGroup OBJECT-GROUP 858 OBJECTS { 859 gmplsOutSegmentDirection, 860 gmplsOutSegmentTTLDecrement 861 } 862 STATUS current 863 DESCRIPTION 864 "Collection of objects needed to implement a GMPLS 865 out-segment." 866 ::= { gmplsLsrGroups 3 } 868 END 870 8. GMPLS Label MIB Definitions 872 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 874 IMPORTS 875 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, 876 Integer32 877 FROM SNMPv2-SMI 878 MODULE-COMPLIANCE, OBJECT-GROUP 879 FROM SNMPv2-CONF 880 RowStatus, StorageType 881 FROM SNMPv2-TC 883 InterfaceIndexOrZero 884 FROM IF-MIB 885 IndexIntegerNextFree 886 FROM DIFFSERV-MIB 887 MplsLabel 888 FROM MPLS-TC-STD-MIB 889 GmplsGeneralizedLabelTypes, GmplsFreeformLabel, 890 gmplsStdMIB 891 FROM GMPLS-TC-STD-MIB 892 ; 894 gmplsLabelStdMIB MODULE-IDENTITY 895 LAST-UPDATED 896 "200310300900Z" -- 30 October 2003 9:00:00 GMT" 897 ORGANIZATION 898 "Common Control And Management Protocols (CCAMP) 899 Working Group" 900 CONTACT-INFO 901 " Thomas D. Nadeau 902 Cisco Systems, Inc. 903 Email: tnadeau@cisco.com 905 Cheenu Srinivasan 906 Bloomberg L.P. 907 Email: cheenu@bloomberg.net 909 Adrian Farrel 910 Old Dog Consulting 911 Email: adrian@olddog.co.uk 913 Ed Harrison 914 Data Connection Ltd. 915 Email: ed.harrison@dataconnection.com 917 Tim Hall 918 Data Connection Ltd. 919 Email: timhall@dataconnection.com 921 Comments about this document should be emailed direct to the 922 CCAMP working group mailing list at ccamp@ops.ietf.org" 923 DESCRIPTION 924 "This MIB module contains managed object definitions 925 for labels within GMPLS systems." 927 -- Revision history. 928 REVISION 929 "200310300900Z" -- 30 October 2003 09:00:00 GMT 930 DESCRIPTION 931 "Initial revision, published as part of RFC XXXX." 932 ::= { gmplsStdMIB xx } 934 -- Top level components of this MIB module. 936 -- Notifications 937 -- no notifications are currently defined. 938 gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 } 939 -- Tables, Scalars 940 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 942 -- Conformance 943 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 945 -- GMPLS Label Table. 947 gmplsLabelIndexNext OBJECT-TYPE 948 SYNTAX IndexIntegerNextFree 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "This object contains an unused value for 953 gmplsLabelIndex, or a zero to indicate 954 that no unused value exists or is available. 956 An management application wishing to create 957 a row in the gmplsLabelTable may read this 958 object and then attempt to create a row in 959 the table. If row creation fails (because 960 another application has already created a row 961 with the supplied index) the management 962 application should read this object again 963 to get a new index value. 965 When a row is created in the gmplsLabelTable 966 with the gmplsLabelIndex value held by this 967 object, an implementation MUST change the value 968 in this object. 969 " 970 ::= { gmplsLabelObjects 1 } 972 gmplsLabelTable OBJECT-TYPE 973 SYNTAX SEQUENCE OF GmplsLabelEntry 974 MAX-ACCESS not-accessible 975 STATUS current 976 DESCRIPTION 977 "Table of GMPLS Labels. This table allows the 978 representation of the more complex label forms 979 required for GMPLS which cannot be held within the 980 textual convention MplsLabel. That is labels that 981 cannot be encoded within 32 bits. It is, 982 nevertheless also capable of holding 32 bit labels 983 or regular MPLS labels if desired. 985 Each entry in this table represents an individual 986 GMPLS label value. Labels in the tables in other 987 MIBs are referred to using row pointer into this 988 table. The indexing of this table provides for 989 arbitrary indexing and also for concatenation of 990 labels." 991 ::= { gmplsLabelObjects 2 } 992 gmplsLabelEntry OBJECT-TYPE 993 SYNTAX GmplsLabelEntry 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "An entry in this table represents a single label 998 value. There are three indexes into the table. 999 - The interface index may be helpful to distinguish 1000 which labels are in use on which interfaces or to 1001 handle cases where there are a very large number 1002 of labels in use in the system. When label 1003 representation is desired to apply to the whole 1004 system or when it is not important to distinguish 1005 labels by their interfaces, this index MAY be set 1006 to zero. 1007 - The label index provides a way of identifying the 1008 label. 1009 - The label sub-index is only used for concatenated 1010 labels. It identifies each component label. When 1011 non-concatenated labels are used, this index 1012 SHOULD be set to zero. 1014 A storage type object is supplied to control the 1015 storage type for each entry, but implementations 1016 should note that the storage type of conceptual rows 1017 in other tables that include row pointers to an 1018 entry in this table SHOULD dictate the storage type 1019 of the rows in this table where the row in the other 1020 table is more persistent." 1021 INDEX { 1022 gmplsLabelInterface, 1023 gmplsLabelIndex, 1024 gmplsLabelSubindex } 1025 ::= { gmplsLabelTable 1 } 1027 GmplsLabelEntry ::= SEQUENCE { 1028 gmplsLabelInterface InterfaceIndexOrZero, 1029 gmplsLabelIndex Unsigned32, 1030 gmplsLabelSubindex Unsigned32, 1031 gmplsLabelType GmplsGeneralizedLabelTypes, 1032 gmplsLabelMplsLabel MplsLabel, 1033 gmplsLabelPortWavelength Unsigned32, 1034 gmplsLabelFreeformLength Integer32, 1035 gmplsLabelFreeform GmplsFreeformLabel, 1036 gmplsLabelSonetSdhSignalIndex Integer32, 1037 gmplsLabelSdhVc Integer32, 1038 gmplsLabelSdhVcBranch Integer32, 1039 gmplsLabelSonetSdhBranch Integer32, 1040 gmplsLabelSonetSdhGroupBranch Integer32, 1041 gmplsLabelWavebandId Unsigned32, 1042 gmplsLabelWavebandStart Unsigned32, 1043 gmplsLabelWavebandEnd Unsigned32, 1044 gmplsLabelRowStatus RowStatus, 1045 gmplsLabelStorageType StorageType 1046 } 1047 gmplsLabelInterface OBJECT-TYPE 1048 SYNTAX InterfaceIndexOrZero 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "The interface on which this label is used. If the 1053 label has or could have applicability across the 1054 whole system, this object SHOULD be set to zero." 1055 ::= { gmplsLabelEntry 1 } 1057 gmplsLabelIndex OBJECT-TYPE 1058 SYNTAX Unsigned32 (0..4294967295) 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "An arbitrary index into the table to identify a 1063 label. 1064 Note that implementations that are representing 32 1065 bit labels within this table MAY choose to align 1066 this index with the value of the label, but should 1067 be aware of the implications of sparsely populated 1068 tables. 1069 A management application may read the gmplsLabelIndexNext 1070 object to find a suitable value for this object." 1071 ::= { gmplsLabelEntry 2 } 1073 gmplsLabelSubindex OBJECT-TYPE 1074 SYNTAX Unsigned32 (0..4294967295) 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "In conjunction with gmplsLabelInterface and 1079 gmplsLabelIndex, this object uniquely identifies 1080 this row. This sub-index allows a single GMPLS label 1081 to be defined as a concatenation of labels. This is 1082 particularly useful in TDM. 1083 The ordering of sub-labels is strict with the sub- 1084 label with lowest gmplsLabelSubindex appearing 1085 first. Note that all sub-labels of a single GMPLS 1086 label must share the same gmplsLabelInterface and 1087 gmplsLabelIndex values. For labels that are not 1088 composed of concatenated sub-labels, this value 1089 SHOULD be set to zero." 1090 ::= { gmplsLabelEntry 3 } 1092 gmplsLabelType OBJECT-TYPE 1093 SYNTAX GmplsGeneralizedLabelTypes 1094 MAX-ACCESS read-create 1095 STATUS current 1096 DESCRIPTION 1097 "Identifies the type of this label. Note that this 1098 object does not determine whether MPLS or GMPLS 1099 signaling is in use: a value of gmplsMplsLabel (1) 1100 denotes that a 23 bit MPLS packet label is present, 1101 but does not describe whether this is signaled using 1102 MPLS or GMPLS. 1104 The value of this object helps determine which of 1105 the following objects are valid. 1106 This object cannot be modified if 1107 gmplsLabelRowStatus is active(1)." 1108 ::= { gmplsLabelEntry 4 } 1110 gmplsLabelMplsLabel OBJECT-TYPE 1111 SYNTAX MplsLabel 1112 MAX-ACCESS read-create 1113 STATUS current 1114 DESCRIPTION 1115 "The value of an MPLS label (that is a packet label) 1116 if this table is used to store it. This may be used 1117 in MPLS systems even though the label values can be 1118 adequately stored in the MPLS MIB modules. Further, 1119 in mixed MPLS and GMPLS systems it may be 1120 advantageous to store all labels in a single label 1121 table. Lastly, in GMPLS systems where packet labels 1122 are used (that is in systems that use GMPLS 1123 signaling and GMPLS labels for packet switching) it 1124 may be desirable to use this table. 1125 This object is only valid if gmplsLabelType is set 1126 to gmplsMplsLabel (1). 1127 This object cannot be modified if 1128 gmplsLabelRowStatus is active(1)." 1129 ::= { gmplsLabelEntry 6 } 1131 gmplsLabelPortWavelength OBJECT-TYPE 1132 SYNTAX Unsigned32 1133 MAX-ACCESS read-create 1134 STATUS current 1135 DESCRIPTION 1136 "The value of a Port or Wavelength Label when carried 1137 as a Generalized Label. Only valid if gmplsLabelType 1138 is set to gmplsPortWavelengthLabel(2). 1139 This object cannot be modified if 1140 gmplsLabelRowStatus is active(1)." 1141 ::= { gmplsLabelEntry 7 } 1143 gmplsLabelFreeformLength OBJECT-TYPE 1144 SYNTAX Integer32 (1..64) 1145 MAX-ACCESS read-create 1146 STATUS current 1147 DESCRIPTION 1148 "The length of a freeform Generalized Label indicated 1150 in the gmplsFreeformLabel object. Only valid if 1151 gmplsLabelType is set to 1152 gmplsFreeformGeneralizedLabel(3). 1153 This object cannot be modified if 1154 gmplsLabelRowStatus is active(1)." 1155 ::= { gmplsLabelEntry 8 } 1157 gmplsLabelFreeform OBJECT-TYPE 1158 SYNTAX GmplsFreeformLabel 1159 MAX-ACCESS read-create 1160 STATUS current 1161 DESCRIPTION 1162 "The value of a freeform Generalized Label that does 1163 not conform to one of the standardized label 1164 encoding or that an implementation chooses to 1166 represent as an octet string without further 1167 decoding. The length of this object is given by the 1168 value of gmplsFreeformLength. Only valid if 1169 gmplsLabelType is set to 1170 gmplsFreeformGeneralizedLabel(3). 1171 This object cannot be modified if 1172 gmplsLabelRowStatus is active(1)." 1173 ::= { gmplsLabelEntry 9 } 1175 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 1176 SYNTAX Integer32 (0..4095) 1177 MAX-ACCESS read-create 1178 STATUS current 1179 DESCRIPTION 1180 "The Signal Index value (S) of a SONET or SDH 1181 Generalized Label. Zero indicates that this field is 1182 not significant. Only valid if gmplsLabelType is set 1183 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1184 This object cannot be modified if 1185 gmplsLabelRowStatus is active(1)." 1186 ::= { gmplsLabelEntry 10 } 1188 gmplsLabelSdhVc OBJECT-TYPE 1189 SYNTAX Integer32 (0..15) 1190 MAX-ACCESS read-create 1191 STATUS current 1192 DESCRIPTION 1193 "The VC Indicator (U) of an SDH Generalized Label. 1194 Zero indicates that this field is non-significant. 1195 Only valid if gmplsLabelType is set to 1196 gmplsSdhLabel(5). 1197 This object cannot be modified if 1198 gmplsLabelRowStatus is active(1)." 1199 ::= { gmplsLabelEntry 11 } 1201 gmplsLabelSdhVcBranch OBJECT-TYPE 1202 SYNTAX Integer32 (0..15) 1203 MAX-ACCESS read-create 1204 STATUS current 1205 DESCRIPTION 1206 "The VC Branch Indicator (K) of an SDH Generalized 1207 Label. Zero indicates that this field is non- 1208 significant. Only valid if gmplsLabelType is set to 1209 gmplsSdhLabel(5). 1210 This object cannot be modified if 1211 gmplsLabelRowStatus is active(1)." 1212 ::= { gmplsLabelEntry 12 } 1214 gmplsLabelSonetSdhBranch OBJECT-TYPE 1215 SYNTAX Integer32 (0..15) 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "The Branch Indicator (L) of a SONET or SDH 1220 Generalized Label. Zero indicates that this field is 1221 non-significant. Only valid gmplsLabelType is set to 1222 gmplsSonetLabel(4) or gmplsSdhLabel(5). 1223 This object cannot be modified if 1224 gmplsLabelRowStatus is active(1)." 1225 ::= { gmplsLabelEntry 13 } 1227 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1228 SYNTAX Integer32 (0..15) 1229 MAX-ACCESS read-create 1230 STATUS current 1231 DESCRIPTION 1232 "The Group Branch Indicator (M) of a SONET or SDH 1233 Generalized Label. Zero indicates that this field is 1234 non-significant. Only valid if gmplsLabelType is set 1235 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1236 This object cannot be modified if 1237 gmplsLabelRowStatus is active(1)." 1238 ::= { gmplsLabelEntry 14 } 1240 gmplsLabelWavebandId OBJECT-TYPE 1241 SYNTAX Unsigned32 1242 MAX-ACCESS read-create 1243 STATUS current 1244 DESCRIPTION 1245 "The waveband identifier component of a waveband 1246 label. Only valid if gmplsLabelType is set to 1247 gmplsWavebandLabel(6). 1248 This object cannot be modified if 1249 gmplsLabelRowStatus is active(1)." 1250 ::= { gmplsLabelEntry 15 } 1252 gmplsLabelWavebandStart OBJECT-TYPE 1253 SYNTAX Unsigned32 1254 MAX-ACCESS read-create 1255 STATUS current 1256 DESCRIPTION 1257 "The starting label component of a waveband label. 1258 Only valid if gmplsLabelType is set to 1259 gmplsWavebandLabel(6). 1260 This object cannot be modified if 1261 gmplsLabelRowStatus is active(1)." 1262 ::= { gmplsLabelEntry 16 } 1264 gmplsLabelWavebandEnd OBJECT-TYPE 1265 SYNTAX Unsigned32 1266 MAX-ACCESS read-create 1267 STATUS current 1268 DESCRIPTION 1269 "The end label component of a waveband label. Only 1270 valid if gmplsLabelType is set to 1271 gmplsWavebandLabel(6). 1272 This object cannot be modified if 1273 gmplsLabelRowStatus is active(1)." 1274 ::= { gmplsLabelEntry 17 } 1275 gmplsLabelRowStatus OBJECT-TYPE 1276 SYNTAX RowStatus 1277 MAX-ACCESS read-create 1278 STATUS current 1279 DESCRIPTION 1280 "This variable is used to create, modify, and/or 1281 delete a row in this table. When a row in this 1282 table has a row in the active(1) state, no 1283 objects in this row can be modified except the 1284 gmplsLabelRowStatus and gmplsLabelStorageType." 1285 ::= { gmplsLabelEntry 18 } 1287 gmplsLabelStorageType OBJECT-TYPE 1288 SYNTAX StorageType 1289 MAX-ACCESS read-create 1290 STATUS current 1291 DESCRIPTION 1292 "This variable indicates the storage type for this 1293 object. 1295 The agent MUST ensure that this object's value 1296 remains consistent with the storage type of any rows 1297 in other tables that contain pointers to this row. 1298 In particular, the storage type of this row must be 1299 at least as permanent as that of any row that point 1300 to it. 1302 Conceptual rows having the value 'permanent' need 1303 not allow write-access to any columnar objects in 1304 the row." 1305 REFERENCE 1306 "See RFC2579." 1307 DEFVAL { volatile } 1308 ::= { gmplsLabelEntry 19 } 1310 -- End of GMPLS Label Table 1312 -- Module compliance. 1314 gmplsLabelGroups 1315 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1317 gmplsLabelCompliances 1318 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1320 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1321 STATUS current 1322 DESCRIPTION 1323 "Compliance statement for agents that support 1324 the GMPLS Label MIB module." 1326 MODULE -- this module 1328 -- The mandatory groups have to be implemented by 1329 -- LSRs claiming support for this MIB module. This MIB module is, 1330 -- however, not mandatory for a working implementation of a GMPLS 1331 -- LSR with full MIB support if the GMPLS labels in use can be 1332 -- represented within a 32 bit quantity. 1334 MANDATORY-GROUPS { 1335 gmplsLabelTableGroup 1336 } 1338 -- Units of conformance. 1340 GROUP gmplsLabelTableGroup 1341 DESCRIPTION 1342 "This group is mandatory for devices which support 1343 the gmplsLabelTable." 1345 GROUP gmplsLabelPacketGroup 1346 DESCRIPTION 1347 "This group extends gmplsLabelTableGroup for 1348 implementations that support packet labels." 1350 GROUP gmplsLabelPortWavelengthGroup 1351 DESCRIPTION 1352 "This group extends gmplsLabelTableGroup for 1353 implementations that support port and wavelength 1354 labels." 1356 GROUP gmplsLabelFreeformGroup 1357 DESCRIPTION 1358 "This group extends gmplsLabelTableGroup for 1359 implementations that support freeform labels." 1361 GROUP gmplsLabelSonetSdhGroup 1362 DESCRIPTION 1363 "This group extends gmplsLabelTableGroup for 1364 implementations that support SONET or SDH labels." 1366 GROUP gmplsLabelWavebandGroup 1367 DESCRIPTION 1368 "This group extends gmplsLabelTableGroup for 1369 implementations that support Waveband labels." 1371 -- gmplsLabelTable 1373 OBJECT gmplsLabelType 1374 MIN-ACCESS read-only 1375 DESCRIPTION 1376 "Write access is not required." 1378 OBJECT gmplsLabelMplsLabel 1379 MIN-ACCESS read-only 1380 DESCRIPTION 1381 "Write access is not required." 1383 OBJECT gmplsLabelPortWavelength 1384 MIN-ACCESS read-only 1385 DESCRIPTION 1386 "Write access is not required." 1388 OBJECT gmplsLabelFreeformLength 1389 MIN-ACCESS read-only 1390 DESCRIPTION 1391 "Write access is not required." 1393 OBJECT gmplsLabelFreeform 1394 MIN-ACCESS read-only 1395 DESCRIPTION 1396 "Write access is not required." 1398 OBJECT gmplsLabelSonetSdhSignalIndex 1399 MIN-ACCESS read-only 1400 DESCRIPTION 1401 "Write access is not required." 1403 OBJECT gmplsLabelSdhVc 1404 MIN-ACCESS read-only 1405 DESCRIPTION 1406 "Write access is not required." 1408 OBJECT gmplsLabelSdhVcBranch 1409 MIN-ACCESS read-only 1410 DESCRIPTION 1411 "Write access is not required." 1413 OBJECT gmplsLabelSonetSdhBranch 1414 MIN-ACCESS read-only 1415 DESCRIPTION 1416 "Write access is not required." 1418 OBJECT gmplsLabelSonetSdhGroupBranch 1419 MIN-ACCESS read-only 1420 DESCRIPTION 1421 "Write access is not required." 1423 OBJECT gmplsLabelWavebandId 1424 MIN-ACCESS read-only 1425 DESCRIPTION 1426 "Write access is not required." 1428 OBJECT gmplsLabelWavebandStart 1429 MIN-ACCESS read-only 1430 DESCRIPTION 1431 "Write access is not required." 1433 OBJECT gmplsLabelWavebandEnd 1434 MIN-ACCESS read-only 1435 DESCRIPTION 1436 "Write access is not required." 1438 OBJECT gmplsLabelRowStatus 1439 SYNTAX RowStatus { 1440 active(1), 1441 notInService(2) 1442 } 1443 WRITE-SYNTAX RowStatus { 1444 active(1), 1445 notInService(2), 1446 createAndGo(4), 1447 destroy(6) 1448 } 1449 DESCRIPTION 1450 "Support for notInService, createAndWait and notReady 1451 is not required." 1453 OBJECT gmplsLabelStorageType 1454 MIN-ACCESS read-only 1455 DESCRIPTION 1456 "Write access is not required." 1458 ::= { gmplsLabelCompliances 1 } 1460 -- Units of conformance. 1462 gmplsLabelTableGroup OBJECT-GROUP 1463 OBJECTS { 1464 gmplsLabelIndexNext, 1465 gmplsLabelType, 1466 gmplsLabelRowStatus, 1467 gmplsLabelStorageType 1468 } 1469 STATUS current 1470 DESCRIPTION 1471 "Necessary, but not sufficient, set of objects to 1472 implement label table support. In addition, 1473 depending on the type of labels supported (for 1474 example, wavelength labels), the following other 1475 groups defined below are mandatory: 1476 gmplsLabelPacketGroup and/or 1477 gmplsLabelPortWavelengthGroup and/or 1478 gmplsLabelFreeformGroup and/or 1479 gmplsLabelSonetSdhGroup." 1480 ::= { gmplsLabelGroups 1 } 1482 gmplsLabelPacketGroup OBJECT-GROUP 1483 OBJECTS { 1484 gmplsLabelMplsLabel 1485 } 1486 STATUS current 1487 DESCRIPTION 1488 "Object needed to implement Packet (MPLS) labels." 1489 ::= { gmplsLabelGroups 2 } 1490 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1491 OBJECTS { 1492 gmplsLabelPortWavelength 1493 } 1494 STATUS current 1495 DESCRIPTION 1496 "Object needed to implement Port and Wavelength 1497 labels." 1498 ::= { gmplsLabelGroups 3 } 1500 gmplsLabelFreeformGroup OBJECT-GROUP 1501 OBJECTS { 1502 gmplsLabelFreeformLength, 1503 gmplsLabelFreeform 1504 } 1505 STATUS current 1506 DESCRIPTION 1507 "Object needed to implement Freeform labels." 1508 ::= { gmplsLabelGroups 4 } 1510 gmplsLabelSonetSdhGroup OBJECT-GROUP 1511 OBJECTS { 1512 gmplsLabelSonetSdhSignalIndex, 1513 gmplsLabelSdhVc, 1514 gmplsLabelSdhVcBranch, 1515 gmplsLabelSonetSdhBranch, 1516 gmplsLabelSonetSdhGroupBranch 1517 } 1518 STATUS current 1519 DESCRIPTION 1520 "Object needed to implement SONET and SDH labels." 1521 ::= { gmplsLabelGroups 5 } 1523 gmplsLabelWavebandGroup OBJECT-GROUP 1524 OBJECTS { 1525 gmplsLabelWavebandId, 1526 gmplsLabelWavebandStart, 1527 gmplsLabelWavebandEnd 1528 } 1529 STATUS current 1530 DESCRIPTION 1531 "Object needed to implement Waveband labels." 1532 ::= { gmplsLabelGroups 6 } 1534 END 1536 9. Security Considerations 1538 It is clear that the MIB modules described in this document in 1539 association with the MPLS-LSR-STD-MIB are potentially useful for 1540 monitoring of GMPLS LSRs. These MIB modules can also be used for 1541 configuration of certain objects, and anything that can be configured 1542 can be incorrectly configured, with potentially disastrous results. 1544 There are a number of management objects defined in these MIB modules 1545 with a MAX-ACCESS clause of read-write and/or read-create. Such 1546 objects may be considered sensitive or vulnerable in some network 1547 environments. The support for SET operations in a non-secure 1548 environment without proper protection can have a negative effect on 1549 network operations. These are the tables and objects and their 1550 sensitivity/vulnerability: 1552 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1553 and gmplsLabelTable collectively contain objects to provision 1554 GMPLS interfaces, LSPs and their associated parameters on a Label 1555 Switching Router (LSR). Unauthorized write access to objects in 1556 these tables, could result in disruption of traffic on the 1557 network. This is especially true if an LSP has already been 1558 established. The use of stronger mechanisms such as SNMPv3 1559 security should be considered where possible. Specifically, SNMPv3 1560 VACM and USM MUST be used with any SNMPv3 agent which implements 1561 these MIB modules. 1563 Some of the readable objects in these MIB modules "i.e., objects with 1564 a MAX-ACCESS other than not-accessible" may be considered sensitive 1565 or vulnerable in some network environments. It is thus important to 1566 control even GET and/or NOTIFY access to these objects and possibly 1567 to even encrypt the values of these objects when sending them over 1568 the network via SNMP. These are the tables and objects and their 1569 sensitivity/vulnerability: 1571 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1572 and gmplsLabelTable collectively show the LSP network topology and 1573 its capabilities. If an Administrator does not want to reveal this 1574 information, then these tables should be considered 1575 sensitive/vulnerable. 1577 SNMP versions prior to SNMPv3 did not include adequate security. Even 1578 if the network itself is secure "for example by using IPSec", even 1579 then, there is no control as to who on the secure network is allowed 1580 to access and GET/SET "read/change/create/delete" the objects in 1581 these MIB modules. It is RECOMMENDED that implementers consider the 1582 security features as provided by the SNMPv3 framework "see [RFC3410], 1583 section 8", including full support for the SNMPv3 cryptographic 1584 mechanisms "for authentication and privacy". 1586 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1587 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1588 enable cryptographic security. It is then a customer/operator 1589 responsibility to ensure that the SNMP entity giving access to an 1590 instance of this MIB module, is properly configured to give access to 1591 the objects only to those principals "users" that have legitimate 1592 rights to indeed GET or SET "change/create/delete" them. 1594 10. Acknowledgments 1596 This draft extends [LSRMIB]. The authors would like to express their 1597 gratitude to all those who worked on that earlier MIB document. 1599 The authors would like to express their thanks to Dan Joyle for his 1600 careful review and comments on early versions of the Label Table. 1601 Special thanks to Joan Cucchiara and Len Nieman for their help with 1602 compilation issues. 1604 11. IANA Considerations 1606 MPLS related standards track MIB modules are rooted under the 1607 mplsStdMIB subtree. 1609 One of the MIB modules contained in this document extends tables 1610 contained in MPLS MIB modules. 1612 As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the 1613 two MIB modules contained in this document should be placed in the 1614 mplsStdMIB subtree as well. 1616 New assignments can only be made via a Standards Action as specified 1617 in [RFC2434]. 1619 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 1621 The IANA is requested to assign { mplsStdMIB xx } to the 1622 GMPLS-LSR-STD-MIB module specified in this document. 1624 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 1626 The IANA is requested to assign { mplsStdMIB xx } to the 1627 GMPLS-LABEL-STD-MIB module specified in this document. 1629 12. References 1631 12.1. Normative References 1633 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1634 Requirement Levels", BCP 14, RFC 2119, March 1997. 1636 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1637 Case, J., Rose, M., and S. Waldbusser, "Structure 1638 of Management Information Version 2 (SMIv2)", STD 1639 58, RFC 2578, April 1999. 1641 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1642 Case, J., Rose, M., and S. Waldbusser, "Textual 1643 Conventions for SMIv2", STD 58, RFC 2579, April 1644 1999. 1646 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1647 Case, J., Rose, M., and S. Waldbusser, "Conformance 1648 Statements for SMIv2", STD 58, RFC 2580, April 1649 1999. 1651 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces 1652 Group MIB", RFC 2863, June 2000. 1654 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 1655 Label Switching (GMPLS) Architecture", Internet 1656 Draft , May 1657 2003, work in progress. 1659 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 1660 "Generalized Multi-Protocol Label Switching 1661 Extensions for SONET and SDH Control", Internet 1662 Draft , 1663 February 2003, work in progress. 1665 [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 1666 and Harrison, E., "Definitions of Textual 1667 Conventions for Multiprotocol Label Switching 1668 (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib- 1669 03.txt, November 2003, work in progress. 1671 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 1672 and Harrison, E., "Generalized Multiprotocol Label 1673 Switching (GMPLS) Traffic Engineering Management 1674 Information Base", draft-ietf-ccamp-gmpls-te-mib- 1675 03.txt, November 2003, work in progress. 1677 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of 1678 Textual Conventions for Multiprotocol Label 1679 Switching (MPLS) Management", Internet Draft 1680 , August 2003, work 1681 in progress. 1683 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, 1684 "Multiprotocol Label Switching (MPLS) Label 1685 Switching Router (LSR) Management Information 1686 Base", Internet Draft , August 2003, work in progress. 1689 12.2. Informational References 1691 [RFC2026] S. Bradner, "The Internet Standards Process -- 1692 Revision 3", RFC 2026, October 1996. 1694 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 1695 Writing an IANA Considerations Section in RFCs", 1696 BCP: 26, RFC 2434, October 1998. 1698 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1699 "Multiprotocol Label Switching Architecture", RFC 1700 3031, January 2001. 1702 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 1703 Srinivasan, V., and G. Swallow, "RSVP-TE: 1704 Extensions to RSVP for LSP Tunnels", RFC 3209, 1705 December 2001. 1707 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 1708 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 1709 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 1710 T., Feldman, N., Fredette, A., Girish, M., Gray, 1711 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 1712 A., and P. Vaananen, "Constraint-Based LSP Setup 1713 using LDP", RFC 3212, December 2001." 1715 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1716 "Introduction and Applicability Statements for 1717 Internet-Standard Management Framework", RFC 3410, 1718 December 2002. 1720 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1721 Architecture for Describing Simple Network 1722 Management Protocol (SNMP) Management Frameworks", 1723 RFC 3411, December 2002. 1725 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 1726 Applications", RFC 3413, December 2002. 1728 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 1729 Label Switching (GMPLS) Signaling Functional 1730 Description", RFC 3471, January 2003. 1732 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 1733 "Generalized MPLS Signaling - CR-LDP Extensions", 1734 RFC 3472, January 2003. 1736 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 1737 RSVP-TE Extensions", RFC 3473 January 2003. 1739 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 1740 "Multiprotocol Label Switching (MPLS) Traffic 1741 Engineering Management Information Base", Internet 1742 Draft , August 2003, 1743 work in progress. 1745 13. Authors' Addresses 1747 Thomas D. Nadeau 1748 Cisco Systems, Inc. 1749 300 Apollo Drive 1750 Chelmsford, MA 01824 1751 Phone: +1-978-244-3051 1752 Email: tnadeau@cisco.com 1754 Cheenu Srinivasan 1755 Bloomberg L.P. 1756 499 Park Ave., 1757 New York, NY 10022 1758 Phone: +1-212-893-3682 1759 Email: cheenu@bloomberg.net 1761 Adrian Farrel 1762 Old Dog Consulting 1763 Phone: +44-(0)-1978-860944 1764 Email: adrian@olddog.co.uk 1766 Tim Hall 1767 Data Connection Ltd. 1768 100 Church Street 1769 Enfield, Middlesex, EN2 6BQ, UK 1770 Phone: +44 20 8366 1177 1771 Email: timhall@dataconnection.com 1772 Ed Harrison 1773 Data Connection Ltd. 1774 100 Church Street 1775 Enfield, Middlesex, EN2 6BQ, UK 1776 Phone: +44 20 8366 1177 1777 Email: ed.harrison@dataconnection.com 1779 14. Full Copyright Statement 1781 Copyright (C) The Internet Society (2003). All Rights Reserved. 1783 This document and translations of it may be copied and furnished to 1784 others, and derivative works that comment on or otherwise explain it 1785 or assist in its implementation may be prepared, copied, published 1786 and distributed, in whole or in part, without restriction of any 1787 kind, provided that the above copyright notice and this paragraph 1788 are included on all such copies and derivative works. However, this 1789 document itself may not be modified in any way, such as by removing 1790 the copyright notice or references to the Internet Society or other 1791 Internet organizations, except as needed for the purpose of 1792 developing Internet standards in which case the procedures for 1793 copyrights defined in the Internet Standards process must be 1794 followed, or as required to translate it into languages other than 1795 English. 1797 The limited permissions granted above are perpetual and will not be 1798 revoked by the Internet Society or its successors or assigns. This 1799 document and the information contained herein is provided on an "AS 1800 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1801 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 1802 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 1803 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1804 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1806 15. Intellectual Property Notice 1808 The IETF takes no position regarding the validity or scope of any 1809 intellectual property or other rights that might be claimed to 1810 pertain to the implementation or use of the technology described in 1811 this document or the extent to which any license under such rights 1812 might or might not be available; neither does it represent that it 1813 has made any effort to identify any such rights. Information on the 1814 IETF's procedures with respect to rights in standards-track and 1815 standards-related documentation can be found in BCP-11 [RFC2028]. 1817 Copies of claims of rights made available for publication and any 1818 assurances of licenses to be made available, or the result of an 1819 attempt made to obtain a general license or permission for the use 1820 of such proprietary rights by implementers or users of this 1821 specification can be obtained from the IETF Secretariat. 1823 The IETF invites any interested party to bring to its attention any 1824 copyrights, patents or patent applications, or other proprietary 1825 rights that may cover technology that may be required to practice 1826 this standard. Please address the information to the IETF Executive 1827 Director. 1829 16. Changes and Pending Work 1831 This section must be removed before the draft progresses to RFC. 1833 16.1. Pending Work 1835 The following work items have been identified for this draft. They 1836 will be addressed in a future version. 1838 - Expand conformance statements to give one for monitoring only, 1839 and one for monitoring and control. 1840 - Provide support for monitoring tunnel resources in GMPLS systems. 1841 For example, SONET/SDH or G.709. This might be done through an 1842 arbitrary RowPointer to an external MIB. 1843 - Extend the performance tables from the MPLS-LSR-MIB for 1844 technology-specific GMPLS LSPs. 1845 - Determine whether the 'discriminated union' in the Label Table is 1846 good MIB. 1848 16.1. Changes from version 2 to version 3 1850 - Work on basic compilation issues. 1851 - Provide a next index object to supply the next available 1852 arbitrary index into the Label Table. 1853 - Update references. 1854 - Update examples.