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