draft-ietf-mpls-lc-if-mib-02.txt   draft-ietf-mpls-lc-if-mib-03.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: December 2004 Cisco Systems, Inc. Expires: February 2005 Cisco Systems, Inc.
May 2004 August 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-02.txt draft-ietf-mpls-lc-if-mib-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with Abstract
all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the In ternet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work
in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This memo defines two MIB modules and corresponding MIB Object
http://www.ietf.org/shadow.html. Definitions that describe how label switching controlled
Frame-Relay and ATM interfaces can be managed given the
interface stacking as defined in the MPLS-LSR-STD-MIB and
MPLS-TE-STD-MIB.
Table of Contents Table of Contents
1. Abstract .................................................. 2 1. Introduction .............................................. 3
2. Introduction .............................................. 2 2. Terminology ............................................... 3
3. Terminology ............................................... 2 3. The SNMP Management Framework ............................. 3
4. The SNMP Management Framework ............................. 2 4. Interface Stacking of LC-ATM and LC-FR .................... 5
5. Interface Stacking of LC-ATM and LC-FR and LC-FR Interfaces. 3 5. MPLS Label Controlled ATM MIB Definitions ................. 13
6. MPLS Label Controlled ATM MIB Definitions .................. 3 6. MPLS Label Controlled Frame Relay MIB Definitions ......... 13
7. MPLS Label Controlled Frame Relay MIB Definitions .......... 9 7. Security Considerations ................................... 51
8. Security Considerations ................................... 14 8. 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-STD-MIB ............... 52
14.1. IANA Considerations for MPLS-LC-ATM-MIB ............... 18 14.2. IANA Considerations for MPLS-LC-FR-STD-MIB ................ 52
14.2. IANA Considerations for MPLS-LC-FR-MIB ................ 18 15 Acknowledgments............................................ 52
15 Acknowledgments............................................ 18
1. Abstract
This memo defines how label switching controlled Frame-Relay
and ATM interfaces can be realized given the interface stacking
as defined in the MPLS-LSR-STD and MPLS-TE-STD MIBs.
2. Introduction 1. 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-STD [LSRMIB] the interface stacking as defined in the MPLS-LSR-STD [LSRMIB]
and MPLS-TE-STD [TEMIB] MIBs. This document also contains a and MPLS-TE-STD [TEMIB] MIBs. This document also contains a
MIB module that sparsely augments the MPLS-LSR-STD 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
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
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
RFC 2119, reference [RFC2119]. RFC 2119, reference [RFC2119].
3. Terminology 2. Terminology
This document uses terminology from the document describing the This document uses terminology from the document describing the
MPLS architecture [RFC3031], as well as RFC3035 and RFC3034. MPLS architecture [RFC3031], as well as RFC3035 and RFC3034.
Specifically, the following terms will be used in this document. Specifically, the following terms will be used in this document.
LC-FR RFC3034 defines a label switching controlled Frame Relay LC-FR RFC3034 defines a label switching controlled Frame Relay
(LC-FR) interface a Frame-Relay interface controlled by the (LC-FR) interface a Frame-Relay interface controlled by the
label switching control component. Packets traversing label switching control component. Packets traversing
such an interface carry labels in the DLCI field such an interface carry labels in the DLCI field
skipping to change at page 3, line 26 skipping to change at page 3, line 8
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 and LC-FR Interfaces 5. Interface Stacking of LC-ATM
Since LC-ATM interfaces [RFC2863] can carry labeled MPLS Since LC-ATM interfaces [RFC2863] can carry labeled MPLS
traffic, they too are considered MPLS subinterfaces with traffic, they too are considered MPLS subinterfaces with
ifType = 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-STD MIB's mplsInterfaceTable (see section 6 for MPLS-LSR-STD MIB's mplsInterfaceTable (see section 6 for
LC-ATM or 7 for LC-FR). LC-ATM or 7 for LC-FR).
skipping to change at page 3, line 49 skipping to change at page 3, line 31
MPLS-LC-ATM-STD-MIB 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 -- RFC2514
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
; ;
mplsLcAtmStdMIB MODULE-IDENTITY mplsLcAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200405011200Z" -- 01 May 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
skipping to change at page 4, line 26 skipping to change at page 4, line 9
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
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.
Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200405011200Z" -- 01 May 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 ::= { mplsStdMIB 999 } -- 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
mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 } mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 }
mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 } mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 }
mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 } mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 }
-- MPLS LC-ATM Interface Configuration Table. -- MPLS LC-ATM Interface Configuration Table.
mplsLcAtmStdInterfaceConfTable OBJECT-TYPE mplsLcAtmStdInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcAtmStdInterfaceConfEntry 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 sparsely augments the MPLS-LSR-STD MIB's this table sparsely augments the MPLS-LSR-STD-MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcAtmStdObjects 1 } ::= { mplsLcAtmStdObjects 1 }
mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsLcAtmStdInterfaceConfEntry 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.
skipping to change at page 5, line 29 skipping to change at page 5, line 17
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcAtmStdInterfaceConfTable 1 } ::= { mplsLcAtmStdInterfaceConfTable 1 }
MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE { MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE {
mplsLcAtmStdCtrlVpi AtmVpIdentifier, mplsLcAtmStdCtrlVpi AtmVpIdentifier,
mplsLcAtmStdCtrlVci MplsAtmVcIdentifier, mplsLcAtmStdCtrlVci MplsAtmVcIdentifier,
mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier, mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier,
mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier,
mplsLcAtmStdVcMerge TruthValue, mplsLcAtmStdVcMerge TruthValue,
mplsLcAtmStdInterfaceConfRowStatus RowStatus, mplsLcAtmVcDirectlyConnected TruthValue,
mplsLcAtmStdInterfaceConfStoreType StorageType mplsLcAtmLcAtmVPI AtmVpIdentifier,
mplsLcAtmStdIfConfRowStatus RowStatus,
mplsLcAtmStdIfConfStoreType StorageType
} }
mplsLcAtmStdCtrlVpi 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."
skipping to change at page 6, line 34 skipping to change at page 6, line 24
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If set to true(1), 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(2)." be set to false(2)."
DEFVAL { false } DEFVAL { false }
::= { mplsLcAtmStdInterfaceConfEntry 5 } ::= { mplsLcAtmStdInterfaceConfEntry 5 }
mplsLcAtmStdInterfaceConfRowStatus OBJECT-TYPE mplsLcAtmVcDirectlyConnected OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates whether an LC-ATM is directly
or indirectly (by means of a VP) connected. If set to
true(0), indicates that this interface is directly
connected LC-ATM, otherwise it MUST be set to
false(1)."
DEFVAL { true }
::= { mplsLcAtmStdInterfaceConfEntry 6 }
mplsLcAtmLcAtmVPI OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This is the VPI value used for indirectly
connected LC-ATM interfaces For indirectly
connected interfaces, the VPI field is not
available to MPLS, and the label MUST be
encoded entirely within the VCI field.
(see RFC 3035). If the interface is directly
connected, this value MUST be set to zero."
DEFVAL { 0 }
::= { mplsLcAtmStdInterfaceConfEntry 7 }
mplsLcAtmStdIfConfRowStatus 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 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)."
::= { mplsLcAtmStdInterfaceConfEntry 6 } ::= { mplsLcAtmStdInterfaceConfEntry 8 }
mplsLcAtmStdInterfaceConfStoreType OBJECT-TYPE
mplsLcAtmStdIfConfStoreType 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."
::= { mplsLcAtmStdInterfaceConfEntry 7 } ::= { mplsLcAtmStdInterfaceConfEntry 9 }
-- End of mplsLcAtmStdInterfaceConfTable -- End of mplsLcAtmStdInterfaceConfTable
-- Module compliance. -- Module compliance.
mplsLcAtmStdCompliances mplsLcAtmStdCompliances
OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 } OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 }
mplsLcAtmStdGroups mplsLcAtmStdGroups
OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 } OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 }
skipping to change at page 7, line 36 skipping to change at page 8, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide "Compliance statement for agents that provide
full support for MPLS-LC-ATM-STD-MIB. Such full support for MPLS-LC-ATM-STD-MIB. Such
devices can be monitored and also be configured devices can be monitored and also be configured
using this MIB module." using this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcAtmStdIfGroup mplsLcAtmStdIfGroup
} }
::= { mplsLcAtmStdCompliances 1 } ::= { mplsLcAtmStdCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLcAtmStdModuleReadOnlyCompliance MODULE-COMPLIANCE mplsLcAtmStdModuleROCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for MPLS-LC-ATM-STD-MIB. provide read-only support for MPLS-LC-ATM-STD-MIB.
Such devices can be monitored but cannot be configured Such devices can be monitored but cannot be configured
using this MIB module. using this MIB module.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
skipping to change at page 8, line 31 skipping to change at page 8, line 49
OBJECT mplsLcAtmStdUnlabTrafVci OBJECT mplsLcAtmStdUnlabTrafVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdVcMerge OBJECT mplsLcAtmStdVcMerge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdInterfaceConfRowStatus OBJECT mplsLcAtmStdIfConfRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsLcAtmVcDirectlyConnected
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdInterfaceConfStoreType OBJECT mplsLcAtmLcAtmVPI
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsLcAtmStdIfConfStoreType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcAtmStdCompliances 2 } ::= { mplsLcAtmStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcAtmStdIfGroup OBJECT-GROUP mplsLcAtmStdIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcAtmStdCtrlVpi, mplsLcAtmStdCtrlVpi,
mplsLcAtmStdCtrlVci, mplsLcAtmStdCtrlVci,
mplsLcAtmStdUnlabTrafVpi, mplsLcAtmStdUnlabTrafVpi,
mplsLcAtmStdUnlabTrafVci, mplsLcAtmStdUnlabTrafVci,
mplsLcAtmStdVcMerge, mplsLcAtmStdVcMerge,
mplsLcAtmStdInterfaceConfRowStatus, mplsLcAtmVcDirectlyConnected,
mplsLcAtmStdInterfaceConfStoreType mplsLcAtmLcAtmVPI,
mplsLcAtmStdIfConfRowStatus,
mplsLcAtmStdIfConfStoreType
} }
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."
::= { mplsLcAtmStdGroups 1 } ::= { mplsLcAtmStdGroups 1 }
END END
7. MPLS Label Controlled Frame-Relay MIB Definitions 7. MPLS Label Controlled Frame-Relay MIB Definitions
skipping to change at page 9, line 26 skipping to change at page 10, line 7
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 -- RFC2115
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
; ;
mplsLcFrStdMIB MODULE-IDENTITY mplsLcFrStdMIB MODULE-IDENTITY
LAST-UPDATED "200405011200Z" -- 01 May 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
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Subrahmanya Hegde Subrahmanya Hegde
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.
Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200405011200Z" -- 01 May 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 ::= { 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
skipping to change at page 10, line 20 skipping to change at page 11, line 5
mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 } mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 }
-- MPLS LC-FR Interface Configuration Table. -- MPLS LC-FR Interface Configuration Table.
mplsLcFrStdInterfaceConfTable OBJECT-TYPE mplsLcFrStdInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcFrStdInterfaceConfEntry 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 sparsely augments the MPLS-LSR-STD MIB's this table sparsely augments the MPLS-LSR-STD-MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcFrStdObjects 1 } ::= { mplsLcFrStdObjects 1 }
mplsLcFrStdInterfaceConfEntry OBJECT-TYPE mplsLcFrStdInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsLcFrStdInterfaceConfEntry 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.
skipping to change at page 14, line 35 skipping to change at page 15, line 20
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 MplsLcAtmStdInterfaceConfTable and o the MplsLcAtmStdInterfaceConfTable and
mplsLcFrStdInterfaceConfTable collectively mplsLcFrStdInterfaceConfTable collectively
contain objects which may be used to provision MPLS LC or contain objects which may be used to provision MPLS LC or FR-enabled
FR-enabled interfaces. Unauthorized access to objects in these interfaces. Unauthorized access to objects in these tables,
tables, could result in disruption of traffic on the network. could result in disruption of traffic on the network. This is
This is especially true if traffic has been established over especially true if traffic has been established over these
these interfaces. The use of stronger mechanisms such as SNMPv3 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
skipping to change at page 15, line 38 skipping to change at page 16, line 23
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access instance of this MIB module, is properly configured to give access
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
[RFC2115]
[RFC2514]
[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.
[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
skipping to change at page 16, line 14 skipping to change at page 16, line 52
[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.
[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-14.txt>, RFC3812, June 2004.
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 ", RFC3813, June 2004.
ietf-mpls-lsr-mib-14.txt>, November 2003.
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., [TCMIB] Nadeau, T., Cucchiara, J., Editors,
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", RFC3811, June 2004.
10.txt>, October 2003.
9.2 Informative References 9.2 Informative References
[RFC2026] S. Bradner, "The Internet Standards Process --
Revision 3", RFC 2026, October 1996.
[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 [LDPMIB] J. Cucchiara, et al., "Definitions of
Managed Objects for the Multiprotocol Label Managed Objects for the Multiprotocol Label
Switching, Label Distribution Protocol Switching, Label Distribution Protocol
(LDP)", <draft-ietf-mpls-ldp-mib-14.txt>, (LDP)", <draft-ietf-mpls-ldp-mib-14.txt>,
November 2003. November 2003.
skipping to change at page 18, line 21 skipping to change at page 19, line 5
13. IANA Considerations 13. IANA Considerations
As described in and as requested in the MPLS-TC-STD-MIB As described in and as requested in the MPLS-TC-STD-MIB
[TCMIB], 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-STD-MIB
The IANA is requested to assign { mplsStdMIB 9 } to the The IANA is requested to assign { mplsStdMIB 9 } to the
MPLS-LC-ATM-MIB module specified in this document. MPLS-LC-ATM-STD-MIB module specified in this document.
14.2. IANA Considerations for MPLS-LC-FR-MIB 14.2. IANA Considerations for MPLS-LC-FR-STD-MIB
The IANA is requested to assign { mplsStdMIB 10 } to the The IANA is requested to assign { mplsStdMIB 10 } to the
MPLS-LC-FR-MIB module specified in this document. MPLS-LC-FR-STD-MIB module specified in this document.
15. Acknowledgments 15. Acknowledgments
We wish to thank Joan Cucchiara for her comments on We wish to thank Joan Cucchiara for her comments on
this document. this document.
 End of changes. 

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