idnits 2.17.1 draft-ietf-mpls-ldp-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 52 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. ** There are 44 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2356 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.) -- The document date (October 1999) is 8959 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '17' is defined on line 2258, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2267, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 2276, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 2282, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 2285, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 2289, but no explicit reference was found in the text == Unused Reference: '27' is defined on line 2297, but no explicit reference was found in the text == Unused Reference: '28' is defined on line 2302, but no explicit reference was found in the text == Unused Reference: '30' is defined on line 2308, but no explicit reference was found in the text == Unused Reference: '31' is defined on line 2311, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2434 (ref. '17') (Obsoleted by RFC 5226) == Outdated reference: A later version (-11) exists of draft-ietf-mpls-ldp-06 == Outdated reference: A later version (-05) exists of draft-ietf-mpls-framework-04 -- Possible downref: Normative reference to a draft: ref. '19' == Outdated reference: A later version (-07) exists of draft-ietf-mpls-arch-06 == Outdated reference: A later version (-06) exists of draft-ietf-mpls-cr-ldp-02 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-te-mib-01 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-00 -- Possible downref: Non-RFC (?) normative reference: ref. '27' ** Obsolete normative reference: RFC 2233 (ref. '29') (Obsoleted by RFC 2863) Summary: 18 errors (**), 0 flaws (~~), 20 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Cucchiara 2 Internet-Draft IronBridge Networks 3 Expires March 2000 H. Sjostrand 4 Ericsson 5 J. Luciani 6 Nortel Networks 7 October 1999 9 Definitions of Managed Objects for 10 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 12 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. Internet-Drafts are 18 working documents of the Internet Engineering Task Force (IETF), its 19 areas, and its working groups. Note that other groups may also 20 distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 Distribution of this document is unlimited. Please send comments to 34 the Multiprotocol Label Switching (mpls) Working Group, 35 . 37 Copyright Notice 39 Copyright (C) The Internet Society (1999). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes managed objects for the Multiprotocol 46 Label Switching, Label Distribution Protocol (LDP). 48 Table of Contents 50 1 Introduction ................................................. 3 51 2 The SNMP Management Framework ................................ 3 52 3 Structure of the MIB ......................................... 5 53 3.1 Overview ................................................... 5 54 3.2 Interface Indexing ......................................... 5 55 3.3 Future Considerations ...................................... 5 56 3.4 Discussion of MIB Groups ................................... 6 57 3.5 The MPLS LDP General Group ................................. 6 58 3.5.1 The Label Distribution Protocol's Entity Table ........... 6 59 3.5.2 The Label Distribution Protocol's Entity ATM Objects ..... 6 60 Objects ................................................... 6 61 Table ..................................................... 7 62 3.5.5 The LDP Peer Table ....................................... 7 63 3.5.6 The LDP Session Table .................................... 7 64 3.5.7 The LDP ATM Session Table ................................ 7 65 3.5.8 The LDP Frame Relay Session Table ........................ 7 66 3.5.9 The LDP Session Statistics Table ......................... 7 67 3.5.10 The LDP Session Peer Address Table ...................... 8 68 3.5.11 The LDP Adjacencies Table ............................... 8 69 3.5.12 The LDP Label Information Base (LIB) Table .............. 8 70 3.5.13 The LDP FEC Table ....................................... 8 71 3.6 The LDP Notifications Group ................................ 8 72 3.6.1 LDP Notifications ........................................ 8 73 4 MPLS Label Distribution Protocol MIB Definitions ............. 8 74 5 Revision History ............................................. 45 75 5.1 Changes from .............. 45 76 5.2 Changes from .............. 46 77 6 TO DO List ................................................... 47 78 7 Acknowledgments .............................................. 47 79 8 References ................................................... 48 80 9 Security Considerations ...................................... 50 81 10 Authors' Addresses .......................................... 50 82 11 Full Copyright Statement .................................... 51 83 12 IANA Address Family Numbers MIB ............................. 51 85 1. Introduction 87 This memo defines a portion of the Management Information Base (MIB) 88 for use with network management protocols in the Internet community. 89 In particular, it describes managed objects for the Multiprotocol 90 Label Switching, Label Distribution Protocol (LDP) [18]. 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC 2119 [22]. 96 2. The SNMP Management Framework 98 The SNMP Management Framework presently consists of five major 99 components: 101 o An overall architecture, described in RFC 2571 [RFC2571]. 103 o Mechanisms for describing and naming objects and events for the 104 purpose of management. The first version of this Structure of 105 Management Information (SMI) is called SMIv1 and described in 106 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 107 1215 [RFC1215]. The second version, called SMIv2, is described 108 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 109 [RFC2580]. 111 o Message protocols for transferring management information. The 112 first version of the SNMP message protocol is called SNMPv1 and 113 described in STD 15, RFC 1157 [RFC1157]. A second version of the 114 SNMP message protocol, which is not an Internet standards track 115 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 116 and RFC 1906 [RFC1906]. The third version of the message 117 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 118 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 120 o Protocol operations for accessing management information. The 121 first set of protocol operations and associated PDU formats is 122 described in STD 15, RFC 1157 [RFC1157]. A second set of 123 protocol operations and associated PDU formats is described in 124 RFC 1905 [RFC1905]. 126 o A set of fundamental applications described in RFC 2573 127 [RFC2573] and the view-based access control mechanism described 128 in RFC 2575 [RFC2575]. 130 A more detailed introduction to the current SNMP Management Framework 131 can be found in RFC 2570 [RFC2570]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. Objects in the MIB are 135 defined using the mechanisms defined in the SMI. 137 This memo specifies a MIB module that is compliant to the SMIv2. A 138 MIB conforming to the SMIv1 can be produced through the appropriate 139 translations. The resulting translated MIB must be semantically 140 equivalent, except where objects or events are omitted because no 141 translation is possible (use of Counter64). Some machine readable 142 information in SMIv2 will be converted into textual descriptions in 143 SMIv1 during the translation process. However, this loss of machine 144 readable information is not considered to change the semantics of the 145 MIB. 147 3. Structure of the MIB 149 This memo defines a portion of the Management Information Base (MIB) 150 for use with network management protocols in the Internet community. 151 In particular, it describes managed objects for the Multiprotocol 152 Label Switching, Label Distribution Protocol (LDP) as defined in 153 [18]. 155 3.1. Overview 157 The MIB provides objects to configure/set-up potential LDP sessions 158 on a specific LSR. A table is used to configure potential LDP 159 Sessions, where each row in the table initiates an LDP Session. This 160 is the mplsLdpEntityTable. 162 Another table, the mplsLdpPeerTable, is a read-only table which 163 records information learned via discovery. Each row in the Peer 164 Table represents a peer. 166 A third table is used to show the actual sessions which have been, or 167 are in the process of being established. Each row represents a 168 specific session between an Entity (on this LSR) and a peer. The 169 following figure demonstrates these relationships: 171 Entity Peer 172 ------------ ------------ 173 | | | | 174 ------------ ------------- 175 | | -------------- | | 176 ------------ -----> | | <----- ------------ 177 -------------- 178 Session 180 3.2. Interface Indexing 182 Interface Indexes as specified in [29] are used in the MIB. The 183 descriptions of the ifIndexes denote which ifIndex is being used. 184 NOTE: the use of ifIndex is for actual existing connections. 186 3.3. Future Considerations 188 The following aspects are not addressed in this document: VPN issues 189 (i.e. potential MIB objects such as the VPN Identifier are not 190 included at this time), and lastly, multicast issues are not 191 discussed. 193 Some of these issues need further clarification before adding to the 194 MIB. 196 3.4. Discussion of MIB Groups 198 Currently, there are four groups: the MPLS LDP General Group, the 199 MPLS LDP ATM Group, the MPLS LDP Frame Relay Group and the MPLS LDP 200 Notifications Group. The MPLS LDP General Group and the MPLS LDP 201 Notifications Group should always be supported. The MPLS LDP ATM 202 Group is specific to ATM and should be supported only if LDP is using 203 ATM. Likewise, the MPLS LDP Frame Relay group is specific to Frame 204 Relay and should be supported only if LDP is using Frame Relay. 206 3.5. The MPLS LDP General Group 208 This group contains information about the specific LDP Entities which 209 are associated with this agent. Each LSR must have one LDP Entity. 211 3.5.1. The Label Distribution Protocol's Entity Table 213 The LDP Entity Table provides a way to configure the LSR for using 214 LDP. There must be at least one LDP Entity for the LSR to support 215 LDP. 217 Each entry/row in this table represents a single LDP Entity. 219 3.5.2. The Label Distribution Protocol's Entity ATM Objects 221 There exists two tables to configure LDP for using ATM. These tables 222 are the mplsLdpEntityAtmParmsTable and the 223 mplsLdpEntityConfAtmLabelRangeTable. 225 The mplsLdpEntityAtmParmsTable provides a way to configure 226 information which would be contained in the 'Optional Paramer' 227 portion of an LDP PDU Initialization Message. 229 The mplsLdpEntityConfAtmLabelRangeTable provides a way to configure 230 information which would be contained in the 'ATM Label Range 231 Components' portion of an LDP PDU Intialization Message. 233 3.5.3. The Label Distribution Protocol's Entity Frame Relay Objects 235 There exists two tables to configure LDP for using Frame Relay. 236 These tables are the mplsLdpEntityFrameRelayParmsTable and the 237 mplsLdpEntityConfFrLabelRangeTable. 239 The mplsLdpEntityFrameRelayParmsTable provides a way to configure 240 information which would be contained in the 'Optional Paramer' 241 portion of an LDP PDU Initialization Message. 243 The mplsLdpEntityConfFrLabelRangeTable provides a way to configure 244 information which would be contained in the portion of an LDP PDU 245 Intialization Message. 247 3.5.4. The Label Distribution Protocol's Entity Statistics Table 249 The LDP Entity Statistics Table will maintain counters related to an 250 LDP Entity. This Table should be a read-only table which contains 251 statistical information. 253 Each row in this table will be related to a single LDP Entity. 255 3.5.5. The LDP Peer Table 257 The LDP Peer Table is a read-only table which contains information 258 about LDP Peers. Each row in this table represents an LDP Peer which 259 is known to an LDP Entity. 261 3.5.6. The LDP Session Table 263 The LDP Session Table is a read-only table. Each entry in this table 264 represents a single session between an LDP Entity and a Peer. 266 3.5.7. The LDP ATM Session Table 268 The MPLS LDP ATM Session Table is a read-only table which contains 269 session information specific to ATM. 271 3.5.8. The LDP Frame Relay Session Table 273 The MPLS LDP Frame Relay Session Table is a read-only table which 274 contains session information specific to Frame Relay. 276 3.5.9. The LDP Session Statistics Table 278 The MPLS LDP Session Stats Table is a read-only table which contains 279 statistical information on sessions. 281 3.5.10. The LDP Session Peer Address Table 283 The MPLS LDP Session Peer Address Table is a table which 'extends' 284 the mplsLdpSessionTable. This table is a read-only table which 285 stores Addresses learned after session initialization via "Address 286 Message" advertisement. 288 3.5.11. The LDP Adjacencies Table 290 This is a table of all adjacencies between all LPD Entities and all 291 LDP Peers. A Session may have one or more adjacencies. 293 3.5.12. The LDP Label Information Base (LIB) Table 295 The MPLS LDP LIB Table is a read-only table which contains 296 information stored in the LIB. This table is indexed by a unique 297 number which could be used to represent the LSP segment related to 298 this LIB entry. The Lsp number corresponds to a FEC entry in the FEC 299 Table which is described next. 301 3.5.13. The LDP FEC Table 303 The FEC Table is a read-only table whic contains FEC (Forwarding 304 Equivalence Class) information. Each entry/row represents a single 305 FEC Element. 307 3.6. The LDP Notifications Group 309 3.6.1. LDP Notifications 311 Currently, there is one notification which will be sent when an LDP 312 attempts to initialize the same session beyond the configured 313 threshold. 315 4. MPLS Label Distribution Protocol MIB Definitions 317 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 319 IMPORTS 320 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 321 experimental, 322 Integer32, Counter32, Unsigned32 323 FROM SNMPv2-SMI 325 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 326 FROM SNMPv2-CONF 328 TEXTUAL-CONVENTION, RowStatus, TimeInterval 329 FROM SNMPv2-TC 330 InterfaceIndex 331 FROM IF-MIB 332 -- AtmInterfaceType, 333 AtmVcIdentifier, AtmVpIdentifier 334 FROM ATM-TC-MIB 335 AddressFamilyNumbers 336 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 337 ; 339 mplsLdpMIB MODULE-IDENTITY 340 LAST-UPDATED "9910071200Z" -- October 7, 1999 341 ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" 342 CONTACT-INFO 343 "Joan Cucchiara (joan@ironbridgenetworks.com) 344 IronBridge Networks 346 Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 347 Ericsson 349 James V. Luciani (luciani@baynetworks.com) 350 Nortel Networks" 351 DESCRIPTION 352 "This MIB contains managed object definitions for the 353 Multiprotocol Label Switching, Label Distribution 354 Protocol, LDP, as defined in draft-ietf-mpls-ldp-06.txt." 355 ::= { experimental XXXX } -- to be assigned 357 --******************************************************************** 358 -- MPLS LDP Textual Conventions 359 --******************************************************************** 360 -- 362 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 363 STATUS current 364 DESCRIPTION 365 "The Label Switch Router (LSR) identifier 366 is the first 4 bytes or the IP Address component 367 of the Label Distribution Protocol (LDP) identifier." 368 SYNTAX OCTET STRING (SIZE (4)) 370 -- 371 -- A similar TC is also used in RFC2677.txt, perhaps 372 -- this should be made general and not MPLS specific. 373 -- 374 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 375 STATUS current 376 DESCRIPTION 377 "The value of an network layer or data link layer address." 378 SYNTAX OCTET STRING (SIZE (0..64)) 380 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 381 STATUS current 382 DESCRIPTION 383 "The LDP identifier is a six octet quantity 384 which is used to identify an Label Switch Router 385 (LSR) label space. 387 The first four octets encode an IP address 388 assigned to the LSR, and the last two octets 389 identify a specific label space within the LSR." 390 SYNTAX OCTET STRING (SIZE (6)) 392 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 393 STATUS current 394 DESCRIPTION 395 "The Layer 2 label types which are defined for 396 MPLS LDP are generic(1), atm(2), or frameRelay(3)." 397 SYNTAX INTEGER(1..3) 399 -- Top-level structure of the MIB (the following is proposed) 400 mpls OBJECT IDENTIFIER ::= { mplsProtocols } 402 mplsProtocols OBJECT IDENTIFIER ::= { mplsLdpObjects } 403 -- under mplsProtocols will be LDP, CR-LDP, 404 -- and other MPLS "Protocols". 406 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 407 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 408 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 410 --**************************************************************** 411 -- MPLS LDP Objects 412 --**************************************************************** 414 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 416 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 418 -- 419 -- The MPLS Label Distribution Protocol Label Switch Router Objects 420 -- 422 mplsLdpLsrId OBJECT-TYPE 423 SYNTAX MplsLsrIdentifier 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The LSR's Identifier." 428 ::= { mplsLdpLsrObjects 1 } 430 mplsLdpLsrLabelRetentionMode OBJECT-TYPE 431 SYNTAX INTEGER { 432 conservative(1), 433 liberal(2) 434 } 435 MAX-ACCESS read-write 436 STATUS current 437 DESCRIPTION 438 "The LSR can be configured to use either 439 conservative or liberal label retention mode. 441 If the value of this object is conservative(1) 442 then advertized label mappings are retained 443 only if they will be used to forward packets, 444 i.e. if label came from a valid next hop. 446 If the value of this object is liberal(2) 447 then all advertized label mappings are retained 448 whether they are from a valid next hop or not." 449 ::= { mplsLdpLsrObjects 2 } 451 -- 452 -- The MPLS Label Distribution Protocol Entity Table 453 -- 455 mplsLdpEntityTable OBJECT-TYPE 456 SYNTAX SEQUENCE OF MplsLdpEntityEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION 460 "This table contains information about the 461 MPLS Label Distribution Protocol Entities which 462 exist on this Label Switch Router (LSR)." 463 ::= { mplsLdpEntityObjects 1 } 465 mplsLdpEntityEntry OBJECT-TYPE 466 SYNTAX MplsLdpEntityEntry 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "An entry in this table represents an LDP entity. 471 An entry can be created by a network administrator 472 or by an SNMP agent as instructed by LDP." 474 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 475 ::= { mplsLdpEntityTable 1 } 477 MplsLdpEntityEntry ::= SEQUENCE { 478 mplsLdpEntityLdpId MplsLdpIdentifier, 479 mplsLdpEntityIndex Unsigned32, 480 mplsLdpEntityWellKnownDiscoveryPort Unsigned32, 481 mplsLdpEntityMtu Integer32, 482 mplsLdpEntityKeepAliveHoldTimer Integer32, 483 mplsLdpEntityFailedInitSessionThreshold Integer32, 484 mplsLdpEntityLabelDistributionMethod INTEGER, 485 mplsLdpEntityOptionalParameters MplsLdpLabelTypes, 486 mplsLdpEntityRowStatus RowStatus 487 } 489 mplsLdpEntityLdpId OBJECT-TYPE 490 SYNTAX MplsLdpIdentifier 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION 494 "The LDP identifier. 496 The first four octets encode an IP address 497 assigned to the LSR, and the last two octets 498 identify a specific label space within the 499 LSR." 500 REFERENCE 501 "LDP Specification, Section on LDP Identifiers." 502 ::= { mplsLdpEntityEntry 1 } 504 mplsLdpEntityIndex OBJECT-TYPE 505 SYNTAX Unsigned32 (1..4294967295) 506 MAX-ACCESS not-accessible 507 STATUS current 508 DESCRIPTION 509 "This index should be unique to differentiate 510 LDP Identifiers, such that this index along 511 with the LDP Identifier will uniquely identify 512 the row." 513 ::= { mplsLdpEntityEntry 2 } 515 mplsLdpEntityWellKnownDiscoveryPort OBJECT-TYPE 516 SYNTAX Unsigned32 517 MAX-ACCESS read-create 518 STATUS current 519 DESCRIPTION 520 "The well known LDP Discovery Port." 521 ::= { mplsLdpEntityEntry 3 } 523 mplsLdpEntityMtu OBJECT-TYPE 524 SYNTAX Integer32 (0..65535) 525 MAX-ACCESS read-create 526 STATUS current 527 DESCRIPTION 528 "The maximum transmission unit (MTU) that was configured 529 for this entity." 530 ::= { mplsLdpEntityEntry 4 } 532 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 533 SYNTAX Integer32 (1..65535) 534 UNITS "seconds" 535 MAX-ACCESS read-create 536 STATUS current 537 DESCRIPTION 538 "The two octet value which is the proposed keep alive hold 539 timer for this LDP Entity." 540 ::= { mplsLdpEntityEntry 5 } 542 mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE 543 SYNTAX Integer32 544 MAX-ACCESS read-create 545 STATUS current 546 DESCRIPTION 547 "When attempting to establish a session with a 548 given Peer, the given LDP Entity should 549 send out a notification when exceeding this threshold. 550 A value of 0 (zero) for this object 551 indicates that the threshold is infinity. 552 In other words, a notification will not 553 be sent if the value of this object is 0 (zero)." 554 ::= { mplsLdpEntityEntry 6 } 556 mplsLdpEntityLabelDistributionMethod OBJECT-TYPE 557 SYNTAX INTEGER { 558 downstreamOnDemand(1), 559 downstreamUnsolicited(2) 560 } 561 MAX-ACCESS read-create 562 STATUS current 563 DESCRIPTION 564 "For any given LDP session, the method of 565 label distribution must be specified." 566 ::= { mplsLdpEntityEntry 7 } 568 mplsLdpEntityOptionalParameters OBJECT-TYPE 569 SYNTAX MplsLdpLabelTypes 570 MAX-ACCESS read-create 571 STATUS current 572 DESCRIPTION 573 "Specifies the optional parameters for the LDP 574 Initialization Message. If the value is generic(1) 575 then no optional parameters will be sent in 576 the LDP Initialization message associated with 577 this Entity. 579 If the value is atmParameters(2) then 580 a row must be created in the mplsLdpEntityAtmParms 581 Table, which corresponds to this entry. 583 If the value is frameRelayParameters(3) then 584 a row must be created in the mplsLdpEntityFrameRelayParms 585 Table, which corresponds to this entry." 586 ::= { mplsLdpEntityEntry 8 } 588 mplsLdpEntityRowStatus OBJECT-TYPE 589 SYNTAX RowStatus 590 MAX-ACCESS read-create 591 STATUS current 592 DESCRIPTION 593 "An object that allows entries in this table to 594 be created and deleted using the 595 RowStatus convention." 596 ::= { mplsLdpEntityEntry 9 } 598 -- 599 -- Ldp Entity Objects for ATM 600 -- 602 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= { mplsLdpEntityObjects 2 } 604 mplsLdpEntityAtmParmsTable OBJECT-TYPE 605 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 606 MAX-ACCESS not-accessible 607 STATUS current 608 DESCRIPTION 609 "This table contains information about the 610 ATM specific information which could be used 611 in the 'Optional Parameters'." 612 ::= { mplsLdpEntityAtmObjects 1 } 614 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 615 SYNTAX MplsLdpEntityAtmParmsEntry 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "An entry in this table represents the ATM parameters 620 for this LDP entity." 621 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 622 ::= { mplsLdpEntityAtmParmsTable 1 } 624 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 625 mplsLdpEntityAtmMergeCap INTEGER, 626 mplsLdpEntityAtmLabelRangeComponents Unsigned32, 627 mplsLdpEntityAtmVcDirectionality INTEGER, 628 mplsLdpEntityAtmRowStatus RowStatus 629 } 631 mplsLdpEntityAtmMergeCap OBJECT-TYPE 632 SYNTAX INTEGER { 633 notSupported(0), 634 vpMerge(1), 635 vcMerge(2), 636 vpAndVcMerge(3) 637 } 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "Denotes the Merge Capability of this Entity." 642 ::= { mplsLdpEntityAtmParmsEntry 1 } 644 mplsLdpEntityAtmLabelRangeComponents OBJECT-TYPE 645 SYNTAX Unsigned32 (1..65535) 646 MAX-ACCESS read-create 647 STATUS current 648 DESCRIPTION 649 "Number of LabelRange Components in the Initialization 650 message. This also represents the number of entries 651 in the mplsLdpLabelRangeComponentsTable which correspond 652 to this entry." 653 ::= { mplsLdpEntityAtmParmsEntry 2 } 655 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 656 SYNTAX INTEGER { 657 bidirectional(0), 658 unidirectional(1) 659 } 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "If the value of this object is 'bidirectional(0)', 664 a given VCI, within a given VPI, is used as a 665 label for both directions independently. 667 If the value of this object is 'unidirectional(1)', 668 a given VCI within a VPI designates one direction." 669 ::= { mplsLdpEntityAtmParmsEntry 3 } 671 mplsLdpEntityAtmRowStatus OBJECT-TYPE 672 SYNTAX RowStatus 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "An object that allows entries in this table to 677 be created and deleted using the 678 RowStatus convention." 679 ::= { mplsLdpEntityAtmParmsEntry 4 } 681 -- 682 -- The MPLS LDP Entity Configurable ATM Label Range Table 683 -- 685 mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE 686 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "The MPLS LDP Entity Configurable ATM Label Range Table. 691 The purpose of this table is to provide a mechanism 692 for specifying a contiguous range of vpi's 693 with a contiguous range of vci's, or a 'label range' 694 for LDP Entities. 696 LDP Entities which use ATM must have at least one 697 entry in this table." 698 ::= { mplsLdpEntityAtmObjects 2 } 700 mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE 701 SYNTAX MplsLdpEntityConfAtmLabelRangeEntry 702 MAX-ACCESS not-accessible 703 STATUS current 704 DESCRIPTION 705 "A row in the LDP Entity Configurable ATM Label 706 Range Table. One entry in this table contains 707 information on a single range of labels 708 represented by the configured Upper and Lower 709 Bounds VPI/VCI pairs. These are the same 710 data used in the Initialization Message. 712 NOTE: The ranges for a specific LDP Entity 713 are UNIQUE and non-overlapping. For example, 714 for a specific LDP Entity index, there could 715 be one entry having ConfLowerBound vpi/vci == 0/32, and 716 ConfUpperBound vpi/vci == 0/100, and a second entry for this 717 same interface with ConfLowerBound vpi/vci == 0/101 and 718 ConfUpperBound vpi/vci == 0/200. However, there could not be 719 a third entry with ConfLowerBound vpi/vci == 0/200 and 720 ConfUpperBound vpi/vci == 0/300 because this label range overlaps 721 with the second entry (i.e. both entries now have 0/200). 723 A row will not be created unless a unique and non-overlapping 724 range is specified. Thus, row creation implies a one-shot 725 row creation of LDP EntityID and ConfLowerBound vpi/vci and 726 ConfUpperBound vpi/vci. At least one label range entry 727 for a specific LDP Entity MUST include the default VPI/VCI 728 values denoted in the LDP Entity Table." 729 INDEX { mplsLdpEntityLdpId, 730 mplsLdpEntityIndex } 731 ::= { mplsLdpEntityConfAtmLabelRangeTable 1 } 733 MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { 734 mplsLdpEntityConfAtmLabelRangeMinimumVpi AtmVpIdentifier, 735 mplsLdpEntityConfAtmLabelRangeMinimumVci AtmVcIdentifier, 736 mplsLdpEntityConfAtmLabelRangeMaximumVpi AtmVpIdentifier, 737 mplsLdpEntityConfAtmLabelRangeMaximumVci AtmVcIdentifier, 738 mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus 739 } 741 mplsLdpEntityConfAtmLabelRangeMinimumVpi OBJECT-TYPE 742 SYNTAX AtmVpIdentifier 743 MAX-ACCESS read-create 744 STATUS current 745 DESCRIPTION 746 "The minimum VPI number configured for this range." 747 ::= { mplsLdpEntityConfAtmLabelRangeEntry 1 } 749 mplsLdpEntityConfAtmLabelRangeMinimumVci OBJECT-TYPE 750 SYNTAX AtmVcIdentifier 751 MAX-ACCESS read-create 752 STATUS current 753 DESCRIPTION 754 "The minimum VCI number configured for this range." 755 ::= { mplsLdpEntityConfAtmLabelRangeEntry 2 } 757 mplsLdpEntityConfAtmLabelRangeMaximumVpi OBJECT-TYPE 758 SYNTAX AtmVpIdentifier 759 MAX-ACCESS read-create 760 STATUS current 761 DESCRIPTION 762 "The maximum VPI number configured for this range." 763 ::= { mplsLdpEntityConfAtmLabelRangeEntry 3 } 765 mplsLdpEntityConfAtmLabelRangeMaximumVci OBJECT-TYPE 766 SYNTAX AtmVcIdentifier 767 MAX-ACCESS read-create 768 STATUS current 769 DESCRIPTION 770 "The maximum VCI number configured for this range." 771 ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } 773 mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE 774 SYNTAX RowStatus 775 MAX-ACCESS read-create 776 STATUS current 777 DESCRIPTION 778 "An object that allows entries in this 779 table to be created and deleted using 780 the RowStatus convention. 782 There must exist at least one entry in this 783 table for every LDP Entity that has 784 'mplsLdpEntityOptionalParameters' object with 785 a value of 'atmSessionParameters'." 786 ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } 788 -- 789 -- Ldp Entity Objects for Frame Relay 790 -- 792 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 793 { mplsLdpEntityObjects 3 } 795 mplsLdpEntityFrameRelayParmsTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayParmsEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "This table contains information about the 801 Optional Parameters to specify what this Entity is 802 going to specify for Frame Relay specific 803 LDP Intialization Messages." 804 ::= { mplsLdpEntityFrameRelayObjects 1 } 806 mplsLdpEntityFrameRelayParmsEntry OBJECT-TYPE 807 SYNTAX MplsLdpEntityFrameRelayParmsEntry 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "An entry in this table represents the Frame Relay 812 optional parameters associated with the LDP entity." 813 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 814 ::= { mplsLdpEntityFrameRelayParmsTable 1 } 816 MplsLdpEntityFrameRelayParmsEntry ::= SEQUENCE { 817 mplsLdpEntityFrMergeCap INTEGER, 818 mplsLdpEntityFrLabelRangeComponents Unsigned32, 819 mplsLdpEntityFrVcDirectionality INTEGER, 820 mplsLdpEntityFrParmsRowStatus RowStatus 821 } 823 mplsLdpEntityFrMergeCap OBJECT-TYPE 824 SYNTAX INTEGER { 825 notSupported(0), 826 supported(1) 827 } 828 MAX-ACCESS read-create 829 STATUS current 830 DESCRIPTION 831 "This represents whether or not Frame Relay merge capability 832 is supported." 833 ::= { mplsLdpEntityFrameRelayParmsEntry 1 } 835 mplsLdpEntityFrLabelRangeComponents OBJECT-TYPE 836 SYNTAX Unsigned32 (1..65535) 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "Number of LabelRange Components in the Initialization 841 message. This also represents the number of entries 842 in the mplsLdpEntityConfFRLabelRangeTable which correspond 843 to this entry." 844 ::= { mplsLdpEntityFrameRelayParmsEntry 2 } 846 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 847 SYNTAX INTEGER { 848 bidirectional(0), 849 unidirection(1) 850 } 851 MAX-ACCESS read-create 852 STATUS current 853 DESCRIPTION 854 "If the value of this object is 'bidirectional(0)', then 855 the LSR supports the use of a given DLCI as a label for 856 both directions independently. If the value of this object 857 is 'unidirectional(1)', then the LSR uses the given DLCI 858 as a label in only one direction." 859 ::= { mplsLdpEntityFrameRelayParmsEntry 3 } 861 mplsLdpEntityFrParmsRowStatus OBJECT-TYPE 862 SYNTAX RowStatus 863 MAX-ACCESS read-create 864 STATUS current 865 DESCRIPTION 866 "An object that allows entries in this table to 867 be created and deleted using the 868 RowStatus convention." 869 ::= { mplsLdpEntityFrameRelayParmsEntry 4 } 871 -- 872 -- Frame Relay Label Range Components 873 -- 875 mplsLdpEntityConfFrLabelRangeTable OBJECT-TYPE 876 SYNTAX SEQUENCE OF MplsLdpEntityConfFrLabelRangeEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "This table contains information about the 881 Optional Parameters to specify what this Entity is 882 going to specify for Frame Relay specific 883 LDP Intialization Messages." 884 ::= { mplsLdpEntityFrameRelayObjects 2 } 886 mplsLdpEntityConfFrLabelRangeEntry OBJECT-TYPE 887 SYNTAX MplsLdpEntityConfFrLabelRangeEntry 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "An entry in this table represents the Frame Relay 892 optional parameters associated with the LDP entity." 893 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 894 ::= { mplsLdpEntityConfFrLabelRangeTable 1 } 896 MplsLdpEntityConfFrLabelRangeEntry ::= SEQUENCE { 897 mplsLdpConfFrLen INTEGER, 898 mplsLdpConfFrMinimumDlci Integer32, 899 mplsLdpConfFrMaximumDlci Integer32, 900 mplsLdpConfFrRowStatus RowStatus 901 } 903 mplsLdpConfFrLen OBJECT-TYPE 904 SYNTAX INTEGER { 905 tenDlciBits(0), 906 seventeenDlciBits(1), 907 twentyThreeDlciBits(2) 908 } 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "This object specifies the DLCI bits." 913 ::= { mplsLdpEntityConfFrLabelRangeEntry 1 } 915 mplsLdpConfFrMinimumDlci OBJECT-TYPE 916 SYNTAX Integer32 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "The lower bound which is supported. This value should 921 be the same as that in the Frame Relay Label Range Component's 922 Minimum DLCI field." 923 ::= { mplsLdpEntityConfFrLabelRangeEntry 2 } 925 mplsLdpConfFrMaximumDlci OBJECT-TYPE 926 SYNTAX Integer32 927 MAX-ACCESS read-create 928 STATUS current 929 DESCRIPTION 930 "The upper bound which is supported. This value should 931 be the same as that in the Frame Relay Label Range Component's 932 Maximum DLCI field." 933 ::= { mplsLdpEntityConfFrLabelRangeEntry 3 } 935 mplsLdpConfFrRowStatus OBJECT-TYPE 936 SYNTAX RowStatus 937 MAX-ACCESS read-create 938 STATUS current 939 DESCRIPTION 940 "An object that allows entries in this table to 941 be created and deleted using the 942 RowStatus convention. 944 If the value of the object 'mplsLdpEntityOptionalParameters' 945 contains the value of 'frameReleaySessionParameters(3)' then 946 there must be at least one corresponding entry in this table." 947 ::= { mplsLdpEntityConfFrLabelRangeEntry 4 } 949 -- 950 -- The MPLS LDP Entity Statistics Table 951 -- 953 mplsLdpEntityStatsTable OBJECT-TYPE 954 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 955 MAX-ACCESS not-accessible 956 STATUS current 957 DESCRIPTION 958 "This table is a read-only table which augments 959 the mplsLdpEntityTable. The purpose of this 960 table is to keep statistical information about 961 the LDP Entities on the LSR." 962 ::= { mplsLdpEntityObjects 4 } 964 mplsLdpEntityStatsEntry OBJECT-TYPE 965 SYNTAX MplsLdpEntityStatsEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "A row in this table contains statistical information 970 about an LDP Entity. Some counters contained in a 971 row are for fatal errors received during a former 972 LDP Session associated with this entry. For example, 973 an Ldp Pdu received on a TCP connection for an 974 LDP Session which contains a fatal error is counted 975 here, because the session is terminated. 976 If the error is NOT fatal (i.e. and the Session 977 remains), then the error is counted in the 978 mplsLdpSessionStatsEntry." 979 AUGMENTS { mplsLdpEntityEntry } 980 ::= { mplsLdpEntityStatsTable 1 } 982 MplsLdpEntityStatsEntry ::= SEQUENCE { 983 mplsLdpAttemptedSessions Counter32, 984 mplsLdpSessionRejectedNoHelloErrors Counter32, 985 mplsLdpSessionRejectedAdvertisementErrors Counter32, 986 mplsLdpSessionRejectedMaxPduErrors Counter32, 987 mplsLdpSessionRejectedLabelRangeErrors Counter32, 988 mplsLdpBadLdpIdentifierErrors Counter32, 989 mplsLdpBadPduLengthErrors Counter32, 990 mplsLdpBadMessageLengthErrors Counter32, 991 mplsLdpBadTlvLengthErrors Counter32, 992 mplsLdpMalformedTlvValueErrors Counter32, 993 mplsLdpKeepAliveTimerExpiredErrors Counter32, 994 mplsLdpShutdownNotifReceived Counter32, 995 mplsLdpShutdownNotifSent Counter32 996 } 998 mplsLdpAttemptedSessions OBJECT-TYPE 999 SYNTAX Counter32 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "A count of the total attempted sessions for 1004 this LDP Entity." 1005 ::= { mplsLdpEntityStatsEntry 1 } 1007 mplsLdpSessionRejectedNoHelloErrors OBJECT-TYPE 1008 SYNTAX Counter32 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "A count of the Session Rejected/No Hello Error 1013 Notification Messages sent or received by 1014 this LDP Entity." 1016 ::= { mplsLdpEntityStatsEntry 2 } 1018 mplsLdpSessionRejectedAdvertisementErrors OBJECT-TYPE 1019 SYNTAX Counter32 1020 MAX-ACCESS read-only 1021 STATUS current 1022 DESCRIPTION 1023 "A count of the Session Rejected/Parameters 1024 Advertisement Mode Error Notification Messages sent 1025 or received by this LDP Entity." 1026 ::= { mplsLdpEntityStatsEntry 3 } 1028 mplsLdpSessionRejectedMaxPduErrors OBJECT-TYPE 1029 SYNTAX Counter32 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "A count of the Session Rejected/Parameters 1034 Max Pdu Length Error Notification Messages sent 1035 or received by this LDP Entity." 1036 ::= { mplsLdpEntityStatsEntry 4 } 1038 mplsLdpSessionRejectedLabelRangeErrors OBJECT-TYPE 1039 SYNTAX Counter32 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "A count of the Session Rejected/Parameters 1044 Label Range Notification Notification Messages sent 1045 or received by this LDP Entity." 1046 ::= { mplsLdpEntityStatsEntry 5 } 1048 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1049 SYNTAX Counter32 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "This object counts the number of Bad LDP Identifier Fatal 1054 Errors detected by the session(s) (past and present) associated 1055 with this LDP Entity." 1056 REFERENCE 1057 "LDP Specification, Section 3.5.1.2." 1058 ::= { mplsLdpEntityStatsEntry 6 } 1060 mplsLdpBadPduLengthErrors OBJECT-TYPE 1061 SYNTAX Counter32 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "This object counts the number of Bad Pdu Length Fatal 1066 Errors detected by the session(s) (past and present) associated 1067 with this LDP Entity." 1068 REFERENCE 1069 "LDP Specification, Section 3.5.1.2." 1070 ::= { mplsLdpEntityStatsEntry 7 } 1072 mplsLdpBadMessageLengthErrors OBJECT-TYPE 1073 SYNTAX Counter32 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "This object counts the number of Bad Message Length Fatal 1078 Errors detected by the session(s) (past and present) associated 1079 with this LDP Entity." 1080 REFERENCE 1081 "LDP Specification, Section 3.5.1.2." 1082 ::= { mplsLdpEntityStatsEntry 8 } 1084 mplsLdpBadTlvLengthErrors OBJECT-TYPE 1085 SYNTAX Counter32 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "This object counts the number of Bad TLV Length Fatal 1090 Errors detected by the session(s) (past and present) associated 1091 with this LDP Entity." 1092 REFERENCE 1093 "LDP Specification, Section 3.5.1.2." 1094 ::= { mplsLdpEntityStatsEntry 9 } 1096 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 1097 SYNTAX Counter32 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "This object counts the number of Malformed TLV Value Fatal 1102 Errors detected by the session(s) (past and present) associated 1103 with this LDP Entity." 1104 REFERENCE 1105 "LDP Specification, Section 3.5.1.2." 1106 ::= { mplsLdpEntityStatsEntry 10 } 1108 mplsLdpKeepAliveTimerExpiredErrors OBJECT-TYPE 1109 SYNTAX Counter32 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "This object counts the number of Session Keep Alive Timer 1114 Expired Errors detected by the session(s) (past and present) 1115 associated with this LDP Entity." 1116 REFERENCE 1117 "LDP Specification, Section 3.5.1.2." 1118 ::= { mplsLdpEntityStatsEntry 11 } 1120 mplsLdpShutdownNotifReceived OBJECT-TYPE 1121 SYNTAX Counter32 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "This object counts the number of Shutdown Notfications 1126 received related to session(s) (past and present) associated 1127 with this LDP Entity." 1128 ::= { mplsLdpEntityStatsEntry 12 } 1130 mplsLdpShutdownNotifSent OBJECT-TYPE 1131 SYNTAX Counter32 1132 MAX-ACCESS read-only 1133 STATUS current 1134 DESCRIPTION 1135 "This object counts the number of Shutdown Notfications 1136 sent related to session(s) (past and present) associated 1137 with this LDP Entity." 1138 ::= { mplsLdpEntityStatsEntry 13 } 1140 -- 1141 -- The MPLS LDP Peer Table 1142 -- 1144 mplsLdpPeerObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1146 mplsLdpPeerTable OBJECT-TYPE 1147 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "Information about LDP peers which have been discovered 1152 by the LDP Entities that are managed by this agent." 1153 ::= { mplsLdpPeerObjects 1 } 1155 mplsLdpPeerEntry OBJECT-TYPE 1156 SYNTAX MplsLdpPeerEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "Information about a single Peer." 1161 INDEX { mplsLdpPeerLdpId, 1162 mplsLdpPeerIndex } 1164 ::= { mplsLdpPeerTable 1 } 1166 MplsLdpPeerEntry ::= SEQUENCE { 1167 mplsLdpPeerLdpId MplsLdpIdentifier, 1168 mplsLdpPeerIndex Unsigned32, 1169 mplsLdpPeerInternetworkAddrType AddressFamilyNumbers, 1170 mplsLdpPeerInternetworkAddr MplsLdpGenAddr, 1171 mplsLdpPeerLabelDistributionMethod INTEGER, 1172 mplsLdpPeerLoopDetectionForPV INTEGER, 1173 mplsLdpPeerPathVectorLimit Integer32 1174 } 1176 mplsLdpPeerLdpId OBJECT-TYPE 1177 SYNTAX MplsLdpIdentifier 1178 MAX-ACCESS not-accessible 1179 STATUS current 1180 DESCRIPTION 1181 "The LDP identifier of this LDP Peer." 1182 ::= { mplsLdpPeerEntry 1 } 1184 mplsLdpPeerIndex OBJECT-TYPE 1185 SYNTAX Unsigned32 (1..4294967295) 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "An identifier for the LDP peer that is unique within the 1190 scope of this agent." 1191 ::= { mplsLdpPeerEntry 2 } 1193 mplsLdpPeerInternetworkAddrType OBJECT-TYPE 1194 SYNTAX AddressFamilyNumbers 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "The type of the internetwork layer address of this 1199 LDP peer. This object indicates how the value of 1200 mplsLdpPeerInternetworkAddr is to be interpreted." 1201 ::= { mplsLdpPeerEntry 3 } 1203 mplsLdpPeerInternetworkAddr OBJECT-TYPE 1204 SYNTAX MplsLdpGenAddr 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "The value of the internetwork layer address of this LDP peer." 1209 ::= { mplsLdpPeerEntry 4 } 1211 mplsLdpPeerLabelDistributionMethod OBJECT-TYPE 1212 SYNTAX INTEGER { 1213 downstreamOnDemand(1), 1214 downstreamUnsolicited(2) 1215 } 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "For any given LDP session, the method of 1220 label distribution must be specified." 1221 REFERENCE 1222 "draft-ietf-mpls-arch-06.txt [20]." 1223 ::= { mplsLdpPeerEntry 5 } 1225 mplsLdpPeerLoopDetectionForPV OBJECT-TYPE 1226 SYNTAX INTEGER { 1227 disabled(0), 1228 enabled(1) 1229 } 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "An indication of whether loop detection based on path vectors is 1234 disabled or enabled for this Peer. 1236 If this object has a value of disabled(0), 1237 then loop detection is disabled. Otherwise, if this object has 1238 a value of enabled(1), then loop detection based on path vectors 1239 is enabled." 1240 ::= { mplsLdpPeerEntry 6 } 1242 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1243 SYNTAX Integer32 (0..255) 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "If the value of 'mplsLdpPeerLoopDetectionForPV' for this entry is 1248 'enabled(1)', the this object represents that Path Vector Limit 1249 for this peer. 1251 If the value of 'mplsLdpPeerLoopDetectionForPV' for this entry 1252 is 'disabled(0)', then this value should be 0 (zero)." 1253 ::= { mplsLdpPeerEntry 7 } 1255 -- 1256 -- The MPLS LDP Sessions Table 1257 -- 1259 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 4 } 1261 mplsLdpSessionTable OBJECT-TYPE 1262 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1263 MAX-ACCESS not-accessible 1264 STATUS current 1265 DESCRIPTION 1266 "A table of Sessions between the LDP Entities and 1267 LDP Peers. Each row represents a single session." 1268 ::= { mplsLdpSessionObjects 1 } 1270 mplsLdpSessionEntry OBJECT-TYPE 1271 SYNTAX MplsLdpSessionEntry 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "An entry in this table represents information on a 1276 single session between an LDP Entity and LDP Peer. 1277 The information contained in a row is read-only." 1278 INDEX { mplsLdpEntityLdpId, 1279 mplsLdpEntityIndex, 1280 mplsLdpPeerLdpId, 1281 mplsLdpPeerIndex, 1282 mplsLdpSessionIndex 1283 } 1284 ::= { mplsLdpSessionTable 1 } 1286 MplsLdpSessionEntry ::= SEQUENCE { 1287 mplsLdpSessionIndex Unsigned32, 1288 mplsLdpSessionState INTEGER, 1289 mplsLdpSessionProtocolVersion Integer32, 1290 mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, 1291 mplsLdpSessionLabelAdvertisement INTEGER, 1292 mplsLdpSessionLoopDetectionForPV INTEGER, 1293 mplsLdpSessionPathVectorLimit Integer32, 1294 mplsLdpSessionMaxPduLength Integer32 1295 } 1297 mplsLdpSessionIndex OBJECT-TYPE 1298 SYNTAX Unsigned32 (1..4294967295) 1299 MAX-ACCESS not-accessible 1300 STATUS current 1301 DESCRIPTION 1302 "An unique identifier for this entry such that it 1303 identifies a specific LDP Session." 1304 ::= { mplsLdpSessionEntry 1 } 1306 mplsLdpSessionState OBJECT-TYPE 1307 SYNTAX INTEGER { 1308 nonexistent(1), 1309 initialized(2), 1310 openrec(3), 1311 opensent(4), 1312 operational(5) 1314 } 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "The current state of the session, all of the 1319 states 1 - 5 are based on the state machine for 1320 session negotiation behavior." 1321 ::= { mplsLdpSessionEntry 2 } 1323 mplsLdpSessionProtocolVersion OBJECT-TYPE 1324 SYNTAX Integer32(1..65535) 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "The version of the LDP Protocol which 1329 this session is using." 1330 ::= { mplsLdpSessionEntry 3 } 1332 mplsLdpSessionKeepAliveHoldTimeRemaining OBJECT-TYPE 1333 SYNTAX TimeInterval 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "The keep alive hold time remaining for this session." 1338 ::= { mplsLdpSessionEntry 4 } 1340 mplsLdpSessionLabelAdvertisement OBJECT-TYPE 1341 SYNTAX INTEGER { 1342 downStreamUnsolicited(0), 1343 downStreamOnDemand(1) 1344 } 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "The label advertisement discipline used for this Session." 1349 ::= { mplsLdpSessionEntry 5 } 1351 mplsLdpSessionLoopDetectionForPV OBJECT-TYPE 1352 SYNTAX INTEGER { 1353 disabled(0), 1354 enabled(1) 1355 } 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION 1359 "An indication of whether loop detection based on path vectors is 1360 disabled or enabled for this session. 1362 If this object has a value of disabled(0), 1363 then loop detection is disabled. Otherwise, if this object has 1364 a value of enabled(1), then loop detection based on path vectors 1365 is enabled." 1366 ::= { mplsLdpSessionEntry 6 } 1368 mplsLdpSessionPathVectorLimit OBJECT-TYPE 1369 SYNTAX Integer32 (0..255) 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "If the value of 'mplsLdpSessionLoopDetectionForPV' for this entry is 1374 'enabled(1)', the this object represents the Path Vector Limit 1375 for this session. 1377 If the value of 'mplsLdpSessionLoopDetectionForPV' for this entry 1378 is 'disabled(0)', then this value should be 0 (zero)." 1379 ::= { mplsLdpSessionEntry 7 } 1381 mplsLdpSessionMaxPduLength OBJECT-TYPE 1382 SYNTAX Integer32 (0..65535) 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "The value of maximum allowable length for LDP PDUs for 1387 this session. This value may have been negotiated during 1388 the Session Initialization." 1389 ::= { mplsLdpSessionEntry 8 } 1391 -- 1392 -- MPLS LDP ATM Session Information 1393 -- 1395 mplsLdpAtmSessionTable OBJECT-TYPE 1396 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 1397 MAX-ACCESS not-accessible 1398 STATUS current 1399 DESCRIPTION 1400 "A table of Sessions between the LDP Entities and 1401 LDP Peers using ATM as the underlying media. 1402 Each row represents a single session. 1404 NOTE: this table cannot use the 'AUGMENTS' 1405 clause because there is not necessarily a one-to-one 1406 mapping between this table and the mplsLdpSessionTable." 1407 ::= { mplsLdpSessionObjects 2 } 1409 mplsLdpAtmSessionEntry OBJECT-TYPE 1410 SYNTAX MplsLdpAtmSessionEntry 1411 MAX-ACCESS not-accessible 1412 STATUS current 1413 DESCRIPTION 1414 "An entry in this table represents information on a 1415 single session between an LDP Entity and LDP Peer. 1416 The information contained in a row is read-only." 1417 INDEX { mplsLdpEntityLdpId, 1418 mplsLdpEntityIndex, 1419 mplsLdpPeerLdpId, 1420 mplsLdpPeerIndex, 1421 mplsLdpSessionIndex 1422 } 1423 ::= { mplsLdpAtmSessionTable 1 } 1425 MplsLdpAtmSessionEntry ::= SEQUENCE { 1426 mplsLdpSessionAtmLabelRangeLowerBoundVpi AtmVpIdentifier, 1427 mplsLdpSessionAtmLabelRangeLowerBoundVci AtmVcIdentifier, 1428 mplsLdpSessionAtmLabelRangeUpperBoundVpi AtmVpIdentifier, 1429 mplsLdpSessionAtmLabelRangeUpperBoundVci AtmVcIdentifier 1430 } 1432 mplsLdpSessionAtmLabelRangeLowerBoundVpi OBJECT-TYPE 1433 SYNTAX AtmVpIdentifier 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "The minimum VPI number for this range." 1438 ::= { mplsLdpAtmSessionEntry 1 } 1440 mplsLdpSessionAtmLabelRangeLowerBoundVci OBJECT-TYPE 1441 SYNTAX AtmVcIdentifier 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "The minimum VCI number for this range." 1446 ::= { mplsLdpAtmSessionEntry 2 } 1448 mplsLdpSessionAtmLabelRangeUpperBoundVpi OBJECT-TYPE 1449 SYNTAX AtmVpIdentifier 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "The maximum VPI number for this range." 1454 ::= { mplsLdpAtmSessionEntry 3 } 1456 mplsLdpSessionAtmLabelRangeUpperBoundVci OBJECT-TYPE 1457 SYNTAX AtmVcIdentifier 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "The maximum VCI number for this range." 1462 ::= { mplsLdpAtmSessionEntry 4 } 1464 -- 1465 -- MPLS LDP Frame Relay Session Information 1466 -- 1468 mplsLdpFrameRelaySessionTable OBJECT-TYPE 1469 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION 1473 "A table of Sessions between the LDP Entities and 1474 LDP Peers using Frame Relay as the underlying media. 1475 Each row represents a single session. 1477 NOTE: this table cannot use the 'AUGMENTS' 1478 clause because there is not necessarily a one-to-one 1479 mapping between this table and the mplsLdpSessionTable." 1480 ::= { mplsLdpSessionObjects 3 } 1482 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 1483 SYNTAX MplsLdpFrameRelaySessionEntry 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "An entry in this table represents information on a 1488 single session between an LDP Entity and LDP Peer. 1489 The information contained in a row is read-only." 1490 INDEX { mplsLdpEntityLdpId, 1491 mplsLdpEntityIndex, 1492 mplsLdpPeerLdpId, 1493 mplsLdpPeerIndex, 1494 mplsLdpSessionIndex 1495 } 1496 ::= { mplsLdpFrameRelaySessionTable 1 } 1498 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 1499 mplsLdpFrSessionLen INTEGER, 1500 mplsLdpFrSessionMinDlci Integer32, 1501 mplsLdpFrSessionMaxDlci Integer32 1502 } 1504 mplsLdpFrSessionLen OBJECT-TYPE 1505 SYNTAX INTEGER { 1506 tenDlciBits(0), 1507 seventeenDlciBits(1), 1508 twentyThreeDlciBits(2) 1510 } 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "This object specifies the DLCI bits." 1515 ::= { mplsLdpFrameRelaySessionEntry 1 } 1517 mplsLdpFrSessionMinDlci OBJECT-TYPE 1518 SYNTAX Integer32 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "The lower bound of DLCIs which are supported." 1523 ::= { mplsLdpFrameRelaySessionEntry 2 } 1525 mplsLdpFrSessionMaxDlci OBJECT-TYPE 1526 SYNTAX Integer32 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "The upper bound of DLCIs which are supported." 1531 ::= { mplsLdpFrameRelaySessionEntry 3 } 1533 -- 1534 -- The MPLS LDP Session Statistics Table 1535 -- 1537 mplsLdpSessionStatsTable OBJECT-TYPE 1538 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 1539 MAX-ACCESS not-accessible 1540 STATUS current 1541 DESCRIPTION 1542 "A table of Sessions between the LDP Entities and 1543 LDP Peers." 1544 ::= { mplsLdpSessionObjects 4 } 1546 mplsLdpSessionStatsEntry OBJECT-TYPE 1547 SYNTAX MplsLdpSessionStatsEntry 1548 MAX-ACCESS not-accessible 1549 STATUS current 1550 DESCRIPTION 1551 "An entry in this table represents statistical information on a 1552 single session between an LDP Entity and LDP Peer." 1553 AUGMENTS { mplsLdpSessionEntry } 1554 ::= { mplsLdpSessionStatsTable 1 } 1556 MplsLdpSessionStatsEntry ::= SEQUENCE { 1557 mplsLdpSessionStatsUnknownMessageTypeErrors Counter32, 1558 mplsLdpSessionStatsUnknownTlvErrors Counter32 1560 } 1562 mplsLdpSessionStatsUnknownMessageTypeErrors OBJECT-TYPE 1563 SYNTAX Counter32 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "This object counts the number of Unknown Message Type 1568 Errors detected during this session." 1569 ::= { mplsLdpSessionStatsEntry 1 } 1571 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 1572 SYNTAX Counter32 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "This object counts the number of Unknown TLV Errors 1577 detected during this session." 1578 ::= { mplsLdpSessionStatsEntry 2 } 1580 -- 1581 -- Address Message/Address Withdraw Message Information 1582 -- 1583 -- This information is associated with a specific Session 1584 -- because Label Address Messages are sent after session 1585 -- initialization has taken place. 1586 -- 1588 mplsLdpSessionPeerAddressTable OBJECT-TYPE 1589 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddressEntry 1590 MAX-ACCESS not-accessible 1591 STATUS current 1592 DESCRIPTION 1593 "This table 'extends' the mplsLdpSessionTable. 1594 This table is used to store Label Address Information 1595 from Label Address Message received by this LSR from 1596 Peers. This table is read-only and should be updated 1597 when Label Withdraw Address Messages are received, i.e. 1598 Rows should be deleted as apropriate. 1600 NOTE: since more than one address may be contained 1601 in a Label Address Message, this table 'extends', 1602 rather than 'AUGMENTS' the mplsLdpSessionTable's 1603 information." 1604 ::= { mplsLdpSessionObjects 5 } 1606 mplsLdpSessionPeerAddressEntry OBJECT-TYPE 1607 SYNTAX MplsLdpSessionPeerAddressEntry 1608 MAX-ACCESS not-accessible 1609 STATUS current 1610 DESCRIPTION 1611 "An entry in this table represents information on 1612 session's for a single next hop address which was 1613 advertised in an Address Message from the LDP peer. 1614 The information contained in a row is read-only." 1615 INDEX { mplsLdpEntityLdpId, 1616 mplsLdpEntityIndex, 1617 mplsLdpPeerLdpId, 1618 mplsLdpPeerIndex, 1619 mplsLdpSessionIndex 1620 } 1621 ::= { mplsLdpSessionPeerAddressTable 1 } 1623 MplsLdpSessionPeerAddressEntry ::= SEQUENCE { 1624 mplsLdpSessionPeerNextHopAddressType AddressFamilyNumbers, 1625 mplsLdpSessionPeerNextHopAddress MplsLdpGenAddr 1626 } 1628 mplsLdpSessionPeerNextHopAddressType OBJECT-TYPE 1629 SYNTAX AddressFamilyNumbers 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "The internetwork layer address type of this Next Hop 1634 Address as specified in the Label Address Message associated 1635 with this Session. The value of this object indicates 1636 how to interpret the value of mplsLdpSessionPeerNextHopAddress." 1637 ::= { mplsLdpSessionPeerAddressEntry 1 } 1639 mplsLdpSessionPeerNextHopAddress OBJECT-TYPE 1640 SYNTAX MplsLdpGenAddr 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "The value of the next hop address." 1645 REFERENCE 1646 "LDP Specification [18] defines only IPv4 for LDP Protocol 1647 Version 1, see section 3.4.3." 1648 ::= { mplsLdpSessionPeerAddressEntry 2 } 1650 -- 1651 -- The MPLS LDP Hello Adjacency Table 1652 -- 1654 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 5 } 1656 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1657 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1658 MAX-ACCESS not-accessible 1659 STATUS current 1660 DESCRIPTION 1661 "A table of Hello Adjacencies for Sessions." 1662 ::= { mplsLdpHelloAdjacencyObjects 1 } 1664 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1665 SYNTAX MplsLdpHelloAdjacencyEntry 1666 MAX-ACCESS not-accessible 1667 STATUS current 1668 DESCRIPTION 1669 "Each row represents a single LDP Hello Adjacency. 1670 An LDP Session can have one or more Hello adjacencies." 1671 INDEX { mplsLdpEntityLdpId, 1672 mplsLdpEntityIndex, 1673 mplsLdpPeerLdpId, 1674 mplsLdpPeerIndex, 1675 mplsLdpHelloAdjacencyIndex } 1676 ::= { mplsLdpHelloAdjacencyTable 1 } 1678 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1679 mplsLdpHelloAdjacencyIndex Unsigned32, 1680 mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval, 1681 mplsLdpHelloAdjacencyType INTEGER 1682 } 1684 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1685 SYNTAX Unsigned32 (1..4294967295) 1686 MAX-ACCESS not-accessible 1687 STATUS current 1688 DESCRIPTION 1689 "An identifier for this specific adjacency." 1690 ::= { mplsLdpHelloAdjacencyEntry 1 } 1692 mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE 1693 SYNTAX TimeInterval 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "The time remaining for this Hello Adjacency. 1698 This interval will change when the 'next' 1699 Hello message which corresponds to this 1700 Hello Adjacency is received." 1701 ::= { mplsLdpHelloAdjacencyEntry 2 } 1703 mplsLdpHelloAdjacencyType OBJECT-TYPE 1704 SYNTAX INTEGER { 1705 link(1), 1706 targeted(2) 1707 } 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "This adjacency is the result of a 'link' 1712 hello if the value of this object is link(1). 1713 Otherwise, it is a result of a 'targeted' 1714 hello, targeted(2)." 1715 ::= { mplsLdpHelloAdjacencyEntry 3 } 1717 -- 1718 -- MPLS LDP LIB Table 1719 -- 1721 mplsLdpLibObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 6 } 1723 mplsLdpLibTable OBJECT-TYPE 1724 SYNTAX SEQUENCE OF MplsLdpLibEntry 1725 MAX-ACCESS not-accessible 1726 STATUS current 1727 DESCRIPTION 1728 "This table represents LIB (Label Information Base) 1729 Information. The table is read-only." 1730 ::= { mplsLdpLibObjects 1 } 1732 mplsLdpLibEntry OBJECT-TYPE 1733 SYNTAX MplsLdpLibEntry 1734 MAX-ACCESS not-accessible 1735 STATUS current 1736 DESCRIPTION 1737 "Each row represents a single LDP LIB entry." 1738 INDEX { mplsLdpLibLspId } 1739 ::= { mplsLdpLibTable 1 } 1741 MplsLdpLibEntry ::= SEQUENCE { 1742 mplsLdpLibLspId Unsigned32, 1743 mplsLdpLibLabelInIfIndex InterfaceIndex, 1744 mplsLdpLibLabelOutIfIndex InterfaceIndex, 1745 mplsLdpLibLabelType MplsLdpLabelTypes, 1746 mplsLdpLibInLabel MplsLdpGenAddr, 1747 mplsLdpLibOutLabel MplsLdpGenAddr 1748 } 1750 mplsLdpLibLspId OBJECT-TYPE 1751 SYNTAX Unsigned32 (1..4294967295) 1752 MAX-ACCESS not-accessible 1753 STATUS current 1754 DESCRIPTION 1755 "This number is used to uniquely identify this row, since this 1756 row is associated with a specific LSP, it may also be used 1757 to describe a unique number for an LSP. This number is used 1758 in the mplsLdpFecTable to identify which FECs or FEC is 1759 associated with this LIB entry." 1760 ::= { mplsLdpLibEntry 1 } 1762 mplsLdpLibLabelInIfIndex OBJECT-TYPE 1763 SYNTAX InterfaceIndex 1764 MAX-ACCESS read-only 1765 STATUS current 1766 DESCRIPTION 1767 "The ifIndex of the 'mplsLdpInLabel'." 1768 ::= { mplsLdpLibEntry 2 } 1770 mplsLdpLibLabelOutIfIndex OBJECT-TYPE 1771 SYNTAX InterfaceIndex 1772 MAX-ACCESS read-only 1773 STATUS current 1774 DESCRIPTION 1775 "The ifIndex of the 'mplsLdpOutLabel'." 1776 ::= { mplsLdpLibEntry 3 } 1778 mplsLdpLibLabelType OBJECT-TYPE 1779 SYNTAX MplsLdpLabelTypes 1780 MAX-ACCESS read-only 1781 STATUS current 1782 DESCRIPTION 1783 "The Layer 2 Label Type for 'mplsLdpInLabel' and 1784 'mplsLdpOutLabel'." 1785 ::= { mplsLdpLibEntry 4 } 1787 mplsLdpLibInLabel OBJECT-TYPE 1788 SYNTAX MplsLdpGenAddr 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "The incoming label of this LSP." 1793 ::= { mplsLdpLibEntry 5 } 1795 mplsLdpLibOutLabel OBJECT-TYPE 1796 SYNTAX MplsLdpGenAddr 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The outgoing label of this LSP." 1801 ::= { mplsLdpLibEntry 6 } 1803 -- 1804 -- Mpls Ldp FEC Table 1805 -- 1807 mplsLdpFecTable OBJECT-TYPE 1808 SYNTAX SEQUENCE OF MplsLdpFecEntry 1809 MAX-ACCESS not-accessible 1810 STATUS current 1811 DESCRIPTION 1812 "This table represents the FEC 1813 (Forwarding Equivalence Class) 1814 Information associated with an LSP. 1815 The table is read-only." 1816 ::= { mplsLdpLibObjects 2 } 1818 mplsLdpFecEntry OBJECT-TYPE 1819 SYNTAX MplsLdpFecEntry 1820 MAX-ACCESS not-accessible 1821 STATUS current 1822 DESCRIPTION 1823 "Each row represents a single FEC Element." 1824 INDEX { mplsLdpFecType, 1825 mplsLdpFecAddressFamily, 1826 mplsLdpFecAddressLength, 1827 mplsLdpFecAddress } 1828 ::= { mplsLdpFecTable 1 } 1830 MplsLdpFecEntry ::= SEQUENCE { 1831 mplsLdpFecType INTEGER, 1832 mplsLdpFecAddressFamily AddressFamilyNumbers, 1833 mplsLdpFecAddressLength Integer32(0..255), 1834 mplsLdpFecAddress MplsLdpGenAddr, 1835 mplsLdpFecLspId Unsigned32 1836 } 1838 mplsLdpFecType OBJECT-TYPE 1839 SYNTAX INTEGER { 1840 prefix(1), 1841 hostAddress(2) 1842 } 1843 MAX-ACCESS not-accessible 1844 STATUS current 1845 DESCRIPTION 1846 "The type of the FEC. If the value of this object 1847 is 'prefix(1)' then the FEC type described by this 1848 row is for address prefixes. 1850 If the value of this object is 'hostAddress(2)' then 1851 the FEC type described by this row is a host address." 1852 ::= { mplsLdpFecEntry 1 } 1854 mplsLdpFecAddressFamily OBJECT-TYPE 1855 SYNTAX AddressFamilyNumbers 1856 MAX-ACCESS not-accessible 1857 STATUS current 1858 DESCRIPTION 1859 "The value of this object is from the Address Family 1860 Numbers." 1861 ::= { mplsLdpFecEntry 2 } 1863 mplsLdpFecAddressLength OBJECT-TYPE 1864 SYNTAX Integer32(0..255) 1865 MAX-ACCESS not-accessible 1866 STATUS current 1867 DESCRIPTION 1868 "If the value of 'mplsLdpFecType' is 'prefix(1)' 1869 then the value of this object is the length in 1870 bits of the address prefix represented by 1871 'mplsLdpFecAddress', or if the length is zero then 1872 this is a special value which indicates that the 1873 prefix matches all addresses. In this case the 1874 prefix is also zero (i.e. 'mplsLdpFecAddress' will 1875 have the value of zero.)" 1876 ::= { mplsLdpFecEntry 3 } 1878 mplsLdpFecAddress OBJECT-TYPE 1879 SYNTAX MplsLdpGenAddr 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "If the value of 'mplsLdpFecType' is 'prefix(1)' 1884 then the value of this object is the address prefix. 1885 If the value of the 'mplsLdpFecAddressLength' 1886 is object is zero, then this object should also be 1887 zero." 1888 ::= { mplsLdpFecEntry 4 } 1890 mplsLdpFecLspId OBJECT-TYPE 1891 SYNTAX Unsigned32 (1..4294967295) 1892 MAX-ACCESS read-only 1893 STATUS current 1894 DESCRIPTION 1895 "This number represents the LSP which is related to 1896 this FEC. The value of this object should correspond 1897 to an entry in the MplsLdpLibTable, as denoted by 1898 the 'mplsLdpLibLspId' object. In other words, this 1899 object and the 'mplsLdpLibLspId' should have the same 1900 value." 1901 ::= { mplsLdpFecEntry 5 } 1903 --- 1904 --- Notifications 1905 --- 1907 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 1908 { mplsLdpNotifications 0 } 1910 mplsLdpFailedInitSessionThresholdExceeded NOTIFICATION-TYPE 1911 OBJECTS { 1912 mplsLdpEntityFailedInitSessionThreshold 1913 } 1914 STATUS current 1915 DESCRIPTION 1916 "This notification is generated whenever the value 1917 of mplsLdpEntityFailedInitSessionThreshold is 1918 exceeded." 1919 ::= { mplsLdpNotificationPrefix 1 } 1921 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 1922 OBJECTS { 1923 mplsLdpPeerPathVectorLimit, 1924 mplsLdpSessionPathVectorLimit 1925 } 1926 STATUS current 1927 DESCRIPTION 1928 "This notification is generated when the value 1929 of mplsLdpSessionPathVectorLimit does NOT match 1930 the value of the mplsLdpPeerPathVectorLimit for 1931 the corresponding mplsLdpPeerEntry." 1932 REFERENCE 1933 "LDP Specification, Section 3.5.3." 1934 ::= { mplsLdpNotificationPrefix 2 } 1936 --******************************************************************** 1937 -- Module Conformance Statement 1938 --******************************************************************** 1940 mplsLdpGroups 1941 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 1943 mplsLdpCompliances 1944 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 1946 -- 1947 -- Compliance Statements 1948 -- 1949 mplsLdpModuleCompliance MODULE-COMPLIANCE 1950 STATUS current 1951 DESCRIPTION 1952 "The basic implentation requirements for agents that support 1953 the MPLS LDP MIB." 1954 MODULE -- this module 1955 MANDATORY-GROUPS { mplsLdpGeneralGroup, 1956 mplsLdpNotificationsGroup 1957 } 1958 GROUP mplsLdpAtmGroup 1959 DESCRIPTION 1960 "This group must be supported if ATM is used in the 1961 MPLS LDP implementation." 1963 GROUP mplsLdpFrameRelayGroup 1964 DESCRIPTION 1965 "This group must be supported if Frame Relay is used in the 1966 MPLS LDP implementation." 1967 ::= { mplsLdpCompliances 1 } 1969 -- units of conformance 1971 mplsLdpGeneralGroup OBJECT-GROUP 1972 OBJECTS { 1973 mplsLdpLsrId, 1974 mplsLdpLsrLabelRetentionMode, 1975 mplsLdpEntityWellKnownDiscoveryPort, 1976 mplsLdpEntityMtu, 1977 mplsLdpEntityKeepAliveHoldTimer, 1978 mplsLdpEntityFailedInitSessionThreshold, 1979 mplsLdpEntityLabelDistributionMethod, 1980 mplsLdpEntityOptionalParameters, 1981 mplsLdpEntityRowStatus, 1982 mplsLdpAttemptedSessions, 1983 mplsLdpSessionRejectedNoHelloErrors, 1984 mplsLdpSessionRejectedAdvertisementErrors, 1985 mplsLdpSessionRejectedMaxPduErrors, 1986 mplsLdpSessionRejectedLabelRangeErrors, 1987 mplsLdpBadLdpIdentifierErrors, 1988 mplsLdpBadPduLengthErrors, 1989 mplsLdpBadMessageLengthErrors, 1990 mplsLdpBadTlvLengthErrors, 1991 mplsLdpMalformedTlvValueErrors, 1992 mplsLdpKeepAliveTimerExpiredErrors, 1993 mplsLdpShutdownNotifReceived, 1994 mplsLdpShutdownNotifSent, 1995 mplsLdpPeerInternetworkAddrType, 1996 mplsLdpPeerInternetworkAddr, 1997 mplsLdpPeerLabelDistributionMethod, 1998 mplsLdpPeerLoopDetectionForPV, 1999 mplsLdpPeerPathVectorLimit, 2000 mplsLdpSessionState, 2001 mplsLdpSessionProtocolVersion, 2002 mplsLdpSessionKeepAliveHoldTimeRemaining, 2003 mplsLdpSessionLabelAdvertisement, 2004 mplsLdpSessionLoopDetectionForPV, 2005 mplsLdpSessionPathVectorLimit, 2006 mplsLdpSessionMaxPduLength, 2007 mplsLdpSessionStatsUnknownMessageTypeErrors, 2008 mplsLdpSessionStatsUnknownTlvErrors, 2009 mplsLdpSessionPeerNextHopAddressType, 2010 mplsLdpSessionPeerNextHopAddress, 2011 mplsLdpHelloAdjacencyHoldTimeRemaining, 2012 mplsLdpHelloAdjacencyType, 2013 mplsLdpLibLabelInIfIndex, 2014 mplsLdpLibLabelOutIfIndex, 2015 mplsLdpLibLabelType, 2016 mplsLdpLibInLabel, 2017 mplsLdpLibOutLabel, 2018 mplsLdpFecLspId 2020 } 2021 STATUS current 2022 DESCRIPTION 2023 "Objects that apply to all MPLS LDP implementations." 2024 ::= { mplsLdpGroups 1 } 2026 mplsLdpAtmGroup OBJECT-GROUP 2027 OBJECTS { 2028 mplsLdpEntityAtmMergeCap, 2029 mplsLdpEntityAtmLabelRangeComponents, 2030 mplsLdpEntityAtmVcDirectionality, 2031 mplsLdpEntityAtmRowStatus, 2032 mplsLdpEntityConfAtmLabelRangeMinimumVpi, 2033 mplsLdpEntityConfAtmLabelRangeMinimumVci, 2034 mplsLdpEntityConfAtmLabelRangeMaximumVpi, 2035 mplsLdpEntityConfAtmLabelRangeMaximumVci, 2036 mplsLdpEntityConfAtmLabelRangeRowStatus, 2037 mplsLdpSessionAtmLabelRangeLowerBoundVpi, 2038 mplsLdpSessionAtmLabelRangeLowerBoundVci, 2039 mplsLdpSessionAtmLabelRangeUpperBoundVpi, 2040 mplsLdpSessionAtmLabelRangeUpperBoundVci 2042 } 2043 STATUS current 2044 DESCRIPTION 2045 "Objects that apply to all MPLS LDP implementations over ATM." 2046 ::= { mplsLdpGroups 2 } 2048 mplsLdpFrameRelayGroup OBJECT-GROUP 2049 OBJECTS { 2050 mplsLdpEntityFrMergeCap, 2051 mplsLdpEntityFrLabelRangeComponents, 2052 mplsLdpEntityFrVcDirectionality, 2053 mplsLdpEntityFrParmsRowStatus, 2054 mplsLdpConfFrLen, 2055 mplsLdpConfFrMinimumDlci, 2056 mplsLdpConfFrMaximumDlci, 2057 mplsLdpConfFrRowStatus, 2058 mplsLdpFrSessionLen, 2059 mplsLdpFrSessionMinDlci, 2060 mplsLdpFrSessionMaxDlci 2061 } 2062 STATUS current 2063 DESCRIPTION 2064 "Objects that apply to all MPLS LDP implementations over 2065 Frame Relay." 2066 ::= { mplsLdpGroups 3 } 2068 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2069 NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded, 2070 mplsLdpPathVectorLimitMismatch 2071 } 2072 STATUS current 2073 DESCRIPTION 2074 "The notification(s) which an MPLS LDP implemention 2075 is required to implement." 2076 ::= { mplsLdpGroups 4 } 2078 END 2080 5. Revision History 2082 This section should be removed when this document is published as an 2083 RFC. 2085 5.1. Changes from 2087 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 2088 the LDP Specification [18]. 2090 The front section was updated. 2092 The MIB was made to be less ATM-centric. Essentially, the ATM 2093 specific objects where removed from the tables and placed in ATM 2094 specific Tables. A "type" was added to the "base" tables and a row 2095 is to be created in the ATM/FR/etc. "type" table. Apropos 2096 compliance statements were added to reflect the separation of ATM and 2097 Frame Relay objects into their respective tables. 2099 Objects for Loop Detection were removed from describing the LDP 2100 implementation (i.e. the scalars were removed) and Loop Dection 2101 objects were added to the Session Table. (Although as the LDP 2102 Specification indicates loop detection should be for an LSR within a 2103 domain.) 2105 The following tables were added: mplsLdpEntityAtmParmsTable, 2106 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 2107 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 2108 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 2109 mplsLdpLibTable, and the mplsLdpFecTable. 2111 The following notifications were added: notification for Session 2112 removal. 2114 The following objects were removed from the Session Table: 2115 mplsLdpSessionRole was removed (this can be determined by comparing 2116 LSR Ids and does not need to be explicitely in the MIB.) ATM 2117 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 2118 mplsLdpSessionAtmLabelRangeLowerBoundVci, 2119 mplsLdpSessionAtmLabelRangeUpperBoundVpi 2120 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 2121 separate table. Frame Relay objects were added in a separate table. 2123 Hello Adjacency Table was updated. 2125 The objects, mplsLdpSessionRejectedParamErrors, 2126 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 2127 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 2128 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 2129 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 2130 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 2132 The mplsLdpSessionStatsTable was added to count statics based on a 2133 per Session basis. 2135 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 2136 need to configure information for a Peer. All information for a peer 2137 is learned, thus peer information is read-only. 2139 (Editorial) References were updated to reflect the documents which 2140 this version was based on. 2142 5.2. Changes from 2144 Textual conventions were added for the LSR Identifier and the LDP 2145 Identifier. 2147 Top-level mib structure was added. The LDP MIB falls under a proposed 2148 hierarchy of mpls.mplsProtocols. 2150 The mib hierarchy within the LDP MIB was also changed. A new branch, 2151 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 2152 branch is mplsLdpLsrObjects. Currently, this contains several new 2153 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 2154 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 2155 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 2156 mplsLdpLsrLoopPreventionAdminStatus, and 2157 mplsLdpLsrLabelRetentionMode. 2159 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 2160 is the LDP Identifier used in Session establishment. 2161 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 2162 were removed from this table. 2164 The following objects were added to the mplsLdpEntityTable: 2165 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 2166 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 2167 mplsLdpEntityVcDirectionality, and 2168 mplsLdpEntityLabelDistributionMethod. 2170 The following objects were added to the mplsLdpPeerEntityTable: 2171 mplsLdpPeerLabelDistributionMethod. 2173 The following object was removed from the mplsLdpEntityStatsTable: 2174 mplsLdpEntityEstablishedSessions. 2176 References were added and revised. 2178 6. TO DO List 2180 This section should be removed when this document is published as an 2181 RFC. This section outlines the next areas the authors intend to 2182 address in subsequent revisions. 2184 o Remove the following sections prior to final publication: IANA 2185 Considerations Section, Revisions Section and this (TO DO List) 2186 Section. 2188 o Updates as suggested by review of working group. 2190 7. Acknowledgments 2192 The authors would like to thank the following people: Leigh 2193 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 2194 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. 2196 8. References 2198 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2199 for Describing SNMP Management Frameworks", RFC 2571, April 2200 1999 2202 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2203 of Management Information for TCP/IP-based Internets", STD 2204 16, RFC 1155, May 1990 2206 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2207 16, RFC 1212, March 1991 2209 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2210 SNMP", RFC 1215, March 1991 2212 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2213 Rose, M., and S. Waldbusser, "Structure of Management 2214 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2216 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2217 Rose, M., and S. Waldbusser, "Textual Conventions for 2218 SMIv2", STD 58, RFC 2579, April 1999 2220 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2221 Rose, M., and S. Waldbusser, "Conformance Statements for 2222 SMIv2", STD 58, RFC 2580, April 1999 2224 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2225 Network Management Protocol", STD 15, RFC 1157, May 1990. 2227 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2228 "Introduction to Community-based SNMPv2", RFC 1901, January 2229 1996. 2231 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2232 "Transport Mappings for Version 2 of the Simple Network 2233 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2235 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2236 Processing and Dispatching for the Simple Network Management 2237 Protocol (SNMP)", RFC 2572, April 1999 2239 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2240 (USM) for version 3 of the Simple Network Management 2241 Protocol (SNMPv3)", RFC 2574, April 1999 2243 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2244 "Protocol Operations for Version 2 of the Simple Network 2245 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2247 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2248 RFC 2573, April 1999 2250 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2251 Access Control Model (VACM) for the Simple Network 2252 Management Protocol (SNMP)", RFC 2575, April 1999 2254 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2255 "Introduction to Version 3 of the Internet-standard Network 2256 Management Framework", RFC 2570, April 1999 2258 [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 2259 Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 2260 1998 2262 [18] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and Thomas, 2263 B., "LDP Specification.", draft-ietf-mpls-ldp-06.txt, Nortel 2264 Networks, Ennovate Networks, IBM, Nortel Networks, Cisco Systems 2265 October 1999 2267 [19] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and 2268 A. Viswanathan, "A Framework for Multiprotocol Label Switching", 2269 draft-ietf-mpls-framework-04.txt, IronBridge Networks, Ennovate 2270 Networks, IBM, Nortel Networks, Cisco Systems, July 1999. 2272 [20] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label 2273 Switching Architecture", draft-ietf-mpls-arch-06.txt, Cisco 2274 Systems, Lucent Technologies, and IronBridge Networks, August 1999. 2276 [21] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP", 2277 draft-ietf-mpls-cr-ldp-02.txt, August 1999. 2279 [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2280 Levels", BCP 14, RFC 2119, Harvard University, March 1997 2282 [23] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 2283 RFC 2026, Harvard University, October 1996 2285 [24] Srinivansan, C., and A. Viswanathan, "MPLS Traffic Engineering 2286 Management Information Base Using SMIv2", draft-ietf-mpls-te-mib- 2287 01.txt, Lucent Technologies, June 1999. 2289 [25] Srinivansan, C., and A. Viswanathan, "MPLS Label Switch Router 2290 Management Information Base Using SMIv2", draft-ietf-mpls-lsr-mib- 2291 00.txt, Lucent Technologies, June 1999. 2293 [26] Greene, M., J. Cucchiara, J. Luciani, "Definition of Managed 2294 Objects for the NBMA Next Hop Resolution Protocol (NHRP)", RFC 2295 2677, August 1999. 2297 [27] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, 2298 (http://www.isi.edu/in-notes/iana/assignements/address-family- 2299 numbers), for MIB 2300 (ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib). 2302 [28] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual Conventions 2303 and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. 2305 [29] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using 2306 SMIv2", RFC 2233, November 1997. 2308 [30] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 2309 Management", RFC 2515, February 1999. 2311 [31] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation over 2312 ATM Adaptation Layer 5", RFC 2684, September 1999. 2314 9. Security Considerations 2316 Assuming that secure network management (such as SNMP v3) is 2317 implemented, the objects represented in this MIB do not pose a threat 2318 to the security of the network. 2320 10. Authors' Addresses 2322 James V. Luciani 2323 Nortel Networks 2324 3 Federal Street 2325 Mail Stop: BL3-03 2326 Billerica, MA 01821 2327 Phone: (978) 288-4734 2328 Email: luciani@baynetworks.com 2330 Hans Sjostrand 2331 Ericsson 2332 Business Unit Datacom Networks and IP Services 2333 S-126 25 Stockholm, Sweden 2334 Phone: +46 8 719 9960 2335 Email: hans.sjostrand@etx.ericsson.se 2337 Joan Cucchiara 2338 IronBridge Networks 2339 55 Hayden Ave., Suite 1000 2340 Lexington, MA 02421 2341 Phone: (781) 372-8236 2342 Email: joan@ironbridgenetworks.com 2344 11. Full Copyright Statement 2346 Copyright (C) The Internet Society (1999). All Rights Reserved. 2348 This document and translations of it may be copied and furnished to 2349 others, and derivative works that comment on or otherwise explain it 2350 or assist in its implementation may be prepared, copied, published 2351 and distributed, in whole or in part, without restriction of any 2352 kind, provided that the above copyright notice and this paragraph are 2353 included on all such copies and derivative works. However, this 2354 document itself may not be modified in any way, such as by removing 2355 the copyright notice or references to the Internet Society or other 2356 Internet organizations, except as needed for the purpose of 2357 developing Internet standards in which case the procedures for 2358 copyrights defined in the Internet Standards process must be 2359 followed, or as required to translate it into languages other than 2360 English. 2362 The limited permissions granted above are perpetual and will not be 2363 revoked by the Internet Society or its successors or assigns. 2365 This document and the information contained herein is provided on an 2366 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2367 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2368 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2369 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2370 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2372 12. IANA Address Family Numbers MIB 2374 This section is copied verbatim from the RFC2677 [26]. This section 2375 will be removed in future versions of this draft. This section was 2376 copied here for convenience, as it is IMPORTED into the LDP MIB. 2378 The Internet Assigned Numbers Authority (IANA) has been and continues 2379 to be responsible for maintaining the ADDRESS FAMILY NUMBERS 2380 (http://www.isi.edu/in-notes/iana/assignments/address-family-numbers) 2381 name space assignments. The IANA has placed this list in a MIB 2382 module, such that it may be imported into other MIBs. The motivation 2383 for doing this is to allow MIBs to not have to change when a new 2384 assignment is made to the ADDRESS FAMILY NUMBERS. This is very 2385 similar to the motivation behind the IANAifType-MIB. 2387 Any additions or changes to the list of ADDRESS FAMILY NUMBERS 2388 registered via IANA will be done as they have in the past and this 2389 document does not propose any changes to the ADDRESS FAMILY NUMBERS 2390 other than to place them into a MIB, which can be found via anonymous 2391 FTP at: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib.