idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-09.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 1972. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1945. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1952. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1958. ** 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 (October 2005) is 6768 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 1786, 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: April 2006 Adrian Farrel, Ed. 5 Old Dog Consulting 7 October 2005 9 Generalized Multiprotocol Label Switching (GMPLS) 10 Label Switching Router (LSR) Management Information Base 12 draft-ietf-ccamp-gmpls-lsr-mib-09.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 ............................. 9 58 7. GMPLS Label Switching Router MIB Definitions .... 11 59 8. GMPLS Label MIB Definitions ..................... 22 60 9. Security Considerations ......................... 37 61 10. Acknowledgments ................................ 39 62 11. IANA Considerations ............................ 39 63 11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 39 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 ....................... 41 68 13. Contact Information ............................ 41 69 14. Intellectual Property Considerations ........... 42 70 15. Full Copyright Statement ....................... 43 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 } 321 In gmplsLabelTable: 322 { 323 gmplsLabelInterface = 13, 324 gmplsLabelIndex = 1, 325 gmplsLabelSubindex = 0, 326 gmplsLabelType = gmplsFreeformLabel(3), 327 gmplsLabelFreeform = 0xFEDCBA9876543210 328 gmplsLabelRowStatus = createAndGo(4) 329 } 331 We must next create the appropriate in-segment and out-segment 332 entries. These are done in [RFC3813] using the mplsInSegmentTable and 333 mplsOutSegmentTable. Note that we use a row pointer to the two rows 334 in the gmplsLabelTable rather than specifying the labels explicitly 335 in the in- and out-segment tables. Also note that the row status for 336 each row is set to createAndWait(5) to allow corresponding entries in 337 the gmplsInSegmentTable and gmplsOutSegmentTable to be created. 339 For the forward direction. 341 In mplsInSegmentTable: 342 { 343 mplsInSegmentIndex = 0x00000015 344 mplsInSegmentLabel = 0, -- incoming label in label table 345 mplsInSegmentNPop = 1, 346 mplsInSegmentInterface = 12, -- incoming interface 347 -- RowPointer MUST point to the first accsesible column. 348 mplsInSegmentTrafficParamPtr = 0.0, 349 mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0) 350 mplsInSegmentRowStatus = createAndWait(5) 351 } 353 In mplsOutSegmentTable: 354 { 355 mplsOutSegmentIndex = 0x00000012, 356 mplsOutSegmentInterface = 13, -- outgoing interface 357 mplsOutSegmentPushTopLabel = true(1), 358 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 360 -- RowPointer MUST point to the first accessible column. 361 mplsOutSegmentTrafficParamPtr = 0.0, 362 mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0) 363 mplsOutSegmentRowStatus = createAndWait(5) 364 } 365 For the reverse direction. 367 In mplsInSegmentTable: 368 { 369 mplsInSegmentIndex = 0x00000016 371 mplsInSegmentLabel = 0, -- incoming label in label table 372 mplsInSegmentNPop = 1, 373 mplsInSegmentInterface = 13, -- incoming interface 375 -- RowPointer MUST point to the first accessible column. 376 mplsInSegmentTrafficParamPtr = 0.0, 377 mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0) 379 mplsInSegmentRowStatus = createAndWait(5) 380 } 382 In mplsOutSegmentTable: 383 { 384 mplsOutSegmentIndex = 0x00000013, 385 mplsOutSegmentInterface = 12, -- outgoing interface 386 mplsOutSegmentPushTopLabel = true(1), 387 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 389 -- RowPointer MUST point to the first accessible column. 390 mplsOutSegmentTrafficParamPtr = 0.0, 391 mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0) 393 mplsOutSegmentRowStatus = createAndWait(5) 394 } 396 These table entries are extended by entries in gmplsInSegmentTable 397 and gmplsOutSegmentTable. Note that the nature of the 'extends' 398 relationship is a sparse augmentation so that the entry in 399 gmplsInSegmentTable has the same index values as the entry in 400 mplsInSegmentTable. Similarly, the entry in gmplsOutSegmentTable has 401 the same index values as the entry in mplsOutSegmentTable. 403 First for the forward direction: 405 In gmplsInSegmentTable(0x00000015) 406 { 407 gmplsInSegmentDirection = forward (1) 408 } 410 In gmplsOutSegmentTable(0x00000012) 411 { 412 gmplsOutSegmentDirection = forward (1) 413 } 414 Next for the reverse direction: 416 In gmplsInSegmentTable(0x00000016) 417 { 418 gmplsInSegmentDirection = reverse (2) 419 } 421 In gmplsOutSegmentTable(0x00000013) 422 { 423 gmplsOutSegmentDirection = reverse (2) 424 } 426 Next, two cross-connect entries are created in the mplsXCTable of the 427 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 428 segments together. 430 In mplsXCTable: 431 { 432 mplsXCIndex = 0x01, 433 mplsXCInSegmentIndex = 0x00000015, 434 mplsXCOutSegmentIndex = 0x00000012, 435 mplsXCLspId = 0x0102 -- unique ID 436 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 437 mplsXCRowStatus = createAndGo(4) 438 } 440 In mplsXCTable: 441 { 442 mplsXCIndex = 0x02, 443 mplsXCInSegmentIndex = 0x00000016, 444 mplsXCOutSegmentIndex = 0x00000013, 445 mplsXCLspId = 0x0102 -- unique ID 446 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 447 mplsXCRowStatus = createAndGo(4) 448 } 450 Finally, the in-segments and out-segments are activated. 452 In mplsInSegmentTable(0x00000015): 453 { 454 mplsInSegmentRowStatus = active(1) 455 } 456 In mplsInSegmentTable(0x00000016): 457 { 458 mplsInSegmentRowStatus = active(1) 459 } 460 In mplsOutSegmentTable(0x00000012): 461 { 462 mplsOutSegmentRowStatus = active(1) 463 } 464 In mplsOutSegmentTable(0x00000013): 465 { 466 mplsOutSegmentRowStatus = active(1) 467 } 469 7. GMPLS Label Switching Router MIB Definitions 471 This MIB module makes references to the following documents. 472 [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3209], [RFC3443], 473 [RFC3472], [RFC3473], [RFC3811], [RFC3813], and [GMPLSTCMIB]. 475 GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN 477 IMPORTS 478 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, zeroDotZero 479 FROM SNMPv2-SMI -- RFC2578 480 MODULE-COMPLIANCE, OBJECT-GROUP 481 FROM SNMPv2-CONF -- RFC2580 482 RowPointer 483 FROM SNMPv2-TC -- RFC2579 484 GmplsSegmentDirection 485 FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB 486 -- RFC-Editor please resolve the reference above using the RFC number 487 -- and remove this note 488 mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex, 489 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 490 mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup 491 FROM MPLS-LSR-STD-MIB -- RFC3813 492 ifGeneralInformationGroup, ifCounterDiscontinuityGroup 493 FROM IF-MIB -- RFC2863 494 mplsStdMIB 495 FROM MPLS-TC-STD-MIB -- RFC3811 496 ; 498 gmplsLsrStdMIB MODULE-IDENTITY 499 LAST-UPDATED 500 "200505200001Z" -- 20 May 2005 00:00:01 GMT 501 ORGANIZATION 502 "IETF Common Control And Measurement Plane (CCAMP) Working Group" 503 CONTACT-INFO 504 " Thomas D. Nadeau 505 Cisco Systems, Inc. 506 Email: tnadeau@cisco.com 507 Adrian Farrel 508 Old Dog Consulting 509 Email: adrian@olddog.co.uk 510 Comments about this document should be emailed direct to the 511 CCAMP working group mailing list at ccamp@ops.ietf.org" 513 DESCRIPTION 514 "Copyright (C) The Internet Society (2005). This version of 515 this MIB module is part of RFC XXX; see the RFC itself for 516 full legal notices. 517 -- RFC Editor. Please replace XXX above with the correct RFC number and 518 -- remove this note. 520 This MIB module contains managed object definitions for the 521 Generalized Multiprotocol (GMPLS) Label Switching Router as 522 defined in: Generalized Multi-Protocol Label Switching (GMPLS) 523 Architecture, Mannie et al., RFC 3945, October 2004." 525 REVISION 526 "200505200001Z" -- 20 May 2005 00:00:01 GMT 527 DESCRIPTION 528 "Initial version issued as part of RFC XXX." 529 ::= { mplsStdMIB YYY } 530 -- RFC Editor. Please replace XXX above with the correct RFC number and 531 -- remove this note. 533 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 534 -- and remove this note 536 -- no notifications are currently defined. 537 gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } 538 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } 540 gmplsInterfaceTable OBJECT-TYPE 541 SYNTAX SEQUENCE OF GmplsInterfaceEntry 542 MAX-ACCESS not-accessible 543 STATUS current 544 DESCRIPTION 545 "This table specifies per-interface GMPLS capability and 546 associated information. It extends the information in 547 mplsInterfaceTable of the MPLS-LSR-STD-MIB through a 548 sparse augmentation relationship." 549 REFERENCE 550 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 551 Router Management Information Base (MIB), RFC 3813." 552 ::= { gmplsLsrObjects 1 } 554 gmplsInterfaceEntry OBJECT-TYPE 555 SYNTAX GmplsInterfaceEntry 556 MAX-ACCESS not-accessible 557 STATUS current 558 DESCRIPTION 559 "A conceptual row in this table is created automatically by an 560 LSR for each interface that is both capable of supporting 561 GMPLS and that is configured to support GMPLS. Note that 562 support of GMPLS is not limited to control plane signaling, 563 but may include data-plane only function configured through 564 SNMP SET commands performed on this MIB module. 566 A conceptual row in this table may also be created via SNMP 567 SET commands or automatically by the LSR to supplement a 568 conceptual row in the mplsInterfaceTable where the interface 569 is not capable of GMPLS but where the other objects carried 570 in this row provide useful additional information for an 571 MPLS interface. 573 A conceptual row in this table will exist if and only if a 574 corresponding entry in mplsInterfaceTable exists, and a 575 corresponding entry in ifTable exists with ifType = mpls(166). 576 If the associated entry in ifTable is operationally disabled 577 (thus removing the GMPLS capabilities on the interface) or the 578 entry in mplsInterfaceTable is deleted, the corresponding entry 579 in this table MUST be deleted shortly thereafter. 581 The indexes are the same as for mplsInterfaceTable. Thus, the 582 entry with index 0 represents the per-platform label space and 583 contains parameters that apply to all interfaces that 584 participate in the per-platform label space." 585 REFERENCE 586 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 587 Router Management Information Base (MIB), RFC 3813." 588 INDEX { mplsInterfaceIndex } 589 ::= { gmplsInterfaceTable 1 } 591 GmplsInterfaceEntry ::= SEQUENCE { 592 gmplsInterfaceSignalingCaps BITS, 593 gmplsInterfaceRsvpHelloPeriod Unsigned32 594 } 596 gmplsInterfaceSignalingCaps OBJECT-TYPE 597 SYNTAX BITS { 598 unknown (0), 599 rsvpGmpls (1), 600 crldpGmpls (2), -- note the use of CR-LDP is deprecated 601 otherGmpls (3) 602 } 603 MAX-ACCESS read-create 604 STATUS current 605 DESCRIPTION 606 "Defines the signaling capabilities on this interface. Multiple 607 bits may legitimately be set at once, but if 'unknown' is set 608 then no other bit may be set. Setting no bits implies that GMPLS 609 signaling cannot be performed on this interface and all LSPs 610 must be manually provisioned or that this table entry is only 611 present to supplement an entry in the mplsInterfaceTable by 612 providing the information carried in other objects in this row." 613 REFERENCE 614 "1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472. 615 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 616 DEFVAL { { rsvpGmpls } } 617 ::= { gmplsInterfaceEntry 1 } 619 gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE 620 SYNTAX Unsigned32 621 UNITS "milliseconds" 622 MAX-ACCESS read-create 623 STATUS current 624 DESCRIPTION 625 "Period, in milliseconds, between sending RSVP Hello messages on 626 this interface. A value of 0 indicates that no Hello messages 627 should be sent on this interface. 629 This object is only valid if gmplsInterfaceSignalingCaps has no 630 bits set or includes the rsvpGmpls bit." 631 REFERENCE 632 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, 633 section 5. 634 "2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 635 section 9.3." 636 DEFVAL { 3000 } 637 ::= { gmplsInterfaceEntry 2 } 639 gmplsInSegmentTable OBJECT-TYPE 640 SYNTAX SEQUENCE OF GmplsInSegmentEntry 641 MAX-ACCESS not-accessible 642 STATUS current 643 DESCRIPTION 644 "This table sparse augments the mplsInSegmentTable of the 645 MPLS-LSR-STD-MIB to provide GMPLS-specific information about 646 incoming segments to an LSR." 647 REFERENCE 648 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 649 Router Management Information Base (MIB), RFC 3813." 650 ::= { gmplsLsrObjects 2 } 651 gmplsInSegmentEntry OBJECT-TYPE 652 SYNTAX GmplsInSegmentEntry 653 MAX-ACCESS not-accessible 654 STATUS current 655 DESCRIPTION 656 "An entry in this table extends the representation of an incoming 657 segment represented by an entry in mplsInSegmentTable in the 658 MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be 659 created by a network administrator via SNMP SET commands, or in 660 response to signaling protocol events. 662 Note that the storage type for this entry is given by the value 663 of mplsInSegmentStorageType in the corresponding entry of the 664 mplsInSegmentTable." 665 REFERENCE 666 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 667 Router Management Information Base (MIB), RFC 3813." 668 INDEX { mplsInSegmentIndex } 669 ::= { gmplsInSegmentTable 1 } 671 GmplsInSegmentEntry ::= SEQUENCE { 672 gmplsInSegmentDirection GmplsSegmentDirection, 673 gmplsInSegmentExtraParamsPtr RowPointer 674 } 676 gmplsInSegmentDirection OBJECT-TYPE 677 SYNTAX GmplsSegmentDirection 678 MAX-ACCESS read-create 679 STATUS current 680 DESCRIPTION 681 "This object indicates the direction of data flow on this 682 segment. This object cannot be modified if 683 mplsInSegmentRowStatus for the corresponding entry in the 684 mplsInSegmentTable is active(1)." 685 REFERENCE 686 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 687 Router Management Information Base (MIB), RFC 3813." 688 DEFVAL { forward } 689 ::= { gmplsInSegmentEntry 1 } 690 gmplsInSegmentExtraParamsPtr OBJECT-TYPE 691 SYNTAX RowPointer 692 MAX-ACCESS read-create 693 STATUS current 694 DESCRIPTION 695 "Some Tunnels will run over transports that can usefully support 696 technology-specific additional parameters (for example, SONET 697 resource usage). Such can be supplied from an external table and 698 referenced from here. A value of zeroDotzero in this attribute 699 indicates that there is no such additional information." 700 DEFVAL { zeroDotZero } 701 ::= { gmplsInSegmentEntry 2 } 703 gmplsOutSegmentTable OBJECT-TYPE 704 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 705 MAX-ACCESS not-accessible 706 STATUS current 707 DESCRIPTION 708 "This table sparse augments the mplsOutSegmentTable of the 709 MPLS-LSR-STD-MIB to provide GMPLS-specific information about 710 outgoing segments from an LSR." 711 REFERENCE 712 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 713 Router Management Information Base (MIB), RFC 3813." 714 ::= { gmplsLsrObjects 3 } 716 gmplsOutSegmentEntry OBJECT-TYPE 717 SYNTAX GmplsOutSegmentEntry 718 MAX-ACCESS not-accessible 719 STATUS current 720 DESCRIPTION 721 "An entry in this table extends the representation of an outgoing 722 segment represented by an entry in mplsOutSegmentTable of the 723 MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be 724 created by a network administrator via SNMP SET commands, or in 725 response to signaling protocol events. 727 Note that the storage type for this entry is given by the value 728 of mplsOutSegmentStorageType in the corresponding entry of the 729 mplsOutSegmentTable." 730 REFERENCE 731 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 732 Router Management Information Base (MIB), RFC 3813." 733 INDEX { mplsOutSegmentIndex } 734 ::= { gmplsOutSegmentTable 1 } 735 GmplsOutSegmentEntry ::= SEQUENCE { 736 gmplsOutSegmentDirection GmplsSegmentDirection, 737 gmplsOutSegmentTTLDecrement Unsigned32, 738 gmplsOutSegmentExtraParamsPtr RowPointer 739 } 741 gmplsOutSegmentDirection OBJECT-TYPE 742 SYNTAX GmplsSegmentDirection 743 MAX-ACCESS read-create 744 STATUS current 745 DESCRIPTION 746 "This object indicates the direction of data flow on this 747 segment. This object cannot be modified if 748 mplsOutSegmentRowStatus for the corresponding entry in the 749 mplsOutSegmentTable is active(1)." 750 REFERENCE 751 "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) 752 Router Management Information Base (MIB), RFC 3813." 753 DEFVAL { forward } 754 ::= { gmplsOutSegmentEntry 1 } 756 gmplsOutSegmentTTLDecrement OBJECT-TYPE 757 SYNTAX Unsigned32 (0..255) 758 MAX-ACCESS read-create 759 STATUS current 760 DESCRIPTION 761 "This object indicates the amount by which to decrement the TTL 762 of any payload packets forwarded on this segment if per-hop 763 decrementing is being done. 765 A value of zero indicates that no decrement should be made or 766 that per-hop decrementing is not in use. 768 See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable 769 of GMPLS-TE-STD-MIB for a value by which to decrement the TTL 770 for the whole of a tunnel. 772 This object cannot be modified if mplsOutSegmentRowStatus for 773 the associated entry in the mplsOutSegmentTable is active(1)." 774 REFERENCE 775 "1. Time To Live (TTL) Processing in Multi-Protocol Label 776 Switching (MPLS) Networks, RFC 3443. 777 2. Generalized Multiprotocol Label Switching (GMPLS) Traffic 778 Engineering Management Information Base, RFC XXX." 779 -- RFC Editor. Please insert the correct RFC number and remove this note 780 DEFVAL { 0 } 781 ::= { gmplsOutSegmentEntry 2 } 782 gmplsOutSegmentExtraParamsPtr OBJECT-TYPE 783 SYNTAX RowPointer 784 MAX-ACCESS read-create 785 STATUS current 786 DESCRIPTION 787 "Some Tunnels will run over transports that can usefully support 788 technology-specific additional parameters (for example, SONET 789 resource usage). Such can be supplied from an external table and 790 referenced from here. 792 A value of zeroDotzero in this attribute indicates that there is 793 no such additional information." 794 DEFVAL { zeroDotZero } 795 ::= { gmplsOutSegmentEntry 3 } 797 gmplsLsrGroups 798 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 800 gmplsLsrCompliances 801 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 803 -- Compliance requirement for fully compliant implementations. 805 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 806 STATUS current 807 DESCRIPTION 808 "Compliance statement for agents that provide full support for 809 GMPLS-LSR-STD-MIB." 811 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 813 MANDATORY-GROUPS { 814 ifGeneralInformationGroup, 815 ifCounterDiscontinuityGroup 816 } 818 MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB RFC 3813 820 MANDATORY-GROUPS { 821 mplsInterfaceGroup, 822 mplsInSegmentGroup, 823 mplsOutSegmentGroup, 824 mplsXCGroup, 825 mplsPerfGroup, 826 mplsLsrNotificationGroup 827 } 828 MODULE -- this module 830 MANDATORY-GROUPS { 831 gmplsInterfaceGroup, 832 gmplsInSegmentGroup, 833 gmplsOutSegmentGroup 834 } 836 OBJECT gmplsInSegmentDirection 837 SYNTAX GmplsSegmentDirection 838 MIN-ACCESS read-write 839 DESCRIPTION 840 "Only forward(1) needs to be supported by implementations that 841 only support unidirectional LSPs." 843 OBJECT gmplsOutSegmentDirection 844 SYNTAX GmplsSegmentDirection 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 gmplsOutSegmentTTLDecrement 851 SYNTAX Unsigned32 (0..255) 852 MIN-ACCESS read-only 853 DESCRIPTION 854 "Write access is not required." 856 ::= { gmplsLsrCompliances 1 } 858 -- Compliance requirement for implementations that provide read-only 859 -- access. 861 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 862 STATUS current 863 DESCRIPTION 864 "Compliance requirement for implementations that only provide 865 read-only support for GMPLS-LSR-STD-MIB. Such devices can then 866 be monitored but cannot be configured using this MIB modules." 868 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 870 MANDATORY-GROUPS { 871 ifGeneralInformationGroup, 872 ifCounterDiscontinuityGroup 873 } 874 MODULE MPLS-LSR-STD-MIB 876 MANDATORY-GROUPS { 877 mplsInterfaceGroup, 878 mplsInSegmentGroup, 879 mplsOutSegmentGroup, 880 mplsXCGroup, 881 mplsPerfGroup 882 } 884 MODULE -- this module 886 MANDATORY-GROUPS { 887 gmplsInterfaceGroup, 888 gmplsInSegmentGroup, 889 gmplsOutSegmentGroup 890 } 892 OBJECT gmplsInterfaceSignalingCaps 893 SYNTAX BITS { 894 unknown (0), 895 rsvpGmpls (1), 896 crldpGmpls (2), 897 otherGmpls (3) 898 } 899 MIN-ACCESS read-only 900 DESCRIPTION 901 "Write access is not required." 903 OBJECT gmplsInterfaceRsvpHelloPeriod 904 SYNTAX Unsigned32 905 MIN-ACCESS read-only 906 DESCRIPTION 907 "Write access is not required." 909 OBJECT gmplsInSegmentDirection 910 SYNTAX GmplsSegmentDirection 911 MIN-ACCESS read-only 912 DESCRIPTION 913 "Write access is not required. Only forward(1) needs to be 914 supported by implementations that only support unidirectional 915 LSPs." 917 OBJECT gmplsInSegmentExtraParamsPtr 918 SYNTAX RowPointer 919 MIN-ACCESS read-only 920 DESCRIPTION 921 "Write access is not required." 923 OBJECT gmplsOutSegmentDirection 924 SYNTAX GmplsSegmentDirection 925 MIN-ACCESS read-only 926 DESCRIPTION 927 "Write access is not required. Only forward(1) needs to be 928 supported by implementations that only support unidirectional 929 LSPs." 931 OBJECT gmplsOutSegmentTTLDecrement 932 SYNTAX Unsigned32 (0..255) 933 MIN-ACCESS read-only 934 DESCRIPTION 935 "Write access is not required." 937 OBJECT gmplsOutSegmentExtraParamsPtr 938 SYNTAX RowPointer 939 MIN-ACCESS read-only 940 DESCRIPTION 941 "Write access is not required." 943 ::= { gmplsLsrCompliances 2 } 945 gmplsInterfaceGroup OBJECT-GROUP 946 OBJECTS { 947 gmplsInterfaceSignalingCaps, 948 gmplsInterfaceRsvpHelloPeriod 949 } 950 STATUS current 951 DESCRIPTION 952 "Collection of objects needed for GMPLS interface configuration 953 and performance information." 954 ::= { gmplsLsrGroups 1 } 956 gmplsInSegmentGroup OBJECT-GROUP 957 OBJECTS { 958 gmplsInSegmentDirection, 959 gmplsInSegmentExtraParamsPtr 960 } 961 STATUS current 962 DESCRIPTION 963 "Collection of objects needed to implement a GMPLS 964 in-segment." 965 ::= { gmplsLsrGroups 2 } 966 gmplsOutSegmentGroup OBJECT-GROUP 967 OBJECTS { 968 gmplsOutSegmentDirection, 969 gmplsOutSegmentTTLDecrement, 970 gmplsOutSegmentExtraParamsPtr 971 } 972 STATUS current 973 DESCRIPTION 974 "Collection of objects needed to implement a GMPLS out-segment." 975 ::= { gmplsLsrGroups 3 } 976 END 978 8. GMPLS Label MIB Definitions 980 This MIB module makes references to the following documents. 981 [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3032], [RFC3289], 982 [RFC3471], [RFC3811], [RFC3945], [RFC3946] and [GMPLSTCMIB]. 984 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 986 IMPORTS 987 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32 988 FROM SNMPv2-SMI -- RFC2578 989 MODULE-COMPLIANCE, OBJECT-GROUP 990 FROM SNMPv2-CONF -- RFC2580 991 RowStatus, StorageType 992 FROM SNMPv2-TC -- RFC2579 993 InterfaceIndexOrZero 994 FROM IF-MIB -- RFC2863 995 IndexIntegerNextFree 996 FROM DIFFSERV-MIB -- RFC3289 997 MplsLabel, mplsStdMIB 998 FROM MPLS-TC-STD-MIB -- RFC3811 999 GmplsLabelType, GmplsFreeformLabel 1000 FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB 1001 -- RFC-Editor. Please resolve the reference above to use the RFC number 1002 -- and remove this note 1003 ; 1005 gmplsLabelStdMIB MODULE-IDENTITY 1006 LAST-UPDATED 1007 "200505200001Z" -- 20 May 2005 00:00:01 GMT 1008 ORGANIZATION 1009 "IETF Common Control And Measurement Plane (CCAMP) Working Group" 1010 CONTACT-INFO 1011 " Thomas D. Nadeau 1012 Cisco Systems, Inc. 1013 Email: tnadeau@cisco.com 1014 Adrian Farrel 1015 Old Dog Consulting 1016 Email: adrian@olddog.co.uk 1018 Comments about this document should be emailed direct to the 1019 CCAMP working group mailing list at ccamp@ops.ietf.org" 1021 DESCRIPTION 1022 "Copyright (C) The Internet Society (2005). This version of 1023 this MIB module is part of RFC XXX; see the RFC itself for 1024 full legal notices. 1025 -- RFC Editor. Please replace XXX above with the correct RFC number and 1026 -- remove this note. 1028 This MIB module contains managed object definitions for labels 1029 within GMPLS systems as defined in: 1030 Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1031 Functional Description, Berger, L. (Editor), RFC 3471, 1032 January 2003." 1034 REVISION 1035 "200505200001Z" -- 20 May 2005 00:00:01 GMT 1036 DESCRIPTION 1037 "Initial version issued as part of RFC XXX." 1038 ::= { mplsStdMIB ZZZ } 1039 -- RFC Editor. Please replace XXX above with the correct RFC number and 1040 -- remove this note. 1042 -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA 1043 -- and remove this note 1045 -- no notifications are currently defined. 1047 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 1048 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 1050 gmplsLabelIndexNext OBJECT-TYPE 1051 SYNTAX IndexIntegerNextFree 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "This object contains an unused value for gmplsLabelIndex, 1056 or a zero to indicate that no unused value exists or is 1057 available. 1059 A management application wishing to create a row in the 1060 gmplsLabelTable may read this object and then attempt to 1061 create a row in the table. If row creation fails (because 1062 another application has already created a row with the 1063 supplied index) the management application should read this 1064 object again to get a new index value. 1066 When a row is created in the gmplsLabelTable with the 1067 gmplsLabelIndex value held by this object, an implementation 1068 MUST change the value in this object." 1069 ::= { gmplsLabelObjects 1 } 1071 gmplsLabelTable OBJECT-TYPE 1072 SYNTAX SEQUENCE OF GmplsLabelEntry 1073 MAX-ACCESS not-accessible 1074 STATUS current 1075 DESCRIPTION 1076 "Table of GMPLS Labels. This table allows the representation 1077 of the more complex label forms required for GMPLS which cannot 1078 be held within the textual convention MplsLabel. That is labels 1079 that cannot be encoded within 32 bits. It is, nevertheless also 1080 capable of holding 32 bit labels or regular MPLS labels if 1081 desired. 1083 Each entry in this table represents an individual GMPLS label 1084 value. Labels in the tables in other MIB modules may be referred 1085 to using row pointer into this table. The indexing of this table 1086 provides for arbitrary indexing and also for concatenation of 1087 labels. 1089 For an example of label concatenation see RFC3945 section 7.1. 1090 In essence, a GMPLS label may be composite in order to identify 1091 a set of resources in the data plane. Practial examples are 1092 timeslots and wavelength sets (which are not contiguous like 1093 wavebands). 1095 The indexing mechanism allows multiple entries in this table to 1096 be seen as a sequence of labels that should be concatenated. 1097 Ordering is potentially very sensitive for concatenation." 1098 REFERENCE 1099 "1. Generalized Multiprotocol Label Switching (GMPLS) 1100 Architecture, RFC 3945, section 7.1," 1101 ::= { gmplsLabelObjects 2 } 1103 gmplsLabelEntry OBJECT-TYPE 1104 SYNTAX GmplsLabelEntry 1105 MAX-ACCESS not-accessible 1106 STATUS current 1107 DESCRIPTION 1108 "An entry in this table represents a single label value. There 1109 are three indexes into the table. 1110 - The interface index may be helpful to distinguish which 1111 labels are in use on which interfaces or to handle cases 1112 where there are a very large number of labels in use in the 1113 system. When label representation is desired to apply to the 1114 whole system or when it is not important to distinguish 1115 labels by their interfaces, this index MAY be set to zero. 1117 - The label index provides a way of identifying the label. 1118 - The label sub-index is only used for concatenated labels. It 1119 identifies each component label. When non-concatenated labels 1120 are used, this index SHOULD be set to zero. 1121 A storage type object is supplied to control the storage type 1122 for each entry, but implementations should note that the storage 1123 type of conceptual rows in other tables that include row 1124 pointers to an entry in this table SHOULD dictate the storage 1125 type of the rows in this table where the row in the other table 1126 is more persistent." 1127 INDEX { 1128 gmplsLabelInterface, 1129 gmplsLabelIndex, 1130 gmplsLabelSubindex } 1131 ::= { gmplsLabelTable 1 } 1133 GmplsLabelEntry ::= SEQUENCE { 1134 gmplsLabelInterface InterfaceIndexOrZero, 1135 gmplsLabelIndex Unsigned32, 1136 gmplsLabelSubindex Unsigned32, 1137 gmplsLabelType GmplsLabelType, 1138 gmplsLabelMplsLabel MplsLabel, 1139 gmplsLabelPortWavelength Unsigned32, 1140 gmplsLabelFreeform GmplsFreeformLabel, 1141 gmplsLabelSonetSdhSignalIndex Integer32, 1142 gmplsLabelSdhVc Integer32, 1143 gmplsLabelSdhVcBranch Integer32, 1144 gmplsLabelSonetSdhBranch Integer32, 1145 gmplsLabelSonetSdhGroupBranch Integer32, 1146 gmplsLabelWavebandId Unsigned32, 1147 gmplsLabelWavebandStart Unsigned32, 1148 gmplsLabelWavebandEnd Unsigned32, 1149 gmplsLabelStorageType StorageType, 1150 gmplsLabelRowStatus RowStatus 1151 } 1152 gmplsLabelInterface OBJECT-TYPE 1153 SYNTAX InterfaceIndexOrZero 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "The interface on which this label is used. If this object is set 1158 to zero, the label has or could have applicability across the 1159 whole system and is not limited to a single interface." 1160 ::= { gmplsLabelEntry 1 } 1162 gmplsLabelIndex OBJECT-TYPE 1163 SYNTAX Unsigned32 (0..4294967295) 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "An arbitrary index into the table to identify a label. 1169 Note that implementations that are representing 32 bit labels 1170 within this table MAY choose to align this index with the value 1171 of the label and this may result in the use of the value zero. 1172 Such implementation should be aware of the implications of 1173 sparsely populated tables. 1175 A management application may read the gmplsLabelIndexNext 1176 object to find a suitable value for this object." 1177 ::= { gmplsLabelEntry 2 } 1179 gmplsLabelSubindex OBJECT-TYPE 1180 SYNTAX Unsigned32 (0..4294967295) 1181 MAX-ACCESS not-accessible 1182 STATUS current 1183 DESCRIPTION 1184 "In conjunction with gmplsLabelInterface and gmplsLabelIndex, 1185 this object uniquely identifies this row. This sub-index allows 1186 a single GMPLS label to be defined as a concatenation of labels. 1187 This is particularly useful in TDM. 1189 The ordering of sub-labels is strict with the sub-label with 1190 lowest gmplsLabelSubindex appearing first. Note that all 1191 sub-labels of a single GMPLS label must share the same 1192 gmplsLabelInterface and gmplsLabelIndex values. For labels that 1193 are not composed of concatenated sub-labels, this value SHOULD 1194 be set to zero." 1195 ::= { gmplsLabelEntry 3 } 1196 gmplsLabelType OBJECT-TYPE 1197 SYNTAX GmplsLabelType 1198 MAX-ACCESS read-create 1199 STATUS current 1200 DESCRIPTION 1201 "Identifies the type of this label. Note that this object does 1202 not determine whether MPLS or GMPLS signaling is in use: a value 1203 of gmplsMplsLabel (1) denotes that an MPLS packet label is 1204 present in the gmplsLabelMplsLabel object and encoded using the 1205 MplsLabel textual convention (may be a 20-bit MPLS label, a 10- 1206 or 23-bit Frame Relay label, or an ATM label), but does not 1207 describe whether this is signaled using MPLS or GMPLS. 1209 The value of this object helps determine which of the following 1210 objects are valid. This object cannot be modified if 1211 gmplsLabelRowStatus is active(1)." 1212 REFERENCE 1213 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1214 Functional Description, RFC 3471, section 3." 1215 ::= { gmplsLabelEntry 4 } 1217 gmplsLabelMplsLabel OBJECT-TYPE 1218 SYNTAX MplsLabel 1219 MAX-ACCESS read-create 1220 STATUS current 1221 DESCRIPTION 1222 "The value of an MPLS label (that is a packet label) if this 1223 table is used to store it. This may be used in MPLS systems even 1224 though the label values can be adequately stored in the MPLS MIB 1225 modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Further, in 1226 mixed MPLS and GMPLS systems it may be advantageous to store all 1227 labels in a single label table. Lastly, in GMPLS systems where 1228 packet labels are used (that is in systems that use GMPLS 1229 signaling and GMPLS labels for packet switching) it may be 1230 desirable to use this table. 1232 This object is only valid if gmplsLabelType is set 1233 to gmplsMplsLabel (1). This object cannot be modified if 1234 gmplsLabelRowStatus is active(1)." 1235 REFERENCE 1236 "1. MPLS Label Stack Encoding, RFC 3032." 1237 DEFVAL { 0 } 1238 ::= { gmplsLabelEntry 5 } 1239 gmplsLabelPortWavelength OBJECT-TYPE 1240 SYNTAX Unsigned32 1241 MAX-ACCESS read-create 1242 STATUS current 1243 DESCRIPTION 1244 "The value of a Port or Wavelength Label when carried as a 1245 Generalized Label. Only valid if gmplsLabelType is set to 1246 gmplsPortWavelengthLabel(2). This object cannot be modified if 1247 gmplsLabelRowStatus is active(1)." 1248 REFERENCE 1249 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1250 Functional Description, RFC 3471, section 3.2.1.1." 1251 DEFVAL { 0 } 1252 ::= { gmplsLabelEntry 6 } 1254 gmplsLabelFreeform OBJECT-TYPE 1255 SYNTAX GmplsFreeformLabel 1256 MAX-ACCESS read-create 1257 STATUS current 1258 DESCRIPTION 1259 "The value of a freeform Generalized Label that does not conform 1260 to one of the standardized label encoding or that an 1261 implementation chooses to represent as an octet string without 1262 further decoding. Only valid if gmplsLabelType is set to 1263 gmplsFreeformLabel(3). This object cannot be modified 1264 if gmplsLabelRowStatus is active(1)." 1265 REFERENCE 1266 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1267 Functional Description, RFC 3471, section 3.2." 1268 DEFVAL { '' } 1269 ::= { gmplsLabelEntry 7 } 1271 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 1272 SYNTAX Integer32 (0..4095) 1273 MAX-ACCESS read-create 1274 STATUS current 1275 DESCRIPTION 1276 "The Signal Index value (S) of a SONET or SDH Generalized Label. 1277 Zero indicates that this field is not significant. Only valid if 1278 gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1279 This object cannot be modified if gmplsLabelRowStatus is 1280 active(1)." 1281 REFERENCE 1282 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1283 for Synchronous Optical Network (SONET) and Synchronous 1284 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1285 DEFVAL { 0 } 1286 ::= { gmplsLabelEntry 8 } 1287 gmplsLabelSdhVc OBJECT-TYPE 1288 SYNTAX Integer32 (0..15) 1289 MAX-ACCESS read-create 1290 STATUS current 1291 DESCRIPTION 1292 "The VC Indicator (U) of an SDH Generalized Label. Zero indicates 1293 that this field is non-significant. 1294 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). 1295 This object cannot be modified if gmplsLabelRowStatus is 1296 active(1)." 1297 REFERENCE 1298 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1299 for Synchronous Optical Network (SONET) and Synchronous 1300 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1301 DEFVAL { 0 } 1302 ::= { gmplsLabelEntry 9 } 1304 gmplsLabelSdhVcBranch OBJECT-TYPE 1305 SYNTAX Integer32 (0..15) 1306 MAX-ACCESS read-create 1307 STATUS current 1308 DESCRIPTION 1309 "The VC Branch Indicator (K) of an SDH Generalized Label. Zero 1310 indicates that this field is non-significant. 1311 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This 1312 object cannot be modified if gmplsLabelRowStatus is active(1)." 1313 REFERENCE 1314 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1315 for Synchronous Optical Network (SONET) and Synchronous 1316 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1317 DEFVAL { 0 } 1318 ::= { gmplsLabelEntry 10 } 1320 gmplsLabelSonetSdhBranch OBJECT-TYPE 1321 SYNTAX Integer32 (0..15) 1322 MAX-ACCESS read-create 1323 STATUS current 1324 DESCRIPTION 1325 "The Branch Indicator (L) of a SONET or SDH Generalized Label. 1326 Zero indicates that this field is non-significant. 1327 Only valid gmplsLabelType is set to gmplsSonetLabel(4) or 1328 gmplsSdhLabel(5). This object cannot be modified if 1329 gmplsLabelRowStatus is active(1)." 1330 REFERENCE 1331 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1332 for Synchronous Optical Network (SONET) and Synchronous 1333 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1334 DEFVAL { 0 } 1335 ::= { gmplsLabelEntry 11 } 1336 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1337 SYNTAX Integer32 (0..15) 1338 MAX-ACCESS read-create 1339 STATUS current 1340 DESCRIPTION 1341 "The Group Branch Indicator (M) of a SONET or SDH Generalized 1342 Label. 1343 Zero indicates that this field is non-significant. 1344 Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or 1345 gmplsSdhLabel(5). This object cannot be modified if 1346 gmplsLabelRowStatus is active(1)." 1347 REFERENCE 1348 "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 1349 for Synchronous Optical Network (SONET) and Synchronous 1350 Digital Hierarchy (SDH) Control, RFC 3946, section 3." 1351 DEFVAL { 0 } 1352 ::= { gmplsLabelEntry 12 } 1354 gmplsLabelWavebandId OBJECT-TYPE 1355 SYNTAX Unsigned32 1356 MAX-ACCESS read-create 1357 STATUS current 1358 DESCRIPTION 1359 "The waveband identifier component of a waveband label. Only 1360 valid if gmplsLabelType is set to gmplsWavebandLabel(6). This 1361 object cannot be modified if gmplsLabelRowStatus is active(1)." 1362 REFERENCE 1363 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1364 Functional Description, RFC 3471, section 3.3." 1365 DEFVAL { 0 } 1366 ::= { gmplsLabelEntry 13 } 1368 gmplsLabelWavebandStart OBJECT-TYPE 1369 SYNTAX Unsigned32 1370 MAX-ACCESS read-create 1371 STATUS current 1372 DESCRIPTION 1373 "The starting label component of a waveband label. 1374 Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). 1375 This object cannot be modified if 1376 gmplsLabelRowStatus is active(1)." 1377 REFERENCE 1378 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1379 Functional Description, RFC 3471, section 3.3." 1380 DEFVAL { 0 } 1381 ::= { gmplsLabelEntry 14 } 1382 gmplsLabelWavebandEnd OBJECT-TYPE 1383 SYNTAX Unsigned32 1384 MAX-ACCESS read-create 1385 STATUS current 1386 DESCRIPTION 1387 "The end label component of a waveband label. Only valid if 1388 gmplsLabelType is set to gmplsWavebandLabel(6). This object 1389 cannot be modified if gmplsLabelRowStatus is active(1)." 1390 REFERENCE 1391 "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling 1392 Functional Description, RFC 3471, section 3.3." 1393 DEFVAL { 0 } 1394 ::= { gmplsLabelEntry 15 } 1396 gmplsLabelStorageType OBJECT-TYPE 1397 SYNTAX StorageType 1398 MAX-ACCESS read-create 1399 STATUS current 1400 DESCRIPTION 1401 "This variable indicates the storage type for this object. The 1402 agent MUST ensure that this object's value remains consistent 1403 with the storage type of any rows in other tables that contain 1404 pointers to this row. In particular, the storage type of this 1405 row must be at least as permanent as that of any row that point 1406 to it. 1408 Conceptual rows having the value 'permanent' need not 1409 allow write-access to any columnar objects in the row." 1410 REFERENCE 1411 "1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2." 1412 DEFVAL { volatile } 1413 ::= { gmplsLabelEntry 16 } 1415 gmplsLabelRowStatus OBJECT-TYPE 1416 SYNTAX RowStatus 1417 MAX-ACCESS read-create 1418 STATUS current 1419 DESCRIPTION 1420 "This variable is used to create, modify, and/or delete a row in 1421 this table. When a row in this table has a row in the active(1) 1422 state, no objects in this row can be modified except the 1423 gmplsLabelRowStatus and gmplsLabelStorageType. 1425 The gmplsLabelType object does not have a default and must be 1426 set before a row can become active. The corresponding label 1427 objects (dependent on the value of gmplsLabelType) should also 1428 be set unless they happen to need to use the specified default 1429 values as follows: 1431 gmplsLabelType setting objects to be set 1432 -------------------------------------------------------------- 1433 gmplsMplsLabel(1) gmplsLabelMplsLabel 1435 gmplsPortWavelengthLabel(2) gmplsLabelPortWavelength 1437 gmplsFreeformLabel(3) gmplsLabelFreeform 1439 gmplsSonetLabel(4) gmplsLabelSonetSdhSignalIndex 1440 gmplsLabelSdhVc 1441 gmplsLabelSdhVcBranch 1442 gmplsLabelSonetSdhBranch 1443 gmplsLabelSonetSdhGroupBranch 1445 gmplsSdhLabel(5) gmplsLabelSonetSdhSignalIndex 1446 gmplsLabelSdhVc 1447 gmplsLabelSdhVcBranch 1448 gmplsLabelSonetSdhBranch 1449 gmplsLabelSonetSdhGroupBranch 1451 gmplsWavebandLabel(6) gmplsLabelWavebandId 1452 gmplsLabelWavebandStart 1453 gmplsLabelWavebandEnd" 1454 ::= { gmplsLabelEntry 17 } 1456 gmplsLabelGroups 1457 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1459 gmplsLabelCompliances 1460 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1462 gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE 1463 STATUS current 1464 DESCRIPTION 1465 "Compliance requirement for implementations that only provide 1466 read-only support for GMPLS-LABEL-STD-MIB. Such devices can then 1467 be monitored but cannot be configured using this MIB module." 1469 MODULE -- this module 1471 -- The mandatory groups have to be implemented by LSRs claiming 1472 -- support for this MIB module. This MIB module is, however, not 1473 -- mandatory for a working implementation of a GMPLS LSR with full 1474 -- MIB support if the GMPLS labels in use can be represented within 1475 -- a 32 bit quantity. 1477 MANDATORY-GROUPS { 1478 gmplsLabelTableGroup 1479 } 1480 GROUP gmplsLabelTableGroup 1481 DESCRIPTION 1482 "This group is mandatory for devices which support the 1483 gmplsLabelTable." 1485 GROUP gmplsLabelPacketGroup 1486 DESCRIPTION 1487 "This group extends gmplsLabelTableGroup for implementations that 1488 support packet labels." 1490 GROUP gmplsLabelPortWavelengthGroup 1491 DESCRIPTION 1492 "This group extends gmplsLabelTableGroup for implementations that 1493 support port and wavelength labels." 1495 GROUP gmplsLabelFreeformGroup 1496 DESCRIPTION 1497 "This group extends gmplsLabelTableGroup for implementations that 1498 support freeform labels." 1500 GROUP gmplsLabelSonetSdhGroup 1501 DESCRIPTION 1502 "This group extends gmplsLabelTableGroup for implementations that 1503 support SONET or SDH labels." 1505 GROUP gmplsLabelWavebandGroup 1506 DESCRIPTION 1507 "This group extends gmplsLabelTableGroup for implementations that 1508 support Waveband labels." 1510 OBJECT gmplsLabelType 1511 MIN-ACCESS read-only 1512 DESCRIPTION 1513 "Write access is not required." 1515 OBJECT gmplsLabelMplsLabel 1516 MIN-ACCESS read-only 1517 DESCRIPTION 1518 "Write access is not required." 1520 OBJECT gmplsLabelPortWavelength 1521 MIN-ACCESS read-only 1522 DESCRIPTION 1523 "Write access is not required." 1525 OBJECT gmplsLabelFreeform 1526 MIN-ACCESS read-only 1527 DESCRIPTION 1528 "Write access is not required." 1530 OBJECT gmplsLabelSonetSdhSignalIndex 1531 MIN-ACCESS read-only 1532 DESCRIPTION 1533 "Write access is not required." 1535 OBJECT gmplsLabelSdhVc 1536 MIN-ACCESS read-only 1537 DESCRIPTION 1538 "Write access is not required." 1540 OBJECT gmplsLabelSdhVcBranch 1541 MIN-ACCESS read-only 1542 DESCRIPTION 1543 "Write access is not required." 1545 OBJECT gmplsLabelSonetSdhBranch 1546 MIN-ACCESS read-only 1547 DESCRIPTION 1548 "Write access is not required." 1550 OBJECT gmplsLabelSonetSdhGroupBranch 1551 MIN-ACCESS read-only 1552 DESCRIPTION 1553 "Write access is not required." 1555 OBJECT gmplsLabelWavebandId 1556 MIN-ACCESS read-only 1557 DESCRIPTION 1558 "Write access is not required." 1560 OBJECT gmplsLabelWavebandStart 1561 MIN-ACCESS read-only 1562 DESCRIPTION 1563 "Write access is not required." 1565 OBJECT gmplsLabelWavebandEnd 1566 MIN-ACCESS read-only 1567 DESCRIPTION 1568 "Write access is not required." 1570 OBJECT gmplsLabelStorageType 1571 MIN-ACCESS read-only 1572 DESCRIPTION 1573 "Write access is not required." 1575 OBJECT gmplsLabelRowStatus 1576 SYNTAX RowStatus { 1577 active(1), 1578 notInService(2) 1579 } 1581 WRITE-SYNTAX RowStatus { 1582 active(1), 1583 notInService(2), 1584 createAndGo(4), 1585 destroy(6) 1586 } 1587 DESCRIPTION 1588 "Support for notInService, createAndWait and notReady is not 1589 required." 1591 ::= { gmplsLabelCompliances 1 } 1593 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1594 STATUS current 1595 DESCRIPTION 1596 "Compliance statement for agents that support the complete 1597 GMPLS-LABEL-STD-MIB module." 1599 MODULE -- this module 1601 -- The mandatory groups have to be implemented by GMPLS LSRs 1602 -- claiming support for this MIB module. This MIB module is, 1603 -- however, not mandatory for a working implementation of a GMPLS 1604 -- LSR with full MIB support if the GMPLS labels in use can be 1605 -- represented within a 32 bit quantity. 1607 MANDATORY-GROUPS { 1608 gmplsLabelTableGroup, 1609 gmplsLabelPacketGroup, 1610 gmplsLabelPortWavelengthGroup, 1611 gmplsLabelFreeformGroup, 1612 gmplsLabelSonetSdhGroup, 1613 gmplsLabelWavebandGroup 1614 } 1616 OBJECT gmplsLabelRowStatus 1617 SYNTAX RowStatus { active(1), notInService(2) } 1618 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1619 createAndGo(4), destroy(6) } 1620 DESCRIPTION 1621 "Support for notInService, createAndWait and notReady is not 1622 required." 1623 ::= { gmplsLabelCompliances 2 } 1624 gmplsLabelTableGroup OBJECT-GROUP 1625 OBJECTS { 1626 gmplsLabelIndexNext, 1627 gmplsLabelType, 1628 gmplsLabelStorageType, 1629 gmplsLabelRowStatus 1630 } 1632 STATUS current 1633 DESCRIPTION 1634 "Necessary, but not sufficient, set of objects to implement label 1635 table support. In addition, depending on the type of labels 1636 supported (for example, wavelength labels), the following other 1637 groups defined below are mandatory: 1638 gmplsLabelPacketGroup and/or 1639 gmplsLabelPortWavelengthGroup and/or 1640 gmplsLabelFreeformGroup and/or 1641 gmplsLabelSonetSdhGroup." 1642 ::= { gmplsLabelGroups 1 } 1644 gmplsLabelPacketGroup OBJECT-GROUP 1645 OBJECTS { 1646 gmplsLabelMplsLabel 1647 } 1648 STATUS current 1649 DESCRIPTION 1650 "Object needed to implement Packet (MPLS) labels." 1651 ::= { gmplsLabelGroups 2 } 1653 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1654 OBJECTS { 1655 gmplsLabelPortWavelength 1656 } 1657 STATUS current 1658 DESCRIPTION 1659 "Object needed to implement Port and Wavelength labels." 1660 ::= { gmplsLabelGroups 3 } 1662 gmplsLabelFreeformGroup OBJECT-GROUP 1663 OBJECTS { 1664 gmplsLabelFreeform 1665 } 1666 STATUS current 1667 DESCRIPTION 1668 "Object needed to implement Freeform labels." 1669 ::= { gmplsLabelGroups 4 } 1670 gmplsLabelSonetSdhGroup OBJECT-GROUP 1671 OBJECTS { 1672 gmplsLabelSonetSdhSignalIndex, 1673 gmplsLabelSdhVc, 1674 gmplsLabelSdhVcBranch, 1675 gmplsLabelSonetSdhBranch, 1676 gmplsLabelSonetSdhGroupBranch 1677 } 1678 STATUS current 1679 DESCRIPTION 1680 "Object needed to implement SONET and SDH labels." 1681 ::= { gmplsLabelGroups 5 } 1683 gmplsLabelWavebandGroup OBJECT-GROUP 1684 OBJECTS { 1685 gmplsLabelWavebandId, 1686 gmplsLabelWavebandStart, 1687 gmplsLabelWavebandEnd 1688 } 1689 STATUS current 1690 DESCRIPTION 1691 "Object needed to implement Waveband labels." 1692 ::= { gmplsLabelGroups 6 } 1693 END 1695 9. Security Considerations 1697 It is clear that the MIB modules described in this document in 1698 association with the MPLS-LSR-STD-MIB [RFC3813] are potentially 1699 useful for monitoring of GMPLS LSRs. These MIB modules can also be 1700 used for configuration of certain objects, and anything that can be 1701 configured can be incorrectly configured, with potentially disastrous 1702 results. 1704 There are a number of management objects defined in these MIB modules 1705 with a MAX-ACCESS clause of read-write and/or read-create. Such 1706 objects may be considered sensitive or vulnerable in some network 1707 environments. The support for SET operations in a non-secure 1708 environment without proper protection can have a negative effect on 1709 network operations. These are the tables and objects and their 1710 sensitivity/vulnerability: 1712 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1713 and gmplsLabelTable collectively contain objects to provision 1714 GMPLS interfaces, LSPs and their associated parameters on a Label 1715 Switching Router (LSR). Unauthorized write access to objects in 1716 these tables, could result in disruption of traffic on the 1717 network. This is especially true if an LSP has already been 1718 established. 1720 Some of the readable objects in these MIB modules (i.e., objects with 1721 a MAX-ACCESS other than not-accessible) may be considered sensitive 1722 or vulnerable in some network environments. It is thus important to 1723 control even GET and/or NOTIFY access to these objects and possibly 1724 to even encrypt the values of these objects when sending them over 1725 the network via SNMP. These are the tables and objects and their 1726 sensitivity/vulnerability: 1728 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1729 and gmplsLabelTable collectively show the LSP network topology and 1730 its capabilities. If an Administrator does not want to reveal this 1731 information, then these tables should be considered 1732 sensitive/vulnerable. 1734 SNMP versions prior to SNMPv3 did not include adequate security. Even 1735 if the network itself is secure (for example by using IPSec), even 1736 then, there is no control as to who on the secure network is allowed 1737 to access and GET/SET (read/change/create/delete) the objects in 1738 these MIB modules. 1740 It is RECOMMENDED that implementers consider the security features as 1741 provided by the SNMPv3 framework (see [RFC3410], section 8), 1742 including full support for the SNMPv3 cryptographic mechanisms (for 1743 authentication and privacy). 1745 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1746 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1747 enable cryptographic security. It is then a customer/operator 1748 responsibility to ensure that the SNMP entity giving access to an 1749 instance of this MIB module, is properly configured to give access to 1750 the objects only to those principals (users) that have legitimate 1751 rights to indeed GET or SET (change/create/delete) them. 1753 10. Acknowledgments 1755 This document is a product of the CCAMP Working Group. 1757 This document extends [RFC3813]. The authors would like to express 1758 their gratitude to all those who worked on that earlier MIB document. 1760 The authors would like to express their thanks to Dan Joyle for his 1761 careful review and comments on early versions of the Label Table. 1762 Special thanks to Joan Cucchiara and Len Nieman for their help with 1763 compilation issues. Tom Petch and Bert Wijnen provided useful input 1764 in the final stages of review. 1766 Joan Cucchiara provided a helpful and very thorough MIB Doctor 1767 review. 1769 11. IANA Considerations 1771 -- (Note to RFC-Editor:) 1772 -- We request that you assign contiguous RFC numbers to the three GMPLS 1773 -- MIB documents. 1774 -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to 1775 -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to 1776 -- draft-ietf-ccamp-gmpls-te-mib. 1777 -- (Please remove this note prior to publication.) 1779 IANA is requested to root MIB objects in the two MIB modules 1780 contained in this document under the mplsStdMIB subtree. 1782 In the future, GMPLS related standards track MIB modules should be 1783 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to 1784 manage that namespace in the SMI Numbers registry [RFC3811]. New 1785 assignments can only be made via a Standards Action as specified in 1786 [RFC2434]. 1788 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 1790 The IANA is requested to assign { mplsStdMIB YYY } to the 1791 GMPLS-LSR-STD-MIB module specified in this document, and to record 1792 the assignment in the SMI Numbers registry. 1794 -- RFC Editor. Please replace YYY above with the OID assigned by IANA 1795 -- and remove this note 1797 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 1799 The IANA is requested to assign { mplsStdMIB ZZZ } to the 1800 GMPLS-LABEL-STD-MIB module specified in this document, and to record 1801 the assignment in the SMI Numbers registry. 1803 -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA 1804 -- and remove this note 1806 12. References 1808 12.1. Normative References 1810 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1811 Requirements Levels", BCP 14, RFC 2119, March 1997. 1813 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1814 J., Rose, M., and S. Waldbusser, "Structure of 1815 Management Information Version 2 (SMIv2)", STD 58, RFC 1816 2578, April 1999. 1818 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1819 J., Rose, M., and S. Waldbusser, "Textual Conventions 1820 for SMIv2", STD 58, RFC 2579, April 1999. 1822 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1823 J., Rose, M., and S. Waldbusser, "Conformance Statements 1824 for SMIv2", STD 58, RFC 2580, April 1999. 1826 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1827 MIB", RFC 2863, June 2000. 1829 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1830 "Multiprotocol Label Switching Architecture", RFC 3031, 1831 January 2001. 1833 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 1834 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 1835 Encoding", RFC 3032, January 2001. 1837 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 1838 V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 1839 Tunnels", RFC 3209, December 2001. 1841 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1842 Information Base for the Differentiated Services 1843 Architecture", RFC 3289, May 2002. 1845 [RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL) 1846 Processing in Multi-Protocol Label Switching (MPLS) 1847 Networks", RFC 3443, January 2003. 1849 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 1850 (GMPLS) Signaling Functional Description", RFC 3471, 1851 January 2003. 1853 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 1854 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1855 Engineering (RSVP-TE) Extensions", RFC 3473, January 1856 2003. 1858 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1859 Conventions and for Multiprotocol Label Switching (MPLS) 1860 Management", RFC 3811, June 2004. 1862 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1863 "Multiprotocol Label Switching (MPLS) Label Switching 1864 (LSR) Router Management Information Base (MIB)", RFC 1865 3813, June 2004. 1867 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 1868 Switching (GMPLS) Architecture", RFC 3945, October 2004. 1870 [RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi- 1871 Protocol Label Switching (GMPLS) Extensions for 1872 Synchronous Optical Network (SONET) and Synchronous 1873 Digital Hierarchy (SDH) Control", RFC 3946, October 1874 2004. 1876 [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual 1877 Conventions for Multiprotocol Label Switching (MPLS) 1878 Management", draft-ietf-ccamp-gmpls-tc-mib, work in 1879 progress. 1881 [GMPLSTEMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 1882 Label Switching (GMPLS) Traffic Engineering Management 1883 Information Base", draft-ietf-ccamp-gmpls-te-mib, work 1884 in progress. 1886 12.2. Informative References 1888 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1889 "Introduction and Applicability Statements for 1890 Internet-Standard Management Framework", RFC 3410, 1891 December 2002. 1893 [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized 1894 Multi-Protocol Label Switching (MPLS) Signaling 1895 - Constraint-based Routed Label Distribution Protocol 1896 (CR-LDP) Extensions", RFC 3472, January 2003. 1898 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1899 "Multiprotocol Label Switching (MPLS) Traffic 1900 Engineering (TE) Management Information Base (MIB)", 1901 RFC 3812, June 2004. 1903 13. Contact Information 1905 Thomas D. Nadeau 1906 Cisco Systems, Inc. 1907 1414 Massachusetts Ave. 1908 Boxborough, MA 01719 1909 Email: tnadeau@cisco.com 1911 Adrian Farrel 1912 Old Dog Consulting 1913 Phone: +44-(0)-1978-860944 1914 Email: adrian@olddog.co.uk 1915 Cheenu Srinivasan 1916 Bloomberg L.P. 1917 731 Lexington Ave. 1918 New York, NY 10022 1919 Phone: +1-212-617-3682 1920 Email: cheenu@bloomberg.net 1922 Tim Hall 1923 Data Connection Ltd. 1924 100 Church Street 1925 Enfield, Middlesex, EN2 6BQ, UK 1926 Phone: +44 20 8366 1177 1927 Email: tim.hall@dataconnection.com 1929 Ed Harrison 1930 Data Connection Ltd. 1931 100 Church Street 1932 Enfield, Middlesex, EN2 6BQ, UK 1933 Phone: +44 20 8366 1177 1934 Email: ed.harrison@dataconnection.com 1936 14. Intellectual Property Considerations 1938 The IETF takes no position regarding the validity or scope of any 1939 Intellectual Property Rights or other rights that might be claimed to 1940 pertain to the implementation or use of the technology described in 1941 this document or the extent to which any license under such rights 1942 might or might not be available; nor does it represent that it has 1943 made any independent effort to identify any such rights. Information 1944 on the procedures with respect to rights in RFC documents can be 1945 found in BCP 78 and BCP 79. 1947 Copies of IPR disclosures made to the IETF Secretariat and any 1948 assurances of licenses to be made available, or the result of an 1949 attempt made to obtain a general license or permission for the use of 1950 such proprietary rights by implementers or users of this 1951 specification can be obtained from the IETF on-line IPR repository at 1952 http://www.ietf.org/ipr. 1954 The IETF invites any interested party to bring to its attention any 1955 copyrights, patents or patent applications, or other proprietary 1956 rights that may cover technology that may be required to implement 1957 this standard. Please address the information to the IETF at ietf- 1958 ipr@ietf.org. 1960 15. Full Copyright Statement 1962 Copyright (C) The Internet Society (2005). This document is subject 1963 to the rights, licenses and restrictions contained in BCP 78, and 1964 except as set forth therein, the authors retain all their rights. 1966 This document and the information contained herein are provided on an 1967 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1968 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1969 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1970 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1971 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1972 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.