draft-ietf-mpls-lc-if-mib-00.txt   draft-ietf-mpls-lc-if-mib-01.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: December 2002 Cisco Systems, Inc. Expires: October 2004 Cisco Systems, Inc.
June 2002 January 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-00.txt draft-ietf-mpls-lc-if-mib-01.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 [RFC2026]. all provisions of Section 10 of RFC 2026.
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 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.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
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 .............................................. 3
3. Terminology ............................................... 3 3. Terminology ............................................... 3
4. The SNMP Management Framework ............................. 3 4. The SNMP Management Framework ............................. 3
5. Feature Checklist ......................................... 4 5. Interface Stacking of LC-ATM and LC-FR .................... 5
6. Outline ................................................... 5 6. MPLS Label Controlled ATM MIB Definitions ................. 13
6.1. Summary of LSR MIB ..................................... 6 7. MPLS Label Controlled Frame Relay MIB Definitions ......... 13
7. Brief Description of MIB Objects .......................... 6 8. Security Considerations ................................... 51
7.1. mplsInterfaceConfTable ................................. 7 9. References ................................................ 52
7.2. mplsInterfacePerfTable ................................. 7 9.1 Normative References...................................... 52
7.3. mplsInSegmentTable ..................................... 7 9.2 Informative References.................................... 52
7.4. mplsInSegmentPerfTable ................................. 7 10. Authors' Addresses ....................................... 54
7.5. mplsOutSegmentTable .................................... 8 11. Full Copyright Statement ................................. 55
7.6. mplsOutSegmentPerfTable ................................ 8 12. Intellectual Property Notice ............................ 52
7.7. mplsXCTable ............................................ 8 13. IANA Considerations ..................................... 52
7.8. mplsLabelStackTable .................................... 8 14.1. IANA Considerations for MPLS-LC-ATM-MIB ............... 52
7.9. mplsTrafficParamTable .................................. 9 14.2. IANA Considerations for MPLS-LC-FR-MIB ................ 52
8. Example of LSP Setup ...................................... 9
9. Application of the Interface Group to MPLS ................ 11
9.1. Support of the MPLS Layer by ifTable ................... 11
10. The Use of RowPointer .................................... 13
11. MPLS Label Switch Router MIB Definitions ................. 13
12. Security Considerations .................................. 51
13. Acknowledgments .......................................... 52
14. References ............................................... 52
15. Authors' Addresses ....................................... 54
16. Full Copyright Statement ................................. 55
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 and MPLS-TE 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 [LSRMIB]
and MPLS-TE [TEMIB] MIBs. This document also contains a and MPLS-TE [TEMIB] MIBs. This document also contains a
skipping to change at page 3, line 17 skipping to change at page 3, line 4
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.
4. The SNMP Management Framework 4. The SNMP Management Framework
For a detailed overview of the documents that describe the current
The SNMP Management Framework presently consists of five major Internet-Standard Management Framework, please refer to section 7 of
components: RFC 3410 [RFC3410].
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570].
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. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
5. Interface Stacking Relationship for MPLS
The MPLS-LSR and MPLS-TE MIBs define the media-specific
extensions to the Interfaces Group for managing MPLS interfaces.
They also define the conceptual interface stacking as follows.
+------------------------------------------------+
| MPLS tunnel interface ifType = mplsTunnel(150) |
+------------------------------------------------+
| MPLS-interface ifType = mpls(166) +
+------------------------------------------------+
| Underlying Layer... +
+------------------------------------------------+
In the above diagram, MPLS-enabled interfaces are
represented by an ifEntry with ifType set to mpls(166).
This subinterface is conceptually stacked above some
underlying layer. The "Underlying Layer..." refers to the
ifIndex of any interface type, which has been defined for MPLS
interworking. Examples include ATM, Frame Relay, Ethernet, etc.
The top-most layer defines zero or more TE tunnel interfaces
that are conceptually stacked above the MPLS-type interface
that carries its traffic.
6. Interface Stacking of LC-ATM 5. Interface Stacking of LC-ATM
Since LC-ATM interfaces can carry labeled MPLS traffic, Since LC-ATM interfaces can carry labeled MPLS traffic,
they too are considered MPLS subinterfaces with ifType = they too are considered MPLS subinterfaces with ifType =
mpls(166). They differ slightly in their capability 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 MIB's mplsInterfaceConfTable (see section 7 for
LC-ATM or 8 for LC-FR). LC-ATM or 8 for LC-FR).
7. MPLS Label Controlled ATM MIB Definitions 6. MPLS Label Controlled ATM MIB Definitions
MPLS-LC-ATM-MIB DEFINITIONS ::= BEGIN
MPLS-LC-ATM-MIB-DRAFT-01 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
mplsInterfaceConfIndex
FROM MPLS-LSR-MIB
AtmVpIdentifier AtmVpIdentifier
FROM ATM-TC-MIB FROM ATM-TC-MIB
mplsMIB, MplsAtmVcIdentifier mplsStdMIB, MplsAtmVcIdentifier
FROM MPLS-TC-MIB FROM MPLS-TC-STD-MIB
mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB
; ;
mplsLcAtmMIB MODULE-IDENTITY mplsLcAtmMIB MODULE-IDENTITY
LAST-UPDATED "200205101200Z" -- 10 May 2002 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. 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 5, line 40 skipping to change at page 4, line 15
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 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
"200012251200Z" -- 25 December 2001 12:00:00 GMT "200401301200Z" -- 30 January 2004 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC XXXX."
::= { mplsMIB n } -- To Be Assigned, maybe 6 ::= { mplsStdMIB XXX } -- To Be Assigned by IANA, maybe 6
-- Top level components of this MIB. -- Top level components of this MIB.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcAtmNotifyPrefix OBJECT IDENTIFIER ::= { mplsLcAtmMIB 0 }
mplsLcAtmNotifications OBJECT IDENTIFIER ::= { mplsLcAtmMIB 0 }
mplsLcAtmObjects OBJECT IDENTIFIER ::= { mplsLcAtmMIB 1 } mplsLcAtmObjects OBJECT IDENTIFIER ::= { mplsLcAtmMIB 1 }
mplsLcAtmNotifications OBJECT IDENTIFIER ::= { mplsLcAtmMIB 2 }
mplsLcAtmConformance OBJECT IDENTIFIER ::= { mplsLcAtmMIB 3 }
mplsLcAtmConformance OBJECT IDENTIFIER ::= { mplsLcAtmMIB 2 }
-- MPLS LC-ATM Interface Configuration Table.
mplsLcAtmIfConfTable OBJECT-TYPE mplsLcAtmIfConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcAtmIfConfEntry SYNTAX SEQUENCE OF MplsLcAtmIfConfEntry
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 extends the MPLS-LSR MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcAtmObjects 1 } ::= { mplsLcAtmObjects 1 }
skipping to change at page 6, line 39 skipping to change at page 5, line 13
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 { mplsInterfaceConfIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcAtmIfConfTable 1 } ::= { mplsLcAtmIfConfTable 1 }
MplsLcAtmIfConfEntry ::= SEQUENCE { MplsLcAtmIfConfEntry ::= SEQUENCE {
mplsLcAtmCtrlVpi AtmVpIdentifier, mplsLcAtmCtrlVpi AtmVpIdentifier,
mplsLcAtmCtrlVci MplsAtmVcIdentifier, mplsLcAtmCtrlVci MplsAtmVcIdentifier,
mplsLcAtmUnlabTrafVpi AtmVpIdentifier, mplsLcAtmUnlabTrafVpi AtmVpIdentifier,
mplsLcAtmUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmUnlabTrafVci MplsAtmVcIdentifier,
mplsLcAtmVcMerge TruthValue, mplsLcAtmVcMerge TruthValue,
mplsLcAtmIfConfRowStatus RowStatus, mplsLcAtmIfConfRowStatus RowStatus,
mplsLcAtmIfConfStoreType StorageType mplsLcAtmIfConfStoreType StorageType
skipping to change at page 8, line 34 skipping to change at page 7, line 8
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 } ::= { mplsLcAtmIfConfEntry 7 }
-- End of mplsLcAtmIfConfTable -- End of mplsLcAtmIfConfTable
-- Module compliance. -- Module compliance.
mplsLcAtmGroups mplsLcAtmCompliances
OBJECT IDENTIFIER ::= { mplsLcAtmConformance 1 } OBJECT IDENTIFIER ::= { mplsLcAtmConformance 1 }
mplsLcAtmCompliances mplsLcAtmGroups
OBJECT IDENTIFIER ::= { mplsLcAtmConformance 2 } OBJECT IDENTIFIER ::= { mplsLcAtmConformance 2 }
mplsLcAtmModuleCompliance MODULE-COMPLIANCE mplsLcAtmModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support "Compliance statement for agents that support
MPLS LC-ATM Interfaces." MPLS LC-ATM Interfaces."
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
skipping to change at page 9, line 8 skipping to change at page 7, line 26
mplsLcAtmModuleCompliance MODULE-COMPLIANCE mplsLcAtmModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support "Compliance statement for agents that support
MPLS LC-ATM Interfaces." MPLS LC-ATM Interfaces."
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 {
mplsLcAtmIfGroup mplsLcAtmIfGroup
} }
GROUP mplsLcAtmIfGroup
DESCRIPTION
"This group is mandatory for those LSRs
that support LC-ATM interfaces."
-- mplsLcAtmIfConfTable -- mplsLcAtmIfConfTable
OBJECT mplsLcAtmCtrlVpi OBJECT mplsLcAtmCtrlVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmCtrlVci OBJECT mplsLcAtmCtrlVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmUnlabTrafVpi OBJECT mplsLcAtmUnlabTrafVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmUnlabTrafVci, OBJECT mplsLcAtmUnlabTrafVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmVcMerge OBJECT mplsLcAtmVcMerge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmIfConfRowStatus OBJECT mplsLcAtmIfConfRowStatus
skipping to change at page 10, line 23 skipping to change at page 8, line 35
mplsLcAtmUnlabTrafVci, mplsLcAtmUnlabTrafVci,
mplsLcAtmVcMerge, mplsLcAtmVcMerge,
mplsLcAtmIfConfRowStatus, mplsLcAtmIfConfRowStatus,
mplsLcAtmIfConfStoreType mplsLcAtmIfConfStoreType
} }
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 } ::= { mplsLcAtmGroups 1 }
END END
8. MPLS Label Controlled Frame-Relay MIB Definitions 7. MPLS Label Controlled Frame-Relay MIB Definitions
MPLS-LC-FR-MIB DEFINITIONS ::= BEGIN
MPLS-LC-FR-MIB-DRAFT-01 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
mplsInterfaceConfIndex mplsInterfaceIndex
FROM MPLS-LSR-MIB FROM MPLS-LSR-STD-MIB
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB FROM FRAME-RELAY-DTE-MIB
mplsMIB mplsStdMIB
FROM MPLS-TC-MIB FROM MPLS-TC-STD-MIB
; ;
mplsLcFrMIB MODULE-IDENTITY mplsLcFrMIB MODULE-IDENTITY
LAST-UPDATED "200205101200Z" -- 10 May 2002 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. 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 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
"200012251200Z" -- 25 December 2001 12:00:00 GMT "200401301200Z" -- 30 January 2004 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial draft revision."
::= { mplsMIB n } -- To Be Assigned, maybe 7 ::= { mplsStdMIB XXX } -- To Be Assigned by IANA, maybe 7
-- Top level components of this MIB. -- Top level components of this MIB.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcFrNotifyPrefix OBJECT IDENTIFIER ::= { mplsLcFrMIB 0 }
mplsLcFrNotifications OBJECT IDENTIFIER ::= { mplsLcFrMIB 0 }
mplsLcFrObjects OBJECT IDENTIFIER ::= { mplsLcFrMIB 1 } mplsLcFrObjects OBJECT IDENTIFIER ::= { mplsLcFrMIB 1 }
mplsLcFrNotifications OBJECT IDENTIFIER ::= { mplsLcFrMIB 2 } mplsLcFrConformance OBJECT IDENTIFIER ::= { mplsLcFrMIB 2 }
mplsLcFrConformance OBJECT IDENTIFIER ::= { mplsLcFrMIB 3 }
-- MPLS LC-FR Interface Configuration Table. -- MPLS LC-FR Interface Configuration Table.
mplsLcFrIfConfTable OBJECT-TYPE mplsLcFrIfConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcFrIfConfEntry SYNTAX SEQUENCE OF MplsLcFrIfConfEntry
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 extends the MPLS-LSR MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcFrObjects 1 } ::= { mplsLcFrObjects 1 }
skipping to change at page 12, line 12 skipping to change at page 10, line 15
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 { mplsInterfaceConfIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcFrIfConfTable 1 } ::= { mplsLcFrIfConfTable 1 }
MplsLcFrIfConfEntry ::= SEQUENCE { MplsLcFrIfConfEntry ::= SEQUENCE {
mplsLcFrTrafficMinDlci DLCI, mplsLcFrTrafficMinDlci DLCI,
mplsLcFrTrafficMaxDlci DLCI, mplsLcFrTrafficMaxDlci DLCI,
mplsLcFrCtrlMinDlci DLCI, mplsLcFrCtrlMinDlci DLCI,
mplsLcFrCtrlMaxDlci DLCI, mplsLcFrCtrlMaxDlci DLCI,
mplsLcFrIfConfRowStatus RowStatus, mplsLcFrIfConfRowStatus RowStatus,
mplsLcFrIfConfStoreType StorageType mplsLcFrIfConfStoreType StorageType
} }
skipping to change at page 13, line 46 skipping to change at page 11, line 48
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 } ::= { mplsLcFrIfConfEntry 6 }
-- End of mplsLcFrIfConfTable -- End of mplsLcFrIfConfTable
-- Module compliance. -- Module compliance.
mplsLcFrGroups mplsLcFrCompliances
OBJECT IDENTIFIER ::= { mplsLcFrConformance 1 } OBJECT IDENTIFIER ::= { mplsLcFrConformance 1 }
mplsLcFrCompliances mplsLcFrGroups
OBJECT IDENTIFIER ::= { mplsLcFrConformance 2 } OBJECT IDENTIFIER ::= { mplsLcFrConformance 2 }
mplsLcFrModuleCompliance MODULE-COMPLIANCE mplsLcFrModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support "Compliance statement for agents that support
MPLS LC-FR Interfaces." MPLS LC-FR Interfaces."
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 mplsLcFrIfGroup
} }
GROUP mplsLcFrIfGroup
DESCRIPTION
"This group is mandatory for those LSRs
that support LC-FR interfaces."
-- mplsLcFrIfConfTable -- mplsLcFrIfConfTable
OBJECT mplsLcFrTrafficMinDlci OBJECT mplsLcFrTrafficMinDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrTrafficMaxDlci OBJECT mplsLcFrTrafficMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 15, line 25 skipping to change at page 13, line 17
mplsLcFrIfGroup OBJECT-GROUP mplsLcFrIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcFrTrafficMinDlci, mplsLcFrTrafficMinDlci,
mplsLcFrTrafficMaxDlci, mplsLcFrTrafficMaxDlci,
mplsLcFrCtrlMinDlci, mplsLcFrCtrlMinDlci,
mplsLcFrCtrlMaxDlci, mplsLcFrCtrlMaxDlci,
mplsLcFrIfConfRowStatus, mplsLcFrIfConfRowStatus,
mplsLcFrIfConfStoreType mplsLcFrIfConfStoreType
} }
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 } ::= { mplsLcFrGroups 1 }
END END
12. Security Considerations 8. Security Considerations
This module does not define any management objects. Instead, it
defines two new ifTypes which may be used by other MPLS MIB
modules to define management objects.
Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has
no impact on the security of the Internet.
13. Acknowledgments
TBD. It is clear that these MIB modules are potentially useful for
monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These
MIB can also be used for configuration of certain objects, and
anything that can be configured can be incorrectly configured,
with potentially disastrous results.
14. References 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
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", o the MplsLcAtmIfConfTable and mplsLcFrIfConfTable collectively
RFC 1700, October 1994. See also: contain objects which may be used to provision MPLS LC or FR-enabled
http://www.isi.edu/in-notes/iana/assignments/smi- interfaces. Unauthorized access to objects in these tables,
numbers could result in disruption of traffic on the network. This is
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS especially true if traffic has been established over these
FAMILY NUMBERS,(http://www.isi.edu/in- interfaces. The use of stronger mechanisms such as SNMPv3
notes/iana/assignements/address-family-numbers), security should be considered where possible. Specifically,
for MIB see: SNMPv3 VACM and USM MUST be used with any v3 agent which
ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum implements this MIB module. Administrators should consider
bers.mib whether read access to these objects should be allowed,
since read access may be undesirable under certain
circumstances.
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, Some of the readable objects in this MIB module "i.e., objects with a
Viswanathan, A. and H. Sjostrand, "Definition of MAX-ACCESS other than not-accessible" may be considered sensitive or
Textual Conventions and OBJECT-IDENTITIES for Multi- vulnerable in some network environments. It is thus important to
Protocol Label Switching (MPLS) Management", control even GET and/or NOTIFY access to these objects and possibly
Internet Draft <draft-ietf-mpls-tc-mib-02.txt>, to even encrypt the values of these objects when sending them over
August 2001. the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
[RFC1155] Rose, M., and K. McCloghrie, "Structure and o the MplsLcAtmIfConfTable and mplsLcFrIfConfTable collectively
Identification of Management Information for TCP/IP- collectively show the LC-ATM and/or LC-FR interfaces,
based Internets", RFC 1155, May 1990. their associated configurations and their linkages to other
MPLS-related configuration and/or performanc statistics.
Administrators not wishing to reveal this information should
consider these objects sensitive/vulnerable and take
precautions so they are not revealed.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, SNMP versions prior to SNMPv3 did not include adequate security.
"Simple Network Management Protocol", RFC 1157, May Even if the network itself is secure "for example by using IPSec",
1990. even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects
in this MIB module.
[RFC1215] M. Rose, "A Convention for Defining Traps for use It is RECOMMENDED that implementers consider the security features as
with the SNMP", RFC 1215, March 1991. provided by the SNMPv3 framework "see [RFC3410], section 8",
including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy".
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Further, deployment of SNMP versions prior to SNMPv3 is NOT
Waldbusser, "Introduction to Community-based RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
SNMPv2", RFC 1901, January 1996. enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access
to the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 9. References
Waldbusser, "Protocol Operations for Version 2 of
the Simple Network Management Protocol (SNMPv2)",
RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 9.1 Normative References
Waldbusser, "Transport Mappings for Version 2 of
the Simple Network Management Protocol (SNMPv2)",
RFC 1906, January 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2233] McCloghrie, K., and F. Kastenholtz, "The Interfaces [RFC2515] Tesink, K., et al., "Definitions of Managed Objects
Group MIB using SMIv2", RFC 2233, Nov. 1997 for ATM Management", RFC 2515, February 1999.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
for the Internet Protocol", RFC 2401, November J., Rose, M., and S. Waldbusser, "Structure of
1998. Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2515] Tesink, K., "Definitions of Managed Objects for ATM [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Management", RFC 2515, Feb. 1999 J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
"Introduction to Version 3 of the Internet-standard J., Rose, M., and S. Waldbusser, "Conformance
Network Management Framework", RFC 2570, April Statements for SMIv2", STD 58, RFC 2580, April 1999.
1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Architecture for Describing SNMP Management Group MIB", RFC 2863, June 2000.
Frameworks", RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Message Processing and Dispatching for the Simple "Multiprotocol Label Switching Architecture", RFC
Network Management Protocol (SNMP)", RFC 2572, 3031, January 2001.
April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [RFC3291] Daniele, M., Haberman, B., Routhier., S.,
Applications", RFC 2573, April 1999. Schoenwaelder., J., "Textual Conventions
for Internet Network Addresses", RFC3291,
May 2002.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Model (USM) for version 3 of the Simple Network Architecture for Describing Simple Network Management
Management Protocol (SNMPv3)", RFC 2574, April Protocol (SNMP) Management Frameworks", RFC 3411,
1999. December 2002.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- [TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS
based Access Control Model (VACM) for the Simple Traffic Engineering Management Information Base ",
Network Management Protocol (SNMP)", RFC 2575, Internet Draft <draft-ietf-mpls-te-mib-09.txt>,
April 1999. November 2002.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., [LSRMIB] Srinivasan, C., Viswanathan, A. and T.
Case, J., Rose, M., and S. Waldbusser, "Structure Nadeau, "MPLS Multiprotocol Label Switching
of Management Information Version 2 (SMIv2)", STD (MPLS) Label Switch Router Management
58, RFC 2578, April 1999. Information Base ", Internet Draft <draft-
ietf-mpls-lsr-mib-14.txt>, November 2003.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C.,
Case, J., Rose, M., and S. Waldbusser, "Textual Viswanathan, A., Sjostrand, H. and K. Kompella,
Conventions for SMIv2", STD 58, RFC 2579, April "Definition of Textual Conventions and OBJECT-
1999. IDENTITIES for Multi-Protocol Label Switching (MPLS)
Management", Internet Draft <draft-ietf-mpls-tc-mib-
06.txt>, April 2003.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
and J. McManus, "Requirements for Traffic FAMILY NUMBERS, (http://www.isi.edu/in-
Engineering Over MPLS", RFC 2702, September 1999. notes/iana/assignements/address-family-numbers),
for MIB see:
ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum
bers.mib
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 9.2 Informative References
Case, J., Rose, M., and S. Waldbusser, "Conformance [RFC2026] S. Bradner, "The Internet Standards Process --
Statements for SMIv2", STD 58, RFC 2580, April Revision 3", RFC 2026, October 1996.
1999.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3413] Levi, D., Meyer, P., Stewart, B.,
"Multiprotocol Label Switching Architecture", RFC "SNMP Applications", RFC 3413, December 2002.
3031, January 2001.
[RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Federokow, G., Li, T., and A. Conta, "MPLS Label "Introduction and Applicability Statements for
Stack Encoding", RFC 3032, January 2001. Internet-Standard Management Framework", RFC 3410,
December 2002.
15. Authors' Addresses 10. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 300 Beaver Brook Road
Chelmsford, MA 01824 Boxboro, MA 01719
Phone: +1-978-244-3051 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
Phone: +1-408-525-6562 Phone: +1-408-525-6562
Email: subrah@cisco.com Email: subrah@cisco.com
16. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
skipping to change at line 889 skipping to change at page 17, line 9
languages other than English. languages other than English.
The limited permissions granted above are perpetual and will not The limited permissions granted above are perpetual and will not
be revoked by the Internet Society or its successors or assigns. be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
12. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
13. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB
[MPLSTCMIB], 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-MIB
The IANA is requested to assign { mplsStdMIB 6 } to the
MPLS-LC-ATM-MIB module specified in this document.
14.2. IANA Considerations for MPLS-LC-FR-MIB
The IANA is requested to assign { mplsStdMIB 7 } to the
MPLS-LC-FR-MIB module specified in this document.
 End of changes. 

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