draft-ietf-mpls-ldp-mib-12.txt   draft-ietf-mpls-ldp-mib-13.txt 
Network Working Group J. Cucchiara Network Working Group J. Cucchiara
Internet-Draft Artel Internet-Draft Artel
Expires December 2003 H. Sjostrand Expires February 2004 H. Sjostrand
IP Unplugged IP Unplugged
J. Luciani J. Luciani
Consultant Consultant
June 2003 August 2003
Definitions of Managed Objects for Definitions of Managed Objects for
the Multiprotocol Label Switching, Label Distribution Protocol (LDP) the Multiprotocol Label Switching, Label Distribution Protocol (LDP)
<draft-ietf-mpls-ldp-mib-12.txt> <draft-ietf-mpls-ldp-mib-13.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 ................................................. 3 1 Introduction ................................................. 4
2 The Internet-Standard Management Framework ................... 3 2 The Internet-Standard Management Framework ................... 4
3 Structure of the MIB Modules ................................. 4 3 Structure of the MIB Modules ................................. 5
3.1 Overview ................................................... 4 3.1 Overview ................................................... 5
3.2 Future Considerations ...................................... 4 3.2 Future Considerations ...................................... 5
3.3 Interface Indexing ......................................... 5 3.3 Interface Indexing ......................................... 6
3.4 Differences from the LDP Specification ..................... 5 3.4 Differences from the LDP Specification ..................... 6
3.5 The MPLS-LDP-STD-MIB Module ................................ 6 3.5 The MPLS-LDP-STD-MIB Module ................................ 7
3.5.1 LDP Scalar Objects ....................................... 6 3.5.1 LDP Scalar Objects ....................................... 7
3.5.2 The LDP Entity Table ..................................... 6 3.5.2 The LDP Entity Table ..................................... 7
3.5.2.1 Changing Values After Session Establishment ............ 7 3.5.2.1 Changing Values After Session Establishment ............ 8
3.5.3 The LDP Entity Statistics Table .......................... 8 3.5.3 The LDP Entity Statistics Table .......................... 9
3.5.4 The LDP Peer Table ....................................... 8 3.5.4 The LDP Peer Table ....................................... 9
3.5.5 The LDP Session Table .................................... 9 3.5.5 The LDP Session Table .................................... 10
3.5.6 The LDP Session Statistics Table ......................... 9 3.5.6 The LDP Session Statistics Table ......................... 10
3.5.7 The LDP Hello Adjacency Table ............................ 9 3.5.7 The LDP Hello Adjacency Table ............................ 10
3.5.8 The LDP LSP Table ........................................ 9 3.5.8 The LDP LSP Table ........................................ 10
3.5.9 The FEC Table ............................................ 10 3.5.9 The FEC Table ............................................ 11
3.5.10 The LDP Session Peer Address Table ...................... 10 3.5.10 The LDP Session Peer Address Table ...................... 11
3.6 LDP Notifications .......................................... 10 3.6 LDP Notifications .......................................... 11
3.7 LDP Notification Frequency ................................. 11 3.7 LDP Notification Frequency ................................. 12
4 MPLS Label Distribution Protocol MIB Definitions ............. 11 4 MPLS Label Distribution Protocol MIB Definitions ............. 12
4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 65 4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 66
4.1.1 The LDP Entity ATM Table ................................. 65 4.1.1 The LDP Entity ATM Table ................................. 66
4.1.2 The LDP Entity ATM Label Range Table ..................... 65 4.1.2 The LDP Entity ATM Label Range Table ..................... 66
4.1.3 The LDP ATM Session Table ................................ 65 4.1.3 The LDP ATM Session Table ................................ 66
4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 82 4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 83
4.2.1 The LDP Entity Frame Relay Table ........................ 82 4.2.1 The LDP Entity Frame Relay Table ......................... 84
4.2.2 The LDP Entity Frame Relay Label Range Table ............. 83 4.2.2 The LDP Entity Frame Relay Label Range Table ............. 84
4.2.3 The LDP Frame Relay Session Table ........................ 83 4.2.3 The LDP Frame Relay Session Table ........................ 84
4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 97 4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 98
5 Revision History ............................................. 105 5 Revision History ............................................. 107
5.1 Changes from <draft-ietf-mpls-ldp-mib-11.txt> .............. 105 5.1 Changes from <draft-ietf-mpls-ldp-mib-12.txt> .............. 107
5.2 Changes from <draft-ietf-mpls-ldp-mib-10.txt> .............. 105 5.2 Changes from <draft-ietf-mpls-ldp-mib-11.txt> .............. 107
5.3 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 105 5.3 Changes from <draft-ietf-mpls-ldp-mib-10.txt> .............. 107
5.3.1 Changes based on MIB Doctor Review Comments .............. 106 5.4 Changes from <draft-ietf-mpls-ldp-mib-09.txt> .............. 108
5.4 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 110 5.4.1 Changes based on MIB Doctor Review Comments .............. 108
5.5 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 113 5.5 Changes from <draft-ietf-mpls-ldp-mib-08.txt> .............. 113
5.6 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 114 5.6 Changes from <draft-ietf-mpls-ldp-mib-07.txt> .............. 115
5.7 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 114 5.7 Changes from <draft-ietf-mpls-ldp-mib-06.txt> .............. 116
5.8 Changes from <draft-ietf-mpls-ldp-mib-04.txt> .............. 116 5.8 Changes from <draft-ietf-mpls-ldp-mib-05.txt> .............. 117
5.9 Changes from <draft-ietf-mpls-ldp-mib-03.txt> .............. 118 5.9 Changes from <draft-ietf-mpls-ldp-mib-04.txt> .............. 118
5.10 Changes from <draft-ietf-mpls-ldp-mib-02.txt> ............. 120 5.10 Changes from <draft-ietf-mpls-ldp-mib-03.txt> ............. 119
5.11 Changes from <draft-ietf-mpls-ldp-mib-01.txt> ............. 121 5.11 Changes from <draft-ietf-mpls-ldp-mib-02.txt> ............. 122
5.12 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 122 5.12 Changes from <draft-ietf-mpls-ldp-mib-01.txt> ............. 123
6 Acknowledgments .............................................. 124 5.13 Changes from <draft-ietf-mpls-ldp-mib-00.txt> ............. 124
7 Normative References ......................................... 125 6 Acknowledgments .............................................. 125
8 Informative References ....................................... 127 7 Normative References ......................................... 126
9 Security Considerations ...................................... 127 8 Informative References ....................................... 128
9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 127 9 Security Considerations ...................................... 128
9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 128 9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 128
9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ... 129 9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 129
9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 130 9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ... 130
9.5 Additional Security Considerations ......................... 130 9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 131
10 IANA Considerations ......................................... 131 9.5 Additional Security Considerations ......................... 131
10.1 IANA Considerations for MPLS-LDP-STD-MIB .................. 131 10 IANA Considerations ......................................... 132
10.2 IANA Considerations for MPLS-LDP-ATM-STD-MIB .............. 131 10.1 IANA Considerations for MPLS-LDP-STD-MIB .................. 132
10.3 IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ...... 131 10.2 IANA Considerations for MPLS-LDP-ATM-STD-MIB .............. 132
10.4 IANA Considerations for MPLS-LDP-GENERIC-STD-MIB .......... 132 10.3 IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ...... 132
11 Intellectual Property Notice ................................ 132 10.4 IANA Considerations for MPLS-LDP-GENERIC-STD-MIB .......... 133
12 Authors' Addresses .......................................... 132 11 Intellectual Property Notice ................................ 133
13 Full Copyright Statement .................................... 133 12 Authors' Addresses .......................................... 133
13 Full Copyright Statement .................................... 134
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
skipping to change at page 6, line 41 skipping to change at page 6, line 41
subsequent SET request. subsequent SET request.
A second difference is the mplsLdpEntityConfGenericLRTable in the A second difference is the mplsLdpEntityConfGenericLRTable in the
MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a
way to reserve a range of generic labels, does not exist in the LDP way 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-MIB [MPLSTCMIB]. This TC MplsAtmVcIdentifier which is in the MPLS-TC-STD-MIB [MPLSTCMIB].
was added to restrict vci values to be greater than 31 as described This TC was added to restrict vci values to be greater than 31 as
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 table allows the Label Edge Router (LER) or the Label Switching This table allows the Label Edge Router (LER) or the Label Switching
Router (LSR) to initiate and/or receive requests to establish LDP Router (LSR) to initiate and/or receive requests to establish LDP
sessions. As the LDP protocol distributes labels and establishes sessions. As the LDP protocol distributes labels and establishes
skipping to change at page 11, line 40 skipping to change at page 11, line 40
The MPLS LDP Session Peer Address Table is a table which extends the The MPLS LDP Session Peer Address Table 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 2573 which enable or disable notifications from being generated. RFC 3413
[RFC2573] contains MIB modules which can be implemented that will [RFC3413] contains MIB modules which can be implemented that will
enable or disable these notifications from being generated. enable or disable these notifications from being generated.
The mplsLdpInitSessionThresholdExceeded notification indicates to the The mplsLdpInitSessionThresholdExceeded notification indicates to the
operator that there may be a misconfigured mplsLdpEntityEntry because operator that there may be a misconfigured mplsLdpEntityEntry because
the session associated with this Entity is not being established, and the session associated with this Entity is not being established, and
the Entity keeps trying to establish the session. A side effect of the Entity keeps trying to establish the session. A side effect of
this situation is that a row in the mplsLdpSessionTable may not be this situation is that a row in the mplsLdpSessionTable may not be
reaching the operational state as indicated by the reaching the operational state as indicated by the
mplsLdpSessionState object. If the value of mplsLdpSessionState object. If the value of
mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to
skipping to change at page 13, line 36 skipping to change at page 13, line 36
MplsLdpLabelType, MplsLdpLabelType,
MplsLspType, MplsLspType,
MplsLsrIdentifier, MplsLsrIdentifier,
MplsRetentionMode MplsRetentionMode
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
MplsIndexType MplsIndexType
FROM MPLS-LSR-STD-MIB; FROM MPLS-LSR-STD-MIB;
mplsLdpStdMIB MODULE-IDENTITY mplsLdpStdMIB MODULE-IDENTITY
LAST-UPDATED "200306281200Z" -- 28 June 2003 LAST-UPDATED "200308011200Z" -- 1 August 2003
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@artel.com)
Artel Artel
Hans Sjostrand (hans@ipunplugged.com) Hans Sjostrand (hans@ipunplugged.com)
ipUnplugged ipUnplugged
skipping to change at page 14, line 21 skipping to change at page 14, line 21
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
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 "200306281200Z" -- 28 June 2003 REVISION "200308011200Z" -- 1 August 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsStdMIB subId is 4, e.g. -- The requested mplsStdMIB subId is 4, e.g.
-- ::= { mplsStdMIB 4 } -- ::= { mplsStdMIB 4 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
skipping to change at page 50, line 39 skipping to change at page 50, line 39
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsFecEntry 6 } ::= { mplsFecEntry 6 }
mplsFecRowStatus OBJECT-TYPE mplsFecRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. If the value of this "The status of this conceptual row. If the value of this
object is 'active(1)', then none of the writable objects of object is 'active(1)', then none of the writable objects
this entry can be modified, except to set this object of this entry can be modified, except to set this object
to 'destroy(6)'. to 'destroy(6)'.
NOTE: if this row is being referenced by any entry in the NOTE: if this row is being referenced by any entry in
mplsLdpLspFecTable, then a request to destroy this row, will the mplsLdpLspFecTable, then a request to destroy
result in an inconsistentValue error." this row, will result in an inconsistentValue error."
::= { mplsFecEntry 7 } ::= { mplsFecEntry 7 }
-- --
-- LDP LSP FEC Table -- LDP LSP FEC Table
-- --
mplsLdpLspFecLastChange OBJECT-TYPE mplsLdpLspFecLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 54, line 10 skipping to change at page 54, line 10
Establishment', and again described in the Establishment', and again described in the
DESCRIPTION clause of the DESCRIPTION clause of the
mplsLdpEntityAdminStatus object) mplsLdpEntityAdminStatus object)
is to set the mplsLdpEntityAdminStatus to is to set the mplsLdpEntityAdminStatus to
down, thereby explicitly causing a session down, thereby explicitly causing a session
to be torn down. This will also to be torn down. This will also
cause this entry to be deleted. cause this entry to be deleted.
Then, set the mplsLdpEntityAdminStatus Then, set the mplsLdpEntityAdminStatus
to enable which enables a new session to be initiated. to enable which enables a new session to be initiated.
Once the session is initiated, an entry may be added to this Once the session is initiated, an entry may be
table to associate the new session with a FEC." added to this table to associate the new session
with a FEC."
::= { mplsLdpLspFecEntry 5 } ::= { mplsLdpLspFecEntry 5 }
-- --
-- Address Message/Address Withdraw Message Information -- Address Message/Address Withdraw Message Information
-- --
-- This information is associated with a specific Session -- This information is associated with a specific Session
-- because Label Address Messages are sent after session -- because Label Address Messages are sent after session
-- initialization has taken place. -- initialization has taken place.
-- --
skipping to change at page 67, line 33 skipping to change at page 67, line 33
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpAtmStdMIB MODULE-IDENTITY mplsLdpAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200306281200Z" -- 28 June 2003 LAST-UPDATED "200308011200Z" -- 1 August 2003
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@artel.com)
Artel Artel
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)
skipping to change at page 68, line 16 skipping to change at page 68, line 16
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
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 "200306281200Z" -- 28 June 2003 REVISION "200308011200Z" -- 1 August 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section -- Please see the IANA Considerations Section
-- the suggested mplsStdMIB subId is 5, e.g. -- the suggested mplsStdMIB subId is 5, e.g.
-- ::= { mplsStdMIB 5 } -- ::= { mplsStdMIB 5 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
skipping to change at page 70, line 27 skipping to change at page 70, line 27
SYNTAX INTEGER { SYNTAX INTEGER {
notSupported(0), notSupported(0),
vpMerge(1), vpMerge(1),
vcMerge(2), vcMerge(2),
vpAndVcMerge(3) vpAndVcMerge(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the Merge Capability of this Entity. "Denotes the Merge Capability of this Entity.
This is the EXACT value for the ATM Session Parameter, This is the EXACT value for the ATM Session
field M (for ATM Merge Capabilities). The ATM Session Parameter Parameter, field M (for ATM Merge Capabilities).
is an optional parameter in the Initialization Message. The ATM Session Parameter is an optional
parameter in the Initialization Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'M, ATM Merge Capabilities 'M, ATM Merge Capabilities
Specifies the merge capabilities of an ATM switch. The Specifies the merge capabilities of an ATM switch. The
following values are supported in this version of the following values are supported in this version of the
specification: specification:
Value Meaning Value Meaning
0 Merge not supported 0 Merge not supported
1 VP Merge supported 1 VP Merge supported
2 VC Merge supported 2 VC Merge supported
3 VP & VC Merge supported 3 VP & VC Merge supported
If the merge capabilities of the LSRs differ, then: If the merge capabilities of the LSRs differ, then:
- Non-merge and VC-merge LSRs may freely interoperate. - Non-merge and VC-merge LSRs may freely interoperate.
- The interoperability of VP-merge-capable switches with non- - The interoperability of VP-merge-capable switches
VP-merge-capable switches is a subject for future study. with non-VP-merge-capable switches is a subject
for future study. When the LSRs differ on the
When the LSRs differ on the use of VP-merge, the session is use of VP-merge, the session is established,
established, but VP merge is not used.' but VP merge is not used.'
Please refer to the following reference for a complete Please refer to the following reference for a
description of this feature." complete description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 2 } ::= { mplsLdpEntityAtmEntry 2 }
mplsLdpEntityAtmLRComponents OBJECT-TYPE mplsLdpEntityAtmLRComponents OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of Label Range Components in the Initialization "Number of Label Range Components in the Initialization
message. This also represents the number of entries message. This also represents the number of entries
in the mplsLdpEntityAtmLRTable which correspond in the mplsLdpEntityAtmLRTable which correspond
to this entry. to this entry.
This is the EXACT value for the ATM Session Parameter, This is the EXACT value for the ATM Session Parameter,
field N (for Number of label range components). The ATM field N (for Number of label range components).
Session Parameter is an optional parameter in the Initialization The ATM Session Parameter is an optional parameter
Message. in the Initialization Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'N, Number of label range components 'N, Number of label range components
Specifies the number of ATM Label Range Components Specifies the number of ATM Label Range
included in the TLV.' Components included in the TLV.'
Please refer to the following reference for a complete Please refer to the following reference for
description of this feature." a complete description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 3 } ::= { mplsLdpEntityAtmEntry 3 }
mplsLdpEntityAtmVcDirectionality OBJECT-TYPE mplsLdpEntityAtmVcDirectionality OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bidirectional(0), bidirectional(0),
unidirectional(1) unidirectional(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 'bidirectional(0)', "If the value of this object is 'bidirectional(0)',
a given VCI, within a given VPI, is used as a a given VCI, within a given VPI, is used as a
label for both directions independently. label for both directions independently.
If the value of this object is 'unidirectional(1)', If the value of this object is 'unidirectional(1)',
a given VCI within a VPI designates one direction. a given VCI within a VPI designates one direction.
This is the EXACT value for the ATM Session Parameter, This is the EXACT value for the ATM Session Parameter,
field D (for VC Directionality). The ATM Session Parameter field D (for VC Directionality). The ATM Session
is an optional parameter in the Initialization Message. Parameter is an optional parameter in the
Initialization Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'D, VC Directionality 'D, VC Directionality
A value of 0 specifies bidirectional VC capability, meaning the A value of 0 specifies bidirectional VC capability,
LSR can (within a given VPI) support the use of a given VCI as meaning the LSR can (within a given VPI) support
a label for both link directions independently. A value of 1 the use of a given VCI as a label for both link
specifies unidirectional VC capability, meaning (within a given directions independently. A value of 1
VPI) a given VCI may appear in a label mapping for one specifies unidirectional VC capability, meaning
direction on the link only. When either or both of the peers (within a given VPI) a given VCI may appear in
specifies unidirectional VC capability, both LSRs use a label mapping for one direction on the link
unidirectional VC label assignment for the link as follows. only. When either or both of the peers
The LSRs compare their LDP Identifiers as unsigned integers. specifies unidirectional VC capability, both
The LSR with the larger LDP Identifier may assign only odd- LSRs use unidirectional VC label assignment for
numbered VCIs in the VPI/VCI range as labels. The system with the link as follows. The LSRs compare their
the smaller LDP Identifier may assign only even-numbered VCIs LDP Identifiers as unsigned integers. The LSR
in the VPI/VCI range as labels.' with the larger LDP Identifier may assign
only odd-numbered VCIs in the VPI/VCI
range as labels. The system with the smaller
LDP Identifier may assign only even-numbered
VCIs in the VPI/VCI range as labels.'
Please refer to the following reference for a complete Please refer to the following reference
description of this feature." for a complete description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 4 } ::= { mplsLdpEntityAtmEntry 4 }
mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
direct(1), direct(1),
indirect(2) indirect(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The peer LSR may be connected indirectly by means of an "The peer LSR may be connected indirectly by means
ATM VP so that the VPI values may be different on either of an ATM VP so that the VPI values may be different
endpoint so the label MUST be encoded entirely within the on either endpoint so the label MUST be encoded
VCI field." entirely within the VCI field."
DEFVAL { direct } DEFVAL { direct }
::= { mplsLdpEntityAtmEntry 5 } ::= { mplsLdpEntityAtmEntry 5 }
mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The default VPI value for the non-MPLS connection. The "The default VPI value for the non-MPLS connection. The
default value of this is 0 (zero) but other values may default value of this is 0 (zero) but other values may
skipping to change at page 85, line 4 skipping to change at page 85, line 10
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex, mplsLdpEntityIndex,
mplsLdpPeerLdpId mplsLdpPeerLdpId
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpFrameRelayStdMIB MODULE-IDENTITY mplsLdpFrameRelayStdMIB MODULE-IDENTITY
LAST-UPDATED "200306281200Z" -- 28 June 2003 LAST-UPDATED "200308011200Z" -- 1 August 2003
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@artel.com)
Artel Artel
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)
skipping to change at page 85, line 35 skipping to change at page 85, line 42
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
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 "200306281200Z" -- 28 June 2003 REVISION "200308011200Z" -- 1 August 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsStdMIB subId is 6, e.g. -- The requested mplsStdMIB subId is 6, e.g.
-- ::= { mplsStdMIB 6 } -- ::= { mplsStdMIB 6 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
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 87, line 48 skipping to change at page 88, line 8
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This represents whether or not the Frame Relay merge "This represents whether or not the Frame Relay merge
capability is supported. This is the EXACT value for the capability is supported. This is the EXACT value for the
Frame Relay Session Parameter, field M (for Frame Relay Frame Relay Session Parameter, field M (for Frame Relay
Merge Capabilities). The Frame Relay Session Parameter Merge Capabilities). The Frame Relay Session Parameter
is an optional parameter in the Initialization Message. is an optional parameter in the Initialization Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'M, Frame Relay Merge Capabilities 'M, Frame Relay Merge Capabilities
Specifies the merge capabilities of a Frame Relay switch. The Specifies the merge capabilities of a Frame
following values are supported in this version of the Relay switch. The following values are
supported in this version of the
specification: specification:
Value Meaning Value Meaning
0 Merge not supported 0 Merge not supported
1 Merge supported 1 Merge supported
Non-merge and merge Frame Relay LSRs may freely interoperate.' Non-merge and merge Frame Relay LSRs may
freely interoperate.'
Please refer to the following reference for a complete Please refer to the following reference for a
description of this feature." complete description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 2 } ::= { mplsLdpEntityFrameRelayEntry 2 }
mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of Label Range Components in the Initialization "Number of Label Range Components in the Initialization
message. This also represents the number of entries message. This also represents the number of entries
in the mplsLdpEntityFrameRelayLRTable which correspond in the mplsLdpEntityFrameRelayLRTable which correspond
to this entry. to this entry.
This is the EXACT value for the Frame Relay Session Parameter, This is the EXACT value for the Frame Relay Session
field N (for Number of label range components). The Frame Relay Parameter, field N (for Number of label range
Session Parameter is an optional parameter in components). The Frame Relay Session Parameter
the Initialization Message. is an optional parameter in the Initialization
Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'N, Number of label range components 'N, Number of label range components
Specifies the number of Frame Relay Label Range Components Specifies the number of Frame Relay Label
included in the TLV.' Range Components included in the TLV.'
Please refer to the following reference for a
Please refer to the following reference for a complete complete description of this feature."
description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 3 } ::= { mplsLdpEntityFrameRelayEntry 3 }
mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bidirectional(0), bidirectional(0),
unidirection(1) unidirection(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 'bidirectional(0)', then "If the value of this object is 'bidirectional(0)', then
the LSR supports the use of a given DLCI as a label for the LSR supports the use of a given DLCI as a label for
both directions independently. If the value of both directions independently. If the value of
this object is 'unidirectional(1)', then the LSR this object is 'unidirectional(1)', then the LSR
uses the given DLCI as a label in only one direction. uses the given DLCI as a label in only one direction.
This is the EXACT value for the Frame Relay Session Parameter, This is the EXACT value for the Frame Relay Session
field D (for VC Directionality). The Frame Relay Session Parameter Parameter, field D (for VC Directionality). The
is an optional parameter in the Initialization Message. Frame Relay Session Parameter is an optional
parameter in the Initialization Message.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'D, VC Directionality 'D, VC Directionality
A value of 0 specifies bidirectional VC capability, meaning the A value of 0 specifies bidirectional VC capability,
LSR can support the use of a given DLCI as a label for both meaning the LSR can support the use of a given
link directions independently. A value of 1 specifies DLCI as a label for both link directions
unidirectional VC capability, meaning a given DLCI may appear independently. A value of 1 specifies
in a label mapping for one direction on the link only. When unidirectional VC capability, meaning a given
either or both of the peers specifies unidirectional VC DLCI may appear in a label mapping for one
capability, both LSRs use unidirectional VC label assignment direction on the link only. When either or both
for the link as follows. The LSRs compare their LDP of the peers specifies unidirectional VC
Identifiers as unsigned integers. The LSR with the larger LDP capability, both LSRs use unidirectional VC
Identifier may assign only odd-numbered DLCIs in the range as label assignment for the link as follows. The
labels. The system with the smaller LDP Identifier may assign LSRs compare their LDP Identifiers as unsigned
only even-numbered DLCIs in the range as labels.' integers. The LSR with the larger LDP
Identifier may assign only odd-numbered DLCIs
Please refer to the following reference for a complete in the range as labels. The system with the
description of this feature." smaller LDP Identifier may assign only
even-numbered DLCIs in the range as labels.'
Please refer to the following reference for a
complete description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 4 } ::= { mplsLdpEntityFrameRelayEntry 4 }
mplsLdpEntityFrameRelayStorageType OBJECT-TYPE mplsLdpEntityFrameRelayStorageType 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.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
skipping to change at page 91, line 38 skipping to change at page 92, line 6
mplsLdpEntityFrameRelayLRLen INTEGER, mplsLdpEntityFrameRelayLRLen INTEGER,
mplsLdpEntityFrameRelayLRStorageType StorageType, mplsLdpEntityFrameRelayLRStorageType StorageType,
mplsLdpEntityFrameRelayLRRowStatus RowStatus mplsLdpEntityFrameRelayLRRowStatus RowStatus
} }
mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lower bound which is supported. This value should "The lower bound which is supported. This value
be the same as that in the Frame Relay Label Range should be the same as that in the Frame Relay Label
Component's Minimum DLCI field. The value of zero Range Component's Minimum DLCI field. The value
is valid for the minimum DLCI field of the label." of zero is valid for the minimum DLCI field of
the label."
REFERENCE REFERENCE
"RFC3034, Use of Label Switching on Frame Relay Networks "RFC3034, Use of Label Switching on Frame Relay
Specification." Networks Specification."
::= { mplsLdpEntityFrameRelayLREntry 1 } ::= { mplsLdpEntityFrameRelayLREntry 1 }
mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The upper bound which is supported. This value should "The upper bound which is supported. This value
be the same as that in the Frame Relay Label Range should be the same as that in the Frame Relay Label
Component's Maximum DLCI field." Range Component's Maximum DLCI field."
::= { mplsLdpEntityFrameRelayLREntry 2 } ::= { mplsLdpEntityFrameRelayLREntry 2 }
mplsLdpEntityFrameRelayLRLen OBJECT-TYPE mplsLdpEntityFrameRelayLRLen OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
tenDlciBits(0), tenDlciBits(0),
twentyThreeDlciBits(2) twentyThreeDlciBits(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the length of the DLCI bits. "This object specifies the length of the DLCI bits.
This is the EXACT value for the Len field of the This is the EXACT value for the Len field of the
Frame Relay Label Range Component. Frame Relay Label Range Component.
The description from rfc3036.txt is: The description from rfc3036.txt is:
'Len 'Len
This field specifies the number of bits of the DLCI. The This field specifies the number of bits of the DLCI.
following values are supported: The following values are supported:
Len DLCI bits Len DLCI bits
0 10 0 10
2 23 2 23
Len values 1 and 3 are reserved.' Len values 1 and 3 are reserved.'
Please refer to the following reference for a complete Please refer to the following reference for a complete
description of this feature." description of this feature."
REFERENCE REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message." "RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayLREntry 3 } ::= { mplsLdpEntityFrameRelayLREntry 3 }
mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE mplsLdpEntityFrameRelayLRStorageType 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.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
skipping to change at page 94, line 4 skipping to change at page 94, line 18
mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::= mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 2 } { mplsLdpFrameRelayObjects 2 }
mplsLdpFrameRelaySessionTable OBJECT-TYPE mplsLdpFrameRelaySessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Frame Relay label range intersections "A table of Frame Relay label range intersections
between the LDP Entities and LDP Peers. between the LDP Entities and LDP Peers.
Each row represents a single label range intersection. Each row represents a single label range intersection.
NOTE: this table cannot use the 'AUGMENTS' NOTE: this table cannot use the 'AUGMENTS'
clause because there is not necessarily a one-to-one clause because there is not necessarily a one-to-one
mapping between this table and the mplsLdpSessionTable." mapping between this table and the
mplsLdpSessionTable."
::= { mplsLdpFrameRelaySessionObjects 1 } ::= { mplsLdpFrameRelaySessionObjects 1 }
mplsLdpFrameRelaySessionEntry OBJECT-TYPE mplsLdpFrameRelaySessionEntry OBJECT-TYPE
SYNTAX MplsLdpFrameRelaySessionEntry SYNTAX MplsLdpFrameRelaySessionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents information on a "An entry in this table represents information on a
single label range intersection between an single label range intersection between an
LDP Entity and LDP Peer. LDP Entity and LDP Peer.
skipping to change at page 94, line 34 skipping to change at page 95, line 4
mplsLdpPeerLdpId, mplsLdpPeerLdpId,
mplsLdpFrameRelaySessionMinDlci mplsLdpFrameRelaySessionMinDlci
} }
::= { mplsLdpFrameRelaySessionTable 1 } ::= { mplsLdpFrameRelaySessionTable 1 }
MplsLdpFrameRelaySessionEntry ::= SEQUENCE { MplsLdpFrameRelaySessionEntry ::= SEQUENCE {
mplsLdpFrameRelaySessionMinDlci DLCI, mplsLdpFrameRelaySessionMinDlci DLCI,
mplsLdpFrameRelaySessionMaxDlci DLCI, mplsLdpFrameRelaySessionMaxDlci DLCI,
mplsLdpFrameRelaySessionLen INTEGER mplsLdpFrameRelaySessionLen INTEGER
} }
mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lower bound of DLCIs which are supported. "The lower bound of DLCIs which are supported.
The value of zero is a valid value for the The value of zero is a valid value for the
minimum DLCI field of the label." minimum DLCI field of the label."
REFERENCE REFERENCE
"RFC3034, Use of Label Switching on Frame Relay Networks "RFC3034, Use of Label Switching on Frame Relay
Specification." Networks Specification."
::= { mplsLdpFrameRelaySessionEntry 1 } ::= { mplsLdpFrameRelaySessionEntry 1 }
mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The upper bound of DLCIs which are supported." "The upper bound of DLCIs which are supported."
::= { mplsLdpFrameRelaySessionEntry 2 } ::= { mplsLdpFrameRelaySessionEntry 2 }
skipping to change at page 99, line 16 skipping to change at page 99, line 31
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsLdpEntityLdpId, mplsLdpEntityLdpId,
mplsLdpEntityIndex mplsLdpEntityIndex
FROM MPLS-LDP-STD-MIB FROM MPLS-LDP-STD-MIB
; ;
mplsLdpGenericStdMIB MODULE-IDENTITY mplsLdpGenericStdMIB MODULE-IDENTITY
LAST-UPDATED "200306281200Z" -- 28 June 2003 LAST-UPDATED "200308011200Z" -- 1 August 2003
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@artel.com)
Artel Artel
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)
skipping to change at page 99, line 44 skipping to change at page 100, line 14
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
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 "200306281200Z" -- 28 June 2003 REVISION "200308011200Z" -- 1 August 2003
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsStdMIB subId is 7, e.g. -- The requested mplsStdMIB subId is 7, e.g.
-- ::= { mplsStdMIB 7 } -- ::= { mplsStdMIB 7 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
--**************************************************************** --****************************************************************
mplsLdpGenericObjects mplsLdpGenericObjects
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 } OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 }
mplsLdpGenericConformance mplsLdpGenericConformance
skipping to change at page 106, line 10 skipping to change at page 107, line 10
using Generic Labels as the Layer 2." using Generic Labels as the Layer 2."
::= { mplsLdpGenericGroups 1 } ::= { mplsLdpGenericGroups 1 }
END END
5. Revision History 5. Revision History
NOTE TO RFC-Editor: before publishing this document as an RFC, NOTE TO RFC-Editor: before publishing this document as an RFC,
please remove this Revision History (change log) section. please remove this Revision History (change log) section.
5.1. Changes from <draft-ietf-mpls-ldp-mib-11.txt> 5.1. 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.2. Changes from <draft-ietf-mpls-ldp-mib-11.txt>
Updated with comments from the 3rd Last Call for this MIB which took Updated with comments from the 3rd Last Call for this MIB which took
place, Thursday, June 12 to June 24, 2003. place, Thursday, June 12 to June 24, 2003.
Updated with last call comments from Adrian Farell posted to the MPLS Updated with last call comments from Adrian Farrel posted to the MPLS
Working Group email list on June 12, 2003. Working Group email list on June 12, 2003.
Updated the 2 outstanding issues from Bert's email May 9th which was 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 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 version 10, so were addressed in version 11: 1) updated #3 from that
email and 2) reviewed all the InetAddressType and InetAddress objects email and 2) reviewed all the InetAddressType and InetAddress objects
to make sure that descriptions were per rfc3291. to make sure that descriptions were per rfc3291.
5.2. Changes from <draft-ietf-mpls-ldp-mib-10.txt> 5.3. Changes from <draft-ietf-mpls-ldp-mib-10.txt>
Renamed the MIB module to include Std and also updated the IANA Renamed the MIB module to include Std and also updated the IANA
Considerations Section to use mplsStdMIB. Considerations Section to use mplsStdMIB.
Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet 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 update #3 from that email and 2) did not yet review all the
InetAddressType and InetAddress objects to make sure that InetAddressType and InetAddress objects to make sure that
descriptions were per rfc3291. descriptions were per rfc3291.
Changed Ses to Session for clarity. Changed Ses to Session for clarity.
5.3. Changes from <draft-ietf-mpls-ldp-mib-09.txt> 5.4. Changes from <draft-ietf-mpls-ldp-mib-09.txt>
Added the new MIB boiler plate and associated MIB reference changes. Added the new MIB boiler plate and associated MIB reference changes.
Reworked the OID tree structure so that the Modules only have the Reworked the OID tree structure so that the Modules only have the
mplsMIB subid dependency. This was discussed in mpls wg email mplsMIB subid dependency. This was discussed in mpls wg email
(discussion was mostly between Bert, Tom and Joan). (discussion was mostly between Bert, Tom and Joan).
Added IANA Considerations section. This contains 4 subsections, one Added IANA Considerations section. This contains 4 subsections, one
per MIB module. per MIB module.
Updated and added new references as needed. Updated and added new references as needed.
Changed mplsMIB subid values to agree with the latest "Multiprotocol Changed mplsMIB subid values to agree with the latest "Multiprotocol
Label Switching (MPLS) Management Overview" document, [MPLSMGMT]. Label Switching (MPLS) Management Overview" document, [MPLSMGMT].
Moved MIB modules around so that they would appear in subId order. 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 Generic MIB module is shown last, since the subid is 7 (which is
the last (and largest) subid requested by IANA. the last (and largest) subid requested by IANA.
5.3.1. Changes based on MIB Doctor Review Comments 5.4.1. Changes based on MIB Doctor Review Comments
The following changes are based on comments from the MIB DR Review. 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, The comments are from email to the mpls working group dated, Dec 6,
2002. These comments are quoted and prefaced by "REQ: comment goes 2002. These comments are quoted and prefaced by "REQ: comment goes
here", and then followed by our resolution. here", and then followed by our resolution.
"REQ: - missing IPR section". RSP: it has been added. "REQ: - missing IPR section". RSP: it has been added.
"REQ: - Security considerations probably needs more work "REQ: - Security considerations probably needs more work
Security ADs want you to explain what the vulnerabilities/risks Security ADs want you to explain what the vulnerabilities/risks
skipping to change at page 111, line 33 skipping to change at page 113, line 5
"REQ:- I see the xxxDlci index objects start at zero. "REQ:- I see the xxxDlci index objects start at zero.
Pls add to DESCRIPTION clauses why zero must be an index.". RSP: 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 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 statement was added about this. Also, used the DLCI TC from
rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB 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 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:- zero. A statement was added to this Index also. "REQ:-
mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP: mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP:
done. done.
5.4. Changes from <draft-ietf-mpls-ldp-mib-08.txt> 5.5. Changes from <draft-ietf-mpls-ldp-mib-08.txt>
The following changes are from the IESG MIB review. The following changes are from the IESG MIB review.
Changed "Label Switch Router" to "Label Switching Router". Changed "Label Switch Router" to "Label Switching Router".
Spelling errors fixed (unlabelled, atttempt, subsytem). Spelling errors fixed (unlabelled, atttempt, subsytem).
Changed some of the enums to start at 1, instead of zero: Changed some of the enums to start at 1, instead of zero:
mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus.
skipping to change at page 112, line 46 skipping to change at page 114, line 15
Removed AddressFamilyNumbers TC and used InetAddressType TC from the Removed AddressFamilyNumbers TC and used InetAddressType TC from the
INET-ADDRESS-MIB. One of the MIB compilers as a warning because INET-ADDRESS-MIB. One of the MIB compilers as a warning because
apparently one is expected to use InetAddressType and InetAddress apparently one is expected to use InetAddressType and InetAddress
together (although, think this restriction is too restrictive). Also, together (although, think this restriction is too restrictive). Also,
removed the reference for the Address Family Numbers MIB. removed the reference for the Address Family Numbers MIB.
Changed the name TargPeer to TargetPeer. Changed the name TargPeer to TargetPeer.
Removed the Enable/Disable trap objects: Removed the Enable/Disable trap objects:
mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC
2573 should be used to eable/disable traps. 3413 should be used to enable/disable traps.
Removed the import for "transmission" and instead, imported "mplsMIB Removed the import for "transmission" and instead, imported "mplsMIB
from the MPLS-TC-MIB". from the MPLS-TC-STD-MIB".
Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated
the DESCRIPTION clause. Also, the PVL abbreviation was expanded to the DESCRIPTION clause. Also, the PVL abbreviation was expanded to
PathVectorLimit for other objects. PathVectorLimit for other objects.
Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL
into one object: mplsLdpPeerPathVectorLimit and updated the into one object: mplsLdpPeerPathVectorLimit and updated the
DESCRIPTION clause. DESCRIPTION clause.
mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS- mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS-
skipping to change at page 114, line 5 skipping to change at page 115, line 18
Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus
objects. RowStatus now reflects the status of the row, and Admin objects. RowStatus now reflects the status of the row, and Admin
status controls enabling/disabling the entry. status controls enabling/disabling the entry.
Updated the DESCRIPTION clauses for the objects in the Updated the DESCRIPTION clauses for the objects in the
mplsLdpEntityStatsTable to refer to the mplsLdpEntityStatsTable to refer to the
mplsLdpEntityDiscontinuityTime object. mplsLdpEntityDiscontinuityTime object.
Changed StorType to StorageType. Changed StorType to StorageType.
5.5. Changes from <draft-ietf-mpls-ldp-mib-07.txt> 5.6. Changes from <draft-ietf-mpls-ldp-mib-07.txt>
There were three types of changes: the first change was that all the 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 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were
moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc- moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc-
mib-00.txt". The Textual Conventions are now IMPORTED from mib-00.txt". The Textual Conventions are now IMPORTED from
[MPLSTCMIB]. The second type of change was updates based on comments [MPLSTCMIB]. The second type of change was updates based on comments
from the IESG. These changes will be discussed below. The third from the IESG. These changes will be discussed below. The third
type of changes were based on minor editorial changes from the co- type of changes were based on minor editorial changes from the co-
authors. authors.
skipping to change at page 115, line 13 skipping to change at page 116, line 27
mplsLdpEntityInitSesTrapEnable object is useless and was removed mplsLdpEntityInitSesTrapEnable object is useless and was removed
since setting mplsLdpEntityInitSesThreshold=0 acheives the same since setting mplsLdpEntityInitSesThreshold=0 acheives the same
thing. Also removed it from the descriptive text in section 3. thing. Also removed it from the descriptive text in section 3.
Page 47, mplsLdpSessionDiscontinuityTime The initial value of this Page 47, mplsLdpSessionDiscontinuityTime The initial value of this
was changed to be sysUpTime instead of zero. sysUpTime for when the was changed to be sysUpTime instead of zero. sysUpTime for when the
session starts is more meaningful and was added to the Session 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 also. Also, added the Session specific stats to the
up/down traps. up/down traps.
5.6. Changes from <draft-ietf-mpls-ldp-mib-06.txt> 5.7. Changes from <draft-ietf-mpls-ldp-mib-06.txt>
All changes were from the second last call which took place Thursday, All changes were from the second last call which took place Thursday,
July 20th, until Thursday, July 27th, 2000 and are described in the July 20th, until Thursday, July 27th, 2000 and are described in the
remainder of this section. remainder of this section.
Remove the reference to the MPLS framework document. Remove the reference to the MPLS framework document.
Add an mplsFecIndexNext type of object. Add an mplsFecIndexNext type of object.
Change the conformance of the FEC table objects to be part of the Change the conformance of the FEC table objects to be part of the
mplsLdpGeneralGroup. mplsLdpGeneralGroup.
The mplsLdpEntityConfGenericTable is no longer needed because the The mplsLdpEntityConfGenericTable is no longer needed because the
functionality has been absorbed by the functionality has been absorbed by the
mplsLdpEntityConfGenericLabelRangeTable. The mplsLdpEntityConfGenericLabelRangeTable. The
mplsLdpEntityConfGenericTable has been removed and the front section mplsLdpEntityConfGenericTable has been removed and the front section
was updated accordingly. was updated accordingly.
Other editorial issues, updating references, typos and so forth. Other editorial issues, updating references, typos and so forth.
5.7. Changes from <draft-ietf-mpls-ldp-mib-05.txt> 5.8. Changes from <draft-ietf-mpls-ldp-mib-05.txt>
The majority of changes in this revision are based on Last Call The majority of changes in this revision are based on Last Call
comments which were received during the last call from Thursday, comments which were received during the last call from Thursday,
March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. March 9, 2000 to Friday, March 17, 2000, or slightly thereafter.
Also, changes were made to agree with the latest specifications. Also, changes were made to agree with the latest specifications.
These changes are described in this section. These changes are described in this section.
Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls- Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-
ldp-08.txt. Specifically, removing references to IPv4/IP and using ldp-08.txt. Specifically, removing references to IPv4/IP and using
router id, as appropriate. router id, as appropriate.
skipping to change at page 117, line 28 skipping to change at page 118, line 43
one for TCP and one for UDP. The names are one for TCP and one for UDP. The names are
Typo in the description for the Typo in the description for the
The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The
mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to
show that these two tables are related. There has been wording added show that these two tables are related. There has been wording added
to the mplsLdpSessionEntry description and to the description for the to the mplsLdpSessionEntry description and to the description for the
mplsLdpPeerTable. mplsLdpPeerTable.
5.8. Changes from <draft-ietf-mpls-ldp-mib-04.txt> 5.9. Changes from <draft-ietf-mpls-ldp-mib-04.txt>
Editorial changes, fixing typo's, fixing wrapping lines, etc. Editorial changes, fixing typo's, fixing wrapping lines, etc.
Updated references for latest drafts, and added [RFC3032] and Updated references for latest drafts, and added [RFC3032] and
[RFC3034] to Reference Section. [RFC3034] to Reference Section.
Added to the Acknowledgements Section. Added to the Acknowledgements Section.
Changed the SYNTAX and DESCRIPTION of the Changed the SYNTAX and DESCRIPTION of the
'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support
skipping to change at page 119, line 44 skipping to change at page 121, line 14
object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to
fit in with the 'mplsLdpEntityFrameRelayParmsTable'. fit in with the 'mplsLdpEntityFrameRelayParmsTable'.
Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen
object. (The 17 bit length was dropped by the Frame Relay Forum and object. (The 17 bit length was dropped by the Frame Relay Forum and
thus, is no longer required.) thus, is no longer required.)
Corrected the range of the 'mplsLdpEntityIndexNext' object to include Corrected the range of the 'mplsLdpEntityIndexNext' object to include
0 (zero). 0 (zero).
5.9. Changes from <draft-ietf-mpls-ldp-mib-03.txt> 5.10. Changes from <draft-ietf-mpls-ldp-mib-03.txt>
Reworded the description of the mplsLdpAtmSessionTable to clarify Reworded the description of the mplsLdpAtmSessionTable to clarify
that one or MORE label range intersection(s) is/are represented in that one or MORE label range intersection(s) is/are represented in
this table. this table.
Reworded the description of the mplsLdpFrameRelaySessionTable to Reworded the description of the mplsLdpFrameRelaySessionTable to
clarify that one or MORE label range intersection(s) is/are clarify that one or MORE label range intersection(s) is/are
represented in this table. represented in this table.
Added a new index, mplsLdpSessionPeerIndex, to the Added a new index, mplsLdpSessionPeerIndex, to the
skipping to change at page 121, line 19 skipping to change at page 122, line 37
The mplsLdpSessionIndex was removed throughout the MIB. This was The mplsLdpSessionIndex was removed throughout the MIB. This was
replaced by the object mplsLdpSessionDiscontinuityTime. The replaced by the object mplsLdpSessionDiscontinuityTime. The
motivation was to reduce the number of indices. motivation was to reduce the number of indices.
The descriptions for the objects in the mplsLdpSessionStatsTable, The descriptions for the objects in the mplsLdpSessionStatsTable,
mplsLdpSessionStatsUnknownMessageTypeErrors and mplsLdpSessionStatsUnknownMessageTypeErrors and
mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a
reference to the mplsLdpSessionDiscontinuityTime object. reference to the mplsLdpSessionDiscontinuityTime object.
5.10. Changes from <draft-ietf-mpls-ldp-mib-02.txt> 5.11. Changes from <draft-ietf-mpls-ldp-mib-02.txt>
Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and
mplsLdpEntityIndexNext. mplsLdpEntityIndexNext.
Added the following objects to the mplsLdpEntityTable: Added the following objects to the mplsLdpEntityTable:
mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus,
mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer,
mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and
mplsLdpEntityHelloHoldTimer. mplsLdpEntityHelloHoldTimer.
skipping to change at page 122, line 5 skipping to change at page 123, line 19
Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to
include the minimum VPI/VCI. This is to ensure that indices in this include the minimum VPI/VCI. This is to ensure that indices in this
table are unique. table are unique.
Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to
include the minimum DLCI value. This is to ensure that indices in include the minimum DLCI value. This is to ensure that indices in
this table are unique. this table are unique.
Added [RFC3036] to Reference Section. Added [RFC3036] to Reference Section.
5.11. Changes from <draft-ietf-mpls-ldp-mib-01.txt> 5.12. Changes from <draft-ietf-mpls-ldp-mib-01.txt>
The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of
the LDP Specification [RFC3036]. the LDP Specification [RFC3036].
The front section was updated. The front section was updated.
The MIB was made to be less ATM-centric. Essentially, the ATM The MIB was made to be less ATM-centric. Essentially, the ATM
specific objects where removed from the tables and placed in 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 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 be created in the ATM/FR/etc. type table. Apropos compliance
skipping to change at page 123, line 15 skipping to change at page 124, line 32
The mplsLdpSessionStatsTable was added to count statics based on a The mplsLdpSessionStatsTable was added to count statics based on a
per Session basis. per Session basis.
The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no
need to configure information for a Peer. All information for a peer need to configure information for a Peer. All information for a peer
is learned, thus peer information is read-only. is learned, thus peer information is read-only.
(Editorial) References were updated to reflect the documents which (Editorial) References were updated to reflect the documents which
this version was based on. this version was based on.
5.12. Changes from <draft-ietf-mpls-ldp-mib-00.txt> 5.13. Changes from <draft-ietf-mpls-ldp-mib-00.txt>
Textual conventions were added for the LSR Identifier and the LDP Textual conventions were added for the LSR Identifier and the LDP
Identifier. Identifier.
Top-level mib structure was added. The LDP MIB falls under a proposed Top-level mib structure was added. The LDP MIB falls under a proposed
hierarchy of mpls.mplsProtocols. hierarchy of mpls.mplsProtocols.
The mib hierarchy within the LDP MIB was also changed. A new branch, The mib hierarchy within the LDP MIB was also changed. A new branch,
under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This
branch is mplsLdpLsrObjects. Currently, this contains several new branch is mplsLdpLsrObjects. Currently, this contains several new
skipping to change at page 126, line 19 skipping to change at page 127, line 19
Machine", RFC 3215, January 2002. Machine", RFC 3215, January 2002.
[RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information [RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information
Base for the Differentiated Services Architecture", RFC Base for the Differentiated Services Architecture", RFC
3289, May 2002. 3289, May 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J.
Schoenwaelder, "Textual Coventions for Internet Network Schoenwaelder, "Textual Coventions for Internet Network
Addresses", RFC 3291, May 2002. Addresses", RFC 3291, May 2002.
[LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label [RFC3413] Levi, D., Meyers, P., and B. Stewart, "Simple Network
Switching Router Management Information Base Using SMIv2", Management Protocol (SNMP) Applications", December 2002.
draft-ietf-mpls-lsr-mib-11.txt, June 2003.
[LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau, "MPLS
Label Switching Router Management Information Base Using
SMIv2", draft-ietf-mpls-lsr-mib-12.txt, August 2003.
[MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual [MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual
Conventions for Multiprotocol Label Switching Management", Conventions for Multiprotocol Label Switching Management",
draft-ietf-mpls-tc-mib-08.txt, June 2003. draft-ietf-mpls-tc-mib-09.txt, August 2003.
8. Informative References 8. Informative References
[RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3",
RFC 2026, October 1996. RFC 2026, October 1996.
[RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation
over ATM Adaptation Layer 5", RFC 2684, September 1999. over ATM Adaptation Layer 5", RFC 2684, September 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
Label Switching (MPLS) Management Overview", draft-ietf- Label Switching (MPLS) Management Overview", draft-ietf-
mpls-mgmt-overview-06.txt, June 2003. mpls-mgmt-overview-08.txt, August 2003.
9. Security Considerations 9. 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 9.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
 End of changes. 

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