draft-ietf-mpls-ldp-mib-14.txt   rfc3815.txt 
Network Working Group J. Cucchiara Network Working Group J. Cucchiara
Internet-Draft Artel Request for Comments: 3815 Marconi Communications, Inc.
Expires February 2004 H. Sjostrand Category: Standards Track H. Sjostrand
IP Unplugged ipUnplugged
J. Luciani J. Luciani
Marconi Marconi Communications, Inc.
November 2003 June 2004
Definitions of Managed Objects for
the Multiprotocol Label Switching, Label Distribution Protocol (LDP)
<draft-ietf-mpls-ldp-mib-14.txt> Definitions of Managed Objects for the
Multiprotocol Label Switching (MPLS),
Label Distribution Protocol (LDP)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC 2026. Internet-Drafts are Internet community, and requests discussion and suggestions for
working documents of the Internet Engineering Task Force (IETF), its improvements. Please refer to the current edition of the "Internet
areas, and its working groups. Note that other groups may also Official Protocol Standards" (STD 1) for the standardization state
distribute working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
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 (2003). All Rights Reserved. Copyright (C) The Internet Society (2004).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for the Multiprotocol In particular, it describes managed objects for the Multiprotocol
Label Switching, Label Distribution Protocol (LDP). Label Switching, Label Distribution Protocol (LDP).
Table of Contents Table of Contents
1 Introduction ................................................. 4 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2 The Internet-Standard Management Framework ................... 4 2. The Internet-Standard Management Framework. . . . . . . . . . 3
3 Structure of the MIB Modules ................................. 5 3. Structure of the MIB Modules. . . . . . . . . . . . . . . . . 3
3.1 Overview ................................................... 5 3.1. Overview. . . . . . . . . . . . . . . . . . . . . . . . 3
3.2 Future Considerations ...................................... 5 3.2. Future Considerations . . . . . . . . . . . . . . . . . 4
3.3 Interface Indexing ......................................... 6 3.3. Interface Indexing. . . . . . . . . . . . . . . . . . . 4
3.4 Differences from the LDP Specification ..................... 6 3.4. Differences from the LDP Specification. . . . . . . . . 4
3.5 The MPLS-LDP-STD-MIB Module ................................ 7 3.5. The MPLS-LDP-STD-MIB Module . . . . . . . . . . . . . . 5
3.5.1 LDP Scalar Objects ....................................... 7 3.5.1. LDP Scalar Objects. . . . . . . . . . . . . . . 5
3.5.2 The LDP Entity Table ..................................... 7 3.5.2. The LDP Entity Table. . . . . . . . . . . . . . 6
3.5.2.1 Changing Values After Session Establishment ............ 8 3.5.2.1. Changing Values After Session
3.5.3 The LDP Entity Statistics Table .......................... 9 Establishment . . . . . . . . . . . . 6
3.5.4 The LDP Peer Table ....................................... 9 3.5.3. The LDP Entity Statistics Table . . . . . . . . 7
3.5.5 The LDP Session Table .................................... 10 3.5.4. The LDP Peer Table. . . . . . . . . . . . . . . 7
3.5.6 The LDP Session Statistics Table ......................... 10 3.5.5. The LDP Session Table . . . . . . . . . . . . . 8
3.5.7 The LDP Hello Adjacency Table ............................ 10 3.5.6. The LDP Session Statistics Table. . . . . . . . 8
3.5.8 The LDP LSP Table ........................................ 10 3.5.7. The LDP Hello Adjacency Table . . . . . . . . . 8
3.5.9 The FEC Table ............................................ 11 3.5.8. The LDP LSP Tables. . . . . . . . . . . . . . . 8
3.5.10 The LDP Session Peer Address Table ...................... 11 3.5.9. The FEC Tables. . . . . . . . . . . . . . . . . 9
3.6 LDP Notifications .......................................... 11 3.5.10. The LDP Session Peer Address Table. . . . . . . 9
3.7 LDP Notification Frequency ................................. 12 3.6. LDP Notifications . . . . . . . . . . . . . . . . . . . 9
4 MPLS Label Distribution Protocol MIB Definitions ............. 12 3.7. LDP Notification Frequency. . . . . . . . . . . . . . . 10
4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 66 4. MPLS Label Distribution Protocol MIB Definitions. . . . . . . 10
4.1.1 The LDP Entity ATM Table ................................. 66 4.1. The MPLS-LDP-ATM-STD-MIB Module . . . . . . . . . . . . 60
4.1.2 The LDP Entity ATM Label Range Table ..................... 66 4.1.1. The LDP Entity ATM Table. . . . . . . . . . . . 61
4.1.3 The LDP ATM Session Table ................................ 66 4.1.2. The LDP Entity ATM Label Range Table. . . . . . 61
4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 83 4.1.3. The LDP ATM Session Table . . . . . . . . . . . 61
4.2.1 The LDP Entity Frame Relay Table ......................... 83 4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module . . . . . . . . 77
4.2.2 The LDP Entity Frame Relay Label Range Table ............. 84 4.2.1. The LDP Entity Frame Relay Table. . . . . . . . 77
4.2.3 The LDP Frame Relay Session Table ........................ 84 4.2.2. The LDP Entity Frame Relay Label Range Table. . 77
4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 98 4.2.3. The LDP Frame Relay Session Table . . . . . . . 77
5 Revision History ............................................. 107 4.3. The MPLS-LDP-GENERIC-STD-MIB Module . . . . . . . . . . 91
5.1 Changes from <draft-ietf-mpls-ldp-mib-13.txt> .............. 107 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 98
5.2 Changes from <draft-ietf-mpls-ldp-mib-12.txt> .............. 107 6. References. . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.3 Changes from <draft-ietf-mpls-ldp-mib-11.txt> .............. 107 6.1. Normative References. . . . . . . . . . . . . . . . . . 98
5.4 Changes from <draft-ietf-mpls-ldp-mib-10.txt> .............. 108 6.2. Informative References. . . . . . . . . . . . . . . . .100
5.5 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 108 7. Security Considerations . . . . . . . . . . . . . . . . . . .100
5.5.1 Changes based on MIB Doctor Review Comments .............. 108 7.1. Security Considerations for MPLS-LDP-STD-MIB. . . . . .100
5.6 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 113 7.2. Security Considerations for MPLS-LDP-ATM-STD-MIB. . . .101
5.7 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 115 7.3. Security Considerations for
5.8 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 116 MPLS-LDP-FRAME-RELAY-STD-MIB. . . . . . . . . . . . . .102
5.9 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 117 7.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB. .103
5.10 Changes from <draft-ietf-mpls-ldp-mib-04.txt> ............. 119 7.5. Additional Security Considerations. . . . . . . . . . .103
5.11 Changes from <draft-ietf-mpls-ldp-mib-03.txt> ............. 121 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . .104
5.12 Changes from <draft-ietf-mpls-ldp-mib-02.txt> ............. 122 8.1. IANA Considerations for MPLS-LDP-STD-MIB. . . . . . . .104
5.13 Changes from <draft-ietf-mpls-ldp-mib-01.txt> ............. 123 8.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB. . . . . .104
5.14 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 124 8.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB. .104
6 Acknowledgments .............................................. 125 8.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB. . . .104
7 Normative References ......................................... 127 9. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . .105
8 Informative References ....................................... 129 10. Full Copyright Statement. . . . . . . . . . . . . . . . . . .106
9 Security Considerations ...................................... 129
9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 129
9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 130
9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ... 131
9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 132
9.5 Additional Security Considerations ......................... 132
10 IANA Considerations ......................................... 133
10.1 IANA Considerations for MPLS-LDP-STD-MIB .................. 133
10.2 IANA Considerations for MPLS-LDP-ATM-STD-MIB .............. 133
10.3 IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ...... 133
10.4 IANA Considerations for MPLS-LDP-GENERIC-STD-MIB .......... 134
11 Intellectual Property Notice ................................ 134
12 Authors' Addresses .......................................... 134
13 Full Copyright Statement .................................... 135
1. Introduction 1. Introduction
This document defines 4 MIB Modules which together support the This document defines 4 MIB Modules which together support the
configuration and monitoring of the Label Distribution Protocol configuration and monitoring of the Label Distribution Protocol
(LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type
of Multiprotocol Label Switching (MPLS) protocols described in of Multiprotocol Label Switching (MPLS) protocols described in
[RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an
operator to configure LDP sessions using 3 different Layer 2 media. operator to configure LDP sessions using 3 different Layer 2 media.
The Layer 2 media supported by the MIB Modules are Ethernet, ATM and The Layer 2 media supported by the MIB Modules are Ethernet, ATM and
Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035]. Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
For an introduction to the concepts of MPLS, see [RFC3031]. For
further on LDP refer to [RFC3037] and [RFC3215].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
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. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 5, line 24 skipping to change at page 3, line 46
defines objects which are common to all LDP implementations. The defines objects which are common to all LDP implementations. The
MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space
objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB
defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with
the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer
2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB. 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB.
The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of
the Layer 2 MIB Modules MUST be implemented by an Agent developer on the Layer 2 MIB Modules MUST be implemented by an Agent developer on
an Label Switching Router (LSR) or Label Edge Router (LER). As an an Label Switching Router (LSR) or Label Edge Router (LER). As an
example, if an Label Switching Router (LSR) or Label Edge Router example, if a Label Switching Router (LSR) or Label Edge Router (LER)
(LER) implementation intends to support LDP utilizing a Layer 2 of implementation intends to support LDP utilizing a Layer 2 of
Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB
Modules MUST implemented. If an LSR/LER implementation intends to Modules MUST implemented. If an LSR/LER implementation intends to
support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB
Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an
LSR/LER implementation intends to support LDP utilizing a Layer 2 of LSR/LER implementation intends to support LDP utilizing a Layer 2 of
FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME- FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME-
RELAY-STD-MIB Module MUST be implemented. An LDP implementation that RELAY-STD-MIB Module MUST be implemented. An LDP implementation that
utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST
support all 4 MIB Modules. Each of the Modules will be discussed in support all 4 MIB Modules. Each of the Modules will be discussed in
detail in the following sections. detail in the following sections.
skipping to change at page 6, line 33 skipping to change at page 5, line 5
are documented here. are documented here.
The first difference is that the LDP Entity Table contains some The first difference is that the LDP Entity Table contains some
DEFVAL clauses which are not specified explicitly in the LDP DEFVAL clauses which are not specified explicitly in the LDP
Specification. These values, although not documented in the LDP Specification. These values, although not documented in the LDP
Specification, are widely used by existing LDP MIB implementations Specification, are widely used by existing LDP MIB implementations
and thus, have been adopted within this MPLS-LDP-STD-MIB module. and thus, have been adopted within this MPLS-LDP-STD-MIB module.
Please note, they can certainly be changed during row creation or a Please note, they can certainly be changed during row creation or a
subsequent SET request. subsequent SET request.
A second difference is the mplsLdpEntityConfGenericLRTable in the A second difference is the mplsLdpEntityGenericLRTable in the MPLS-
MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a LDP-GENERIC-STD-MIB Module. This table, although provided as a way
way to reserve a range of generic labels, does not exist in the LDP to reserve a range of generic labels, does not exist in the LDP
Specification. It was added to the MIB due to a request from the Specification. It was added to the MIB due to a request from the
working group and because this table was considered useful for working group and because this table was considered useful for
reserving a range of generic labels. reserving a range of generic labels.
The third difference is documented by the TEXTUAL-CONVENTION, The third difference is documented by the TEXTUAL-CONVENTION,
MplsAtmVcIdentifier which is in the MPLS-TC-STD-MIB [MPLSTCMIB]. MplsAtmVcIdentifier which is in the MPLS-TC-STD-MIB [RFC3811]. This
This TC was added to restrict vci values to be greater than 31 as TC was added to restrict vci values to be greater than 31 as
described in RFC 3035 [RFC3035]. described in RFC 3035 [RFC3035].
3.5. The MPLS-LDP-STD-MIB Module 3.5. The MPLS-LDP-STD-MIB Module
This MIB Module contains objects which are common to all LDP This MIB Module contains objects which are common to all LDP
implementations. This MIB Module MUST always be implemented along implementations. This MIB Module MUST always be implemented along
with one or more of the Layer 2 MIB Modules. with one or more of the Layer 2 MIB Modules. This MIB Module IMPORTS
IndexInteger and IndexIntegerNextFree TEXTUAL-CONVENTIONs from
[RFC3289], and IMPORTS InetAddressPrefixLength, InetAddressType,
InetAddressInetPortNumber TEXTUAL-CONVENTIONs from [RFC3291].
This table allows the Label Edge Router (LER) or the Label Switching The mplsLdpEntityTable table allows the Label Edge Router (LER) or
Router (LSR) to initiate and/or receive requests to establish LDP the Label Switching Router (LSR) to initiate and/or receive requests
sessions. As the LDP protocol distributes labels and establishes to establish LDP sessions. As the LDP protocol distributes labels
sessions with Peers most of the tables in this module are populated and establishes sessions with Peers most of the tables in this module
by the agent as instructed by the LDP protocol. The exception is the are populated by the agent as instructed by the LDP protocol. The
mplsFecTable and the mplsLdpLspFecTable which can be configured by exception is the mplsFecTable and the mplsLdpLspFecTable which can be
the operator to specify Forwarding Equivalence Class information for configured by the operator to specify Forwarding Equivalence Class
an LSP. information for an LSP.
Some scalars and each table in the MPLS-LDP-STD-MIB Module is Some scalars and each table in the MPLS-LDP-STD-MIB Module are
described in the following subsections. described in the following subsections.
3.5.1. LDP Scalar Objects 3.5.1. LDP Scalar Objects
There are several scalar objects in the LDP MIB module. The There are several scalar objects in the LDP MIB module. The
mplsLdpLsrId is a read-only scalar object which reports Lable mplsLdpLsrId is a read-only scalar object which reports Label
Switching Router's (LSR's) Identifier. This MUST be a globally Switching Router's (LSR's) Identifier. This MUST be a globally
unique value, such as the 32-bit router ID assigned to the LSR. unique value, such as the 32-bit router ID assigned to the LSR.
The mplsLdpLsrLoopDetectionCapable scalar object denotes whether the The mplsLdpLsrLoopDetectionCapable scalar object denotes whether the
LSR is capable of supporting loop detection and if so, which form of LSR is capable of supporting loop detection and if so, which form of
loop detection. loop detection.
There are two LastChange scalar objects, mplsLdpEntityLastChange and There are two LastChange scalar objects, mplsLdpEntityLastChange and
mplsLdpPeerLastChange. These objects give an indication of there was mplsLdpPeerLastChange. These objects give an indication of there was
a change in the number of entries in the table, or if any of the a change in the number of entries in the table, or if any of the
skipping to change at page 8, line 30 skipping to change at page 6, line 46
information learned by that session must be discarded. The objects information learned by that session must be discarded. The objects
should then be modified, and session initialization started. should then be modified, and session initialization started.
Assuming that the configuration was done correctly, then a new Assuming that the configuration was done correctly, then a new
session will be created. session will be created.
For example, assume that an operator wishes to change the For example, assume that an operator wishes to change the
configuration of a Label Range which is used by a Session that has configuration of a Label Range which is used by a Session that has
already been established. The operator should change the already been established. The operator should change the
mplsLdpEntityAdminStatus to "disable(2)". Setting the mplsLdpEntityAdminStatus to "disable(2)". Setting the
mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be
torn down (i.e. this will signal to LDP that it should send out tear torn down (i.e., this will signal to LDP that it should send out tear
down messages for that session). Also, all information related to down messages for that session). Also, all information related to
that session should be removed from this MIB by the Agent. This that session should be removed from this MIB by the Agent. This
includes Peer information (i.e. relevant row in the mplsPeerTable) includes Peer information (i.e., relevant row in the mplsPeerTable)
and Session statistics (i.e. relevant row in the and Session statistics (i.e., relevant row in the
mplsLdpSessionTable). Also, if the MPLS-LSR-STD-MIB module [LSRMIB] mplsLdpSessionTable). Also, if the MPLS-LSR-STD-MIB module [RFC3813]
is implemented and the optional Mapping Table objects are is implemented and the optional Mapping Table objects are
implemented, then all information related to the LSPs in this session implemented, then all information related to the LSPs in this session
should be removed from these MIB modules. [For more information should be removed from these MIB modules. [For more information
please see the section on "The Mapping Tables".] At this point, the please see the section on "The Mapping Tables".] At this point, the
operator could modify the Label Range. Lastly, the operator should operator could modify the Label Range. Lastly, the operator should
set the mplsLdpEntityAdminStatus to "enable(1)". At this point set the mplsLdpEntityAdminStatus to "enable(1)". At this point
session initialization should occur. The LDP Entity goes through the session initialization should occur. The LDP Entity goes through the
Session Initialization in order to communicate the new Label Ranges Session Initialization in order to communicate the new Label Ranges
to the Peer and establish new LSPs. to the Peer and establish new LSPs.
skipping to change at page 9, line 39 skipping to change at page 7, line 47
configured in the mplsLdpEntityTable and the Peer's values are configured in the mplsLdpEntityTable and the Peer's values are
learned (and placed into the mplsLdpPeerTable). The learned (and placed into the mplsLdpPeerTable). The
mplsLdpSessionTable shows the values used in establishing the mplsLdpSessionTable shows the values used in establishing the
session. session.
One example, of when the Peer's values and the Session's values may One example, of when the Peer's values and the Session's values may
differ is with the Peer's Path Limit information. The Peer's Path differ is with the Peer's Path Limit information. The Peer's Path
Limit information is learned from the session initialization phase. Limit information is learned from the session initialization phase.
The actual value for the Path Vector Limit is the Peer's value and The actual value for the Path Vector Limit is the Peer's value and
may not be the same value that appears in the session. There could may not be the same value that appears in the session. There could
be a mismatch in this value between the Entity and the Peer. In the be a mismatch in this value between the Entity and the Peer. In the
event of a mismatch, then the session will use the Path Limit set by event of a mismatch, then the session will use the Path Limit set by
the Entity (and not the Peer). the Entity (and not the Peer).
The Peer Table information was placed in a separate table from the The Peer Table information was placed in a separate table from the
Session information to allow for a more comprehensive and coherent Session information to allow for a more comprehensive and coherent
MIB model. MIB model.
3.5.5. The LDP Session Table 3.5.5. The LDP Session Table
The LDP Session Table is a read-only table. Each entry in this table The mplsLdpSessionTable is a read-only table. Each entry in this
represents a single session between an LDP Entity and a Peer. The table represents a single session between an LDP Entity and a Peer.
mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. The mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry.
The information in this table is learned during session The information in this table is learned during session
establishment. NOTE: rows in this table will appear during session establishment. NOTE: rows in this table will appear during session
intialization. intialization.
3.5.6. The LDP Session Statistics Table 3.5.6. The LDP Session Statistics Table
The mplsLdpSessionStatsTable is a read-only table which contains The mplsLdpSessionStatsTable is a read-only table which contains
statistical information on sessions. This table AUGMENTS the statistical information on sessions. This table AUGMENTS the
mplsLdpPeerTable. mplsLdpPeerTable.
3.5.7. The LDP Hello Adjacency Table 3.5.7. The LDP Hello Adjacency Table
This is a table of all adjacencies between all LDP Entities and all This is a table of all adjacencies between all LDP Entities and all
LDP Peers. A Session may have one or more adjacencies. A session LDP Peers. A Session may have one or more adjacencies. A session
should not have zero adjacencies, because this indicates that the should not have zero adjacencies, because this indicates that the
session has lost contact with the Peer. A session which has zero session has lost contact with the Peer. A session which has zero
Hello Adjacencies should be removed. Hello Adjacencies should be removed.
3.5.8. The LDP LSP Table 3.5.8. The LDP LSP Tables
The Label Information Base (LIB) contains information about labels The Label Information Base (LIB) contains information about labels
learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e., all
currently defined MPLS protocols) is represented in the LSR MIB currently defined MPLS protocols) is represented in the LSR MIB
[LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls [RFC3813]. The LIB is represented by the LSR MIB's mplsXCTable (mpls
Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and
the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable
models the cross-connection of the incoming label with a specific models the cross-connection of the incoming label with a specific
outgoing label. The mplsInSegmentTable stores the incoming label's outgoing label. The mplsInSegmentTable stores the incoming label's
information, and the mplsOutSegmentTable stores the outgoing label's information, and the mplsOutSegmentTable stores the outgoing label's
information. information.
The LDP Session that created the LSP and the LSP's (incoming label, The LDP Session that created the LSP and the LSP's (incoming label,
outgoing label) pair along with other information is contained in the outgoing label) pair along with other information is contained in the
MPLS-LSR-STD-MIB module's mplsXCTable, the mplsInSegmentTable and the MPLS-LSR-STD-MIB module's mplsXCTable, the mplsInSegmentTable and the
skipping to change at page 11, line 22 skipping to change at page 9, line 24
mplsOutSegmentLdpLspTable, have been made optional in the conformance mplsOutSegmentLdpLspTable, have been made optional in the conformance
section of the MIB. They only need to be supported if the LSR MIBs section of the MIB. They only need to be supported if the LSR MIBs
mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are
implemented. implemented.
As discussed in the section, "Changing Values after Session As discussed in the section, "Changing Values after Session
Establishment", if a session is torn down, then all the information Establishment", if a session is torn down, then all the information
related to this session, must be removed from the both LDP MIB and, related to this session, must be removed from the both LDP MIB and,
if implemented, from the LSR MIB. if implemented, from the LSR MIB.
3.5.9. The FEC Table 3.5.9. The FEC Tables
The FEC Table is a table which contains FEC (Forwarding Equivalence The mplsLdpFecTable is a table which contains FEC (Forwarding
Class) information. Each entry/row represents a single FEC Element. Equivalence Class) information. Each entry/row represents a single
There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which FEC Element. There is also an LDP LSP FEC Table, mplsLdpLspFecTable,
associates FECs with the LSPs. which associates FECs with the LSPs.
3.5.10. The LDP Session Peer Address Table 3.5.10. The LDP Session Peer Address Table
The MPLS LDP Session Peer Address Table is a table which extends the The mplsLdpSessionPeerAddrTable is a table which extends the
mplsLdpSessionTable. This table is a read-only table which stores mplsLdpSessionTable. This table is a read-only table which stores
Addresses learned after session initialization via Address Message Addresses learned after session initialization via Address Message
advertisement. advertisement.
3.6. LDP Notifications 3.6. LDP Notifications
Currently, there are several notifications which are specific for Currently, there are several notifications which are specific for
LDP. These are described in this section. There are no objects LDP. These are described in this section. There are no objects
which enable or disable notifications from being generated. RFC 3413 which enable or disable notifications from being generated. RFC 3413
[RFC3413] contains MIB modules which can be implemented that will [RFC3413] contains MIB modules which can be implemented that will
skipping to change at page 12, line 22 skipping to change at page 10, line 18
The mplsLdpPathVectorLimitMismatch notification is generated when The mplsLdpPathVectorLimitMismatch notification is generated when
there is a mismatch in the Path Vector Limits between the Entity and there is a mismatch in the Path Vector Limits between the Entity and
Peer during session initialization. The session uses the value which Peer during session initialization. The session uses the value which
is configured as the Entity's Path Vector Limit. However, a is configured as the Entity's Path Vector Limit. However, a
notification should be generated to indicate that a mismatch notification should be generated to indicate that a mismatch
occurred. For further details, please see Section 3.5.3 of the LDP occurred. For further details, please see Section 3.5.3 of the LDP
Specification [RFC3036]. Specification [RFC3036].
The mplsLdpSessionUp and mplsLdpSessionDown notifications are The mplsLdpSessionUp and mplsLdpSessionDown notifications are
generated when there is an appropriate change in the generated when there is an appropriate change in the
mplsLdpSessionState object, e.g. when sessions change state (Up to mplsLdpSessionState object, e.g., when sessions change state (Up to
Down for the mplsLdpSessionDown notification, or Down to Up for the Down for the mplsLdpSessionDown notification, or Down to Up for the
mplsLdpSessionUp notification). There was discussion about combining mplsLdpSessionUp notification). There was discussion about combining
these two notifications into a single notification, however, some NMS these two notifications into a single notification, however, some NMS
applications can utilize two different notifications, rather than applications can utilize two different notifications, rather than
having to parse the varbind list of a single notification. For having to parse the varbind list of a single notification. For
example, the SessionDown is matched to a SessionUp notification more example, the SessionDown is matched to a SessionUp notification more
easily by some NMS applications, than having to parse a Varbind list easily by some NMS applications, than having to parse a Varbind list
in a SessionChange type of notification. in a SessionChange type of notification.
3.7. LDP Notification Frequency 3.7. LDP Notification Frequency
LDP Notifications are expected to be few in number when LDP is LDP Notifications are expected to be few in number when LDP is
ubiquitously deployed in a relatively stable network. A notification ubiquitously deployed in a relatively stable network. A notification
receiver, e.g. an NMS, that receives these notifications should not receiver, e.g., an NMS, that receives these notifications should not
be overwhelmed by the frequency of LDP notifications. If this be overwhelmed by the frequency of LDP notifications. If this
assertion proves to be inaccurate, then a throttling object to assertion proves to be inaccurate, then a throttling object to
throttle these notifications may be added to future versions of the throttle these notifications may be added to future versions of the
MPLS-LDP-STD-MIB. MPLS-LDP-STD-MIB.
4. MPLS Label Distribution Protocol MIB Definitions 4. MPLS Label Distribution Protocol MIB Definitions
MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
Integer32, Counter32, Unsigned32 Integer32, Counter32, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
RowStatus, TimeInterval, TruthValue, RowStatus, TimeInterval, TruthValue,
TimeStamp, StorageType TimeStamp, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InetAddressPrefixLength, InetAddressPrefixLength,
InetAddressType, InetAddressType,
InetAddress, InetAddress,
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB -- [RFC3291]
IndexInteger, IndexInteger,
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB FROM DIFFSERV-MIB -- [RFC3289]
mplsStdMIB, mplsStdMIB,
MplsLabelDistributionMethod, MplsLabelDistributionMethod,
MplsLdpIdentifier, MplsLdpIdentifier,
MplsLdpLabelType, MplsLdpLabelType,
MplsLspType, MplsLspType,
MplsLsrIdentifier, MplsLsrIdentifier,
MplsRetentionMode MplsRetentionMode
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsIndexType MplsIndexType
FROM MPLS-LSR-STD-MIB; FROM MPLS-LSR-STD-MIB; -- [RFC3813]
mplsLdpStdMIB MODULE-IDENTITY mplsLdpStdMIB MODULE-IDENTITY
LAST-UPDATED "200311181200Z" -- 18 November 2003 LAST-UPDATED "200406030000Z" -- June 3, 2004
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@mindspring.com)
Artel Marconi Communications, Inc.
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
Marconi Communications, Inc. Marconi Communications, Inc.
Working Group Chairs: Working Group Chairs:
George Swallow, email: swallow@cisco.com George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net" MPLS Working Group, email: mpls@uu.net"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2004). The
version of this MIB module is part of RFCXXX; see initial version of this MIB module was published
the RFC itself for full legal notices. in RFC 3815. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
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' document." Protocol, LDP' document."
REVISION "200311181200Z" -- 18 November 2003 REVISION "200406030000Z" -- June 3, 2004
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC 3815."
-- Please see the IANA Considerations Section.
-- The requested mplsStdMIB subId is 4, e.g.
-- ::= { mplsStdMIB 4 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB 4 }
--**************************************************************** --****************************************************************
mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 } mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 }
mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 } mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 }
mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 } mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP Objects -- MPLS LDP Objects
--**************************************************************** --****************************************************************
skipping to change at page 17, line 4 skipping to change at page 14, line 31
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 Label Switching Router (LSR) exist on this Label Switching Router (LSR)
or Label Edge Router (LER)." or Label Edge Router (LER)."
::= { mplsLdpEntityObjects 3 }
::= { mplsLdpEntityObjects 3 } mplsLdpEntityEntry OBJECT-TYPE
SYNTAX MplsLdpEntityEntry
mplsLdpEntityEntry OBJECT-TYPE MAX-ACCESS not-accessible
SYNTAX MplsLdpEntityEntry STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "An entry in this table represents an LDP entity.
DESCRIPTION An entry can be created by a network administrator
"An entry in this table represents an LDP entity. or by an SNMP agent as instructed by LDP."
An entry can be created by a network administrator INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex }
or by an SNMP agent as instructed by LDP." ::= { mplsLdpEntityTable 1 }
INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex }
::= { mplsLdpEntityTable 1 }
MplsLdpEntityEntry ::= SEQUENCE {
mplsLdpEntityLdpId MplsLdpIdentifier,
mplsLdpEntityIndex IndexInteger,
mplsLdpEntityProtocolVersion Unsigned32,
mplsLdpEntityAdminStatus INTEGER,
mplsLdpEntityOperStatus INTEGER,
mplsLdpEntityTcpDscPort InetPortNumber,
mplsLdpEntityUdpDscPort InetPortNumber,
mplsLdpEntityMaxPduLength Unsigned32,
mplsLdpEntityKeepAliveHoldTimer Unsigned32,
mplsLdpEntityHelloHoldTimer Unsigned32,
mplsLdpEntityInitSessionThreshold Integer32,
mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod,
mplsLdpEntityLabelRetentionMode MplsRetentionMode,
mplsLdpEntityPathVectorLimit Integer32,
mplsLdpEntityHopCountLimit Integer32,
mplsLdpEntityTransportAddrKind INTEGER,
mplsLdpEntityTargetPeer TruthValue,
mplsLdpEntityTargetPeerAddrType InetAddressType,
mplsLdpEntityTargetPeerAddr InetAddress,
mplsLdpEntityLabelType MplsLdpLabelType,
mplsLdpEntityDiscontinuityTime TimeStamp,
mplsLdpEntityStorageType StorageType,
mplsLdpEntityRowStatus RowStatus
}
mplsLdpEntityLdpId OBJECT-TYPE MplsLdpEntityEntry ::= SEQUENCE {
SYNTAX MplsLdpIdentifier mplsLdpEntityLdpId MplsLdpIdentifier,
MAX-ACCESS not-accessible mplsLdpEntityIndex IndexInteger,
STATUS current mplsLdpEntityProtocolVersion Unsigned32,
DESCRIPTION mplsLdpEntityAdminStatus INTEGER,
"The LDP identifier." mplsLdpEntityOperStatus INTEGER,
mplsLdpEntityTcpPort InetPortNumber,
mplsLdpEntityUdpDscPort InetPortNumber,
mplsLdpEntityMaxPduLength Unsigned32,
mplsLdpEntityKeepAliveHoldTimer Unsigned32,
mplsLdpEntityHelloHoldTimer Unsigned32,
mplsLdpEntityInitSessionThreshold Integer32,
mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod,
mplsLdpEntityLabelRetentionMode MplsRetentionMode,
mplsLdpEntityPathVectorLimit Integer32,
mplsLdpEntityHopCountLimit Integer32,
mplsLdpEntityTransportAddrKind INTEGER,
mplsLdpEntityTargetPeer TruthValue,
mplsLdpEntityTargetPeerAddrType InetAddressType,
mplsLdpEntityTargetPeerAddr InetAddress,
mplsLdpEntityLabelType MplsLdpLabelType,
mplsLdpEntityDiscontinuityTime TimeStamp,
mplsLdpEntityStorageType StorageType,
mplsLdpEntityRowStatus RowStatus
}
mplsLdpEntityLdpId OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP identifier."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section on LDP Identifiers." "RFC3036, LDP Specification, Section on LDP Identifiers."
::= { mplsLdpEntityEntry 1 } ::= { mplsLdpEntityEntry 1 }
mplsLdpEntityIndex OBJECT-TYPE mplsLdpEntityIndex OBJECT-TYPE
SYNTAX IndexInteger SYNTAX IndexInteger
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index is used as a secondary index to uniquely "This index is used as a secondary index to uniquely
skipping to change at page 20, line 4 skipping to change at page 17, line 24
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational status of this LDP Entity. "The operational status of this LDP Entity.
The value of unknown(1) indicates that the The value of unknown(1) indicates that the
operational status cannot be determined at operational status cannot be determined at
this time. The value of unknown should be this time. The value of unknown should be
a transient condition before changing a transient condition before changing
to enabled(2) or disabled(3)." to enabled(2) or disabled(3)."
::= { mplsLdpEntityEntry 5 } ::= { mplsLdpEntityEntry 5 }
mplsLdpEntityTcpDscPort OBJECT-TYPE mplsLdpEntityTcpPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TCP Discovery Port for "The TCP Port for
LDP. The default value is the well-known LDP. The default value is the well-known
value of this port." value of this port."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 2.4.1, "RFC3036, LDP Specification, Section 3.10, Well-known
Basic Discovery Mechanism, Section 2.4.2, Numbers, and Section 3.10.1. UDP and TCP Ports."
Extended Discovery Mechanism, Section
3.10, Well-known Numbers, and Section 3.10.1.
UDP and TCP Ports."
DEFVAL { 646 } DEFVAL { 646 }
::= { mplsLdpEntityEntry 6 } ::= { mplsLdpEntityEntry 6 }
mplsLdpEntityUdpDscPort OBJECT-TYPE mplsLdpEntityUdpDscPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The UDP Discovery Port for "The UDP Discovery Port for
LDP. The default value is the LDP. The default value is the
skipping to change at page 21, line 6 skipping to change at page 18, line 21
UNITS "octets" UNITS "octets"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum PDU Length that is sent in "The maximum PDU Length that is sent in
the Common Session Parameters of an Initialization the Common Session Parameters of an Initialization
Message. According to the LDP Specification [RFC3036] Message. According to the LDP Specification [RFC3036]
a value of 255 or less specifies the a value of 255 or less specifies the
default maximum length of 4096 octets, this is why default maximum length of 4096 octets, this is why
the value of this object starts at 256. The operator the value of this object starts at 256. The operator
should explicitly choose the default value (i.e. 4096), should explicitly choose the default value (i.e., 4096),
or some other value. or some other value.
The receiving LSR MUST calculate the maximum PDU The receiving LSR MUST calculate the maximum PDU
length for the session by using the smaller of its and length for the session by using the smaller of its and
its peer's proposals for Max PDU Length." its peer's proposals for Max PDU Length."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3. "RFC3036, LDP Specification, Section 3.5.3.
Initialization Message." Initialization Message."
DEFVAL { 4096 } DEFVAL { 4096 }
::= { mplsLdpEntityEntry 8 } ::= { mplsLdpEntityEntry 8 }
skipping to change at page 22, line 5 skipping to change at page 19, line 17
the Hold Time in the Common Hello Parameters TLV of the Hold Time in the Common Hello Parameters TLV of
the Hello Message. the Hello Message.
A value of 0 is a default value and should be A value of 0 is a default value and should be
interpretted in conjunction with the interpretted in conjunction with the
mplsLdpEntityTargetPeer object. mplsLdpEntityTargetPeer object.
If the value of this object is 0: if the value of the If the value of this object is 0: if the value of the
mplsLdpEntityTargetPeer object is false(2), then this mplsLdpEntityTargetPeer object is false(2), then this
specifies that the Hold Time's actual default value is specifies that the Hold Time's actual default value is
15 seconds (i.e. the default Hold time for Link Hellos 15 seconds (i.e., the default Hold time for Link Hellos
is 15 seconds). Otherwise if the value of the is 15 seconds). Otherwise if the value of the
mplsLdpEntityTargetPeer object is true(1), then this mplsLdpEntityTargetPeer object is true(1), then this
specifies that the Hold Time's actual default value is specifies that the Hold Time's actual default value is
45 seconds (i.e. the default Hold time for Targeted 45 seconds (i.e., the default Hold time for Targeted
Hellos is 45 seconds). Hellos is 45 seconds).
A value of 65535 means infinite (i.e. wait forever). A value of 65535 means infinite (i.e., wait forever).
All other values represent the amount of time in All other values represent the amount of time in
seconds to wait for a Hello Message. Setting the seconds to wait for a Hello Message. Setting the
hold time to a value smaller than 15 is not hold time to a value smaller than 15 is not
recommended, although not forbidden according recommended, although not forbidden according
to RFC3036." to RFC3036."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.2., "RFC3036, LDP Specification, Section 3.5.2.,
Hello Message." Hello Message."
DEFVAL { 0 } DEFVAL { 0 }
skipping to change at page 22, line 39 skipping to change at page 19, line 51
DESCRIPTION DESCRIPTION
"When attempting to establish a session with "When attempting to establish a session with
a given Peer, the given LDP Entity should a given Peer, the given LDP Entity should
send out the SNMP notification, send out the SNMP notification,
'mplsLdpInitSessionThresholdExceeded', when 'mplsLdpInitSessionThresholdExceeded', when
the number of Session Initialization messages the number of Session Initialization messages
sent exceeds this threshold. sent exceeds this threshold.
The notification is used to notify an The notification is used to notify an
operator when this Entity and its Peer are operator when this Entity and its Peer are
possibily engaged in an endless sequence possibly engaged in an endless sequence
of messages as each NAKs the other's of messages as each NAKs the other's
Initialization messages with Error Notification Initialization messages with Error Notification
messages. Setting this threshold which triggers messages. Setting this threshold which triggers
the notification is one way to notify the the notification is one way to notify the
operator. The notification should be generated operator. The notification should be generated
each time this threshold is exceeded and each time this threshold is exceeded and
for every subsequent Initialization message for every subsequent Initialization message
which is NAK'd with an Error Notification which is NAK'd with an Error Notification
message after this threshold is exceeded. message after this threshold is exceeded.
skipping to change at page 23, line 34 skipping to change at page 20, line 42
SYNTAX MplsRetentionMode SYNTAX MplsRetentionMode
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP Entity can be configured to use either "The LDP Entity can be configured to use either
conservative or liberal label retention mode. conservative or liberal label retention mode.
If the value of this object is conservative(1) If the value of this object is conservative(1)
then advertized label mappings are retained then advertized label mappings are retained
only if they will be used to forward packets, only if they will be used to forward packets,
i.e. if label came from a valid next hop. i.e., if label came from a valid next hop.
If the value of this object is liberal(2) If the value of this object is liberal(2)
then all advertized label mappings are retained then all advertized label mappings are retained
whether they are from a valid next hop or not." whether they are from a valid next hop or not."
::= { mplsLdpEntityEntry 13 } ::= { mplsLdpEntityEntry 13 }
mplsLdpEntityPathVectorLimit OBJECT-TYPE mplsLdpEntityPathVectorLimit OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 0 (zero) then "If the value of this object is 0 (zero) then
Loop Dection for Path Vectors is disabled. Loop Detection for Path Vectors is disabled.
Otherwise, if this object has a value greater than Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors is enabled, zero, then Loop Dection for Path Vectors is enabled,
and the Path Vector Limit is this value. and the Path Vector Limit is this value.
Also, the value of the object, Also, the value of the object,
'mplsLdpLsrLoopDetectionCapable', must be set to 'mplsLdpLsrLoopDetectionCapable', must be set to
either 'pathVector(4)' or 'hopCountAndPathVector(5)', either 'pathVector(4)' or 'hopCountAndPathVector(5)',
if this object has a value greater than 0 (zero), if this object has a value greater than 0 (zero),
otherwise it is ignored." otherwise it is ignored."
REFERENCE REFERENCE
skipping to change at page 25, line 46 skipping to change at page 22, line 50
::= { mplsLdpEntityEntry 18 } ::= { mplsLdpEntityEntry 18 }
mplsLdpEntityTargetPeerAddr OBJECT-TYPE mplsLdpEntityTargetPeerAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the internetwork layer address "The value of the internetwork layer address
used for the Extended Discovery. The value of used for the Extended Discovery. The value of
mplsLdpEntityTargetPeerAddrType specifies how mplsLdpEntityTargetPeerAddrType specifies how
this address is to be intepreted." this address is to be interpreted."
::= { mplsLdpEntityEntry 19 } ::= { mplsLdpEntityEntry 19 }
mplsLdpEntityLabelType OBJECT-TYPE mplsLdpEntityLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType SYNTAX MplsLdpLabelType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the optional parameters for the LDP "Specifies the optional parameters for the LDP
Initialization Message. Initialization Message.
skipping to change at page 28, line 21 skipping to change at page 25, line 16
DESCRIPTION DESCRIPTION
"A row in this table contains statistical information "A row in this table contains statistical information
about an LDP Entity. Some counters contained in a about an LDP Entity. Some counters contained in a
row are for fatal errors received during a former row are for fatal errors received during a former
LDP Session associated with this entry. For example, LDP Session associated with this entry. For example,
an LDP PDU received on a TCP connection during an an LDP PDU received on a TCP connection during an
LDP Session contains a fatal error. That LDP Session contains a fatal error. That
error is counted here, because the error is counted here, because the
session is terminated. session is terminated.
If the error is NOT fatal (i.e. the Session If the error is NOT fatal (i.e., the Session
remains), then the error is counted in the remains), then the error is counted in the
mplsLdpSessionStatsEntry." mplsLdpSessionStatsEntry."
AUGMENTS { mplsLdpEntityEntry } AUGMENTS { mplsLdpEntityEntry }
::= { mplsLdpEntityStatsTable 1 } ::= { mplsLdpEntityStatsTable 1 }
MplsLdpEntityStatsEntry ::= SEQUENCE { MplsLdpEntityStatsEntry ::= SEQUENCE {
mplsLdpEntityStatsSessionAttempts Counter32, mplsLdpEntityStatsSessionAttempts Counter32,
mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32, mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32,
mplsLdpEntityStatsSessionRejectedAdErrors Counter32, mplsLdpEntityStatsSessionRejectedAdErrors Counter32,
mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32, mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32,
skipping to change at page 32, line 45 skipping to change at page 29, line 31
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2." "RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 11 } ::= { mplsLdpEntityStatsEntry 11 }
mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Shutdown Notfications "This object counts the number of Shutdown Notifications
received related to session(s) (past and present) received related to session(s) (past and present)
associated with this LDP Entity. associated with this LDP Entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
mplsLdpEntityDiscontinuityTime." mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 12 } ::= { mplsLdpEntityStatsEntry 12 }
mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE
skipping to change at page 39, line 5 skipping to change at page 35, line 20
mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The keep alive hold time remaining for "The keep alive hold time remaining for
this session." this session."
::= { mplsLdpSessionEntry 5 } ::= { mplsLdpSessionEntry 5 }
mplsLdpSessionKeepAliveTime OBJECT-TYPE mplsLdpSessionKeepAliveTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated KeepAlive Time which "The negotiated KeepAlive Time which
represents the amount of seconds between represents the amount of seconds between
keep alive messages. The keep alive messages. The
mplsLdpEntityKeepAliveHoldTimer mplsLdpEntityKeepAliveHoldTimer
related to this Session is the related to this Session is the
value that was proposed as the value that was proposed as the
KeepAlive Time for this session. KeepAlive Time for this session.
This value is negotiated during This value is negotiated during
session initialization between session initialization between
the entity's proposed value the entity's proposed value
(i.e. the value configured in (i.e., the value configured in
mplsLdpEntityKeepAliveHoldTimer) mplsLdpEntityKeepAliveHoldTimer)
and the peer's proposed and the peer's proposed
KeepAlive Hold Timer value. KeepAlive Hold Timer value.
This value is the smaller This value is the smaller
of the two proposed values." of the two proposed values."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3, "RFC3036, LDP Specification, Section 3.5.3,
Initialization Message." Initialization Message."
::= { mplsLdpSessionEntry 6 } ::= { mplsLdpSessionEntry 6 }
mplsLdpSessionMaxPduLength OBJECT-TYPE mplsLdpSessionMaxPduLength OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of maximum allowable length for LDP PDUs for "The value of maximum allowable length for LDP PDUs for
this session. This value may have been negotiated during this session. This value may have been negotiated
the Session Initialization. This object is related to during the Session Initialization. This object is
the mplsLdpEntityMaxPduLength object. The related to the mplsLdpEntityMaxPduLength object. The
mplsLdpEntityMaxPduLength object specifies the requested mplsLdpEntityMaxPduLength object specifies the requested
LDP PDU length, and this object reflects the negotiated LDP PDU length, and this object reflects the negotiated
LDP PDU length between the Entity and LDP PDU length between the Entity and
the Peer." the Peer."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3, "RFC3036, LDP Specification, Section 3.5.3,
Initialization Message." Initialization Message."
::= { mplsLdpSessionEntry 7 } ::= { mplsLdpSessionEntry 7 }
mplsLdpSessionDiscontinuityTime OBJECT-TYPE mplsLdpSessionDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of sysUpTime on the most recent occasion
at which any one or more of this session's counters at which any one or more of this session's counters
suffered a discontinuity. The relevant counters are suffered a discontinuity. The relevant counters are
the specific instances associated with this session the specific instances associated with this session
skipping to change at page 42, line 47 skipping to change at page 39, line 8
::= { mplsLdpHelloAdjacencyEntry 1 } ::= { mplsLdpHelloAdjacencyEntry 1 }
mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 65535, "If the value of this object is 65535,
this means that the hold time is infinite this means that the hold time is infinite
(i.e. wait forever). (i.e., wait forever).
Otherwise, the time remaining for Otherwise, the time remaining for
this Hello Adjacency to receive its this Hello Adjacency to receive its
next Hello Message. next Hello Message.
This interval will change when the 'next' This interval will change when the 'next'
Hello Message which corresponds to this Hello Message which corresponds to this
Hello Adjacency is received unless it Hello Adjacency is received unless it
is infinite." is infinite."
::= { mplsLdpHelloAdjacencyEntry 2 } ::= { mplsLdpHelloAdjacencyEntry 2 }
skipping to change at page 44, line 26 skipping to change at page 40, line 29
-- from the MPLS-LSR-STD-MIB. -- from the MPLS-LSR-STD-MIB.
-- --
mplsInSegmentLdpLspTable OBJECT-TYPE mplsInSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of LDP LSP's which "A table of LDP LSP's which
map to the mplsInSegmentTable in the map to the mplsInSegmentTable in the
the MPLS-LSR-STD-MIB module." MPLS-LSR-STD-MIB module."
::= { mplsLdpSessionObjects 6 } ::= { mplsLdpSessionObjects 6 }
mplsInSegmentLdpLspEntry OBJECT-TYPE mplsInSegmentLdpLspEntry OBJECT-TYPE
SYNTAX MplsInSegmentLdpLspEntry SYNTAX MplsInSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information "An entry in this table represents information
on a single LDP LSP which is represented by on a single LDP LSP which is represented by
a session's index triple (mplsLdpEntityLdpId, a session's index triple (mplsLdpEntityLdpId,
skipping to change at page 45, line 49 skipping to change at page 41, line 49
-- Out Segment LIB Information. -- Out Segment LIB Information.
-- --
mplsOutSegmentLdpLspTable OBJECT-TYPE mplsOutSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of LDP LSP's which "A table of LDP LSP's which
map to the mplsOutSegmentTable in the map to the mplsOutSegmentTable in the
the MPLS-LSR-STD-MIB." MPLS-LSR-STD-MIB."
::= { mplsLdpSessionObjects 7 } ::= { mplsLdpSessionObjects 7 }
mplsOutSegmentLdpLspEntry OBJECT-TYPE mplsOutSegmentLdpLspEntry OBJECT-TYPE
SYNTAX MplsOutSegmentLdpLspEntry SYNTAX MplsOutSegmentLdpLspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information "An entry in this table represents information
on a single LDP LSP which is represented by on a single LDP LSP which is represented by
a session's index triple (mplsLdpEntityLdpId, a session's index triple (mplsLdpEntityLdpId,
skipping to change at page 50, line 14 skipping to change at page 45, line 47
DESCRIPTION DESCRIPTION
"If the value of the 'mplsFecType' is 'hostAddress(2)' "If the value of the 'mplsFecType' is 'hostAddress(2)'
then this object is undefined. then this object is undefined.
If the value of 'mplsFecType' is 'prefix(1)' If the value of 'mplsFecType' is 'prefix(1)'
then the value of this object is the length in then the value of this object is the length in
bits of the address prefix represented by bits of the address prefix represented by
'mplsFecAddr', or zero. If the value of this 'mplsFecAddr', or zero. If the value of this
object is zero, this indicates that the object is zero, this indicates that the
prefix matches all addresses. In this case the prefix matches all addresses. In this case the
address prefix MUST also be zero (i.e. 'mplsFecAddr' address prefix MUST also be zero (i.e., 'mplsFecAddr'
should have the value of zero.)" should have the value of zero.)"
REFERENCE REFERENCE
"RFC3036, Section 3.4.1. FEC TLV." "RFC3036, Section 3.4.1. FEC TLV."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsFecEntry 3 } ::= { mplsFecEntry 3 }
mplsFecStorageType OBJECT-TYPE mplsFecStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 54, line 32 skipping to change at page 50, line 4
mplsLdpSessionPeerAddrTable OBJECT-TYPE mplsLdpSessionPeerAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table 'extends' the mplsLdpSessionTable. "This table 'extends' the mplsLdpSessionTable.
This table is used to store Label Address Information This table is used to store Label Address Information
from Label Address Messages received by this LSR from from Label Address Messages received by this LSR from
Peers. This table is read-only and should be updated Peers. This table is read-only and should be updated
when Label Withdraw Address Messages are received, i.e. when Label Withdraw Address Messages are received, i.e.,
Rows should be deleted as apropriate. Rows should be deleted as appropriate.
NOTE: since more than one address may be contained NOTE: since more than one address may be contained
in a Label Address Message, this table 'sparse augments', in a Label Address Message, this table 'sparse augments',
the mplsLdpSessionTable's information." the mplsLdpSessionTable's information."
::= { mplsLdpSessionObjects 11 } ::= { mplsLdpSessionObjects 11 }
mplsLdpSessionPeerAddrEntry OBJECT-TYPE mplsLdpSessionPeerAddrEntry OBJECT-TYPE
SYNTAX MplsLdpSessionPeerAddrEntry SYNTAX MplsLdpSessionPeerAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 56, line 4 skipping to change at page 51, line 18
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The next hop address. The type of this address "The next hop address. The type of this address
is specified by the value of the is specified by the value of the
mplsLdpSessionPeerNextHopAddrType." mplsLdpSessionPeerNextHopAddrType."
REFERENCE REFERENCE
"RFC3036, Section 2.7. LDP Identifiers "RFC3036, Section 2.7. LDP Identifiers
and Next Hop Addresses" and Next Hop Addresses"
::= { mplsLdpSessionPeerAddrEntry 3 }
::= { mplsLdpSessionPeerAddrEntry 3 }
--- ---
--- Notifications --- Notifications
--- ---
mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsLdpEntityInitSessionThreshold mplsLdpEntityInitSessionThreshold
} }
STATUS current STATUS current
skipping to change at page 57, line 18 skipping to change at page 52, line 30
OBJECTS { OBJECTS {
mplsLdpSessionState, mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime, mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors, mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors mplsLdpSessionStatsUnknownTlvErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent when the "This notification is sent when the
the value of 'mplsLdpSessionState' leaves value of 'mplsLdpSessionState' leaves
the 'operational(5)' state." the 'operational(5)' state."
::= { mplsLdpNotifications 4 } ::= { mplsLdpNotifications 4 }
--**************************************************************** --****************************************************************
-- Module Conformance Statement -- Module Conformance Statement
--**************************************************************** --****************************************************************
mplsLdpGroups mplsLdpGroups
OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } OBJECT IDENTIFIER ::= { mplsLdpConformance 1 }
skipping to change at page 60, line 12 skipping to change at page 55, line 12
OBJECT mplsLdpEntityProtocolVersion OBJECT mplsLdpEntityProtocolVersion
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityAdminStatus OBJECT mplsLdpEntityAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityTcpDscPort OBJECT mplsLdpEntityTcpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityUdpDscPort OBJECT mplsLdpEntityUdpDscPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLdpEntityMaxPduLength OBJECT mplsLdpEntityMaxPduLength
skipping to change at page 63, line 44 skipping to change at page 58, line 37
mplsLdpGeneralGroup OBJECT-GROUP mplsLdpGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLdpLsrId, mplsLdpLsrId,
mplsLdpLsrLoopDetectionCapable, mplsLdpLsrLoopDetectionCapable,
mplsLdpEntityLastChange, mplsLdpEntityLastChange,
mplsLdpEntityIndexNext, mplsLdpEntityIndexNext,
mplsLdpEntityProtocolVersion, mplsLdpEntityProtocolVersion,
mplsLdpEntityAdminStatus, mplsLdpEntityAdminStatus,
mplsLdpEntityOperStatus, mplsLdpEntityOperStatus,
mplsLdpEntityTcpDscPort, mplsLdpEntityTcpPort,
mplsLdpEntityUdpDscPort, mplsLdpEntityUdpDscPort,
mplsLdpEntityMaxPduLength, mplsLdpEntityMaxPduLength,
mplsLdpEntityKeepAliveHoldTimer, mplsLdpEntityKeepAliveHoldTimer,
mplsLdpEntityHelloHoldTimer, mplsLdpEntityHelloHoldTimer,
mplsLdpEntityInitSessionThreshold, mplsLdpEntityInitSessionThreshold,
mplsLdpEntityLabelDistMethod, mplsLdpEntityLabelDistMethod,
mplsLdpEntityLabelRetentionMode, mplsLdpEntityLabelRetentionMode,
mplsLdpEntityPathVectorLimit, mplsLdpEntityPathVectorLimit,
mplsLdpEntityHopCountLimit, mplsLdpEntityHopCountLimit,
mplsLdpEntityTransportAddrKind, mplsLdpEntityTransportAddrKind,
skipping to change at page 65, line 47 skipping to change at page 60, line 34
::= { mplsLdpGroups 2 } ::= { mplsLdpGroups 2 }
mplsLdpNotificationsGroup NOTIFICATION-GROUP mplsLdpNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded, NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded,
mplsLdpPathVectorLimitMismatch, mplsLdpPathVectorLimitMismatch,
mplsLdpSessionUp, mplsLdpSessionUp,
mplsLdpSessionDown mplsLdpSessionDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification for an MPLS LDP implemention." "The notification for an MPLS LDP implementation."
::= { mplsLdpGroups 3 } ::= { mplsLdpGroups 3 }
END END
4.1. The MPLS-LDP-ATM-STD-MIB Module 4.1. The MPLS-LDP-ATM-STD-MIB Module
This MIB Module MUST be supported if LDP uses ATM as the Layer 2 This MIB Module MUST be supported if LDP uses ATM as the Layer 2
medium. There are three tables in this MIB Module. Two tables are medium. There are three tables in this MIB Module. Two tables are
for configuring LDP to use ATM. These tables are the for configuring LDP to use ATM. These tables are the
mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. The third mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. The third
table is the mplsLdpAtmSessionTable which is a read-only table. table is the mplsLdpAtmSessionTable which is a read-only table. This
MIB Module IMPORTS the AtmVpIdentifier TEXTUAL-CONVENTION from
[RFC2514].
4.1.1. The LDP Entity ATM Table 4.1.1. The LDP Entity ATM Table
The mplsLdpEntityAtmTable provides a way to configure information The mplsLdpEntityAtmTable provides a way to configure information
which would be contained in the "Optional Parameter" portion of an which would be contained in the "Optional Parameter" portion of an
LDP PDU Initialization Message. LDP PDU Initialization Message.
4.1.2. The LDP Entity ATM Label Range Table 4.1.2. The LDP Entity ATM Label Range Table
The mplsLdpEntityAtmLRTable provides a way to configure information The mplsLdpEntityAtmLRTable provides a way to configure information
skipping to change at page 66, line 39 skipping to change at page 61, line 27
4.1.3. The LDP ATM Session Table 4.1.3. The LDP ATM Session Table
The MPLS LDP ATM Session Table is a read-only table which contains The MPLS LDP ATM Session Table is a read-only table which contains
session information specific to ATM. session information specific to ATM.
MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
RowStatus, RowStatus,
StorageType StorageType
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB -- [RFC2020]
AtmVpIdentifier AtmVpIdentifier
FROM ATM-TC-MIB FROM ATM-TC-MIB -- [RFC2514]
mplsStdMIB, mplsStdMIB,
MplsAtmVcIdentifier MplsAtmVcIdentifier
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB -- [RFC3813]
; ;
mplsLdpAtmStdMIB MODULE-IDENTITY mplsLdpAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200311181200Z" -- 18 November 2003 LAST-UPDATED "200406030000Z" -- June 3, 2004
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@mindspring.com)
Artel Marconi Communications, Inc.
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
Marconi Communications, Inc. Marconi Communications, Inc.
Working Group Chairs: Working Group Chairs:
George Swallow, email: swallow@cisco.com George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net MPLS Working Group, email: mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2004). The
version of this MIB module is part of RFCXXX; see initial version of this MIB module was published
the RFC itself for full legal notices. in RFC 3815. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for This MIB contains managed object definitions for
configuring and monitoring the Multiprotocol Label configuring and monitoring the Multiprotocol Label
Switching (MPLS), Label Distribution Protocol (LDP), Switching (MPLS), Label Distribution Protocol (LDP),
utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 utilizing Asynchronous Transfer Mode (ATM) as the Layer 2
media." media."
REVISION "200311181200Z" -- 18 November 2003 REVISION "200406030000Z" -- June 3, 2004
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC 3815."
-- Please see the IANA Considerations Section
-- the suggested mplsStdMIB subId is 5, e.g.
-- ::= { mplsStdMIB 5 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB 5 }
--**************************************************************** --****************************************************************
mplsLdpAtmObjects OBJECT IDENTIFIER mplsLdpAtmObjects OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 1 } ::= { mplsLdpAtmStdMIB 1 }
mplsLdpAtmConformance OBJECT IDENTIFIER mplsLdpAtmConformance OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 2 } ::= { mplsLdpAtmStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP ATM Objects -- MPLS LDP ATM Objects
skipping to change at page 69, line 46 skipping to change at page 64, line 15
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents either the InterfaceIndex "This value represents either the InterfaceIndex
or 0 (zero). The value of zero means that the or 0 (zero). The value of zero means that the
InterfaceIndex is not known. InterfaceIndex is not known.
However, if the InterfaceIndex is known, then it must However, if the InterfaceIndex is known, then it must
be represented by this value. be represented by this value.
If an InterfaceIndex becomes known, then the If an InterfaceIndex becomes known, then the
network management entity (e.g. SNMP agent) responsible network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex. If an ATM Label is value of the InterfaceIndex. If an ATM Label is
being used in forwarding data, then the value of this being used in forwarding data, then the value of this
object MUST be the InterfaceIndex." object MUST be the InterfaceIndex."
::= { mplsLdpEntityAtmEntry 1 } ::= { mplsLdpEntityAtmEntry 1 }
mplsLdpEntityAtmMergeCap OBJECT-TYPE mplsLdpEntityAtmMergeCap OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupported(0), notSupported(0),
vpMerge(1), vpMerge(1),
skipping to change at page 75, line 46 skipping to change at page 69, line 49
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 LowerBound vpi/vci == 0/32, and be one entry having LowerBound vpi/vci == 0/32, and
UpperBound vpi/vci == 0/100, and a second entry UpperBound vpi/vci == 0/100, and a second entry
for this same interface with LowerBound for this same interface with LowerBound
vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. vpi/vci == 0/101 and UpperBound vpi/vci == 0/200.
However, there could not be a third entry with However, there could not be a third entry with
LowerBound vpi/vci == 0/200 and LowerBound vpi/vci == 0/200 and
UpperBound vpi/vci == 0/300 because this label UpperBound vpi/vci == 0/300 because this label
range overlaps with the second entry (i.e. both range overlaps with the second entry (i.e., both
entries now have 0/200). entries now have 0/200).
A row will not become active unless a unique and A row will not become active unless a unique and
non-overlapping range is specified. non-overlapping range is specified.
At least one label range entry for a At least one label range entry for a
specific LDP Entity MUST specific LDP Entity MUST
include the default VPI/VCI values denoted include the default VPI/VCI values denoted
in the LDP Entity Table. in the LDP Entity Table.
skipping to change at page 83, line 37 skipping to change at page 77, line 18
END END
4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module 4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module
This MIB Module MUST be supported if LDP uses FRAME RELAY as the This MIB Module MUST be supported if LDP uses FRAME RELAY as the
Layer 2 medium. There are three tables in this MIB Module. Two Layer 2 medium. There are three tables in this MIB Module. Two
tables are to configure LDP for using Frame Relay. These tables are tables are to configure LDP for using Frame Relay. These tables are
the mplsLdpEntityFrameRelayTable and the the mplsLdpEntityFrameRelayTable and the
mplsLdpEntityFrameRelayLRTable. The third table, mplsLdpEntityFrameRelayLRTable. The third table,
mplsLdpFrameRelaySessionTable, is a read-only table. mplsLdpFrameRelaySessionTable, is a read-only table. This MIB Module
IMPORTS the DLCI TEXTUAL-CONVENTION from [RFC2115].
4.2.1. The LDP Entity Frame Relay Table 4.2.1. The LDP Entity Frame Relay Table
The mplsLdpEntityFrameRelayTable provides a way to configure The mplsLdpEntityFrameRelayTable provides a way to configure
information which would be contained in the "Optional Parameter" information which would be contained in the "Optional Parameter"
portion of an LDP PDU Initialization Message. portion of an LDP PDU Initialization Message.
4.2.2. The LDP Entity Frame Relay Label Range Table 4.2.2. The LDP Entity Frame Relay Label Range Table
The mplsLdpEntityFrameRelayLRTable provides a way to configure The mplsLdpEntityFrameRelayLRTable provides a way to configure
information which would be contained in the "Frame Relay Label Range information which would be contained in the "Frame Relay Label Range
Components" portion of an LDP PDU Intialization Message, see Components" portion of an LDP PDU Intialization Message, see
[RFC3034] and [RFC3036]. [RFC3034] and [RFC3036].
4.2.3. The LDP Frame Relay Session Table 4.2.3. The LDP Frame Relay Session Table
The MPLS LDP Frame Relay Session Table is a read-only table which The mplsLdpFrameRelaySessionTable is a table which contains session
contains session information specific to Frame Relay. information specific to Frame Relay.
MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
RowStatus, RowStatus,
StorageType StorageType
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB FROM FRAME-RELAY-DTE-MIB -- [RFC2115]
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB -- [RFC2020]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB -- [RFC3813]
; ;
mplsLdpFrameRelayStdMIB MODULE-IDENTITY mplsLdpFrameRelayStdMIB MODULE-IDENTITY
LAST-UPDATED "200311181200Z" -- 18 November 2003 LAST-UPDATED "200406030000Z" -- June 3, 2004
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@mindspring.com)
Artel Marconi Communications, Inc.
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
Marconi Communications, Inc. Marconi Communications, Inc.
Working Group Chairs: Working Group Chairs:
George Swallow, email: swallow@cisco.com George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net MPLS Working Group, email: mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (year). The
version of this MIB module is part of RFCXXX; see initial version of this MIB module was published
the RFC itself for full legal notices. in RFC 3815. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for This MIB contains managed object definitions for
configuring and monitoring the Multiprotocol Label configuring and monitoring the Multiprotocol Label
Switching (MPLS), Label Distribution Protocol (LDP), Switching (MPLS), Label Distribution Protocol (LDP),
utilizing Frame Relay as the Layer 2 media." utilizing Frame Relay as the Layer 2 media."
REVISION "200311181200Z" -- 18 November 2003
DESCRIPTION
"Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. REVISION "200406030000Z" -- June 6, 2004
-- The requested mplsStdMIB subId is 6, e.g. DESCRIPTION
-- ::= { mplsStdMIB 6 } "Initial version published as part of RFC 3815."
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB 6 }
--**************************************************************** --****************************************************************
mplsLdpFrameRelayObjects OBJECT IDENTIFIER mplsLdpFrameRelayObjects OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 1 } ::= { mplsLdpFrameRelayStdMIB 1 }
mplsLdpFrameRelayConformance OBJECT IDENTIFIER mplsLdpFrameRelayConformance OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 2 } ::= { mplsLdpFrameRelayStdMIB 2 }
--**************************************************************** --****************************************************************
skipping to change at page 86, line 25 skipping to change at page 79, line 38
{ mplsLdpFrameRelayObjects 1 } { mplsLdpFrameRelayObjects 1 }
mplsLdpEntityFrameRelayTable OBJECT-TYPE mplsLdpEntityFrameRelayTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains Frame Relay specific "This table contains Frame Relay specific
information which could be used in the information which could be used in the
'Optional Parameters' and other Frame Relay 'Optional Parameters' and other Frame Relay
Relay specific information. specific information.
This table 'sparse augments' the mplsLdpEntityTable This table 'sparse augments' the mplsLdpEntityTable
when Frame Relay is the Layer 2 medium." when Frame Relay is the Layer 2 medium."
::= { mplsLdpEntityFrameRelayObjects 1 } ::= { mplsLdpEntityFrameRelayObjects 1 }
mplsLdpEntityFrameRelayEntry OBJECT-TYPE mplsLdpEntityFrameRelayEntry OBJECT-TYPE
SYNTAX MplsLdpEntityFrameRelayEntry SYNTAX MplsLdpEntityFrameRelayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 87, line 22 skipping to change at page 80, line 32
"This value represents either the InterfaceIndex of "This value represents either the InterfaceIndex of
the 'ifLayer' where the Frame Relay Labels 'owned' by this the 'ifLayer' where the Frame Relay Labels 'owned' by this
entry were created, or 0 (zero). The value of zero entry were created, or 0 (zero). The value of zero
means that the InterfaceIndex is not known. For example, means that the InterfaceIndex is not known. For example,
if the InterfaceIndex is created subsequent to the if the InterfaceIndex is created subsequent to the
Frame Relay Label's creation, then it would not be known. Frame Relay Label's creation, then it would not be known.
However, if the InterfaceIndex is known, then it must However, if the InterfaceIndex is known, then it must
be represented by this value. be represented by this value.
If an InterfaceIndex becomes known, then the If an InterfaceIndex becomes known, then the
network management entity (e.g. SNMP agent) responsible network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex. If an Frame Relay Label is value of the InterfaceIndex. If an Frame Relay Label is
being used in forwarding data, then the value of this being used in forwarding data, then the value of this
object MUST be the InterfaceIndex." object MUST be the InterfaceIndex."
::= { mplsLdpEntityFrameRelayEntry 1 } ::= { mplsLdpEntityFrameRelayEntry 1 }
mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupported(0), notSupported(0),
supported(1) supported(1)
skipping to change at page 99, line 7 skipping to change at page 91, line 21
provide a way for configuring Label Ranges for Generic Labels, the provide a way for configuring Label Ranges for Generic Labels, the
MIB does provide a way to reserve a range of generic labels because MIB does provide a way to reserve a range of generic labels because
this was thought to be useful by the working group. this was thought to be useful by the working group.
MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, OBJECT-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
RowStatus, RowStatus,
StorageType StorageType
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB -- [RFC2020]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex mplsLdpEntityIndex
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB -- [RFC3813]
; ;
mplsLdpGenericStdMIB MODULE-IDENTITY mplsLdpGenericStdMIB MODULE-IDENTITY
LAST-UPDATED "200311181200Z" -- 18 November 2003 LAST-UPDATED "200406030000Z" -- June 6, 2004
ORGANIZATION "Multiprotocol Label Switching (mpls) ORGANIZATION "Multiprotocol Label Switching (mpls)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Joan Cucchiara (jcucchiara@artel.com) "Joan Cucchiara (jcucchiara@mindspring.com)
Artel Marconi Communications, Inc.
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
Marconi Communications, Inc. Marconi Communications, Inc.
Working Group Chairs: Working Group Chairs:
George Swallow, email: swallow@cisco.com George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net MPLS Working Group, email: mpls@uu.net
" "
DESCRIPTION DESCRIPTION
skipping to change at page 100, line 4 skipping to change at page 92, line 14
James V. Luciani (james_luciani@mindspring.com) James V. Luciani (james_luciani@mindspring.com)
Marconi Communications, Inc. Marconi Communications, Inc.
Working Group Chairs: Working Group Chairs:
George Swallow, email: swallow@cisco.com George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net MPLS Working Group, email: mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (year). The
version of this MIB module is part of RFCXXX; see initial version of this MIB module was published
the RFC itself for full legal notices. in RFC 3815. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for This MIB contains managed object definitions for
configuring and monitoring the Multiprotocol Label configuring and monitoring the Multiprotocol Label
Switching (MPLS), Label Distribution Protocol (LDP), Switching (MPLS), Label Distribution Protocol (LDP),
utilizing ethernet as the Layer 2 media." utilizing ethernet as the Layer 2 media."
REVISION "200311181200Z" -- 18 November 2003 REVISION "200406030000Z" -- June 6, 2004
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC 3815."
-- Please see the IANA Considerations Section.
-- The requested mplsStdMIB subId is 7, e.g.
-- ::= { mplsStdMIB 7 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB 7 }
--**************************************************************** --****************************************************************
mplsLdpGenericObjects mplsLdpGenericObjects
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 }
mplsLdpGenericConformance mplsLdpGenericConformance
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 }
--**************************************************************** --****************************************************************
-- MPLS LDP GENERIC Objects -- MPLS LDP GENERIC Objects
skipping to change at page 103, line 14 skipping to change at page 95, line 11
DESCRIPTION DESCRIPTION
"This value represents either the InterfaceIndex of "This value represents either the InterfaceIndex of
the 'ifLayer' where these Generic Label would be created, the 'ifLayer' where these Generic Label would be created,
or 0 (zero). The value of zero means that the or 0 (zero). The value of zero means that the
InterfaceIndex is not known. InterfaceIndex is not known.
However, if the InterfaceIndex is known, However, if the InterfaceIndex is known,
then it must be represented by this value. then it must be represented by this value.
If an InterfaceIndex becomes known, then the If an InterfaceIndex becomes known, then the
network management entity (e.g. SNMP agent) responsible network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex." value of the InterfaceIndex."
::= { mplsLdpEntityGenericLREntry 4 } ::= { mplsLdpEntityGenericLREntry 4 }
mplsLdpEntityGenericLRStorageType OBJECT-TYPE mplsLdpEntityGenericLRStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
skipping to change at page 107, line 5 skipping to change at page 98, line 5
mplsLdpEntityGenericLRRowStatus mplsLdpEntityGenericLRRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that apply to all MPLS LDP implementations "Objects that apply to all MPLS LDP implementations
using Generic Labels as the Layer 2." using Generic Labels as the Layer 2."
::= { mplsLdpGenericGroups 1 } ::= { mplsLdpGenericGroups 1 }
END END
5. Revision History 5. Acknowledgments
NOTE TO RFC-Editor: before publishing this document as an RFC,
please remove this Revision History (change log) section.
5.1. Changes from <draft-ietf-mpls-ldp-mib-13.txt>
Fix in the Full Compliance of the MPLS-LDP-STD-MIB module to remove
MIN-ACCESS read-only from the mplsFecRowStatus and
mplsLdpLspFecRowStatus objects. The DESCRIPTION clauses were also
updated accordingly.
5.2. Changes from <draft-ietf-mpls-ldp-mib-12.txt>
These fixes were from the MIB Doctor Review.
- bottom of page6
s/MPLS-TC-MIB/MPLS-TC-STD-MIB/
- sect 3.6 first para
change RFC2573 into RFC3413
The citation [RFC2573] does not occur in the ref section either
Neither doe RFC3413
Fixed line lengths.
5.3. Changes from <draft-ietf-mpls-ldp-mib-11.txt>
Updated with comments from the 3rd Last Call for this MIB which took
place, Thursday, June 12 to June 24, 2003.
Updated with last call comments from Adrian Farrel posted to the MPLS
Working Group email list on June 12, 2003.
Updated the 2 outstanding issues from Bert's email May 9th which was
posted to the MPLS Working Group. These issues were not updated for
version 10, so were addressed in version 11: 1) updated #3 from that
email and 2) reviewed all the InetAddressType and InetAddress objects
to make sure that descriptions were per rfc3291.
5.4. Changes from <draft-ietf-mpls-ldp-mib-10.txt>
Renamed the MIB module to include Std and also updated the IANA
Considerations Section to use mplsStdMIB.
Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet
update #3 from that email and 2) did not yet review all the
InetAddressType and InetAddress objects to make sure that
descriptions were per rfc3291.
Changed Ses to Session for clarity.
5.5. Changes from <draft-ietf-mpls-ldp-mib-09.txt>
Added the new MIB boiler plate and associated MIB reference changes.
Reworked the OID tree structure so that the Modules only have the
mplsMIB subid dependency. This was discussed in mpls wg email
(discussion was mostly between Bert, Tom and Joan).
Added IANA Considerations section. This contains 4 subsections, one
per MIB module.
Updated and added new references as needed.
Changed mplsMIB subid values to agree with the latest "Multiprotocol
Label Switching (MPLS) Management Overview" document, [MPLSMGMT].
Moved MIB modules around so that they would appear in subId order.
The Generic MIB module is shown last, since the subid is 7 (which is
the last (and largest) subid requested by IANA.
5.5.1. Changes based on MIB Doctor Review Comments
The following changes are based on comments from the MIB DR Review.
The comments are from email to the mpls working group dated, Dec 6,
2002. These comments are quoted and prefaced by "REQ: comment goes
here", and then followed by our resolution.
"REQ: - missing IPR section". RSP: it has been added.
"REQ: - Security considerations probably needs more work
Security ADs want you to explain what the vulnerabilities/risks
are and what to do against them.
Also for read only objects, pls list each (group of) object(s)
and explain what sensitivity attributes they have". RSP: Done. We
added subsections here since the Security template is MIB Module
based and it seemed to us more clear to do a subsection per MIB
Module.
"REQ: - pls do the consistency checking for descriptors and all
that". RSP: believe this to be done. Changed Gen to Generic
everywhere, changed Fr to FrameRelay, changed RO to ReadOnly.
Changed Sessions to Ses everywhere. Reviewed tables to make sure
they were prefixed consistently. Added more references, used more
TCs and other stuff.
"REQ: - sect 3.5 1st sentence, s/would be/are/ ??". RSP: done.
"REQ: - sect 3.5 2nd para first sentence s/initiation/initiate/ ".
RSP: done.
"REQ: - section 3.5.2 s/mpsl/mpls/". RSP: done.
"REQ: - mplsXxxIndexNext
See my comments on FTN MIB and LSR MIB on these type of objects
Best to use something aka rfc3289 ". RSP: We have imported the
IndexInteger and IndexIntegerNextFree TCs (from rfc3289.txt). NOTE:
we do not like the names of these TCs because they use the term
Integer when the values are Unsigned32. Would prefer new TCs with
IndexUnsigned32 and IndexUnsigned32NextFree.
"REQ:- RowStatus and StorageType objects
see my comments about similar objects in LSR MIB
for StorageType might also want to add a DEFVAL ". RSP: Added
descriptive text to the RowStatus objects to specify which columns
can be changed when row is active. Added descriptive text to the
StorageType objects to specify what happens when the StorageType is
permanent. Also added DEFVALs for the StorageType objects.
"REQ: - mplsLdpNotifications ... { mplsLdpMib 2 }
why not { mplsLdpMib 0} so that it is right away the prefix?
I believe LSR MIB does it that way now. You may want to do
it consistently for all notifications.
I can live with either way, but prefer them to be shorter OIDs.".
RSP: We changed this to follow what LSR MIB does (i.e.
mplsLdpNotifications 0) for shorter OIDs..PP "REQ: -
mplsXxxLastChange
does that time stamp only get changed if an addition/deletion takes
place? Not if something gets changed via a SNMP SET command?
I think I'd prefer to also see changes (modifications) via SET.
But in any event, be very explicit about if those are included or
not.". RSP: All Last change object DESCRIPTIONs have been
updated to be very specific.
"REQ:- mplsLdpLspType
All that stuff in the DESCRIPTION clause is just a repeat of the
TC DESCRIPTION clause. Seems not needed to me. What if a value
gets added later... how do you stay in sync?". RSP: This has
been fixed.
"REQ: - mplsFecAddrLength
Should that be of SYNTAX InetAddressPrefixLength as per RFC3291?".
RSP: yes, fixed.
"REQ: - mplsFecAddrFamily and mplsFecAddr
These are strange. The DESCRIPTIONS are certainly not meeting the
requirements as specified in RFC3291. At other places you do it
correct, so you do understand what is required I think.". RSP:
changed to have a better descriptions. Should note that the TLVs in
the LDP Specification use Address Family Numbers and are still
referring to RFC1700.
"REQ: - mplsLdpLspFecTable claims to be a read-only table.
Yet you have a read-create RowStatus object in it.". RSP: fixed.
"REQ: - mplsLdpSessionUp and mplsLdpSessionDown
Is it not better to just have one notification, namely a
mplsLdpSessionStateChange and then the mplsLdpSesState object will
explain what the change is?". RSP: We prefer to leave it this
way. There are some 3rd Party applications that try to resolve
Notifications, so you see one for down, then resolve this by seeing
another one for up. Granted, these 3rd party apps could be coded to
parse the varbind within the trap, but then this requires coding
whereas having 2 distinct notifications is easier on the developer.
Granted, this maybe makes the MIB design more cumbersome. If this is
a blocking issue, then we will change it.
"REQ:- COMPLIANCE section. I hope that INT ADs are OK with making
IPv6
addresses optional. Is that cause current LDP only supports IPv4?
If so you may want to add that as an explanation.". RSP: IPv6
was made mandatory, also supported in MPLS LDP Spec (rfc3036.txt).
Continue with MIB Dr Comments for the MPLS-LDP-GENERIC-MIB.
"REQ:- same on mplsXXXIndexNext and RowStatus and STorageType
objects". RSP: These hdescriptions have been updated. It should
be noted, that these should be EXACTLY the same as the
mplsLdpEntityTable since the Label Range Tables extend the Entity
Table. "REQ:- this looks wierd:
::= { mplsMib 6 } -- to be assigned
use cc instead of 6 if you want IANA to assign, and do tell
-- to be assigned by IANA
and write something about it in an IANA Considerations Section if
this is what you want.". RSP: Added more comments, and added an
IANA Considerations Section. "REQ:- mplsGenModuleROCompliance
I would call it mplsGenModuleReadOnlyCompliance
You have used ReadOnly and Full in other places/mib modules and
it is good to be clear and consistent". RSP: done.
MIB Doctor Review comments for ATM.
"REQ:- s/Moduel/Module/". RSP: done.
"REQ:- same on mplsXXXIndexNext and RowStatus and STorageType
objects". RSP: done.
"REQ:- this looks wierd:
::= { mplsMib 4 } -- to be assigned
use cc instead of 4 if you want IANA to assign, and do tell
-- to be assigned by IANA
and write something about it in an IANA Considerations Section if
this is what you want.". RSP: done.
"REQ:- See earlier remark on Notifications (use zero instead of 2
right away)". RSP:Removed this branch because there aren't any
notifications in this MIB module.
"REQ:- There are still some INTEGER enumerations that start with zero
It is not a BLOCKING problem... but if acceptable, pls make it
start
at 1 (as you have done vor various others of these enumerations)".
RSP: We would rather leave these enums starting with zero. (There are
2 of them in the ATM Module). The reason for leaving them is because
the value zero is what the protocol uses. We have added REFERENCES
to these objects and more info in the descriptions themselves. We
believe it is in the best interest of developers to start enums at
zero. The INET-ADDRESS-MIB uses the value zero, and since we are
already required to use that MIB, there is precedence for zero in an
enum where it makes sense. We believe the value of zero makes sense
for where it is being used in this MIB module.
"REQ:- mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance".
RSP: done.
"REQ:- some formatting problems with DEFVAL lines being split on 2
lines?". RSP: fixed.
MIB Doctor Review comments for FrameRelay
"REQ:- consistency in descriptors (FrameRelay vs FR etc)". RSP:
done. "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType
objects". RSP: done. "REQ:- this looks wierd:
::= { mplsMib 5 } -- to be assigned
use cc instead of 5 if you want IANA to assign, and do tell
-- to be assigned by IANA
and write something about it in an IANA Considerations Section if
this is what you want.". RSP: done. "REQ:- See earlier remark
on Notifications (use zero instead of 2 right away)". RSP:Removed
this branch because there aren't any notifications in this MIB
module.
"REQ:- There are still some INTEGER enumerations that start with zero
It is not a BLOCKING problem... but if acceptable, pls make it
start
at 1 (as you have done vor various others of these enumerations)".
RSP: We would rather leave these enums starting with zero. (There are
4 of them in the Frame Relay Module). The reason for leaving them is
because the value zero is what the protocol uses. We have added
REFERENCES to these objects and more info in the descriptions
themselves. We believe it is in the best interest of developers to
start enums at zero. The INET-ADDRESS-MIB uses the value zero, and
since we are already required to use that MIB, there is precedence
for zero in an enum where it makes sense. We believe the value of
zero makes sense for where it is being used in this MIB module.
"REQ:- mplsLdpEntityFrLRComponents OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Number of Label Range Components in the Initialization
message. This also represents the number of entries
in the mplsLdpEntityConfFrLRTable which correspond
to this entry."
Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed.
"REQ:- I see the xxxDlci index objects start at zero.
Pls add to DESCRIPTION clauses why zero must be an index.". RSP:
Since we are using DLCI and the value of zero is valid for a DLCI. A
statement was added about this. Also, used the DLCI TC from
rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB
module uses an index of the VP which can also take on the value of
zero. A statement was added to this Index also. "REQ:-
mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP:
done.
5.6. Changes from <draft-ietf-mpls-ldp-mib-08.txt>
The following changes are from the IESG MIB review.
Changed "Label Switch Router" to "Label Switching Router".
Spelling errors fixed (unlabelled, atttempt, subsytem).
Changed some of the enums to start at 1, instead of zero:
mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus.
Added REFERENCE clauses.
Added a timestamp object for mplsLdpSesState changes.
Changed NMS to command generator as defined in RFC2571.
Added a lastChange objects: mplsLdpEntityLastChange and
mplsLdpPeerLastChange.
Added TEXTUAL-CONVENTIONS for MplsLabelDistributionMethod and
MplsRetentionMode. These TCs have been incorporated into draft-ietf-
mpls-tc-mib-04.txt.
Divided up the one MIB MODULE into 3 additional modules for a total
of 4 MIB MODULES: 1) mplsLdpMIB, 2) mplsLdpGenericMIB which includes
objects pertaining to Ethernet as the L2, 3) mplsLdpAtmMIB which
includes objects pertaining to ATM as the L2, and 4)
mplsLdpFrameRelayMIB which includes objects pertaining to Frame Relay
as the L2.
Also, reduced the number of objects by creating the mplsLdpLspTable
and removing the Mapping tables.
In section 3.1 changed "where each row in the table initiates" to
"where each row in the table represents".
Updated Reference Section and divided them into Normative vs.
Informative.
Removed the MplsGenAddress TC and used the INET-ADDRESS-MIB's
InetAddress TC. Objects using this TC are:
mplsLdpEntityTargetPeerAddr, mplsFecAddr, and
mplsLdpSesPeerNextHopAddr and are noted in the conformance statements
supporting: unknown(0), ipv4(1), and ipv6(2).
Removed AddressFamilyNumbers TC and used InetAddressType TC from the
INET-ADDRESS-MIB. One of the MIB compilers as a warning because
apparently one is expected to use InetAddressType and InetAddress
together (although, think this restriction is too restrictive). Also,
removed the reference for the Address Family Numbers MIB.
Changed the name TargPeer to TargetPeer.
Removed the Enable/Disable trap objects:
mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC
3413 should be used to enable/disable traps.
Removed the import for "transmission" and instead, imported "mplsMIB
from the MPLS-TC-STD-MIB".
Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated
the DESCRIPTION clause. Also, the PVL abbreviation was expanded to
PathVectorLimit for other objects.
Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL
into one object: mplsLdpPeerPathVectorLimit and updated the
DESCRIPTION clause.
mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS-
MIB. Likewise, mplsLdpEntityUdpDscPort uses the InetPortNumber TC
from the INET-ADDRESS-MIB. Also a REFERENCE clause was added.
The mplsLdpEntityMaxPduLength object has the SYNTAX range changed to
start at 256. Also the DESCRIPTION clause was updated.
The mplsLdpSesMaxPduLen object's name was changed to
mplsLdpSesMaxPduLength and a UNITS clause was added, and the
DESCRIPTION clause was updated. This object is related to the
mplsLdpEntityMaxPduLength object.
The mplsLdpEntityKeepAliveHoldTimer and mplsLdpEntityHelloHoldTimer
DESCRIPTION clause was changed from "The two octet value" to "The
16-bit integer value".
The mplsLdpEntityHelloHoldTimer object's DESCRIPTION clause was
updated.
A range of Integer32(0..100) was added to the SYNTAX clause of the
mplsLdpEntityInitSesThreshold object. Also, the DESCRIPTION clause
of this object was updated.
The mplsLdpEntityOptionalParameters object was renamed to
mplsLdpEntityLabelType.
Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus
objects. RowStatus now reflects the status of the row, and Admin
status controls enabling/disabling the entry.
Updated the DESCRIPTION clauses for the objects in the
mplsLdpEntityStatsTable to refer to the
mplsLdpEntityDiscontinuityTime object.
Changed StorType to StorageType.
5.7. Changes from <draft-ietf-mpls-ldp-mib-07.txt>
There were three types of changes: the first change was that all the
MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were
moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc-
mib-00.txt". The Textual Conventions are now IMPORTED from
[MPLSTCMIB]. The second type of change was updates based on comments
from the IESG. These changes will be discussed below. The third
type of changes were based on minor editorial changes from the co-
authors.
The "Introduction" and "Structure of the MIB" sections were reworded
since they were repetitive.
The "Overview" was rearranged.
References were added to "The LDP Entity ATM Objects" and "The LDP
Entity Frame Relay Objects" Sections.
The Working Group mailing list and Chairs were added to the CONTACT-
INFO.
Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object.
Updated the mplsLdpEntityProtocolVersion to include a range
(1..65535).
Updated the "References" Section.
Running the MIB through the smilint MIB compiler showed that some
object names were longer than 32 characters, these were shortened to
32 characters or fewer.
The following changes were from the co-authors.
Other minor editorial changes such as fixing typographical errors,
and removing MIB comments which are no longer meaningful.
Page 17 (also page 46) the description was enhanced to describe the
version field in the LDP header from RFC3036.
Removed WellKnown from the tcp and upd port names. It's the ports
that get set, and the default value is the well known (actually the
registered) port number.
mplsLdpEntityInitSesTrapEnable object is useless and was removed
since setting mplsLdpEntityInitSesThreshold=0 acheives the same
thing. Also removed it from the descriptive text in section 3.
Page 47, mplsLdpSessionDiscontinuityTime The initial value of this
was changed to be sysUpTime instead of zero. sysUpTime for when the
session starts is more meaningful and was added to the Session
Up/Down Traps also. Also, added the Session specific stats to the
up/down traps.
5.8. Changes from <draft-ietf-mpls-ldp-mib-06.txt>
All changes were from the second last call which took place Thursday,
July 20th, until Thursday, July 27th, 2000 and are described in the
remainder of this section.
Remove the reference to the MPLS framework document.
Add an mplsFecIndexNext type of object.
Change the conformance of the FEC table objects to be part of the
mplsLdpGeneralGroup.
The mplsLdpEntityConfGenericTable is no longer needed because the
functionality has been absorbed by the
mplsLdpEntityConfGenericLabelRangeTable. The
mplsLdpEntityConfGenericTable has been removed and the front section
was updated accordingly.
Other editorial issues, updating references, typos and so forth.
5.9. Changes from <draft-ietf-mpls-ldp-mib-05.txt>
The majority of changes in this revision are based on Last Call
comments which were received during the last call from Thursday,
March 9, 2000 to Friday, March 17, 2000, or slightly thereafter.
Also, changes were made to agree with the latest specifications.
These changes are described in this section.
Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-
ldp-08.txt. Specifically, removing references to IPv4/IP and using
router id, as appropriate.
Removed vpMerge and vpAndVcMerge choices from the object,
mplsLdpEntityAtmMergeCap. VP Merge is not described in [RFC3036].
The LIB Table was removed and replaced by mapping tables to map LDP
LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and
mplsXC tables in the LSR MIB. The conformance section was updated
to include a Mapping Group which is to be implemented iff these LSR
MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable)
are implemented.
The front section was updated to include information on the Generic
label table.
Added more in the front section on on Row
Creation/adminStatus/OperStatus in the LDP Entity and related tables.
Added a generic label range table. NOTE: there is NO corresponding
LDP message which relates to the information in this table, however,
this table does provide a way for a user to 'reserve' a generic label
range.
A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has
the same upper bounds as AtmVcIdentifier (from rfc2514) except that
the lower bound is 32 (and not 0). The lower bound is 32 since this
value is specified by [RFC3035].
Removed the scalar object mplsLsrLabelRetentionMode and added
mplsLdpEntityLabelRetentionMode. The change was made to allow
configuring the retention mode on a per LDP Entity basis, as opposed
for the entire LSR.
Typo in section 3.5.2 was fixed.
Typo in the mplsLdpSessionUp notification description was fixed.
Section 'LDP Notifications' was expanded to cover both the
'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects
which enable and disable these traps have been described in this
Section:
The 'mplsLdpEntityHopCountLoopDetection' object and the
'mplsLdpEntityHopCount' object have been combined into the new
object, 'mplsLdpEntityHopCountLimit'.
MplsLabel has been updated to reflect the VPI value of 12 bits and
not 8.
Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort'
object. The default value is 646.
Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength'
object. The default value is 4096 and the units is octets.
Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The
default value is 1.
Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40
seconds.
Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The
default value is 8.
The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects,
one for TCP and one for UDP. The names are
Typo in the description for the
The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The
mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to
show that these two tables are related. There has been wording added
to the mplsLdpSessionEntry description and to the description for the
mplsLdpPeerTable.
5.10. Changes from <draft-ietf-mpls-ldp-mib-04.txt>
Editorial changes, fixing typo's, fixing wrapping lines, etc.
Updated references for latest drafts, and added [RFC3032] and
[RFC3034] to Reference Section.
Added to the Acknowledgements Section.
Changed the SYNTAX and DESCRIPTION of the
'mplsLdpLsrLoopDetectionCapable' object, so that it will also support
the loop detection by hop count.
Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL'
objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is
now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL'
object. This results in one less object
'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality.
Changed 'mplsLdpLibLabelType' into two objects:
'mplsLdpLibInLabelType' and differ from the egress label type. The
MIB now reflects this.
The following items were changed as a result of the Frame Relay Forum
dropping support for 17-bit DLCIs: the MplsLabel TC description has
been modified, and other Frame Relay Object descriptions were also
modified (as specified in this section).
The MplsLabel TC was also modified and reference 3. was added to the
REFERENCE Clause.
MplsLdpLabelTypes TC was modified to use an enum.
InterfaceIndex support was added to the Entity information. This was
specifically requested by several members of the working group. An
additional table, mplsLdpEntityConfGenericTable as a way to configure
Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was
added to map the InterfaceIndex used by Generic Labels. Objects were
also added to the 'mplsLdpEntityAtmParmsTable' and the and
'mplsLdpEntityFrIfIndex', respectively.
Changed the name of the 'mplsLdpEntityMtu' object to be
'mplsLdpEntityMaxPduLength' which is more consistent with the LDP
Specification. Also, the description and SYNTAX were changed.
Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32
and changed the Range from (0..65535) to (1..65535).
Added and improved the front section discussion on SNMP
Notifications.
Also, modified the DESCRIPTION clause of the
Added objects to enable/disable the sending of traps:
Added an object to enable/disable sending traps for Sessions changing
from Up to Down, or Down to Up.
Added notifications to generate traps from session changing from Up
to Down, or Down to up.
Added a StorageType object to the Entity and associated tables which
are configurable.
Added a Discontinuity Time object to the Entity Table,
Added discussion on row creation in the Entity and other associated
Entity tables. This is a new Section in the Front part of the
document called:
Removed the 'mplsLdpEntityControlMethod'.
Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This
is to allow FECs to map to multiple LSPs. Also add a RowPointer to a
row in the Session Table.
Added an operation status object, 'mplsLdpLspOperStatus' and a last
Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be
used to detect whether an LSP has changed its status.
Changed the name of the mplsLdpPeerTable to the
mplsLdpEntityPeerTable. This table contains information relevant to
Peers which are known to specific Entities. The indexing of this
table has also changed to include the Row in the Entity Table that
this Peer is known by. The mplsLdpHelloAdjacencyTable and the
mplsLdpSessionTable have been moved under this table. Since Hello
Adjacencies are related to Entity-Peer information and Sessions are
related to Entity-Peer information this was seen as a comprehensive
and coherent modelling. Associated descriptions in the front section
and in the tables have been changed to reflect this change.
Moved the 'mplsLdpConfFrLen' object from the
'mplsLdpEntityConfFrLabelRangeTable' to the
'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay
interface/port can only use one header length at a time, i.e. a
specific FR interface supports one address length for all VCs on that
interface. Also, changed the object so that it only supports 10 and
23 bit DLCI lengths. (The 17 bit length was dropped by the Frame
Relay Forum and thus, is no longer required.) The name of this
object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to
fit in with the 'mplsLdpEntityFrameRelayParmsTable'.
Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen
object. (The 17 bit length was dropped by the Frame Relay Forum and
thus, is no longer required.)
Corrected the range of the 'mplsLdpEntityIndexNext' object to include
0 (zero).
5.11. Changes from <draft-ietf-mpls-ldp-mib-03.txt>
Reworded the description of the mplsLdpAtmSessionTable to clarify
that one or MORE label range intersection(s) is/are represented in
this table.
Reworded the description of the mplsLdpFrameRelaySessionTable to
clarify that one or MORE label range intersection(s) is/are
represented in this table.
Added a new index, mplsLdpSessionPeerIndex, to the
mplsLdpSessionPeerAddressTable. This new index uniquely identifies
the entry within a given session. (Since adding
mplsLdpSessionPeerNextHopAddressType,
mplsLdpSessionPeerNextHopAddress to the INDEX clause of the
mplsLdpSessionPeerAddressTable leaves a table with only indices and
no objects, the work around was to add a new index which uniquely
differentiates an entry within a given session.)
Quite a few changes to the mplsLdpPeerTable. First, removed the
mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This
index served no purpose, so was removed. Second, removed the
objects: mplsLdpPeerInternetworkAddrType, and
mplsLdpPeerInternetworkAddr. Third, reworded the description of this
table to include information which is known during Session
Intialization attempts, the specific information has to do with Loop
Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec
when describing the PVLim says: "Although knowledge of a peer's path
vector limit will not change an LSR's behavior, it does enable the
LSR to alert an operator to a possible misconfiguration." and the
object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch
notification.
Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable.
Removed the "IANA Address Family Numbers" MIB section.
Updated the boiler.me from the ops web page dated Weds., Dec 22,
1999.
Updated the Security Section from the ops web page.
Added the following objects to the mplsLdpEntityTable:
mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and
mplsLdpEntityPathVectorLimit.
Removed mplsLdpSessionLabelAdvertisement,
mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit
from the mplsLdpSessionTable.
Changed the mplsLdpPathVectorLimitMismatch Notification to send
mplsLdpEntityPathVectorLimit (instead of
mplsLdpSessionPathVectorLimit).
Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and
replaced the MplsLdpGenAddr for mplsLdpLibInLabel and
mplsLdpLibOutLabel with MplsLabel.
The mplsLdpSessionIndex was removed throughout the MIB. This was
replaced by the object mplsLdpSessionDiscontinuityTime. The
motivation was to reduce the number of indices.
The descriptions for the objects in the mplsLdpSessionStatsTable,
mplsLdpSessionStatsUnknownMessageTypeErrors and
mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a
reference to the mplsLdpSessionDiscontinuityTime object.
5.12. Changes from <draft-ietf-mpls-ldp-mib-02.txt>
Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and
mplsLdpEntityIndexNext.
Added the following objects to the mplsLdpEntityTable:
mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus,
mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer,
mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and
mplsLdpEntityHelloHoldTimer.
Changed the description of the mplsLdpEntityAtmParmsTable and added
the following objects to this table: mplsLdpEntityAtmLsrConnectivity,
mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci,
mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the
last four objects were in Version 01 of the MIB but were mistakenly
omitted from Version 02. Now, they are back.
Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to
include the minimum VPI/VCI. This is to ensure that indices in this
table are unique.
Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to
include the minimum DLCI value. This is to ensure that indices in
this table are unique.
Added [RFC3036] to Reference Section.
5.13. Changes from <draft-ietf-mpls-ldp-mib-01.txt>
The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of
the LDP Specification [RFC3036].
The front section was updated.
The MIB was made to be less ATM-centric. Essentially, the ATM
specific objects where removed from the tables and placed in ATM
specific Tables. A type was added to the base tables and a row is to
be created in the ATM/FR/etc. type table. Apropos compliance
statements were added to reflect the separation of ATM and Frame
Relay objects into their respective tables.
Objects for Loop Detection were removed from describing the LDP
implementation (i.e. the scalars were removed) and Loop Dection
objects were added to the Session Table. (Although as the LDP
Specification indicates loop detection should be for an LSR within a
domain.)
The following tables were added: mplsLdpEntityAtmParmsTable,
mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable,
mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable,
mplsLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable,
mplsLdpLibTable, and the mplsLdpFecTable.
The following notifications were added: notification for Session
removal.
The following objects were removed from the Session Table:
mplsLdpSessionRole was removed (this can be determined by comparing
LSR Ids and does not need to be explicitly in the MIB.) ATM specific
objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi
mplsLdpSessionAtmLabelRangeLowerBoundVci,
mplsLdpSessionAtmLabelRangeUpperBoundVpi
mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a
separate table. Frame Relay objects were added in a separate table.
Hello Adjacency Table was updated.
The objects, mplsLdpSessionRejectedParamErrors,
mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors,
mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors,
mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors,
mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and
mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable.
The mplsLdpSessionStatsTable was added to count statics based on a
per Session basis.
The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no
need to configure information for a Peer. All information for a peer
is learned, thus peer information is read-only.
(Editorial) References were updated to reflect the documents which
this version was based on.
5.14. 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, mplsLdpLsrLoopDetectionPresent,
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.
References were added and revised.
6. Acknowledgments
This document is a product of the MPLS Working Group. The authors This document is a product of the MPLS Working Group. The authors
would like to thank Mike MacFadden and Adrian Farrel for their would like to thank Mike MacFadden and Adrian Farrel for their
helpful comments on several reviews. Also, the authors would like to helpful comments on several reviews. Also, the authors would like to
give a special acknowledgement to Bert Wijnen for his many detailed give a special acknowledgement to Bert Wijnen for his many detailed
reviews. Bert's assistance and guidance is greatly appreciated. reviews. Bert's assistance and guidance is greatly appreciated.
We would also like to thank Cheenu Srinivasan, Arun Viswanathan and We would also like to thank Cheenu Srinivasan, Arun Viswanathan and
Thomas D. Nadeau, the authors of the MPLS-LSR-STD-MIB [LSRMIB], for Thomas D. Nadeau, the authors of the MPLS-LSR-STD-MIB [RFC3813], for
their assistance. their assistance.
Additionally, there have been other members of the working group that Additionally, there have been other members of the working group that
have been very helpful: Alan Kullberg from NetPlane Systems gave have been very helpful: Alan Kullberg from NetPlane Systems gave
input on earlier versions of this document, and more recently, Riza input on earlier versions of this document, and more recently, Riza
Cetin of Alcatel and Neil Jerram of Data Connection who both provided Cetin of Alcatel and Neil Jerram of Data Connection who both provided
MIB objects. MIB objects.
Early versions of this document were also reviewed by colleagues at Early versions of this document were also reviewed by colleagues at
Nortel Networks and Ericsson. The authors would like to thank the Nortel Networks and Ericsson. The authors would like to thank the
following people: Leigh McLellan, Geetha Brown, Geping Chen and following people: Leigh McLellan, Geetha Brown, Geping Chen and
Charlan Zhou from Nortel Networks, and Zoltan Takacs and Bo Charlan Zhou from Nortel Networks, and Zoltan Takacs and Bo
Augustsson from Ericsson. Augustsson from Ericsson.
7. Normative References 6. References
[RFC2115] Brown, C., and F. Baker, "Management Information Base for 6.1. Normative References
Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2115] Brown, C. and F. Baker, "Management Information Base for
Requirement Levels", BCP 14, RFC 2119, Harvard University, Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
March 1997
[RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Textual Conventions and OBJECT-IDENTITIES for ATM Requirement Levels", BCP 14, RFC 2119, March 1997.
Management", RFC 2514, February 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Rose, M. and S. Waldbusser, "Structure of Management IANA Considerations Section in RFCs", BCP: 26, RFC 2434,
Information Version 2 (SMIv2)", STD 58, RFC 2578, April October 1998.
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2514] Noto, M., Spiegel, E., and K. Tesink, editors,
Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", "Definition of Textual Conventions and OBJECT-IDENTITIES
STD 58, RFC 2579, April 1999. for ATM Management", RFC 2514, February 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M. and S. Waldbusser, "Conformance Statements for "Structure of Management Information Version 2 (SMIv2)",
SMIv2", STD 58, RFC 2580, April 1999. STD 58, RFC 2578, April 1999.
[RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
using SMIv2", RFC 2863, June 2000. "Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Label Switching Architecture", RFC 3031, January 2001. "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC MIB", RFC 2863, June 2000.
3032, January 2001.
[RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching [RFC3031] Rosen, E., Viswananthan, A., and R. Callon,
on Frame Relay Networks Specification", RFC 3034, January "Multiprotocol Label Switching Architecture", RFC 3031,
2001. January 2001.
[RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
G., Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Switching", RFC 3035, January 2001. Encoding", RFC 3032, January 2001.
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label
Thomas, "LDP Specification", RFC 3036, January 2001. Switching on Frame Relay Networks Specification", RFC
3034, January 2001.
[RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E.,
January 2001. Swallow, G., Rekhter, Y., and P. Doolan, "MPLS using LDP
and ATM VC Switching", RFC 3035, January 2001.
[RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and
Machine", RFC 3215, January 2002. B. Thomas, "LDP Specification", RFC 3036, January 2001.
[RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037,
Base for the Differentiated Services Architecture", RFC January 2001.
3289, May 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. [RFC3215] Boscher, C., Cheval, P., Wu, L., and E. Gray, "LDP State
Schoenwaelder, "Textual Coventions for Internet Network Machine", RFC 3215, January 2002.
Addresses", RFC 3291, May 2002.
[RFC3413] Levi, D., Meyers, P., and B. Stewart, "Simple Network [RFC3289] Baker, F., Chan, K., and A. Smith, "Management
Management Protocol (SNMP) Applications", December 2002. Information Base for the Differentiated Services
Architecture", RFC 3289, May 2002.
[LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau, "MPLS [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Label Switching Router Management Information Base Using Schoenwaelder, "Textual Coventions for Internet Network
SMIv2", draft-ietf-mpls-lsr-mib-12.txt, August 2003. Addresses", RFC 3291, May 2002.
[MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual [RFC3413] Levi, D., Meyers, P. and B. Stewart, "Simple Network
Conventions for Multiprotocol Label Switching Management", Management Protocol (SNMP) Applications", STD 62, RFC
draft-ietf-mpls-tc-mib-09.txt, August 2003. 3413, December 2002.
8. Informative References [RFC3811] Nadeau, T. and J. Cucchiara, Editors "Definitions of
Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811, June 2004.
[RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", [RFC3813] Srinivansan, C., Viswanathan, A., and T. Nadeau,
RFC 2026, October 1996. "Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB)", RFC
3813, June 2004
[RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation 6.2. Informative References
over ATM Adaptation Layer 5", RFC 2684, September 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
"Introduction and Applicability Statements for Internet- Label Switching (MPLS) Management Overview", Work in
Standard Management Framework", RFC 3410, December 2002. Progress, September 2003.
[MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol [RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol
Label Switching (MPLS) Management Overview", draft-ietf- Encapsulation over ATM Adaptation Layer 5", RFC 2684,
mpls-mgmt-overview-08.txt, August 2003. September 1999.
9. Security Considerations [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
7. Security Considerations
This Security Considerations section consists of 4 subsections, one This Security Considerations section consists of 4 subsections, one
for each of the MIB Modules in this document. for each of the MIB Modules in this document.
9.1. Security Considerations for MPLS-LDP-STD-MIB 7.1. Security Considerations for MPLS-LDP-STD-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityTable contains objects to provision potential o the mplsLdpEntityTable contains objects to provision potential
skipping to change at page 130, line 5 skipping to change at page 101, line 7
associate an LSP with a FEC. Unauthorized access to objects in associate an LSP with a FEC. Unauthorized access to objects in
these tables, could result in disruption of traffic on the these tables, could result in disruption of traffic on the
network. This is especially true if an LDP session has been network. This is especially true if an LDP session has been
established. The use of stronger mechanisms such as SNMPv3 established. The use of stronger mechanisms such as SNMPv3
security should be considered where possible. Specifically, security should be considered where possible. Specifically,
SNMPv3 VACM and USM MUST be used with any v3 agent which SNMPv3 VACM and USM MUST be used with any v3 agent which
implements this MIB. Administrators should consider whether implements this MIB. Administrators should consider whether
read access to these objects should be allowed, since read read access to these objects should be allowed, since read
access may be undesirable under certain circumstances. access may be undesirable under certain circumstances.
Some of the readable objects in this MIB module i.e., "objects with a Some of the readable objects in this MIB module i.e., (objects with a
MAX-ACCESS other than not-accessible", may be considered sensitive or MAX-ACCESS other than not-accessible), may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSessionTable
mplsLdpSesStatsTable collectively show the LDP LSP network and mplsLdpSessionStatsTable collectively show the LDP LSP
topology. If an Administrator does not want to reveal the LDP network topology. If an Administrator does not want to reveal
LSP topology of the network, then these tables should be the LDP LSP topology of the network, then these tables should be
considered sensitive/vulnerable. considered sensitive/vulnerable.
9.2. Security Considerations for MPLS-LDP-ATM-STD-MIB 7.2. Security Considerations for MPLS-LDP-ATM-STD-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain
skipping to change at page 130, line 43 skipping to change at page 101, line 45
LDP-MIB. Unauthorized access to objects in these tables, could LDP-MIB. Unauthorized access to objects in these tables, could
result in disruption of traffic on the network. This is result in disruption of traffic on the network. This is
especially true if an LDP session has been established. The use especially true if an LDP session has been established. The use
of stronger mechanisms such as SNMPv3 security should be of stronger mechanisms such as SNMPv3 security should be
considered where possible. Specifically, SNMPv3 VACM and USM considered where possible. Specifically, SNMPv3 VACM and USM
MUST be used with any v3 agent which implements this MIB. MUST be used with any v3 agent which implements this MIB.
Administrators should consider whether read access to these Administrators should consider whether read access to these
objects should be allowed, since read access may be undesirable objects should be allowed, since read access may be undesirable
under certain circumstances. under certain circumstances.
Some of the readable objects in this MIB module i.e., "objects with a Some of the readable objects in this MIB module i.e., (objects with a
MAX-ACCESS other than not-accessible", may be considered sensitive or MAX-ACCESS other than not-accessible), may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the
Label Ranges for ATM. If an Administrator does not want to Label Ranges for ATM. If an Administrator does not want to
reveal this information then these tables should be considered reveal this information then these tables should be considered
sensitive/vulnerable and treated accordingly. sensitive/vulnerable and treated accordingly.
9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB 7.3. Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityFrameRelayTable and o the mplsLdpEntityFrameRelayTable and
skipping to change at page 131, line 35 skipping to change at page 102, line 35
Unauthorized access to objects in these tables, could result in Unauthorized access to objects in these tables, could result in
disruption of traffic on the network. This is especially true disruption of traffic on the network. This is especially true
if an LDP session has been established. The use of stronger if an LDP session has been established. The use of stronger
mechanisms such as SNMPv3 security should be considered where mechanisms such as SNMPv3 security should be considered where
possible. Specifically, SNMPv3 VACM and USM MUST be used with possible. Specifically, SNMPv3 VACM and USM MUST be used with
any v3 agent which implements this MIB. Administrators should any v3 agent which implements this MIB. Administrators should
consider whether read access to these objects should be allowed, consider whether read access to these objects should be allowed,
since read access may be undesirable under certain since read access may be undesirable under certain
circumstances. circumstances.
Some of the readable objects in this MIB module i.e., "objects with a Some of the readable objects in this MIB module i.e., (objects with a
MAX-ACCESS other than not-accessible", may be considered sensitive or MAX-ACCESS other than not-accessible), may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityFrameRelayTable and o the mplsLdpEntityFrameRelayTable and
mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame
Relay. If an Administrator does not want to reveal this Relay. If an Administrator does not want to reveal this
information then these tables should be considered information then these tables should be considered
sensitive/vulnerable and treated accordingly. sensitive/vulnerable and treated accordingly.
9.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB 7.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityGenericLRTable contains objects to provision o the mplsLdpEntityGenericLRTable contains objects to provision
skipping to change at page 132, line 29 skipping to change at page 103, line 29
Unauthorized access to objects in these tables, could result in Unauthorized access to objects in these tables, could result in
disruption of traffic on the network. This is especially true disruption of traffic on the network. This is especially true
if an LDP session has been established. The use of stronger if an LDP session has been established. The use of stronger
mechanisms such as SNMPv3 security should be considered where mechanisms such as SNMPv3 security should be considered where
possible. Specifically, SNMPv3 VACM and USM MUST be used with possible. Specifically, SNMPv3 VACM and USM MUST be used with
any v3 agent which implements this MIB. Administrators should any v3 agent which implements this MIB. Administrators should
consider whether read access to these objects should be allowed, consider whether read access to these objects should be allowed,
since read access may be undesirable under certain since read access may be undesirable under certain
circumstances. circumstances.
Some of the readable objects in this MIB module i.e., "objects with a Some of the readable objects in this MIB module i.e., (objects with a
MAX-ACCESS other than not-accessible", may be considered sensitive or MAX-ACCESS other than not-accessible), may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLdpEntityGenericLRTable shows the Label Ranges for o the mplsLdpEntityGenericLRTable shows the Label Ranges for
ethernet. If an Administrator does not want to reveal this ethernet. If an Administrator does not want to reveal this
information then these tables should be considered information then these tables should be considered
sensitive/vulnerable and treated accordingly. sensitive/vulnerable and treated accordingly.
9.5. Additional Security Considerations 7.5. Additional Security Considerations
The following paragraphs describe additional security considerations The following paragraphs describe additional security considerations
which are applicable to all 4 of the MIB Modules in this document. which are applicable to all 4 of the MIB Modules in this document.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec", Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8", provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms "for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy". authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET (change/create/delete) them.
10. IANA Considerations 8. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB
[MPLSTCMIB], MPLS related standards track MIB modules should be [MPLSTCMIB], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules
contained in this document, each of the following "IANA contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under Considerations" subsections lists new IANA assignments under the
the mplsStdMIB subtree. New assignments can only be made via a mplsStdMIB subtree. New assignments can only be made via a Standards
Standards Action as specified in [RFC2434]. Action as specified in [RFC2434].
10.1. IANA Considerations for MPLS-LDP-STD-MIB 8.1. IANA Considerations for MPLS-LDP-STD-MIB
The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD- The IANA has assigned { mplsStdMIB 4 } to the MPLS-LDP-STD-MIB module
MIB module specified in this document. specified in this document.
10.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB 8.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB
The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM- The IANA has assigned { mplsStdMIB 5 } to the MPLS-LDP-ATM-STD-MIB
module specified in this document.
8.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB
The IANA has assigned { mplsStdMIB 6 } to the MPLS-LDP-FRAME-RELAY-
STD-MIB module specified in this document. STD-MIB module specified in this document.
10.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB 8.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB
The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP- The IANA has assigned { mplsStdMIB 7 } to the MPLS-LDP-GENERIC-STD-
FRAME-RELAY-STD-MIB module specified in this document. MIB module specified in this document.
10.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB 9. Authors' Addresses
The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP- James V. Luciani
GENERIC-STD-MIB module specified in this document. Marconi Communications, Inc.
900 Chelmsford Street
Lowell, MA 01851
11. Intellectual Property Notice EMail: james_luciani@mindspring.com
Hans Sjostrand
ipUnplugged
P.O. Box 101 60
S-121 28 Stockholm, Sweden
Phone: +46 8 725 5900
EMail: hans@ipunplugged.com
Joan E. Cucchiara
Marconi Communications, Inc.
900 Chelmsford Street
Lowell, MA 01851
Phone: +1 978 275 7400
EMail: jcucchiara@mindspring.com
10. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11 [RFC2028]. found in BCP 78 and BCP 79.
Copies of claims of rights made available for publication and any
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
12. Authors' Addresses
James V. Luciani
Marconi Communications, Inc.
2000 Marconi Drive
Warrendale, PA 15086
USA
Email: james_luciani@mindspring.com
Hans Sjostrand
ipUnplugged
P.O. Box 101 60
S-121 28 Stockholm, Sweden
Phone: +46 8 725 5930
Email: hans@ipunplugged.com
Joan Cucchiara
Artel
237 Cedar Hill Street
Marlborough, MA 01752
Phone: +1-508-303-8200 x302
Email: jcucchiara@artel.com
13. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Acknowledgement
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an Funding for the RFC Editor function is currently provided by the
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING Internet Society.
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 178 change blocks. 
1343 lines changed or deleted 469 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/