idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-01.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. == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 31 longer pages, the longest (page 14) being 63 lines 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 (August 2003) is 7554 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: 'RFC2434' is mentioned on line 1424, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2863' is defined on line 1458, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 1461, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 1465, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 1469, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 1477, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 1509, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 1512, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 1520, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1529, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 1534, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSonetSDH' -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-01 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-01 -- Duplicate reference: draft-ietf-ccamp-gmpls-te-mib, mentioned in 'GMPLSTCMIB', was also mentioned in 'GMPLSTEMIB'. Summary: 3 errors (**), 0 flaws (~~), 18 warnings (==), 7 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: February 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 August 2003 17 Generalized Multiprotocol Label Switching (GMPLS) 18 Label Switching Router (LSR) Management Information Base 20 draft-ietf-ccamp-gmpls-lsr-mib-01.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 (LSRs). 48 Table of Contents 50 1. Introduction 2 51 1.1. Migration Strategy 2 52 2. Terminology 3 53 3. The SNMP Management Framework 3 54 4. Outline 3 55 4.1. Summary of the GMPLS LSR MIB Module 4 56 5. Bidirectional LSPs 4 57 6. Example of LSP Setup 5 58 7. GMPLS Label Switching Router MIB Definitions 6 59 8. GMPLS Label MIB Definitions 14 60 9. Security Considerations 25 61 10. Acknowledgments 26 62 11. IANA Considerations 27 63 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 27 64 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB 27 65 12. References 27 66 12.1. Normative References 27 67 12.2. Informational References 28 68 13. Authors' Addresses 29 69 14. Full Copyright Statement 30 70 15. Intellectual Property Notice 30 71 16. Changes and Pending Work 31 72 16.1. Pending Work 31 74 1. Introduction 76 This memo defines a portion of the Management Information Base (MIB) 77 for use with network management protocols in the Internet community. 78 In particular, it describes managed objects for modeling a 79 Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label 80 Switching Router (LSR). 82 Comments should be made directly to the CCAMP mailing list at 83 ccamp@ops.ietf.org. 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in RFC 2119, reference 88 [RFC2119]. 90 1.1. Migration Strategy 92 This MIB module extends the Label Switching Router MIB module defined 93 for use with MPLS [LSRMIB]. The only changes made are additions for 94 support of GMPLS or changes that are necessary to support the 95 increased complexity of a GMPLS system. 97 The companion document modeling and managing GMPLS based traffic 98 engineering [GMPLSTEMIB] extends the MPLS TE MIB module [TEMIB] with 99 the same intentions. 101 Textual conventions and OBJECT-IDENTIFIERS are defined in 102 [GMPLSTCMIB] which extends the set of textual conventions originally 103 defined in [TCMIB]. 105 2. Terminology 107 This document uses terminology from the document describing the MPLS 108 architecture [RFC3031] and the GMPLS architecture [GMPLSArch]. 110 A label switched path (LSP) is modeled as a connection consisting of 111 one or more incoming segments (in-segments) and/or one or more 112 outgoing segments (out-segments) at an LSR. The association or 113 interconnection of the in-segments and out-segments is accomplished 114 by using a cross-connect. We use the terminology "connection" and 115 "LSP" interchangeably where the meaning is clear from the context. 117 in-segment This is analogous to a GMPLS label on an interface. 118 out-segment This is analogous to a GMPLS label on an interface. 119 cross-connect This describes the conceptual connection between a 120 set of in-segments and out-segments. 121 Note that either set may be 0; that is, a cross- 122 connect may connect only out-segments together with 123 no in-segments in the case where an LSP is 124 originating on an LSR. 126 3. The SNMP Management Framework 128 For a detailed overview of the documents that describe the current 129 Internet-Standard Management Framework, please refer to section 7 of 130 RFC 3410 [RFC3410]. 132 Managed objects are accessed via a virtual information store, termed 133 the Management Information Base or MIB. MIB objects are generally 134 accessed through the Simple Network Management Protocol (SNMP). 135 Objects in the MIB are defined using the mechanisms defined in the 136 Structure of Management Information (SMI). This memo specifies a 137 MIB module that is compliant to the SMIv2, which is described in STD 138 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 139 2580 [RFC2580]. 141 4. Outline 143 Configuring statically provisioned GMPLS LSPs through an LSR involves 144 the following steps: 146 - Configuring an interface using the MPLS LSR MIB module. 148 - Enabling GMPLS on GMPLS capable interfaces using this MIB module. 150 - Configuring in-segments and out-segments using the MPLS LSR MIB 151 module. 153 - Configuring GMPLS extensions to the in-segments and out-segments 154 using this MIB module. 156 - Setting up the cross-connect table in the MPLS LSR MIB module to 157 associate segments and/or to indicate connection origination and 158 termination. 160 - Optionally setting up labels in the label table in this MIB module 161 if the textual convention 162 MplsLabel is not capable of holding the required label (for 163 example, if the label requires more than 32 bits to encode it), or 164 if the operator wishes to disambiguate GMPLS label types. 166 - Optionally specifying label stack actions in the MPLS LSR MIB 167 module. 169 - Optionally specifying segment traffic parameters in the MPLS LSR 170 MIB module. 172 4.1. Summary of the GMPLS LSR MIB Module 174 The MIB tables in this MIB module are as follows. 176 - The interface configuration table (gmplsInterfaceTable), which 177 extends mplsInterfaceTable to enable the GMPLS protocol on MPLS- 178 capable interfaces. 180 - The in-segment (gmplsInSegmentTable) and out-segment 181 (gmplsOutSegmentTable) tables extend mplsInSegmentTable and 182 mplsOutSegmentTable to configuring GMPLS-specific parameters for 183 LSP segments at an LSR. 185 - The gmplsLabelTable extends mplsLabelTable and allows Generalized 186 Labels to be defined and managed in a central location. 187 Generalized Labels can be of variable length and have distinct 188 bit-by-bit interpretations according to the use that is made of 189 them. 191 These tables are described in the subsequent sections. 193 5. Bidirectional LSPs 195 This MIB supports bidirectional LSPs as required for GMPLS. 196 A single value of mplsXCIndex is shared by all of the segments for 197 the entire bidirectional LSP. This facilitates a simple reference 198 from [TEMIB] and [GMPLSTEMIB], and makes fate-sharing more obvious. 200 It is, however, important that the direction of segments is 201 understood to avoid connecting all in-segments to all out-segments. 202 This is achieved by an object in each segment that indicates the 203 direction of the segment with respect to data flow. 205 A segment that is marked as 'forward' carries data from the 'head' of 206 the LSP to the 'tail'. A segment marked as 'reverse' carries data in 207 the reverse direction. 209 Where an LSP is signaled using a conventional signaling protocol, the 210 'head' of the LSP is the source of the signaling (also known as the 211 ingress) and the 'tail' is the destination (also known as the 212 egress). For manually configured LSPs an arbitrary decision must be 213 made about which segments are 'forward' and which 'reverse'. For 214 consistency this decision should be made across all LSRs that 215 participate in the LSP by assigning 'head' and 'tail' ends to the 216 LSP. 218 6. Example of LSP Setup 220 In this section we provide a brief example of using the MIB objects 221 described in section 9 to set up an LSP. While this example is not 222 meant to illustrate every nuance of the MIB, it is intended as an aid 223 to understanding some of the key concepts. It is meant to be read 224 after going through the MIB itself. A prerequisite is an 225 understanding of [LSRMIB]. 227 Suppose that one would like to manually create a best-effort, bi- 228 directional LSP. Assume that, in the forward direction, the LSP 229 enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR 230 via MPLS interface B with ifIndex 13. For the reverse direction, we 231 assume the LSP enters via interface B and leaves via interface A 232 (i.e. the forward and reverse directions use the same bi-directional 233 interfaces). Let us also assume that we do not wish to have a label 234 stack beneath the top label on the outgoing labeled packets. The 235 following example illustrates which rows and corresponding objects 236 might be created to accomplish this. 238 First, the traffic parameter entries must be set-up for both 239 segments. These are configured entirely in the MPLS LSR MIB through 240 the mplsTrafficParamTable. 242 Note that for a bi-directional LSP, the segments in the reverse 243 direction MAY share the traffic parameter entries (and hence 244 resources) with the segments in the forward direction. 246 We must next create the appropriate in-segment and out-segment 247 entries with suitable traffic parameters by pointing to the 248 appropriate traffic parameter entries that we have just created. This 249 is also done in the MPLS LSR MIB using mplsInSegmentTable and 250 mplsOutSegmentTable. 252 These table entries are extended by entries in gmplsInSegmentTable 253 and gmplsOutSegmentTable. Note that the nature of the 'extends' 254 relationship is that the entry in gmplsInSegmentTable has the same 255 index values as the entry in mplsInSegmentTable. Similarly, the entry 256 in gmplsOutSegmentTable has the same index values as the entry in 257 mplsOutSegmentTable. 259 First for the forward direction: 261 In gmplsInSegmentTable 262 { 263 gmplsInSegmentDirection = forward (1), 264 } 266 In gmplsOutSegmentTable 267 { 268 gmplsOutSegmentDirection = forward (1) 269 } 270 Next for the reverse direction: 272 In gmplsInSegmentTable 273 { 274 gmplsInSegmentDirection = reverse (2) 275 } 277 In gmplsOutSegmentTable 278 { 279 gmplsOutSegmentDirection = reverse (2) 280 } 282 Next, two cross-connect entries are created in the mplsXCTable of the 283 MPLS LSR MIB, thereby associating the newly created segments 284 together. 286 7. GMPLS Label Switching Router MIB Definitions 288 GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN 290 IMPORTS 291 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32 292 FROM SNMPv2-SMI 293 MODULE-COMPLIANCE, OBJECT-GROUP 294 FROM SNMPv2-CONF 295 GmplsSegmentDirection 296 FROM GMPLS-TC-STD-MIB 297 ; 299 gmplsLsrStdMIB MODULE-IDENTITY 300 LAST-UPDATED 301 "200308190900Z " -- 19 August 2003 9:00:00 GMT" 302 ORGANIZATION 303 "Common Control And Management Protocols (CCAMP) 304 Working Group" 305 CONTACT-INFO 306 " Thomas D. Nadeau 307 Cisco Systems, Inc. 308 Email: tnadeau@cisco.com 310 Cheenu Srinivasan 311 Bloomberg L.P. 312 Email: cheenu@bloomberg.net 314 Adrian Farrel 315 Old Dog Consulting 316 Email: adrian@olddog.co.uk 318 Ed Harrison 319 Data Connection Ltd. 320 Email: ed.harrison@dataconnection.com 322 Tim Hall 323 Data Connection Ltd. 324 Email: timhall@dataconnection.com 325 Comments about this document should be emailed direct to the 326 CCAMP working group mailing list at ccamp@ops.ietf.org" 327 DESCRIPTION 328 "This MIB module contains managed object definitions 329 for the Generalized Multiprotocol Label Switching 330 (GMPLS) Router as defined in: Ashwood-Smith et al., 331 Generalized Multiprotocol Label Switching (GMPLS) 332 Architecture, Internet Draft , March 2001, work in progress. 335 Copyright (C) The Internet Society (2003). This 336 version of this MIB module is part of RFCXXX; see 337 the RFC itself for full legal notices." 339 -- Revision history. 340 REVISION 341 "200308190900Z" -- 19 August 2003 09:00:00 GMT 342 DESCRIPTION 343 "Initial revision, published as part of RFC XXXX." 344 ::= { gmplsStdMIB xx } 346 -- Top level components of this MIB module. 348 -- Notifications 349 -- no notifications are currently defined. 350 gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 } 352 -- Tables, Scalars 353 gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } 355 -- Conformance 356 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } 358 -- GMPLS Interface Table. 360 gmplsInterfaceTable OBJECT-TYPE 361 SYNTAX SEQUENCE OF GmplsInterfaceEntry 362 MAX-ACCESS not-accessible 363 STATUS current 364 DESCRIPTION 365 "This table specifies per-interface GMPLS capability 366 and associated information. It extends the 367 information in mplsInterfaceTable." 368 ::= { gmplsLsrObjects 1 } 370 gmplsInterfaceEntry OBJECT-TYPE 371 SYNTAX GmplsInterfaceEntry 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "A conceptual row in this table is created 376 automatically by an LSR for every interface capable 377 of supporting GMPLS and which is configured to do 378 so. A conceptual row in this table will exist if and 379 only if a corresponding entry in mplsInterfaceTable 380 exists, and a corresponding entry in ifTable exists 381 with ifType = mpls(166). If the associated entry in 382 ifTable is operationally disabled (thus removing the 383 GMPLS capabilities on the interface) or the entry in 384 mplsInterfaceTable is deleted, the corresponding 385 entry in this table MUST be deleted shortly 386 thereafter. 388 The indexing is the same as that for 389 mplsInterfaceTable. Thus, the entry with index 0 390 represents the per-platform label space and contains 391 parameters that apply to all interfaces that 392 participate in the per-platform label space." 393 INDEX { mplsInterfaceIndex } 394 ::= { gmplsInterfaceTable 1 } 396 GmplsInterfaceEntry ::= SEQUENCE { 397 gmplsInterfaceSignalingCaps BITS 398 } 400 gmplsInterfaceSignalingCaps OBJECT-TYPE 401 SYNTAX BITS { 402 rsvp-gmpls (1), 403 crldp-gmpls (2), -- note the use of CR-LDP is deprecated 404 other-gmpls (3) 405 } 406 MAX-ACCESS read-create 407 STATUS current 408 DESCRIPTION 409 "Defines the signaling capabilities on this 410 interface. Multiple bits may legitimately be set at 411 once. Setting no bits implies that GMPLS signaling 412 cannot be performed on this interface and all LSPs 413 must be manually provisioned." 414 ::= { gmplsInterfaceEntry 1 } 416 -- End of gmplsInterfaceTable 418 -- In-segment table. 420 gmplsInSegmentTable OBJECT-TYPE 421 SYNTAX SEQUENCE OF GmplsInSegmentEntry 422 MAX-ACCESS not-accessible 423 STATUS current 424 DESCRIPTION 425 "This table extends the mplsInSegmentTable to provide 426 GMPLS-specific information about incoming segments 427 to an LSR." 428 ::= { gmplsLsrObjects 2 } 430 gmplsInSegmentEntry OBJECT-TYPE 431 SYNTAX GmplsInSegmentEntry 432 MAX-ACCESS not-accessible 433 STATUS current 434 DESCRIPTION 435 "An entry in this table extends the representation of 436 an incoming segment represented by an entry in 437 mplsInSegmentTable. An entry can be created by a 438 network administrator or an SNMP agent, or a GMPLS 439 signaling protocol. 441 Note that the storage type for this entry SHOULD be 442 inherited from the corresponding entry in the 443 mplsInSegmentTable given by the value of the 444 mplsInSegmentStorageType object." 445 INDEX { mplsInSegmentIndex } 446 ::= { gmplsInSegmentTable 1 } 448 GmplsInSegmentEntry ::= SEQUENCE { 449 gmplsInSegmentDirection GmplsSegmentDirection 450 } 452 gmplsInSegmentDirection OBJECT-TYPE 453 SYNTAX GmplsSegmentDirection 454 MAX-ACCESS read-create 455 STATUS current 456 DESCRIPTION 457 "This object indicates the direction of data flow on 458 this segment. This object cannot be modified if 459 mplsInSegmentRowStatus for the associated entry in 460 the mplsInSegmentTable is active(1)." 461 DEFVAL { forward } 462 ::= { gmplsInSegmentEntry 1 } 464 -- End of gmplsInSegmentTable 466 -- Out-segment table. 468 gmplsOutSegmentTable OBJECT-TYPE 469 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 470 MAX-ACCESS not-accessible 471 STATUS current 472 DESCRIPTION 473 "This table extends the mplsOutSegmentTable to 474 provide GMPLS-specific information about outgoing 475 segments from an LSR." 476 ::= { gmplsLsrObjects 3 } 478 gmplsOutSegmentEntry OBJECT-TYPE 479 SYNTAX GmplsOutSegmentEntry 480 MAX-ACCESS not-accessible 481 STATUS current 482 DESCRIPTION 483 "An entry in this table extends the representation of 484 an outgoing segment represented by an entry in 485 mplsOutSegmentTable. An entry can be created by a 486 network administrator or an SNMP agent, or a GMPLS 487 signaling protocol. 488 Note that the storage type for this entry SHOULD be 489 inherited from the corresponding entry in the 490 mplsOutSegmentTable given by the value of the 491 mplsOutSegmentStorageType object." 492 INDEX { mplsOutSegmentIndex } 493 ::= { gmplsOutSegmentTable 1 } 494 GmplsOutSegmentEntry ::= SEQUENCE { 495 gmplsOutSegmentDirection GmplsSegmentDirection, 496 gmplsOutSegmentTTLDecrement Unsigned32 497 } 499 gmplsOutSegmentDirection OBJECT-TYPE 500 SYNTAX GmplsSegmentDirection 501 MAX-ACCESS read-create 502 STATUS current 503 DESCRIPTION 504 "This object indicates the direction of data flow on 505 this segment. This object cannot be modified if 506 mplsOutSegmentRowStatus for the associated entry in 507 the mplsOutSegmentTable is active(1)." 508 DEFVAL { forward } 509 ::= { gmplsOutSegmentEntry 1 } 511 gmplsOutSegmentTTLDecrement OBJECT-TYPE 512 SYNTAX Unsigned32 (0..255) 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "This object indicates the amount by which to 517 decrement the TTL of any payload packets forwarded 518 on this segment if per-hop decrementing is being 519 done. 521 A value of zero indicates that no decrement should 522 be made or that per-hop decrementing is not in 523 force. 525 See the gmplsTunnelTTLDecrement object in the 526 gmplsTunnelTable of [GMPLSTEMIB] for a value by 527 which to decrement the TTL for the whole of a 528 tunnel. 530 This object cannot be modified if 531 mplsOutSegmentRowStatus for the associated entry in 532 the mplsOutSegmentTable is active(1)." 533 DEFVAL { 0 } 534 ::= { gmplsOutSegmentEntry 2 } 536 -- End of gmplsOutSegmentTable 538 -- Module compliance. 540 gmplsLsrGroups 541 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 543 gmplsLsrCompliances 544 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 546 -- Compliance requirement for fully compliant implementations. 548 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 549 STATUS current 550 DESCRIPTION 551 "Compliance statement for agents that provide full 552 support for GMPLS-LSR-STD-MIB." 554 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 556 MANDATORY-GROUPS { 557 ifGeneralInformationGroup, 558 ifCounterDiscontinuityGroup 559 } 561 MODULE MPLS-LSR-STD-MIB � The MPLS LSR MIB 563 MANDATORY-GROUPS { 564 mplsInterfaceGroup, 565 mplsInSegmentGroup, 566 mplsOutSegmentGroup, 567 mplsXCGroup, 568 mplsPerfGroup, 569 mplsLsrNotificationGroup 570 } 572 MODULE -- this module 574 MANDATORY-GROUPS { 575 gmplsInterfaceGroup, 576 gmplsInSegmentGroup, 577 gmplsOutSegmentGroup 578 } 580 -- gmplsInSegmentTable 582 OBJECT gmplsInSegmentDirection 583 SYNTAX GmplsSegmentDirection 584 MIN-ACCESS read-write 585 DESCRIPTION 586 "Only forward(1) needs to be supported by 587 implementations that only support unidirectional 588 LSPs." 590 -- gmplsOutSegmentTable 592 OBJECT gmplsOutSegmentDirection 593 SYNTAX GmplsSegmentDirection 594 MIN-ACCESS read-write 595 DESCRIPTION 596 "Only forward(1) needs to be supported by 597 implementations that only support unidirectional 598 LSPs." 600 OBJECT gmplsOutSegmentTTLDecrement 601 SYNTAX Unsigned32 (0..255) 602 MIN-ACCESS read-only 603 DESCRIPTION 604 "Write access is not required." 606 ::= { gmplsLsrCompliances 1 } 608 -- Compliance requirement for implementations that provide read-only 609 -- access. 611 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 612 STATUS current 613 DESCRIPTION 614 "Compliance requirement for implementations that only 615 provide read-only support for GMPLS-LSR-STD-MIB. Such 616 devices can then be monitored but cannot be configured 617 using this MIB modules." 619 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 621 MANDATORY-GROUPS { 622 ifGeneralInformationGroup, 623 ifCounterDiscontinuityGroup 624 } 626 MODULE MPLS-LSR-STD-MIB 628 MANDATORY-GROUPS { 629 mplsInterfaceGroup, 630 mplsInSegmentGroup, 631 mplsOutSegmentGroup, 632 mplsXCGroup, 633 mplsPerfGroup 634 } 636 MODULE -- this module 638 MANDATORY-GROUPS { 639 gmplsInterfaceGroup, 640 gmplsInSegmentGroup, 641 gmplsOutSegmentGroup 642 } 644 -- gmplsInterfaceGroup 646 OBJECT gmplsInterfaceSignalingCaps 647 SYNTAX BITS 648 MIN-ACCESS read-only 649 DESCRIPTION 650 "Write access is not required." 652 -- gmplsInSegmentTable 654 OBJECT gmplsInSegmentDirection 655 SYNTAX GmplsSegmentDirection 656 MIN-ACCESS read-only 657 DESCRIPTION 658 "Write access is not required. Only forward(1) needs 659 to be supported by implementations that only support 660 unidirectional LSPs." 662 -- gmplsOutSegmentTable 664 OBJECT gmplsOutSegmentDirection 665 SYNTAX GmplsSegmentDirection 666 MIN-ACCESS read-only 667 DESCRIPTION 668 "Write access is not required. Only forward(1) needs 669 to be supported by implementations that only support 670 unidirectional LSPs." 672 OBJECT gmplsOutSegmentTTLDecrement 673 SYNTAX Unsigned32 (0..255) 674 MIN-ACCESS read-only 675 DESCRIPTION 676 "Write access is not required." 678 ::= { gmplsLsrCompliances 2 } 680 -- Units of conformance. 682 gmplsInterfaceGroup OBJECT-GROUP 683 OBJECTS { 684 gmplsInterfaceSignalingCaps 685 } 686 STATUS current 687 DESCRIPTION 688 "Collection of objects needed for GMPLS interface 689 configuration and performance information." 690 ::= { gmplsLsrGroups 1 } 692 gmplsInSegmentGroup OBJECT-GROUP 693 OBJECTS { 694 gmplsInSegmentDirection 695 } 696 STATUS current 697 DESCRIPTION 698 "Collection of objects needed to implement a GMPLS 699 in-segment." 700 ::= { gmplsLsrGroups 2 } 701 gmplsOutSegmentGroup OBJECT-GROUP 702 OBJECTS { 703 gmplsOutSegmentDirection, 704 gmplsOutSegmentTTLDecrement 705 } 706 STATUS current 707 DESCRIPTION 708 "Collection of objects needed to implement a GMPLS 709 out-segment." 710 ::= { gmplsLsrGroups 3 } 712 END 714 8. GMPLS Label MIB Definitions 716 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 718 IMPORTS 719 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32 720 FROM SNMPv2-SMI 721 MODULE-COMPLIANCE, OBJECT-GROUP 722 FROM SNMPv2-CONF 723 RowStatus, StorageType 724 FROM SNMPv2-TC 725 InterfaceIndexOrZero 726 FROM IF-MIB 727 MplsLabel 728 FROM MPLS-TC-STD-MIB 729 GmplsGeneralizedLabelTypes, GmplsFreeformLabel 730 FROM GMPLS-TC-STD-MIB 731 ; 733 gmplsLabelStdMIB MODULE-IDENTITY 734 LAST-UPDATED 735 "200308190900Z " -- 19 August 2003 9:00:00 GMT" 736 ORGANIZATION 737 "Common Control And Management Protocols (CCAMP) 738 Working Group" 739 CONTACT-INFO 740 " Thomas D. Nadeau 741 Cisco Systems, Inc. 742 Email: tnadeau@cisco.com 744 Cheenu Srinivasan 745 Bloomberg L.P. 746 Email: cheenu@bloomberg.net 748 Adrian Farrel 749 Old Dog Consulting 750 Email: adrian@olddog.co.uk 752 Ed Harrison 753 Data Connection Ltd. 754 Email: ed.harrison@dataconnection.com 756 Tim Hall 757 Data Connection Ltd. 758 Email: timhall@dataconnection.com 759 Comments about this document should be emailed direct to the 760 CCAMP working group mailing list at ccamp@ops.ietf.org" 761 DESCRIPTION 762 "This MIB module contains managed object definitions 763 for labels within GMPLS systems." 765 -- Revision history. 766 REVISION 767 "200308190900Z" -- 19 August 2003 09:00:00 GMT 768 DESCRIPTION 769 "Initial revision, published as part of RFC XXXX." 770 ::= { gmplsStdMIB 2 } 772 -- Top level components of this MIB module. 774 -- Notifications 775 -- no notifications are currently defined. 776 gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 } 778 -- Tables, Scalars 779 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 781 -- Conformance 782 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 784 -- GMPLS Label Table. 786 gmplsLabelTable OBJECT-TYPE 787 SYNTAX SEQUENCE OF GmplsLabelEntry 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "Table of GMPLS Labels. This table allows the 792 representation of the more complex label forms 793 required for GMPLS which cannot be held within the 794 textual convention MplsLabel. That is labels that 795 cannot be encoded within 32 bits. It is, 796 nevertheless also capable of holding 32 bit labels 797 or regular MPLS labels if desired. 799 Each entry in this table represents an individual 800 GMPLS label value. Labels in the tables in other 801 MIBs are referred to using row pointer into this 802 table. The indexing of this table provides for 803 arbitrary indexing and also for concatenation of 804 labels. " 805 ::= { gmplsLabelObjects 1 } 807 gmplsLabelEntry OBJECT-TYPE 808 SYNTAX GmplsLabelEntry 809 MAX-ACCESS not-accessible 810 STATUS current 811 DESCRIPTION 812 "An entry in this table represents a single label 813 value. There are three indexes into the table. 814 - The interface index may be helpful to distinguish 815 which labels are in use on which interfaces or to 816 handle cases where there are a very large number 817 of labels in use in the system. When label 818 representation is desired to apply to the whole 819 system or when it is not important to distinguish 820 labels by their interfaces, this index MAY be set 821 to zero. 822 - The label index provides a way of identifying the 823 label. 824 - The label sub-index is only used for concatenated 825 labels. It identifies each component label. When 826 non-concatenated labels are used, this index 827 SHOULD be set to zero. 829 A storage type object is supplied to control the 830 storage type for each entry, but implementations 831 should note that the storage type of conceptual rows 832 in other tables that include row pointers to an 833 entry in this table SHOULD dictate the storage type 834 of the rows in this table where the row in the other 835 table is more persistent." 836 INDEX { 837 gmplsLabelInterface, 838 gmplsLabelIndex, 839 gmplsLabelSubindex } 840 ::= { gmplsLabelTable 1 } 842 GmplsLabelEntry ::= SEQUENCE { 843 gmplsLabelInterface InterfaceIndexOrZero, 844 gmplsLabelIndex Unsigned32, 845 gmplsLabelSubindex Unsigned32, 846 gmplsLabelType GmplsGeneralizedLabelTypes, 847 gmplsLabelMplsLabel MplsLabel, 848 gmplsLabelPortWavelength Unsigned32, 849 gmplsLabelFreeformLength INTEGER, 850 gmplsLabelFreeform GmplsFreeformLabel, 851 gmplsLabelSonetSdhSignalIndex INTEGER, 852 gmplsLabelSdhVc INTEGER, 853 gmplsLabelSdhVcBranch INTEGER, 854 gmplsLabelSonetSdhBranch INTEGER, 855 gmplsLabelSonetSdhGroupBranch INTEGER, 856 gmplsLabelWavebandId Unsigned32, 857 gmplsLabelWavebandStartLabel Unsigned32, 858 gmplsLabelWavebandEndLabel Unsigned32, 859 gmplsLabelRowStatus RowStatus, 860 gmplsLabelStorageType StorageType 861 } 863 gmplsLabelInterface OBJECT-TYPE 864 SYNTAX InterfaceIndexOrZero 865 MAX-ACCESS not-accessible 866 STATUS current 867 DESCRIPTION 868 "The interface on which this label is used. If the 869 label has or could have applicability across the 870 whole system, this object SHOULD be set to zero." 871 ::= { gmplsLabelEntry 1 } 872 gmplsLabelIndex OBJECT-TYPE 873 SYNTAX Unsigned32 (0..4294967295) 874 MAX-ACCESS not-accessible 875 STATUS current 876 DESCRIPTION 877 "An arbitrary index into the table to identify a 878 label. 879 Note that implementations that are representing 32 880 bit labels within this table MAY choose to align 881 this index with the value of the label, but should 882 be aware of the implications of sparsely populated 883 tables." 884 ::= { gmplsLabelEntry 2 } 886 gmplsLabelSubindex OBJECT-TYPE 887 SYNTAX Unsigned32 (0..4294967295) 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "In conjunction with gmplsLabelInterface and 892 gmplsLabelIndex, this object uniquely identifies 893 this row. This sub-index allows a single GMPLS label 894 to be defined as a concatenation of labels. This is 895 particularly useful in TDM. 896 The ordering of sub-labels is strict with the sub- 897 label with lowest gmplsLabelSubindex appearing 898 first. Note that all sub-labels of a single GMPLS 899 label must share the same gmplsLabelInterface and 900 gmplsLabelIndex values. For labels that are not 901 composed of concatenated sub-labels, this value 902 SHOULD be set to zero." 903 ::= { gmplsLabelEntry 3 } 905 gmplsLabelType OBJECT-TYPE 906 SYNTAX GmplsGeneralizedLabelTypes 907 MAX-ACCESS read-create 908 STATUS current 909 DESCRIPTION 910 "Identifies the type of this label. Note that this 911 object does not determine whether MPLS or GMPLS 912 signaling is in use: a value of gmplsMplsLabel (1) 913 denotes that a 23 bit MPLS packet label is present, 914 but does not describe whether this is signaled using 915 MPLS or GMPLS. 916 The value of this object helps determine which of 917 the following objects are valid. 918 This object cannot be modified if 919 gmplsLabelRowStatus is active(1)." 920 ::= { gmplsLabelEntry 4 } 922 gmplsLabelMplsLabel OBJECT-TYPE 923 SYNTAX MplsLabel 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "The value of an MPLS label (that is a packet label) 928 if this table is used to store it. This may be used 929 in MPLS systems even though the label values can be 930 adequately stored in the MPLS MIB modules. Further, 931 in mixed MPLS and GMPLS systems it may be 932 advantageous to store all labels in a single label 933 table. Lastly, in GMPLS systems where packet labels 934 are used (that is in systems that use GMPLS 935 signaling and GMPLS labels for packet switching) it 936 may be desirable to use this table. 937 This object is only valid if gmplsLabelType is set 938 to gmplsMplsLabel (1). 939 This object cannot be modified if 940 gmplsLabelRowStatus is active(1)." 941 ::= { gmplsLabelEntry 6 } 943 gmplsLabelPortWavelength OBJECT-TYPE 944 SYNTAX Unsigned32 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "The value of a Port or Wavelength Label when carried 949 as a Generalized Label. Only valid if gmplsLabelType 950 is set to gmplsPortWavelengthLabel(2). 951 This object cannot be modified if 952 gmplsLabelRowStatus is active(1)." 953 ::= { gmplsLabelEntry 7 } 955 gmplsLabelFreeformLength OBJECT-TYPE 956 SYNTAX INTEGER (1..64) 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "The length of a freeform Generalized Label indicated 961 in the gmplsFreeformLabel object. Only valid if 962 gmplsLabelType is set to 963 gmplsFreeformGeneralizedLabel(3). 964 This object cannot be modified if 965 gmplsLabelRowStatus is active(1)." 966 ::= { gmplsLabelEntry 8 } 968 gmplsLabelFreeform OBJECT-TYPE 969 SYNTAX GmplsFreeformLabel 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION 973 "The value of a freeform Generalized Label that does 974 not conform to one of the standardized label 975 encoding or that an implementation chooses to 977 represent as an octet string without further 978 decoding. The length of this object is given by the 979 value of gmplsFreeformLength. Only valid if 980 gmplsLabelType is set to 981 gmplsFreeformGeneralizedLabel(3). 982 This object cannot be modified if 983 gmplsLabelRowStatus is active(1)." 984 ::= { gmplsLabelEntry 9 } 985 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 986 SYNTAX INTEGER (0..4095) 987 MAX-ACCESS read-create 988 STATUS current 989 DESCRIPTION 990 "The Signal Index value (S) of a SONET or SDH 991 Generalized Label. Zero indicates that this field is 992 not significant. Only valid if gmplsLabelType is set 993 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 994 This object cannot be modified if 995 gmplsLabelRowStatus is active(1)." 996 ::= { gmplsLabelEntry 10 } 998 gmplsLabelSdhVc OBJECT-TYPE 999 SYNTAX INTEGER (0..15) 1000 MAX-ACCESS read-create 1001 STATUS current 1002 DESCRIPTION 1003 "The VC Indicator (U) of an SDH Generalized Label. 1004 Zero indicates that this field is non-significant. 1005 Only valid if gmplsLabelType is set to 1006 gmplsSdhLabel(5). 1007 This object cannot be modified if 1008 gmplsLabelRowStatus is active(1)." 1009 ::= { gmplsLabelEntry 11 } 1011 gmplsLabelSdhVcBranch OBJECT-TYPE 1012 SYNTAX INTEGER (0..15) 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "The VC Branch Indicator (K) of an SDH Generalized 1017 Label. Zero indicates that this field is non- 1018 significant. Only valid if gmplsLabelType is set to 1019 gmplsSdhLabel(5). 1020 This object cannot be modified if 1021 gmplsLabelRowStatus is active(1)." 1022 ::= { gmplsLabelEntry 12 } 1024 gmplsLabelSonetSdhBranch OBJECT-TYPE 1025 SYNTAX INTEGER (0..15) 1026 MAX-ACCESS read-create 1027 STATUS current 1028 DESCRIPTION 1029 "The Branch Indicator (L) of a SONET or SDH 1030 Generalized Label. Zero indicates that this field is 1031 non-significant. Only valid gmplsLabelType is set to 1032 gmplsSonetLabel(4) or gmplsSdhLabel(5). 1033 This object cannot be modified if 1034 gmplsLabelRowStatus is active(1)." 1035 ::= { gmplsLabelEntry 13 } 1036 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1037 SYNTAX INTEGER (0..15) 1038 MAX-ACCESS read-create 1039 STATUS current 1040 DESCRIPTION 1041 "The Group Branch Indicator (M) of a SONET or SDH 1042 Generalized Label. Zero indicates that this field is 1043 non-significant. Only valid if gmplsLabelType is set 1044 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1045 This object cannot be modified if 1046 gmplsLabelRowStatus is active(1)." 1047 ::= { gmplsLabelEntry 14 } 1049 gmplsLabelWavebandId OBJECT-TYPE 1050 SYNTAX Uunsigned32 1051 MAX-ACCESS read-create 1052 STATUS current 1053 DESCRIPTION 1054 "The waveband identifier component of a waveband 1055 label. Only valid if gmplsLabelType is set to 1056 gmplsWavebandLabel(6). 1057 This object cannot be modified if 1058 gmplsLabelRowStatus is active(1)." 1059 ::= { gmplsLabelEntry 15 } 1061 gmplsLabelWavebandStart OBJECT-TYPE 1062 SYNTAX Uunsigned32 1063 MAX-ACCESS read-create 1064 STATUS current 1065 DESCRIPTION 1066 "The starting label component of a waveband label. 1067 Only valid if gmplsLabelType is set to 1068 gmplsWavebandLabel(6). 1069 This object cannot be modified if 1070 gmplsLabelRowStatus is active(1)." 1071 ::= { gmplsLabelEntry 16 } 1073 gmplsLabelWavebandEnd OBJECT-TYPE 1074 SYNTAX Uunsigned32 1075 MAX-ACCESS read-create 1076 STATUS current 1077 DESCRIPTION 1078 "The end label component of a waveband label. Only 1079 valid if gmplsLabelType is set to 1080 gmplsWavebandLabel(6). 1081 This object cannot be modified if 1082 gmplsLabelRowStatus is active(1)." 1083 ::= { gmplsLabelEntry 17 } 1084 gmplsLabelRowStatus OBJECT-TYPE 1085 SYNTAX RowStatus 1086 MAX-ACCESS read-create 1087 STATUS current 1088 DESCRIPTION 1089 "This variable is used to create, modify, and/or 1090 delete a row in this table. When a row in this 1091 table has a row in the active(1) state, no 1092 objects in this row can be modified except the 1093 gmplsLabelRowStatus and gmplsLabelStorageType." 1094 ::= { gmplsLabelEntry 18 } 1096 gmplsLabelStorageType OBJECT-TYPE 1097 SYNTAX StorageType 1098 MAX-ACCESS read-create 1099 STATUS current 1100 DESCRIPTION 1101 "This variable indicates the storage type for this 1102 object. 1104 The agent MUST ensure that this object's value 1105 remains consistent with the storage type of any rows 1106 in other tables that contain pointers to this row. 1107 In particular, the storage type of this row must be 1108 at least as permanent as that of any row that point 1109 to it. 1111 Conceptual rows having the value 'permanent' need 1112 not allow write-access to any columnar objects in 1113 the row." 1114 REFERENCE 1115 "See RFC2579." 1116 DEFVAL { volatile } 1117 ::= { gmplsLabelEntry 19 } 1119 -- End of GMPLS Label Table 1121 -- Module compliance. 1123 gmplsLabelGroups 1124 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1126 gmplsLabelCompliances 1127 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1129 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1130 STATUS current 1131 DESCRIPTION 1132 "Compliance statement for agents that support 1133 the GMPLS Label MIB module." 1135 MODULE -- this module 1137 -- The mandatory groups have to be implemented by 1138 -- LSRs claiming support for this MIB module. This MIB module is, 1139 -- however, not mandatory for a working implementation of a GMPLS 1140 -- LSR with full MIB support if the GMPLS labels in use can be 1141 -- represented within a 32 bit quantity. 1143 MANDATORY-GROUPS { 1144 gmplsLabelTableGroup 1145 } 1147 -- Units of conformance. 1149 GROUP gmplsLabelTableGroup 1150 DESCRIPTION 1151 "This group is mandatory for devices which support 1152 the gmplsLabelTable." 1154 GROUP gmplsLabelPacketGroup 1155 DESCRIPTION 1156 "This group extends gmplsLabelTableGroup for 1157 implementations that support packet labels." 1159 GROUP gmplsLabelPortWavelengthGroup 1160 DESCRIPTION 1161 "This group extends gmplsLabelTableGroup for 1162 implementations that support port and wavelength 1163 labels." 1165 GROUP gmplsLabelFreeformGroup 1166 DESCRIPTION 1167 "This group extends gmplsLabelTableGroup for 1168 implementations that support freeform labels." 1170 GROUP gmplsLabelSonetSdhGroup 1171 DESCRIPTION 1172 "This group extends gmplsLabelTableGroup for 1173 implementations that support SONET or SDH labels." 1175 GROUP gmplsLabelWavebandGroup 1176 DESCRIPTION 1177 "This group extends gmplsLabelTableGroup for 1178 implementations that support Waveband labels." 1180 -- gmplsLabelTable 1182 OBJECT gmplsLabelType 1183 MIN-ACCESS read-only 1184 DESCRIPTION 1185 "Write access is not required." 1187 OBJECT gmplsLabelMplsLabel 1188 MIN-ACCESS read-only 1189 DESCRIPTION 1190 "Write access is not required." 1192 OBJECT gmplsLabelPortWavelength 1193 MIN-ACCESS read-only 1194 DESCRIPTION 1195 "Write access is not required." 1197 OBJECT gmplsLabelFreeformLength 1198 MIN-ACCESS read-only 1199 DESCRIPTION 1200 "Write access is not required." 1202 OBJECT gmplsLabelFreeform 1203 MIN-ACCESS read-only 1204 DESCRIPTION 1205 "Write access is not required." 1207 OBJECT gmplsLabelSonetSdhSignalIndex 1208 MIN-ACCESS read-only 1209 DESCRIPTION 1210 "Write access is not required." 1212 OBJECT gmplsLabelSdhVc 1213 MIN-ACCESS read-only 1214 DESCRIPTION 1215 "Write access is not required." 1217 OBJECT gmplsLabelSdhVcBranch 1218 MIN-ACCESS read-only 1219 DESCRIPTION 1220 "Write access is not required." 1222 OBJECT gmplsLabelSonetSdhBranch 1223 MIN-ACCESS read-only 1224 DESCRIPTION 1225 "Write access is not required." 1227 OBJECT gmplsLabelSonetSdhGroupBranch 1228 MIN-ACCESS read-only 1229 DESCRIPTION 1230 "Write access is not required." 1232 OBJECT gmplsLabelWavebandId 1233 MIN-ACCESS read-only 1234 DESCRIPTION 1235 "Write access is not required." 1237 OBJECT gmplsLabelWavebandStart 1238 MIN-ACCESS read-only 1239 DESCRIPTION 1240 "Write access is not required." 1242 OBJECT gmplsLabelWavebandEnd 1243 MIN-ACCESS read-only 1244 DESCRIPTION 1245 "Write access is not required." 1247 OBJECT gmplsLabelRowStatus 1248 SYNTAX RowStatus { 1249 active(1), 1250 notInService(2) 1251 } 1252 WRITE-SYNTAX RowStatus { 1253 active(1), 1254 notInService(2), 1255 createAndGo(4), 1256 destroy(6) 1257 } 1258 DESCRIPTION 1259 "Support for notInService, createAndWait and notReady 1260 is not required." 1262 OBJECT gmplsLabelStorageType 1263 MIN-ACCESS read-only 1264 DESCRIPTION 1265 "Write access is not required." 1267 ::= { gmplsLabelCompliances 1 } 1269 -- Units of conformance. 1271 gmplsLabelTableGroup OBJECT-GROUP 1272 OBJECTS { 1273 gmplsLabelType, 1274 gmplsLabelSubtype, 1275 gmplsLabelRowStatus, 1276 gmplsLabelStorageType 1277 } 1278 STATUS current 1279 DESCRIPTION 1280 "Necessary, but not sufficient, set of objects to 1281 implement label table support. In addition, 1282 depending on the type of labels supported (for 1283 example, wavelength labels), the following other 1284 groups defined below are mandatory: 1285 gmplsLabelPacketGroup and/or 1286 gmplsLabelPortWavelengthGroup and/or 1287 gmplsLabelFreeformGroup and/or 1288 gmplsLabelSonetSdhGroup." 1289 ::= { gmplsLabelGroups 1 } 1291 gmplsLabelPacketGroup OBJECT-GROUP 1292 OBJECTS { 1293 gmplsLabelMplsLabel 1294 } 1295 STATUS current 1296 DESCRIPTION 1297 "Object needed to implement Packet (MPLS) labels." 1298 ::= { gmplsLabelGroups 2 } 1299 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1300 OBJECTS { 1301 gmplsLabelPortWavelength 1302 } 1303 STATUS current 1304 DESCRIPTION 1305 "Object needed to implement Port and Wavelength 1306 labels." 1307 ::= { gmplsLabelGroups 3 } 1309 gmplsLabelFreeformGroup OBJECT-GROUP 1310 OBJECTS { 1311 gmplsLabelFreeformLength, 1312 gmplsLabelFreeform 1313 } 1314 STATUS current 1315 DESCRIPTION 1316 "Object needed to implement Freeform labels." 1317 ::= { gmplsLabelGroups 4 } 1319 gmplsLabelSonetSdhGroup OBJECT-GROUP 1320 OBJECTS { 1321 gmplsLabelSonetSdhSignalIndex, 1322 gmplsLabelSdhVc, 1323 gmplsLabelSdhVcBranch, 1324 gmplsLabelSonetSdhBranch, 1325 gmplsLabelSonetSdhGroupBranch 1326 } 1327 STATUS current 1328 DESCRIPTION 1329 "Object needed to implement SONET and SDH labels." 1330 ::= { gmplsLabelGroups 5 } 1332 gmplsLabelWavebandGroup OBJECT-GROUP 1333 OBJECTS { 1334 gmplsLabelWavebandId, 1335 gmplsLabelWavebandStart, 1336 gmplsLabelWavebandEnd 1337 } 1338 STATUS current 1339 DESCRIPTION 1340 "Object needed to implement Waveband labels." 1341 ::= { gmplsLabelGroups 6 } 1343 END 1345 9. Security Considerations 1347 It is clear that the MIB modules described in this document in 1348 association with the MPLS-LSR-STD-MIB are potentially useful for 1349 monitoring of GMPLS LSRs. These MIB modules can also be used for 1350 configuration of certain objects, and anything that can be configured 1351 can be incorrectly configured, with potentially disastrous results. 1353 There are a number of management objects defined in these MIB modules 1354 with a MAX-ACCESS clause of read-write and/or read-create. Such 1355 objects may be considered sensitive or vulnerable in some network 1356 environments. The support for SET operations in a non-secure 1357 environment without proper protection can have a negative effect on 1358 network operations. These are the tables and objects and their 1359 sensitivity/vulnerability: 1361 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1362 and gmplsLabelTable collectively contain objects to provision 1363 GMPLS interfaces, LSPs and their associated parameters on a Label 1364 Switching Router (LSR). Unauthorized write access to objects in 1365 these tables, could result in disruption of traffic on the 1366 network. This is especially true if an LSP has already been 1367 established. The use of stronger mechanisms such as SNMPv3 1368 security should be considered where possible. Specifically, SNMPv3 1369 VACM and USM MUST be used with any SNMPv3 agent which implements 1370 these MIB modules. 1372 Some of the readable objects in these MIB modules "i.e., objects with 1373 a MAX-ACCESS other than not-accessible" may be considered sensitive 1374 or vulnerable in some network environments. It is thus important to 1375 control even GET and/or NOTIFY access to these objects and possibly 1376 to even encrypt the values of these objects when sending them over 1377 the network via SNMP. These are the tables and objects and their 1378 sensitivity/vulnerability: 1380 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1381 and gmplsLabelTable collectively show the LSP network topology and 1382 its capabilities. If an Administrator does not want to reveal this 1383 information, then these tables should be considered 1384 sensitive/vulnerable. 1386 SNMP versions prior to SNMPv3 did not include adequate security. Even 1387 if the network itself is secure "for example by using IPSec", even 1388 then, there is no control as to who on the secure network is allowed 1389 to access and GET/SET "read/change/create/delete" the objects in 1390 these MIB modules. It is RECOMMENDED that implementers consider the 1391 security features as provided by the SNMPv3 framework "see [RFC3410], 1392 section 8", including full support for the SNMPv3 cryptographic 1393 mechanisms "for authentication and privacy". 1395 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1396 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1397 enable cryptographic security. It is then a customer/operator 1398 responsibility to ensure that the SNMP entity giving access to an 1399 instance of this MIB module, is properly configured to give access to 1400 the objects only to those principals "users" that have legitimate 1401 rights to indeed GET or SET "change/create/delete" them. 1403 10. Acknowledgments 1405 This draft extends [LSRMIB]. The authors would like to express their 1406 gratitude to all those who worked on that earlier MIB document. 1408 The authors would like to express their thanks to Dan Joyle for his 1409 careful review and comments on early versions of the Label Table. 1411 11. IANA Considerations 1413 MPLS related standards track MIB modules are rooted under the 1414 mplsStdMIB subtree. 1416 One of the MIB modules contained in this document extends tables 1417 contained in MPLS MIB modules. 1419 As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the 1420 two MIB modules contained in this document should be placed in the 1421 mplsStdMIB subtree as well. 1423 New assignments can only be made via a Standards Action as specified 1424 in [RFC2434]. 1426 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 1428 The IANA is requested to assign { mplsStdMIB xx } to the 1429 GMPLS-LSR-STD-MIB module specified in this document. 1431 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 1433 The IANA is requested to assign { mplsStdMIB xx } to the 1434 GMPLS-LABEL-STD-MIB module specified in this document. 1436 12. References 1438 12.1. Normative References 1440 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1441 Requirement Levels", BCP 14, RFC 2119, March 1997. 1443 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1444 Case, J., Rose, M., and S. Waldbusser, "Structure 1445 of Management Information Version 2 (SMIv2)", STD 1446 58, RFC 2578, April 1999. 1448 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1449 Case, J., Rose, M., and S. Waldbusser, "Textual 1450 Conventions for SMIv2", STD 58, RFC 2579, April 1451 1999. 1453 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1454 Case, J., Rose, M., and S. Waldbusser, "Conformance 1455 Statements for SMIv2", STD 58, RFC 2580, April 1456 1999. 1458 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces 1459 Group MIB", RFC 2863, June 2000. 1461 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 1462 Label Switching (GMPLS) Signaling Functional 1463 Description�, RFC 3471, January 2003. 1465 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 1466 "Generalized MPLS Signaling - CR-LDP Extensions", 1467 RFC 3472, January 2003. 1469 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 1470 RSVP-TE Extensions", RFC 3473 January 2003. 1472 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 1473 Label Switching (GMPLS) Architecture", Internet 1474 Draft , May 1475 2003, work in progress. 1477 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 1478 "Generalized Multi-Protocol Label Switching 1479 Extensions for SONET and SDH Control", Internet 1480 Draft , 1481 February 2003, work in progress. 1483 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of 1484 Textual Conventions for Multiprotocol Label 1485 Switching (MPLS) Management", Internet Draft 1486 , August 2003, work 1487 in progress. 1489 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, 1490 "Multiprotocol Label Switching (MPLS) Label 1491 Switching Router (LSR) Management Information 1492 Base", Internet Draft , August 2003, work in progress. 1495 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 1496 and Harrison, E., "Generalized Multiprotocol Label 1497 Switching (GMPLS) Traffic Engineering Management 1498 Information Base", draft-ietf-ccamp-gmpls-te-mib- 1499 01.txt, August 2003, work in progress. 1501 [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 1502 and Harrison, E., "Definitions of Textual 1503 Conventions for Multiprotocol Label Switching 1504 (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib- 1505 01.txt, August 2003, work in progress. 1507 12.2. Informational References 1509 [RFC2026] S. Bradner, "The Internet Standards Process -- 1510 Revision 3", RFC 2026, October 1996. 1512 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 1513 Applications", RFC 3413, December 2002. 1515 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1516 "Introduction and Applicability Statements for 1517 Internet-Standard Management Framework", RFC 3410, 1518 December 2002. 1520 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1521 Architecture for Describing Simple Network 1522 Management Protocol (SNMP) Management Frameworks", 1523 RFC 3411, December 2002. 1525 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1526 "Multiprotocol Label Switching Architecture", RFC 1527 3031, January 2001. 1529 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 1530 Srinivasan, V., and G. Swallow, "RSVP-TE: 1531 Extensions to RSVP for LSP Tunnels", RFC 3209, 1532 December 2001. 1534 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 1535 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 1536 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 1537 T., Feldman, N., Fredette, A., Girish, M., Gray, 1538 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 1539 A., and P. Vaananen, "Constraint-Based LSP Setup 1540 using LDP", RFC 3212, December 2001." 1542 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 1543 "Multiprotocol Label Switching (MPLS) Traffic 1544 Engineering Management Information Base", Internet 1545 Draft , August 2003, 1546 work in progress. 1548 13. Authors' Addresses 1550 Thomas D. Nadeau 1551 Cisco Systems, Inc. 1552 300 Apollo Drive 1553 Chelmsford, MA 01824 1554 Phone: +1-978-244-3051 1555 Email: tnadeau@cisco.com 1557 Cheenu Srinivasan 1558 Bloomberg L.P. 1559 499 Park Ave., 1560 New York, NY 10022 1561 Phone: +1-212-893-3682 1562 Email: cheenu@bloomberg.net 1564 Adrian Farrel 1565 Old Dog Consulting 1566 Phone: +44-(0)-1978-860944 1567 Email: adrian@olddog.co.uk 1569 Tim Hall 1570 Data Connection Ltd. 1571 100 Church Street 1572 Enfield, Middlesex 1573 EN2 6BQ, UK 1574 Phone: +44 20 8366 1177 1575 Email: timhall@dataconnection.com 1576 Ed Harrison 1577 Data Connection Ltd. 1578 100 Church Street 1579 Enfield, Middlesex 1580 EN2 6BQ, UK 1581 Phone: +44 20 8366 1177 1582 Email: ed.harrison@dataconnection.com 1584 14. Full Copyright Statement 1586 Copyright (C) The Internet Society (2003). All Rights Reserved. 1588 This document and translations of it may be copied and furnished to 1589 others, and derivative works that comment on or otherwise explain it 1590 or assist in its implementation may be prepared, copied, published 1591 and distributed, in whole or in part, without restriction of any 1592 kind, provided that the above copyright notice and this paragraph 1593 are included on all such copies and derivative works. However, this 1594 document itself may not be modified in any way, such as by removing 1595 the copyright notice or references to the Internet Society or other 1596 Internet organizations, except as needed for the purpose of 1597 developing Internet standards in which case the procedures for 1598 copyrights defined in the Internet Standards process must be 1599 followed, or as required to translate it into languages other than 1600 English. 1602 The limited permissions granted above are perpetual and will not be 1603 revoked by the Internet Society or its successors or assigns. This 1604 document and the information contained herein is provided on an "AS 1605 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1606 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 1607 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 1608 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1609 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1611 15. Intellectual Property Notice 1613 The IETF takes no position regarding the validity or scope of any 1614 intellectual property or other rights that might be claimed to 1615 pertain to the implementation or use of the technology described in 1616 this document or the extent to which any license under such rights 1617 might or might not be available; neither does it represent that it 1618 has made any effort to identify any such rights. Information on the 1619 IETF's procedures with respect to rights in standards-track and 1620 standards-related documentation can be found in BCP-11 [RFC2028]. 1622 Copies of claims of rights made available for publication and any 1623 assurances of licenses to be made available, or the result of an 1624 attempt made to obtain a general license or permission for the use 1625 of such proprietary rights by implementers or users of this 1626 specification can be obtained from the IETF Secretariat. 1628 The IETF invites any interested party to bring to its attention any 1629 copyrights, patents or patent applications, or other proprietary 1630 rights that may cover technology that may be required to practice 1631 this standard. Please address the information to the IETF Executive 1632 Director. 1634 16. Changes and Pending Work 1636 This section must be removed before the draft progresses to RFC. 1638 16.1. Pending Work 1640 The following work items have been identified for this draft. They 1641 will be addressed in a future version. 1643 - Expand conformance statements to give one for monitoring only, 1644 and one for monitoring and control. 1646 - Extend mplsTrafficParamsTable from the MPLS-LSR-MIB to support 1647 GMPLS traffic parameters for signaled and static LSPs. 1649 - Provide support for monitoring tunnel resources in GMPLS systems. 1650 For example, SONET/SDH or G.709. This might be done through an 1651 arbitrary RowPointer to an external MIB. 1653 - Extend the performance tables from the MPLS-LSR-MIB for 1654 technology-specific GMPLS LSPs. 1656 - Supply more and better examples, especially ones using the Label 1657 Table. 1659 - Provide a next index object to supply the next available 1660 arbitrary index into the Label Table.