idnits 2.17.1 draft-ietf-mpls-ldp-mib-00.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: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 30 longer pages, the longest (page 2) being 114 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 31 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' scope of this agent."' ) ** 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.) ** There are 33 instances of too long lines in the document, the longest one being 6 characters in excess of 72. ** The abstract seems to contain references ([17]), 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 472: '...cific LDP Entity MUST include the defa...' RFC 2119 keyword, line 724: '...pecific LDP Peer MUST include the defa...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 1998) is 9379 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '17' on line 1176 looks like a reference -- Missing reference section? '1' on line 1099 looks like a reference -- Missing reference section? '2' on line 1104 looks like a reference -- Missing reference section? '3' on line 1108 looks like a reference -- Missing reference section? '4' on line 1111 looks like a reference -- Missing reference section? '5' on line 1114 looks like a reference -- Missing reference section? '6' on line 1120 looks like a reference -- Missing reference section? '7' on line 1126 looks like a reference -- Missing reference section? '8' on line 1132 looks like a reference -- Missing reference section? '9' on line 1137 looks like a reference -- Missing reference section? '10' on line 1142 looks like a reference -- Missing reference section? '11' on line 1148 looks like a reference -- Missing reference section? '12' on line 1153 looks like a reference -- Missing reference section? '13' on line 1157 looks like a reference -- Missing reference section? '14' on line 1163 looks like a reference -- Missing reference section? '15' on line 1167 looks like a reference -- Missing reference section? '16' on line 1172 looks like a reference -- Missing reference section? '18' on line 1181 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 4 warnings (==), 20 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects for 3 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 5 August 1998 7 9 Joan Cucchiara 10 Bay Networks 11 joanc@baynetworks.com 13 Hans Sjostrand 14 Ericsson 15 hans.sjostrand@etx.ericsson.se 17 James V. Luciani 18 Bay Networks 19 luciani@baynetworks.com 21 Status of this Memo 23 This document is an Internet-Draft. Internet-Drafts are working 24 documents of the Internet Engineering Task Force (IETF), its Areas, 25 and its Working Groups. Note that other groups may also distribute 26 working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as a "work in progress". 33 To view the entire list of current Internet-Drafts, please check the 34 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 35 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 36 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 37 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 39 Copyright Notice 41 Copyright (C) The Internet Society (1998). All Rights Reserved. 43 Abstract 45 This memo defines an experimental portion of the Management 46 Information Base (MIB) for use with network management protocols in 47 the Internet community. In particular, it describes managed objects 48 for the Multiprotocol Label Switching, Label Distribution Protocol 49 (LDP) as defined in [17]. 51 This memo does not specify a standard for the Internet community. 53 1. The SNMP Management Framework 55 The SNMP Management Framework presently consists of five major 56 components: 58 o An overall architecture, described in RFC 2271 [1]. 60 o Mechanisms for describing and naming objects and events for the 61 purpose of management. The first version of this Structure of 62 Management Information (SMI) is called SMIv1 and described in 63 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 64 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 65 1904 [7]. 67 o Message protocols for transferring management information. The 68 first version of the SNMP message protocol is called SNMPv1 and 69 described in RFC 1157 [8]. A second version of the SNMP message 70 protocol, which is not an Internet standards track protocol, is 71 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 72 The third version of the message protocol is called SNMPv3 and 73 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 75 o Protocol operations for accessing management information. The 76 first set of protocol operations and associated PDU formats is 77 described in RFC 1157 [8]. A second set of protocol operations 78 and associated PDU formats is described in RFC 1905 [13]. 80 o A set of fundamental applications described in RFC 2273 [14] and 81 the view-based access control mechanism described in RFC 2275 82 [15]. 84 Managed objects are accessed via a virtual information store, termed 85 the Management Information Base or MIB. Objects in the MIB are 86 defined using the mechanisms defined in the SMI. 88 This memo specifies a MIB module that is compliant to the SMIv2. A 89 MIB conforming to the SMIv1 can be produced through the appropriate 90 translations. The resulting translated MIB must be semantically 91 equivalent, except where objects or events are omitted because no 92 translation is possible (use of Counter64). Some machine readable 93 information in SMIv2 will be converted into textual descriptions in 94 SMIv1 during the translation process. However, this loss of machine 95 readable information is not considered to change the semantics of the 96 MIB. 98 1.1. Object Definitions 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. Objects in the MIB are 102 defined using the subset of Abstract Syntax Notation One (ASN.1) 103 defined in the SMI. In particular, each object type is named by an 104 OBJECT IDENTIFIER, an administratively assigned name. The object 105 type together with an object instance serves to uniquely identify a 106 specific instantiation of the object. For human convenience, we 107 often use a textual string, termed the descriptor, to also refer to 108 the object type. 110 2. Structure of the MIB 112 The following aspects are not addressed in this document: Interfaces 113 with respect to the IFMIB (e.g. is ldp an interface in the sense of 114 being stacked onto of the data link layer, and its relationship to 115 the network layer), VPN issues (i.e. potential MIB objects such as 116 the VPN Identifier are not included at this time), and lastly, 117 multicast issues are not discussed. 119 Some of these issues need further clarification before adding to this 120 MIB. 122 Currently, there is two groups. The MPLS LDP General Group and the 123 MPLS LDP Notifications Group. 125 2.1. The MPLS LDP General Group 127 This group contains information about the specific LDP Entities which 128 are associated with this agent. Each LSR must have one LDP Entity. 130 2.1.1. The Label Distribution Protocol's Entity Table 132 The LDP Entity Table represents the LDP Entities which exist on a 133 single Label Switch Router (LSR). The LDP Entity performs the LDP 134 protocol. There must be at least one LDP Entity for the LSR to 135 support LDP. 137 Each entry/row in this table represents a single LDP Entity. 139 2.1.2. The Label Distribution Protocol's Entity Statistics Table 141 The LDP Entity Statistics Table will maintain counters related to an 142 LDP Entity. This Table should be a read-only table which contains 143 statistical information. 145 Each row in this table will be related to a single LDP Entity. 147 2.1.3. The LDP Peer Table 149 The LDP Peer Table contains information about LDP Peers. Each row in 150 this table represents an LDP Peer which is known to an LDP Entity. 152 2.1.4. The LDP Sessions Table 154 Each entry in this table represents a session between an LDP Entity 155 and a Peer. 157 2.1.5. The LDP Adjacencies Table 159 This is a table of all adjacencies between all LPD Entities and all 160 LDP Peers. A Session may have one or more adjacencies. 162 2.1.6. The LDP Label Information Base (LIB) Table 164 TBD. Some potential objects: incoming label, outgoing label, and the 165 mid. 167 2.2. The LDP Notifications Group 169 2.2.1. LDP Notifications 171 Currently, there is one notification which will be sent when an LDP 172 attempts to initialize the same session beyond the configured 173 threshold. 175 3. MPLS Label Distribution Protocol MIB Definitions 177 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 179 IMPORTS 180 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 181 experimental, 182 Integer32, Counter32, Unsigned32 183 FROM SNMPv2-SMI 184 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 185 FROM SNMPv2-CONF 187 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeInterval 188 FROM SNMPv2-TC 190 ; 192 mplsLdpMIB MODULE-IDENTITY 193 LAST-UPDATED "9808261200Z" -- August 26, 1998 194 ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" 195 CONTACT-INFO 196 "Joan Cucchiara (joanc@baynetworks.com) 197 Bay Networks 199 Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 200 Ericsson 202 James V. Luciani (luciani@baynetworks.com) 203 Bay Networks" 204 DESCRIPTION 205 "This MIB contains managed object definitions for the 206 Multiprotocol Label Switching, Label Distribution 207 Protocol, LDP, as defined in draft-ietf-mpls-ldp-01.txt." 208 ::= { experimental 9876 } -- to be assigned 210 --******************************************************************** 211 -- MPLS LDP Textual Conventions 212 --******************************************************************** 214 MplsLdpIANAAddrFamily ::= TEXTUAL-CONVENTION 215 STATUS current 216 DESCRIPTION 217 "An address family. Values are defined in Assigned Numbers, 218 RFC1700. Note that not all these values make sense in all 219 contexts where this type is used in this MIB, but they are 220 included for completeness." 221 REFERENCE 222 "Assigned Numbers, RFC1700, ADDRESS FAMILY NUMBERS" 223 SYNTAX INTEGER { 224 other(0), 225 ipV4(1), 226 ipV6(2), 227 nsap(3), 228 hdlc(4), 229 bbn1822(5), 230 ieee802(6), 231 e163(7), 232 e164(8), 233 f69(9), 234 x121(10), 235 ipx(11), 236 appleTalk(12), 237 decnetIV(13), 238 banyanVines(14), 239 e164WithNsap(15) 240 } 242 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 243 STATUS current 244 DESCRIPTION 245 "The value of an network layer or data link layer address." 246 SYNTAX OCTET STRING (SIZE (0..60)) 248 AtmVpIdentifier ::= TEXTUAL-CONVENTION 249 STATUS current 250 DESCRIPTION 251 "The VPI value for a VPL. The value VPI=0 is not 252 used for a VPL not associated with a VCL. For ATM 253 UNIs supporting VPCs the VPI value ranges from 1 254 to 255. For ATM UNIs supporting VCCs the VPI value 255 ranges from 0 to 255. The maximum VPI value 256 cannot exceed the value allowable by 257 atmInterfaceMaxVpiBits defined in ATM-MIB." 258 SYNTAX Unsigned32 (0..4095) 260 AtmVcIdentifier ::= TEXTUAL-CONVENTION 261 STATUS current 262 DESCRIPTION 263 "The VCI value for a VCL. The maximum VCI value 264 cannot exceed the value allowable by 265 atmInterfaceMaxVciBits defined in ATM-MIB." 266 SYNTAX Unsigned32 (0..65535) 268 -- Top-level structure of the MIB 270 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 271 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 272 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 274 --******************************************************************** 275 -- MPLS LDP Objects 276 --******************************************************************** 278 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 280 -- 281 -- The MPLS Label Distribution Protocol Entity Table 282 -- 284 mplsLdpEntityTable OBJECT-TYPE 285 SYNTAX SEQUENCE OF MplsLdpEntityEntry 286 MAX-ACCESS not-accessible 287 STATUS current 288 DESCRIPTION 289 "This table contains information about the 290 MPLS Label Distribution Protocol Entities which 291 exist on this LSR." 292 ::= { mplsLdpEntityObjects 1 } 294 mplsLdpEntityEntry OBJECT-TYPE 295 SYNTAX MplsLdpEntityEntry 296 MAX-ACCESS not-accessible 297 STATUS current 298 DESCRIPTION 299 "An entry in this table represents an LDP entity. 300 An entry can be created by a network administrator 301 or by an SNMP agent as instructed by LDP." 302 INDEX { mplsLdpEntityIndex } 303 ::= { mplsLdpEntityTable 1 } 305 MplsLdpEntityEntry ::= SEQUENCE { 306 mplsLdpEntityIndex Integer32, 307 mplsLdpEntityConfId OCTET STRING, 308 mplsLdpEntityConfDefVpi AtmVpIdentifier, 309 mplsLdpEntityConfDefVci AtmVcIdentifier, 310 mplsLdpEntityConfWellKnownDiscoveryPort Unsigned32, 311 mplsLdpEntityConfMtu Integer32, 312 mplsLdpEntityConfKeepAliveHoldTimer Integer32, 313 mplsLdpEntityLoopDetection TruthValue, 314 mplsLdpEntityLoopPrevention TruthValue, 315 mplsLdpEntityFailedInitSessionThreshold Integer32, 316 mplsLdpEntityRowStatus RowStatus 317 } 319 mplsLdpEntityIndex OBJECT-TYPE 320 SYNTAX Integer32 (1..2147483647) 321 MAX-ACCESS not-accessible 322 STATUS current 323 DESCRIPTION 324 "A locally arbitrary, but unique identifier 325 for this entity. An agent assigns a unique 326 identifier when the row is created." 327 ::= { mplsLdpEntityEntry 1 } 329 mplsLdpEntityConfId OBJECT-TYPE 330 SYNTAX OCTET STRING (SIZE (6)) 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION 334 "The LDP identifier of this LDP Entity." 335 ::= { mplsLdpEntityEntry 2 } 337 mplsLdpEntityConfDefVpi OBJECT-TYPE 338 SYNTAX AtmVpIdentifier 339 MAX-ACCESS read-create 340 STATUS current 341 DESCRIPTION 342 "The Default VPI value used in the label for the default 343 VPI." 344 ::= { mplsLdpEntityEntry 3 } 346 mplsLdpEntityConfDefVci OBJECT-TYPE 347 SYNTAX AtmVcIdentifier 348 MAX-ACCESS read-create 349 STATUS current 350 DESCRIPTION 351 "The Default VCI value used in the label for the default 352 VCI." 353 ::= { mplsLdpEntityEntry 4 } 355 mplsLdpEntityConfWellKnownDiscoveryPort OBJECT-TYPE 356 SYNTAX Unsigned32 357 MAX-ACCESS read-create 358 STATUS current 359 DESCRIPTION 360 "The well known LDP Discovery Port." 361 ::= { mplsLdpEntityEntry 5 } 363 mplsLdpEntityConfMtu OBJECT-TYPE 364 SYNTAX Integer32 (0..65535) 365 MAX-ACCESS read-create 366 STATUS current 367 DESCRIPTION 368 "The maximum transmission unit (MTU) that was configured 369 for this entity." 370 ::= { mplsLdpEntityEntry 6 } 372 mplsLdpEntityConfKeepAliveHoldTimer OBJECT-TYPE 373 SYNTAX Integer32 (1..65535) 374 UNITS "seconds" 375 MAX-ACCESS read-create 376 STATUS current 377 DESCRIPTION 378 "The two octet value which is the proposed keep alive hold 379 timer for this LDP Entity." 381 ::= { mplsLdpEntityEntry 7 } 383 mplsLdpEntityLoopDetection OBJECT-TYPE 384 SYNTAX TruthValue 385 MAX-ACCESS read-create 386 STATUS current 387 DESCRIPTION 388 "A value of true (1) indicates that Loop Detection is 'on' 389 for this entity, a value of false (2) indicates that Loop 390 Detection is off." 391 ::= { mplsLdpEntityEntry 8 } 393 mplsLdpEntityLoopPrevention OBJECT-TYPE 394 SYNTAX TruthValue 395 MAX-ACCESS read-create 396 STATUS current 397 DESCRIPTION 398 "A value of true(1), indicates that this LDP entity has 399 loop prevention via Diffusion on. A value of false(2), 400 indicates that loop prevention via Diffusion is off." 401 ::= { mplsLdpEntityEntry 9 } 403 mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE 404 SYNTAX Integer32 405 MAX-ACCESS read-create 406 STATUS current 407 DESCRIPTION 408 "When attempting to establish a session with a 409 given Peer, the given LDP Entity should 410 send out a notification when exceeding this threshold. 411 A value of 0 (zero) for this object 412 indicates that the threshold is infinity. 413 In other words, a notification will not 414 be sent if the value of this object is 0 (zero)." 415 ::= { mplsLdpEntityEntry 10 } 417 mplsLdpEntityRowStatus OBJECT-TYPE 418 SYNTAX RowStatus 419 MAX-ACCESS read-create 420 STATUS current 421 DESCRIPTION 422 "An object that allows entries in this table to be created 423 and deleted using the RowStatus convention." 424 REFERENCE 425 "Textual Conventions for Version 2 of the Simple Network 426 Management Protocol (SNMPv2), RFC1903." 428 ::= { mplsLdpEntityEntry 11 } 430 -- 431 -- The MPLS LDP Entity Configurable ATM Label Range Table 432 -- 434 mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE 435 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry 436 MAX-ACCESS not-accessible 437 STATUS current 438 DESCRIPTION 439 "The MPLS LDP Entity Configurable ATM Label Range Table. 440 The purpose of this table is to provide a mechanism 441 for specifying a contiguous range of vpi's with a contiguous 442 range of vci's, or a 'label range' for LDP Entities. 443 LDP Entities which use ATM must have at least one 444 entry in this table." 445 ::= { mplsLdpEntityObjects 2 } 447 mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE 448 SYNTAX MplsLdpEntityConfAtmLabelRangeEntry 449 MAX-ACCESS not-accessible 450 STATUS current 451 DESCRIPTION 452 "A row in the LDP Entity Configurable ATM Label Range Table. 453 One entry in this table contains information 454 on a single range of labels represented by 455 the configured Upper and Lower Bounds VPI/VCI pairs. 457 NOTE: The ranges for a specific LDP Entity 458 are UNIQUE and non-overlapping. For example, 459 for a specific LDP Entity index, there could 460 be one entry having ConfLowerBound vpi/vci == 0/32, and 461 ConfUpperBound vpi/vci == 0/100, and a second entry for this 462 same interface with ConfLowerBound vpi/vci == 0/101 and 463 ConfUpperBound vpi/vci == 0/200. However, there could not be 464 a third entry with ConfLowerBound vpi/vci == 0/200 and 465 ConfUpperBound vpi/vci == 0/300 because this label range overlaps 466 with the second entry (i.e. both entries now have 0/200). 468 A row will not be created unless a unique and non-overlapping 469 range is specified. Thus, row creation implies a one-shot 470 row creation of LDP EntityIndex and ConfLowerBound vpi/vci and 471 ConfUpperBound vpi/vci. At least one label range entry 472 for a specific LDP Entity MUST include the default VPI/VCI 473 values denoted in the LDP Entity Table." 474 INDEX { mplsLdpEntityIndex, 475 mplsLdpEntityConfAtmLabelRangeLowerBoundVPI, 476 mplsLdpEntityConfAtmLabelRangeLowerBoundVCI } 477 ::= { mplsLdpEntityConfAtmLabelRangeTable 1 } 479 MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { 480 mplsLdpEntityConfAtmLabelRangeLowerBoundVPI AtmVpIdentifier, 481 mplsLdpEntityConfAtmLabelRangeLowerBoundVCI AtmVcIdentifier, 482 mplsLdpEntityConfAtmLabelRangeUpperBoundVPI AtmVpIdentifier, 483 mplsLdpEntityConfAtmLabelRangeUpperBoundVCI AtmVcIdentifier, 484 mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus 485 } 487 mplsLdpEntityConfAtmLabelRangeLowerBoundVPI OBJECT-TYPE 488 SYNTAX AtmVpIdentifier 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "The minimum VPI number configured for this range." 493 ::= { mplsLdpEntityConfAtmLabelRangeEntry 1 } 495 mplsLdpEntityConfAtmLabelRangeLowerBoundVCI OBJECT-TYPE 496 SYNTAX AtmVcIdentifier 497 MAX-ACCESS not-accessible 498 STATUS current 499 DESCRIPTION 500 "The minimum VCI number configured for this range." 501 ::= { mplsLdpEntityConfAtmLabelRangeEntry 2 } 503 mplsLdpEntityConfAtmLabelRangeUpperBoundVPI OBJECT-TYPE 504 SYNTAX AtmVpIdentifier 505 MAX-ACCESS read-create 506 STATUS current 507 DESCRIPTION 508 "The maximum VPI number configured for this range." 509 ::= { mplsLdpEntityConfAtmLabelRangeEntry 3 } 511 mplsLdpEntityConfAtmLabelRangeUpperBoundVCI OBJECT-TYPE 512 SYNTAX AtmVcIdentifier 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "The maximum VCI number configured for this range." 517 ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } 519 mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE 520 SYNTAX RowStatus 521 MAX-ACCESS read-create 522 STATUS current 523 DESCRIPTION 524 "An object that allows entries in this table to be created 525 and deleted using the RowStatus convention." 526 REFERENCE 527 "Textual Conventions for Version 2 of the Simple Network 528 Management Protocol (SNMPv2), RFC1903." 529 ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } 531 -- 532 -- The MPLS LDP Entity Statistics Table 533 -- 535 mplsLdpEntityStatsTable OBJECT-TYPE 536 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 537 MAX-ACCESS not-accessible 538 STATUS current 539 DESCRIPTION 540 "This table is a read-only table which augments 541 the MplsLdpConfEntityTable. The purpose of this 542 table is to keep statistical information about 543 the LDP Entities on the LSR." 544 ::= { mplsLdpEntityObjects 3 } 546 mplsLdpEntityStatsEntry OBJECT-TYPE 547 SYNTAX MplsLdpEntityStatsEntry 548 MAX-ACCESS not-accessible 549 STATUS current 550 DESCRIPTION 551 "A row in this table contains statistical information 552 about an LDP Entity." 553 AUGMENTS { mplsLdpEntityEntry } 554 ::= { mplsLdpEntityStatsTable 1 } 556 MplsLdpEntityStatsEntry ::= SEQUENCE { 557 mplsLdpEstablishedSessions Counter32, 558 mplsLdpAttemptedSessions Counter32 559 } 561 mplsLdpEstablishedSessions OBJECT-TYPE 562 SYNTAX Counter32 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "A count of the total established sessions for 567 this LDP Entity." 569 ::= { mplsLdpEntityStatsEntry 1 } 571 mplsLdpAttemptedSessions OBJECT-TYPE 572 SYNTAX Counter32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "A count of the total attempted sessions for 577 this LDP Entity." 578 ::= { mplsLdpEntityStatsEntry 2 } 580 -- 581 -- The MPLS LDP Peer Table 582 -- 584 mplsLdpPeerObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 586 mplsLdpPeerTable OBJECT-TYPE 587 SYNTAX SEQUENCE OF MplsLdpPeerEntry 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "Information about LDP peers which have been discovered 592 by the LDP Entities that are managed by this agent." 593 ::= { mplsLdpPeerObjects 1 } 595 mplsLdpPeerEntry OBJECT-TYPE 596 SYNTAX MplsLdpPeerEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "Information about a single Peer." 601 INDEX { mplsLdpEntityIndex, 602 mplsLdpPeerIndex } 603 ::= { mplsLdpPeerTable 1 } 605 MplsLdpPeerEntry ::= SEQUENCE { 606 mplsLdpPeerIndex Integer32, 607 mplsLdpPeerId OCTET STRING, 608 mplsLdpPeerInternetworkAddrType MplsLdpIANAAddrFamily, 609 mplsLdpPeerInternetworkAddr MplsLdpGenAddr, 610 mplsLdpPeerDefaultMtu Integer32, 611 mplsLdpPeerKeepAliveHoldTimer Integer32, 612 mplsLdpPeerRowStatus RowStatus 613 } 614 mplsLdpPeerIndex OBJECT-TYPE 615 SYNTAX Integer32 (1..65535) 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "An identifier for the LDP peer that is unique within the 620 scope of this agent." 621 ::= { mplsLdpPeerEntry 1 } 623 mplsLdpPeerId OBJECT-TYPE 624 SYNTAX OCTET STRING (SIZE (6)) 625 MAX-ACCESS read-create 626 STATUS current 627 DESCRIPTION 628 "The LDP identifier of this LDP Peer." 629 ::= { mplsLdpPeerEntry 2 } 631 mplsLdpPeerInternetworkAddrType OBJECT-TYPE 632 SYNTAX MplsLdpIANAAddrFamily 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "The type of the internetwork layer address of this 637 LDP peer. This object indicates how the value of 638 mplsLdpPeerInternetworkAddr is to be interpreted." 639 ::= { mplsLdpPeerEntry 3 } 641 mplsLdpPeerInternetworkAddr OBJECT-TYPE 642 SYNTAX MplsLdpGenAddr 643 MAX-ACCESS read-create 644 STATUS current 645 DESCRIPTION 646 "The value of the internetwork layer address of this LDP peer." 647 ::= { mplsLdpPeerEntry 4 } 649 mplsLdpPeerDefaultMtu OBJECT-TYPE 650 SYNTAX Integer32 (0..65535) 651 MAX-ACCESS read-create 652 STATUS current 653 DESCRIPTION 654 "The default maximum transmission unit (MTU) of the 655 LDP Peer." 656 DEFVAL { 9180 } 657 ::= { mplsLdpPeerEntry 5 } 659 mplsLdpPeerKeepAliveHoldTimer OBJECT-TYPE 660 SYNTAX Integer32 (1..65535) 661 UNITS "seconds" 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "The two octet unsigned non zero integer that indicates 666 the number of seconds that this Peer proposes for the 667 value of the KeepAlive Interval." 668 ::= { mplsLdpPeerEntry 6 } 670 mplsLdpPeerRowStatus OBJECT-TYPE 671 SYNTAX RowStatus 672 MAX-ACCESS read-create 673 STATUS current 674 DESCRIPTION 675 "An object that allows entries in this table to be created 676 and deleted using the RowStatus convention." 677 REFERENCE 678 "Textual Conventions for Version 2 of the Simple Network 679 Management Protocol (SNMPv2), RFC1903." 680 ::= { mplsLdpPeerEntry 7 } 682 -- 683 -- The MPLS LDP Peer Configurable ATM Label Range Table 684 -- 686 mplsLdpPeerConfAtmLabelRangeTable OBJECT-TYPE 687 SYNTAX SEQUENCE OF MplsLdpPeerConfAtmLabelRangeEntry 688 MAX-ACCESS not-accessible 689 STATUS current 690 DESCRIPTION 691 "The MPLS LDP Peer Configurable ATM Label Range Table. 692 The purpose of this table is to provide a mechanism 693 for specifying a contiguous range of vpi's with a contiguous 694 range of vci's, or a 'label range' for LDP Peers. 695 LDP Peers which use ATM must have at least one 696 entry in this table." 697 ::= { mplsLdpPeerObjects 2 } 699 mplsLdpPeerConfAtmLabelRangeEntry OBJECT-TYPE 700 SYNTAX MplsLdpPeerConfAtmLabelRangeEntry 701 MAX-ACCESS not-accessible 702 STATUS current 703 DESCRIPTION 704 "A row in the LDP Peer Configurable ATM Label Range Table. 705 One entry in this table contains information 706 on a single range of labels represented by 707 the configured Upper and Lower Bounds VPI/VCI pairs. 709 NOTE: The ranges for a specific LDP Peer 710 are UNIQUE and non-overlapping. For example, 711 for a specific LDP Peer index, there could 712 be one entry having ConfLowerBound vpi/vci == 0/32, and 713 ConfUpperBound vpi/vci == 0/100, and a second entry for this 714 same interface with ConfLowerBound vpi/vci == 0/101 and 715 ConfUpperBound vpi/vci == 0/200. However, there could not be 716 a third entry with ConfLowerBound vpi/vci == 0/200 and 717 ConfUpperBound vpi/vci == 0/300 because this label range overlaps 718 with the second entry (i.e. both entries now have 0/200). 720 A row will not be created unless a unique and non-overlapping 721 range is specified. Thus, row creation implies a one-shot 722 row creation of LDP PeerIndex and ConfLowerBound vpi/vci and 723 ConfUpperBound vpi/vci. At least one label range entry 724 for a specific LDP Peer MUST include the default VPI/VCI 725 values denoted in the LDP Peer Table." 726 INDEX { mplsLdpPeerIndex, 727 mplsLdpPeerConfAtmLabelRangeLowerBoundVPI, 728 mplsLdpPeerConfAtmLabelRangeLowerBoundVCI } 729 ::= { mplsLdpPeerConfAtmLabelRangeTable 1 } 731 MplsLdpPeerConfAtmLabelRangeEntry ::= SEQUENCE { 732 mplsLdpPeerConfAtmLabelRangeLowerBoundVPI AtmVpIdentifier, 733 mplsLdpPeerConfAtmLabelRangeLowerBoundVCI AtmVcIdentifier, 734 mplsLdpPeerConfAtmLabelRangeUpperBoundVPI AtmVpIdentifier, 735 mplsLdpPeerConfAtmLabelRangeUpperBoundVCI AtmVcIdentifier, 736 mplsLdpPeerConfAtmLabelRangeRowStatus RowStatus 737 } 739 mplsLdpPeerConfAtmLabelRangeLowerBoundVPI OBJECT-TYPE 740 SYNTAX AtmVpIdentifier 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "The minimum VPI number configured for this range." 745 ::= { mplsLdpPeerConfAtmLabelRangeEntry 1 } 747 mplsLdpPeerConfAtmLabelRangeLowerBoundVCI OBJECT-TYPE 748 SYNTAX AtmVcIdentifier 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "The minimum VCI number configured for this range." 753 ::= { mplsLdpPeerConfAtmLabelRangeEntry 2 } 755 mplsLdpPeerConfAtmLabelRangeUpperBoundVPI OBJECT-TYPE 756 SYNTAX AtmVpIdentifier 757 MAX-ACCESS read-create 758 STATUS current 759 DESCRIPTION 760 "The maximum VPI number configured for this range." 761 ::= { mplsLdpPeerConfAtmLabelRangeEntry 3 } 763 mplsLdpPeerConfAtmLabelRangeUpperBoundVCI OBJECT-TYPE 764 SYNTAX AtmVcIdentifier 765 MAX-ACCESS read-create 766 STATUS current 767 DESCRIPTION 768 "The maximum VCI number configured for this range." 769 ::= { mplsLdpPeerConfAtmLabelRangeEntry 4 } 771 mplsLdpPeerConfAtmLabelRangeRowStatus OBJECT-TYPE 772 SYNTAX RowStatus 773 MAX-ACCESS read-create 774 STATUS current 775 DESCRIPTION 776 "An object that allows entries in this table to be created 777 and deleted using the RowStatus convention." 778 REFERENCE 779 "Textual Conventions for Version 2 of the Simple Network 780 Management Protocol (SNMPv2), RFC1903." 781 ::= { mplsLdpPeerConfAtmLabelRangeEntry 5 } 783 -- 784 -- The MPLS LDP Sessions Table 785 -- 787 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 789 mplsLdpSessionTable OBJECT-TYPE 790 SYNTAX SEQUENCE OF MplsLdpSessionEntry 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "A table of Sessions between the LDP Entities and 795 LDP Peers." 796 ::= { mplsLdpSessionObjects 1 } 798 mplsLdpSessionEntry OBJECT-TYPE 799 SYNTAX MplsLdpSessionEntry 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "An entry in this table represents information on a 804 single session between an LDP Entity and LDP Peer." 805 INDEX { mplsLdpEntityIndex, 806 mplsLdpPeerIndex, 807 mplsLdpSessionIndex 808 } 809 ::= { mplsLdpSessionTable 1 } 811 MplsLdpSessionEntry ::= SEQUENCE { 812 mplsLdpSessionIndex Integer32, 813 mplsLdpSessionId OCTET STRING, 814 mplsLdpSessionProtocolVersion Integer32, 815 mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, 816 mplsLdpSessionRole INTEGER, 817 mplsLdpSessionState INTEGER, 818 mplsLdpSessionAtmLabelRangeLowerBoundVPI AtmVpIdentifier, 819 mplsLdpSessionAtmLabelRangeLowerBoundVCI AtmVcIdentifier, 820 mplsLdpSessionAtmLabelRangeUpperBoundVPI AtmVpIdentifier, 821 mplsLdpSessionAtmLabelRangeUpperBoundVCI AtmVcIdentifier, 822 mplsLdpSessionRowStatus RowStatus 823 } 825 mplsLdpSessionIndex OBJECT-TYPE 826 SYNTAX Integer32 (1..2147483647) 827 MAX-ACCESS not-accessible 828 STATUS current 829 DESCRIPTION 830 "An unique identifier for this entry such that it 831 identifies a specific LDP Session." 832 ::= { mplsLdpSessionEntry 1 } 834 mplsLdpSessionId OBJECT-TYPE 835 SYNTAX OCTET STRING(SIZE(6)) 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The LDP Session identifier." 840 ::= { mplsLdpSessionEntry 2 } 842 mplsLdpSessionProtocolVersion OBJECT-TYPE 843 SYNTAX Integer32(0..65535) 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "The version of the LDP Protocol which 848 this session is using." 849 ::= { mplsLdpSessionEntry 3 } 851 mplsLdpSessionKeepAliveHoldTimeRemaining OBJECT-TYPE 852 SYNTAX TimeInterval 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "The keep alive hold time remaining for this session." 857 ::= { mplsLdpSessionEntry 4 } 859 mplsLdpSessionRole OBJECT-TYPE 860 SYNTAX INTEGER { 861 active(1), 862 passive(2) 863 } 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "An indication of whether the LDP Entity associated with 868 this session is acting in an 'active' role or 869 a 'passive' role." 870 ::= { mplsLdpSessionEntry 5 } 872 mplsLdpSessionState OBJECT-TYPE 873 SYNTAX INTEGER { 874 nonexistent(1), 875 initialized(2), 876 openrec(3), 877 opensent(4), 878 operational(5) 879 } 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The current state of the session, all of the 884 states 1 - 5 are based on the state machine for 885 session negotiation behavior." 886 ::= { mplsLdpSessionEntry 6 } 888 mplsLdpSessionAtmLabelRangeLowerBoundVPI OBJECT-TYPE 889 SYNTAX AtmVpIdentifier 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "The minimum VPI number for this range." 894 ::= { mplsLdpSessionEntry 7 } 896 mplsLdpSessionAtmLabelRangeLowerBoundVCI OBJECT-TYPE 897 SYNTAX AtmVcIdentifier 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "The minimum VCI number for this range." 902 ::= { mplsLdpSessionEntry 8 } 904 mplsLdpSessionAtmLabelRangeUpperBoundVPI OBJECT-TYPE 905 SYNTAX AtmVpIdentifier 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The maximum VPI number for this range." 910 ::= { mplsLdpSessionEntry 9 } 912 mplsLdpSessionAtmLabelRangeUpperBoundVCI OBJECT-TYPE 913 SYNTAX AtmVcIdentifier 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "The maximum VCI number for this range." 918 ::= { mplsLdpSessionEntry 10 } 920 mplsLdpSessionRowStatus OBJECT-TYPE 921 SYNTAX RowStatus 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "An object that allows entries in this table to be created 926 and deleted using the RowStatus convention." 927 REFERENCE 928 "Textual Conventions for Version 2 of the Simple Network 929 Management Protocol (SNMPv2), RFC1903." 930 ::= { mplsLdpSessionEntry 11 } 932 -- 933 -- The MPLS LDP Hello Adjacency Table 934 -- 936 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 4 } 938 mplsLdpHelloAdjacencyTable OBJECT-TYPE 939 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "A table of Hello Adjacencies for Sessions." 944 ::= { mplsLdpHelloAdjacencyObjects 1 } 946 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 947 SYNTAX MplsLdpHelloAdjacencyEntry 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "Each row represents a single LDP Hello Adjacency. 952 An LDP Session can have one or more Hello adjacencies." 953 INDEX { mplsLdpSessionIndex, 954 mplsLdpHelloAdjacencyIndex } 955 ::= { mplsLdpHelloAdjacencyTable 1 } 957 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 958 mplsLdpHelloAdjacencyIndex Integer32, 959 mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval 960 } 962 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 963 SYNTAX Integer32 (1..2147483647) 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "An identifier for the adjacency." 968 ::= { mplsLdpHelloAdjacencyEntry 1 } 970 mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE 971 SYNTAX TimeInterval 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "The time remaining for this Hello Adjacency." 976 ::= { mplsLdpHelloAdjacencyEntry 2 } 978 --- 979 --- Notifications 980 --- 982 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 983 { mplsLdpNotifications 0 } 985 mplsLdpFailedInitSessionThresholdExceeded NOTIFICATION-TYPE 986 OBJECTS { 987 mplsLdpEntityFailedInitSessionThreshold 988 } 989 STATUS current 990 DESCRIPTION 991 "This notification is generated whenever the value 992 of mplsLdpEntityFailedInitSessionThreshold is 993 exceeded." 994 ::= { mplsLdpNotificationPrefix 1 } 996 --******************************************************************** 997 -- Module Compliance Statement 998 --******************************************************************** 1000 mplsLdpGroups 1001 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 1003 mplsLdpCompliances 1004 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 1006 mplsLdpModuleCompliance MODULE-COMPLIANCE 1007 STATUS current 1008 DESCRIPTION 1009 "The compliance statement for agents that support 1010 the MPLS LDP MIB." 1011 MODULE -- this module 1012 MANDATORY-GROUPS { mplsLdpGeneralGroup, 1013 mplsLdpNotificationsGroup 1014 } 1015 OBJECT mplsLdpEntityRowStatus 1016 MIN-ACCESS read-only 1017 DESCRIPTION 1018 "The agent is not required to support a SET operation 1019 to this object." 1021 OBJECT mplsLdpPeerRowStatus 1022 MIN-ACCESS read-only 1023 DESCRIPTION 1024 "The agent is not required to support a SET operation 1025 to this object." 1026 ::= { mplsLdpCompliances 1 } 1028 -- units of conformance 1030 mplsLdpGeneralGroup OBJECT-GROUP 1031 OBJECTS { 1032 mplsLdpEntityIndex, 1033 mplsLdpEntityConfId, 1034 mplsLdpEntityConfDefVpi, 1035 mplsLdpEntityConfDefVci, 1036 mplsLdpEntityConfWellKnownDiscoveryPort, 1037 mplsLdpEntityConfMtu, 1038 mplsLdpEntityConfKeepAliveHoldTimer, 1039 mplsLdpEntityLoopDetection, 1040 mplsLdpEntityLoopPrevention, 1041 mplsLdpEntityFailedInitSessionThreshold, 1042 mplsLdpEntityRowStatus, 1043 mplsLdpEntityConfAtmLabelRangeLowerBoundVPI, 1044 mplsLdpEntityConfAtmLabelRangeLowerBoundVCI, 1045 mplsLdpEntityConfAtmLabelRangeUpperBoundVPI, 1046 mplsLdpEntityConfAtmLabelRangeUpperBoundVCI, 1047 mplsLdpEntityConfAtmLabelRangeRowStatus, 1048 mplsLdpEstablishedSessions, 1049 mplsLdpAttemptedSessions, 1050 mplsLdpPeerIndex, 1051 mplsLdpPeerId, 1052 mplsLdpPeerInternetworkAddrType, 1053 mplsLdpPeerInternetworkAddr, 1054 mplsLdpPeerDefaultMtu, 1055 mplsLdpPeerKeepAliveHoldTimer, 1056 mplsLdpPeerRowStatus, 1057 mplsLdpPeerConfAtmLabelRangeLowerBoundVPI, 1058 mplsLdpPeerConfAtmLabelRangeLowerBoundVCI, 1059 mplsLdpPeerConfAtmLabelRangeUpperBoundVPI, 1060 mplsLdpPeerConfAtmLabelRangeUpperBoundVCI, 1061 mplsLdpPeerConfAtmLabelRangeRowStatus, 1062 mplsLdpSessionIndex, 1063 mplsLdpSessionId, 1064 mplsLdpSessionProtocolVersion, 1065 mplsLdpSessionKeepAliveHoldTimeRemaining, 1066 mplsLdpSessionRole, 1067 mplsLdpSessionState, 1068 mplsLdpSessionAtmLabelRangeLowerBoundVPI, 1069 mplsLdpSessionAtmLabelRangeLowerBoundVCI, 1070 mplsLdpSessionAtmLabelRangeUpperBoundVPI, 1071 mplsLdpSessionAtmLabelRangeUpperBoundVCI, 1072 mplsLdpSessionRowStatus, 1073 mplsLdpHelloAdjacencyIndex, 1074 mplsLdpHelloAdjacencyHoldTimeRemaining 1075 } 1076 STATUS current 1077 DESCRIPTION 1078 "Objects that apply to all MPLS LDP implementations over ATM." 1079 ::= { mplsLdpGroups 1 } 1081 mplsLdpNotificationsGroup NOTIFICATION-GROUP 1082 NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded } 1083 STATUS current 1084 DESCRIPTION 1085 "The notification(s) which an MPLS LDP implemention 1086 is required to implement." 1087 ::= { mplsLdpGroups 2 } 1089 END 1091 4. Acknowledgments 1093 The authors would like to thank the following people: Leigh 1094 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Bay 1095 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. 1097 5. References 1099 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1100 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1101 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1102 January 1998 1104 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1105 Management Information for TCP/IP-based Internets", RFC 1155, 1106 Performance Systems International, Hughes LAN Systems, May 1990 1108 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1109 Performance Systems International, Hughes LAN Systems, March 1991 1111 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1112 RFC 1215, Performance Systems International, March 1991 1114 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1115 of Management Information for Version 2 of the Simple Network 1116 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 1117 Systems, Inc., Dover Beach Consulting, Inc., International Network 1118 Services, January 1996. 1120 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1121 Conventions for Version 2 of the Simple Network Management Protocol 1122 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1123 Dover Beach Consulting, Inc., International Network Services, 1124 January 1996. 1126 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 1127 Statements for Version 2 of the Simple Network Management Protocol 1128 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 1129 Dover Beach Consulting, Inc., International Network Services, 1130 January 1996. 1132 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1133 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1134 International, Performance Systems International, MIT Laboratory 1135 for Computer Science, May 1990. 1137 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1138 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1139 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1140 International Network Services, January 1996. 1142 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1143 Mappings for Version 2 of the Simple Network Management Protocol 1144 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1145 Dover Beach Consulting, Inc., International Network Services, 1146 January 1996. 1148 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1149 Processing and Dispatching for the Simple Network Management 1150 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1151 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1153 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1154 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1155 2274, IBM T. J. Watson Research, January 1998. 1157 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1158 Operations for Version 2 of the Simple Network Management Protocol 1159 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1160 Dover Beach Consulting, Inc., International Network Services, 1161 January 1996. 1163 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1164 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1165 Systems, January 1998 1167 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1168 Control Model (VACM) for the Simple Network Management Protocol 1169 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1170 Cisco Systems, Inc., January 1998 1172 [16] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 1173 Considerations Section in RFCs", draft-iesg-iana-considerations- 1174 04.txt, IBM, UNINETT, May 1998. 1176 [17] Andersson, Loa, Doolan, P., Feldman, N., Fredette, A., and Thomas, 1177 R., "Label Distribution Protocol.", draft-ietf-mpls-ldp-01.txt, Bay 1178 Networks, Ennovate Networks, IBM, Bay Networks, cisco Systems March 1179 1998. 1181 [18] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and 1182 A. Viswanathan., "A Framework for Multiprotocol Label Switching", 1183 draft-ietf-mpls-framework-02.txt, Ascend Communications, Ennovate 1184 Networks, IBM, Bay Networks, cisco Systems, November 1997. 1186 6. Security Considerations 1188 7. Authors' Addresses 1190 Joan Cucchiara 1191 Bay Networks 1192 3 Federal Street 1193 Mail Stop: BL3-03 1194 Billerica, MA 01821 1195 Phone: (978) 916-8555 1196 Email: joanc@baynetworks.com 1198 Hans Sjostrand 1199 Ericsson 1200 Business Unit Datacom Networks and IP Services 1201 S-126 25 Stockholm, Sweden 1202 Phone: +46 8 719 9960 1203 Email: hans.sjostrand@etx.ericsson.se 1205 James V. Luciani 1206 Bay Networks 1207 3 Federal Street 1208 Mail Stop: BL3-03 1209 Billerica, MA 01821 1210 Phone: (978) 916-4734 1211 Email: luciani@baynetworks.com 1213 Full Copyright Statement 1215 Copyright (C) The Internet Society (1998). All Rights Reserved. 1217 This document and translations of it may be copied and furnished to 1218 others, and derivative works that comment on or otherwise explain it 1219 or assist in its implementation may be prepared, copied, published 1220 and distributed, in whole or in part, without restriction of any 1221 kind, provided that the above copyright notice and this paragraph are 1222 included on all such copies and derivative works. However, this 1223 document itself may not be modified in any way, such as by removing 1224 the copyright notice or references to the Internet Society or other 1225 Internet organizations, except as needed for the purpose of 1226 developing Internet standards in which case the procedures for 1227 copyrights defined in the Internet Standards process must be 1228 followed, or as required to translate it into languages other than 1229 English. 1231 The limited permissions granted above are perpetual and will not be 1232 revoked by the Internet Society or its successors or assigns. 1234 This document and the information contained herein is provided on an 1235 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1236 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1237 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1238 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1239 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1241 Table of Contents 1243 1 The SNMP Management Framework ................................ 2 1244 1.1 Object Definitions ......................................... 3 1245 2 Structure of the MIB ......................................... 4 1246 2.1 The MPLS LDP General Group ................................. 4 1247 2.1.1 The Label Distribution Protocol's Entity Table ........... 4 1248 2.1.2 The Label Distribution Protocol's Entity Statistics 1249 Table ..................................................... 4 1250 2.1.3 The LDP Peer Table ....................................... 4 1251 2.1.4 The LDP Sessions Table ................................... 5 1252 2.1.5 The LDP Adjacencies Table ................................ 5 1253 2.1.6 The LDP Label Information Base (LIB) Table ............... 5 1254 2.2 The LDP Notifications Group ................................ 5 1255 2.2.1 LDP Notifications ........................................ 5 1256 3 MPLS Label Distribution Protocol MIB Definitions ............. 5 1257 4 Acknowledgments .............................................. 26 1258 5 References ................................................... 27 1259 6 Security Considerations ...................................... 29 1260 7 Authors' Addresses ........................................... 29