draft-ietf-mpls-ldp-mib-00.txt   draft-ietf-mpls-ldp-mib-01.txt 
Definitions of Managed Objects for Definitions of Managed Objects for
the Multiprotocol Label Switching, Label Distribution Protocol (LDP) the Multiprotocol Label Switching, Label Distribution Protocol (LDP)
August 1998 June 1999
<draft-ietf-mpls-ldp-mib-00.txt>
Joan Cucchiara
Bay Networks
joanc@baynetworks.com
Hans Sjostrand <draft-ietf-mpls-ldp-mib-01.txt>
Ericsson
hans.sjostrand@etx.ericsson.se
James V. Luciani Joan Cucchiara Hans Sjostrand James V. Luciani
Bay Networks IronBridge Networks Ericsson Nortel Networks
luciani@baynetworks.com
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its Areas, all provisions of Section 10 of RFC 2026. Internet-Drafts are
and its Working Groups. Note that other groups may also distribute working documents of the Internet Engineering Task Force (IETF), its
working documents as Internet-Drafts. areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as a "work in progress". material or to cite them other than as "work in progress".
To view the entire list of current Internet-Drafts, please check the The list of current Internet-Drafts can be accessed at
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/ietf/1id-abstracts.txt
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific The list of Internet-Draft Shadow Directories can be accessed at
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). http://www.ietf.org/shadow.html
Distribution of this document is unlimited. Please send comments to
the Multiprotocol Label Switching (mpls) Working Group,
<mpls@uu.net>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines a portion of the Management Information Base (MIB)
Information Base (MIB) for use with network management protocols in for use with network management protocols in the Internet community.
the Internet community. In particular, it describes managed objects In particular, it describes managed objects for the Multiprotocol
for the Multiprotocol Label Switching, Label Distribution Protocol Label Switching, Label Distribution Protocol (LDP).
(LDP) as defined in [17].
This memo does not specify a standard for the Internet community. Table of Contents
1. The SNMP Management Framework 1 Introduction ................................................. 3
2 The SNMP Management Framework ................................ 3
3 Structure of the MIB ......................................... 5
3.1 The MPLS LDP General Group ................................. 5
3.1.1 The Label Distribution Protocol's Entity Table ........... 5
Table ..................................................... 5
3.1.3 The LDP Peer Table ....................................... 5
3.1.4 The LDP Sessions Table ................................... 6
3.1.5 The LDP Adjacencies Table ................................ 6
3.1.6 The LDP Label Information Base (LIB) Table ............... 6
3.2 The LDP Notifications Group ................................ 6
3.2.1 LDP Notifications ........................................ 6
4 MPLS Label Distribution Protocol MIB Definitions ............. 6
5 Revision History ............................................. 29
5.1 Changes from <draft-ietf-mpls-ldp-mib-00.txt> .............. 29
6 TO DO List ................................................... 29
7 Acknowledgments .............................................. 30
8 References ................................................... 31
9 Security Considerations ...................................... 33
10 Authors' Addresses .......................................... 33
11 Full Copyright Statement .................................... 33
12 IANA Address Family Numbers MIB ............................. 34
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for the Multiprotocol
Label Switching, Label Distribution Protocol (LDP) [18].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [22].
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described
1904 [7]. in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580
[RFC2580].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [RFC1157]. A second version of the
protocol, which is not an Internet standards track protocol, is SNMP message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
The third version of the message protocol is called SNMPv3 and and RFC 1906 [RFC1906]. The third version of the message
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [RFC1157]. A second set of
and associated PDU formats is described in RFC 1905 [13]. protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in RFC 2573
the view-based access control mechanism described in RFC 2275 [RFC2573] and the view-based access control mechanism described
[15]. in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
1.1. Object Definitions 3. Structure of the MIB
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to also refer to
the object type.
2. Structure of the MIB
The following aspects are not addressed in this document: Interfaces The following aspects are not addressed in this document: Interfaces
with respect to the IFMIB (e.g. is ldp an interface in the sense of with respect to the IFMIB (e.g. is ldp an interface in the sense of
being stacked onto of the data link layer, and its relationship to being stacked onto of the data link layer, and its relationship to
the network layer), VPN issues (i.e. potential MIB objects such as the network layer), VPN issues (i.e. potential MIB objects such as
the VPN Identifier are not included at this time), and lastly, the VPN Identifier are not included at this time), and lastly,
multicast issues are not discussed. multicast issues are not discussed.
Some of these issues need further clarification before adding to this Some of these issues need further clarification before adding to this
MIB. MIB.
Currently, there is two groups. The MPLS LDP General Group and the Currently, there is two groups. The MPLS LDP General Group and the
MPLS LDP Notifications Group. MPLS LDP Notifications Group.
2.1. The MPLS LDP General Group 3.1. The MPLS LDP General Group
This group contains information about the specific LDP Entities which This group contains information about the specific LDP Entities which
are associated with this agent. Each LSR must have one LDP Entity. are associated with this agent. Each LSR must have one LDP Entity.
2.1.1. The Label Distribution Protocol's Entity Table 3.1.1. The Label Distribution Protocol's Entity Table
The LDP Entity Table represents the LDP Entities which exist on a The LDP Entity Table represents the LDP Entities which exist on a
single Label Switch Router (LSR). The LDP Entity performs the LDP single Label Switch Router (LSR). The LDP Entity performs the LDP
protocol. There must be at least one LDP Entity for the LSR to protocol. There must be at least one LDP Entity for the LSR to
support LDP. support LDP.
Each entry/row in this table represents a single LDP Entity. Each entry/row in this table represents a single LDP Entity.
2.1.2. The Label Distribution Protocol's Entity Statistics Table 3.1.2. The Label Distribution Protocol's Entity Statistics Table
The LDP Entity Statistics Table will maintain counters related to an The LDP Entity Statistics Table will maintain counters related to an
LDP Entity. This Table should be a read-only table which contains LDP Entity. This Table should be a read-only table which contains
statistical information. statistical information.
Each row in this table will be related to a single LDP Entity. Each row in this table will be related to a single LDP Entity.
2.1.3. The LDP Peer Table 3.1.3. The LDP Peer Table
The LDP Peer Table contains information about LDP Peers. Each row in The LDP Peer Table contains information about LDP Peers. Each row in
this table represents an LDP Peer which is known to an LDP Entity. this table represents an LDP Peer which is known to an LDP Entity.
2.1.4. The LDP Sessions Table 3.1.4. The LDP Sessions Table
Each entry in this table represents a session between an LDP Entity Each entry in this table represents a session between an LDP Entity
and a Peer. and a Peer.
2.1.5. The LDP Adjacencies Table 3.1.5. The LDP Adjacencies Table
This is a table of all adjacencies between all LPD Entities and all This is a table of all adjacencies between all LPD Entities and all
LDP Peers. A Session may have one or more adjacencies. LDP Peers. A Session may have one or more adjacencies.
2.1.6. The LDP Label Information Base (LIB) Table 3.1.6. The LDP Label Information Base (LIB) Table
TBD. Some potential objects: incoming label, outgoing label, and the TBD. Some potential objects: incoming label, outgoing label, and the
mid. mid.
2.2. The LDP Notifications Group 3.2. The LDP Notifications Group
2.2.1. LDP Notifications 3.2.1. LDP Notifications
Currently, there is one notification which will be sent when an LDP Currently, there is one notification which will be sent when an LDP
attempts to initialize the same session beyond the configured attempts to initialize the same session beyond the configured
threshold. threshold.
3. MPLS Label Distribution Protocol MIB Definitions 4. MPLS Label Distribution Protocol MIB Definitions
MPLS-LDP-MIB DEFINITIONS ::= BEGIN MPLS-LDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
experimental, experimental,
Integer32, Counter32, Unsigned32 Integer32, Counter32, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeInterval TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex
FROM IF-MIB
AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
; ;
mplsLdpMIB MODULE-IDENTITY mplsLdpMIB MODULE-IDENTITY
LAST-UPDATED "9808261200Z" -- August 26, 1998 LAST-UPDATED "9906301200Z" -- June 30, 1999
ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (joanc@baynetworks.com) "Joan Cucchiara (joan@ironbridgenetworks.com)
Bay Networks IronBridge Networks
Hans Sjostrand (hans.sjostrand@etx.ericsson.se) Hans Sjostrand (hans.sjostrand@etx.ericsson.se)
Ericsson Ericsson
James V. Luciani (luciani@baynetworks.com) James V. Luciani (luciani@baynetworks.com)
Bay Networks" Nortel Networks"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for the "This MIB contains managed object definitions for the
Multiprotocol Label Switching, Label Distribution Multiprotocol Label Switching, Label Distribution
Protocol, LDP, as defined in draft-ietf-mpls-ldp-01.txt." Protocol, LDP, as defined in draft-ietf-mpls-ldp-04.txt."
::= { experimental 9876 } -- to be assigned ::= { experimental 9876 } -- to be assigned
--******************************************************************** --********************************************************************
-- MPLS LDP Textual Conventions -- MPLS LDP Textual Conventions
--******************************************************************** --********************************************************************
--
MplsLdpIANAAddrFamily ::= TEXTUAL-CONVENTION MplsLsrIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An address family. Values are defined in Assigned Numbers, "The Label Switch Router (LSR) identifier
RFC1700. Note that not all these values make sense in all is the first 4 bytes or the IP Address component
contexts where this type is used in this MIB, but they are of the Label Distribution Protocol (LDP) identifier."
included for completeness." SYNTAX OCTET STRING (SIZE (4))
REFERENCE
"Assigned Numbers, RFC1700, ADDRESS FAMILY NUMBERS"
SYNTAX INTEGER {
other(0),
ipV4(1),
ipV6(2),
nsap(3),
hdlc(4),
bbn1822(5),
ieee802(6),
e163(7),
e164(8),
f69(9),
x121(10),
ipx(11),
appleTalk(12),
decnetIV(13),
banyanVines(14),
e164WithNsap(15)
}
MplsLdpGenAddr ::= TEXTUAL-CONVENTION MplsLdpGenAddr ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of an network layer or data link layer address." "The value of an network layer or data link layer address."
SYNTAX OCTET STRING (SIZE (0..60)) SYNTAX OCTET STRING (SIZE (0..64))
MplsLdpIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The LDP identifier is a six octet quantity
which is used to identify an Label Switch Router
(LSR) label space.
The first four octets encode an IP address
assigned to the LSR, and the last two octets
identify a specific label space within the LSR."
SYNTAX OCTET STRING (SIZE (6))
AtmVpIdentifier ::= TEXTUAL-CONVENTION AtmVpIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VPI value for a VPL. The value VPI=0 is not "The VPI value for a VPL. The value VPI=0 is not
used for a VPL not associated with a VCL. For ATM used for a VPL not associated with a VCL. For ATM
UNIs supporting VPCs the VPI value ranges from 1 UNIs supporting VPCs the VPI value ranges from 1
to 255. For ATM UNIs supporting VCCs the VPI value to 255. For ATM UNIs supporting VCCs the VPI value
ranges from 0 to 255. The maximum VPI value ranges from 0 to 255. The maximum VPI value
cannot exceed the value allowable by cannot exceed the value allowable by
atmInterfaceMaxVpiBits defined in ATM-MIB." atmInterfaceMaxVpiBits defined in ATM-MIB."
SYNTAX Unsigned32 (0..4095) SYNTAX Unsigned32 (0..4095)
AtmVcIdentifier ::= TEXTUAL-CONVENTION AtmVcIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VCI value for a VCL. The maximum VCI value "The VCI value for a VCL. The maximum VCI value
cannot exceed the value allowable by cannot exceed the value allowable by
atmInterfaceMaxVciBits defined in ATM-MIB." atmInterfaceMaxVciBits defined in ATM-MIB."
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
-- Top-level structure of the MIB -- Top-level structure of the MIB (the following is proposed)
mpls OBJECT IDENTIFIER ::= { mplsProtocols }
mplsProtocols OBJECT IDENTIFIER ::= { mplsLdpObjects }
-- under mplsProtocols will be LDP, CR-LDP,
-- and other MPLS "Protocols".
mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 }
mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 }
mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 }
--******************************************************************** --****************************************************************
-- MPLS LDP Objects -- MPLS LDP Objects
--******************************************************************** --****************************************************************
mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 }
mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 }
--
-- The MPLS Label Distribution Protocol Label Switch Router Objects
--
mplsLdpLsrID OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The LSR's Identifier."
::= { mplsLdpLsrObjects 1 }
mplsLdpLsrLoopDetectionPresent OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A indication of whether this LSR supports
loop detection. A value of 'true' indicates
this LSR does support loop detection. A value
of 'false' indicates this LSR does not support
loop detection."
::= { mplsLdpLsrObjects 2 }
mplsLdpLsrLoopDetectionAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To enable loop detection the value of
this object should be 'enabled(1)'.
Otherwise, to turn off loop detection,
set this value to 'disabled(2)'."
::= { mplsLdpLsrObjects 3 }
mplsLdpLsrPathVectorLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object only has meaning if
mplsLdpLsrLoopDetectionPresent has
the value of 'true'.
The value of this object represents the
limit of path vectors which this LSR uses
to treat the message as if it had
traversed a loop."
::= { mplsLdpLsrObjects 4 }
mplsLdpLsrHopCountLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object only has meaning if
mplsLdpLsrLoopDetectionPresent has
the value of 'true'.
The value of this object represents the
limit on the Hop Count which this LSR uses
to treat the message as if it had
traversed a loop."
::= { mplsLdpLsrObjects 5 }
mplsLdpLsrLoopPreventionPresent OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A indication of whether this LSR supports
loop prevention. A value of 'true' indicates
this LSR does support loop prevention. A value
of 'false' indicates this LSR does not support
loop prevention."
::= { mplsLdpLsrObjects 6 }
mplsLdpLsrLoopPreventionAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To enable loop prevention the value of
this object should be 'enabled(1)'.
Otherwise, to turn off loop prevention,
set this value to 'disabled(2)'."
::= { mplsLdpLsrObjects 7 }
mplsLdpLsrLabelRetentionMode OBJECT-TYPE
SYNTAX INTEGER {
conservative(1),
liberal(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The LSR can be configured to use either
conservative or liberal label retention mode.
If the value of this object is conservative(1)
then advertized label mappings are retained
only if they will be used to forward packets,
i.e. if label came from a valid next hop.
If the value of this object is liberal(2)
then all advertized label mappings are retained
whether they are from a valid next hop or not."
::= { mplsLdpLsrObjects 8 }
-- --
-- The MPLS Label Distribution Protocol Entity Table -- The MPLS Label Distribution Protocol Entity Table
-- --
mplsLdpEntityTable OBJECT-TYPE mplsLdpEntityTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityEntry SYNTAX SEQUENCE OF MplsLdpEntityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about the "This table contains information about the
MPLS Label Distribution Protocol Entities which MPLS Label Distribution Protocol Entities which
exist on this LSR." exist on this Label Switch Router (LSR)."
::= { mplsLdpEntityObjects 1 } ::= { mplsLdpEntityObjects 1 }
mplsLdpEntityEntry OBJECT-TYPE mplsLdpEntityEntry OBJECT-TYPE
SYNTAX MplsLdpEntityEntry SYNTAX MplsLdpEntityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents an LDP entity. "An entry in this table represents an LDP entity.
An entry can be created by a network administrator An entry can be created by a network administrator
or by an SNMP agent as instructed by LDP." or by an SNMP agent as instructed by LDP.
INDEX { mplsLdpEntityIndex }
An LPD Entity is uniquely indexed by its LPD
Identifier."
INDEX { mplsLdpEntityID }
::= { mplsLdpEntityTable 1 } ::= { mplsLdpEntityTable 1 }
MplsLdpEntityEntry ::= SEQUENCE { MplsLdpEntityEntry ::= SEQUENCE {
mplsLdpEntityIndex Integer32, mplsLdpEntityID MplsLdpIdentifier,
mplsLdpEntityConfId OCTET STRING, mplsLdpEntityLabelSpaceType INTEGER,
mplsLdpEntityConfDefVpi AtmVpIdentifier, mplsLdpEntityDefVpi AtmVpIdentifier,
mplsLdpEntityConfDefVci AtmVcIdentifier, mplsLdpEntityDefVci AtmVcIdentifier,
mplsLdpEntityConfWellKnownDiscoveryPort Unsigned32, mplsLdpEntityUnlabTrafVpi AtmVpIdentifier,
mplsLdpEntityConfMtu Integer32, mplsLdpEntityUnlabTrafVci AtmVcIdentifier,
mplsLdpEntityConfKeepAliveHoldTimer Integer32, mplsLdpEntityMergeCapability INTEGER,
mplsLdpEntityLoopDetection TruthValue, mplsLdpEntityVcDirectionality INTEGER,
mplsLdpEntityLoopPrevention TruthValue, mplsLdpEntityWellKnownDiscoveryPort Unsigned32,
mplsLdpEntityMtu Integer32,
mplsLdpEntityKeepAliveHoldTimer Integer32,
mplsLdpEntityFailedInitSessionThreshold Integer32, mplsLdpEntityFailedInitSessionThreshold Integer32,
mplsLdpEntityLabelDistributionMethod INTEGER,
mplsLdpEntityRowStatus RowStatus mplsLdpEntityRowStatus RowStatus
} }
mplsLdpEntityID OBJECT-TYPE
mplsLdpEntityIndex OBJECT-TYPE SYNTAX MplsLdpIdentifier
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally arbitrary, but unique identifier "The LDP identifier which uniquely identifies
for this entity. An agent assigns a unique the LDP Entity. This is s six octet quantity
identifier when the row is created." which is used to identify an Label Switch Router
(LSR) label space.
The first four octets encode an IP address
assigned to the LSR, and the last two octets
identify a specific label space within the
LSR."
REFERENCE
"LDP Specification, Section on LDP Identifiers."
::= { mplsLdpEntityEntry 1 } ::= { mplsLdpEntityEntry 1 }
mplsLdpEntityConfId OBJECT-TYPE mplsLdpEntityLabelSpaceType OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (6)) SYNTAX INTEGER {
unknown(1),
perInterface(2),
perPlatform(3)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP identifier of this LDP Entity." "The type of label spaces associated with this
LDP Entity. The values are
'unknown(1)' The type of label space is
not known.
'perInterface(2)' The type of label space is
tied to an interface.
'perPlatform(3)' The type of label space is
tied to the platform."
REFERENCE
"LDP Specification, Section on Label Spaces."
::= { mplsLdpEntityEntry 2 } ::= { mplsLdpEntityEntry 2 }
mplsLdpEntityConfDefVpi OBJECT-TYPE mplsLdpEntityDefVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Default VPI value used in the label for the default "The Default VPI value used in the label for the default
VPI." VPI."
::= { mplsLdpEntityEntry 3 } ::= { mplsLdpEntityEntry 3 }
mplsLdpEntityDefVci OBJECT-TYPE
mplsLdpEntityConfDefVci OBJECT-TYPE
SYNTAX AtmVcIdentifier SYNTAX AtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Default VCI value used in the label for the default "The Default VCI value used in the label for the default
VCI." VCI."
::= { mplsLdpEntityEntry 4 } ::= { mplsLdpEntityEntry 4 }
mplsLdpEntityConfWellKnownDiscoveryPort OBJECT-TYPE mplsLdpEntityUnlabTrafVpi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The well known LDP Discovery Port." "VPI value of the VCC supporting unlabeled traffic."
DEFVAL { 0 }
::= { mplsLdpEntityEntry 5 } ::= { mplsLdpEntityEntry 5 }
mplsLdpEntityConfMtu OBJECT-TYPE mplsLdpEntityUnlabTrafVci OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX AtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum transmission unit (MTU) that was configured "VCI value of the VCC supporting unlabeled traffic."
for this entity." DEFVAL { 31 }
::= { mplsLdpEntityEntry 6 } ::= { mplsLdpEntityEntry 6 }
mplsLdpEntityConfKeepAliveHoldTimer OBJECT-TYPE mplsLdpEntityMergeCapability OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX INTEGER {
UNITS "seconds" noMerge(0),
vpMerge(1),
vcMerge(2),
vpVcMerge(3)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The two octet value which is the proposed keep alive hold "Sets the merge capability for this LDP entity."
timer for this LDP Entity." REFERENCE
"draft-ietf-mpls-ldp-04.txt, Section 3.5.3"
::= { mplsLdpEntityEntry 7 } ::= { mplsLdpEntityEntry 7 }
mplsLdpEntityLoopDetection OBJECT-TYPE mplsLdpEntityVcDirectionality OBJECT-TYPE
SYNTAX TruthValue SYNTAX INTEGER {
bidirectional(1),
unidirectional(2)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value of true (1) indicates that Loop Detection is 'on' "Sets the VC directionality for this LDP entity."
for this entity, a value of false (2) indicates that Loop REFERENCE
Detection is off." "draft-ietf-mpls-ldp-04.txt, Section 3.5.3"
::= { mplsLdpEntityEntry 8 } ::= { mplsLdpEntityEntry 8 }
mplsLdpEntityLoopPrevention OBJECT-TYPE mplsLdpEntityWellKnownDiscoveryPort OBJECT-TYPE
SYNTAX TruthValue SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value of true(1), indicates that this LDP entity has "The well known LDP Discovery Port."
loop prevention via Diffusion on. A value of false(2),
indicates that loop prevention via Diffusion is off."
::= { mplsLdpEntityEntry 9 } ::= { mplsLdpEntityEntry 9 }
mplsLdpEntityMtu OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum transmission unit (MTU) that was configured
for this entity."
::= { mplsLdpEntityEntry 10 }
mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE
SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The two octet value which is the proposed keep alive hold
timer for this LDP Entity."
::= { mplsLdpEntityEntry 11 }
mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When attempting to establish a session with a "When attempting to establish a session with a
given Peer, the given LDP Entity should given Peer, the given LDP Entity should
send out a notification when exceeding this threshold. send out a notification when exceeding this threshold.
A value of 0 (zero) for this object A value of 0 (zero) for this object
indicates that the threshold is infinity. indicates that the threshold is infinity.
In other words, a notification will not In other words, a notification will not
be sent if the value of this object is 0 (zero)." be sent if the value of this object is 0 (zero)."
::= { mplsLdpEntityEntry 10 } ::= { mplsLdpEntityEntry 12 }
mplsLdpEntityLabelDistributionMethod OBJECT-TYPE
SYNTAX INTEGER {
downstreamOnDemand(1),
downstreamUnsolicited(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For any given LDP session, the method of
label distribution must be specified."
REFERENCE
"draft-ietf-mpls-arch-04.txt [20]."
::= { mplsLdpEntityEntry 13 }
mplsLdpEntityRowStatus OBJECT-TYPE mplsLdpEntityRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "An object that allows entries in this table to
and deleted using the RowStatus convention." be created and deleted using the
REFERENCE RowStatus convention."
"Textual Conventions for Version 2 of the Simple Network ::= { mplsLdpEntityEntry 14 }
Management Protocol (SNMPv2), RFC1903."
::= { mplsLdpEntityEntry 11 }
-- --
-- The MPLS LDP Entity Configurable ATM Label Range Table -- The MPLS LDP Entity Configurable ATM Label Range Table
-- --
mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MPLS LDP Entity Configurable ATM Label Range Table. "The MPLS LDP Entity Configurable ATM Label Range Table.
The purpose of this table is to provide a mechanism The purpose of this table is to provide a mechanism
for specifying a contiguous range of vpi's with a contiguous for specifying a contiguous range of vpi's
range of vci's, or a 'label range' for LDP Entities. with a contiguous range of vci's, or a 'label range'
for LDP Entities.
LDP Entities which use ATM must have at least one LDP Entities which use ATM must have at least one
entry in this table." entry in this table."
::= { mplsLdpEntityObjects 2 } ::= { mplsLdpEntityObjects 2 }
mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE
SYNTAX MplsLdpEntityConfAtmLabelRangeEntry SYNTAX MplsLdpEntityConfAtmLabelRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in the LDP Entity Configurable ATM Label Range Table. "A row in the LDP Entity Configurable ATM Label
One entry in this table contains information Range Table. One entry in this table contains
on a single range of labels represented by information on a single range of labels
the configured Upper and Lower Bounds VPI/VCI pairs. represented by the configured Upper and Lower
Bounds VPI/VCI pairs.
NOTE: The ranges for a specific LDP Entity NOTE: The ranges for a specific LDP Entity
are UNIQUE and non-overlapping. For example, are UNIQUE and non-overlapping. For example,
for a specific LDP Entity index, there could for a specific LDP Entity index, there could
be one entry having ConfLowerBound vpi/vci == 0/32, and be one entry having ConfLowerBound vpi/vci == 0/32, and
ConfUpperBound vpi/vci == 0/100, and a second entry for this ConfUpperBound vpi/vci == 0/100, and a second entry for this
same interface with ConfLowerBound vpi/vci == 0/101 and same interface with ConfLowerBound vpi/vci == 0/101 and
ConfUpperBound vpi/vci == 0/200. However, there could not be ConfUpperBound vpi/vci == 0/200. However, there could not be
a third entry with ConfLowerBound vpi/vci == 0/200 and a third entry with ConfLowerBound vpi/vci == 0/200 and
ConfUpperBound vpi/vci == 0/300 because this label range overlaps ConfUpperBound vpi/vci == 0/300 because this label range overlaps
with the second entry (i.e. both entries now have 0/200). with the second entry (i.e. both entries now have 0/200).
A row will not be created unless a unique and non-overlapping A row will not be created unless a unique and non-overlapping
range is specified. Thus, row creation implies a one-shot range is specified. Thus, row creation implies a one-shot
row creation of LDP EntityIndex and ConfLowerBound vpi/vci and row creation of LDP EntityID and ConfLowerBound vpi/vci and
ConfUpperBound vpi/vci. At least one label range entry ConfUpperBound vpi/vci. At least one label range entry
for a specific LDP Entity MUST include the default VPI/VCI for a specific LDP Entity MUST include the default VPI/VCI
values denoted in the LDP Entity Table." values denoted in the LDP Entity Table."
INDEX { mplsLdpEntityIndex, INDEX { mplsLdpEntityID,
mplsLdpEntityConfAtmLabelRangeLowerBoundVPI, mplsLdpEntityConfAtmLabelRangeLowerBoundVPI,
mplsLdpEntityConfAtmLabelRangeLowerBoundVCI } mplsLdpEntityConfAtmLabelRangeLowerBoundVCI }
::= { mplsLdpEntityConfAtmLabelRangeTable 1 } ::= { mplsLdpEntityConfAtmLabelRangeTable 1 }
MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE {
mplsLdpEntityConfAtmLabelRangeLowerBoundVPI AtmVpIdentifier, mplsLdpEntityConfAtmLabelRangeLowerBoundVPI AtmVpIdentifier,
mplsLdpEntityConfAtmLabelRangeLowerBoundVCI AtmVcIdentifier, mplsLdpEntityConfAtmLabelRangeLowerBoundVCI AtmVcIdentifier,
mplsLdpEntityConfAtmLabelRangeUpperBoundVPI AtmVpIdentifier, mplsLdpEntityConfAtmLabelRangeUpperBoundVPI AtmVpIdentifier,
mplsLdpEntityConfAtmLabelRangeUpperBoundVCI AtmVcIdentifier, mplsLdpEntityConfAtmLabelRangeUpperBoundVCI AtmVcIdentifier,
mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus
skipping to change at page 13, line 6 skipping to change at page 17, line 21
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum VCI number configured for this range." "The maximum VCI number configured for this range."
::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 }
mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "An object that allows entries in this
and deleted using the RowStatus convention." table to be created and deleted using
REFERENCE the RowStatus convention."
"Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2), RFC1903."
::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 }
-- --
-- The MPLS LDP Entity Statistics Table -- The MPLS LDP Entity Statistics Table
-- --
mplsLdpEntityStatsTable OBJECT-TYPE mplsLdpEntityStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 13, line 39 skipping to change at page 17, line 52
SYNTAX MplsLdpEntityStatsEntry SYNTAX MplsLdpEntityStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table contains statistical information "A row in this table contains statistical information
about an LDP Entity." about an LDP Entity."
AUGMENTS { mplsLdpEntityEntry } AUGMENTS { mplsLdpEntityEntry }
::= { mplsLdpEntityStatsTable 1 } ::= { mplsLdpEntityStatsTable 1 }
MplsLdpEntityStatsEntry ::= SEQUENCE { MplsLdpEntityStatsEntry ::= SEQUENCE {
mplsLdpEstablishedSessions Counter32,
mplsLdpAttemptedSessions Counter32 mplsLdpAttemptedSessions Counter32
} }
mplsLdpEstablishedSessions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total established sessions for
this LDP Entity."
::= { mplsLdpEntityStatsEntry 1 }
mplsLdpAttemptedSessions OBJECT-TYPE mplsLdpAttemptedSessions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total attempted sessions for "A count of the total attempted sessions for
this LDP Entity." this LDP Entity."
::= { mplsLdpEntityStatsEntry 2 } ::= { mplsLdpEntityStatsEntry 1 }
-- --
-- The MPLS LDP Peer Table -- The MPLS LDP Peer Table
-- --
mplsLdpPeerObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } mplsLdpPeerObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 }
mplsLdpPeerTable OBJECT-TYPE mplsLdpPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpPeerEntry SYNTAX SEQUENCE OF MplsLdpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about LDP peers which have been discovered "Information about LDP peers which have been discovered
by the LDP Entities that are managed by this agent." by the LDP Entities that are managed by this agent."
::= { mplsLdpPeerObjects 1 } ::= { mplsLdpPeerObjects 1 }
mplsLdpPeerEntry OBJECT-TYPE mplsLdpPeerEntry OBJECT-TYPE
SYNTAX MplsLdpPeerEntry SYNTAX MplsLdpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single Peer." "Information about a single Peer."
INDEX { mplsLdpEntityIndex, INDEX { mplsLdpEntityID,
mplsLdpPeerIndex } mplsLdpPeerIndex }
::= { mplsLdpPeerTable 1 } ::= { mplsLdpPeerTable 1 }
MplsLdpPeerEntry ::= SEQUENCE { MplsLdpPeerEntry ::= SEQUENCE {
mplsLdpPeerIndex Integer32, mplsLdpPeerIndex Unsigned32,
mplsLdpPeerId OCTET STRING, mplsLdpPeerID MplsLdpIdentifier,
mplsLdpPeerInternetworkAddrType MplsLdpIANAAddrFamily, mplsLdpPeerInternetworkAddrType AddressFamilyNumbers,
mplsLdpPeerInternetworkAddr MplsLdpGenAddr, mplsLdpPeerInternetworkAddr MplsLdpGenAddr,
mplsLdpPeerDefaultMtu Integer32, mplsLdpPeerDefaultMtu Integer32,
mplsLdpPeerKeepAliveHoldTimer Integer32, mplsLdpPeerKeepAliveHoldTimer Integer32,
mplsLdpPeerLabelDistributionMethod INTEGER,
mplsLdpPeerRowStatus RowStatus mplsLdpPeerRowStatus RowStatus
} }
mplsLdpPeerIndex OBJECT-TYPE mplsLdpPeerIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier for the LDP peer that is unique within the "An identifier for the LDP peer that is unique within the
scope of this agent." scope of this agent."
::= { mplsLdpPeerEntry 1 } ::= { mplsLdpPeerEntry 1 }
mplsLdpPeerId OBJECT-TYPE mplsLdpPeerID OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (6)) SYNTAX MplsLdpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP identifier of this LDP Peer." "The LDP identifier of this LDP Peer."
::= { mplsLdpPeerEntry 2 } ::= { mplsLdpPeerEntry 2 }
mplsLdpPeerInternetworkAddrType OBJECT-TYPE mplsLdpPeerInternetworkAddrType OBJECT-TYPE
SYNTAX MplsLdpIANAAddrFamily SYNTAX AddressFamilyNumbers
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the internetwork layer address of this "The type of the internetwork layer address of this
LDP peer. This object indicates how the value of LDP peer. This object indicates how the value of
mplsLdpPeerInternetworkAddr is to be interpreted." mplsLdpPeerInternetworkAddr is to be interpreted."
::= { mplsLdpPeerEntry 3 } ::= { mplsLdpPeerEntry 3 }
mplsLdpPeerInternetworkAddr OBJECT-TYPE mplsLdpPeerInternetworkAddr OBJECT-TYPE
SYNTAX MplsLdpGenAddr SYNTAX MplsLdpGenAddr
skipping to change at page 16, line 13 skipping to change at page 20, line 8
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The two octet unsigned non zero integer that indicates "The two octet unsigned non zero integer that indicates
the number of seconds that this Peer proposes for the the number of seconds that this Peer proposes for the
value of the KeepAlive Interval." value of the KeepAlive Interval."
::= { mplsLdpPeerEntry 6 } ::= { mplsLdpPeerEntry 6 }
mplsLdpPeerLabelDistributionMethod OBJECT-TYPE
SYNTAX INTEGER {
downstreamOnDemand(1),
downstreamUnsolicited(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For any given LDP session, the method of
label distribution must be specified."
REFERENCE
"draft-ietf-mpls-arch-05.txt [20]."
::= { mplsLdpPeerEntry 7 }
mplsLdpPeerRowStatus OBJECT-TYPE mplsLdpPeerRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "An object that allows entries in this table to be created
and deleted using the RowStatus convention." and deleted using the RowStatus convention."
REFERENCE ::= { mplsLdpPeerEntry 8 }
"Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2), RFC1903."
::= { mplsLdpPeerEntry 7 }
-- --
-- The MPLS LDP Peer Configurable ATM Label Range Table -- The MPLS LDP Peer Configurable ATM Label Range Table
-- --
mplsLdpPeerConfAtmLabelRangeTable OBJECT-TYPE mplsLdpPeerConfAtmLabelRangeTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpPeerConfAtmLabelRangeEntry SYNTAX SEQUENCE OF MplsLdpPeerConfAtmLabelRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 18, line 26 skipping to change at page 22, line 27
"The maximum VCI number configured for this range." "The maximum VCI number configured for this range."
::= { mplsLdpPeerConfAtmLabelRangeEntry 4 } ::= { mplsLdpPeerConfAtmLabelRangeEntry 4 }
mplsLdpPeerConfAtmLabelRangeRowStatus OBJECT-TYPE mplsLdpPeerConfAtmLabelRangeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "An object that allows entries in this table to be created
and deleted using the RowStatus convention." and deleted using the RowStatus convention."
REFERENCE
"Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2), RFC1903."
::= { mplsLdpPeerConfAtmLabelRangeEntry 5 } ::= { mplsLdpPeerConfAtmLabelRangeEntry 5 }
-- --
-- The MPLS LDP Sessions Table -- The MPLS LDP Sessions Table
-- --
mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 4 }
mplsLdpSessionTable OBJECT-TYPE mplsLdpSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionEntry SYNTAX SEQUENCE OF MplsLdpSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Sessions between the LDP Entities and "A table of Sessions between the LDP Entities and
LDP Peers." LDP Peers."
::= { mplsLdpSessionObjects 1 } ::= { mplsLdpSessionObjects 1 }
mplsLdpSessionEntry OBJECT-TYPE mplsLdpSessionEntry OBJECT-TYPE
SYNTAX MplsLdpSessionEntry SYNTAX MplsLdpSessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single session between an LDP Entity and LDP Peer." single session between an LDP Entity and LDP Peer."
INDEX { mplsLdpEntityIndex, INDEX { mplsLdpEntityID,
mplsLdpPeerIndex, mplsLdpPeerIndex,
mplsLdpSessionIndex mplsLdpSessionIndex
} }
::= { mplsLdpSessionTable 1 } ::= { mplsLdpSessionTable 1 }
MplsLdpSessionEntry ::= SEQUENCE { MplsLdpSessionEntry ::= SEQUENCE {
mplsLdpSessionIndex Integer32, mplsLdpSessionIndex Unsigned32,
mplsLdpSessionId OCTET STRING, mplsLdpSessionID MplsLdpIdentifier,
mplsLdpSessionProtocolVersion Integer32, mplsLdpSessionProtocolVersion Integer32,
mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval,
mplsLdpSessionRole INTEGER, mplsLdpSessionRole INTEGER,
mplsLdpSessionState INTEGER, mplsLdpSessionState INTEGER,
mplsLdpSessionAtmLabelRangeLowerBoundVPI AtmVpIdentifier, mplsLdpSessionAtmLabelRangeLowerBoundVPI AtmVpIdentifier,
mplsLdpSessionAtmLabelRangeLowerBoundVCI AtmVcIdentifier, mplsLdpSessionAtmLabelRangeLowerBoundVCI AtmVcIdentifier,
mplsLdpSessionAtmLabelRangeUpperBoundVPI AtmVpIdentifier, mplsLdpSessionAtmLabelRangeUpperBoundVPI AtmVpIdentifier,
mplsLdpSessionAtmLabelRangeUpperBoundVCI AtmVcIdentifier, mplsLdpSessionAtmLabelRangeUpperBoundVCI AtmVcIdentifier,
mplsLdpSessionRowStatus RowStatus mplsLdpSessionRowStatus RowStatus
} }
mplsLdpSessionIndex OBJECT-TYPE mplsLdpSessionIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An unique identifier for this entry such that it "An unique identifier for this entry such that it
identifies a specific LDP Session." identifies a specific LDP Session."
::= { mplsLdpSessionEntry 1 } ::= { mplsLdpSessionEntry 1 }
mplsLdpSessionId OBJECT-TYPE mplsLdpSessionID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(6)) SYNTAX MplsLdpIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP Session identifier." "The LDP Session identifier."
::= { mplsLdpSessionEntry 2 } ::= { mplsLdpSessionEntry 2 }
mplsLdpSessionProtocolVersion OBJECT-TYPE mplsLdpSessionProtocolVersion OBJECT-TYPE
SYNTAX Integer32(0..65535) SYNTAX Integer32(0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 21, line 33 skipping to change at page 25, line 22
"The maximum VCI number for this range." "The maximum VCI number for this range."
::= { mplsLdpSessionEntry 10 } ::= { mplsLdpSessionEntry 10 }
mplsLdpSessionRowStatus OBJECT-TYPE mplsLdpSessionRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "An object that allows entries in this table to be created
and deleted using the RowStatus convention." and deleted using the RowStatus convention."
REFERENCE
"Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2), RFC1903."
::= { mplsLdpSessionEntry 11 } ::= { mplsLdpSessionEntry 11 }
-- --
-- The MPLS LDP Hello Adjacency Table -- The MPLS LDP Hello Adjacency Table
-- --
mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 4 } mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 5 }
mplsLdpHelloAdjacencyTable OBJECT-TYPE mplsLdpHelloAdjacencyTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Hello Adjacencies for Sessions." "A table of Hello Adjacencies for Sessions."
::= { mplsLdpHelloAdjacencyObjects 1 } ::= { mplsLdpHelloAdjacencyObjects 1 }
mplsLdpHelloAdjacencyEntry OBJECT-TYPE mplsLdpHelloAdjacencyEntry OBJECT-TYPE
SYNTAX MplsLdpHelloAdjacencyEntry SYNTAX MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row represents a single LDP Hello Adjacency. "Each row represents a single LDP Hello Adjacency.
An LDP Session can have one or more Hello adjacencies." An LDP Session can have one or more Hello adjacencies."
INDEX { mplsLdpSessionIndex, INDEX { mplsLdpSessionIndex,
mplsLdpHelloAdjacencyIndex } mplsLdpHelloAdjacencyIndex }
::= { mplsLdpHelloAdjacencyTable 1 } ::= { mplsLdpHelloAdjacencyTable 1 }
skipping to change at page 22, line 16 skipping to change at page 25, line 50
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row represents a single LDP Hello Adjacency. "Each row represents a single LDP Hello Adjacency.
An LDP Session can have one or more Hello adjacencies." An LDP Session can have one or more Hello adjacencies."
INDEX { mplsLdpSessionIndex, INDEX { mplsLdpSessionIndex,
mplsLdpHelloAdjacencyIndex } mplsLdpHelloAdjacencyIndex }
::= { mplsLdpHelloAdjacencyTable 1 } ::= { mplsLdpHelloAdjacencyTable 1 }
MplsLdpHelloAdjacencyEntry ::= SEQUENCE { MplsLdpHelloAdjacencyEntry ::= SEQUENCE {
mplsLdpHelloAdjacencyIndex Integer32, mplsLdpHelloAdjacencyIndex Unsigned32,
mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval
} }
mplsLdpHelloAdjacencyIndex OBJECT-TYPE mplsLdpHelloAdjacencyIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier for the adjacency." "An identifier for the adjacency."
::= { mplsLdpHelloAdjacencyEntry 1 } ::= { mplsLdpHelloAdjacencyEntry 1 }
mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 23, line 43 skipping to change at page 27, line 26
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object." to this object."
::= { mplsLdpCompliances 1 } ::= { mplsLdpCompliances 1 }
-- units of conformance -- units of conformance
mplsLdpGeneralGroup OBJECT-GROUP mplsLdpGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLdpEntityIndex, mplsLdpLsrID,
mplsLdpEntityConfId, mplsLdpLsrLoopDetectionPresent,
mplsLdpEntityConfDefVpi, mplsLdpLsrLoopDetectionAdminStatus,
mplsLdpEntityConfDefVci, mplsLdpLsrPathVectorLimit,
mplsLdpEntityConfWellKnownDiscoveryPort, mplsLdpLsrHopCountLimit,
mplsLdpEntityConfMtu, mplsLdpLsrLoopPreventionPresent,
mplsLdpEntityConfKeepAliveHoldTimer, mplsLdpLsrLoopPreventionAdminStatus,
mplsLdpEntityLoopDetection, mplsLdpLsrLabelRetentionMode,
mplsLdpEntityLoopPrevention, mplsLdpEntityLabelSpaceType,
mplsLdpEntityDefVpi,
mplsLdpEntityDefVci,
mplsLdpEntityUnlabTrafVpi,
mplsLdpEntityUnlabTrafVci,
mplsLdpEntityMergeCapability,
mplsLdpEntityVcDirectionality,
mplsLdpEntityWellKnownDiscoveryPort,
mplsLdpEntityMtu,
mplsLdpEntityKeepAliveHoldTimer,
mplsLdpEntityFailedInitSessionThreshold, mplsLdpEntityFailedInitSessionThreshold,
mplsLdpEntityLabelDistributionMethod,
mplsLdpEntityRowStatus, mplsLdpEntityRowStatus,
mplsLdpEntityConfAtmLabelRangeLowerBoundVPI,
mplsLdpEntityConfAtmLabelRangeLowerBoundVCI,
mplsLdpEntityConfAtmLabelRangeUpperBoundVPI, mplsLdpEntityConfAtmLabelRangeUpperBoundVPI,
mplsLdpEntityConfAtmLabelRangeUpperBoundVCI, mplsLdpEntityConfAtmLabelRangeUpperBoundVCI,
mplsLdpEntityConfAtmLabelRangeRowStatus, mplsLdpEntityConfAtmLabelRangeRowStatus,
mplsLdpEstablishedSessions,
mplsLdpAttemptedSessions, mplsLdpAttemptedSessions,
mplsLdpPeerIndex, mplsLdpPeerID,
mplsLdpPeerId,
mplsLdpPeerInternetworkAddrType, mplsLdpPeerInternetworkAddrType,
mplsLdpPeerInternetworkAddr, mplsLdpPeerInternetworkAddr,
mplsLdpPeerDefaultMtu, mplsLdpPeerDefaultMtu,
mplsLdpPeerKeepAliveHoldTimer, mplsLdpPeerKeepAliveHoldTimer,
mplsLdpPeerLabelDistributionMethod,
mplsLdpPeerRowStatus, mplsLdpPeerRowStatus,
mplsLdpPeerConfAtmLabelRangeLowerBoundVPI,
mplsLdpPeerConfAtmLabelRangeLowerBoundVCI,
mplsLdpPeerConfAtmLabelRangeUpperBoundVPI, mplsLdpPeerConfAtmLabelRangeUpperBoundVPI,
mplsLdpPeerConfAtmLabelRangeUpperBoundVCI, mplsLdpPeerConfAtmLabelRangeUpperBoundVCI,
mplsLdpPeerConfAtmLabelRangeRowStatus, mplsLdpPeerConfAtmLabelRangeRowStatus,
mplsLdpSessionIndex,
mplsLdpSessionId,
mplsLdpSessionProtocolVersion, mplsLdpSessionProtocolVersion,
mplsLdpSessionKeepAliveHoldTimeRemaining, mplsLdpSessionKeepAliveHoldTimeRemaining,
mplsLdpSessionRole, mplsLdpSessionRole,
mplsLdpSessionState, mplsLdpSessionState,
mplsLdpSessionAtmLabelRangeLowerBoundVPI, mplsLdpSessionAtmLabelRangeLowerBoundVPI,
mplsLdpSessionAtmLabelRangeLowerBoundVCI, mplsLdpSessionAtmLabelRangeLowerBoundVCI,
mplsLdpSessionAtmLabelRangeUpperBoundVPI, mplsLdpSessionAtmLabelRangeUpperBoundVPI,
mplsLdpSessionAtmLabelRangeUpperBoundVCI, mplsLdpSessionAtmLabelRangeUpperBoundVCI,
mplsLdpSessionRowStatus, mplsLdpSessionRowStatus,
mplsLdpHelloAdjacencyIndex,
mplsLdpHelloAdjacencyHoldTimeRemaining mplsLdpHelloAdjacencyHoldTimeRemaining
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations over ATM." "Objects that apply to all MPLS LDP implementations over ATM."
::= { mplsLdpGroups 1 } ::= { mplsLdpGroups 1 }
mplsLdpNotificationsGroup NOTIFICATION-GROUP mplsLdpNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded } NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification(s) which an MPLS LDP implemention "The notification(s) which an MPLS LDP implemention
is required to implement." is required to implement."
::= { mplsLdpGroups 2 } ::= { mplsLdpGroups 2 }
END END
4. Acknowledgments 5. Revision History
This section should be removed when this document is published as an
RFC.
5.1. Changes from <draft-ietf-mpls-ldp-mib-00.txt>
Textual conventions were added for the LSR Identifier and the LDP
Identifier.
Top-level mib structure was added. The LDP MIB falls under a proposed
hierarchy of mpls.mplsProtocols.
The mib hierarchy within the LDP MIB was also changed. A new branch,
under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This
branch is mplsLdpLsrObjects. Currently, this contains several new
scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDectectionPresent,
mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit,
mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent,
mplsLdpLsrLoopPreventionAdminStatus, and
mplsLdpLsrLabelRetentionMode.
mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which
is the LDP Identifier used in Session establishment.
mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects
were removed from this table.
The following objects were added to the mplsLdpEntityTable:
mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi,
mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability,
mplsLdpEntityVcDirectionality, and
mplsLdpEntityLabelDistributionMethod.
The following objects were added to the mplsLdpPeerEntityTable:
mplsLdpPeerLabelDistributionMethod.
The following object was removed from the mplsLdpEntityStatsTable:
mplsLdpEntityEstablishedSessions.
The LIB table was added.
The following notifications were added.
References were added and revised.
6. TO DO List
This section should be removed when this document is published as an
RFC. This section outlines the next areas the authors intend to
address.
o The MIB should be enhanced support other L2 protocols (e.g.
Frame Relay).
o Update this draft to reflect the latest changes to draft-ietf-
mpls-ldp-05.txt (or later LDP drafts).
o Update the Introduction section of the draft to reflect all the
changes made to the LDP MIB.
o Fix conformance statements.
o Remove the following sections prior to final publication: IANA
Considerations Section, Revisions Section and this (TO DO List)
Section.
7. Acknowledgments
The authors would like to thank the following people: Leigh The authors would like to thank the following people: Leigh
McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Bay McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel
Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Networks, and Zoltan Takacs and Bo Augustsson from Ericsson.
5. References 8. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2271, Cabletron for Describing SNMP Management Frameworks", RFC 2571, April
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1999
January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", RFC 1155, of Management Information for TCP/IP-based Internets", STD
Performance Systems International, Hughes LAN Systems, May 1990 16, RFC 1155, May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
Performance Systems International, Hughes LAN Systems, March 1991 16, RFC 1212, March 1991
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [RFC1215] M. Rose, "A Convention for Defining Traps for use with the
RFC 1215, Performance Systems International, March 1991 SNMP", RFC 1215, March 1991
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
of Management Information for Version 2 of the Simple Network Rose, M., and S. Waldbusser, "Structure of Management
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Conventions for Version 2 of the Simple Network Management Protocol Rose, M., and S. Waldbusser, "Textual Conventions for
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., SMIv2", STD 58, RFC 2579, April 1999
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Statements for Version 2 of the Simple Network Management Protocol Rose, M., and S. Waldbusser, "Conformance Statements for
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., SMIv2", STD 58, RFC 2580, April 1999
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Management Protocol", RFC 1157, SNMP Research, Performance Systems Network Management Protocol", STD 15, RFC 1157, May 1990.
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, "Introduction to Community-based SNMPv2", RFC 1901, January
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1996.
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Mappings for Version 2 of the Simple Network Management Protocol "Transport Mappings for Version 2 of the Simple Network
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1906, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, Protocol (SNMP)", RFC 2572, April 1999
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC (USM) for version 3 of the Simple Network Management
2274, IBM T. J. Watson Research, January 1998. Protocol (SNMPv3)", RFC 2574, April 1999
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Operations for Version 2 of the Simple Network Management Protocol "Protocol Operations for Version 2 of the Simple Network
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1905, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco RFC 2573, April 1999
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management Protocol Access Control Model (VACM) for the Simple Network
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., Management Protocol (SNMP)", RFC 2575, April 1999
Cisco Systems, Inc., January 1998
[16] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
Considerations Section in RFCs", draft-iesg-iana-considerations- "Introduction to Version 3 of the Internet-standard Network
04.txt, IBM, UNINETT, May 1998. Management Framework", RFC 2570, April 1999
[17] Andersson, Loa, Doolan, P., Feldman, N., Fredette, A., and Thomas, [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA
R., "Label Distribution Protocol.", draft-ietf-mpls-ldp-01.txt, Bay Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October
Networks, Ennovate Networks, IBM, Bay Networks, cisco Systems March 1998
1998.
[18] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and [18] Andersson, Loa, Doolan, P., Feldman, N., Fredette, A., and Thomas,
A. Viswanathan., "A Framework for Multiprotocol Label Switching", B., "LDP Specification.", draft-ietf-mpls-ldp-04.txt, Nortel
Networks, Ennovate Networks, IBM, Nortel Networks, cisco Systems
May 1999.
[19] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and
A. Viswanathan, "A Framework for Multiprotocol Label Switching",
draft-ietf-mpls-framework-02.txt, Ascend Communications, Ennovate draft-ietf-mpls-framework-02.txt, Ascend Communications, Ennovate
Networks, IBM, Bay Networks, cisco Systems, November 1997. Networks, IBM, Bay Networks, cisco Systems, November 1997.
6. Security Considerations [20] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label
Switching Architecture", draft-ietf-mpls-arch-05.txt, cisco
Systems, Lucent Technologies, and IronBridge Networks, April 1999.
7. Authors' Addresses [21] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP",
draft-ietf-mpls-cr-ldp-01.txt, February 1999.
[22] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, Harvard University, March 1997
[23] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,
RFC 2026, Harvard University, October 1996
[24] Srinivansan, C., and A. Viswanathan, "MPLS Traffic Engineering
Management Information Base Using SMIv2", draft-ietf-mpls-te-mibs-
00.txt, Lucent Technologies, February 1999.
[25] Greene, M., J. Cucchiara, J. Luciani, "Definition of Managed
Objects for the NBMA Next Hop Resolution Protocol (NHRP)", draft-
ietf-ion-nhrp-mib-09.txt, May 1999.
9. Security Considerations
Assuming that secure network management (such as SNMP v3) is
implemented, the objects represented in this MIB do not pose a threat
to the security of the network.
10. Authors' Addresses
Joan Cucchiara Joan Cucchiara
Bay Networks IronBridge Networks
3 Federal Street 55 Hayden Ave., Suite 1000
Mail Stop: BL3-03 Lexington, MA 02421
Billerica, MA 01821 Phone: (781) 372-8236
Phone: (978) 916-8555 Email: joan@ironbridgenetworks.com
Email: joanc@baynetworks.com
Hans Sjostrand Hans Sjostrand
Ericsson Ericsson
Business Unit Datacom Networks and IP Services Business Unit Datacom Networks and IP Services
S-126 25 Stockholm, Sweden S-126 25 Stockholm, Sweden
Phone: +46 8 719 9960 Phone: +46 8 719 9960
Email: hans.sjostrand@etx.ericsson.se Email: hans.sjostrand@etx.ericsson.se
James V. Luciani James V. Luciani
Bay Networks Nortel Networks
3 Federal Street 3 Federal Street
Mail Stop: BL3-03 Mail Stop: BL3-03
Billerica, MA 01821 Billerica, MA 01821
Phone: (978) 916-4734 Phone: (978) 916-4734
Email: luciani@baynetworks.com Email: luciani@baynetworks.com
Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at page 31, line 5 skipping to change at page 34, line 20
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents 12. IANA Address Family Numbers MIB
1 The SNMP Management Framework ................................ 2 This section is copied verbatim from the draft-ietf-ion-nhrp-mib-
1.1 Object Definitions ......................................... 3 09.txt[]. This section will be removed in future versions of this
2 Structure of the MIB ......................................... 4 draft. This section was copied here to for convenience, as it is
2.1 The MPLS LDP General Group ................................. 4 IMPORTED into the LDP MIB.
2.1.1 The Label Distribution Protocol's Entity Table ........... 4
2.1.2 The Label Distribution Protocol's Entity Statistics This appendix defines the initial content of the IANA-ADDRESS-
Table ..................................................... 4 FAMILY-NUMBERS-MIB. This section should be removed from this
2.1.3 The LDP Peer Table ....................................... 4 document prior to its approval, at which time this MIB will be
2.1.4 The LDP Sessions Table ................................... 5 administered by IANA.
2.1.5 The LDP Adjacencies Table ................................ 5
2.1.6 The LDP Label Information Base (LIB) Table ............... 5 The branch for this MIB needs to be determined, and an appropriate
2.2 The LDP Notifications Group ................................ 5 number should be added where XXX is currently.
2.2.1 LDP Notifications ........................................ 5
3 MPLS Label Distribution Protocol MIB Definitions ............. 5 IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS ::= BEGIN
4 Acknowledgments .............................................. 26
5 References ................................................... 27 IMPORTS
6 Security Considerations ...................................... 29 MODULE-IDENTITY,
7 Authors' Addresses ........................................... 29 mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaAddressFamilyNumbers MODULE-IDENTITY
LAST-UPDATED "9905191200Z" -- May 19, 1999
ORGANIZATION "IANA"
CONTACT-INFO
"Postal: Internet Assigned Numbers Authority
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
USA
Tel: +1 310-822-1511
E-Mail: iana@isi.edu"
DESCRIPTION
"The MIB module defines the AddressFamilyNumbers
textual convention."
-- revision history
REVISION "9905191200Z" -- May 19, 1999
-- RFC-Editor assigns RFC xxxx
DESCRIPTION "Initial version, published as RFC xxxx."
::= { mib-2 XXX } -- to be assigned by IANA
AddressFamilyNumbers ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.
(The latest arrangements can be obtained by
contacting the IANA.)
The enumerations are described as:
other(0), -- none of the following
ipV4(1), -- IP Version 4
ipV6(2), -- IP Version 6
nsap(3), -- NSAP
hdlc(4), -- (8-bit multidrop)
bbn1822(5),
all802(6), -- (includes all 802 media
-- plus Ethernet 'canonical format')
e163(7),
e164(8), -- (SMDS, Frame Relay, ATM)
f69(9), -- (Telex)
x121(10), -- (X.25, Frame Relay)
ipx(11), -- IPX (Internet Protocol Exchange)
appletalk(12), -- Apple Talk
decnetIV(13), -- DEC Net Phase IV
banyanVines(14), -- Banyan Vines
e164withNsap(15),
-- (E.164 with NSAP format subaddress)
reserved(65535)
Requests for new values should be made to IANA via
email (iana@isi.edu)."
SYNTAX INTEGER {
other(0),
ipV4(1),
ipV6(2),
nsap(3),
hdlc(4),
bbn1822(5),
all802(6),
e163(7),
e164(8),
f69(9),
x121(10),
ipx(11),
appletalk(12),
decnetIV(13),
banyanVines(14),
e164withNsap(15),
reserved(65535)
}
END
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/