draft-ietf-mpls-lc-if-mib-01.txt   draft-ietf-mpls-lc-if-mib-02.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: October 2004 Cisco Systems, Inc. Expires: December 2004 Cisco Systems, Inc.
January 2004 May 2004
Multiprotocol Label Switching (MPLS) Label-Controlled ATM Multiprotocol Label Switching (MPLS) Label-Controlled ATM
and Frame-Relay Management Interface Definition and Frame-Relay Management Interface Definition
draft-ietf-mpls-lc-if-mib-01.txt draft-ietf-mpls-lc-if-mib-02.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. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the In ternet Engineering Internet-Drafts are working documents of the In ternet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
in progress." in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Table of Contents Table of Contents
1. Abstract .................................................. 2 1. Abstract .................................................. 2
2. Introduction .............................................. 3 2. Introduction .............................................. 2
3. Terminology ............................................... 3 3. Terminology ............................................... 2
4. The SNMP Management Framework ............................. 3 4. The SNMP Management Framework ............................. 2
5. Interface Stacking of LC-ATM and LC-FR .................... 5 5. Interface Stacking of LC-ATM and LC-FR and LC-FR Interfaces. 3
6. MPLS Label Controlled ATM MIB Definitions ................. 13 6. MPLS Label Controlled ATM MIB Definitions .................. 3
7. MPLS Label Controlled Frame Relay MIB Definitions ......... 13 7. MPLS Label Controlled Frame Relay MIB Definitions .......... 9
8. Security Considerations ................................... 51 8. Security Considerations ................................... 14
9. References ................................................ 52 9. References ................................................ 15
9.1 Normative References...................................... 52 9.1 Normative References...................................... 15
9.2 Informative References.................................... 52 9.2 Informative References.................................... 16
10. Authors' Addresses ....................................... 54 10. Authors' Addresses ....................................... 17
11. Full Copyright Statement ................................. 55 11. Full Copyright Statement ................................. 17
12. Intellectual Property Notice ............................ 52 12. Intellectual Property Notice ............................ 17
13. IANA Considerations ..................................... 52 13. IANA Considerations ..................................... 18
14.1. IANA Considerations for MPLS-LC-ATM-MIB ............... 52 14.1. IANA Considerations for MPLS-LC-ATM-MIB ............... 18
14.2. IANA Considerations for MPLS-LC-FR-MIB ................ 52 14.2. IANA Considerations for MPLS-LC-FR-MIB ................ 18
15 Acknowledgments............................................ 18
1. Abstract 1. Abstract
This memo defines how label switching controlled Frame-Relay This memo defines how label switching controlled Frame-Relay
and ATM interfaces can be realized given the interface stacking and ATM interfaces can be realized given the interface stacking
as defined in the MPLS-LSR and MPLS-TE MIBs. as defined in the MPLS-LSR-STD and MPLS-TE-STD MIBs.
2. Introduction 2. Introduction
This memo defines how label switching controlled Frame-Relay This memo defines how label switching controlled Frame-Relay
[RFC3034] and ATM [RFC3035] interfaces can be realized given [RFC3034] and ATM [RFC3035] interfaces can be realized given
the interface stacking as defined in the MPLS-LSR [LSRMIB] the interface stacking as defined in the MPLS-LSR-STD [LSRMIB]
and MPLS-TE [TEMIB] MIBs. This document also contains a and MPLS-TE-STD [TEMIB] MIBs. This document also contains a
MIB module that extends the MPLS-LSR MIB's MIB module that sparsely augments the MPLS-LSR-STD MIB's
mplsInterfaceConfTable in such a way as to identify which mplsInterfaceConfTable in such a way as to identify which
MPLS-type interfaces have LC-ATM or LC-FR capabilities. MPLS-type interfaces have LC-ATM or LC-FR capabilities.
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
mpls@uu.net. mpls@uu.net.
This memo does not, in its draft form, specify a standard for the This memo does not, in its draft form, specify a standard for the
Internet community. Internet community.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
skipping to change at page 2, line 48 skipping to change at page 2, line 51
LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM) LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM)
interface as an ATM interface controlled by the label interface as an ATM interface controlled by the label
switching control component. When a packet traversing such switching control component. When a packet traversing such
an interface is received, it is treated as a labeled packet. an interface is received, it is treated as a labeled packet.
The packet's top label is inferred either from the contents The packet's top label is inferred either from the contents
of the VCI field or the combined contents of the VPI and VCI of the VCI field or the combined contents of the VPI and VCI
fields. Any two LDP peers which are connected via an LC-ATM fields. Any two LDP peers which are connected via an LC-ATM
interface will use LDP negotiations to determine which of interface will use LDP negotiations to determine which of
these cases is applicable to that interface. these cases is applicable to that interface.
Static configuration of labels is also possible.
When LDP is used to distribute labels for use on label-controlled
interfaces, label configuration information may be available in the
MPLS-LDP-ATM-STD-MIB [LDPMIB] when LC-ATM interfaces are used, or
the MPLS-LDP-FRAME-RELAY-STD-MIB [LDPMIB] when LC-FR interfaces
are used. Specifically,
4. The SNMP Management Framework 4. The SNMP 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
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
skipping to change at page 3, line 17 skipping to change at page 3, line 26
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
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
5. Interface Stacking of LC-ATM 5. Interface Stacking of LC-ATM and LC-FR Interfaces
Since LC-ATM interfaces can carry labeled MPLS traffic, Since LC-ATM interfaces [RFC2863] can carry labeled MPLS
they too are considered MPLS subinterfaces with ifType = traffic, they too are considered MPLS subinterfaces with
mpls(166). They differ slightly in their capability ifType = mpls(166). They differ slightly in their capability
from a packet-oriented MPLS interface in that they may from a packet-oriented MPLS interface in that they may
carry ATM or Frame-Relay encapsulated traffic. It is carry ATM or Frame-Relay encapsulated traffic. It is
thus beneficial to identify them as such. To identify thus beneficial to identify them as such. To identify
them as such, two tables are defined which extend the them as such, two tables are defined which extend the
MPLS-LSR MIB's mplsInterfaceConfTable (see section 7 for MPLS-LSR-STD MIB's mplsInterfaceTable (see section 6 for
LC-ATM or 8 for LC-FR). LC-ATM or 7 for LC-FR).
6. MPLS Label Controlled ATM MIB Definitions 6. MPLS Label Controlled ATM MIB Definitions
MPLS-LC-ATM-MIB-DRAFT-01 DEFINITIONS ::= BEGIN MPLS-LC-ATM-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, StorageType, TruthValue RowStatus, StorageType, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
AtmVpIdentifier AtmVpIdentifier
FROM ATM-TC-MIB FROM ATM-TC-MIB
mplsStdMIB, MplsAtmVcIdentifier mplsStdMIB, MplsAtmVcIdentifier
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB
; ;
mplsLcAtmMIB MODULE-IDENTITY mplsLcAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200401301200Z" -- 30 January 2004 12:00:00 GMT LAST-UPDATED "200405011200Z" -- 01 May 2004 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-244-3051 Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Subrahmanya Hegde Subrahmanya Hegde
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
225 East Tazman Drive 225 East Tazman Drive
Tel: +1-408-525-6562 Tel: +1-408-525-6562
Email: subrah@cisco.com Email: subrah@cisco.com
skipping to change at page 4, line 24 skipping to change at page 4, line 30
Email: subrah@cisco.com Email: subrah@cisco.com
General comments should be sent to mpls@uu.net General comments should be sent to mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
MPLS Label Controlled ATM interfaces as defined in MPLS Label Controlled ATM interfaces as defined in
RFC3035." RFC3035."
-- Revision history. -- Revision history.
REVISION REVISION
"200401301200Z" -- 30 January 2004 12:00:00 GMT "200405011200Z" -- 01 May 2004 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC XXXX."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA, maybe 6 ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB. -- Top level components of this MIB.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcAtmNotifications OBJECT IDENTIFIER ::= { mplsLcAtmMIB 0 } mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 }
mplsLcAtmObjects OBJECT IDENTIFIER ::= { mplsLcAtmMIB 1 } mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 }
mplsLcAtmConformance OBJECT IDENTIFIER ::= { mplsLcAtmMIB 2 } mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 }
-- MPLS LC-ATM Interface Configuration Table. -- MPLS LC-ATM Interface Configuration Table.
mplsLcAtmIfConfTable OBJECT-TYPE mplsLcAtmStdInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcAtmIfConfEntry SYNTAX SEQUENCE OF MplsLcAtmStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies per-interface MPLS LC-ATM "This table specifies per-interface MPLS LC-ATM
capability and associated information. In particular, capability and associated information. In particular,
this table extends the MPLS-LSR MIB's this table sparsely augments the MPLS-LSR-STD MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcAtmObjects 1 } ::= { mplsLcAtmStdObjects 1 }
mplsLcAtmIfConfEntry OBJECT-TYPE mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsLcAtmIfConfEntry SYNTAX MplsLcAtmStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by an LSR for "An entry in this table is created by an LSR for
every interface capable of supporting MPLS LC-ATM. every interface capable of supporting MPLS LC-ATM.
Each entry in this table will exist only if a Each entry in this table will exist only if a
corresponding entry in ifTable and mplsInterfaceConfTable corresponding entry in ifTable and mplsInterfaceConfTable
exist. If the associated entries in ifTable and exist. If the associated entries in ifTable and
mplsInterfaceConfTable are deleted, the corresponding mplsInterfaceConfTable are deleted, the corresponding
entry in this table must also be deleted shortly entry in this table must also be deleted shortly
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcAtmIfConfTable 1 } ::= { mplsLcAtmStdInterfaceConfTable 1 }
MplsLcAtmIfConfEntry ::= SEQUENCE { MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE {
mplsLcAtmCtrlVpi AtmVpIdentifier, mplsLcAtmStdCtrlVpi AtmVpIdentifier,
mplsLcAtmCtrlVci MplsAtmVcIdentifier, mplsLcAtmStdCtrlVci MplsAtmVcIdentifier,
mplsLcAtmUnlabTrafVpi AtmVpIdentifier, mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier,
mplsLcAtmUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier,
mplsLcAtmVcMerge TruthValue, mplsLcAtmStdVcMerge TruthValue,
mplsLcAtmIfConfRowStatus RowStatus, mplsLcAtmStdInterfaceConfRowStatus RowStatus,
mplsLcAtmIfConfStoreType StorageType mplsLcAtmStdInterfaceConfStoreType StorageType
} }
mplsLcAtmCtrlVpi OBJECT-TYPE mplsLcAtmStdCtrlVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VPI value over which this "This is the VPI value over which this
LSR is willing to accept control traffic on LSR is willing to accept control traffic on
this interface." this interface."
::= { mplsLcAtmIfConfEntry 1 } ::= { mplsLcAtmStdInterfaceConfEntry 1 }
mplsLcAtmCtrlVci OBJECT-TYPE mplsLcAtmStdCtrlVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VCI value over which this "This is the VCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
::= { mplsLcAtmIfConfEntry 2 } ::= { mplsLcAtmStdInterfaceConfEntry 2 }
mplsLcAtmUnlabTrafVpi OBJECT-TYPE mplsLcAtmStdUnlabTrafVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the max VPI value over which this "This is the max VPI value over which this
LSR is willing to accept unlabeled traffic LSR is willing to accept unlabeled traffic
on this interface." on this interface."
::= { mplsLcAtmIfConfEntry 3 } ::= { mplsLcAtmStdInterfaceConfEntry 3 }
mplsLcAtmUnlabTrafVci OBJECT-TYPE mplsLcAtmStdUnlabTrafVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VCI value over which this "This is the VCI value over which this
LSR is willing to accept unlabled traffic LSR is willing to accept unlabled traffic
on this interface." on this interface."
::= { mplsLcAtmIfConfEntry 4 } ::= { mplsLcAtmStdInterfaceConfEntry 4 }
mplsLcAtmVcMerge OBJECT-TYPE mplsLcAtmStdVcMerge OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If set to true(0), indicates that this interface "If set to true(1), indicates that this interface
is capabile of ATM VC merge, otherwise it MUST is capabile of ATM VC merge, otherwise it MUST
be set to false(1)." be set to false(2)."
DEFVAL { false } DEFVAL { false }
::= { mplsLcAtmIfConfEntry 5 } ::= { mplsLcAtmStdInterfaceConfEntry 5 }
mplsLcAtmIfConfRowStatus OBJECT-TYPE mplsLcAtmStdInterfaceConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is object is used to create and "This is object is used to create and
delete entries in this table. When configuring delete entries in this table. When configuring
entries in this table, the corresponding entries in this table, the corresponding
corresponding ifEntry and mplsInterfaceConfEntry corresponding ifEntry and mplsInterfaceConfEntry
MUST exist before hand. If an entry is attempted MUST exist before hand. If an entry is attempted
to be created by a manager for a corresponding to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-ATM, mplsInterfaceConfEntry that does not support LC-ATM,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
If this table is implemented read-only, then the If this table is implemented read-only, then the
agent must set this object to active(1) when this agent must set this object to active(1) when this
row is made active. If this table is implemented row is made active. If this table is implemented
writable, then an agent MUST not allow modification writable, then an agent MUST not allow modification
to its objects once this value is set to active(1)." to its objects once this value is set to active(1)."
::= { mplsLcAtmIfConfEntry 6 } ::= { mplsLcAtmStdInterfaceConfEntry 6 }
mplsLcAtmStdInterfaceConfStoreType OBJECT-TYPE
mplsLcAtmIfConfStoreType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SNMP storage type for this entry. All objects "This SNMP storage type for this entry. All objects
are writable for permanent objects." are writable for permanent objects."
::= { mplsLcAtmIfConfEntry 7 } ::= { mplsLcAtmStdInterfaceConfEntry 7 }
-- End of mplsLcAtmStdInterfaceConfTable
-- Module compliance. -- Module compliance.
mplsLcAtmCompliances mplsLcAtmStdCompliances
OBJECT IDENTIFIER ::= { mplsLcAtmConformance 1 } OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 }
mplsLcAtmGroups mplsLcAtmStdGroups
OBJECT IDENTIFIER ::= { mplsLcAtmConformance 2 } OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 }
mplsLcAtmModuleCompliance MODULE-COMPLIANCE -- Compliance requirement for full compliance
mplsLcAtmStdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support "Compliance statement for agents that provide
MPLS LC-ATM Interfaces." full support for MPLS-LC-ATM-STD-MIB. Such
devices can be monitored and also be configured
using this MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented
-- by all LSRs. However, they may all be supported
-- as read-only objects in the case where manual
-- configuration is unsupported.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcAtmIfGroup mplsLcAtmStdIfGroup
} }
-- mplsLcAtmIfConfTable ::= { mplsLcAtmStdCompliances 1 }
OBJECT mplsLcAtmCtrlVpi -- Compliance requirement for read-only implementations.
mplsLcAtmStdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance requirement for implementations that only
provide read-only support for MPLS-LC-ATM-STD-MIB.
Such devices can be monitored but cannot be configured
using this MIB module.
"
MODULE -- this module
MANDATORY-GROUPS {
mplsLcAtmStdIfGroup
}
-- mplsLcAtmStdInterfaceConfTable
OBJECT mplsLcAtmStdCtrlVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmCtrlVci OBJECT mplsLcAtmStdCtrlVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmUnlabTrafVpi OBJECT mplsLcAtmStdUnlabTrafVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmUnlabTrafVci OBJECT mplsLcAtmStdUnlabTrafVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmVcMerge OBJECT mplsLcAtmStdVcMerge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmIfConfRowStatus OBJECT mplsLcAtmStdInterfaceConfRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmIfConfStoreType OBJECT mplsLcAtmStdInterfaceConfStoreType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcAtmCompliances 1 } ::= { mplsLcAtmStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcAtmIfGroup OBJECT-GROUP mplsLcAtmStdIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcAtmCtrlVpi, mplsLcAtmStdCtrlVpi,
mplsLcAtmCtrlVci, mplsLcAtmStdCtrlVci,
mplsLcAtmUnlabTrafVpi, mplsLcAtmStdUnlabTrafVpi,
mplsLcAtmUnlabTrafVci, mplsLcAtmStdUnlabTrafVci,
mplsLcAtmVcMerge, mplsLcAtmStdVcMerge,
mplsLcAtmIfConfRowStatus, mplsLcAtmStdInterfaceConfRowStatus,
mplsLcAtmIfConfStoreType mplsLcAtmStdInterfaceConfStoreType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS LC-ATM "Collection of objects needed for MPLS LC-ATM
interface configuration." interface configuration."
::= { mplsLcAtmGroups 1 } ::= { mplsLcAtmStdGroups 1 }
END END
7. MPLS Label Controlled Frame-Relay MIB Definitions 7. MPLS Label Controlled Frame-Relay MIB Definitions
MPLS-LC-FR-MIB-DRAFT-01 DEFINITIONS ::= BEGIN MPLS-LC-FR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, StorageType RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB FROM FRAME-RELAY-DTE-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
; ;
mplsLcFrStdMIB MODULE-IDENTITY
mplsLcFrMIB MODULE-IDENTITY LAST-UPDATED "200405011200Z" -- 01 May 2004 12:00:00 GMT
LAST-UPDATED "200401301200Z" -- 30 January 2004 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Subrahmanya Hegde Subrahmanya Hegde
Postal: Cisco Systems, Inc.
225 East Tazman Drive
Tel: +1-408-525-6562
Email: subrah@cisco.com Email: subrah@cisco.com
General comments should be sent to mpls@uu.net General comments should be sent to mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
MPLS Label Controlled Frame-Relay interfaces as defined MPLS Label Controlled Frame-Relay interfaces as defined
in RFC3034." in RFC3034."
-- Revision history. -- Revision history.
REVISION REVISION
"200401301200Z" -- 30 January 2004 12:00:00 GMT "200405011200Z" -- 01 May 2004 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial draft revision." "Initial draft revision."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA, maybe 7 ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB. -- Top level components of this MIB.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcFrNotifications OBJECT IDENTIFIER ::= { mplsLcFrMIB 0 } mplsLcFrStdNotifications OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 0 }
mplsLcFrObjects OBJECT IDENTIFIER ::= { mplsLcFrMIB 1 } mplsLcFrStdObjects OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 1 }
mplsLcFrConformance OBJECT IDENTIFIER ::= { mplsLcFrMIB 2 } mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 }
-- MPLS LC-FR Interface Configuration Table. -- MPLS LC-FR Interface Configuration Table.
mplsLcFrIfConfTable OBJECT-TYPE mplsLcFrStdInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcFrIfConfEntry SYNTAX SEQUENCE OF MplsLcFrStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies per-interface MPLS LC-FR "This table specifies per-interface MPLS LC-FR
capability and associated information. In particular, capability and associated information. In particular,
this table extends the MPLS-LSR MIB's this table sparsely augments the MPLS-LSR-STD MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcFrObjects 1 } ::= { mplsLcFrStdObjects 1 }
mplsLcFrIfConfEntry OBJECT-TYPE mplsLcFrStdInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsLcFrIfConfEntry SYNTAX MplsLcFrStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by an LSR for "An entry in this table is created by an LSR for
every interface capable of supporting MPLS LC-FR. every interface capable of supporting MPLS LC-FR.
Each entry in this table will exist only if a Each entry in this table will exist only if a
corresponding entry in ifTable and mplsInterfaceConfTable corresponding entry in ifTable and mplsInterfaceConfTable
exist. If the associated entries in ifTable and exist. If the associated entries in ifTable and
mplsInterfaceConfTable are deleted, the corresponding mplsInterfaceConfTable are deleted, the corresponding
entry in this table must also be deleted shortly entry in this table must also be deleted shortly
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcFrIfConfTable 1 } ::= { mplsLcFrStdInterfaceConfTable 1 }
MplsLcFrIfConfEntry ::= SEQUENCE { MplsLcFrStdInterfaceConfEntry ::= SEQUENCE {
mplsLcFrTrafficMinDlci DLCI, mplsLcFrStdTrafficMinDlci DLCI,
mplsLcFrTrafficMaxDlci DLCI, mplsLcFrStdTrafficMaxDlci DLCI,
mplsLcFrCtrlMinDlci DLCI, mplsLcFrStdCtrlMinDlci DLCI,
mplsLcFrCtrlMaxDlci DLCI, mplsLcFrStdCtrlMaxDlci DLCI,
mplsLcFrIfConfRowStatus RowStatus, mplsLcFrStdInterfaceConfRowStatus RowStatus,
mplsLcFrIfConfStoreType StorageType mplsLcFrStdInterfaceConfStoreType StorageType
} }
mplsLcFrTrafficMinDlci OBJECT-TYPE mplsLcFrStdTrafficMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the minimum DLCI value over which this "This is the minimum DLCI value over which this
LSR is willing to accept traffic on this LSR is willing to accept traffic on this
interface." interface."
::= { mplsLcFrIfConfEntry 1 } ::= { mplsLcFrStdInterfaceConfEntry 1 }
mplsLcFrTrafficMaxDlci OBJECT-TYPE mplsLcFrStdTrafficMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the max DLCI value over which this "This is the max DLCI value over which this
LSR is willing to accept traffic on this LSR is willing to accept traffic on this
interface." interface."
::= { mplsLcFrIfConfEntry 2 } ::= { mplsLcFrStdInterfaceConfEntry 2 }
mplsLcFrCtrlMinDlci OBJECT-TYPE mplsLcFrStdCtrlMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the min DLCI value over which this "This is the min DLCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
::= { mplsLcFrIfConfEntry 3 } ::= { mplsLcFrStdInterfaceConfEntry 3 }
mplsLcFrCtrlMaxDlci OBJECT-TYPE mplsLcFrStdCtrlMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the max DLCI value over which this "This is the max DLCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
::= { mplsLcFrIfConfEntry 4 } ::= { mplsLcFrStdInterfaceConfEntry 4 }
mplsLcFrIfConfRowStatus OBJECT-TYPE mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is object is used to create and "This is object is used to create and
delete entries in this table. When configuring delete entries in this table. When configuring
entries in this table, the corresponding entries in this table, the corresponding
corresponding ifEntry and mplsInterfaceConfEntry corresponding ifEntry and mplsInterfaceConfEntry
MUST exist before hand. If an entry is attempted MUST exist before hand. If an entry is attempted
to be created by a manager for a corresponding to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-FR, mplsInterfaceConfEntry that does not support LC-FR,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
If this table is implemented read-only, then the If this table is implemented read-only, then the
agent must set this object to active(1) when this agent must set this object to active(1) when this
row is made active. If this table is implemented row is made active. If this table is implemented
writable, then an agent MUST not allow modification writable, then an agent MUST not allow modification
to its objects once this value is set to active(1)." to its objects once this value is set to active(1)."
::= { mplsLcFrIfConfEntry 5 } ::= { mplsLcFrStdInterfaceConfEntry 5 }
mplsLcFrIfConfStoreType OBJECT-TYPE mplsLcFrStdInterfaceConfStoreType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This SNMP storage type for this entry. All objects "This SNMP storage type for this entry. All objects
are writable for permanent entries." are writable for permanent entries."
::= { mplsLcFrIfConfEntry 6 } ::= { mplsLcFrStdInterfaceConfEntry 6 }
-- End of mplsLcFrStdInterfaceConfTable
-- Module compliance. -- Module compliance.
mplsLcFrCompliances mplsLcFrStdCompliances
OBJECT IDENTIFIER ::= { mplsLcFrConformance 1 } OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 1 }
mplsLcFrGroups mplsLcFrStdGroups
OBJECT IDENTIFIER ::= { mplsLcFrConformance 2 } OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 2 }
mplsLcFrModuleCompliance MODULE-COMPLIANCE -- Compliance requirement for full compliance
mplsLcFrStdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support "Compliance statement for agents that provide
MPLS LC-FR Interfaces." full support for MPLS-LC-FR-STD-MIB. Such
devices can be monitored and also be configured
using this MIB module."
MODULE -- this module
MANDATORY-GROUPS {
mplsLcFrStdIfGroup
}
::= { mplsLcFrStdCompliances 1 }
-- Compliance requirement for read-only implementations.
mplsLcFrStdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance requirement for implementations that only
provide read-only support for MPLS-LC-FR-STD-MIB.
Such devices can be monitored but cannot be configured
using this MIB module.
"
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented -- The mandatory groups have to be implemented
-- by all LSRs. However, they may all be supported -- by all LSRs. However, they may all be supported
-- as read-only objects in the case where manual -- as read-only objects in the case where manual
-- configuration is unsupported. -- configuration is unsupported.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcFrIfGroup mplsLcFrStdIfGroup
} }
-- mplsLcFrIfConfTable -- mplsLcFrStdInterfaceConfTable
OBJECT mplsLcFrTrafficMinDlci OBJECT mplsLcFrStdTrafficMinDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrTrafficMaxDlci OBJECT mplsLcFrStdTrafficMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrCtrlMinDlci OBJECT mplsLcFrStdCtrlMinDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrCtrlMaxDlci OBJECT mplsLcFrStdCtrlMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrIfConfRowStatus OBJECT mplsLcFrStdInterfaceConfRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrIfConfStoreType OBJECT mplsLcFrStdInterfaceConfStoreType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcFrCompliances 1 } ::= { mplsLcFrStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcFrIfGroup OBJECT-GROUP mplsLcFrStdIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcFrTrafficMinDlci, mplsLcFrStdTrafficMinDlci,
mplsLcFrTrafficMaxDlci, mplsLcFrStdTrafficMaxDlci,
mplsLcFrCtrlMinDlci, mplsLcFrStdCtrlMinDlci,
mplsLcFrCtrlMaxDlci, mplsLcFrStdCtrlMaxDlci,
mplsLcFrIfConfRowStatus, mplsLcFrStdInterfaceConfRowStatus,
mplsLcFrIfConfStoreType mplsLcFrStdInterfaceConfStoreType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS LC-FR "Collection of objects needed for MPLS LC-FR
interface configuration." interface configuration."
::= { mplsLcFrGroups 1 } ::= { mplsLcFrStdGroups 1 }
END END
8. Security Considerations 8. Security Considerations
It is clear that these MIB modules are potentially useful for It is clear that these MIB modules are potentially useful for
monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These
MIB can also be used for configuration of certain objects, and MIB can also be used for configuration of certain objects, and
anything that can be configured can be incorrectly configured, anything that can be configured can be incorrectly configured,
with potentially disastrous results. with potentially disastrous results.
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 MplsLcAtmIfConfTable and mplsLcFrIfConfTable collectively o the MplsLcAtmStdInterfaceConfTable and
contain objects which may be used to provision MPLS LC or FR-enabled mplsLcFrStdInterfaceConfTable collectively
interfaces. Unauthorized access to objects in these tables, contain objects which may be used to provision MPLS LC or
could result in disruption of traffic on the network. This is FR-enabled interfaces. Unauthorized access to objects in these
especially true if traffic has been established over these tables, could result in disruption of traffic on the network.
interfaces. The use of stronger mechanisms such as SNMPv3 This is especially true if traffic has been established over
these interfaces. 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 module. Administrators should consider implements this MIB module. Administrators should consider
whether read access to these objects should be allowed, 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 MplsLcAtmIfConfTable and mplsLcFrIfConfTable collectively o the MplsLcAtmStdInterfaceConfTable and
mplsLcFrStdInterfaceConfTable collectively
collectively show the LC-ATM and/or LC-FR interfaces, collectively show the LC-ATM and/or LC-FR interfaces,
their associated configurations and their linkages to other their associated configurations and their linkages to other
MPLS-related configuration and/or performanc statistics. MPLS-related configuration and/or performanc statistics.
Administrators not wishing to reveal this information should Administrators not wishing to reveal this information should
consider these objects sensitive/vulnerable and take consider these objects sensitive/vulnerable and take
precautions so they are not revealed. precautions so they are not revealed.
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
skipping to change at page 14, line 45 skipping to change at page 15, line 41
to the objects only to those principals "users" that have legitimate to 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.
9. References 9. References
9.1 Normative References 9.1 Normative References
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2515] Tesink, K., et al., "Definitions of Managed Objects
for ATM Management", RFC 2515, February 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC "Multiprotocol Label Switching Architecture", RFC
3031, January 2001. 3031, January 2001.
[RFC3291] Daniele, M., Haberman, B., Routhier., S.,
Schoenwaelder., J., "Textual Conventions
for Internet Network Addresses", RFC3291,
May 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002.
[TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS [TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS
Traffic Engineering Management Information Base ", Traffic Engineering Management Information Base ",
Internet Draft <draft-ietf-mpls-te-mib-09.txt>, Internet Draft <draft-ietf-mpls-te-mib-14.txt>,
November 2002. November 2003.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. [LSRMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau, "MPLS Multiprotocol Label Switching Nadeau, "MPLS Multiprotocol Label Switching
(MPLS) Label Switch Router Management (MPLS) Label Switch Router Management
Information Base ", Internet Draft <draft- Information Base ", Internet Draft <draft-
ietf-mpls-lsr-mib-14.txt>, November 2003. ietf-mpls-lsr-mib-14.txt>, November 2003.
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C.,
Viswanathan, A., Sjostrand, H. and K. Kompella, Viswanathan, A., Sjostrand, H. and K. Kompella,
"Definition of Textual Conventions and OBJECT- "Definition of Textual Conventions and OBJECT-
IDENTITIES for Multi-Protocol Label Switching (MPLS) IDENTITIES for Multi-Protocol Label Switching (MPLS)
Management", Internet Draft <draft-ietf-mpls-tc-mib- Management", Internet Draft <draft-ietf-mpls-tc-mib-
06.txt>, April 2003. 10.txt>, October 2003.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers),
for MIB see:
ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum
bers.mib
9.2 Informative References 9.2 Informative References
[RFC2026] S. Bradner, "The Internet Standards Process -- [RFC2026] S. Bradner, "The Internet Standards Process --
Revision 3", RFC 2026, October 1996. Revision 3", RFC 2026, October 1996.
[RFC3413] Levi, D., Meyer, P., Stewart, B.,
"SNMP Applications", RFC 3413, December 2002.
[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 "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[LDPMIB] J. Cucchiara, et al., "Definitions of
Managed Objects for the Multiprotocol Label
Switching, Label Distribution Protocol
(LDP)", <draft-ietf-mpls-ldp-mib-14.txt>,
November 2003.
10. Authors' Addresses 10. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 300 Beaver Brook Road
Boxboro, MA 01719 Boxboro, MA 01719
Phone: +1-978-936-1470 Phone: +1-978-936-1470
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Subrahmanya Hegde Subrahmanya Hegde
Cisco Systems, Inc. Cisco Systems, Inc.
225 East Tazman Drive 225 East Tazman Drive
San Jose, CA
Phone: +1-408-525-6562 Phone: +1-408-525-6562
Email: subrah@cisco.com Email: subrah@cisco.com
11. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared, explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed Internet Society or other Internet organizations, except as needed
skipping to change at page 17, line 33 skipping to change at page 18, line 13
such proprietary rights by implementors or users of this such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF Secretariat.
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 practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
13. IANA Considerations 13. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB As described in and as requested in the MPLS-TC-STD-MIB
[MPLSTCMIB], MPLS related standards track MIB modules should be [TCMIB], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 2 MPLS MIB Modules rooted under the mplsStdMIB subtree. There are 2 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 requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
14.1. IANA Considerations for MPLS-LC-ATM-MIB 14.1. IANA Considerations for MPLS-LC-ATM-MIB
The IANA is requested to assign { mplsStdMIB 6 } to the The IANA is requested to assign { mplsStdMIB 9 } to the
MPLS-LC-ATM-MIB module specified in this document. MPLS-LC-ATM-MIB module specified in this document.
14.2. IANA Considerations for MPLS-LC-FR-MIB 14.2. IANA Considerations for MPLS-LC-FR-MIB
The IANA is requested to assign { mplsStdMIB 7 } to the The IANA is requested to assign { mplsStdMIB 10 } to the
MPLS-LC-FR-MIB module specified in this document. MPLS-LC-FR-MIB module specified in this document.
15. Acknowledgments
We wish to thank Joan Cucchiara for her comments on
this document.
 End of changes. 

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