idnits 2.17.1 draft-ietf-ccamp-gmpls-lsr-mib-07.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 1932. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1905. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1912. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1918. ** 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. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 40 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 2005) is 7008 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 1769, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 1786, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 1806, but no explicit reference was found in the text == Unused Reference: 'RFC3032' is defined on line 1817, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1820, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 1825, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 1838, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 1843, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 1846, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 1850, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 1854, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-ccamp-gmpls-tc-mib-06 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-08 -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 6 errors (**), 0 flaws (~~), 17 warnings (==), 8 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: August 2005 Adrian Farrel, Ed. 5 Old Dog Consulting 7 February 2005 9 Generalized Multiprotocol Label Switching (GMPLS) 10 Label Switching Router (LSR) Management Information Base 12 draft-ietf-ccamp-gmpls-lsr-mib-07.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 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects to configure and/or 42 monitor a Generalized Multiprotocol Label Switching (GMPLS) Label 43 Switching Router (LSR). 45 Table of Contents 46 1. Introduction ..................................... 2 47 1.1. Migration Strategy ....................... ..... 2 48 2. Terminology ...................................... 3 49 3. The SNMP Management Framework .................... 3 50 4. Outline .......................................... 3 51 4.1. Summary of the GMPLS LSR MIB Module ............ 4 52 4.1.1 Summary of the GMPLS LSR MIB Module ........... 4 53 4.1.2 Summary of the GMPLS Label MIB Module ......... 5 54 5. Bidirectional LSPs ............................... 5 55 6. Example of LSP Setup ............................. 5 56 7. GMPLS Label Switching Router MIB Definitions ..... 9 57 8. GMPLS Label MIB Definitions ..................... 19 58 9. Security Considerations ......................... 34 59 10. Acknowledgments ................................ 35 60 11. IANA Considerations ............................ 35 61 11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 36 62 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB .. 36 63 12. References ..................................... 36 64 12.1. Normative References ......................... 36 65 12.2. Informational References ..................... 37 66 13. Authors' Addresses ............................. 38 67 14. Full Copyright Statement ....................... 39 68 15. Intellectual Property Notice ................... 40 70 1. Introduction 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet community. 74 In particular, it describes managed objects for modeling a 75 Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] Label 76 Switching Router (LSR). 78 Comments should be made directly to the CCAMP mailing list at 79 ccamp@ops.ietf.org. 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in BCP 14, RFC 2119, 84 reference [RFC2119]. 86 1.1. Migration Strategy 88 There are two MIB modules in this document. The GMPLS LSR MIB module 89 extends the LSR MIB module defined for use with MPLS [RFC3813]. The 90 only changes made are additions for support of GMPLS or changes that 91 are necessary to support the increased complexity of a GMPLS system. 92 The GMPLS Label MIB module may be referenced using a row pointer from 93 objects within the LSR MIB module. 95 The companion document modeling and managing GMPLS based traffic 96 engineering [GMPLSTEMIB] extends the MPLS TE MIB module [RFC3812] 97 with the same intentions. 99 Textual conventions and OBJECT-IDENTIFIERS are defined in 100 [GMPLSTCMIB] which extends the set of textual conventions originally 101 defined in [RFC3811]. 103 2. Terminology 105 This document uses terminology from the document describing the MPLS 106 architecture [RFC3031] and the GMPLS architecture [RFC3945]. 108 A label switched path (LSP) is modeled as a connection consisting of 109 one or more incoming segments (in-segments) and/or one or more 110 outgoing segments (out-segments) at an LSR. The association or 111 interconnection of the in-segments and out-segments is accomplished 112 by using a cross-connect. We use the terminology "connection" and 113 "LSP" interchangeably where the meaning is clear from the context. 115 in-segment This is analogous to a GMPLS label on an interface. 116 out-segment This is analogous to a GMPLS label on an interface. 117 cross-connect This describes the conceptual connection between a 118 set of in-segments and out-segments. Note that either 119 set may be empty; for example, a cross-connect may 120 connect only out-segments together with no in-segments 121 in the case where an LSP originates on an LSR. 123 3. The SNMP Management Framework 125 For a detailed overview of the documents that describe the current 126 Internet-Standard Management Framework, please refer to section 7 of 127 RFC 3410 [RFC3410]. 129 Managed objects are accessed via a virtual information store, termed 130 the Management Information Base or MIB. MIB objects are generally 131 accessed through the Simple Network Management Protocol (SNMP). 132 Objects in the MIB are defined using the mechanisms defined in the 133 Structure of Management Information (SMI). This memo specifies a MIB 134 module that is compliant to the SMIv2, which is described in STD 58, 135 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 136 [RFC2580]. 138 4. Outline 140 Configuring statically provisioned GMPLS LSPs through an LSR involves 141 the following steps: 143 - Configuring an interface using the MPLS LSR MIB module. 145 - Enabling GMPLS on GMPLS capable interfaces using this MIB module. 147 - Configuring in and out-segments using the MPLS LSR MIB module. 149 - Configuring GMPLS extensions to the in-segments and out-segments 150 using this MIB module. 152 - Setting up the cross-connect table in the MPLS LSR MIB module to 153 associate segments and/or to indicate connection origination and 154 termination. 156 - Optionally setting up labels in the label table in this MIB module 157 if the textual convention MplsLabel is not capable of holding the 158 required label (for example, if the label requires more than 32 159 bits to encode it), or if the operator wishes to disambiguate 160 GMPLS label types. 162 - Optionally specifying label stack actions in the MPLS LSR MIB 163 module. 165 - Optionally specifying segment traffic parameters in the MPLS LSR 166 MIB module. 168 4.1 MIB Modules 170 There are two MIB modules defined in this document. 172 The GMPLS LSR MIB module contains tables that extend tables defined 173 in the MPLS LSR MIB module. This MIB module is used in conjunction 174 with the MPLS LSR MIB module in systems that support GMPLS. 176 The GMPLS Label MIB module contains objects for managing GMPLS labels 177 when they cannot be represented using the textual conventions of the 178 MPLS TC MIB module, or when more detailed access to the sub-fields of 179 the labels is required. 181 4.1.1 Summary of the GMPLS LSR MIB Module 183 The MIB tables in this MIB module are as follows. 185 - The interface configuration table (gmplsInterfaceTable), which 186 extends mplsInterfaceTable to enable the GMPLS protocol on MPLS- 187 capable interfaces. 189 - The in-segment (gmplsInSegmentTable) and out-segment 190 (gmplsOutSegmentTable) tables extend mplsInSegmentTable and 191 mplsOutSegmentTable to configuring GMPLS-specific parameters for 192 LSP segments at an LSR. 194 These tables are described in the subsequent sections. 196 4.1.2 Summary of the GMPLS Label MIB Module 198 There is one MIB table in this MIB module as follows. 200 - The gmplsLabelTable allows Generalized 201 Labels to be defined and managed in a central location. 202 Generalized Labels can be of variable length and have distinct 203 bit-by-bit interpretations according to the use that is made of 204 them. 206 These tables are described in the subsequent sections. 208 5. Bidirectional LSPs 210 This MIB module supports bidirectional LSPs as required for GMPLS. 211 A single value of mplsXCIndex is shared by all of the segments for 212 the entire bidirectional LSP. This facilitates a simple reference 213 from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing more obvious. 215 It is, however, important that the direction of segments is 216 understood to avoid connecting all in-segments to all out-segments. 217 This is achieved by an object in each segment that indicates the 218 direction of the segment with respect to data flow. 220 A segment that is marked as 'forward' carries data from the 'head' of 221 the LSP to the 'tail'. A segment marked as 'reverse' carries data in 222 the reverse direction. 224 Where an LSP is signaled using a conventional signaling protocol, the 225 'head' of the LSP is the source of the signaling (also known as the 226 ingress) and the 'tail' is the destination (also known as the 227 egress). For manually configured LSPs an arbitrary decision must be 228 made about which segments are 'forward' and which 'reverse'. For 229 consistency this decision should be made across all LSRs that 230 participate in the LSP by assigning 'head' and 'tail' ends to the 231 LSP. 233 6. Example of LSP Setup 235 In this section we provide a brief example of using the MIB objects 236 described in sections 7 and 8 to set up an LSP. While this example is 237 not meant to illustrate every nuance of the MIB, it is intended as an 238 aid to understanding some of the key concepts. It is meant to be read 239 after going through the MIB itself. A prerequisite is an 240 understanding of [RFC3813]. 242 Suppose that one would like to manually create a best-effort, 243 bi-directional LSP. Assume that, in the forward direction, the LSP 244 enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR 245 via MPLS interface B with ifIndex 13. For the reverse direction, we 246 assume the LSP enters via interface B and leaves via interface A 247 (i.e. the forward and reverse directions use the same bi-directional 248 interfaces). Let us also assume that we do not wish to have a label 249 stack beneath the top label on the outgoing labeled packets. The 250 following example illustrates which rows and corresponding objects 251 might be created to accomplish this. 253 We must first create rows in the gmplsLabelTable corresponding to the 254 labels required for each of the forward and reverse direction in- and 255 out-segments. For the purpose of this example the forward and 256 reverse labels on each interface will be the same, hence we need to 257 create just two rows in the gmplsLabelTable - one for each interface. 259 In gmplsLabelTable: 260 { 261 gmplsLabelInterface = 12, 262 gmplsLabelIndex = 1, 263 gmplsLabelSubindex = 0, 264 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 265 gmplsLabelFreeform = 0x123456789ABCDEF0 266 gmplsLabelRowStatus = createAndGo(4) 267 } 269 In gmplsLabelTable: 270 { 271 gmplsLabelInterface = 13, 272 gmplsLabelIndex = 1, 273 gmplsLabelSubindex = 0, 274 gmplsLabelType = gmplsFreeformGeneralizedLabel(3), 275 gmplsLabelFreeform = 0xFEDCBA9876543210 276 gmplsLabelRowStatus = createAndGo(4) 277 } 279 We must next create the appropriate in-segment and out-segment 280 entries. These are done in [RFC3813] using the mplsInSegmentTable and 281 mplsOutSegmentTable. Note that we use a row pointer to the two rows 282 in the gmplsLableTable rather than specifying the labels explicitly 283 in the in- and out-segment tables. Also note that the row status for 284 each row is set to createAndWait(5) to allow corresponding entries in 285 the gmplsInSegmentTable and gmplsOutSegmentTable to be created. 287 For the forward direction. 289 In mplsInSegmentTable: 290 { 291 mplsInSegmentIndex = 0x00000015 292 mplsInSegmentLabel = 0, -- incoming label in label table 293 mplsInSegmentNPop = 1, 294 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 } 344 These table entries are extended by entries in gmplsInSegmentTable 345 and gmplsOutSegmentTable. Note that the nature of the 'extends' 346 relationship is that the entry in gmplsInSegmentTable has the same 347 index values as the entry in mplsInSegmentTable. Similarly, the entry 348 in gmplsOutSegmentTable has the same index values as the entry in 349 mplsOutSegmentTable. 351 First for the forward direction: 353 In gmplsInSegmentTable(0x00000015) 354 { 355 gmplsInSegmentDirection = forward (1) 356 } 358 In gmplsOutSegmentTable(0x00000012) 359 { 360 gmplsOutSegmentDirection = forward (1) 361 } 363 Next for the reverse direction: 365 In gmplsInSegmentTable(0x00000016) 366 { 367 gmplsInSegmentDirection = reverse (2) 368 } 370 In gmplsOutSegmentTable(0x00000013) 371 { 372 gmplsOutSegmentDirection = reverse (2) 373 } 375 Next, two cross-connect entries are created in the mplsXCTable of the 376 MPLS LSR MIB, thereby associating the newly created segments 377 together. 379 In mplsXCTable: 380 { 381 mplsXCIndex = 0x01, 382 mplsXCInSegmentIndex = 0x00000015, 383 mplsXCOutSegmentIndex = 0x00000012, 384 mplsXCLspId = 0x0102 -- unique ID 385 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 386 mplsXCRowStatus = createAndGo(4) 387 } 389 In mplsXCTable: 390 { 391 mplsXCIndex = 0x02, 392 mplsXCInSegmentIndex = 0x00000016, 393 mplsXCOutSegmentIndex = 0x00000013, 394 mplsXCLspId = 0x0102 -- unique ID 395 mplsXCLabelStackIndex = 0x00, -- only a single outgoing label 396 mplsXCRowStatus = createAndGo(4) 397 } 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 "200502140001Z" -- 14 February 2005 00:00:01 GMT 440 ORGANIZATION 441 "Common Control And Measurement Plane (CCAMP) Working Group" 443 CONTACT-INFO 444 " Thomas D. Nadeau 445 Cisco Systems, Inc. 446 Email: tnadeau@cisco.com 448 Adrian Farrel 449 Old Dog Consulting 450 Email: adrian@olddog.co.uk 451 Comments about this document should be emailed direct to the 452 CCAMP working group mailing list at ccamp@ops.ietf.org" 454 DESCRIPTION 455 "Copyright (C) The Internet Society (2005). The 456 initial version of this MIB module was published 457 in RFC xxxx. For full legal notices see the RFC 458 itself or see: http://www.ietf.org/copyrights/ianamib.html 460 This MIB module contains managed object definitions 461 for the Generalized Multiprotocol (GMPLS) Label Switching 462 Router as defined in: 463 Generalized Multi-Protocol Label Switching (GMPLS) 464 Architecture,Mannie et al., RFC 3945, October 2004." 466 -- Revision history. 468 REVISION 469 "200502140001Z" -- 14 February 2005 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 } 549 gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE 550 SYNTAX Unsigned32 551 UNITS "milliseconds" 552 MAX-ACCESS read-create 553 STATUS current 554 DESCRIPTION 555 "Period, in milliseconds, between sending RSVP Hello 556 messages on this interface. A value of 0 indicates 557 that no Hello messages should be sent on this interface." 558 REFERENCE 559 "Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 560 (Editor), RFC 3473, January 2003." 561 DEFVAL { 3000 } 562 ::= { gmplsInterfaceEntry 2 } 564 -- End of gmplsInterfaceTable 566 -- In-segment table. 568 gmplsInSegmentTable OBJECT-TYPE 569 SYNTAX SEQUENCE OF GmplsInSegmentEntry 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION 573 "This table extends the mplsInSegmentTable to provide GMPLS- 574 specific information about incoming segments to an LSR." 575 ::= { gmplsLsrObjects 2 } 577 gmplsInSegmentEntry OBJECT-TYPE 578 SYNTAX GmplsInSegmentEntry 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "An entry in this table extends the representation of 583 an incoming segment represented by an entry in 584 mplsInSegmentTable. An entry can be created by a 585 network administrator or an SNMP agent, or a GMPLS 586 signaling protocol. 588 Note that the storage type for this entry SHOULD be 589 inherited from the corresponding entry in the 590 mplsInSegmentTable given by the value of the 591 mplsInSegmentStorageType object." 593 INDEX { mplsInSegmentIndex } 594 ::= { gmplsInSegmentTable 1 } 596 GmplsInSegmentEntry ::= SEQUENCE { 597 gmplsInSegmentDirection GmplsSegmentDirection, 598 gmplsInSegmentExtraParamsPtr RowPointer 599 } 601 gmplsInSegmentDirection OBJECT-TYPE 602 SYNTAX GmplsSegmentDirection 603 MAX-ACCESS read-create 604 STATUS current 605 DESCRIPTION 606 "This object indicates the direction of data flow on 607 this segment. This object cannot be modified if 608 mplsInSegmentRowStatus for the associated entry in 609 the mplsInSegmentTable is active(1)." 610 DEFVAL { forward } 611 ::= { gmplsInSegmentEntry 1 } 613 gmplsInSegmentExtraParamsPtr OBJECT-TYPE 614 SYNTAX RowPointer 615 MAX-ACCESS read-create 616 STATUS current 617 DESCRIPTION 618 "Some Tunnels will run over transports that can 619 usefully support technology-specific additional parameters 620 (for example, SONET resource usage). Such can be supplied from 621 an external table and referenced from here. 622 A value of zeroDotzero in this attribute indicates that there 623 is no such additional information." 624 DEFVAL { zeroDotZero } 625 ::= { gmplsInSegmentEntry 2 } 627 -- End of gmplsInSegmentTable 629 -- Out-segment table. 631 gmplsOutSegmentTable OBJECT-TYPE 632 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 633 MAX-ACCESS not-accessible 634 STATUS current 635 DESCRIPTION 636 "This table extends the mplsOutSegmentTable to 637 provide GMPLS-specific information about outgoing 638 segments from an LSR." 639 ::= { gmplsLsrObjects 3 } 640 gmplsOutSegmentEntry OBJECT-TYPE 641 SYNTAX GmplsOutSegmentEntry 642 MAX-ACCESS not-accessible 643 STATUS current 644 DESCRIPTION 645 "An entry in this table extends the representation of 646 an outgoing segment represented by an entry in 647 mplsOutSegmentTable. An entry can be created by a 648 network administrator or an SNMP agent, or a GMPLS 649 signaling protocol. 651 Note that the storage type for this entry SHOULD be 652 inherited from the corresponding entry in the 653 mplsOutSegmentTable given by the value of the 654 mplsOutSegmentStorageType object." 655 INDEX { mplsOutSegmentIndex } 656 ::= { gmplsOutSegmentTable 1 } 658 GmplsOutSegmentEntry ::= SEQUENCE { 659 gmplsOutSegmentDirection GmplsSegmentDirection, 660 gmplsOutSegmentTTLDecrement Unsigned32, 661 gmplsOutSegmentExtraParamsPtr RowPointer 662 } 664 gmplsOutSegmentDirection OBJECT-TYPE 665 SYNTAX GmplsSegmentDirection 666 MAX-ACCESS read-create 667 STATUS current 668 DESCRIPTION 669 "This object indicates the direction of data flow on 670 this segment. This object cannot be modified if 671 mplsOutSegmentRowStatus for the associated entry in 672 the mplsOutSegmentTable is active(1)." 673 DEFVAL { forward } 674 ::= { gmplsOutSegmentEntry 1 } 676 gmplsOutSegmentTTLDecrement OBJECT-TYPE 677 SYNTAX Unsigned32 (0..255) 678 MAX-ACCESS read-create 679 STATUS current 680 DESCRIPTION 681 "This object indicates the amount by which to 682 decrement the TTL of any payload packets forwarded 683 on this segment if per-hop decrementing is being 684 done. 685 A value of zero indicates that no decrement should 686 be made or that per-hop decrementing is not in 687 force. 688 See the gmplsTunnelTTLDecrement object in the 689 gmplsTunnelTable of [GMPLSTEMIB] for a value by 690 which to decrement the TTL for the whole of a 691 tunnel. 693 This object cannot be modified if 694 mplsOutSegmentRowStatus for the associated entry in 695 the mplsOutSegmentTable is active(1)." 696 REFERENCE 697 "Time To Live (TTL) Processing in Multi-Protocol Label Switching 698 (MPLS) Networks, Agarwal, P., Akyol, B., RFC 3443, January 2003" 699 DEFVAL { 0 } 700 ::= { gmplsOutSegmentEntry 2 } 702 gmplsOutSegmentExtraParamsPtr OBJECT-TYPE 703 SYNTAX RowPointer 704 MAX-ACCESS read-create 705 STATUS current 706 DESCRIPTION 707 "Some Tunnels will run over transports that can 708 usefully support technology-specific additional parameters 709 (for example, SONET resource usage). Such can be supplied from 710 an external table and referenced from here. 711 A value of zeroDotzero in this attribute indicates that there 712 is no such additional information." 713 DEFVAL { zeroDotZero } 714 ::= { gmplsOutSegmentEntry 3 } 716 -- End of gmplsOutSegmentTable 718 -- Module compliance. 720 gmplsLsrGroups 721 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 723 gmplsLsrCompliances 724 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 726 -- Compliance requirement for fully compliant implementations. 728 gmplsLsrModuleFullCompliance MODULE-COMPLIANCE 729 STATUS current 730 DESCRIPTION 731 "Compliance statement for agents that provide full 732 support for GMPLS-LSR-STD-MIB." 734 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 736 MANDATORY-GROUPS { 737 ifGeneralInformationGroup, 738 ifCounterDiscontinuityGroup 739 } 740 MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB 742 MANDATORY-GROUPS { 743 mplsInterfaceGroup, 744 mplsInSegmentGroup, 745 mplsOutSegmentGroup, 746 mplsXCGroup, 747 mplsPerfGroup, 748 mplsLsrNotificationGroup 749 } 751 MODULE -- this module 753 MANDATORY-GROUPS { 754 gmplsInterfaceGroup, 755 gmplsInSegmentGroup, 756 gmplsOutSegmentGroup 757 } 759 -- gmplsInSegmentTable 761 OBJECT gmplsInSegmentDirection 762 SYNTAX GmplsSegmentDirection 763 MIN-ACCESS read-write 764 DESCRIPTION 765 "Only forward(1) needs to be supported by 766 implementations that only support unidirectional 767 LSPs." 769 -- gmplsOutSegmentTable 771 OBJECT gmplsOutSegmentDirection 772 SYNTAX GmplsSegmentDirection 773 MIN-ACCESS read-write 774 DESCRIPTION 775 "Only forward(1) needs to be supported by 776 implementations that only support unidirectional 777 LSPs." 779 OBJECT gmplsOutSegmentTTLDecrement 780 SYNTAX Unsigned32 (0..255) 781 MIN-ACCESS read-only 782 DESCRIPTION 783 "Write access is not required." 785 ::= { gmplsLsrCompliances 1 } 786 -- Compliance requirement for implementations that provide read-only 787 -- access. 789 gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE 790 STATUS current 791 DESCRIPTION 792 "Compliance requirement for implementations that only 793 provide read-only support for GMPLS-LSR-STD-MIB. Such 794 devices can then be monitored but cannot be configured 795 using this MIB modules." 797 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 799 MANDATORY-GROUPS { 800 ifGeneralInformationGroup, 801 ifCounterDiscontinuityGroup 802 } 804 MODULE MPLS-LSR-STD-MIB 806 MANDATORY-GROUPS { 807 mplsInterfaceGroup, 808 mplsInSegmentGroup, 809 mplsOutSegmentGroup, 810 mplsXCGroup, 811 mplsPerfGroup 812 } 814 MODULE -- this module 816 MANDATORY-GROUPS { 817 gmplsInterfaceGroup, 818 gmplsInSegmentGroup, 819 gmplsOutSegmentGroup 820 } 822 -- gmplsInterfaceGroup 824 OBJECT gmplsInterfaceSignalingCaps 825 SYNTAX BITS { 826 unknown (0), 827 rsvpGmpls (1), 828 crldpGmpls (2), 829 otherGmpls (3) 830 } 831 MIN-ACCESS read-only 832 DESCRIPTION 833 "Write access is not required." 835 OBJECT gmplsInterfaceRsvpHelloPeriod 836 SYNTAX Unsigned32 837 MIN-ACCESS read-only 838 DESCRIPTION 839 "Write access is not required." 841 -- gmplsInSegmentTable 843 OBJECT gmplsInSegmentDirection 844 SYNTAX GmplsSegmentDirection 845 MIN-ACCESS read-only 846 DESCRIPTION 847 "Write access is not required. Only forward(1) needs 848 to be supported by implementations that only support 849 unidirectional LSPs." 851 OBJECT gmplsInSegmentExtraParamsPtr 852 SYNTAX RowPointer 853 MIN-ACCESS read-only 854 DESCRIPTION 855 "Write access is not required." 857 -- gmplsOutSegmentTable 859 OBJECT gmplsOutSegmentDirection 860 SYNTAX GmplsSegmentDirection 861 MIN-ACCESS read-only 862 DESCRIPTION 863 "Write access is not required. Only forward(1) needs 864 to be supported by implementations that only support 865 unidirectional LSPs." 867 OBJECT gmplsOutSegmentTTLDecrement 868 SYNTAX Unsigned32 (0..255) 869 MIN-ACCESS read-only 870 DESCRIPTION 871 "Write access is not required." 873 OBJECT gmplsOutSegmentExtraParamsPtr 874 SYNTAX RowPointer 875 MIN-ACCESS read-only 876 DESCRIPTION 877 "Write access is not required." 879 ::= { gmplsLsrCompliances 2 } 880 -- Units of conformance. 882 gmplsInterfaceGroup OBJECT-GROUP 883 OBJECTS { 884 gmplsInterfaceSignalingCaps, 885 gmplsInterfaceRsvpHelloPeriod 886 } 888 STATUS current 889 DESCRIPTION 890 "Collection of objects needed for GMPLS interface 891 configuration and performance information." 892 ::= { gmplsLsrGroups 1 } 894 gmplsInSegmentGroup OBJECT-GROUP 895 OBJECTS { 896 gmplsInSegmentDirection, 897 gmplsInSegmentExtraParamsPtr 898 } 899 STATUS current 901 DESCRIPTION 902 "Collection of objects needed to implement a GMPLS 903 in-segment." 904 ::= { gmplsLsrGroups 2 } 906 gmplsOutSegmentGroup OBJECT-GROUP 907 OBJECTS { 908 gmplsOutSegmentDirection, 909 gmplsOutSegmentTTLDecrement, 910 gmplsOutSegmentExtraParamsPtr 911 } 912 STATUS current 913 DESCRIPTION 914 "Collection of objects needed to implement a GMPLS 915 out-segment." 916 ::= { gmplsLsrGroups 3 } 917 END 919 8. GMPLS Label MIB Definitions 921 GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN 923 IMPORTS 924 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, 925 Integer32 926 FROM SNMPv2-SMI -- [RFC2578] 927 MODULE-COMPLIANCE, OBJECT-GROUP 928 FROM SNMPv2-CONF -- [RFC2580] 930 RowStatus, StorageType 931 FROM SNMPv2-TC -- [RFC2579] 932 InterfaceIndexOrZero 933 FROM IF-MIB -- [RFC2863] 934 IndexIntegerNextFree 935 FROM DIFFSERV-MIB -- [RFC3289] 936 MplsLabel 937 FROM MPLS-TC-STD-MIB -- [RFC3811] 938 GmplsGeneralizedLabelTypes, GmplsFreeformLabel 939 FROM GMPLS-TC-STD-MIB -- [GMPLSTCMIB] 940 mplsStdMIB 941 FROM MPLS-TC-STD-MIB -- [RFC3811] 942 ; 944 gmplsLabelStdMIB MODULE-IDENTITY 945 LAST-UPDATED 946 "200502140001Z" -- 14 February 2005 00:00:01 GMT 947 ORGANIZATION 948 "Common Control And Measurement Plane (CCAMP) Working Group" 949 CONTACT-INFO 950 " Thomas D. Nadeau 951 Cisco Systems, Inc. 952 Email: tnadeau@cisco.com 954 Adrian Farrel 955 Old Dog Consulting 956 Email: adrian@olddog.co.uk 958 Comments about this document should be emailed direct to the 959 CCAMP working group mailing list at ccamp@ops.ietf.org" 960 DESCRIPTION 961 "Copyright (C) The Internet Society (2005). The 962 initial version of this MIB module was published 963 in RFC xxxx. For full legal notices see the RFC 964 itself or see: http://www.ietf.org/copyrights/ianamib.html 966 This MIB module contains managed object definitions 967 for labels within GMPLS systems as defined in: 969 Generalized Multi-Protocol Label Switching (GMPLS) 970 Signaling Functional Description, Berger, L. (Editor), 971 RFC 3471, January 2003." 973 -- Revision history. 974 REVISION 975 "200502140001Z" -- 14 February 2005 00:00:01 GMT 976 DESCRIPTION 977 "Initial version issued as part of RFC XXXX." 978 ::= { mplsStdMIB xx } 980 -- Top level components of this MIB module. 982 -- Notifications 983 -- no notifications are currently defined. 984 gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 } 986 -- Tables, Scalars 987 gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } 989 -- Conformance 990 gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } 992 -- GMPLS Label Table. 994 gmplsLabelIndexNext OBJECT-TYPE 995 SYNTAX IndexIntegerNextFree 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "This object contains an unused value for 1000 gmplsLabelIndex, or a zero to indicate 1001 that no unused value exists or is available. 1003 An management application wishing to create 1004 a row in the gmplsLabelTable may read this 1005 object and then attempt to create a row in 1006 the table. If row creation fails (because 1007 another application has already created a row 1008 with the supplied index) the management 1009 application should read this object again 1010 to get a new index value. 1012 When a row is created in the gmplsLabelTable 1013 with the gmplsLabelIndex value held by this 1014 object, an implementation MUST change the value 1015 in this object." 1016 ::= { gmplsLabelObjects 1 } 1018 gmplsLabelTable OBJECT-TYPE 1019 SYNTAX SEQUENCE OF GmplsLabelEntry 1020 MAX-ACCESS not-accessible 1021 STATUS current 1022 DESCRIPTION 1023 "Table of GMPLS Labels. This table allows the representation 1024 of the more complex label forms required for GMPLS which 1025 cannot be held within the textual convention MplsLabel. That 1026 is labels that cannot be encoded within 32 bits. It is, 1027 nevertheless also capable of holding 32 bit labels or 1028 regular MPLS labels if desired. 1030 Each entry in this table represents an individual 1031 GMPLS label value. Labels in the tables in other 1032 MIBs are referred to using row pointer into this 1033 table. The indexing of this table provides for 1034 arbitrary indexing and also for concatenation of 1035 labels." 1036 ::= { gmplsLabelObjects 2 } 1038 gmplsLabelEntry OBJECT-TYPE 1039 SYNTAX GmplsLabelEntry 1040 MAX-ACCESS not-accessible 1041 STATUS current 1042 DESCRIPTION 1043 "An entry in this table represents a single label 1044 value. There are three indexes into the table. 1045 - The interface index may be helpful to distinguish 1046 which labels are in use on which interfaces or to 1047 handle cases where there are a very large number 1048 of labels in use in the system. When label 1049 representation is desired to apply to the whole 1050 system or when it is not important to distinguish 1051 labels by their interfaces, this index MAY be set 1052 to zero. 1053 - The label index provides a way of identifying the 1054 label. 1056 - The label sub-index is only used for concatenated 1057 labels. It identifies each component label. When 1058 non-concatenated labels are used, this index 1059 SHOULD be set to zero. 1061 A storage type object is supplied to control the 1062 storage type for each entry, but implementations 1063 should note that the storage type of conceptual rows 1064 in other tables that include row pointers to an 1065 entry in this table SHOULD dictate the storage type 1066 of the rows in this table where the row in the other 1067 table is more persistent." 1068 INDEX { 1069 gmplsLabelInterface, 1070 gmplsLabelIndex, 1071 gmplsLabelSubindex } 1072 ::= { gmplsLabelTable 1 } 1074 GmplsLabelEntry ::= SEQUENCE { 1075 gmplsLabelInterface InterfaceIndexOrZero, 1076 gmplsLabelIndex Unsigned32, 1077 gmplsLabelSubindex Unsigned32, 1078 gmplsLabelType GmplsGeneralizedLabelTypes, 1079 gmplsLabelMplsLabel MplsLabel, 1080 gmplsLabelPortWavelength Unsigned32, 1081 gmplsLabelFreeform GmplsFreeformLabel, 1082 gmplsLabelSonetSdhSignalIndex Integer32, 1083 gmplsLabelSdhVc Integer32, 1084 gmplsLabelSdhVcBranch Integer32, 1085 gmplsLabelSonetSdhBranch Integer32, 1086 gmplsLabelSonetSdhGroupBranch Integer32, 1087 gmplsLabelWavebandId Unsigned32, 1088 gmplsLabelWavebandStart Unsigned32, 1089 gmplsLabelWavebandEnd Unsigned32, 1090 gmplsLabelRowStatus RowStatus, 1091 gmplsLabelStorageType StorageType 1092 } 1094 gmplsLabelInterface OBJECT-TYPE 1095 SYNTAX InterfaceIndexOrZero 1096 MAX-ACCESS not-accessible 1097 STATUS current 1098 DESCRIPTION 1099 "The interface on which this label is used. If the 1100 label has or could have applicability across the 1101 whole system, this object SHOULD be set to zero." 1102 ::= { gmplsLabelEntry 1 } 1104 gmplsLabelIndex OBJECT-TYPE 1105 SYNTAX Unsigned32 (0..4294967295) 1106 MAX-ACCESS not-accessible 1107 STATUS current 1108 DESCRIPTION 1109 "An arbitrary index into the table to identify a label. 1110 Note that implementations that are representing 32 bit 1111 labels within this table MAY choose to align this index 1112 with the value of the label, but should be aware of the 1113 implications of sparsely populated tables. 1114 A management application may read the gmplsLabelIndexNext 1115 object to find a suitable value for this object." 1116 ::= { gmplsLabelEntry 2 } 1118 gmplsLabelSubindex OBJECT-TYPE 1119 SYNTAX Unsigned32 (0..4294967295) 1120 MAX-ACCESS not-accessible 1121 STATUS current 1122 DESCRIPTION 1123 "In conjunction with gmplsLabelInterface and gmplsLabelIndex, 1124 this object uniquely identifies this row. This sub-index 1125 allows a single GMPLS label to be defined as a concatenation 1126 of labels. This is particularly useful in TDM. 1127 The ordering of sub-labels is strict with the sub-label with 1128 lowest gmplsLabelSubindex appearing first. Note that all 1129 sub-labels of a single GMPLS label must share the same 1130 gmplsLabelInterface and gmplsLabelIndex values. For labels 1131 that are not composed of concatenated sub-labels, this value 1132 SHOULD be set to zero." 1133 ::= { gmplsLabelEntry 3 } 1135 gmplsLabelType OBJECT-TYPE 1136 SYNTAX GmplsGeneralizedLabelTypes 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "Identifies the type of this label. Note that this object 1141 does not determine whether MPLS or GMPLS signaling is in 1142 use: a value of gmplsMplsLabel (1) denotes that a 23 bit 1143 MPLS packet label is present, but does not describe 1144 whether this is signaled using MPLS or GMPLS. 1146 The value of this object helps determine which of 1147 the following objects are valid. 1148 This object cannot be modified if 1149 gmplsLabelRowStatus is active(1)." 1150 REFERENCE 1151 "Generalized Multi-Protocol Label Switching (GMPLS) 1152 Signaling Functional Description, Berger, L. (Editor), 1153 RFC 3471, January 2003." 1154 ::= { gmplsLabelEntry 4 } 1156 gmplsLabelMplsLabel OBJECT-TYPE 1157 SYNTAX MplsLabel 1158 MAX-ACCESS read-create 1159 STATUS current 1160 DESCRIPTION 1161 "The value of an MPLS label (that is a packet label) 1162 if this table is used to store it. This may be used 1163 in MPLS systems even though the label values can be 1164 adequately stored in the MPLS MIB modules. Further, 1165 in mixed MPLS and GMPLS systems it may be 1166 advantageous to store all labels in a single label 1167 table. Lastly, in GMPLS systems where packet labels 1168 are used (that is in systems that use GMPLS 1169 signaling and GMPLS labels for packet switching) it 1170 may be desirable to use this table. 1171 This object is only valid if gmplsLabelType is set 1172 to gmplsMplsLabel (1). 1173 This object cannot be modified if 1174 gmplsLabelRowStatus is active(1)." 1175 REFERENCE 1176 "MPLS Label Stack Encoding, Rosen, E. et al, RFC 3032, 1177 January 2001." 1178 DEFVAL { 0 } 1179 ::= { gmplsLabelEntry 6 } 1180 gmplsLabelPortWavelength OBJECT-TYPE 1181 SYNTAX Unsigned32 1182 MAX-ACCESS read-create 1183 STATUS current 1184 DESCRIPTION 1185 "The value of a Port or Wavelength Label when carried 1186 as a Generalized Label. Only valid if gmplsLabelType 1187 is set to gmplsPortWavelengthLabel(2). 1188 This object cannot be modified if 1189 gmplsLabelRowStatus is active(1)." 1190 REFERENCE 1191 "Generalized Multi-Protocol Label Switching (GMPLS) 1192 Signaling Functional Description, Berger, L. (Editor), 1193 RFC 3471, January 2003." 1194 DEFVAL { 0 } 1195 ::= { gmplsLabelEntry 7 } 1197 gmplsLabelFreeform OBJECT-TYPE 1198 SYNTAX GmplsFreeformLabel 1199 MAX-ACCESS read-create 1200 STATUS current 1201 DESCRIPTION 1202 "The value of a freeform Generalized Label that does 1203 not conform to one of the standardized label 1204 encoding or that an implementation chooses to 1205 represent as an octet string without further 1206 decoding. Only valid if gmplsLabelType is set to 1207 gmplsFreeformGeneralizedLabel(3). This object 1208 cannot be modified if gmplsLabelRowStatus is active(1)." 1209 ::= { gmplsLabelEntry 8 } 1211 gmplsLabelSonetSdhSignalIndex OBJECT-TYPE 1212 SYNTAX Integer32 (0..4095) 1213 MAX-ACCESS read-create 1214 STATUS current 1215 DESCRIPTION 1216 "The Signal Index value (S) of a SONET or SDH 1217 Generalized Label. Zero indicates that this field is 1218 not significant. Only valid if gmplsLabelType is set 1219 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1220 This object cannot be modified if 1221 gmplsLabelRowStatus is active(1)." 1222 REFERENCE 1223 "Generalized Multi-Protocol Label Switching Extensions 1224 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1225 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1226 February 2003, work in progress." 1227 DEFVAL { 0 } 1228 ::= { gmplsLabelEntry 9 } 1229 gmplsLabelSdhVc OBJECT-TYPE 1230 SYNTAX Integer32 (0..15) 1231 MAX-ACCESS read-create 1232 STATUS current 1233 DESCRIPTION 1234 "The VC Indicator (U) of an SDH Generalized Label. 1235 Zero indicates that this field is non-significant. 1236 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). 1237 This object cannot be modified if 1238 gmplsLabelRowStatus is active(1)." 1239 REFERENCE 1240 "Generalized Multi-Protocol Label Switching Extensions 1241 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1242 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1243 February 2003, work in progress." 1244 DEFVAL { 0 } 1245 ::= { gmplsLabelEntry 10 } 1247 gmplsLabelSdhVcBranch OBJECT-TYPE 1248 SYNTAX Integer32 (0..15) 1249 MAX-ACCESS read-create 1250 STATUS current 1251 DESCRIPTION 1252 "The VC Branch Indicator (K) of an SDH Generalized 1253 Label. Zero indicates that this field is non-significant. 1254 Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This 1255 object cannot be modified if gmplsLabelRowStatus is active(1)." 1257 REFERENCE 1258 "Generalized Multi-Protocol Label Switching Extensions 1259 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1260 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1261 February 2003, work in progress." 1262 DEFVAL { 0 } 1263 ::= { gmplsLabelEntry 11 } 1265 gmplsLabelSonetSdhBranch OBJECT-TYPE 1266 SYNTAX Integer32 (0..15) 1267 MAX-ACCESS read-create 1268 STATUS current 1269 DESCRIPTION 1270 "The Branch Indicator (L) of a SONET or SDH 1271 Generalized Label. Zero indicates that this field is 1272 non-significant. Only valid gmplsLabelType is set to 1273 gmplsSonetLabel(4) or gmplsSdhLabel(5). 1274 This object cannot be modified if 1275 gmplsLabelRowStatus is active(1)." 1277 REFERENCE 1278 "Generalized Multi-Protocol Label Switching Extensions 1279 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1280 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1281 February 2003, work in progress." 1282 DEFVAL { 0 } 1283 ::= { gmplsLabelEntry 12 } 1285 gmplsLabelSonetSdhGroupBranch OBJECT-TYPE 1286 SYNTAX Integer32 (0..15) 1287 MAX-ACCESS read-create 1288 STATUS current 1289 DESCRIPTION 1290 "The Group Branch Indicator (M) of a SONET or SDH 1291 Generalized Label. Zero indicates that this field is 1292 non-significant. Only valid if gmplsLabelType is set 1293 to gmplsSonetLabel(4) or gmplsSdhLabel(5). 1294 This object cannot be modified if 1295 gmplsLabelRowStatus is active(1)." 1296 REFERENCE 1297 "Generalized Multi-Protocol Label Switching Extensions 1298 for SONET and SDH Control, Mannie, E., Papadimitriou, D. 1299 (Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1300 February 2003, work in progress." 1301 DEFVAL { 0 } 1302 ::= { gmplsLabelEntry 13 } 1304 gmplsLabelWavebandId OBJECT-TYPE 1305 SYNTAX Unsigned32 1306 MAX-ACCESS read-create 1307 STATUS current 1308 DESCRIPTION 1309 "The waveband identifier component of a waveband label. Only 1310 valid if gmplsLabelType is set to gmplsWavebandLabel(6). This 1311 object cannot be modified if gmplsLabelRowStatus is active(1)." 1312 REFERENCE 1313 "Generalized Multi-Protocol Label Switching (GMPLS) 1314 Signaling Functional Description, Berger, L. (Editor), 1315 RFC 3471, January 2003." 1316 DEFVAL { 0 } 1317 ::= { gmplsLabelEntry 14 } 1319 gmplsLabelWavebandStart OBJECT-TYPE 1320 SYNTAX Unsigned32 1321 MAX-ACCESS read-create 1322 STATUS current 1323 DESCRIPTION 1324 "The starting label component of a waveband label. 1325 Only valid if gmplsLabelType is set to 1326 gmplsWavebandLabel(6). 1328 This object cannot be modified if 1329 gmplsLabelRowStatus is active(1)." 1331 REFERENCE 1332 "Generalized Multi-Protocol Label Switching (GMPLS) 1333 Signaling Functional Description, Berger, L. (Editor), 1334 RFC 3471, January 2003." 1335 DEFVAL { 0 } 1336 ::= { gmplsLabelEntry 15 } 1338 gmplsLabelWavebandEnd OBJECT-TYPE 1339 SYNTAX Unsigned32 1340 MAX-ACCESS read-create 1341 STATUS current 1342 DESCRIPTION 1343 "The end label component of a waveband label. Only 1344 valid if gmplsLabelType is set to gmplsWavebandLabel(6). 1345 This object cannot be modified if 1346 gmplsLabelRowStatus is active(1)." 1347 REFERENCE 1348 "Generalized Multi-Protocol Label Switching (GMPLS) 1349 Signaling Functional Description, Berger, L. (Editor), 1350 RFC 3471, January 2003." 1351 DEFVAL { 0 } 1352 ::= { gmplsLabelEntry 16 } 1354 gmplsLabelRowStatus OBJECT-TYPE 1355 SYNTAX RowStatus 1356 MAX-ACCESS read-create 1357 STATUS current 1358 DESCRIPTION 1359 "This variable is used to create, modify, and/or 1360 delete a row in this table. When a row in this 1361 table has a row in the active(1) state, no objects in this row 1362 can be modified except the gmplsLabelRowStatus and 1363 gmplsLabelStorageType." 1364 ::= { gmplsLabelEntry 17 } 1366 gmplsLabelStorageType OBJECT-TYPE 1367 SYNTAX StorageType 1368 MAX-ACCESS read-create 1369 STATUS current 1370 DESCRIPTION 1371 "This variable indicates the storage type for this object. 1372 The agent MUST ensure that this object's value remains 1373 consistent with the storage type of any rows in other 1374 tables that contain pointers to this row. In particular, 1375 the storage type of this row must be at least as permanent 1376 as that of any row that point to it. 1378 Conceptual rows having the value 'permanent' need not 1379 allow write-access to any columnar objects in the row." 1380 REFERENCE 1381 "See RFC2579." 1382 DEFVAL { volatile } 1383 ::= { gmplsLabelEntry 18 } 1385 -- End of GMPLS Label Table 1387 -- Module compliance. 1389 gmplsLabelGroups 1390 OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } 1392 gmplsLabelCompliances 1393 OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } 1395 gmplsLabelModuleROCompliance MODULE-COMPLIANCE 1396 STATUS current 1397 DESCRIPTION 1398 "Compliance requirement for implementations that only 1399 provide read-only support for GMPLS-LABEL-STD-MIB. 1400 Such devices can then be monitored but cannot be 1401 configured using this MIB modules." 1403 MODULE -- this module 1405 -- The mandatory groups have to be implemented by LSRs claiming 1406 -- support for this MIB module. This MIB module is, however, not 1407 -- mandatory for a working implementation of a GMPLS LSR with full 1408 -- MIB support if the GMPLS labels in use can be represented within 1409 -- a 32 bit quantity. 1411 MANDATORY-GROUPS { 1412 gmplsLabelTableGroup 1413 } 1415 -- Units of conformance. 1417 GROUP gmplsLabelTableGroup 1418 DESCRIPTION 1419 "This group is mandatory for devices which support 1420 the gmplsLabelTable." 1422 GROUP gmplsLabelPacketGroup 1423 DESCRIPTION 1424 "This group extends gmplsLabelTableGroup for 1425 implementations that support packet labels." 1427 GROUP gmplsLabelPortWavelengthGroup 1428 DESCRIPTION 1429 "This group extends gmplsLabelTableGroup for 1430 implementations that support port and wavelength 1431 labels." 1433 GROUP gmplsLabelFreeformGroup 1434 DESCRIPTION 1435 "This group extends gmplsLabelTableGroup for 1436 implementations that support freeform labels." 1438 GROUP gmplsLabelSonetSdhGroup 1439 DESCRIPTION 1440 "This group extends gmplsLabelTableGroup for 1441 implementations that support SONET or SDH labels." 1443 GROUP gmplsLabelWavebandGroup 1444 DESCRIPTION 1445 "This group extends gmplsLabelTableGroup for 1446 implementations that support Waveband labels." 1448 -- gmplsLabelTable 1450 OBJECT gmplsLabelType 1451 MIN-ACCESS read-only 1452 DESCRIPTION 1453 "Write access is not required." 1455 OBJECT gmplsLabelMplsLabel 1456 MIN-ACCESS read-only 1457 DESCRIPTION 1458 "Write access is not required." 1460 OBJECT gmplsLabelPortWavelength 1461 MIN-ACCESS read-only 1462 DESCRIPTION 1463 "Write access is not required." 1465 OBJECT gmplsLabelFreeform 1466 MIN-ACCESS read-only 1467 DESCRIPTION 1468 "Write access is not required." 1470 OBJECT gmplsLabelSonetSdhSignalIndex 1471 MIN-ACCESS read-only 1472 DESCRIPTION 1473 "Write access is not required." 1475 OBJECT gmplsLabelSdhVc 1476 MIN-ACCESS read-only 1477 DESCRIPTION 1478 "Write access is not required." 1480 OBJECT gmplsLabelSdhVcBranch 1481 MIN-ACCESS read-only 1482 DESCRIPTION 1483 "Write access is not required." 1485 OBJECT gmplsLabelSonetSdhBranch 1486 MIN-ACCESS read-only 1487 DESCRIPTION 1488 "Write access is not required." 1490 OBJECT gmplsLabelSonetSdhGroupBranch 1491 MIN-ACCESS read-only 1492 DESCRIPTION 1493 "Write access is not required." 1495 OBJECT gmplsLabelWavebandId 1496 MIN-ACCESS read-only 1497 DESCRIPTION 1498 "Write access is not required." 1500 OBJECT gmplsLabelWavebandStart 1501 MIN-ACCESS read-only 1502 DESCRIPTION 1503 "Write access is not required." 1505 OBJECT gmplsLabelWavebandEnd 1506 MIN-ACCESS read-only 1507 DESCRIPTION 1508 "Write access is not required." 1510 OBJECT gmplsLabelRowStatus 1511 SYNTAX RowStatus { 1512 active(1), 1513 notInService(2) 1514 } 1516 WRITE-SYNTAX RowStatus { 1517 active(1), 1518 notInService(2), 1519 createAndGo(4), 1520 destroy(6) 1521 } 1522 DESCRIPTION 1523 "Support for notInService, createAndWait and notReady 1524 is not required." 1526 OBJECT gmplsLabelStorageType 1527 MIN-ACCESS read-only 1528 DESCRIPTION 1529 "Write access is not required." 1531 ::= { gmplsLabelCompliances 1 } 1533 gmplsLabelModuleFullCompliance MODULE-COMPLIANCE 1534 STATUS current 1535 DESCRIPTION 1536 "Compliance statement for agents that support 1537 the complete GMPLS Label MIB module." 1539 MODULE -- this module 1541 -- The mandatory groups have to be implemented by GMPLS LSRs 1542 -- claiming support for this MIB module. This MIB module is, 1543 -- however, not mandatory for a working implementation of a GMPLS 1544 -- LSR with full MIB support if the GMPLS labels in use can be 1545 -- represented within a 32 bit quantity. 1547 MANDATORY-GROUPS { 1548 gmplsLabelTableGroup, 1549 gmplsLabelPacketGroup, 1550 gmplsLabelPortWavelengthGroup, 1551 gmplsLabelFreeformGroup, 1552 gmplsLabelSonetSdhGroup, 1553 gmplsLabelWavebandGroup 1554 } 1556 OBJECT gmplsLabelRowStatus 1557 SYNTAX RowStatus { active(1), notInService(2) } 1558 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1559 createAndGo(4), destroy(6) 1560 } 1561 DESCRIPTION 1562 "Support for notInService, createAndWait and notReady 1563 is not required." 1565 ::= { gmplsLabelCompliances 2 } 1567 -- Units of conformance. 1569 gmplsLabelTableGroup OBJECT-GROUP 1570 OBJECTS { 1571 gmplsLabelIndexNext, 1572 gmplsLabelType, 1573 gmplsLabelRowStatus, 1574 gmplsLabelStorageType 1575 } 1576 STATUS current 1577 DESCRIPTION 1578 "Necessary, but not sufficient, set of objects to 1579 implement label table support. In addition, 1580 depending on the type of labels supported (for 1582 example, wavelength labels), the following other 1583 groups defined below are mandatory: 1584 gmplsLabelPacketGroup and/or 1585 gmplsLabelPortWavelengthGroup and/or 1586 gmplsLabelFreeformGroup and/or 1587 gmplsLabelSonetSdhGroup." 1588 ::= { gmplsLabelGroups 1 } 1590 gmplsLabelPacketGroup OBJECT-GROUP 1591 OBJECTS { 1592 gmplsLabelMplsLabel 1593 } 1594 STATUS current 1595 DESCRIPTION 1596 "Object needed to implement Packet (MPLS) labels." 1597 ::= { gmplsLabelGroups 2 } 1599 gmplsLabelPortWavelengthGroup OBJECT-GROUP 1600 OBJECTS { 1601 gmplsLabelPortWavelength 1602 } 1603 STATUS current 1604 DESCRIPTION 1605 "Object needed to implement Port and Wavelength 1606 labels." 1607 ::= { gmplsLabelGroups 3 } 1609 gmplsLabelFreeformGroup OBJECT-GROUP 1610 OBJECTS { 1611 gmplsLabelFreeform 1612 } 1613 STATUS current 1614 DESCRIPTION 1615 "Object needed to implement Freeform labels." 1616 ::= { gmplsLabelGroups 4 } 1618 gmplsLabelSonetSdhGroup OBJECT-GROUP 1619 OBJECTS { 1620 gmplsLabelSonetSdhSignalIndex, 1621 gmplsLabelSdhVc, 1622 gmplsLabelSdhVcBranch, 1623 gmplsLabelSonetSdhBranch, 1624 gmplsLabelSonetSdhGroupBranch 1625 } 1626 STATUS current 1627 DESCRIPTION 1628 "Object needed to implement SONET and SDH labels." 1629 ::= { gmplsLabelGroups 5 } 1631 gmplsLabelWavebandGroup OBJECT-GROUP 1632 OBJECTS { 1633 gmplsLabelWavebandId, 1634 gmplsLabelWavebandStart, 1635 gmplsLabelWavebandEnd 1636 } 1637 STATUS current 1638 DESCRIPTION 1639 "Object needed to implement Waveband labels." 1640 ::= { gmplsLabelGroups 6 } 1642 END 1644 9. Security Considerations 1646 It is clear that the MIB modules described in this document in 1647 association with the MPLS-LSR-STD-MIB are potentially useful for 1648 monitoring of GMPLS LSRs. These MIB modules can also be used for 1649 configuration of certain objects, and anything that can be configured 1650 can be incorrectly configured, with potentially disastrous results. 1652 There are a number of management objects defined in these MIB modules 1653 with a MAX-ACCESS clause of read-write and/or read-create. Such 1654 objects may be considered sensitive or vulnerable in some network 1655 environments. The support for SET operations in a non-secure 1656 environment without proper protection can have a negative effect on 1657 network operations. These are the tables and objects and their 1658 sensitivity/vulnerability: 1660 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1661 and gmplsLabelTable collectively contain objects to provision 1662 GMPLS interfaces, LSPs and their associated parameters on a Label 1663 Switching Router (LSR). Unauthorized write access to objects in 1664 these tables, could result in disruption of traffic on the 1665 network. This is especially true if an LSP has already been 1666 established. The use of stronger mechanisms such as SNMPv3 1667 security should be considered where possible. Specifically, SNMPv3 1668 VACM and USM MUST be used with any SNMPv3 agent which implements 1669 these MIB modules. 1671 Some of the readable objects in these MIB modules "i.e., objects with 1672 a MAX-ACCESS other than not-accessible" may be considered sensitive 1673 or vulnerable in some network environments. It is thus important to 1674 control even GET and/or NOTIFY access to these objects and possibly 1675 to even encrypt the values of these objects when sending them over 1676 the network via SNMP. These are the tables and objects and their 1677 sensitivity/vulnerability: 1679 o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable 1680 and gmplsLabelTable collectively show the LSP network topology and 1681 its capabilities. If an Administrator does not want to reveal this 1682 information, then these tables should be considered 1683 sensitive/vulnerable. 1685 SNMP versions prior to SNMPv3 did not include adequate security. Even 1686 if the network itself is secure "for example by using IPSec", even 1687 then, there is no control as to who on the secure network is allowed 1688 to access and GET/SET "read/change/create/delete" the objects in 1689 these MIB modules. It is RECOMMENDED that implementers consider the 1690 security features as provided by the SNMPv3 framework "see [RFC3410], 1691 section 8", including full support for the SNMPv3 cryptographic 1692 mechanisms "for authentication and privacy". 1694 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1695 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1696 enable cryptographic security. It is then a customer/operator 1697 responsibility to ensure that the SNMP entity giving access to an 1698 instance of this MIB module, is properly configured to give access to 1699 the objects only to those principals "users" that have legitimate 1700 rights to indeed GET or SET "change/create/delete" them. 1702 10. Acknowledgments 1704 This draft is the work of the five authors listed in the Authors' 1705 Addresses section. 1707 This document extends [RFC3813]. The authors would like to express 1708 their gratitude to all those who worked on that earlier MIB document. 1710 The authors would like to express their thanks to Dan Joyle for his 1711 careful review and comments on early versions of the Label Table. 1712 Special thanks to Joan Cucchiara and Len Nieman for their help with 1713 compilation issues. 1715 11. IANA Considerations 1717 MPLS related standards track MIB modules are rooted under the 1718 mplsStdMIB subtree. 1720 One of the MIB modules contained in this document extends tables 1721 contained in MPLS MIB modules. 1723 As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the 1724 two MIB modules contained in this document should be placed in the 1725 mplsStdMIB subtree as well. 1727 New assignments can only be made via a Standards Action as specified 1728 in [RFC2434]. 1730 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 1732 The IANA is requested to assign { mplsStdMIB xx } to the 1733 GMPLS-LSR-STD-MIB module specified in this document. 1735 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 1737 The IANA is requested to assign { mplsStdMIB xx } to the 1738 GMPLS-LABEL-STD-MIB module specified in this document. 1740 12. References 1742 12.1. Normative References 1744 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1745 Requirement Levels", BCP 14, RFC 2119, March 1997. 1747 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1748 Case, J., Rose, M., and S. Waldbusser, "Structure 1749 of Management Information Version 2 (SMIv2)", STD 1750 58, RFC 2578, April 1999. 1752 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1753 Case, J., Rose, M., and S. Waldbusser, "Textual 1754 Conventions for SMIv2", STD 58, RFC 2579, April 1755 1999. 1757 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1758 Case, J., Rose, M., and S. Waldbusser, "Conformance 1759 Statements for SMIv2", STD 58, RFC 2580, April 1760 1999. 1762 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces 1763 Group MIB", RFC 2863, June 2000. 1765 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 1766 Information Base for the Differentiated Services 1767 Architecture", RFC 3289, May 2002. 1769 [RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL) 1770 Processing in Multi-Protocol Label Switching 1771 (MPLS) Networks", RFC 3443, January 2003. 1773 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1774 Conventions and for Multiprotocol Label Switching 1775 (MPLS) Management", RFC 3811, June 2004. 1777 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1778 "Multiprotocol Label Switching (MPLS) Label 1779 Switching (LSR) Router Management Information Base 1780 (MIB)", RFC 3813, June 2004. 1782 [RFC3945] Mannie, E. (Editor), "Generalized Multiprotocol 1783 Label Switching (GMPLS) Architecture", RFC 3945, 1784 October 2004. 1786 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 1787 "Generalized Multi-Protocol Label Switching 1788 Extensions for SONET and SDH Control", 1789 draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, 1790 February 2003, work in progress. 1792 [GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of 1793 Textual Conventions for Multiprotocol Label 1794 Switching (MPLS) Management", 1795 draft-ietf-ccamp-gmpls-tc-mib-06.txt, October 2004, 1796 work in progress. 1798 [GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized 1799 Multiprotocol Label Switching (GMPLS) Traffic 1800 Engineering Management Information Base", 1801 draft-ietf-ccamp-gmpls-te-mib-08.txt, February 1802 2005, work in progress. 1804 12.2. Informational References 1806 [RFC2026] S. Bradner, "The Internet Standards Process -- 1807 Revision 3", RFC 2026, October 1996. 1809 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 1810 Writing an IANA Considerations Section in RFCs", 1811 BCP: 26, RFC 2434, October 1998. 1813 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1814 "Multiprotocol Label Switching Architecture", RFC 1815 3031, January 2001. 1817 [RFC3032] Rosen, E. et al, "MPLS Label Stack Encoding", 1818 RFC 3032, January 2001. 1820 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 1821 Srinivasan, V., and G. Swallow, "RSVP-TE: 1822 Extensions to RSVP for LSP Tunnels", RFC 3209, 1823 December 2001. 1825 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 1826 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 1827 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 1828 T., Feldman, N., Fredette, A., Girish, M., Gray, 1829 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 1830 A., and P. Vaananen, "Constraint-Based LSP Setup 1831 using LDP", RFC 3212, December 2001." 1833 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1834 "Introduction and Applicability Statements for 1835 Internet-Standard Management Framework", RFC 3410, 1836 December 2002. 1838 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1839 Architecture for Describing Simple Network 1840 Management Protocol (SNMP) Management Frameworks", 1841 RFC 3411, December 2002. 1843 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 1844 Applications", RFC 3413, December 2002. 1846 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 1847 Label Switching (GMPLS) Signaling Functional 1848 Description", RFC 3471, January 2003. 1850 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 1851 "Generalized MPLS Signaling - CR-LDP Extensions", 1852 RFC 3472, January 2003. 1854 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 1855 RSVP-TE Extensions", RFC 3473 January 2003. 1857 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1858 "Multiprotocol Label Switching (MPLS) Traffic 1859 Engineering (TE) Management Information Base 1860 (MIB)", RFC 3812, June 2004. 1862 13. Authors' Addresses 1864 Thomas D. Nadeau 1865 Cisco Systems, Inc. 1866 300 Apollo Drive 1867 Chelmsford, MA 01824 1868 Phone: +1-978-244-3051 1869 Email: tnadeau@cisco.com 1870 Cheenu Srinivasan 1871 Bloomberg L.P. 1872 499 Park Ave., 1873 New York, NY 10022 1874 Phone: +1-212-893-3682 1875 Email: cheenu@bloomberg.net 1877 Adrian Farrel 1878 Old Dog Consulting 1879 Phone: +44-(0)-1978-860944 1880 Email: adrian@olddog.co.uk 1882 Tim Hall 1883 Data Connection Ltd. 1884 100 Church Street 1885 Enfield, Middlesex, EN2 6BQ, UK 1886 Phone: +44 20 8366 1177 1887 Email: tim.hall@dataconnection.com 1889 Ed Harrison 1890 Data Connection Ltd. 1891 100 Church Street 1892 Enfield, Middlesex, EN2 6BQ, UK 1893 Phone: +44 20 8366 1177 1894 Email: ed.harrison@dataconnection.com 1896 14. Intellectual Property Considerations 1898 The IETF takes no position regarding the validity or scope of any 1899 Intellectual Property Rights or other rights that might be claimed to 1900 pertain to the implementation or use of the technology described in 1901 this document or the extent to which any license under such rights 1902 might or might not be available; nor does it represent that it has 1903 made any independent effort to identify any such rights. Information 1904 on the procedures with respect to rights in RFC documents can be 1905 found in BCP 78 and BCP 79. 1907 Copies of IPR disclosures made to the IETF Secretariat and any 1908 assurances of licenses to be made available, or the result of an 1909 attempt made to obtain a general license or permission for the use of 1910 such proprietary rights by implementers or users of this 1911 specification can be obtained from the IETF on-line IPR repository at 1912 http://www.ietf.org/ipr. 1914 The IETF invites any interested party to bring to its attention any 1915 copyrights, patents or patent applications, or other proprietary 1916 rights that may cover technology that may be required to implement 1917 this standard. Please address the information to the IETF at 1918 ietf-ipr@ietf.org. 1920 15. Full Copyright Statement 1922 Copyright (C) The Internet Society (2005). This document is subject 1923 to the rights, licenses and restrictions contained in BCP 78 and 1924 except as set forth therein, the authors retain all their rights. 1926 This document and the information contained herein are provided on an 1927 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1928 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1929 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1930 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1931 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1932 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.