idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1885. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1858. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1865. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1871. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2004) is 7133 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: 'RFC3443' is defined on line 1720, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 1738, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 1758, but no explicit reference was found in the text == Unused Reference: 'RFC3032' is defined on line 1769, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1772, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 1777, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 1790, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 1795, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 1798, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 1802, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 1806, 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-06 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-06 -- 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: 6 errors (**), 0 flaws (~~), 16 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau, Ed. 2 Internet Draft Cisco Systems, Inc. 3 Proposed Status: Standards Track 4 Expires: April 2005 Adrian Farrel, Ed. 5 Old Dog Consulting 7 October 2004 9 Generalized Multiprotocol Label Switching (GMPLS) 10 Label Switching Router (LSR) Management Information Base 12 draft-ietf-ccamp-gmpls-lsr-mib-06.txt 14 Status of this Memo 16 By submitting this Internet-Draft, I certify that any applicable 17 patent or other IPR claims of which I am aware have been disclosed, 18 and any of which I become aware will be disclosed, in accordance with 19 RFC 3668. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other documents 28 at any time. It is inappropriate to use Internet-Drafts as 29 reference material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) 37 for use with network management protocols in the Internet community. 38 In particular, it describes managed objects to configure and/or 39 monitor a Generalized Multiprotocol Label Switching (GMPLS) Label 40 Switching Router (LSR). 42 Table of Contents 43 1. Introduction ..................................... 2 44 1.1. Migration Strategy ....................... ..... 2 45 2. Terminology ...................................... 3 46 3. The SNMP Management Framework .................... 3 47 4. Outline .......................................... 3 48 4.1. Summary of the GMPLS LSR MIB Module ............ 4 49 4.1.1 Summary of the GMPLS LSR MIB Module ........... 4 50 4.1.2 Summary of the GMPLS Label MIB Module ......... 5 51 5. Bidirectional LSPs ............................... 5 52 6. Example of LSP Setup ............................. 5 53 7. GMPLS Label Switching Router MIB Definitions ..... 9 54 8. GMPLS Label MIB Definitions ..................... 19 55 9. Security Considerations ......................... 32 56 10. Acknowledgments ................................ 34 57 11. IANA Considerations ............................ 34 58 11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 34 59 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB .. 34 60 12. References ..................................... 34 61 12.1. Normative References ......................... 34 62 12.2. Informational References ..................... 36 63 13. Authors' Addresses ............................. 37 64 14. Full Copyright Statement ....................... 37 65 15. Intellectual Property Notice ................... 38 67 1. Introduction 69 This memo defines a portion of the Management Information Base (MIB) 70 for use with network management protocols in the Internet community. 71 In particular, it describes managed objects for modeling a 72 Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label 73 Switching Router (LSR). 75 Comments should be made directly to the CCAMP mailing list at 76 ccamp@ops.ietf.org. 78 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 80 document are to be interpreted as described in BCP 14, RFC 2119, 81 reference [RFC2119]. 83 1.1. Migration Strategy 85 There are two MIB modules in this document. The GMPLS LSR MIB module 86 extends the LSR MIB module defined for use with MPLS [RFC3813]. The 87 only changes made are additions for support of GMPLS or changes that 88 are necessary to support the increased complexity of a GMPLS system. 89 The GMPLS Label MIB module may be referenced using a row pointer from 90 objects within the LSR MIB module. 92 The companion document modeling and managing GMPLS based traffic 93 engineering [GMPLSTEMIB] extends the MPLS TE MIB module [RFC3812] 94 with the same intentions. 96 Textual conventions and OBJECT-IDENTIFIERS are defined in 97 [GMPLSTCMIB] which extends the set of textual conventions originally 98 defined in [RFC3811]. 100 2. Terminology 102 This document uses terminology from the document describing the MPLS 103 architecture [RFC3031] and the GMPLS architecture [GMPLSArch]. 105 A label switched path (LSP) is modeled as a connection consisting of 106 one or more incoming segments (in-segments) and/or one or more 107 outgoing segments (out-segments) at an LSR. The association or 108 interconnection of the in-segments and out-segments is accomplished 109 by using a cross-connect. We use the terminology "connection" and 110 "LSP" interchangeably where the meaning is clear from the context. 112 in-segment This is analogous to a GMPLS label on an interface. 113 out-segment This is analogous to a GMPLS label on an interface. 114 cross-connect This describes the conceptual connection between a 115 set of in-segments and out-segments. 116 Note that either set may be empty; for example, a 117 cross-connect may connect only out-segments 118 together with no in-segments in the case where an 119 LSP is originating on an LSR. 121 3. The SNMP Management Framework 123 For a detailed overview of the documents that describe the current 124 Internet-Standard Management Framework, please refer to section 7 of 125 RFC 3410 [RFC3410]. 127 Managed objects are accessed via a virtual information store, termed 128 the Management Information Base or MIB. MIB objects are generally 129 accessed through the Simple Network Management Protocol (SNMP). 130 Objects in the MIB are defined using the mechanisms defined in the 131 Structure of Management Information (SMI). This memo specifies a MIB 132 module that is compliant to the SMIv2, which is described in STD 58, 133 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 134 [RFC2580]. 136 4. Outline 138 Configuring statically provisioned GMPLS LSPs through an LSR involves 139 the following steps: 141 - Configuring an interface using the MPLS LSR MIB module. 143 - Enabling GMPLS on GMPLS capable interfaces using this MIB module. 145 - Configuring in-segments and out-segments using the MPLS LSR MIB 146 module. 148 - Configuring GMPLS extensions to the in-segments and out-segments 149 using this MIB module. 151 - Setting up the cross-connect table in the MPLS LSR MIB module to 152 associate segments and/or to indicate connection origination and 153 termination. 155 - Optionally setting up labels in the label table in this MIB module 156 if the textual convention MplsLabel is not capable of holding the 157 required label (for example, if the label requires more than 32 158 bits to encode it), or if the operator wishes to disambiguate 159 GMPLS label types. 161 - Optionally specifying label stack actions in the MPLS LSR MIB 162 module. 164 - Optionally specifying segment traffic parameters in the MPLS LSR 165 MIB module. 167 4.1 MIB Modules 169 There are two MIB modules defined in this document. 171 The GMPLS LSR MIB module contains tables that extend tables defined 172 in the MPLS LSR MIB module. This MIB module is used in conjunction 173 with the MPLS LSR MIB module in systems that support GMPLS. 175 The GMPLS Label MIB module contains objects for managing GMPLS labels 176 when they cannot be represented using the textual conventions of the 177 MPLS TC MIB module, or when more detailed access to the sub-fields of 178 the labels is required. 180 4.1.1 Summary of the GMPLS LSR MIB Module 182 The MIB tables in this MIB module are as follows. 184 - The interface configuration table (gmplsInterfaceTable), which 185 extends mplsInterfaceTable to enable the GMPLS protocol on MPLS- 186 capable interfaces. 188 - The in-segment (gmplsInSegmentTable) and out-segment 189 (gmplsOutSegmentTable) tables extend mplsInSegmentTable and 190 mplsOutSegmentTable to configuring GMPLS-specific parameters for 191 LSP segments at an LSR. 193 These tables are described in the subsequent sections. 195 4.1.2 Summary of the GMPLS Label MIB Module 197 There is one MIB table in this MIB module as follows. 199 - The gmplsLabelTable allows Generalized 200 Labels to be defined and managed in a central location. 201 Generalized Labels can be of variable length and have distinct 202 bit-by-bit interpretations according to the use that is made of 203 them. 205 These tables are described in the subsequent sections. 207 5. Bidirectional LSPs 209 This MIB module supports bidirectional LSPs as required for GMPLS. 210 A single value of mplsXCIndex is shared by all of the segments for 211 the entire bidirectional LSP. This facilitates a simple reference 212 from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing more obvious. 214 It is, however, important that the direction of segments is 215 understood to avoid connecting all in-segments to all out-segments. 216 This is achieved by an object in each segment that indicates the 217 direction of the segment with respect to data flow. 219 A segment that is marked as 'forward' carries data from the 'head' of 220 the LSP to the 'tail'. A segment marked as 'reverse' carries data in 221 the reverse direction. 223 Where an LSP is signaled using a conventional signaling protocol, the 224 'head' of the LSP is the source of the signaling (also known as the 225 ingress) and the 'tail' is the destination (also known as the 226 egress). For manually configured LSPs an arbitrary decision must be 227 made about which segments are 'forward' and which 'reverse'. For 228 consistency this decision should be made across all LSRs that 229 participate in the LSP by assigning 'head' and 'tail' ends to the 230 LSP. 232 6. Example of LSP Setup 234 In this section we provide a brief example of using the MIB objects 235 described in sections 7 and 8 to set up an LSP. While this example is 236 not meant to illustrate every nuance of the MIB, it is intended as an 237 aid to understanding some of the key concepts. It is meant to be read 238 after going through the MIB itself. A prerequisite is an 239 understanding of [RFC3813]. 241 Suppose that one would like to manually create a best-effort, 242 bi-directional LSP. Assume that, in the forward direction, the LSP 243 enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR 244 via MPLS interface B with ifIndex 13. For the reverse direction, we 245 assume the LSP enters via interface B and leaves via interface A 246 (i.e. the forward and reverse directions use the same bi-directional 247 interfaces). Let us also assume that we do not wish to have a label 248 stack beneath the top label on the outgoing labeled packets. The 249 following example illustrates which rows and corresponding objects 250 might be created to accomplish this. 252 We must first create rows in the gmplsLabelTable corresponding to the 253 labels required for each of the forward and reverse direction in- and 254 out-segments. For the purpose of this example the forward and 255 reverse labels on each interface will be the same, hence we need to 256 create just two rows in the gmplsLabelTable - one for each interface. 258 In gmplsLabelTable: 259 { 260 gmplsLabelInterface = 12, 261 gmplsLabelIndex = 1, 262 gmplsLabelSubindex = 0, 263 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 264 gmplsLabelFreeform = 0x123456789ABCDEF0 265 gmplsLabelRowStatus = createAndGo(4) 266 } 268 In gmplsLabelTable: 269 { 270 gmplsLabelInterface = 13, 271 gmplsLabelIndex = 1, 272 gmplsLabelSubindex = 0, 273 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 274 gmplsLabelFreeform = 0xFEDCBA9876543210 275 gmplsLabelRowStatus = createAndGo(4) 276 } 278 We must next create the appropriate in-segment and out-segment 279 entries. These are done in [RFC3813] using the mplsInSegmentTable and 280 mplsOutSegmentTable. Note that we use a row pointer to the two rows 281 in the gmplsLableTable rather than specifying the labels explicitly 282 in the in- and out-segment tables. Also note that the row status for 283 each row is set to createAndWait(5) to allow corresponding entries in 284 the gmplsInSegmentTable and gmplsOutSegmentTable to be created. 286 For the forward direction. 288 In mplsInSegmentTable: 289 { 290 mplsInSegmentIndex = 0x00000015 291 mplsInSegmentLabel = 0, -- incoming label in label table 292 mplsInSegmentNPop = 1, 293 mplsInSegmentInterface = 12, -- incoming interface 295 -- RowPointer MUST point to the first accesible column. 296 mplsInSegmentTrafficParamPtr = 0.0, 297 mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0) 298 mplsInSegmentRowStatus = createAndWait(5) 299 } 301 In mplsOutSegmentTable: 302 { 303 mplsOutSegmentIndex = 0x00000012, 304 mplsOutSegmentInterface = 13, -- outgoing interface 305 mplsOutSegmentPushTopLabel = true(1), 306 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 308 -- RowPointer MUST point to the first accesible column. 309 mplsOutSegmentTrafficParamPtr = 0.0, 310 mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0) 311 mplsOutSegmentRowStatus = createAndWait(5) 312 } 314 For the reverse direction. 316 In mplsInSegmentTable: 317 { 318 mplsInSegmentIndex = 0x00000016 320 mplsInSegmentLabel = 0, -- incoming label in label table 321 mplsInSegmentNPop = 1, 322 mplsInSegmentInterface = 13, -- incoming interface 324 -- RowPointer MUST point to the first accesible column. 325 mplsInSegmentTrafficParamPtr = 0.0, 326 mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0) 328 mplsInSegmentRowStatus = createAndWait(5) 329 } 331 In mplsOutSegmentTable: 332 { 333 mplsOutSegmentIndex = 0x00000013, 334 mplsOutSegmentInterface = 12, -- outgoing interface 335 mplsOutSegmentPushTopLabel = true(1), 336 mplsOutSegmentTopLabel = 0, -- outgoing label in label table 338 -- RowPointer MUST point to the first accesible column. 339 mplsOutSegmentTrafficParamPtr = 0.0, 340 mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0) 342 mplsOutSegmentRowStatus = createAndWait(5) 343 } 345 These table entries are extended by entries in gmplsInSegmentTable 346 and gmplsOutSegmentTable. Note that the nature of the 'extends' 347 relationship is that the entry in gmplsInSegmentTable has the same 348 index values as the entry in mplsInSegmentTable. Similarly, the entry 349 in gmplsOutSegmentTable has the same index values as the entry in 350 mplsOutSegmentTable. 352 First for the forward direction: 354 In gmplsInSegmentTable(0x00000015) 355 { 356 gmplsInSegmentDirection = forward (1) 357 } 359 In gmplsOutSegmentTable(0x00000012) 360 { 361 gmplsOutSegmentDirection = forward (1) 362 } 364 Next for the reverse direction: 366 In gmplsInSegmentTable(0x00000016) 367 { 368 gmplsInSegmentDirection = reverse (2) 369 } 371 In gmplsOutSegmentTable(0x00000013) 372 { 373 gmplsOutSegmentDirection = reverse (2) 374 } 376 Next, two cross-connect entries are created in the mplsXCTable of the 377 MPLS LSR MIB, thereby associating the newly created segments 378 together. 380 In mplsXCTable: 381 { 382 mplsXCIndex = 0x01, 383 mplsXCInSegmentIndex = 0x00000015, 384 mplsXCOutSegmentIndex = 0x00000012, 385 mplsXCLspId = 0x0102 -- unique ID 386 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 387 mplsXCRowStatus = createAndGo(4) 388 } 390 In mplsXCTable: 391 { 392 mplsXCIndex = 0x02, 393 mplsXCInSegmentIndex = 0x00000016, 394 mplsXCOutSegmentIndex = 0x00000013, 395 mplsXCLspId = 0x0102 -- unique ID 396 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 397 mplsXCRowStatus = createAndGo(4) 398 } 399 Finally, the in-segments and out-segments are activated. 401 In mplsInSegmentTable(0x00000015): 402 { 403 mplsInSegmentRowStatus = active(1) 404 } 405 In mplsInSegmentTable(0x00000016): 406 { 407 mplsInSegmentRowStatus = active(1) 408 } 409 In mplsOutSegmentTable(0x00000012): 410 { 411 mplsOutSegmentRowStatus = active(1) 412 } 413 In mplsOutSegmentTable(0x00000013): 414 { 415 mplsOutSegmentRowStatus = active(1) 416 } 418 7. GMPLS Label Switching Router MIB Definitions 420 GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN 422 IMPORTS 423 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, zeroDotZero 424 FROM SNMPv2-SMI -- [RFC2578] 425 MODULE-COMPLIANCE, OBJECT-GROUP 426 FROM SNMPv2-CONF -- [RFC2580] 427 RowPointer 428 FROM SNMPv2-TC -- [RFC2579] 429 GmplsSegmentDirection 430 FROM GMPLS-TC-STD-MIB -- [GMPLSTCMIB] 431 mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex 432 FROM MPLS-LSR-STD-MIB -- [RFC3813] 433 mplsStdMIB 434 FROM MPLS-TC-STD-MIB -- [RFC3811] 435 ; 437 gmplsLsrStdMIB MODULE-IDENTITY 438 LAST-UPDATED 439 "200410080001Z" -- 8 October 2004 00:00:01 GMT 440 ORGANIZATION 441 "Common Control And Measurement Plane (CCAMP) Working Group" 442 CONTACT-INFO 443 " Thomas D. Nadeau 444 Cisco Systems, Inc. 445 Email: tnadeau@cisco.com 447 Adrian Farrel 448 Old Dog Consulting 449 Email: adrian@olddog.co.uk 450 Comments about this document should be emailed direct to the 451 CCAMP working group mailing list at ccamp@ops.ietf.org" 452 DESCRIPTION 453 "Copyright (C) The Internet Society (2004). The 454 initial version of this MIB module was published 455 in RFC xxxx. For full legal notices see the RFC 456 itself or see: http://www.ietf.org/copyrights/ianamib.html 458 This MIB module contains managed object definitions 459 for the Generalized Multiprotocol (GMPLS) Label Switching 460 Router as defined in: 461 Generalized Multi-Protocol Label Switching (GMPLS) 462 Architecture,Mannie et al., 463 draft-ietf-ccamp-gmpls-architecture-07.txt, May 2003, 464 work in progress." 466 -- Revision history. 468 REVISION 469 "200410080001Z" -- 8 October 2004 00:00:01 GMT 470 DESCRIPTION 471 "Initial version issued as part of RFC XXXX." 472 ::= { mplsStdMIB xx } 474 -- Top level components of this MIB module. 476 -- Notifications 477 -- no notifications are currently defined. 478 gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 } 480 -- Tables, Scalars 481 gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } 483 -- Conformance 484 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } 486 -- GMPLS Interface Table. 488 gmplsInterfaceTable OBJECT-TYPE 489 SYNTAX SEQUENCE OF GmplsInterfaceEntry 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "This table specifies per-interface GMPLS capability 494 and associated information. It extends the 495 information in mplsInterfaceTable." 496 ::= { gmplsLsrObjects 1 } 498 gmplsInterfaceEntry OBJECT-TYPE 499 SYNTAX GmplsInterfaceEntry 500 MAX-ACCESS not-accessible 501 STATUS current 502 DESCRIPTION 503 "A conceptual row in this table is created 504 automatically by an LSR for every interface capable 505 of supporting GMPLS and which is configured to do 506 so. A conceptual row in this table will exist if and 507 only if a corresponding entry in mplsInterfaceTable 508 exists, and a corresponding entry in ifTable exists 509 with ifType = mpls(166). If the associated entry in 510 ifTable is operationally disabled (thus removing the 511 GMPLS capabilities on the interface) or the entry in 512 mplsInterfaceTable is deleted, the corresponding 513 entry in this table MUST be deleted shortly 514 thereafter. 516 The indexing is the same as that for mplsInterfaceTable. 517 Thus, the entry with index 0 represents the per-platform 518 label space and contains parameters that apply to all 519 interfaces that participate in the per-platform label space." 520 INDEX { mplsInterfaceIndex } 521 ::= { gmplsInterfaceTable 1 } 523 GmplsInterfaceEntry ::= SEQUENCE { 524 gmplsInterfaceSignalingCaps BITS, 525 gmplsInterfaceRsvpHelloPeriod Unsigned32 526 } 528 gmplsInterfaceSignalingCaps OBJECT-TYPE 529 SYNTAX BITS { 530 unknown (0), 531 rsvpGmpls (1), 532 crldpGmpls (2), -- note the use of CR-LDP is deprecated 533 otherGmpls (3) 534 } 535 MAX-ACCESS read-create 536 STATUS current 537 DESCRIPTION 538 "Defines the signaling capabilities on this 539 interface. Multiple bits may legitimately be set at 540 once. Setting no bits implies that GMPLS signaling 541 cannot be performed on this interface and all LSPs 542 must be manually provisioned or that this table 543 entry is only present to supplement an entry in 544 the mplsInterfaceTable by providing the information 545 carried in other objects in this row." 546 DEFVAL { { rsvpGmpls } } 547 ::= { gmplsInterfaceEntry 1 } 548 gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE 549 SYNTAX Unsigned32 550 UNITS "milliseconds" 551 MAX-ACCESS read-create 552 STATUS current 553 DESCRIPTION 554 "Period, in milliseconds, between sending RSVP Hello 555 messages on this interface. A value of 0 indicates 556 that no Hello messages should be sent on this interface." 557 REFERENCE 558 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 559 (Editor), RFC 3473, January 2003." 560 DEFVAL { 3000 } 561 ::= { gmplsInterfaceEntry 2 } 563 -- End of gmplsInterfaceTable 565 -- In-segment table. 567 gmplsInSegmentTable OBJECT-TYPE 568 SYNTAX SEQUENCE OF GmplsInSegmentEntry 569 MAX-ACCESS not-accessible 570 STATUS current 571 DESCRIPTION 572 "This table extends the mplsInSegmentTable to provide GMPLS- 573 specific information about incoming segments to an LSR." 574 ::= { gmplsLsrObjects 2 } 576 gmplsInSegmentEntry OBJECT-TYPE 577 SYNTAX GmplsInSegmentEntry 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "An entry in this table extends the representation of 582 an incoming segment represented by an entry in 583 mplsInSegmentTable. An entry can be created by a 584 network administrator or an SNMP agent, or a GMPLS 585 signaling protocol. 587 Note that the storage type for this entry SHOULD be 588 inherited from the corresponding entry in the 589 mplsInSegmentTable given by the value of the 590 mplsInSegmentStorageType object." 591 INDEX { mplsInSegmentIndex } 592 ::= { gmplsInSegmentTable 1 } 594 GmplsInSegmentEntry ::= SEQUENCE { 595 gmplsInSegmentDirection GmplsSegmentDirection, 596 gmplsInSegmentExtraParamsPtr RowPointer 597 } 598 gmplsInSegmentDirection OBJECT-TYPE 599 SYNTAX GmplsSegmentDirection 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "This object indicates the direction of data flow on 604 this segment. This object cannot be modified if 605 mplsInSegmentRowStatus for the associated entry in 606 the mplsInSegmentTable is active(1)." 607 DEFVAL { forward } 608 ::= { gmplsInSegmentEntry 1 } 610 gmplsInSegmentExtraParamsPtr OBJECT-TYPE 611 SYNTAX RowPointer 612 MAX-ACCESS read-create 613 STATUS current 614 DESCRIPTION 615 "Some Tunnels will run over transports that can 616 usefully support technology-specific additional parameters 617 (for example, SONET resource usage). Such can be supplied from 618 an external table and referenced from here. 619 A value of zeroDotzero in this attribute indicates that there 620 is no such additional information." 621 DEFVAL { zeroDotZero } 622 ::= { gmplsInSegmentEntry 2 } 624 -- End of gmplsInSegmentTable 626 -- Out-segment table. 628 gmplsOutSegmentTable OBJECT-TYPE 629 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 630 MAX-ACCESS not-accessible 631 STATUS current 632 DESCRIPTION 633 "This table extends the mplsOutSegmentTable to 634 provide GMPLS-specific information about outgoing 635 segments from an LSR." 636 ::= { gmplsLsrObjects 3 } 638 gmplsOutSegmentEntry OBJECT-TYPE 639 SYNTAX GmplsOutSegmentEntry 640 MAX-ACCESS not-accessible 641 STATUS current 642 DESCRIPTION 643 "An entry in this table extends the representation of 644 an outgoing segment represented by an entry in 645 mplsOutSegmentTable. An entry can be created by a 646 network administrator or an SNMP agent, or a GMPLS 647 signaling protocol. 649 Note that the storage type for this entry SHOULD be 650 inherited from the corresponding entry in the 651 mplsOutSegmentTable given by the value of the 652 mplsOutSegmentStorageType object." 653 INDEX { mplsOutSegmentIndex } 654 ::= { gmplsOutSegmentTable 1 } 656 GmplsOutSegmentEntry ::= SEQUENCE { 657 gmplsOutSegmentDirection GmplsSegmentDirection, 658 gmplsOutSegmentTTLDecrement Unsigned32, 659 gmplsOutSegmentExtraParamsPtr RowPointer 660 } 662 gmplsOutSegmentDirection OBJECT-TYPE 663 SYNTAX GmplsSegmentDirection 664 MAX-ACCESS read-create 665 STATUS current 666 DESCRIPTION 667 "This object indicates the direction of data flow on 668 this segment. This object cannot be modified if 669 mplsOutSegmentRowStatus for the associated entry in 670 the mplsOutSegmentTable is active(1)." 671 DEFVAL { forward } 672 ::= { gmplsOutSegmentEntry 1 } 674 gmplsOutSegmentTTLDecrement OBJECT-TYPE 675 SYNTAX Unsigned32 (0..255) 676 MAX-ACCESS read-create 677 STATUS current 678 DESCRIPTION 679 "This object indicates the amount by which to 680 decrement the TTL of any payload packets forwarded 681 on this segment if per-hop decrementing is being 682 done. 683 A value of zero indicates that no decrement should 684 be made or that per-hop decrementing is not in 685 force. 686 See the gmplsTunnelTTLDecrement object in the 687 gmplsTunnelTable of [GMPLSTEMIB] for a value by 688 which to decrement the TTL for the whole of a 689 tunnel. 690 This object cannot be modified if 691 mplsOutSegmentRowStatus for the associated entry in 692 the mplsOutSegmentTable is active(1)." 693 REFERENCE 694 "Time To Live (TTL) Processing in Multi-Protocol Label Switching 695 (MPLS) Networks, Agarwal, P., Akyol, B., RFC 3443, January 2003" 696 DEFVAL { 0 } 697 ::= { gmplsOutSegmentEntry 2 } 698 gmplsOutSegmentExtraParamsPtr OBJECT-TYPE 699 SYNTAX RowPointer 700 MAX-ACCESS read-create 701 STATUS current 702 DESCRIPTION 703 "Some Tunnels will run over transports that can 704 usefully support technology-specific additional parameters 705 (for example, SONET resource usage). Such can be supplied from 706 an external table and referenced from here. 707 A value of zeroDotzero in this attribute indicates that there 708 is no such additional information." 709 DEFVAL { zeroDotZero } 710 ::= { gmplsOutSegmentEntry 3 } 712 -- End of gmplsOutSegmentTable 714 -- Module compliance. 716 gmplsLsrGroups 717 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 719 gmplsLsrCompliances 720 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 722 -- Compliance requirement for fully compliant implementations. 724 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 725 STATUS current 726 DESCRIPTION 727 "Compliance statement for agents that provide full 728 support for GMPLS-LSR-STD-MIB." 730 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 732 MANDATORY-GROUPS { 733 ifGeneralInformationGroup, 734 ifCounterDiscontinuityGroup 735 } 737 MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB 739 MANDATORY-GROUPS { 740 mplsInterfaceGroup, 741 mplsInSegmentGroup, 742 mplsOutSegmentGroup, 743 mplsXCGroup, 744 mplsPerfGroup, 745 mplsLsrNotificationGroup 746 } 747 MODULE -- this module 749 MANDATORY-GROUPS { 750 gmplsInterfaceGroup, 751 gmplsInSegmentGroup, 752 gmplsOutSegmentGroup 753 } 755 -- gmplsInSegmentTable 757 OBJECT gmplsInSegmentDirection 758 SYNTAX GmplsSegmentDirection 759 MIN-ACCESS read-write 760 DESCRIPTION 761 "Only forward(1) needs to be supported by 762 implementations that only support unidirectional 763 LSPs." 765 -- gmplsOutSegmentTable 767 OBJECT gmplsOutSegmentDirection 768 SYNTAX GmplsSegmentDirection 769 MIN-ACCESS read-write 770 DESCRIPTION 771 "Only forward(1) needs to be supported by 772 implementations that only support unidirectional 773 LSPs." 775 OBJECT gmplsOutSegmentTTLDecrement 776 SYNTAX Unsigned32 (0..255) 777 MIN-ACCESS read-only 778 DESCRIPTION 779 "Write access is not required." 781 ::= { gmplsLsrCompliances 1 } 783 -- Compliance requirement for implementations that provide read-only 784 -- access. 786 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 787 STATUS current 788 DESCRIPTION 789 "Compliance requirement for implementations that only 790 provide read-only support for GMPLS-LSR-STD-MIB. Such 791 devices can then be monitored but cannot be configured 792 using this MIB modules." 794 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 795 MANDATORY-GROUPS { 796 ifGeneralInformationGroup, 797 ifCounterDiscontinuityGroup 798 } 800 MODULE MPLS-LSR-STD-MIB 802 MANDATORY-GROUPS { 803 mplsInterfaceGroup, 804 mplsInSegmentGroup, 805 mplsOutSegmentGroup, 806 mplsXCGroup, 807 mplsPerfGroup 808 } 810 MODULE -- this module 812 MANDATORY-GROUPS { 813 gmplsInterfaceGroup, 814 gmplsInSegmentGroup, 815 gmplsOutSegmentGroup 816 } 818 -- gmplsInterfaceGroup 820 OBJECT gmplsInterfaceSignalingCaps 821 SYNTAX BITS { 822 unknown (0), 823 rsvpGmpls (1), 824 crldpGmpls (2), 825 otherGmpls (3) 826 } 827 MIN-ACCESS read-only 828 DESCRIPTION 829 "Write access is not required." 831 OBJECT gmplsInterfaceRsvpHelloPeriod 832 SYNTAX Unsigned32 833 MIN-ACCESS read-only 834 DESCRIPTION 835 "Write access is not required." 837 -- gmplsInSegmentTable 839 OBJECT gmplsInSegmentDirection 840 SYNTAX GmplsSegmentDirection 841 MIN-ACCESS read-only 842 DESCRIPTION 843 "Write access is not required. Only forward(1) needs 844 to be supported by implementations that only support 845 unidirectional LSPs." 847 OBJECT gmplsInSegmentExtraParamsPtr 848 SYNTAX RowPointer 849 MIN-ACCESS read-only 850 DESCRIPTION 851 "Write access is not required." 853 -- gmplsOutSegmentTable 855 OBJECT gmplsOutSegmentDirection 856 SYNTAX GmplsSegmentDirection 857 MIN-ACCESS read-only 858 DESCRIPTION 859 "Write access is not required. Only forward(1) needs 860 to be supported by implementations that only support 861 unidirectional LSPs." 863 OBJECT gmplsOutSegmentTTLDecrement 864 SYNTAX Unsigned32 (0..255) 865 MIN-ACCESS read-only 866 DESCRIPTION 867 "Write access is not required." 869 OBJECT gmplsOutSegmentExtraParamsPtr 870 SYNTAX RowPointer 871 MIN-ACCESS read-only 872 DESCRIPTION 873 "Write access is not required." 875 ::= { gmplsLsrCompliances 2 } 877 -- Units of conformance. 879 gmplsInterfaceGroup OBJECT-GROUP 880 OBJECTS { 881 gmplsInterfaceSignalingCaps, 882 gmplsInterfaceRsvpHelloPeriod 883 } 884 STATUS current 885 DESCRIPTION 886 "Collection of objects needed for GMPLS interface 887 configuration and performance information." 888 ::= { gmplsLsrGroups 1 } 890 gmplsInSegmentGroup OBJECT-GROUP 891 OBJECTS { 892 gmplsInSegmentDirection, 893 gmplsInSegmentExtraParamsPtr 894 } 895 STATUS current 896 DESCRIPTION 897 "Collection of objects needed to implement a GMPLS 898 in-segment." 899 ::= { gmplsLsrGroups 2 } 901 gmplsOutSegmentGroup OBJECT-GROUP 902 OBJECTS { 903 gmplsOutSegmentDirection, 904 gmplsOutSegmentTTLDecrement, 905 gmplsOutSegmentExtraParamsPtr 906 } 907 STATUS current 908 DESCRIPTION 909 "Collection of objects needed to implement a GMPLS 910 out-segment." 911 ::= { gmplsLsrGroups 3 } 912 END 914 8. GMPLS Label MIB Definitions 916 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 918 IMPORTS 919 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, 920 Integer32 921 FROM SNMPv2-SMI -- [RFC2578] 922 MODULE-COMPLIANCE, OBJECT-GROUP 923 FROM SNMPv2-CONF -- [RFC2580] 924 RowStatus, StorageType 925 FROM SNMPv2-TC -- [RFC2579] 926 InterfaceIndexOrZero 927 FROM IF-MIB -- [RFC2863] 928 IndexIntegerNextFree 929 FROM DIFFSERV-MIB -- [RFC3289] 930 MplsLabel 931 FROM MPLS-TC-STD-MIB -- [RFC3811] 932 GmplsGeneralizedLabelTypes, GmplsFreeformLabel 933 FROM GMPLS-TC-STD-MIB -- [GMPLSTCMIB] 934 mplsStdMIB 935 FROM MPLS-TC-STD-MIB -- [RFC3811] 936 ; 938 gmplsLabelStdMIB MODULE-IDENTITY 939 LAST-UPDATED 940 "200410080001Z" -- 8 October 2004 00:00:01 GMT 941 ORGANIZATION 942 "Common Control And Measurement Plane (CCAMP) Working Group" 943 CONTACT-INFO 944 " Thomas D. Nadeau 945 Cisco Systems, Inc. 946 Email: tnadeau@cisco.com 947 Adrian Farrel 948 Old Dog Consulting 949 Email: adrian@olddog.co.uk 951 Comments about this document should be emailed direct to the 952 CCAMP working group mailing list at ccamp@ops.ietf.org" 953 DESCRIPTION 954 "Copyright (C) The Internet Society (2004). The 955 initial version of this MIB module was published 956 in RFC xxxx. For full legal notices see the RFC 957 itself or see: http://www.ietf.org/copyrights/ianamib.html 959 This MIB module contains managed object definitions 960 for labels within GMPLS systems as defined in: 962 Generalized Multi-Protocol Label Switching (GMPLS) 963 Signaling Functional Description, Berger, L. (Editor), 964 RFC 3471, January 2003." 966 -- Revision history. 967 REVISION 968 "200410080001Z" -- 8 October 2004 00:00:01 GMT 969 DESCRIPTION 970 "Initial version issued as part of RFC XXXX." 971 ::= { mplsStdMIB xx } 973 -- Top level components of this MIB module. 975 -- Notifications 976 -- no notifications are currently defined. 977 gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 } 979 -- Tables, Scalars 980 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 982 -- Conformance 983 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 985 -- GMPLS Label Table. 987 gmplsLabelIndexNext OBJECT-TYPE 988 SYNTAX IndexIntegerNextFree 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "This object contains an unused value for 993 gmplsLabelIndex, or a zero to indicate 994 that no unused value exists or is available. 996 An management application wishing to create 997 a row in the gmplsLabelTable may read this 998 object and then attempt to create a row in 999 the table. If row creation fails (because 1000 another application has already created a row 1001 with the supplied index) the management 1002 application should read this object again 1003 to get a new index value. 1005 When a row is created in the gmplsLabelTable 1006 with the gmplsLabelIndex value held by this 1007 object, an implementation MUST change the value 1008 in this object." 1009 ::= { gmplsLabelObjects 1 } 1011 gmplsLabelTable OBJECT-TYPE 1012 SYNTAX SEQUENCE OF GmplsLabelEntry 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "Table of GMPLS Labels. This table allows the representation 1017 of the more complex label forms required for GMPLS which 1018 cannot be held within the textual convention MplsLabel. That 1019 is labels that cannot be encoded within 32 bits. It is, 1020 nevertheless also capable of holding 32 bit labels or 1021 regular MPLS labels if desired. 1023 Each entry in this table represents an individual 1024 GMPLS label value. Labels in the tables in other 1025 MIBs are referred to using row pointer into this 1026 table. The indexing of this table provides for 1027 arbitrary indexing and also for concatenation of 1028 labels." 1029 ::= { gmplsLabelObjects 2 } 1031 gmplsLabelEntry OBJECT-TYPE 1032 SYNTAX GmplsLabelEntry 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "An entry in this table represents a single label 1037 value. There are three indexes into the table. 1038 - The interface index may be helpful to distinguish 1039 which labels are in use on which interfaces or to 1040 handle cases where there are a very large number 1041 of labels in use in the system. When label 1042 representation is desired to apply to the whole 1043 system or when it is not important to distinguish 1044 labels by their interfaces, this index MAY be set 1045 to zero. 1046 - The label index provides a way of identifying the 1047 label. 1049 - The label sub-index is only used for concatenated 1050 labels. It identifies each component label. When 1051 non-concatenated labels are used, this index 1052 SHOULD be set to zero. 1054 A storage type object is supplied to control the 1055 storage type for each entry, but implementations 1056 should note that the storage type of conceptual rows 1057 in other tables that include row pointers to an 1058 entry in this table SHOULD dictate the storage type 1059 of the rows in this table where the row in the other 1060 table is more persistent." 1061 INDEX { 1062 gmplsLabelInterface, 1063 gmplsLabelIndex, 1064 gmplsLabelSubindex } 1065 ::= { gmplsLabelTable 1 } 1067 GmplsLabelEntry ::= SEQUENCE { 1068 gmplsLabelInterface InterfaceIndexOrZero, 1069 gmplsLabelIndex Unsigned32, 1070 gmplsLabelSubindex Unsigned32, 1071 gmplsLabelType GmplsGeneralizedLabelTypes, 1072 gmplsLabelMplsLabel MplsLabel, 1073 gmplsLabelPortWavelength Unsigned32, 1074 gmplsLabelFreeform GmplsFreeformLabel, 1075 gmplsLabelSonetSdhSignalIndex Integer32, 1076 gmplsLabelSdhVc Integer32, 1077 gmplsLabelSdhVcBranch Integer32, 1078 gmplsLabelSonetSdhBranch Integer32, 1079 gmplsLabelSonetSdhGroupBranch Integer32, 1080 gmplsLabelWavebandId Unsigned32, 1081 gmplsLabelWavebandStart Unsigned32, 1082 gmplsLabelWavebandEnd Unsigned32, 1083 gmplsLabelRowStatus RowStatus, 1084 gmplsLabelStorageType StorageType 1085 } 1087 gmplsLabelInterface OBJECT-TYPE 1088 SYNTAX InterfaceIndexOrZero 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "The interface on which this label is used. If the 1093 label has or could have applicability across the 1094 whole system, this object SHOULD be set to zero." 1095 ::= { gmplsLabelEntry 1 } 1097 gmplsLabelIndex OBJECT-TYPE 1098 SYNTAX Unsigned32 (0..4294967295) 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "An arbitrary index into the table to identify a label. 1103 Note that implementations that are representing 32 bit 1104 labels within this table MAY choose to align this index 1105 with the value of the label, but should be aware of the 1106 implications of sparsely populated tables. 1107 A management application may read the gmplsLabelIndexNext 1108 object to find a suitable value for this object." 1109 ::= { gmplsLabelEntry 2 } 1111 gmplsLabelSubindex OBJECT-TYPE 1112 SYNTAX Unsigned32 (0..4294967295) 1113 MAX-ACCESS not-accessible 1114 STATUS current 1115 DESCRIPTION 1116 "In conjunction with gmplsLabelInterface and gmplsLabelIndex, 1117 this object uniquely identifies this row. This sub-index 1118 allows a single GMPLS label to be defined as a concatenation 1119 of labels. This is particularly useful in TDM. 1121 The ordering of sub-labels is strict with the sub-label with 1122 lowest gmplsLabelSubindex appearing first. Note that all 1123 sub-labels of a single GMPLS label must share the same 1124 gmplsLabelInterface and gmplsLabelIndex values. For labels 1125 that are not composed of concatenated sub-labels, this value 1126 SHOULD be set to zero." 1127 ::= { gmplsLabelEntry 3 } 1129 gmplsLabelType OBJECT-TYPE 1130 SYNTAX GmplsGeneralizedLabelTypes 1131 MAX-ACCESS read-create 1132 STATUS current 1133 DESCRIPTION 1134 "Identifies the type of this label. Note that this object 1135 does not determine whether MPLS or GMPLS signaling is in 1136 use: a value of gmplsMplsLabel (1) denotes that a 23 bit 1137 MPLS packet label is present, but does not describe 1138 whether this is signaled using MPLS or GMPLS. 1140 The value of this object helps determine which of 1141 the following objects are valid. 1142 This object cannot be modified if 1143 gmplsLabelRowStatus is active(1)." 1144 REFERENCE 1145 "Generalized Multi-Protocol Label Switching (GMPLS) 1146 Signaling Functional Description, Berger, L. (Editor), 1147 RFC 3471, January 2003." 1148 ::= { gmplsLabelEntry 4 } 1149 gmplsLabelMplsLabel OBJECT-TYPE 1150 SYNTAX MplsLabel 1151 MAX-ACCESS read-create 1152 STATUS current 1153 DESCRIPTION 1154 "The value of an MPLS label (that is a packet label) 1155 if this table is used to store it. This may be used 1156 in MPLS systems even though the label values can be 1157 adequately stored in the MPLS MIB modules. Further, 1158 in mixed MPLS and GMPLS systems it may be 1159 advantageous to store all labels in a single label 1160 table. Lastly, in GMPLS systems where packet labels 1161 are used (that is in systems that use GMPLS 1162 signaling and GMPLS labels for packet switching) it 1163 may be desirable to use this table. 1164 This object is only valid if gmplsLabelType is set 1165 to gmplsMplsLabel (1). 1166 This object cannot be modified if 1167 gmplsLabelRowStatus is active(1)." 1168 REFERENCE 1169 "MPLS Label Stack Encoding, Rosen, E. et al, RFC 3032, 1170 January 2001." 1171 DEFVAL { 0 } 1172 ::= { gmplsLabelEntry 6 } 1174 gmplsLabelPortWavelength OBJECT-TYPE 1175 SYNTAX Unsigned32 1176 MAX-ACCESS read-create 1177 STATUS current 1178 DESCRIPTION 1179 "The value of a Port or Wavelength Label when carried 1180 as a Generalized Label. Only valid if gmplsLabelType 1181 is set to gmplsPortWavelengthLabel(2). 1182 This object cannot be modified if 1183 gmplsLabelRowStatus is active(1)." 1184 REFERENCE 1185 "Generalized Multi-Protocol Label Switching (GMPLS) 1186 Signaling Functional Description, Berger, L. (Editor), 1187 RFC 3471, January 2003." 1188 DEFVAL { 0 } 1189 ::= { gmplsLabelEntry 7 } 1191 gmplsLabelFreeform OBJECT-TYPE 1192 SYNTAX GmplsFreeformLabel 1193 MAX-ACCESS read-create 1194 STATUS current 1195 DESCRIPTION 1196 "The value of a freeform Generalized Label that does 1197 not conform to one of the standardized label 1198 encoding or that an implementation chooses to 1199 represent as an octet string without further 1200 decoding. Only valid if gmplsLabelType is set to 1201 gmplsFreeformGeneralizedLabel(3). This object 1202 cannot be modified if gmplsLabelRowStatus is active(1)." 1203 ::= { gmplsLabelEntry 8 } 1205 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 1206 SYNTAX Integer32 (0..4095) 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "The Signal Index value (S) of a SONET or SDH 1211 Generalized Label. Zero indicates that this field is 1212 not significant. Only valid if gmplsLabelType is set 1213 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1214 This object cannot be modified if 1215 gmplsLabelRowStatus is active(1)." 1216 REFERENCE 1217 "Generalized Multi-Protocol Label Switching Extensions 1218 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1219 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1220 February 2003, work in progress." 1221 DEFVAL { 0 } 1222 ::= { gmplsLabelEntry 9 } 1224 gmplsLabelSdhVc OBJECT-TYPE 1225 SYNTAX Integer32 (0..15) 1226 MAX-ACCESS read-create 1227 STATUS current 1228 DESCRIPTION 1229 "The VC Indicator (U) of an SDH Generalized Label. 1230 Zero indicates that this field is non-significant. 1231 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). 1232 This object cannot be modified if 1233 gmplsLabelRowStatus is active(1)." 1234 REFERENCE 1235 "Generalized Multi-Protocol Label Switching Extensions 1236 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1237 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1238 February 2003, work in progress." 1239 DEFVAL { 0 } 1240 ::= { gmplsLabelEntry 10 } 1242 gmplsLabelSdhVcBranch OBJECT-TYPE 1243 SYNTAX Integer32 (0..15) 1244 MAX-ACCESS read-create 1245 STATUS current 1246 DESCRIPTION 1247 "The VC Branch Indicator (K) of an SDH Generalized 1248 Label. Zero indicates that this field is non-significant. 1249 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This 1250 object cannot be modified if gmplsLabelRowStatus is active(1)." 1252 REFERENCE 1253 "Generalized Multi-Protocol Label Switching Extensions 1254 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1255 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1256 February 2003, work in progress." 1257 DEFVAL { 0 } 1258 ::= { gmplsLabelEntry 11 } 1260 gmplsLabelSonetSdhBranch OBJECT-TYPE 1261 SYNTAX Integer32 (0..15) 1262 MAX-ACCESS read-create 1263 STATUS current 1264 DESCRIPTION 1265 "The Branch Indicator (L) of a SONET or SDH 1266 Generalized Label. Zero indicates that this field is 1267 non-significant. Only valid gmplsLabelType is set to 1268 gmplsSonetLabel(4) or gmplsSdhLabel(5). 1269 This object cannot be modified if 1270 gmplsLabelRowStatus is active(1)." 1271 REFERENCE 1272 "Generalized Multi-Protocol Label Switching Extensions 1273 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1274 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1275 February 2003, work in progress." 1276 DEFVAL { 0 } 1277 ::= { gmplsLabelEntry 12 } 1279 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1280 SYNTAX Integer32 (0..15) 1281 MAX-ACCESS read-create 1282 STATUS current 1283 DESCRIPTION 1284 "The Group Branch Indicator (M) of a SONET or SDH 1285 Generalized Label. Zero indicates that this field is 1286 non-significant. Only valid if gmplsLabelType is set 1287 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1288 This object cannot be modified if 1289 gmplsLabelRowStatus is active(1)." 1290 REFERENCE 1291 "Generalized Multi-Protocol Label Switching Extensions 1292 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1293 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1294 February 2003, work in progress." 1295 DEFVAL { 0 } 1296 ::= { gmplsLabelEntry 13 } 1298 gmplsLabelWavebandId OBJECT-TYPE 1299 SYNTAX Unsigned32 1300 MAX-ACCESS read-create 1301 STATUS current 1302 DESCRIPTION 1303 "The waveband identifier component of a waveband label. Only 1304 valid if gmplsLabelType is set to gmplsWavebandLabel(6). This 1305 object cannot be modified if gmplsLabelRowStatus is active(1)." 1306 REFERENCE 1307 "Generalized Multi-Protocol Label Switching (GMPLS) 1308 Signaling Functional Description, Berger, L. (Editor), 1309 RFC 3471, January 2003." 1310 DEFVAL { 0 } 1311 ::= { gmplsLabelEntry 14 } 1313 gmplsLabelWavebandStart OBJECT-TYPE 1314 SYNTAX Unsigned32 1315 MAX-ACCESS read-create 1316 STATUS current 1317 DESCRIPTION 1318 "The starting label component of a waveband label. 1319 Only valid if gmplsLabelType is set to 1320 gmplsWavebandLabel(6). 1321 This object cannot be modified if 1322 gmplsLabelRowStatus is active(1)." 1323 REFERENCE 1324 "Generalized Multi-Protocol Label Switching (GMPLS) 1325 Signaling Functional Description, Berger, L. (Editor), 1326 RFC 3471, January 2003." 1327 DEFVAL { 0 } 1328 ::= { gmplsLabelEntry 15 } 1330 gmplsLabelWavebandEnd OBJECT-TYPE 1331 SYNTAX Unsigned32 1332 MAX-ACCESS read-create 1333 STATUS current 1334 DESCRIPTION 1335 "The end label component of a waveband label. Only 1336 valid if gmplsLabelType is set to gmplsWavebandLabel(6). 1337 This object cannot be modified if 1338 gmplsLabelRowStatus is active(1)." 1339 REFERENCE 1340 "Generalized Multi-Protocol Label Switching (GMPLS) 1341 Signaling Functional Description, Berger, L. (Editor), 1342 RFC 3471, January 2003." 1343 DEFVAL { 0 } 1344 ::= { gmplsLabelEntry 16 } 1346 gmplsLabelRowStatus OBJECT-TYPE 1347 SYNTAX RowStatus 1348 MAX-ACCESS read-create 1349 STATUS current 1350 DESCRIPTION 1351 "This variable is used to create, modify, and/or 1352 delete a row in this table. When a row in this 1353 table has a row in the active(1) state, no objects in this row 1354 can be modified except the gmplsLabelRowStatus and 1355 gmplsLabelStorageType." 1356 ::= { gmplsLabelEntry 17 } 1358 gmplsLabelStorageType OBJECT-TYPE 1359 SYNTAX StorageType 1360 MAX-ACCESS read-create 1361 STATUS current 1362 DESCRIPTION 1363 "This variable indicates the storage type for this object. 1364 The agent MUST ensure that this object's value remains 1365 consistent with the storage type of any rows in other 1366 tables that contain pointers to this row. In particular, 1367 the storage type of this row must be at least as permanent 1368 as that of any row that point to it. 1369 Conceptual rows having the value 'permanent' need not 1370 allow write-access to any columnar objects in the row." 1371 REFERENCE 1372 "See RFC2579." 1373 DEFVAL { volatile } 1374 ::= { gmplsLabelEntry 18 } 1376 -- End of GMPLS Label Table 1378 -- Module compliance. 1380 gmplsLabelGroups 1381 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1383 gmplsLabelCompliances 1384 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1386 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1387 STATUS current 1388 DESCRIPTION 1389 "Compliance statement for agents that support 1390 the GMPLS Label MIB module." 1392 MODULE -- this module 1394 -- The mandatory groups have to be implemented by LSRs claiming 1395 -- support for this MIB module. This MIB module is, however, not 1396 -- mandatory for a working implementation of a GMPLS LSR with full 1397 -- MIB support if the GMPLS labels in use can be represented within 1398 -- a 32 bit quantity. 1400 MANDATORY-GROUPS { 1401 gmplsLabelTableGroup 1402 } 1403 -- Units of conformance. 1405 GROUP gmplsLabelTableGroup 1406 DESCRIPTION 1407 "This group is mandatory for devices which support 1408 the gmplsLabelTable." 1410 GROUP gmplsLabelPacketGroup 1411 DESCRIPTION 1412 "This group extends gmplsLabelTableGroup for 1413 implementations that support packet labels." 1415 GROUP gmplsLabelPortWavelengthGroup 1416 DESCRIPTION 1417 "This group extends gmplsLabelTableGroup for 1418 implementations that support port and wavelength 1419 labels." 1421 GROUP gmplsLabelFreeformGroup 1422 DESCRIPTION 1423 "This group extends gmplsLabelTableGroup for 1424 implementations that support freeform labels." 1426 GROUP gmplsLabelSonetSdhGroup 1427 DESCRIPTION 1428 "This group extends gmplsLabelTableGroup for 1429 implementations that support SONET or SDH labels." 1431 GROUP gmplsLabelWavebandGroup 1432 DESCRIPTION 1433 "This group extends gmplsLabelTableGroup for 1434 implementations that support Waveband labels." 1436 -- gmplsLabelTable 1438 OBJECT gmplsLabelType 1439 MIN-ACCESS read-only 1440 DESCRIPTION 1441 "Write access is not required." 1443 OBJECT gmplsLabelMplsLabel 1444 MIN-ACCESS read-only 1445 DESCRIPTION 1446 "Write access is not required." 1448 OBJECT gmplsLabelPortWavelength 1449 MIN-ACCESS read-only 1450 DESCRIPTION 1451 "Write access is not required." 1453 OBJECT gmplsLabelFreeform 1454 MIN-ACCESS read-only 1455 DESCRIPTION 1456 "Write access is not required." 1458 OBJECT gmplsLabelSonetSdhSignalIndex 1459 MIN-ACCESS read-only 1460 DESCRIPTION 1461 "Write access is not required." 1463 OBJECT gmplsLabelSdhVc 1464 MIN-ACCESS read-only 1465 DESCRIPTION 1466 "Write access is not required." 1468 OBJECT gmplsLabelSdhVcBranch 1469 MIN-ACCESS read-only 1470 DESCRIPTION 1471 "Write access is not required." 1473 OBJECT gmplsLabelSonetSdhBranch 1474 MIN-ACCESS read-only 1475 DESCRIPTION 1476 "Write access is not required." 1478 OBJECT gmplsLabelSonetSdhGroupBranch 1479 MIN-ACCESS read-only 1480 DESCRIPTION 1481 "Write access is not required." 1483 OBJECT gmplsLabelWavebandId 1484 MIN-ACCESS read-only 1485 DESCRIPTION 1486 "Write access is not required." 1488 OBJECT gmplsLabelWavebandStart 1489 MIN-ACCESS read-only 1490 DESCRIPTION 1491 "Write access is not required." 1493 OBJECT gmplsLabelWavebandEnd 1494 MIN-ACCESS read-only 1495 DESCRIPTION 1496 "Write access is not required." 1498 OBJECT gmplsLabelRowStatus 1499 SYNTAX RowStatus { 1500 active(1), 1501 notInService(2) 1502 } 1503 WRITE-SYNTAX RowStatus { 1504 active(1), 1505 notInService(2), 1506 createAndGo(4), 1507 destroy(6) 1508 } 1509 DESCRIPTION 1510 "Support for notInService, createAndWait and notReady 1511 is not required." 1513 OBJECT gmplsLabelStorageType 1514 MIN-ACCESS read-only 1515 DESCRIPTION 1516 "Write access is not required." 1518 ::= { gmplsLabelCompliances 1 } 1520 -- Units of conformance. 1522 gmplsLabelTableGroup OBJECT-GROUP 1523 OBJECTS { 1524 gmplsLabelIndexNext, 1525 gmplsLabelType, 1526 gmplsLabelRowStatus, 1527 gmplsLabelStorageType 1528 } 1529 STATUS current 1530 DESCRIPTION 1531 "Necessary, but not sufficient, set of objects to 1532 implement label table support. In addition, 1533 depending on the type of labels supported (for 1534 example, wavelength labels), the following other 1535 groups defined below are mandatory: 1536 gmplsLabelPacketGroup and/or 1537 gmplsLabelPortWavelengthGroup and/or 1538 gmplsLabelFreeformGroup and/or 1539 gmplsLabelSonetSdhGroup." 1540 ::= { gmplsLabelGroups 1 } 1542 gmplsLabelPacketGroup OBJECT-GROUP 1543 OBJECTS { 1544 gmplsLabelMplsLabel 1545 } 1546 STATUS current 1547 DESCRIPTION 1548 "Object needed to implement Packet (MPLS) labels." 1549 ::= { gmplsLabelGroups 2 } 1550 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1551 OBJECTS { 1552 gmplsLabelPortWavelength 1553 } 1554 STATUS current 1555 DESCRIPTION 1556 "Object needed to implement Port and Wavelength 1557 labels." 1558 ::= { gmplsLabelGroups 3 } 1560 gmplsLabelFreeformGroup OBJECT-GROUP 1561 OBJECTS { 1562 gmplsLabelFreeform 1563 } 1564 STATUS current 1565 DESCRIPTION 1566 "Object needed to implement Freeform labels." 1567 ::= { gmplsLabelGroups 4 } 1569 gmplsLabelSonetSdhGroup OBJECT-GROUP 1570 OBJECTS { 1571 gmplsLabelSonetSdhSignalIndex, 1572 gmplsLabelSdhVc, 1573 gmplsLabelSdhVcBranch, 1574 gmplsLabelSonetSdhBranch, 1575 gmplsLabelSonetSdhGroupBranch 1576 } 1577 STATUS current 1578 DESCRIPTION 1579 "Object needed to implement SONET and SDH labels." 1580 ::= { gmplsLabelGroups 5 } 1582 gmplsLabelWavebandGroup OBJECT-GROUP 1583 OBJECTS { 1584 gmplsLabelWavebandId, 1585 gmplsLabelWavebandStart, 1586 gmplsLabelWavebandEnd 1587 } 1588 STATUS current 1589 DESCRIPTION 1590 "Object needed to implement Waveband labels." 1591 ::= { gmplsLabelGroups 6 } 1593 END 1595 9. Security Considerations 1597 It is clear that the MIB modules described in this document in 1598 association with the MPLS-LSR-STD-MIB are potentially useful for 1599 monitoring of GMPLS LSRs. These MIB modules can also be used for 1600 configuration of certain objects, and anything that can be configured 1601 can be incorrectly configured, with potentially disastrous results. 1603 There are a number of management objects defined in these MIB modules 1604 with a MAX-ACCESS clause of read-write and/or read-create. Such 1605 objects may be considered sensitive or vulnerable in some network 1606 environments. The support for SET operations in a non-secure 1607 environment without proper protection can have a negative effect on 1608 network operations. These are the tables and objects and their 1609 sensitivity/vulnerability: 1611 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1612 and gmplsLabelTable collectively contain objects to provision 1613 GMPLS interfaces, LSPs and their associated parameters on a Label 1614 Switching Router (LSR). Unauthorized write access to objects in 1615 these tables, could result in disruption of traffic on the 1616 network. This is especially true if an LSP has already been 1617 established. The use of stronger mechanisms such as SNMPv3 1618 security should be considered where possible. Specifically, SNMPv3 1619 VACM and USM MUST be used with any SNMPv3 agent which implements 1620 these MIB modules. 1622 Some of the readable objects in these MIB modules "i.e., objects with 1623 a MAX-ACCESS other than not-accessible" may be considered sensitive 1624 or vulnerable in some network environments. It is thus important to 1625 control even GET and/or NOTIFY access to these objects and possibly 1626 to even encrypt the values of these objects when sending them over 1627 the network via SNMP. These are the tables and objects and their 1628 sensitivity/vulnerability: 1630 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1631 and gmplsLabelTable collectively show the LSP network topology and 1632 its capabilities. If an Administrator does not want to reveal this 1633 information, then these tables should be considered 1634 sensitive/vulnerable. 1636 SNMP versions prior to SNMPv3 did not include adequate security. Even 1637 if the network itself is secure "for example by using IPSec", even 1638 then, there is no control as to who on the secure network is allowed 1639 to access and GET/SET "read/change/create/delete" the objects in 1640 these MIB modules. It is RECOMMENDED that implementers consider the 1641 security features as provided by the SNMPv3 framework "see [RFC3410], 1642 section 8", including full support for the SNMPv3 cryptographic 1643 mechanisms "for authentication and privacy". 1645 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1646 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1647 enable cryptographic security. It is then a customer/operator 1648 responsibility to ensure that the SNMP entity giving access to an 1649 instance of this MIB module, is properly configured to give access to 1650 the objects only to those principals "users" that have legitimate 1651 rights to indeed GET or SET "change/create/delete" them. 1653 10. Acknowledgments 1655 This draft is the work of the five authors listed in the Authors' 1656 Addresses section. 1658 This document extends [RFC3813]. The authors would like to express 1659 their gratitude to all those who worked on that earlier MIB document. 1661 The authors would like to express their thanks to Dan Joyle for his 1662 careful review and comments on early versions of the Label Table. 1663 Special thanks to Joan Cucchiara and Len Nieman for their help with 1664 compilation issues. 1666 11. IANA Considerations 1668 MPLS related standards track MIB modules are rooted under the 1669 mplsStdMIB subtree. 1671 One of the MIB modules contained in this document extends tables 1672 contained in MPLS MIB modules. 1674 As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the 1675 two MIB modules contained in this document should be placed in the 1676 mplsStdMIB subtree as well. 1678 New assignments can only be made via a Standards Action as specified 1679 in [RFC2434]. 1681 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 1683 The IANA is requested to assign { mplsStdMIB xx } to the 1684 GMPLS-LSR-STD-MIB module specified in this document. 1686 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 1688 The IANA is requested to assign { mplsStdMIB xx } to the 1689 GMPLS-LABEL-STD-MIB module specified in this document. 1691 12. References 1693 12.1. Normative References 1695 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1696 Requirement Levels", BCP 14, RFC 2119, March 1997. 1698 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1699 Case, J., Rose, M., and S. Waldbusser, "Structure 1700 of Management Information Version 2 (SMIv2)", STD 1701 58, RFC 2578, April 1999. 1703 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1704 Case, J., Rose, M., and S. Waldbusser, "Textual 1705 Conventions for SMIv2", STD 58, RFC 2579, April 1706 1999. 1708 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1709 Case, J., Rose, M., and S. Waldbusser, "Conformance 1710 Statements for SMIv2", STD 58, RFC 2580, April 1711 1999. 1713 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces 1714 Group MIB", RFC 2863, June 2000. 1716 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1717 Information Base for the Differentiated Services 1718 Architecture", RFC 3289, May 2002. 1720 [RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL) 1721 Processing in Multi-Protocol Label Switching 1722 (MPLS) Networks", RFC 3443, January 2003. 1724 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1725 Conventions and for Multiprotocol Label Switching 1726 (MPLS) Management", RFC 3811, June 2004. 1728 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1729 "Multiprotocol Label Switching (MPLS) Label 1730 Switching (LSR) Router Management Information Base 1731 (MIB)", RFC 3813, June 2004. 1733 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 1734 Label Switching (GMPLS) Architecture", 1735 draft-many-gmpls-architecture-07.txt, May 2003, 1736 work in progress. 1738 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 1739 "Generalized Multi-Protocol Label Switching 1740 Extensions for SONET and SDH Control", 1741 draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1742 February 2003, work in progress. 1744 [GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of 1745 Textual Conventions for Multiprotocol Label 1746 Switching (MPLS) Management", 1747 draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004, 1748 work in progress. 1750 [GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized 1751 Multiprotocol Label Switching (GMPLS) Traffic 1752 Engineering Management Information Base", 1753 draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004, 1754 work in progress. 1756 12.2. Informational References 1758 [RFC2026] S. Bradner, "The Internet Standards Process -- 1759 Revision 3", RFC 2026, October 1996. 1761 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 1762 Writing an IANA Considerations Section in RFCs", 1763 BCP: 26, RFC 2434, October 1998. 1765 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1766 "Multiprotocol Label Switching Architecture", RFC 1767 3031, January 2001. 1769 [RFC3032] Rosen, E. et al, "MPLS Label Stack Encoding", 1770 RFC 3032, January 2001. 1772 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 1773 Srinivasan, V., and G. Swallow, "RSVP-TE: 1774 Extensions to RSVP for LSP Tunnels", RFC 3209, 1775 December 2001. 1777 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 1778 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 1779 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 1780 T., Feldman, N., Fredette, A., Girish, M., Gray, 1781 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 1782 A., and P. Vaananen, "Constraint-Based LSP Setup 1783 using LDP", RFC 3212, December 2001." 1785 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1786 "Introduction and Applicability Statements for 1787 Internet-Standard Management Framework", RFC 3410, 1788 December 2002. 1790 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1791 Architecture for Describing Simple Network 1792 Management Protocol (SNMP) Management Frameworks", 1793 RFC 3411, December 2002. 1795 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 1796 Applications", RFC 3413, December 2002. 1798 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 1799 Label Switching (GMPLS) Signaling Functional 1800 Description", RFC 3471, January 2003. 1802 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 1803 "Generalized MPLS Signaling - CR-LDP Extensions", 1804 RFC 3472, January 2003. 1806 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 1807 RSVP-TE Extensions", RFC 3473 January 2003. 1809 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1810 "Multiprotocol Label Switching (MPLS) Traffic 1811 Engineering (TE) Management Information Base 1812 (MIB)", RFC 3812, June 2004. 1814 13. Authors' Addresses 1816 Thomas D. Nadeau 1817 Cisco Systems, Inc. 1818 300 Apollo Drive 1819 Chelmsford, MA 01824 1820 Phone: +1-978-244-3051 1821 Email: tnadeau@cisco.com 1823 Cheenu Srinivasan 1824 Bloomberg L.P. 1825 499 Park Ave., 1826 New York, NY 10022 1827 Phone: +1-212-893-3682 1828 Email: cheenu@bloomberg.net 1830 Adrian Farrel 1831 Old Dog Consulting 1832 Phone: +44-(0)-1978-860944 1833 Email: adrian@olddog.co.uk 1835 Tim Hall 1836 Data Connection Ltd. 1837 100 Church Street 1838 Enfield, Middlesex, EN2 6BQ, UK 1839 Phone: +44 20 8366 1177 1840 Email: tim.hall@dataconnection.com 1842 Ed Harrison 1843 Data Connection Ltd. 1844 100 Church Street 1845 Enfield, Middlesex, EN2 6BQ, UK 1846 Phone: +44 20 8366 1177 1847 Email: ed.harrison@dataconnection.com 1849 14. Intellectual Property Considerations 1851 The IETF takes no position regarding the validity or scope of any 1852 Intellectual Property Rights or other rights that might be claimed to 1853 pertain to the implementation or use of the technology described in 1854 this document or the extent to which any license under such rights 1855 might or might not be available; nor does it represent that it has 1856 made any independent effort to identify any such rights. Information 1857 on the procedures with respect to rights in RFC documents can be 1858 found in BCP 78 and BCP 79. 1860 Copies of IPR disclosures made to the IETF Secretariat and any 1861 assurances of licenses to be made available, or the result of an 1862 attempt made to obtain a general license or permission for the use of 1863 such proprietary rights by implementers or users of this 1864 specification can be obtained from the IETF on-line IPR repository at 1865 http://www.ietf.org/ipr. 1867 The IETF invites any interested party to bring to its attention any 1868 copyrights, patents or patent applications, or other proprietary 1869 rights that may cover technology that may be required to implement 1870 this standard. Please address the information to the IETF at 1871 ietf-ipr@ietf.org. 1873 15. Full Copyright Statement 1875 Copyright (C) The Internet Society (2004). This document is subject 1876 to the rights, licenses and restrictions contained in BCP 78, and 1877 except as set forth therein, the authors retain all their rights. 1879 This document and the information contained herein are provided on an 1880 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1881 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1882 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1883 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1884 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1885 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1887 16. Changes 1889 This section must be removed before the draft progresses to RFC. 1891 16.1. Changes from version 5 to version 6 1893 - ID nits and MIB bolierplate 1895 16.2. Changes from version 4 to version 5 1897 - New IPR and copyright boiler plate. 1898 - Clarify description of gmplsInterfaceSignalingCaps. 1900 16.3. Changes from version 3 to version 4 1901 - Update references. 1902 - Allow configuration of the Hello timer per interface. 1903 - Provide support for monitoring technology-specific resources or 1904 performance through an arbitrary row pointer. 1905 - Retire unnecessary gmplsLabelFreeformLength. 1906 - Update examples. 1908 16.4. Changes from version 2 to version 3 1910 - Work on basic compilation issues. 1911 - Provide a next index object to supply the next available 1912 arbitrary index into the Label Table. 1913 - Update references. 1914 - Update examples.