draft-ietf-mpls-lc-if-mib-04.txt   draft-ietf-mpls-lc-if-mib-05.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: April 2005 Cisco Systems, Inc. Expires: October 2005 Cisco Systems, Inc.
October 2004 April 2005
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-04.txt draft-ietf-mpls-lc-if-mib-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than a "work in progress." material or to cite them other than as "work 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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.
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668.
Abstract Abstract
This memo defines two MIB modules and corresponding MIB Object This memo defines two MIB modules and corresponding MIB Object
Definitions that describe how label switching controlled Definitions that describe how label switching controlled
Frame-Relay and ATM interfaces can be managed given the Frame-Relay and ATM interfaces can be managed given the
interface stacking as defined in the MPLS-LSR-STD-MIB and interface stacking as defined in the MPLS-LSR-STD-MIB and
MPLS-TE-STD-MIB. MPLS-TE-STD-MIB.
Table of Contents Table of Contents
1. Introduction .............................................. 3 1. Introduction .............................................. 3
2. Terminology ............................................... 3 2. Terminology ............................................... 3
3. The SNMP Management Framework ............................. 3 3. The SNMP Management Framework ............................. 3
4. Interface Stacking of LC-ATM and LC-FR .................... 5 4. Interface Stacking of LC-ATM and LC-FR .................... 5
5. MPLS Label Controlled ATM MIB Definitions ................. 13 5. MPLS Label Controlled ATM MIB Definitions ................. 13
6. MPLS Label Controlled Frame Relay MIB Definitions ......... 13 6. MPLS Label Controlled Frame Relay MIB Definitions ......... 13
7. Security Considerations ................................... 51 7. Authors' Addresses ........................................ 54
8. References ................................................ 52 8. Full Copyright Statement................................... 55
10. Authors' Addresses ........................................ 54 9 Acknowledgments............................................ 52
11. Copyright Notice........................................... 55 10 Security Considerations ................................... 51
12. Full Copyright Statement................................... 55 11 IANA Considerations........................................ 55
13. Intellectual Property...................................... 55 12 References ................................................ 52
14. IANA Considerations........................................ 55 13 Intellectual Property...................................... 55
15 Acknowledgments............................................ 52
1. 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 [RFC3813]
and MPLS-TE-STD [TEMIB] MIBs. This document also contains a and MPLS-TE-STD [RFC3812] 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.
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].
skipping to change at page 2, line 50 skipping to change at page 3, line 4
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. Static configuration of labels is also possible.
When LDP is used to distribute labels for use on label-controlled When LDP is used to distribute labels for use on label-controlled
interfaces, label configuration information may be available in the interfaces, label configuration information may be available in the
MPLS-LDP-ATM-STD-MIB [LDPMIB] when LC-ATM interfaces are used, or MPLS-LDP-ATM-STD-MIB [RFC3815] when LC-ATM interfaces are used, or
the MPLS-LDP-FRAME-RELAY-STD-MIB [LDPMIB] when LC-FR interfaces the MPLS-LDP-FRAME-RELAY-STD-MIB [RFC3815] when LC-FR interfaces
are used. Specifically, are used. Specifically,
4. The SNMP Management Framework 3. 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,
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 4. 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).
6. MPLS Label Controlled ATM MIB Definitions 5. MPLS Label Controlled ATM MIB Definitions
The following MIB module imports from [RFC2514],
[RFC3811], [RFC3813].
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 -- RFC2514 FROM ATM-TC-MIB
mplsStdMIB, MplsAtmVcIdentifier mplsStdMIB, MplsAtmVcIdentifier
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB -- RFC3813 FROM MPLS-LSR-STD-MIB
; ;
mplsLcAtmStdMIB MODULE-IDENTITY mplsLcAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200410121200Z" -- 12 October 2004 12:00:00 GMT LAST-UPDATED "200503011200Z" -- 01 March 2005 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
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 module 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 Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200410121200Z" -- 12 October 2004 12:00:00 GMT "200504281200Z" -- 28 April 2005 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 XXX } -- To Be Assigned by IANA
-- Top level components of this MIB module.
-- 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.
skipping to change at page 7, line 10 skipping to change at page 7, line 15
mplsLcAtmLcAtmVPI OBJECT-TYPE mplsLcAtmLcAtmVPI 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 used for indirectly "This is the VPI value used for indirectly
connected LC-ATM interfaces. For these connected LC-ATM interfaces. For these
interfaces, the VPI field is not interfaces, the VPI field is not
available to MPLS, and the label MUST be available to MPLS, and the label MUST be
encoded entirely within the VCI field. encoded entirely within the VCI field.
(see RFC 3035). If the interface is directly (see [RFC3035]). If the interface is directly
connected, this value MUST be set to zero." connected, this value MUST be set to zero."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLcAtmStdInterfaceConfEntry 7 } ::= { mplsLcAtmStdInterfaceConfEntry 7 }
mplsLcAtmStdIfConfRowStatus OBJECT-TYPE 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
skipping to change at page 7, line 32 skipping to change at page 7, line 37
entries in this table, the corresponding entries in this table, the 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)
except mplsLcAtmStdIfConfRowStatus and
mplsLcAtmStdIfConfStoreType."
::= { mplsLcAtmStdInterfaceConfEntry 8 } ::= { mplsLcAtmStdInterfaceConfEntry 8 }
mplsLcAtmStdIfConfStoreType 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 "The storage type for this conceptual row.
are writable for permanent objects." Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLcAtmStdInterfaceConfEntry 9 } ::= { mplsLcAtmStdInterfaceConfEntry 9 }
-- End of mplsLcAtmStdInterfaceConfTable -- End of mplsLcAtmStdInterfaceConfTable
-- Module compliance. -- Module compliance.
mplsLcAtmStdCompliances mplsLcAtmStdCompliances
OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 } OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 }
mplsLcAtmStdGroups mplsLcAtmStdGroups
skipping to change at page 8, line 19 skipping to change at page 8, line 29
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
} }
OBJECT mplsLcAtmStdIfConfRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
::= { mplsLcAtmStdCompliances 1 } ::= { mplsLcAtmStdCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLcAtmStdModuleROCompliance 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
skipping to change at page 9, line 14 skipping to change at page 9, line 32
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 mplsLcAtmStdIfConfRowStatus OBJECT mplsLcAtmStdIfConfRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), MIN-ACCESS read-only
createAndGo(4), destroy(6) DESCRIPTION "Write access is not required."
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
OBJECT mplsLcAtmVcDirectlyConnected OBJECT mplsLcAtmVcDirectlyConnected
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmLcAtmVPI OBJECT mplsLcAtmLcAtmVPI
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 10, line 9 skipping to change at page 10, line 24
mplsLcAtmStdIfConfRowStatus, mplsLcAtmStdIfConfRowStatus,
mplsLcAtmStdIfConfStoreType 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 6. MPLS Label Controlled Frame Relay MIB Definitions
The following MIB module imports from [RFC2115],
[RFC3811], [RFC3813].
MPLS-LC-FR-STD-MIB 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 -- RFC3813 FROM MPLS-LSR-STD-MIB
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB -- RFC2115 FROM FRAME-RELAY-DTE-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB
; ;
mplsLcFrStdMIB MODULE-IDENTITY mplsLcFrStdMIB MODULE-IDENTITY
LAST-UPDATED "200405011200Z" -- 01 May 2004 12:00:00 GMT LAST-UPDATED "200503011200Z" -- 01 March 2005 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 module 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 Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200405011200Z" -- 01 May 2004 12:00:00 GMT "200503011200Z" -- 01 March 2005 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 module.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcFrStdNotifications OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 0 } mplsLcFrStdNotifications OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 0 }
mplsLcFrStdObjects OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 1 } mplsLcFrStdObjects OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 1 }
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
skipping to change at page 13, line 6 skipping to change at page 13, line 23
delete entries in this table. When configuring delete entries in this table. When configuring
entries in this table, the corresponding ifEntry and entries in this table, the corresponding ifEntry and
mplsInterfaceConfEntry MUST exist before hand. If an entry mplsInterfaceConfEntry MUST exist before hand. If an entry
is attempted to be created by a manager for a corresponding is attempted 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)
except mplsLcFrStdInterfaceConfRowStatus and
mplsLcFrStdInterfaceConfStoreType."
::= { mplsLcFrStdInterfaceConfEntry 5 } ::= { mplsLcFrStdInterfaceConfEntry 5 }
mplsLcFrStdInterfaceConfStoreType 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 "The storage type for this conceptual row.
are writable for permanent entries." Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLcFrStdInterfaceConfEntry 6 } ::= { mplsLcFrStdInterfaceConfEntry 6 }
-- End of mplsLcFrStdInterfaceConfTable -- End of mplsLcFrStdInterfaceConfTable
-- Module compliance. -- Module compliance.
mplsLcFrStdCompliances mplsLcFrStdCompliances
OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 1 } OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 1 }
mplsLcFrStdGroups mplsLcFrStdGroups
skipping to change at page 13, line 42 skipping to change at page 14, line 15
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide "Compliance statement for agents that provide
full support for MPLS-LC-FR-STD-MIB. Such full support for MPLS-LC-FR-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 {
mplsLcFrStdIfGroup mplsLcFrStdIfGroup
} }
OBJECT mplsLcFrStdInterfaceConfRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
::= { mplsLcFrStdCompliances 1 } ::= { mplsLcFrStdCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLcFrStdModuleReadOnlyCompliance MODULE-COMPLIANCE mplsLcFrStdModuleReadOnlyCompliance 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-FR-STD-MIB. provide read-only support for MPLS-LC-FR-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
-- 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 {
mplsLcFrStdIfGroup mplsLcFrStdIfGroup
} }
-- mplsLcFrStdInterfaceConfTable -- mplsLcFrStdInterfaceConfTable
OBJECT mplsLcFrStdTrafficMinDlci OBJECT mplsLcFrStdTrafficMinDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 14, line 38 skipping to change at page 15, line 14
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdCtrlMaxDlci OBJECT mplsLcFrStdCtrlMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdInterfaceConfRowStatus OBJECT mplsLcFrStdInterfaceConfRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), MIN-ACCESS read-only
createAndGo(4), destroy(6) DESCRIPTION "Write access is not required."
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
OBJECT mplsLcFrStdInterfaceConfStoreType OBJECT mplsLcFrStdInterfaceConfStoreType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcFrStdCompliances 2 } ::= { mplsLcFrStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcFrStdIfGroup OBJECT-GROUP mplsLcFrStdIfGroup OBJECT-GROUP
skipping to change at page 15, line 20 skipping to change at page 15, line 43
mplsLcFrStdInterfaceConfStoreType 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."
::= { mplsLcFrStdGroups 1 } ::= { mplsLcFrStdGroups 1 }
END END
8. Security Considerations 7. Authors' Addresses
Thomas D. Nadeau Subrahmanya Hegde
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 225 East Tazman Drive
Boxboro, MA 01719 San Jose, CA
Phone: +1-978-936-1470 Phone: +1-408-525-6562
Email: tnadeau@cisco.com Email: subrah@cisco.com
8. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is
subject to the rights, licenses and restrictions contained in BCP
78, and except as set forth therein, the authors retain all their
rights.
This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
9. Acknowledgments
We wish to thank Joan Cucchiara and Carlos Pignataro for
their comments on this document.
10. 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
skipping to change at page 16, line 37 skipping to change at page 17, line 41
authentication and privacy". authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access 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 11. IANA Considerations
9.1 Normative References As described in and as requested in the MPLS-TC-STD-MIB
[RFC3811], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 2 MPLS MIB modules
contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434].
11.1. IANA Considerations for MPLS-LC-ATM-STD-MIB
The IANA is requested to assign { mplsStdMIB 9 } to the
MPLS-LC-ATM-STD-MIB module specified in this document.
11.2. IANA Considerations for MPLS-LC-FR-STD-MIB
The IANA is requested to assign { mplsStdMIB 10 } to the
MPLS-LC-FR-STD-MIB module specified in this document.
12. References
12.1 Normative References
[RFC3034] Conta, A., Doolan, P., Malis, A., "Use
of Label Switching on Frame Relay Networks
Specification", Rfc3034, JANUARY 2001.
[RFC3035] Davie, B., mcCloghhrie, K., Rosen., E., Swallow, G.,
Rekhter, Y., Doolan, P., "MPLS using LDP and ATM VC
Switching", RFC3035, January 2001.
[RFC2115] Brown, C., Baker, F., "Management Information Base [RFC2115] Brown, C., Baker, F., "Management Information Base
for Frame Relay DTEs Using SMIv2", RFC2115, September for Frame Relay DTEs Using SMIv2", RFC2115, September
1997. 1997.
[RFC2514] Noto, M., Spiegel, E., Tesink, K., et al., "Definitions [RFC2514] Noto, M., Spiegel, E., Tesink, K., et al., "Definitions
of Textual Conventions and OBJECT-IDENTITIES for ATM of Textual Conventions and OBJECT-IDENTITIES for ATM
Management", RFC2514, February 1999. Management", RFC2514, February 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.
[TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS [RFC3811] Nadeau, T., Cucchiara, J., Editors,
"Definition of Textual Conventions and OBJECT-
IDENTITIES for Multi-Protocol Label Switching (MPLS)
Management", RFC3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS
Traffic Engineering Management Information Base ", Traffic Engineering Management Information Base ",
RFC3812, June 2004. RFC3812, June 2004.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. [RFC3813] 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 ", RFC3813, June 2004. Information Base ", RFC3813, June 2004.
[TCMIB] Nadeau, T., Cucchiara, J., Editors,
"Definition of Textual Conventions and OBJECT-
IDENTITIES for Multi-Protocol Label Switching (MPLS)
Management", RFC3811, June 2004.
9.2 Informative 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.
[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.
12.2 Informative References
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[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 [RFC3815] 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. June 2004.
10. Authors' Addresses
Thomas D. Nadeau Subrahmanya Hegde
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 225 East Tazman Drive
Boxboro, MA 01719 San Jose, CA
Phone: +1-978-936-1470 Phone: +1-408-525-6562
Email: tnadeau@cisco.com Email: subrah@cisco.com
11. Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
12. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
13. Intellectual Property 13. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 18, line 51 skipping to change at line 946
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
14. IANA Considerations
As described in and as requested in the MPLS-TC-STD-MIB
[TCMIB], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 2 MPLS MIB Modules
contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434].
14.1. IANA Considerations for MPLS-LC-ATM-STD-MIB
The IANA is requested to assign { mplsStdMIB 9 } to the
MPLS-LC-ATM-STD-MIB module specified in this document.
14.2. IANA Considerations for MPLS-LC-FR-STD-MIB
The IANA is requested to assign { mplsStdMIB 10 } to the
MPLS-LC-FR-STD-MIB module specified in this document.
15. Acknowledgments
We wish to thank Joan Cucchiara and Carlos Pignataro for
their 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/