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