idnits 2.17.1 draft-ietf-mpls-lsr-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document is more than 15 pages and seems to lack a Table of Contents. == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 54 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 55 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([MPLSArch,MPLSFW]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1605: '... mplsOutSegmentIndex MUST be non-zero....' RFC 2119 keyword, line 1613: '...5 imply terminating LSPs and MUST have...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2659 has weird spacing: '...for the purpo...' -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 83, but not defined == Unused Reference: 'LDPMIB' is defined on line 2525, but no explicit reference was found in the text == Unused Reference: 'RSVPTun' is defined on line 2536, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 2541, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2545, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSFW' -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LDPMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTun' -- Possible downref: Non-RFC (?) normative reference: ref. 'CRLDP' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 22 errors (**), 0 flaws (~~), 10 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Cheenu Srinivasan 2 Internet Draft Tachion Networks, Inc. 3 Expires: August 2000 4 Arun Viswanathan 5 Force10 Networks 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 MPLS Label Switch Router Management Information Base Using SMIv2 12 draft-ietf-mpls-lsr-mib-01.txt 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet- 27 Drafts as reference material or to cite them other than as "work 28 in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This memo defines an experimental portion of the Management 39 Information Base (MIB) for use with network management protocols 40 in the Internet community. In particular, it describes managed 41 objects for modeling a Multi-Protocol Label Switching (MPLS) 42 [MPLSArch, MPLSFW] Label Switch Router (LSR). 44 Open Issues 46 Still waiting for new IANA ifType for MPLS interface layer. 48 1. Introduction 49 This memo defines an experimental portion of the Management 50 Information Base (MIB) for use with network management protocols 51 in the Internet community. In particular, it describes managed 52 objects for modeling a Multi-Protocol Label Switching (MPLS) 53 [MPLSArch, MPLSFW] Label Switch Router (LSR). 55 Comments should be made directly to the MPLS mailing list at 56 mpls@uu.net. 58 This memo does not, in its draft form, specify a standard for the 59 Internet community. 61 2. Terminology 63 This document uses terminology from the document describing the 64 MPLS architecture [MPLSArch]. A label switched path (LSP) is 65 modeled as a connection consisting of one or more incoming 66 segments (in-segments) and/or one or more outgoing segments (out- 67 segments) at a label switch router (LSR). The association or 68 interconnection of the in-segments and out-segments is 69 accomplished by using a cross-connect. We use the terminology 70 "connection" and "LSP" interchangeably where the meaning is clear 71 from the context. 73 3. The SNMP Management Framework 75 The SNMP Management Framework presently consists of five major 76 components: 78 - An overall architecture, described in RFC 2271 [SNMPArch]. 80 - Mechanisms for describing and naming objects and events for the 81 purpose of management. The first version of this Structure of 82 Management Information (SMI) is called SMIv1 and described in 83 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 84 [SNMPv1Traps]. The second version, called SMIv2, is described 85 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 86 [SNMPv2Conf]. 88 - Message protocols for transferring management information. The 89 first version of the SNMP message protocol is called SNMPv1 90 and described in RFC 1157 [SNMPv1]. A second version of the 91 SNMP message protocol, which is not an Internet standards 92 track protocol, is called SNMPv2c and described in RFC 1901 93 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 94 message protocol is called SNMPv3 and described in RFC 1906 95 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 97 - Protocol operations for accessing management information. The 98 first set of protocol operations and associated PDU formats is 99 described in RFC 1157 [SNMPv1]. A second set of protocol 100 operations and associated PDU formats is described in RFC 1905 101 [SNMPv2PO]. 103 - A set of fundamental applications described in RFC 2273 104 [SNMPv3App] and the view-based access control mechanism 105 described in RFC 2575 [SNMPv3VACM]. 107 Managed objects are accessed via a virtual information store, 108 termed the Management Information Base or MIB. Objects in the MIB 109 are defined using the mechanisms defined in the SMI. This memo 110 specifies a MIB module that is compliant to the SMIv2. A MIB 111 conforming to the SMIv1 can be produced through the appropriate 112 translations. The resulting translated MIB must be semantically 113 equivalent, except where objects or events are omitted because no 114 translation is possible (use of Counter64). Some machine-readable 115 information in SMIv2 will be converted into textual descriptions 116 in SMIv1 during the translation process. However, this loss of 117 machine-readable information is not considered to change the 118 semantics of the MIB. 120 3.1. Object Definitions 122 Managed objects are accessed via a virtual information store, 123 termed the Management Information Base or MIB. Objects in the MIB 124 are defined using the subset of Abstract Syntax Notation One 125 (ASN.1) defined in the SMI. In particular, each object type is 126 named by an OBJECT IDENTIFIER, an administratively assigned name. 127 The object type together with an object instance serves to 128 uniquely identify a specific instantiation of the object. For 129 human convenience, we often use a textual string, termed the 130 descriptor, to also refer to the object type. 132 4. Feature Checklist 134 The MPLS label switch router MIB (LSR-MIB) is designed to satisfy 135 the following requirements and constraints: 137 - The MIB should be able to support both manually configured LSPs 138 as well as those configured via CR-LDP and/or RSVP signaling. 140 - The MIB must support the enabling and disabling of MPLS 141 capability on MPLS capable interfaces of an LSR. 143 - The MIB should allow resource sharing between two or more LSPs. 145 - Both per-platform and per-interface label spaces must be 146 supported. 148 - MPLS packets must be forwarded solely based on an incoming top 149 label [MPLSArch, LblStk]. 151 - Support must be provided for next-hop resolution when the 152 outgoing interface is a shared media interface. In the point- 153 to-multipoint case, each outgoing segment can reside on a 154 different shared media interface. 156 - The MIB must support point-to-point, point-to-multipoint and 157 multipoint-to-point connections at an LSR. 159 - For multipoint-to-point connections all outgoing packets must 160 have the same top label. 162 - For multipoint-to-point connections, the outgoing resources of 163 the merged connections must be shared. 165 - For multipoint-to-point connections, packets from different 166 incoming connections may have distinct outgoing label stacks 167 beneath the (identical) top label. 169 - In the point-to-multipoint case each outgoing connection can 170 have a distinct label stack including the top label. 172 - All the members of a point-to-multipoint connection share the 173 resources allocated for the ingress segments. 175 - The MIB must provide cross-connect capability to "pop" an 176 incoming label and forward the packet with the remainder of 177 the label stack unchanged and without pushing any labels ("pop- 178 and-go") [LblStk]. 180 - It must be possible to assign or re-map the Class of Service 181 (COS) bits [LblStk] on the outgoing label. In the multipoint- 182 to-point case, each in-segment can have a different outgoing 183 COS value. In the point-to-multipoint case, each out-segment 184 can have a different outgoing COS value. 186 - It should be possible to support persistent as well as non- 187 persistent LSPs. 189 - Performance counters must be provided for in-segments and out- 190 segments as well as for measuring MPLS performance on a per- 191 interface basis. 193 5. Outline 194 Configuring LSPs through an LSR involves the following steps: 196 - Enabling MPLS on MPLS capable interfaces. 198 - Configuring in-segments and out-segments. 200 - Setting up the cross-connect table to associate segments and/or 201 to indicate connection origination and termination. 203 - Optionally specifying label stack actions. 205 - Optionally specifying segment traffic parameters. 207 5.1. Summary of LSR MIB 209 The MIB objects for performing these actions consist of the 210 following tables: 212 - The interface configuration table (mplsInterfaceConfTable), 213 which is used for enabling the MPLS protocol on MPLS-capable 214 interfaces. 216 - The in-segment (mplsInSegmentTable) and out-segment 217 (mplsOutSegmentTable) tables, which are used for configuring 218 LSP segments at an LSR. 220 - The cross-connect table (mplsXCTable), which is used to 221 associate in and out segments together, in order to form a 222 cross-connect. 224 - The label stack table (mplsLabelStackTable), which is used for 225 specifying label stack operations. 227 - The TSpec table (mplsTSpecTable), which is used for specifying 228 LSP-related traffic parameters. 230 Further, the MPLS in-segment and out-segment performance tables, 231 mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the 232 objects necessary to measure the performance of LSPs, and 233 mplsInterfacePerfTable has objects to measure MPLS performance on 234 a per-interface basis. 236 These tables are described in the subsequent sections. 238 6. Brief Description of MIB Objects 240 Sections 6.1-6.3 describe objects pertaining to MPLS capable 241 interfaces of an LSR. The objects described in Sections 6.4-6.9, 242 when considered together, are equivalent to the tables described 243 in the MPLS architecture document [MPLSArch], that is, the 244 Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry 245 (NHLFE) tables. Section 6.10 describes objects for specifying 246 traffic parameters for in and out segments. 248 6.1. mplsInterfaceConfTable 250 This table represents the interfaces that are MPLS capable. An 251 LSR creates an entry in this table for every MPLS capable 252 interface on that LSR. Each entry contains information about per- 253 interface label ranges. The administrator can specify the desired 254 MPLS status (enable/up, disable/down, testing) of an interface by 255 writing the object mplsInterfaceAdminStatus. The actual status is 256 indicated by the object mplsInterfaceOperStatus. 258 6.2. mplsInterfaceResTable 260 This table provides resource information such as available and 261 allocated bandwidth and buffers on each MPLS capable interface for 262 each priority level. 264 6.3. mplsInterfacePerfTable 266 This table contains objects to measure the MPLS performance of 267 MPLS capable interfaces and is an AUGMENT to 268 mplsInterfaceConfTable. High capacity counters are provided for 269 objects that are likely to wrap around quickly on high-speed 270 interfaces. 272 6.4. mplsInSegmentTable 274 This table contains a description of the incoming MPLS segments to 275 an LSR and their associated parameters. 277 6.5. mplsInSegmentPerfTable 279 The MPLS In-Segment Performance Table has objects to measure the 280 performance of an incoming segment configured on an LSR. It is an 281 AUGMENT to mplsInSegmentTable. High capacity counters are 282 provided for objects that are likely to wrap around quickly on 283 high-speed interfaces. 285 6.6. mplsOutSegmentTable 287 The Out-Segment Table contains a description of the outgoing MPLS 288 segments at an LSR and their associated parameters. 290 6.7. mplsOutSegmentPerfTable 292 The MPLS Out-Segment Table contains objects to measure the 293 performance of an outgoing segment configured on an LSR. It is an 294 AUGMENT to mplsOutSegmentTable. High capacity counters are 295 provided for objects that are likely to wrap around quickly on 296 high-speed interfaces. 298 6.8. mplsXCTable 300 The mplsXCTable specifies information for associating segments 301 together in order to instruct the LSR to switch between the 302 specified segments. It supports point-to-point, point-to-multi- 303 point and multi-point-to-point connections. 305 6.9. mplsLabelStackTable 307 The mplsLabelStackTable specifies the label stack to be pushed 308 onto a packet, beneath the top label. Entries to this table are 309 referred to from mplsXCTable. 311 6.10. mplsTSpecTable 313 The mplsTSpecTable contains objects for specifying the traffic 314 parameters of in-segments and out-segments. Entries in this table 315 are referred to from mplsInSegmentTable and mplsOutSegmentTable. 317 7. Example of LSP Setup 319 In this section we provide a brief example of using the MIB 320 objects described in Section 8 to set up an LSP. While this 321 example is not meant to illustrate every nuance of the MIB, it is 322 intended as an aid to understanding some of the key concepts. It 323 is meant to be read after going through the MIB itself. 325 Suppose that one would like to manually create a best-effort, 326 unidirectional LSP. Assume that the LSP enters the LSR via MPLS 327 interface A with ifIndex 12 and exits the LSR via MPLS interface B 328 with ifIndex 13. Let us assume that we do not wish to have a label 329 stack beneath the top label on the outgoing labeled packets. The 330 following example illustrates which rows and corresponding objects 331 might be created to accomplish this. 333 First, the TSpec entries must be set-up for both segments. 335 In mplsTSpecTable for the incoming direction: 336 { 337 mplsTSpecIndex = 5 338 mplsTSpecDirection = in(1), 339 mplsTSpecMaxRate = 100000, 340 mplsTSpecMeanRate = 100000, 341 mplsTSpecMaxBurstSize = 2000, 342 mplsTSpecRowStatus = createAndGo(4) 343 } 345 In mplsTSpecTable for the outgoing direction: 346 { 347 mplsTSpecIndex = 6 348 mplsTSpecDirection = out(2), 349 mplsTSpecMaxRate = 100000, 350 mplsTSpecMeanRate = 100000, 351 mplsTSpecMaxBurstSize = 2000, 352 mplsTSpecRowStatus = createAndGo(4) 354 } 356 Note that if we were setting up a bi-directional LSP, the segments 357 in the reverse direction can share the TSpec entries (and hence 358 resources) with the segments in the forward direction. 360 We must next create the appropriate in-segment and out-segment 361 entries with suitable traffic parameters by pointing to the 362 appropriate TSpec entries that we have just created. 364 In mplsInSegmentTable: 365 { 366 mplsInSegmentIfIndex = 12, -- incoming interface 367 mplsInSegmentLabel = 21, -- incoming label 368 mplsInSegmentNPop = 1, 369 mplsInSegmentTSpecIndex = 5, 370 mplsInSegmentRowStatus = createAndGo(4) 371 } 373 In mplsOutSegmentTable: 374 { 375 mplsOutSegmentIndex = 1, 376 mplsOutSegmentIfIndex = 13, -- outgoing interface 377 mplsOutSegmentPushTopLabel = true(1), 378 mplsOutSegmentTopLabel = 22, -- outgoing label 379 mplsOutSegmentTSpecIndex = 6, 380 mplsOutSegmentRowStatus = createAndGo(4) 381 } 383 Next, a cross-connect entry is created thereby associating the 384 newly created segments together. 386 In mplsXCTable: 387 { 388 mplsXCIndex = 2, 389 mplsXCLspId = "1.2.3.4-2", 390 mplsInSegmentIfIndex = 12, 391 mplsInSegmentLabel = 21, 392 mplsOutSegmentIndex = 1, 393 mplsXCCOS = 0, 394 mplsXCIsPersistent = false (1), 395 mplsLabelStackIndex = 0, -- only a single outgoing label 396 mplsXCRowStatus = createAndGo(4) 397 } 399 Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex 400 objects will automatically be populated with the value 2 when 401 these segments are referred to from the corresponding cross- 402 connect entry. 404 8. Application of the Interface Group to MPLS 406 The Interfaces Group of MIB II defines generic managed objects for 407 managing interfaces. This memo contains the media-specific 408 extensions to the Interfaces Group for managing MPLS interfaces. 410 This memo assumes the interpretation of the Interfaces Group to be 411 in accordance with [IFMIB] which states that the interfaces table 412 (ifTable) contains information on the managed resource's 413 interfaces and that each sub-layer below the internetwork layer of 414 a network interface is considered an interface. Thus, the MPLS 415 layer interface is represented as an entry in the ifTable. This 416 entry is concerned with the MPLS layer as a whole, and not with 417 individual LSPs/tunnels which are managed via the MPLS-specific 418 managed objects specified in this memo and [TEMIB]. The inter- 419 relation of entries in the ifTable is defined by Interfaces Stack 420 Group defined in [IFMIB]. 422 8.1. Support of the MPLS Layer by ifTable 424 Some specific interpretations of ifTable for the MPLS layer 425 follow. 427 Object Use for the MPLS layer 429 ifIndex Each MPLS interface is represented by an ifEntry. 431 ifDescr Description of the MPLS interface. 433 ifType The value that is allocated for MPLS is . 435 ifSpeed The total bandwidth in bits per second for use by 436 the MPLS layer. 438 ifPhysAddress Unused. 440 ifAdminStatus See [IFMIB]. 442 ifOperStatus Assumes the value down(2) if the MPLS layer is 443 down. 445 ifLastChange See [IFMIB]. 447 ifInOctets The number of received octets over the interface, 448 i.e., the number of received, octets received as 449 labeled packets. 451 ifOutOctets The number of transmitted octets over the 452 interface, i.e., the number of octets transmitted 453 as labeled packets. 455 ifInErrors The number of labeled packets dropped due to 456 uncorrectable errors. 458 ifInUnknownProtos 459 The number of received packets discarded during 460 packet header validation, including packets with 461 unrecognized label values. 463 ifOutErrors See [IFMIB]. 465 ifName Textual name (unique on this system) of the 466 interface or an octet string of zero length. 468 ifLinkUpDownTrapEnable 469 Default is disabled (2). 471 ifConnectorPresent 472 Set to false (2). 474 ifHighSpeed See [IFMIB]. 476 ifHCInOctets The 64-bit version of ifInOctets; supported if 477 required by the compliance statements in [IFMIB]. 479 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 480 required by the compliance statements in [IFMIB]. 482 ifAlias The non-volatile 'alias' name for the interface as 483 specified by a network manager. 485 9. MPLS Label Switch Router MIB Definitions 487 MPLS-LSR-MIB DEFINITIONS ::= BEGIN 489 IMPORTS 490 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 491 experimental, Integer32, Unsigned32, Counter32, 492 Counter64, Gauge32, IpAddress 493 FROM SNMPv2-SMI 494 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 495 FROM SNMPv2-CONF 496 TEXTUAL-CONVENTION, TruthValue, RowStatus 497 FROM SNMPv2-TC 498 ifIndex, InterfaceIndex, InterfaceIndexOrZero 499 FROM IF-MIB; 501 mplsLsrMIB MODULE-IDENTITY 502 LAST-UPDATED "200002161200Z" -- 16 February 2000 12:00:00 EST 503 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 504 CONTACT-INFO 505 " Cheenu Srinivasan 506 Postal: Tachion Networks, Inc. 507 2 Meridian Road 508 Eatontown, NJ 0772 509 Tel: +1 732 542 7750 x234 510 Email: cheenu@tachion.com 512 Arun Viswanathan 513 Postal: Force10 Networks 514 1440 McCarthy Blvd 515 Milpitas, CA 95035 516 Tel: +1-408-571-3516 517 Email: arun@force10networks.com 519 Thomas D. Nadeau 520 Postal: Cisco Systems, Inc. 521 250 Apollo Drive 522 Chelmsford, MA 01824 523 Tel: +1-978-244-3051 524 Email: tnadeau@cisco.com" 526 DESCRIPTION 527 "This MIB contains managed object definitions for the 528 Multiprotocol Label Switching (MPLS) Router as 529 defined in: Rosen, E., Viswanathan, A., and R. 530 Callon, Multiprotocol Label Switching Architecture, 531 Internet Draft , 532 February 2000." 534 -- Revision history. 535 REVISION 536 "199907161200Z" -- 16 July 1999 12:00:00 EST 537 DESCRIPTION 538 "Initial draft version." 539 REVISION 540 "200002161200Z" -- 16 February 2000 12:00:00 EST 541 DESCRIPTION 542 "Second draft version." 544 ::= { experimental 96 } 546 -- Textual Conventions. 548 MplsLSPID ::= TEXTUAL-CONVENTION 549 STATUS current 550 DESCRIPTION 551 "An identifier that is assigned to each LSP and is 552 used to uniquely identify it. This is assigned at 553 the head end of the LSP and can be used by all LSRs 554 to identify this LSP. This value is piggybacked by 555 the signaling protocol when this LSP is signaled 556 within the network. This identifier can then be used 557 at each LSR to identify which labels are being 558 swapped to other labels for this LSP. For IPv4 559 addresses this results in a 6-octet long cookie." 560 SYNTAX OCTET STRING (SIZE (0..63)) 562 MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION 563 STATUS current 564 DESCRIPTION 565 "An address family. These values are defined in RFC 566 1700 and are maintained by The IANA. All values may 567 not be relevant in all contexts when used in this 568 MIB, but are included for completeness." 569 REFERENCE 570 "RFC 1700 - Assigned Numbers, Reynolds, J. and J. 571 Postel, Oct. 1994" 572 SYNTAX INTEGER { 573 other(0), 574 ipv4(1), 575 ipv6(2), 576 nsap(3), 577 hdlc(4), 578 bbn1822(5), 579 ieee802(6), 580 e163(7), 581 e164(8), 582 f69(9), 583 x121(10), 584 ipx(11), 585 appleTalk(12), 586 decnetIV(13), 587 banyanVines(14), 588 e164WithNsap(15) 589 } 591 -- An MPLS label. 592 MplsLabel ::= TEXTUAL-CONVENTION 593 STATUS current 594 DESCRIPTION 595 "Represents an MPLS label. Note that the contents of 596 a label field are interpreted in an interface-type 597 specific fashion. For example, the 20-bit wide 598 label carried in the MPLS shim header is contained 599 in bits 0-19 and bits 20-31 must be zero. The frame 600 relay label can be either 10, 17 or 23 bits wide 601 depending on the size of the DLCI field and bits 10- 602 31, 17-31 or 23-31 must be zero, respectively. For 603 an ATM interface, bits 0-15 must be interpreted as 604 the VCI, bits 16-23 as the VPI and bits 24-31 must 605 be zero. Note that the permissible label values are 606 also a function of the interface type. For example, 607 the value 3 has special semantics in the control 608 plane for an MPLS shim header label and is not a 609 valid label value in the data path." 610 REFERENCE 611 "1. MPLS Label Stack Encoding, Rosen et al, draft- 612 ietf-mpls-label-encaps-07.txt, March 2000. 613 2. Use of Label Switching on Frame Relay Networks, 614 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998." 615 SYNTAX Integer32 617 Ipv6Address ::= TEXTUAL-CONVENTION 618 STATUS current 619 DESCRIPTION 620 "IPv6 address." 621 SYNTAX OCTET STRING (SIZE(16)) 623 BitRate ::= TEXTUAL-CONVENTION 624 DISPLAY-HINT "d" 625 STATUS current 626 DESCRIPTION 627 " The rate in bits/second." 628 SYNTAX INTEGER (0..'7FFFFFFF'h) 630 BurstSize ::= TEXTUAL-CONVENTION 631 DISPLAY-HINT "d" 632 STATUS current 633 DESCRIPTION 634 "The number of octets of.MPLS data that the stream 635 may send without concern for policing." 636 SYNTAX INTEGER (0..'7FFFFFFF'h) 638 BufferSize ::= TEXTUAL-CONVENTION 639 DISPLAY-HINT "d" 640 STATUS current 641 DESCRIPTION 642 "Size of buffer in octets of.MPLS data." 643 SYNTAX INTEGER (0..'7FFFFFFF'h) 645 -- Top level components of this MIB. 647 -- tables, scalars 648 mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } 649 -- traps 650 mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } 651 -- conformance 652 mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 } 654 -- MPLS Interface Configuration Table. 656 mplsInterfaceConfTable OBJECT-TYPE 657 SYNTAX SEQUENCE OF MplsInterfaceConfEntry 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "This table specifies per-interface MPLS capability 662 and associated information." 663 ::= { mplsLsrObjects 1 } 665 mplsInterfaceConfEntry OBJECT-TYPE 666 SYNTAX MplsInterfaceConfEntry 667 MAX-ACCESS not-accessible 668 STATUS current 669 DESCRIPTION 670 "An entry in this table is created by an LSR for 671 every interface capable of supporting MPLS." 672 INDEX { mplsInterfaceConfIndex } 673 ::= { mplsInterfaceConfTable 1 } 675 MplsInterfaceConfEntry ::= SEQUENCE { 676 mplsInterfaceConfIndex InterfaceIndexOrZero, 677 mplsInterfaceLabelMinIn MplsLabel, 678 mplsInterfaceLabelMaxIn MplsLabel, 679 mplsInterfaceLabelMinOut MplsLabel, 680 mplsInterfaceLabelMaxOut MplsLabel, 681 mplsInterfaceTotalBandwidth BitRate, 682 mplsInterfaceAvailableBandwidth BitRate, 683 mplsInterfaceTotalBuffer BufferSize, 684 mplsInterfaceAvailableBuffer BufferSize, 685 mplsInterfaceIsGlobalLabelSpace TruthValue, 686 mplsInterfaceAdminStatus INTEGER, 687 mplsInterfaceOperStatus INTEGER 688 } 690 mplsInterfaceConfIndex OBJECT-TYPE 691 SYNTAX InterfaceIndexOrZero 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "This is a unique index for an entry in the 696 MplsInterfaceConfTable. A non-zero index for an 697 entry indicates the ifIndex for the corresponding 698 interface entry in of the MPLS-layer in the ifTable. 699 Note that the global label space may apply to 700 several interfaces, and therefore the configuration 701 of the global label space interface parameters will 702 apply to all of the interfaces that are 703 participating in the global label space." 704 REFERENCE 705 "RFC 2233 - The Interfaces Group MIB using SMIv2, 706 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 707 ::= { mplsInterfaceConfEntry 1 } 709 mplsInterfaceLabelMinIn OBJECT-TYPE 710 SYNTAX MplsLabel 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "This is the minimum value of an MPLS label that this 715 LSR is willing to receive on this interface." 716 ::= { mplsInterfaceConfEntry 2 } 718 mplsInterfaceLabelMaxIn OBJECT-TYPE 719 SYNTAX MplsLabel 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "This is the maximum value of an MPLS label that this 724 LSR is willing to receive on this interface." 725 ::= { mplsInterfaceConfEntry 3 } 727 mplsInterfaceLabelMinOut OBJECT-TYPE 728 SYNTAX MplsLabel 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "This is the minimum value of an MPLS label that this 733 LSR is willing to send on this interface." 734 ::= { mplsInterfaceConfEntry 4 } 736 mplsInterfaceLabelMaxOut OBJECT-TYPE 737 SYNTAX MplsLabel 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "This is the maximum value of an MPLS label that this 742 LSR is willing to send on this interface." 743 ::= { mplsInterfaceConfEntry 5 } 745 mplsInterfaceTotalBandwidth OBJECT-TYPE 746 SYNTAX BitRate 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "This value indicates the total amount of usable 751 bandwidth on this interface and is specified in 752 kilobytes per second (Kbps/sec)." 753 ::= { mplsInterfaceConfEntry 6 } 755 mplsInterfaceAvailableBandwidth OBJECT-TYPE 756 SYNTAX BitRate 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "This value indicates the total amount of available 761 bandwidth available on this interface and is 762 specified in kilobytes per second (Kbps/sec). This 763 value is calculated as the difference between the 764 amount of bandwidth currently in use and that 765 specified in mplsInterfaceTotalBandwidth." 766 ::= { mplsInterfaceConfEntry 7 } 768 mplsInterfaceTotalBuffer OBJECT-TYPE 769 SYNTAX BufferSize 770 MAX-ACCESS read-only 771 STATUS current 772 DESCRIPTION 773 "This value indicates the total amount of buffer 774 space allocated for this interface." 775 ::= { mplsInterfaceConfEntry 8 } 777 mplsInterfaceAvailableBuffer OBJECT-TYPE 778 SYNTAX BufferSize 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "This value reflects the total amount of buffer space 783 available on this interface." 784 ::= { mplsInterfaceConfEntry 9 } 786 mplsInterfaceIsGlobalLabelSpace OBJECT-TYPE 787 SYNTAX TruthValue 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "This value indicates whether or not this interface 792 participates in the global label space. If this 793 interface participates in the platform-specific 794 label space, then this value will be set to false." 795 ::= { mplsInterfaceConfEntry 10 } 797 mplsInterfaceAdminStatus OBJECT-TYPE 798 SYNTAX INTEGER { 799 up(1), -- enable MPLS on this interface 800 down(2), -- disable MPLS on this interface 801 testing(3) -- in some test mode 802 } 803 MAX-ACCESS read-write 804 STATUS current 805 DESCRIPTION 806 "This variable indicates the administrator's intent 807 as to whether MPLS should be enabled, disabled, or 808 running in some diagnostic testing mode on this 809 interface." 810 DEFVAL { down } 811 ::= { mplsInterfaceConfEntry 11 } 813 mplsInterfaceOperStatus OBJECT-TYPE 814 SYNTAX INTEGER { 815 up(1), -- ready to pass packets 816 down(2), 817 testing(3), -- in some test mode 818 unknown(4), -- status cannot be determined for some 819 -- reason 820 dormant(5), 821 notPresent(6), -- some component is missing 822 lowerLayerDown(7) 823 -- down due to the state of 824 -- lower layer interfaces 825 } 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "This value reflects the actual or operational status 830 of MPLS on this interface." 831 ::= { mplsInterfaceConfEntry 12 } 833 -- End of mplsInterfaceConfTable 835 -- MPLS Interface Performance Table. 837 mplsInterfacePerfTable OBJECT-TYPE 838 SYNTAX SEQUENCE OF MplsInterfacePerfEntry 839 MAX-ACCESS not-accessible 840 STATUS current 841 DESCRIPTION 842 "This table provides MPLS performance information on 843 a per-interface basis." 844 ::= { mplsLsrObjects 2 } 846 mplsInterfacePerfEntry OBJECT-TYPE 847 SYNTAX MplsInterfacePerfEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "An entry in this table is created by the LSR for 852 every interface capable of supporting MPLS. Its is 853 an extension to the mplsInterfaceConfEntry table." 854 AUGMENTS { mplsInterfaceConfEntry } 855 ::= { mplsInterfacePerfTable 1 } 857 MplsInterfacePerfEntry ::= SEQUENCE { 858 -- incoming direction 859 mplsInterfaceInLabelsUsed Gauge32, 860 mplsInterfaceInPackets Counter32, 861 mplsInterfaceInDiscards Counter32, 862 mplsInterfaceFailedLabelLookup Counter32, 864 -- outgoing direction 865 mplsInterfaceOutLabelsUsed Gauge32, 866 mplsInterfaceOutPackets Counter32, 867 mplsInterfaceOutDiscards Counter32, 868 mplsInterfaceOutFragments Counter32 869 } 871 mplsInterfaceInLabelsUsed OBJECT-TYPE 872 SYNTAX Gauge32 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "This value indicates the specific number of labels 877 that are in use at this point in time on this 878 interface in the incoming direction." 879 ::= { mplsInterfacePerfEntry 1 } 881 mplsInterfaceInPackets OBJECT-TYPE 882 SYNTAX Counter32 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "This variable reflects the number of labeled packets 887 that have been received on this interface." 888 ::= { mplsInterfacePerfEntry 2 } 890 mplsInterfaceInDiscards OBJECT-TYPE 891 SYNTAX Counter32 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The number of inbound labeled packets, which were 896 chosen to be discarded even though no errors had 897 been detected to prevent their being transmitted. 898 One possible reason for discarding such a labeled 899 packet could be to free up buffer space." 900 ::= { mplsInterfacePerfEntry 3 } 902 mplsInterfaceFailedLabelLookup OBJECT-TYPE 903 SYNTAX Counter32 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "This value indicates the number of labeled packets 908 that have been received on this interface and were 909 discarded because there were no matching entries 910 found for them in mplsInSegmentTable." 911 ::= { mplsInterfacePerfEntry 4 } 913 mplsInterfaceOutLabelsUsed OBJECT-TYPE 914 SYNTAX Gauge32 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "Indicates the number of top-most labels in the 919 outgoing label stacks that are in use at this point 920 in time on this interface." 922 ::= { mplsInterfacePerfEntry 5 } 924 mplsInterfaceOutPackets OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "This variable contains the number of labeled packets 930 that have been transmitted on this interface." 931 ::= { mplsInterfacePerfEntry 6 } 933 mplsInterfaceOutDiscards OBJECT-TYPE 934 SYNTAX Counter32 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "The number of outbound labeled packets, which were 939 chosen to be discarded even though no errors had 940 been detected to prevent their being transmitted. 941 One possible reason for discarding such a labeled 942 packet could be to free up buffer space." 943 ::= { mplsInterfacePerfEntry 7 } 945 mplsInterfaceOutFragments OBJECT-TYPE 946 SYNTAX Counter32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "This variable indicates the number of outgoing MPLS 951 packets that were fragmented before transmission on 952 this interface." 953 ::= { mplsInterfacePerfEntry 8 } 955 -- End of mplsInterfacePerfTable 957 -- In-segment table. 959 mplsInSegmentTable OBJECT-TYPE 960 SYNTAX SEQUENCE OF MplsInSegmentEntry 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION 964 "This table contains a collection of incoming 965 segments to an LSR." 966 ::= { mplsLsrObjects 3 } 968 mplsInSegmentEntry OBJECT-TYPE 969 SYNTAX MplsInSegmentEntry 970 MAX-ACCESS not-accessible 971 STATUS current 972 DESCRIPTION 973 "An entry in this table represents one incoming 974 segment. An entry can be created by a network 975 administrator or by an SNMP agent as instructed by 976 CR-LDP or RSVP. The creator of the entry is denoted 977 by mplsInSegmentOwner. An entry in this table is 978 indexed by the ifIndex of the incoming interface and 979 the (top) label. Note that some segments are 980 associated with a tunnel, so the traffic parameters 981 of these rows are supported as read-only objects and 982 their modification can be done only via the tunnel 983 table, mplsTunnelTable." 984 REFERENCE 985 "MPLS Traffic Engineering Management Information Base 986 Using SMIv2, Srinivasan, Viswanathan and Nadeau, 987 draft-ietf-mpls-te-mib-02.txt, February 2000." 988 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 989 ::= { mplsInSegmentTable 1 } 991 MplsInSegmentEntry ::= SEQUENCE { 992 mplsInSegmentIfIndex InterfaceIndex, 993 mplsInSegmentLabel MplsLabel, 994 mplsInSegmentNPop Integer32, 995 mplsInSegmentAddrFamily MplsLsrIANAAddrFamily, 996 mplsInSegmentXCIndex Integer32, 997 mplsInSegmentTSpecIndex Unsigned32, 998 mplsInSegmentOwner INTEGER, 999 mplsInSegmentAdminStatus INTEGER, 1000 mplsInSegmentOperStatus INTEGER, 1001 mplsInSegmentRowStatus RowStatus 1002 } 1004 mplsInSegmentIfIndex OBJECT-TYPE 1005 SYNTAX InterfaceIndexOrZero 1006 MAX-ACCESS read-create 1007 STATUS current 1008 DESCRIPTION 1009 "This is a unique index for an entry in the 1010 MplsInSegmentTable. This value represents the 1011 interface index for the incoming MPLS interface. A 1012 value of zero represents an incoming label from the 1013 per-platform label space. In this case, the 1014 mplsInSegmentLabel is interpreted to be an MPLS-type 1015 label." 1016 ::= { mplsInSegmentEntry 1 } 1018 mplsInSegmentLabel OBJECT-TYPE 1019 SYNTAX MplsLabel 1020 MAX-ACCESS read-create 1021 STATUS current 1022 DESCRIPTION 1023 "The incoming label for this segment." 1024 ::= { mplsInSegmentEntry 2 } 1026 mplsInSegmentNPop OBJECT-TYPE 1027 SYNTAX Unsigned32(1..4294967295) 1028 MAX-ACCESS read-create 1029 STATUS current 1030 DESCRIPTION 1031 "The number of labels to pop from the incoming 1032 packet. Normally only the top label is popped from 1033 the packet and used for all switching decisions for 1034 that packet." 1035 DEFVAL { 1 } 1036 ::= { mplsInSegmentEntry 3 } 1038 mplsInSegmentAddrFamily OBJECT-TYPE 1039 SYNTAX MplsLsrIANAAddrFamily 1040 MAX-ACCESS read-create 1041 STATUS current 1042 DESCRIPTION 1043 "The IANA address family of the incoming packet. A 1044 value of zero indicates that the family type is 1045 either unknown or undefined. This latter case is 1046 possible for example, when packet streams of 1047 different types are merged in a multipoint-to-point 1048 connection." 1049 REFERENCE 1050 "RFC 1700 - Assigned Numbers, Reynolds and Postel, 1051 October 1994." 1052 DEFVAL { 0 } 1053 ::= { mplsInSegmentEntry 4 } 1055 mplsInSegmentXCIndex OBJECT-TYPE 1056 SYNTAX Integer32 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "The index into mplsXCTable is used to identify which 1061 cross-connect entry this segment is part of. Note 1062 that a value of zero indicates that it is not being 1063 referred to by any cross-connect entry." 1064 DEFVAL { 0 } 1065 ::= { mplsInSegmentEntry 5 } 1067 mplsInSegmentTSpecIndex OBJECT-TYPE 1068 SYNTAX Unsigned32 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION 1072 "This variable represents a pointer into the 1073 mplsTSpecTable and indicates the TSpec which is to 1074 be assigned to this segment. A value of zero 1075 indicates best-effort treatment. Two or more 1076 segments can indicate resource sharing by pointing 1077 to the same entry in mplsTSpecTable." 1078 DEFVAL { 0 } 1079 ::= { mplsInSegmentEntry 6 } 1081 mplsInSegmentOwner OBJECT-TYPE 1082 SYNTAX INTEGER { 1083 snmp(1), 1084 crldp(2), 1085 rsvp(3), 1086 policyAgent(4), 1087 other(5) 1088 } 1089 MAX-ACCESS read-create 1090 STATUS current 1091 DESCRIPTION 1092 "Denotes the entity that created and is responsible 1093 for managing this segment." 1094 ::= { mplsInSegmentEntry 7 } 1096 mplsInSegmentAdminStatus OBJECT-TYPE 1097 SYNTAX INTEGER { 1098 up(1), -- ready to pass packets 1099 down(2), 1100 testing(3) -- in some test mode 1101 } 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "This value is used to represent the manager�s 1106 desired operational status of this segment." 1107 ::= { mplsInSegmentEntry 8 } 1109 mplsInSegmentOperStatus OBJECT-TYPE 1110 SYNTAX INTEGER { 1111 up(1), -- ready to pass packets 1112 down(2), 1113 testing(3), -- in some test mode 1114 unknown(4), -- status cannot be determined for 1115 -- some reason 1116 domant(5), 1117 notPresent(6), -- some component is missing 1118 lowerLayerDown(7) 1119 -- down due to the state of 1120 -- lower layer interfaces 1122 } 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "This value represents the actual operational status 1127 of this segment." 1128 ::= { mplsInSegmentEntry 9 } 1130 mplsInSegmentRowStatus OBJECT-TYPE 1131 SYNTAX RowStatus 1132 MAX-ACCESS read-create 1133 STATUS current 1134 DESCRIPTION 1135 "This variable is used to create, modify, and/or 1136 delete a row in this table." 1137 ::= { mplsInSegmentEntry 10 } 1139 -- End of mplsInSegmentTable 1141 -- In-segment performance table. 1143 mplsInSegmentPerfTable OBJECT-TYPE 1144 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 1145 MAX-ACCESS not-accessible 1146 STATUS current 1147 DESCRIPTION 1148 "This table contains statistical information for 1149 incoming MPLS segments to an LSR." 1150 ::= { mplsLsrObjects 4 } 1152 mplsInSegmentPerfEntry OBJECT-TYPE 1153 SYNTAX MplsInSegmentPerfEntry 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "An entry in this table contains statistical 1158 information about one incoming segment which was 1159 configured in the mplsInSegmentTable." 1160 AUGMENTS { mplsInSegmentEntry } 1161 ::= { mplsInSegmentPerfTable 1 } 1163 MplsInSegmentPerfEntry ::= SEQUENCE { 1164 mplsInSegmentOctets Counter32, 1165 mplsInSegmentPackets Counter32, 1166 mplsInSegmentErrors Counter32, 1167 mplsInSegmentDiscards Counter32, 1169 -- high capacity counter 1170 mplsInSegmentHCOctets Counter64 1172 } 1174 mplsInSegmentOctets OBJECT-TYPE 1175 SYNTAX Counter32 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "This value represents the total number of octets 1180 received by this segment." 1181 ::= { mplsInSegmentPerfEntry 1 } 1183 mplsInSegmentPackets OBJECT-TYPE 1184 SYNTAX Counter32 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "Total number of packets received by this segment." 1189 ::= { mplsInSegmentPerfEntry 2 } 1191 mplsInSegmentErrors OBJECT-TYPE 1192 SYNTAX Counter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The number of packets received in error by this 1197 LSR." 1198 ::= { mplsInSegmentPerfEntry 3 } 1200 mplsInSegmentDiscards OBJECT-TYPE 1201 SYNTAX Counter32 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION 1205 "The number of labeled packets received on this in- 1206 segment, which were chosen to be discarded even 1207 though no errors had been detected to prevent their 1208 being transmitted. One possible reason for 1209 discarding such a labeled packet could be to free up 1210 buffer space." 1211 ::= { mplsInSegmentPerfEntry 4 } 1213 mplsInSegmentHCOctets OBJECT-TYPE 1214 SYNTAX Counter32 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "The total number of octets received. This is the 64 1219 bit version of mplsInSegmentOctets." 1220 ::= { mplsInSegmentPerfEntry 5 } 1222 -- End of mplsInSegmentPerfTable. 1224 -- Out-segment table. 1226 mplsOutSegmentIndexNext OBJECT-TYPE 1227 SYNTAX Integer32 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "This object contains the next appropriate value to 1232 be used for mplsOutSegmentIndex when creating 1233 entries in the mplsOutSegmentTable. If the number of 1234 unassigned entries is exhausted, this object will 1235 take on the value of 0. To obtain the 1236 mplsOutSegmentIndex value for a new entry, the 1237 manager must first issue a management protocol 1238 retrieval operation to obtain the current value of 1239 this object. The agent should modify the value to 1240 reflect the next unassigned index after each 1241 retrieval operation. After a manager retrieves a 1242 value the agent will determine through its local 1243 policy when this index value will be made available 1244 for reuse." 1245 ::= { mplsLsrObjects 5 } 1247 mplsOutSegmentTable OBJECT-TYPE 1248 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "This table contains a representation of the outgoing 1253 segments from an LSR." 1254 ::= { mplsLsrObjects 6 } 1256 mplsOutSegmentEntry OBJECT-TYPE 1257 SYNTAX MplsOutSegmentEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "An entry in this table represents one incoming 1262 segment. An entry can be created by a network 1263 administrator or by an SNMP agent as instructed by 1264 CR-LDP or RSVP. The creator of the entry is denoted 1265 by mplsOutSegmentOwner. An entry in this table is 1266 indexed by the ifIndex of the incoming interface and 1267 the (top) label. Note that since it is possible 1268 that some segments are associated with a tunnel, 1269 traffic parameters of these rows are supported as 1270 read-only objects and their modification can be done 1271 only via the tunnel table, mplsTunnelTable." 1272 REFERENCE 1273 "MPLS Traffic Engineering Management Information Base 1274 Using SMIv2, Srinivasan, Viswanathan and Nadeau, 1275 draft-ietf-mpls-te-mib-02.txt, February 2000." 1277 INDEX { mplsOutSegmentIndex } 1278 ::= { mplsOutSegmentTable 1 } 1280 MplsOutSegmentEntry ::= SEQUENCE { 1281 mplsOutSegmentIndex Integer32, 1282 mplsOutSegmentIfIndex InterfaceIndex, 1283 mplsOutSegmentPushTopLabel TruthValue, 1284 mplsOutSegmentTopLabel MplsLabel, 1285 mplsOutSegmentNextHopIpAddrType INTEGER, 1286 mplsOutSegmentNextHopIpv4Addr IpAddress, 1287 mplsOutSegmentNextHopIpv6Addr Ipv6Address, 1288 mplsOutSegmentXCIndex Integer32, 1289 mplsOutSegmentTSpecIndex Unsigned32, 1290 mplsOutSegmentOwner INTEGER, 1291 mplsOutSegmentAdminStatus INTEGER, 1292 mplsOutSegmentOperStatus INTEGER, 1293 mplsOutSegmentRowStatus RowStatus 1294 } 1296 mplsOutSegmentIndex OBJECT-TYPE 1297 SYNTAX Integer32 1298 MAX-ACCESS read-create 1299 STATUS current 1300 DESCRIPTION 1301 "This value contains a unique index for this row. 1302 While a value of 0 is not valid as an index for this 1303 row it can be supplied as a valid value to index 1304 mplsXCTable to access entries for which no out- 1305 segment has been configured." 1306 ::= { mplsOutSegmentEntry 1 } 1308 mplsOutSegmentIfIndex OBJECT-TYPE 1309 SYNTAX InterfaceIndex 1310 MAX-ACCESS read-create 1311 STATUS current 1312 DESCRIPTION 1313 "This value contains the interface index of the 1314 outgoing interface." 1315 ::= { mplsOutSegmentEntry 2 } 1317 mplsOutSegmentPushTopLabel OBJECT-TYPE 1318 SYNTAX TruthValue 1319 MAX-ACCESS read-create 1320 STATUS current 1321 DESCRIPTION 1322 "This value indicates whether or not a top label 1323 should be pushed onto the outgoing packet's label 1324 stack. The value of this variable must be set to 1325 true if the outgoing interface is ATM, which does 1326 not support pop-and-go, or if it is a tunnel 1327 origination. Note that it is considered an error in 1328 the case that mplsOutSegmentPushTopLabel is set to 1329 false, but the cross-connect entry which refers to 1330 this out-segment has a non-zero mplsLabelStackIndex. 1331 The LSR should ensure that this situation cannot 1332 happen " 1333 ::= { mplsOutSegmentEntry 3 } 1335 mplsOutSegmentTopLabel OBJECT-TYPE 1336 SYNTAX MplsLabel 1337 MAX-ACCESS read-create 1338 STATUS current 1339 DESCRIPTION 1340 "If mplsOutSegmentPushTopLabel is true then this is 1341 the label that should be pushed onto the outgoing 1342 packet's label stack. Note that the contents of the 1343 label field can be interpreted in an outgoing 1344 interface specific fashion. For example, the label 1345 carried in the MPLS shim header is 20 bits wide and 1346 the top 12 bits must be zero. The Frame Relay label 1347 is 24 bits wide and the top 8 bits must be zero. 1348 For ATM interfaces the lowermost 16 bits are 1349 interpreted as the VCI, the next 8 bits as the VPI 1350 and the remaining bits must be zero." 1351 ::= { mplsOutSegmentEntry 4 } 1353 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1354 SYNTAX INTEGER { none (1), ipV4 (2), ipV6 (3) } 1355 MAX-ACCESS read-create 1356 STATUS current 1357 DESCRIPTION 1358 "Indicates whether the next hop address is IPv4 or 1359 IPv6. Note that a value of none (1) is valid only 1360 when the outgoing interface is of type point-to- 1361 point." 1362 DEFVAL { none } 1363 ::= { mplsOutSegmentEntry 5 } 1365 mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1366 SYNTAX IpAddress 1367 MAX-ACCESS read-create 1368 STATUS current 1369 DESCRIPTION 1370 "IPv4 Address of the next hop. Its value is 1371 significant only when 1372 mplsOutSegmentNextHopIpAddrType is ipV4 (2), 1373 otherwise it should return a value of 0." 1374 ::= { mplsOutSegmentEntry 6 } 1376 mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1377 SYNTAX Ipv6Address 1378 MAX-ACCESS read-create 1379 STATUS current 1380 DESCRIPTION 1381 "IPv6 address of the next hop. Its value is 1382 significant only when 1383 mplsOutSegmentNextHopIpAddrType is ipV6 (3), 1384 otherwise it should return a value of 0." 1385 ::= { mplsOutSegmentEntry 7 } 1387 mplsOutSegmentXCIndex OBJECT-TYPE 1388 SYNTAX Integer32 1389 MAX-ACCESS read-create 1390 STATUS current 1391 DESCRIPTION 1392 "Index into mplsXCTable which identifies which cross- 1393 connect entry this segment is part of. A value of 1394 zero indicates that this entry is not referred to by 1395 any cross-connect entry." 1396 DEFVAL { 0 } 1397 ::= { mplsOutSegmentEntry 8 } 1399 mplsOutSegmentTSpecIndex OBJECT-TYPE 1400 SYNTAX Unsigned32 1401 MAX-ACCESS read-create 1402 STATUS current 1403 DESCRIPTION 1404 "A pointer into the mplsTSpecTable indicating the 1405 TSpec to be assigned for this segment. A value of 1406 zero indicates best-effort treatment. Two or more 1407 segments can indicate resource sharing by pointing 1408 to the same entry in mplsTSpecTable." 1409 DEFVAL { 0 } 1410 ::= { mplsOutSegmentEntry 9 } 1412 mplsOutSegmentOwner OBJECT-TYPE 1413 SYNTAX INTEGER { 1414 snmp(1), 1415 crldp(2), 1416 rsvp(3), 1417 policyAgent(4), 1418 other(5) 1420 } 1421 MAX-ACCESS read-create 1422 STATUS current 1423 DESCRIPTION 1424 "Denotes the entity which created and is responsible 1425 for managing this segment." 1426 ::= { mplsOutSegmentEntry 10 } 1428 mplsOutSegmentAdminStatus OBJECT-TYPE 1429 SYNTAX INTEGER { 1430 up(1), -- ready to pass packets 1431 down(2), 1432 testing(3) -- in some test mode 1433 } 1434 MAX-ACCESS read-create 1435 STATUS current 1436 DESCRIPTION 1437 "The desired operational status of this segment." 1438 ::= { mplsOutSegmentEntry 11 } 1440 mplsOutSegmentOperStatus OBJECT-TYPE 1441 SYNTAX INTEGER { 1442 up(1), -- ready to pass packets 1443 down(2), 1444 testing(3), -- in some test mode 1445 unknown(4), -- status cannot be determined for 1446 -- some reason 1447 dormant(5), 1448 notPresent(6), -- some component is missing 1449 lowerLayerDown(7) 1450 -- down due to the state of 1451 -- lower layer interfaces 1452 } 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "The actual operational status of this segment." 1457 ::= { mplsOutSegmentEntry 12 } 1459 mplsOutSegmentRowStatus OBJECT-TYPE 1460 SYNTAX RowStatus 1461 MAX-ACCESS read-create 1462 STATUS current 1463 DESCRIPTION 1464 "For creating, modifying, and deleting this row." 1465 ::= { mplsOutSegmentEntry 13 } 1467 -- End of mplsOutSegmentTable 1468 -- Out-segment performance table. 1470 mplsOutSegmentPerfTable OBJECT-TYPE 1471 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "This table contains statistical information about 1476 incoming segments to an LSR." 1477 ::= { mplsLsrObjects 7 } 1479 mplsOutSegmentPerfEntry OBJECT-TYPE 1480 SYNTAX MplsOutSegmentPerfEntry 1481 MAX-ACCESS not-accessible 1482 STATUS current 1483 DESCRIPTION 1484 "An entry in this table contains statistical 1485 information about one incoming segment configured in 1486 mplsOutSegmentTable." 1487 AUGMENTS { mplsOutSegmentEntry } 1488 ::= { mplsOutSegmentPerfTable 1 } 1490 MplsOutSegmentPerfEntry ::= SEQUENCE { 1491 mplsOutSegmentOctets Counter32, 1492 mplsOutSegmentPackets Counter32, 1493 mplsOutSegmentErrors Counter32, 1494 mplsOutSegmentDiscards Counter32, 1496 -- HC counter 1497 mplsOutSegmentHCOctets Counter64 1498 } 1500 mplsOutSegmentOctets OBJECT-TYPE 1501 SYNTAX Counter32 1502 MAX-ACCESS read-only 1503 STATUS current 1504 DESCRIPTION 1505 "This value contains the total number of octets sent 1506 on this segment." 1507 ::= { mplsOutSegmentPerfEntry 1 } 1509 mplsOutSegmentPackets OBJECT-TYPE 1510 SYNTAX Counter32 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "This value contains the total number of packets sent 1515 on this segment." 1516 ::= { mplsOutSegmentPerfEntry 2 } 1518 mplsOutSegmentErrors OBJECT-TYPE 1519 SYNTAX Counter32 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "Number of packets that could not be sent due to 1524 errors." 1525 ::= { mplsOutSegmentPerfEntry 3 } 1527 mplsOutSegmentDiscards OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "The number of labeled packets received on this out- 1533 segment, which were chosen to be discarded even 1534 though no errors had been detected to prevent their 1535 being transmitted. One possible reason for 1536 discarding such a labeled packet could be to free up 1537 buffer space." 1538 ::= { mplsOutSegmentPerfEntry 4 } 1540 mplsOutSegmentHCOctets OBJECT-TYPE 1541 SYNTAX Counter64 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "Total number of octets sent. This is the 64 bit 1546 version of mplsOutSegmentOctets." 1547 ::= { mplsOutSegmentPerfEntry 5 } 1549 -- End of mplsOutSegmentPerfTable. 1551 -- Cross-connect table. 1553 mplsXCIndexNext OBJECT-TYPE 1554 SYNTAX Integer32 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "This object contains an appropriate value to be used 1559 for mplsXCIndex when creating entries in the 1560 mplsXCTable. The value 0 indicates that no 1561 unassigned entries are available. To obtain the 1562 value of mplsXCIndex for a new entry in the 1563 mplsXCTable, the manager issues a management 1564 protocol retrieval operation to obtain the current 1565 value of mplsXCIndex. After each retrieval 1566 operation, the agent should modify the value to 1567 reflect the next unassigned index. After a manager 1568 retrieves a value the agent will determine through 1569 its local policy when this index value will be made 1570 available for reuse." 1571 ::= { mplsLsrObjects 8 } 1573 mplsXCTable OBJECT-TYPE 1574 SYNTAX SEQUENCE OF MplsXCEntry 1575 MAX-ACCESS not-accessible 1576 STATUS current 1577 DESCRIPTION 1578 "This table specifies information for switching 1579 between LSP segments. It supports point-to-point, 1580 point-to-multipoint and multipoint-to-point 1581 connections. mplsLabelStackTable specifies the 1582 label stack information for a cross-connect LSR and 1583 is referred to from mplsXCTable." 1584 ::= { mplsLsrObjects 9 } 1586 mplsXCEntry OBJECT-TYPE 1587 SYNTAX MplsXCEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "A row in this table represents one cross-connect 1592 entry. The following objects index it: 1594 - cross-connect index mplsXCIndex that uniquely 1595 identifies a group of cross-connect entries 1596 - interface index of the in-segment, 1597 mplsInSegmentIfIndex 1598 - incoming label(s), mplsInSegmentLabel 1599 - out-segment index, mplsOutSegmentIndex 1601 Originating LSPs: 1602 These are represented by using the special 1603 combination of values mplsInSegmentIfIndex=0 and 1604 mplsInSegmentLabel=0 as indexes. In this case the 1605 mplsOutSegmentIndex MUST be non-zero. 1607 Terminating LSPs: 1608 These are represented by using the special value 1609 mplsOutSegmentIndex=0 as index. 1611 Special labels: 1612 Entries indexed by reserved MPLS label values 0 1613 through 15 imply terminating LSPs and MUST have 1614 mplsOutSegmentIndex=0. 1616 An entry can be created by a network administrator or 1617 by an SNMP agent as instructed by CR-LDP or RSVP." 1618 INDEX { mplsXCIndex, mplsInSegmentIfIndex, 1619 mplsInSegmentLabel, mplsOutSegmentIndex } 1620 ::= { mplsXCTable 1 } 1622 MplsXCEntry ::= SEQUENCE { 1623 mplsXCIndex INTEGER, 1624 mplsXCLspId MplsLSPID, 1625 mplsXCLabelStackIndex Integer32, 1626 mplsXCCOS Integer32, 1627 mplsXCIsPersistent TruthValue, 1628 mplsXCAdminStatus INTEGER, 1629 mplsXCOperStatus INTEGER, 1630 mplsXCRowStatus RowStatus 1631 } 1633 mplsXCIndex OBJECT-TYPE 1634 SYNTAX INTEGER (0..4294967295) 1635 MAX-ACCESS read-create 1636 STATUS current 1637 DESCRIPTION 1638 "Primary index for the row identifying a group of 1639 cross-connect segments." 1640 ::= { mplsXCEntry 1 } 1642 mplsXCLspId OBJECT-TYPE 1643 SYNTAX MplsLSPID 1644 MAX-ACCESS read-create 1645 STATUS current 1646 DESCRIPTION 1647 "This value identifies the label switched path that 1648 this cross-connect entry belongs to." 1649 ::= { mplsXCEntry 2 } 1651 mplsXCLabelStackIndex OBJECT-TYPE 1652 SYNTAX Integer32 1653 MAX-ACCESS read-create 1654 STATUS current 1655 DESCRIPTION 1656 "Primary index into mplsLabelStackTable identifying a 1657 stack of labels to be pushed beneath the top label. 1658 Note that the top label identified by the out- 1659 segment ensures that all the components of a 1660 multipoint-to-point connection have the same 1661 outgoing label. A value of 0 indicates that no 1662 labels are to be stacked beneath the top label." 1663 ::= { mplsXCEntry 3 } 1665 mplsXCCOS OBJECT-TYPE 1666 SYNTAX Integer32 1667 MAX-ACCESS read-create 1668 STATUS current 1669 DESCRIPTION 1670 "This value is used to override the incoming COS 1671 field for a cross-connect. It may also be used as a 1672 value to assign to outgoing packets for an outgoing 1673 segment of a tunnel. Note that packet treatment at 1674 this LSR is determined by the incoming COS value and 1675 the new COS value only impacts packet treatment at a 1676 downstream LSR." 1677 ::= { mplsXCEntry 4 } 1679 mplsXCIsPersistent OBJECT-TYPE 1680 SYNTAX TruthValue 1681 MAX-ACCESS read-create 1682 STATUS current 1683 DESCRIPTION 1684 "Denotes whether or not this cross-connect entry and 1685 associated in- and out-segments should be restored 1686 automatically after failures." 1687 DEFVAL { false } 1688 ::= { mplsXCEntry 5 } 1690 mplsXCAdminStatus OBJECT-TYPE 1691 SYNTAX INTEGER { 1692 up(1), -- ready to pass packets 1693 down(2), 1694 testing(3) -- in some test mode 1695 } 1696 MAX-ACCESS read-create 1697 STATUS current 1698 DESCRIPTION 1699 "The desired operational status of this segment." 1700 ::= { mplsXCEntry 6 } 1702 mplsXCOperStatus OBJECT-TYPE 1703 SYNTAX INTEGER { 1704 up(1), -- ready to pass packets 1705 down(2), 1706 testing(3), -- in some test mode 1707 unknown(4), -- status cannot be determined for 1708 -- some reason 1709 dormant(5), 1710 notPresent(6), -- some component is missing 1711 lowerLayerDown(7) 1712 -- down due to the state of 1713 -- lower layer interfaces 1714 } 1715 MAX-ACCESS read-only 1716 STATUS current 1717 DESCRIPTION 1718 "The actual operational status of this cross- 1719 connect." 1720 ::= { mplsXCEntry 7 } 1722 mplsXCRowStatus OBJECT-TYPE 1723 SYNTAX RowStatus 1724 MAX-ACCESS read-create 1725 STATUS current 1726 DESCRIPTION 1727 "For creating, modifying, and deleting this row." 1728 ::= { mplsXCEntry 8 } 1730 -- End of mplsXCTable 1732 -- Label stack table. 1733 mplsMaxLabelStackDepth OBJECT-TYPE 1734 SYNTAX Integer32 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION 1738 "The maximum stack depth supported by this LSR." 1739 ::= { mplsLsrObjects 10 } 1741 mplsLabelStackIndexNext OBJECT-TYPE 1742 SYNTAX Integer32 1743 MAX-ACCESS read-only 1744 STATUS current 1745 DESCRIPTION 1746 "This object contains an appropriate value to be used 1747 for mplsLabelStackIndex when creating entries in the 1748 mplsLabelStackTable. The value 0 indicates that no 1749 unassigned entries are available. To obtain an 1750 mplsLabelStackIndex value for a new entry, the 1751 manager issues a management protocol retrieval 1752 operation to obtain the current value of this 1753 object. After each retrieval operation, the agent 1754 should modify the value to reflect the next 1755 unassigned index. After a manager retrieves a value 1756 the agent will determine through its local policy 1757 when this index value will be made available for 1758 reuse." 1759 ::= { mplsLsrObjects 11 } 1761 mplsLabelStackTable OBJECT-TYPE 1762 SYNTAX SEQUENCE OF MplsLabelStackEntry 1763 MAX-ACCESS not-accessible 1764 STATUS current 1765 DESCRIPTION 1766 "This table specifies the label stack to be pushed 1767 onto a packet, beneath the top label. Entries into 1768 this table are referred to from mplsXCTable." 1769 ::= { mplsLsrObjects 12 } 1771 mplsLabelStackEntry OBJECT-TYPE 1772 SYNTAX MplsLabelStackEntry 1773 MAX-ACCESS not-accessible 1774 STATUS current 1775 DESCRIPTION 1776 "An entry in this table represents one label which is 1777 to be pushed onto an outgoing packet, beneath the 1778 top label. An entry can be created by a network 1779 administrator or by an SNMP agent as instructed by 1780 CR-LDP or RSVP." 1781 INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex } 1782 ::= { mplsLabelStackTable 1 } 1784 MplsLabelStackEntry ::= SEQUENCE { 1785 mplsLabelStackIndex Integer32, 1786 mplsLabelStackLabelIndex Integer32, 1787 mplsLabelStackLabel MplsLabel, 1788 mplsLabelStackRowStatus RowStatus 1789 } 1791 mplsLabelStackIndex OBJECT-TYPE 1792 SYNTAX Integer32 1793 MAX-ACCESS read-create 1794 STATUS current 1795 DESCRIPTION 1796 "Primary index for this row identifying a stack of 1797 labels to be pushed on an outgoing packet, beneath 1798 the top label." 1799 ::= { mplsLabelStackEntry 1 } 1801 mplsLabelStackLabelIndex OBJECT-TYPE 1802 SYNTAX Integer32 1803 MAX-ACCESS not-accessible 1804 STATUS current 1805 DESCRIPTION 1806 "Secondary index for this row identifying one label 1807 of the stack. Note that an entry with a smaller 1808 mplsLabelStackLabelIndex would refer to a label 1809 higher up the label stack and would be popped before 1810 a label represented by a higher 1811 mplsLabelStackLabelIndex at a downstream LSR." 1812 ::= { mplsLabelStackEntry 2 } 1814 mplsLabelStackLabel OBJECT-TYPE 1815 SYNTAX MplsLabel 1816 MAX-ACCESS read-create 1817 STATUS current 1818 DESCRIPTION 1819 "The label to pushed." 1820 ::= { mplsLabelStackEntry 3 } 1822 mplsLabelStackRowStatus OBJECT-TYPE 1823 SYNTAX RowStatus 1824 MAX-ACCESS read-create 1825 STATUS current 1826 DESCRIPTION 1827 "For creating, modifying, and deleting this row." 1828 ::= { mplsLabelStackEntry 4 } 1830 -- End of mplsLabelStackTable 1832 -- TSpec table. 1834 mplsTSpecIndexNext OBJECT-TYPE 1835 SYNTAX Integer32 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "This object contains an appropriate value which will 1840 be used for mplsTSpecIndex when creating entries in 1841 the mplsTSpecTable. The value 0 indicates that no 1842 unassigned entries are available. To obtain the 1843 mplsTSpecIndex value for a new entry, the manager 1844 issues a management protocol retrieval operation to 1845 obtain the current value of this object. After each 1846 retrieval operation, the agent should modify the 1847 value to reflect the next unassigned index. After a 1848 manager retrieves a value the agent will determine 1849 through its local policy when this index value will 1850 be made available for reuse." 1851 ::= { mplsLsrObjects 13 } 1853 mplsTSpecTable OBJECT-TYPE 1854 SYNTAX SEQUENCE OF MplsTSpecEntry 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "This table specifies the Traffic Specification 1859 (TSpec) objects for in and out-segments." 1860 ::= { mplsLsrObjects 14 } 1862 mplsTSpecEntry OBJECT-TYPE 1863 SYNTAX MplsTSpecEntry 1864 MAX-ACCESS not-accessible 1865 STATUS current 1866 DESCRIPTION 1867 "An entry in this table represents the TSpec objects 1868 for one or more in or out segments. A single entry 1869 can be pointed to by multiple segments indicating 1870 resource sharing." 1871 INDEX { mplsTSpecIndex } 1872 ::= { mplsTSpecTable 1 } 1874 MplsTSpecEntry ::= SEQUENCE { 1875 mplsTSpecIndex Unsigned32, 1876 mplsTSpecDirection INTEGER, 1877 mplsTSpecMaxRate BitRate, 1878 mplsTSpecMeanRate BitRate, 1879 mplsTSpecMaxBurstSize BurstSize, 1880 mplsTSpecRowStatus RowStatus 1881 } 1883 mplsTSpecIndex OBJECT-TYPE 1884 SYNTAX Unsigned32 1885 MAX-ACCESS read-create 1886 STATUS current 1887 DESCRIPTION 1888 "Uniquely identifies this row of the table. Note 1889 that zero represents an invalid index." 1890 ::= { mplsTSpecEntry 1 } 1892 mplsTSpecDirection OBJECT-TYPE 1893 SYNTAX INTEGER { in(1), out(2) } 1894 MAX-ACCESS read-create 1895 STATUS current 1896 DESCRIPTION 1897 "The direction that these objects pertain to. Valid 1898 values specify either incoming or outgoing 1899 directions." 1900 ::= { mplsTSpecEntry 2 } 1902 mplsTSpecMaxRate OBJECT-TYPE 1903 SYNTAX BitRate 1904 UNITS "bits per second" 1905 MAX-ACCESS read-create 1906 STATUS current 1907 DESCRIPTION 1908 "Maximum rate in bits/second." 1909 ::= { mplsTSpecEntry 3 } 1911 mplsTSpecMeanRate OBJECT-TYPE 1912 SYNTAX BitRate 1913 UNITS "bits per second" 1914 MAX-ACCESS read-create 1915 STATUS current 1916 DESCRIPTION 1917 "Mean rate in bits/second." 1918 ::= { mplsTSpecEntry 4 } 1920 mplsTSpecMaxBurstSize OBJECT-TYPE 1921 SYNTAX BurstSize 1922 UNITS "bytes" 1923 MAX-ACCESS read-create 1924 STATUS current 1925 DESCRIPTION 1926 "Maximum burst size in bytes." 1927 ::= { mplsTSpecEntry 5 } 1929 mplsTSpecRowStatus OBJECT-TYPE 1930 SYNTAX RowStatus 1931 MAX-ACCESS read-create 1932 STATUS current 1933 DESCRIPTION 1934 "For creating, modifying, and deleting this row." 1935 ::= { mplsTSpecEntry 6 } 1937 -- End of mplsTSpecTable 1939 -- Notifications. 1941 -- Interface configuration. 1943 mplsInterfaceUp NOTIFICATION-TYPE 1944 OBJECTS { mplsInterfaceConfIndex, 1945 mplsInterfaceAdminStatus, mplsInterfaceOperStatus } 1946 STATUS current 1947 DESCRIPTION 1948 "This notification is generated when a 1949 mplsInterfaceOperStatus object for one of the 1950 entries in mplsInterfaceConfTable is about to leave 1951 the down state and transition into some other state 1952 (but not into the notPresent state). This other 1953 state is indicated by the included value of 1954 mplsInterfaceOperStatus." 1955 ::= { mplsLsrNotifications 1 } 1957 mplsInterfaceDown NOTIFICATION-TYPE 1958 OBJECTS { mplsInterfaceConfIndex, 1959 mplsInterfaceAdminStatus, mplsInterfaceOperStatus } 1960 STATUS current 1961 DESCRIPTION 1962 "This notification is generated when a 1963 mplsInterfaceOperStatus object for one of the 1964 entries in mplsInterfaceConfTable is about to enter 1965 the down state from some other state (but not from 1966 the notPresent state). This other state is 1967 indicated by the included value of 1968 mplsInterfaceOperStatus." 1969 ::= { mplsLsrNotifications 2 } 1971 -- In-segment. 1973 mplsInSegmentUp NOTIFICATION-TYPE 1974 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 1975 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 1976 STATUS current 1977 DESCRIPTION 1978 "This notification is generated when a 1979 mplsInSegmentOperStatus object for one of the 1980 configured in-segments is about to leave the down 1981 state and transition into some other state (but not 1982 into the notPresent state). This other state is 1983 indicated by the included value of 1984 mplsInSegmentOperStatus." 1985 ::= { mplsLsrNotifications 3 } 1987 mplsInSegmentDown NOTIFICATION-TYPE 1988 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 1989 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 1990 STATUS current 1991 DESCRIPTION 1992 "This notification is generated when a 1993 mplsInSegmentOperStatus object for one of the 1994 configured in-segments is about to enter the down 1995 state from some other state (but not from the 1996 notPresent state). This other state is indicated by 1997 the included value of mplsInSegmentOperStatus." 1998 ::= { mplsLsrNotifications 4 } 2000 -- Out-segment. 2002 mplsOutSegmentUp NOTIFICATION-TYPE 2003 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 2004 mplsInSegmentOperStatus } 2005 STATUS current 2006 DESCRIPTION 2007 "This notification is generated when a 2008 mplsOutSegmentOperStatus object for one of the 2009 configured out-segments is about to leave the down 2010 state and transition into some other state (but not 2011 into the notPresent state). This other state is 2012 indicated by the included value of 2013 mplsOutSegmentOperStatus." 2015 ::= { mplsLsrNotifications 5 } 2017 mplsOutSegmentDown NOTIFICATION-TYPE 2018 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 2019 mplsInSegmentOperStatus } 2020 STATUS current 2021 DESCRIPTION 2022 "This notification is generated when a 2023 mplsOutSegmentOperStatus object for one of the 2024 configured out-segments is about to enter the down 2025 state from some other state (but not from the 2026 notPresent state). This other state is indicated by 2027 the included value of mplsOutSegmentOperStatus." 2028 ::= { mplsLsrNotifications 6 } 2030 -- Cross-connect. 2032 mplsXCUp NOTIFICATION-TYPE 2033 OBJECTS { mplsXCIndex, 2034 mplsInSegmentIfIndex, mplsInSegmentLabel, 2035 mplsOutSegmentIndex, 2036 mplsXCAdminStatus, mplsXCOperStatus } 2037 STATUS current 2038 DESCRIPTION 2039 "This notification is generated when a 2040 mplsXCOperStatus object for one of the configured 2041 cross-connect entries is about to leave the down 2042 state and transition into some other state (but not 2043 into the notPresent state). This other state is 2044 indicated by the included value of 2045 mplsXCOperStatus." 2046 ::= { mplsLsrNotifications 7 } 2048 mplsXCDown NOTIFICATION-TYPE 2049 OBJECTS { mplsXCIndex, 2050 mplsInSegmentIfIndex, mplsInSegmentLabel, 2051 mplsOutSegmentIndex, 2052 mplsXCAdminStatus, mplsXCOperStatus } 2053 STATUS current 2054 DESCRIPTION 2055 "This notification is generated when a 2056 mplsXCOperStatus object for one of the configured 2057 cross-connect entries is about to enter the down 2058 state from some other state (but not from the 2059 notPresent state). This other state is indicated by 2060 the included value of mplsXCOperStatus." 2061 ::= { mplsLsrNotifications 8 } 2063 -- End of notifications. 2065 -- Module compliance. 2067 mplsLsrGroups 2068 OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } 2070 mplsLsrCompliances 2071 OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } 2073 mplsLsrModuleCompliance MODULE-COMPLIANCE 2074 STATUS current 2075 DESCRIPTION 2076 "Compliance statement for agents that support the 2077 MPLS LSR MIB." 2078 MODULE -- this module 2080 -- The mandatory groups have to be implemented by all LSRs. 2081 -- However, they may all be supported as read-only objects 2082 -- in the case where manual configuration is unsupported. 2084 MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup, 2085 mplsXCGroup, mplsInterfaceGroup, 2086 mplsPerfGroup } 2088 GROUP mplsHCInterfacePerfGroup 2089 DESCRIPTION 2090 "This group is mandatory for high-speed MPLS 2091 capable interfaces for which the objects 2092 mplsInterfaceInOctets and mplsInterfaceOutOctets 2093 wrap around too quickly." 2095 GROUP mplsHCInSegmentPerfGroup 2096 DESCRIPTION 2097 "This group is mandatory for those in-segment 2098 entries for which the object 2099 mplsInSegmentOutOctets wraps around too 2100 quickly." 2102 GROUP mplsHCOutSegmentPerfGroup 2103 DESCRIPTION 2104 "This group is mandatory for those out-segment 2105 entries for which the object 2106 mplsOutSegmentOctets wraps around too quickly." 2108 GROUP mplsTSpecGroup 2109 DESCRIPTION 2110 "This group is mandatory for those LSRs that 2111 support Int-Serv style resource reservation." 2113 -- Depending on whether the device implements persistent 2114 -- cross-connects or not one of the following two groups 2115 -- is mandatory. 2117 GROUP mplsXCIsPersistentGroup 2118 DESCRIPTION 2119 "This group is mandatory for devices which 2120 support persistent cross-connects. The 2121 following constraints apply: mplsXCIsPersistent 2122 must at least be read-only returning true(2)." 2124 GROUP mplsXCIsNotPersistentGroup 2125 DESCRIPTION 2126 "This group is mandatory for devices which 2127 support non-persistent cross-connects. The 2128 following constraints apply: mplsXCIsPersistent 2129 must at least be read-only returning false(1)." 2131 -- mplsInterfaceConfTable 2133 OBJECT mplsInterfaceAdminStatus 2134 SYNTAX INTEGER { up(1), down(2) } 2135 MIN-ACCESS read-only 2136 DESCRIPTION 2137 "A value of testing(3) need not be supported." 2139 OBJECT mplsInterfaceOperStatus 2140 SYNTAX INTEGER { up(1), down(2) } 2141 MIN-ACCESS read-only 2142 DESCRIPTION 2143 "Only up(1) and down(2) need to be supported." 2145 -- mplsInSegmentTable 2147 OBJECT mplsInSegmentIfIndex 2148 MIN-ACCESS read-only 2149 DESCRIPTION 2150 "Write access is not required." 2152 OBJECT mplsInSegmentLabel 2153 MIN-ACCESS read-only 2154 DESCRIPTION 2155 "Write access is not required." 2157 OBJECT mplsInSegmentXCIndex 2158 MIN-ACCESS read-only 2159 DESCRIPTION 2160 "Write access is not required." 2162 OBJECT mplsInSegmentTSpecIndex 2163 MIN-ACCESS read-only 2164 DESCRIPTION 2165 "Write access is not required." 2167 OBJECT mplsInSegmentNPop 2168 MIN-ACCESS read-only 2169 DESCRIPTION 2170 "Write access if not required. This object 2171 should be set to 1 if it is read-only." 2173 OBJECT mplsInSegmentAddrFamily 2174 SYNTAX INTEGER { other(0) } 2175 MIN-ACCESS read-only 2176 DESCRIPTION 2177 "Write access is not required. A value of 2178 other(0) should be supported." 2180 OBJECT mplsInSegmentAdminStatus 2181 SYNTAX INTEGER { up(1), down(2) } 2182 MIN-ACCESS read-only 2183 DESCRIPTION 2184 "A value of testing(3) need not be supported." 2186 OBJECT mplsInSegmentOperStatus 2187 SYNTAX INTEGER { up(1), down(2) } 2188 MIN-ACCESS read-only 2189 DESCRIPTION 2190 "Only up(1) and down(2) need to be supported." 2192 OBJECT mplsInSegmentRowStatus 2193 SYNTAX INTEGER { active(1), notInService(2), 2194 createAndGo(4), 2195 destroy(6) } 2196 MIN-ACCESS read-only 2197 DESCRIPTION 2198 "The notReady(3) and createAndWait(5) states need 2199 not be supported." 2201 -- mplsOutSegmentTable 2203 OBJECT mplsOutSegmentIndexNext 2204 MIN-ACCESS read-only 2205 DESCRIPTION 2206 "Write access is not required." 2208 OBJECT mplsOutSegmentIndex 2209 MIN-ACCESS read-only 2210 DESCRIPTION 2211 "Write access is not required." 2213 OBJECT mplsOutSegmentIfIndex 2214 MIN-ACCESS read-only 2215 DESCRIPTION 2216 "Write access is not required." 2218 OBJECT mplsOutSegmentPushTopLabel 2219 MIN-ACCESS read-only 2220 DESCRIPTION 2221 "Write access is not required." 2223 OBJECT mplsOutSegmentTopLabel 2224 MIN-ACCESS read-only 2225 DESCRIPTION 2226 "Write access is not required." 2228 OBJECT mplsOutSegmentNextHopIpAddrType 2229 SYNTAX INTEGER { none(1), ipV4(2) } 2230 MIN-ACCESS read-only 2231 DESCRIPTION 2232 "ipV6(3) need not be supported." 2234 OBJECT mplsOutSegmentNextHopIpv4Addr 2235 MIN-ACCESS read-only 2236 DESCRIPTION 2237 "Write access is not required." 2239 OBJECT mplsOutSegmentNextHopIpv6Addr 2240 MIN-ACCESS read-only 2241 DESCRIPTION 2242 "Write access is not required." 2244 OBJECT mplsOutSegmentXCIndex 2245 MIN-ACCESS read-only 2246 DESCRIPTION 2247 "Write access is not required." 2249 OBJECT mplsOutSegmentTSpecIndex 2250 MIN-ACCESS read-only 2251 DESCRIPTION 2252 "Write access is not required." 2254 OBJECT mplsOutSegmentAdminStatus 2255 SYNTAX INTEGER { up(1), down(2) } 2256 MIN-ACCESS read-only 2257 DESCRIPTION 2258 "A value of testing(3) need not be supported." 2260 OBJECT mplsOutSegmentOperStatus 2261 SYNTAX INTEGER { up(1), down(2) } 2262 MIN-ACCESS read-only 2263 DESCRIPTION 2264 "Only up(1) and down(2) need to be supported." 2266 OBJECT mplsOutSegmentRowStatus 2267 SYNTAX INTEGER { active(1), notInService(2), 2268 createAndGo(4), destroy(6) } 2269 MIN-ACCESS read-only 2270 DESCRIPTION 2271 "The notReady(3) and createAndWait(5) states need 2272 not be supported." 2274 -- mplsXCTable 2276 OBJECT mplsXCIndexNext 2277 MIN-ACCESS read-only 2278 DESCRIPTION 2279 "Write access is not required." 2281 OBJECT mplsXCIndex 2282 MIN-ACCESS read-only 2283 DESCRIPTION 2284 "Write access is not required." 2286 OBJECT mplsXCLabelStackIndexNext 2287 MIN-ACCESS read-only 2288 DESCRIPTION 2289 "Write access is not required." 2291 OBJECT mplsXCLabelStackIndex 2292 MIN-ACCESS read-only 2293 DESCRIPTION 2294 "Write access is not required." 2296 OBJECT mplsXCCOS 2297 MIN-ACCESS read-only 2298 DESCRIPTION 2299 "Write access is not required." 2301 OBJECT mplsXCIsPersistent 2302 MIN-ACCESS read-only 2303 DESCRIPTION 2304 "Write access is not required." 2306 OBJECT mplsXCAdminStatus 2307 SYNTAX INTEGER { up(1), down(2) } 2308 MIN-ACCESS read-only 2309 DESCRIPTION 2310 "A value of testing(3) need not be supported." 2312 OBJECT mplsXCOperStatus 2313 SYNTAX INTEGER { up(1), down(2) } 2314 MIN-ACCESS read-only 2315 DESCRIPTION 2316 "Only up(1) and down(2) need to be supported." 2318 OBJECT mplsXCRowStatus 2319 SYNTAX INTEGER { active(1), notInService(2), 2320 createAndGo(4), destroy(6) } 2321 MIN-ACCESS read-only 2322 DESCRIPTION 2323 "The notReady(3) and createAndWait(5) states need 2324 not be supported." 2326 ::= { mplsLsrCompliances 1 } 2328 -- Units of conformance. 2330 mplsInterfaceGroup OBJECT-GROUP 2331 OBJECTS { mplsInterfaceConfIndex, 2332 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 2333 mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut, 2334 mplsInterfaceAdminStatus, mplsInterfaceOperStatus, 2335 mplsInterfaceInLabelsUsed, 2336 mplsInterfaceOutLabelsUsed } 2337 STATUS current 2338 DESCRIPTION 2339 "Collection of objects needed for MPLS interface 2340 configuration and performance information." 2341 ::= { mplsLsrGroups 1 } 2343 mplsInSegmentGroup OBJECT-GROUP 2344 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 2345 mplsInSegmentNPop, mplsInSegmentAddrFamily, 2346 mplsInSegmentXCIndex, mplsInSegmentTSpecIndex, 2347 mplsInSegmentAdminStatus, mplsInSegmentOperStatus, 2348 mplsInSegmentRowStatus, 2349 mplsInSegmentOctets, mplsInSegmentDiscards } 2350 STATUS current 2351 DESCRIPTION 2352 "Collection of objects needed to implement an in- 2353 segment." 2354 ::= { mplsLsrGroups 2 } 2356 mplsOutSegmentGroup OBJECT-GROUP 2357 OBJECTS { mplsOutSegmentIndexNext, 2358 mplsOutSegmentIndex, mplsOutSegmentIfIndex, 2359 mplsOutSegmentPushTopLabel, mplsOutSegmentTopLabel, 2360 mplsOutSegmentNextHopIpAddrType, 2361 mplsOutSegmentNextHopIpv4Addr, 2362 mplsOutSegmentNextHopIpv6Addr, 2363 mplsOutSegmentXCIndex, mplsOutSegmentTSpecIndex, 2364 mplsOutSegmentAdminStatus, mplsOutSegmentOperStatus, 2365 mplsOutSegmentRowStatus, 2366 mplsOutSegmentOctets, mplsOutSegmentDiscards } 2367 STATUS current 2368 DESCRIPTION 2369 "Collection of objects needed to implement an out- 2370 segment." 2371 ::= { mplsLsrGroups 3 } 2373 mplsXCGroup OBJECT-GROUP 2374 OBJECTS { mplsXCIndexNext, 2375 mplsXCIndex, mplsXCLabelStackIndex, 2376 mplsXCAdminStatus, mplsXCOperStatus, 2377 mplsXCRowStatus } 2378 STATUS current 2379 DESCRIPTION 2380 "Collection of objects needed to implement a 2381 cross-connect entry." 2382 ::= { mplsLsrGroups 4 } 2384 mplsPerfGroup OBJECT-GROUP 2385 OBJECTS { mplsInterfaceInPackets, mplsInterfaceInDiscards, 2386 mplsInterfaceOutPackets, mplsInterfaceOutDiscards, 2387 mplsInSegmentOctets, mplsInSegmentPackets, 2388 mplsInSegmentDiscards, 2389 mplsOutSegmentOctets, mplsOutSegmentPackets, 2390 mplsOutSegmentDiscards } 2391 STATUS current 2392 DESCRIPTION 2393 "Collection of objects providing performance 2394 information 2395 about an LSR." 2396 ::= { mplsLsrGroups 5 } 2398 mplsHCInSegmentPerfGroup OBJECT-GROUP 2399 OBJECTS { mplsInSegmentHCOctets } 2400 STATUS current 2401 DESCRIPTION 2402 "Object(s) providing performance information 2403 specific to out-segments for which the object 2404 mplsInterfaceInOctets wraps around too quickly." 2405 ::= { mplsLsrGroups 6 } 2407 mplsHCOutSegmentPerfGroup OBJECT-GROUP 2408 OBJECTS { mplsOutSegmentHCOctets } 2409 STATUS current 2410 DESCRIPTION 2411 "Object(s) providing performance information 2412 specific to out-segments for which the object 2413 mplsInterfaceOutOctets wraps around too 2414 quickly." 2415 ::= { mplsLsrGroups 7 } 2417 mplsTSpecGroup OBJECT-GROUP 2418 OBJECTS { mplsTSpecIndex, mplsTSpecDirection, 2419 mplsTSpecMaxRate, mplsTSpecMeanRate, 2420 mplsTSpecMaxBurstSize, mplsTSpecRowStatus } 2421 STATUS current 2422 DESCRIPTION 2423 "Object(s) required for supporting Int-Serv style 2424 resource reservation." 2425 ::= { mplsLsrGroups 8 } 2427 mplsXCIsPersistentGroup OBJECT-GROUP 2428 OBJECTS { mplsXCIsPersistent } 2429 STATUS current 2430 DESCRIPTION 2431 "Objects needed to support persistent cross- 2432 connects." 2433 ::= { mplsLsrGroups 9 } 2435 mplsXCIsNotPersistentGroup OBJECT-GROUP 2436 OBJECTS { mplsXCIsPersistent } 2437 STATUS current 2438 DESCRIPTION 2439 "Objects needed to support non-persistent cross- 2440 connects." 2441 ::= { mplsLsrGroups 10 } 2443 mplsLsrNotificationGroup NOTIFICATION-GROUP 2444 NOTIFICATIONS { mplsInterfaceUp, mplsInterfaceDown, 2445 mplsInSegmentUp, mplsInSegmentDown, 2446 mplsOutSegmentUp, mplsOutSegmentDown, 2447 mplsXCUp, mplsXCDown } 2448 STATUS current 2449 DESCRIPTION 2450 "Set of notifications implemented in this module. 2451 None is mandatory." 2452 ::= { mplsLsrGroups 11 } 2454 -- End of MPLS-LSR-MIB 2455 END 2457 10. Security Considerations 2458 It is clear that this MIB is potentially useful for monitoring of 2459 MPLS LSRs. This MIB can also be used for configuration of certain 2460 objects, and anything that can be configured can be incorrectly 2461 configured, with potentially disastrous results. 2463 At this writing, no security holes have been identified beyond 2464 those that SNMP Security [SNMPArch] is itself intended to address. 2465 These relate to primarily controlled access to sensitive 2466 information and the ability to configure a device - or which might 2467 result from operator error, which is beyond the scope of any 2468 security architecture. 2470 There are a number of management objects defined in this MIB which 2471 have a MAX-ACCESS clause of read-write and/or read-create. Such 2472 objects may be considered sensitive or vulnerable in some network 2473 environments. The support for SET operations in a non-secure 2474 environment without proper protection can have a negative effect 2475 on network operations. The use of SNMP Version 3 is recommended 2476 over prior versions, for configuration control, as its security 2477 model is improved. 2479 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even 2480 if the network itself is secure (for example by using IPSec 2481 [IPSEC]), there is no control as to who on the secure network is 2482 allowed to access and GET/SET (read/change/create/delete) the 2483 objects in this MIB. It is recommended that the implementers 2484 consider the security features as provided by the SNMPv3 2485 framework. Specifically, the use of the User-based Security Model 2486 [SNMPv3USM] and the View- based Access Control [SNMPv3VACM] is 2487 recommended. It is then a customer/user responsibility to ensure 2488 that the SNMP entity giving access to an instance of this MIB is 2489 properly configured to give access to the objects only to those 2490 principals (users) that have legitimate rights to indeed GET or 2491 SET (change/create/delete) them. 2493 There are a number of managed objects in this MIB that may contain 2494 information that may be sensitive from a business perspective, in 2495 that they represent a customer's interface to the MPLS network. 2496 Allowing uncontrolled access to these objects could result in 2497 malicious and unwanted disruptions of network traffic or incorrect 2498 configurations for these customers. There are no objects that are 2499 particularly sensitive in their own right, such as passwords or 2500 monetary amounts. 2502 11. Acknowledgments 2503 We wish to thank Ron Bonica of MCI, Dan Tappan of Cisco Systems, 2504 Bala Rajagopalan of NEC CCRL, and Eric Gray and Vasanthi 2505 Thirumalai of Lucent Technogies for their comments and input on 2506 this document. 2508 12. References 2510 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 2511 "Multiprotocol Label Switching Architecture", 2512 Internet Draft , 2513 August 1999. 2515 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 2516 Swallow, G., and A. Viswanathan, "A Framework for 2517 Multiprotocol Label Switching", Internet Draft 2518 , September 1999. 2520 [TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., 2521 "MPLS Traffic Engineering Management Information 2522 Base Using SMIv2", Internet Draft , February 2000. 2525 [LDPMIB] Cucchiara, J., Sjostrand, H., and J. Luciani, " 2526 Definitions of Managed Objects for the 2527 Multiprotocol Label Switching, Label Distribution 2528 Protocol (LDP)", Internet Draft , February 2000. 2531 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2532 Federokow, G., Li, T., and A. Conta, "MPLS Label 2533 Stack Encoding", Internet Draft , September 1999. 2536 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T., 2537 Swallow, G., and V. Srinivasan, "Extensions to RSVP 2538 for LSP Tunnels", Internet Draft , September 1999. 2541 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup 2542 using LDP", Internet Draft , September 1999. 2545 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2546 RFC 1700, October 1994. See also: 2547 http://www.isi.edu/in-notes/iana/assignments/smi- 2548 numbers 2550 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2551 Architecture for Describing SNMP Management 2552 Frameworks", RFC 2271, January 1998. 2554 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2555 Identification of Management Information for TCP/IP- 2556 based Internets", RFC 1155, May 1990. 2558 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2559 Definitions", RFC 1212, March 1991. 2561 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2562 with the SNMP", RFC 1215, March 1991. 2564 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2565 Waldbusser, "Structure of Management Information 2566 for Version 2 of the Simple Network Management 2567 Protocol (SNMPv2)", RFC 1902, January 1996. 2569 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2570 Waldbusser, "Textual Conventions for Version 2 of 2571 the Simple Network Management Protocol (SNMPv2)", 2572 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2573 January 1996. 2575 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2576 Waldbusser, "Conformance Statements for Version 2 2577 of the Simple Network Management Protocol 2578 (SNMPv2)", RFC 1904, January 1996. 2580 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2581 "Simple Network Management Protocol", RFC 1157, May 2582 1990. 2584 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2585 Waldbusser, "Introduction to Community-based 2586 SNMPv2", RFC 1901, January 1996. 2588 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2589 Waldbusser, "Transport Mappings for Version 2 of 2590 the Simple Network Management Protocol (SNMPv2)", 2591 RFC 1906, January 1996. 2593 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2594 "Message Processing and Dispatching for the Simple 2595 Network Management Protocol (SNMP)", RFC 2272, 2596 January 1998. 2598 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2599 Model (USM) for version 3 of the Simple Network 2600 Management Protocol (SNMPv3)", RFC 2574, April 2601 1999. 2603 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2604 Waldbusser, "Protocol Operations for Version 2 of 2605 the Simple Network Management Protocol (SNMPv2)", 2606 RFC 1905, January 1996. 2608 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2609 Applications", RFC 2273, January 1998. 2611 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2612 based Access Control Model (VACM) for the Simple 2613 Network Management Protocol (SNMP)", RFC 2575, 2614 April 1999. 2616 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2617 for the Internet Protocol", RFC 2401, November 2618 1998. 2620 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2621 Group MIB using SMIv2", RFC 2233, Nov. 1997 2623 13. Authors' Addresses 2625 Cheenu Srinivasan 2626 Tachion Networks, Inc. 2627 2 Meridian Road 2628 Eatontown, NJ 07724 2629 Phone: +1-732-542-7750 x234 2630 Email: cheenu@tachion.com 2632 Arun Viswanathan 2633 Force10 Networks 2634 1440 McCarthy Blvd 2635 Milpitas, CA 95035 2636 Phone: +1-408-571-3516 2637 Email: arun@force10networks.com 2639 Thomas D. Nadeau 2640 Cisco Systems, Inc. 2641 250 Apollo Drive 2642 Chelmsford, MA 01824 2643 Phone: +1-978-244-3051 2644 Email: tnadeau@cisco.com 2646 14. Full Copyright Statement 2648 Copyright (C) The Internet Society (2000). All Rights Reserved. 2650 This document and translations of it may be copied and furnished 2651 to others, and derivative works that comment on or otherwise 2652 explain it or assist in its implementation may be prepared, 2653 copied, published and distributed, in whole or in part, without 2654 restriction of any kind, provided that the above copyright notice 2655 and this paragraph are included on all such copies and derivative 2656 works. However, this document itself may not be modified in any 2657 way, such as by removing the copyright notice or references to the 2658 Internet Society or other Internet organizations, except as needed 2659 for the purpose of developing Internet standards in which case 2660 the procedures for copyrights defined in the Internet Standards 2661 process must be followed, or as required to translate it into 2662 languages other than English. 2664 The limited permissions granted above are perpetual and will not 2665 be revoked by the Internet Society or its successors or assigns. 2666 This document and the information contained herein is provided on 2667 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2668 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2669 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2670 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2671 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.