draft-ietf-mpls-lc-if-mib-08.txt   rfc4368.txt 
Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde
Expires: April 2006 Cisco Systems, Inc.
October 2005
Multiprotocol Label Switching (MPLS) Label-Controlled ATM
and Frame-Relay Management Interface Definition
draft-ietf-mpls-lc-if-mib-08.txt
Status of this Memo Network Working Group T. Nadeau
Request for Comments: 4368 S. Hegde
Category: Standards Track Cisco Systems, Inc.
January 2006
By submitting this Internet-Draft, each author represents that Multiprotocol Label Switching (MPLS) Label-Controlled
any applicable patent or other IPR claims of which he or she is Asynchronous Transfer Mode (ATM) and Frame-Relay
aware have been or will be disclosed, and any of which he or she Management Interface Definition
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
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 This document specifies an Internet standards track protocol for the
and may be updated, replaced, or obsoleted by other documents at any Internet community, and requests discussion and suggestions for
time. It is inappropriate to use Internet-Drafts as reference improvements. Please refer to the current edition of the "Internet
material or to cite them other than as "work in progress." Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2006).
http://www.ietf.org/shadow.html.
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
Frame-Relay and ATM interfaces can be managed given the and Asynchronous Transfer Mode (ATM) interfaces can be managed given
interface stacking as defined in the MPLS-LSR-STD-MIB and the 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
2. Terminology ............................................... 3
3. The SNMP Management Framework ............................. 3
4. Interface Stacking of LC-ATM and LC-FR .................... 5
5. Structure of the MPLS-LC-ATM-STD-MIB module ............... 14
6. Structure of the MPLS-LC-FR-STD-MIB module ................ 14
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
7. MPLS Label Controlled ATM MIB Definitions ................. 13 1. Introduction ....................................................2
8. MPLS Label Controlled Frame Relay MIB Definitions ......... 15 2. Terminology .....................................................2
9. Authors' Addresses ........................................ 54 3. The SNMP Management Framework ...................................3
10. Full Copyright Statement................................... 55 4. Interface Stacking of LC-ATM ....................................3
11. Acknowledgments............................................ 52 5. Structure of the MPLS-LC-ATM-STD-MIB Module .....................3
12. Security Considerations ................................... 51 6. Structure of the MPLS-LC-FR-STD-MIB Module ......................4
13. IANA Considerations........................................ 55 7. MPLS Label-Controlled ATM MIB Definitions .......................5
14. References ................................................ 52 8. MPLS Label-Controlled Frame Relay MIB Definitions ..............12
14.1 Normative References ..................................... 52 9. Acknowledgments ................................................18
14.2 Informative References ................................... 53 10. Security Considerations .......................................18
15. Intellectual Property...................................... 55 11. IANA Considerations ...........................................19
11.1. IANA Considerations for MPLS-LC-ATM-STD-MIB ..............19
11.2. IANA Considerations for MPLS-LC-FR-STD-MIB ...............19
12. References ....................................................20
12.1. Normative References .....................................20
12.2. Informative References ...................................21
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
the interface stacking as defined in the MPLS-LSR-STD [RFC3813] interface stacking as defined in the MPLS-LSR-STD [RFC3813] and
and MPLS-TE-STD [RFC3812] MIBs. This document also contains a MPLS-TE-STD [RFC3812] MIBs. This document also contains a MIB module
MIB module that sparsely extends the MPLS-LSR-STD MIB's that sparsely extends the MPLS-LSR-STD MIB's mplsInterfaceConfTable
mplsInterfaceConfTable in such a way as to identify which in such a way as to identify which MPLS-type interfaces have LC-ATM
MPLS-type interfaces have LC-ATM or LC-FR capabilities. or LC-FR capabilities. Comments should be made directly to the MPLS
Comments should be made directly to the MPLS mailing list at 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",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
"OPTIONAL" in this document are to be interpreted as described in document are to be interpreted as described in RFC 2119, reference
RFC 2119, reference [RFC2119]. [RFC2119].
2. Terminology 2. Terminology
This document uses terminology from the document describing the This document uses terminology from the document describing the MPLS
MPLS architecture [RFC3031], as well as RFC3035 and RFC3034. architecture [RFC3031], as well as from RFC 3035 and RFC 3034.
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 C-FR RFC 3034 defines a label-switching-controlled Frame Relay
(LC-FR) interface a Frame-Relay interface controlled by the (LC-FR) interface. Packets traversing such an interface carry
label switching control component. Packets traversing labels in the DLCI field
such an interface carry labels in the DLCI field
LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM)
interface as an ATM interface controlled by the label
switching control component. When a packet traversing such
an interface is received, it is treated as a labeled packet.
The packet's top label is inferred either from the contents
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
of the VCI field or the combined contents of the VPI and VCI C-ATM RFC 3035 defines a label-switching-controlled ATM (LC-ATM)
fields. Any two LDP peers which are connected via an LC-ATM interface as an ATM interface controlled by the label switching
interface will use LDP negotiations to determine which of control component. When a packet traversing such an interface
these cases is applicable to that interface. is received, it is treated as a labeled packet. The packet's
Static configuration of labels is also possible. top label is inferred from either the contents of the Virtual
Channel Identifier (VCI) field or the combined contents of the
Virtual Path Identifier (VPI) and VCI fields. Any two LDP
peers that are connected via an LC-ATM interface will use LDP
negotiations to determine which of these cases is applicable to
that interface. Static configuration of labels is also
possible.
When LDP is used to distribute labels for use on label-controlled 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 [RFC3815] 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 [RFC3815] when LC-FR interfaces the MPLS-LDP-FRAME-RELAY-STD-MIB [RFC3815] when LC-FR interfaces are
are used. Specifically, used.
3. 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].
4. 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,
traffic, they too are considered MPLS subinterfaces with they too are considered MPLS subinterfaces with ifType = mpls(166).
ifType = mpls(166). They differ slightly in their capability They differ slightly in their capability from a packet-oriented MPLS
from a packet-oriented MPLS interface in that they may interface in that they may carry ATM- or Frame-Relay-encapsulated
carry ATM or Frame-Relay encapsulated traffic. It is traffic. It is thus beneficial to identify them as such. To do
thus beneficial to identify them as such. To identify this, two tables are defined that extend the MPLS-LSR-STD MIB's
them as such, two tables are defined which extend the mplsInterfaceTable (see section 5 for LC-ATM or section 6 for LC-FR).
MPLS-LSR-STD MIB's mplsInterfaceTable (see section 5 for
LC-ATM or 6 for LC-FR).
5. Structure of the MPLS-LC-ATM-STD-MIB module
The MPLS-LC-ATM-STD-MIB module is structured simply 5. Structure of the MPLS-LC-ATM-STD-MIB Module
as a table of entries which sparesely extend those
found in the interfaces table. In particular, the
entries in the mplsLcAtmStdInterfaceConfTable
extend those interfaces capable of supporting
MPLS, as is defined in [RFC3813] to include those
entries which also support LC-ATM (and their unique
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
attributes). Therefore, the module can be The MPLS-LC-ATM-STD-MIB module is structured simply as a table of
visualized as follows. Note that the ifTable entries that sparsely extend those found in the interfaces table. In
comes from [RFC2863], mplsInterfaceTable from particular, the entries in the mplsLcAtmStdInterfaceConfTable extend
[RFC3813] and mplsLcAtmStdInterfaceConfTable from interfaces capable of supporting MPLS, as is defined in [RFC3813], to
the MPLS-LC-ATM-STD-MIB module described below. include entries that also support LC-ATM (and their unique
attributes). Therefore, the module can be visualized as follows.
Note that the ifTable comes from [RFC2863], the mplsInterfaceTable
from [RFC3813], and the mplsLcAtmStdInterfaceConfTable from the
MPLS-LC-ATM-STD-MIB module described below.
ifTable mplsInterfaceTable mplsLcAtmStdInterfaceConfTable ifTable mplsInterfaceTable mplsLcAtmStdInterfaceConfTable
.1 .1
.2 .2 .2 .2
.3 .3
.4 .4 .4 .4 .4 .4
.5 .5
In the example shown above, five interfaces exist on the device in
question. Of those interfaces, those with ifIndex = .2 and .4 are of
ifType = mpls(166) indicating that they are capable of MPLS. Of
those two, the entry with index .4 is capable of MPLS LC-ATM
operations.
In the example shown above, five interfaces exist on the Note that the label partition model utilized by the authors of this
device in question. Of those interfaces, those with document reflects widespread implementation and is seen by the MPLS
ifIndex = .2 and .4 are of ifType = mpls(166) indicating working group as sufficiently flexible to meet the operational needs,
that they are capable of MPLS. Of those two, the entry even if it is more restrictive than [RFC3035] allows. To this end,
with index .4 is capable of MPLS LC-ATM operations. we have limited the control and unlabeled VPI and VCI to single
values. Note that mplsLcAtmStdUnlabTrafVci and mplsLcAtmStdCtrlVci
It should be noted that the label partition model MUST not be equal; nor should mplsLcAtmStdCtrlVpi or
utilized by the authors of this document reflects widespread
implementation, and is seen by the MPLS working group as
sufficiently flexible to meet the operational needs, even
if it is more restrictive than [RFC3035] allows. To this
end, we have limited the control and unlabeled VPI and
VCI to single values. It should be noted
mplsLcAtmStdUnlabTrafVci and mplsLcAtmStdCtrlVci MUST
not be equal, nor should mplsLcAtmStdCtrlVpi or
mplsLcAtmStdUnlabTrafVpi be equal. mplsLcAtmStdUnlabTrafVpi be equal.
6. Structure of the MPLS-LC-FR-STD-MIB module 6. Structure of the MPLS-LC-FR-STD-MIB Module
The MPLS-LC-FR-STD-MIB module is structured simply The MPLS-LC-FR-STD-MIB module is structured simply as a table of
as a table of entries which sparesely extend those entries that sparsely extend those found in the interfaces table. In
found in the interfaces table. In particular, the particular, the entries in the mplsLcFrStdInterfaceConfTable extend
entries in the mplsLcFrStdInterfaceConfTable interfaces capable of supporting MPLS, as is defined in [RFC3813], to
extend those interfaces capable of supporting include entries that also support LC-Frame Relay (and their unique
MPLS, as is defined in [RFC3813] to include those attributes). Therefore, the module can be visualized as follows.
entries which also support LC-Frame Relay (and their Note that the ifTable comes from [RFC2863], the mplsInterfaceTable
unique attributes). Therefore, the module can be from [RFC3813], and the mplsLcAtmStdInterfaceConfTable from the
visualized as follows. Note that the ifTable MPLS-LC-FR-STD-MIB module described below.
comes from [RFC2863], mplsInterfaceTable from
[RFC3813] and mplsLcAtmStdInterfaceConfTable from
the MPLS-LC-FR-STD-MIB module described below.
ifTable mplsInterfaceTable mplsLcFrStdInterfaceConfTable ifTable mplsInterfaceTable mplsLcFrStdInterfaceConfTable
.1 .1
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
.2 .2 .2 .2
.3 .3
.4 .4 .4 .4 .4 .4
.5 .5
In the example shown above, five interfaces exist on the In the example shown above, five interfaces exist on the device in
device in question. Of those interfaces, those with question. Of those interfaces, those with ifIndex = .2 and .4 are of
ifIndex = .2 and .4 are of ifType = mpls(166) indicating ifType = mpls(166) indicating that they are capable of MPLS. Of
that they are capable of MPLS. Of those two, the entry those two, the entry with index .4 is capable of MPLS LC-Frame Relay
with index .4 is capable of MPLS LC-Frame Relay operations. operations.
It should be noted that even though the architecture as Note that even though the architecture as described in [RFC3034]
described in [RFC3034] calls for supporting mixed labeled calls for supporting mixed labeled and unlabeled traffic, this MIB
and unlabeled traffic, this MIB does not support that does not support that, as this capability does not seem to be used
as this capability does not seem to be used operationally. operationally. Note that the DLCI ranges represented by
It should be noted that the DLCI ranges represented by mplsLcFrStdTrafficMinDlci to mplsLcFrStdTrafficMaxDlci and
mplsLcFrStdTrafficMinDlci and mplsLcFrStdTrafficMaxDlci mplsLcFrStdCtrlMinDlci to mplsLcFrStdCtrlMaxDlci MUST not overlap.
mplsLcFrStdCtrlMinDlci and mplsLcFrStdCtrlMaxDlci MUST
not overlap.
7. MPLS Label Controlled ATM MIB Definitions 7. MPLS Label-Controlled ATM MIB Definitions
The following MIB module imports from [RFC2514], The following MIB module imports from [RFC2514], [RFC3811], and
[RFC3811], [RFC3813]. [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 FROM ATM-TC-MIB
mplsStdMIB, MplsAtmVcIdentifier mplsStdMIB, MplsAtmVcIdentifier
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB
; ;
mplsLcAtmStdMIB MODULE-IDENTITY mplsLcAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200506171200Z" -- 17 June 2005 12:00:00 GMT LAST-UPDATED "200601120000Z" -- 12 January 2006
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
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
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 module 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 (2005). This Copyright (C) The Internet Society (2006). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFC 4368; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200506171200Z" -- 17 June 2005 12:00:00 GMT "200601120000Z" -- 12 January 2006
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC 4368."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA ::= { mplsStdMIB 9 }
-- Top level components of this MIB module. -- 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 }
skipping to change at page 7, line 4 skipping to change at page 6, line 31
-- 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 extends the MPLS-LSR-STD-MIB's this table sparsely extends the MPLS-LSR-STD-MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
::= { 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.
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 exists. If the associated entries in ifTable and
mplsInterfaceConfTable are deleted, the corresponding mplsInterfaceConfTable are deleted, the corresponding
entry in this table must also be deleted shortly entry in this table must also be deleted shortly
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcAtmStdInterfaceConfTable 1 } ::= { mplsLcAtmStdInterfaceConfTable 1 }
MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE { MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE {
mplsLcAtmStdCtrlVpi AtmVpIdentifier, mplsLcAtmStdCtrlVpi AtmVpIdentifier,
mplsLcAtmStdCtrlVci MplsAtmVcIdentifier, mplsLcAtmStdCtrlVci MplsAtmVcIdentifier,
mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier, mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier,
skipping to change at page 8, line 4 skipping to change at page 7, line 31
::= { mplsLcAtmStdInterfaceConfEntry 1 } ::= { mplsLcAtmStdInterfaceConfEntry 1 }
mplsLcAtmStdCtrlVci OBJECT-TYPE mplsLcAtmStdCtrlVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VCI value over which this "This is the VCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
::= { mplsLcAtmStdInterfaceConfEntry 2 } ::= { mplsLcAtmStdInterfaceConfEntry 2 }
mplsLcAtmStdUnlabTrafVpi OBJECT-TYPE mplsLcAtmStdUnlabTrafVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VPI value over which this "This is the VPI value over which this
LSR is willing to accept unlabeled traffic LSR is willing to accept unlabeled traffic
on this interface." on this interface."
::= { mplsLcAtmStdInterfaceConfEntry 3 } ::= { mplsLcAtmStdInterfaceConfEntry 3 }
mplsLcAtmStdUnlabTrafVci OBJECT-TYPE mplsLcAtmStdUnlabTrafVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VCI value over which this "This is the VCI value over which this
LSR is willing to accept unlabled traffic LSR is willing to accept unlabeled traffic
on this interface." on this interface."
::= { mplsLcAtmStdInterfaceConfEntry 4 } ::= { mplsLcAtmStdInterfaceConfEntry 4 }
mplsLcAtmStdVcMerge OBJECT-TYPE mplsLcAtmStdVcMerge OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If set to true(1), indicates that this interface "If set to true(1), indicates that this interface
is capabile of ATM VC merge, otherwise it MUST is capable 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 }
mplsLcAtmVcDirectlyConnected OBJECT-TYPE mplsLcAtmVcDirectlyConnected OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether an LC-ATM is directly "This value indicates whether an LC-ATM is directly
or indirectly (by means of a VP) connected. If set to or indirectly (by means of a VP) connected. If set to
true(1), indicates that this interface is directly true(1), indicates that this interface is directly
connected LC-ATM, otherwise it MUST be set to connected LC-ATM; otherwise, it MUST be set to
false(2). It should be noted that although false(2). Note that although it can be intimated
it can be intimated from RFC 3057 that multiple from RFC 3057 that multiple VPs may be used,
VPs maybe used, that in practice only a single in practice only a single one is used, and therefore
one is used, and therefore the authors of the authors of this MIB module have chosen to model
this MIB module have chosen to model it as such." it as such."
DEFVAL { true } DEFVAL { true }
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
::= { mplsLcAtmStdInterfaceConfEntry 6 } ::= { mplsLcAtmStdInterfaceConfEntry 6 }
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 [RFC3035]). 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 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
ifEntry and mplsInterfaceConfEntry ifEntry and mplsInterfaceConfEntry
MUST exist before hand. If an entry is attempted MUST exist beforehand. If a manager attempts to
to be created by a manager for a corresponding create an entry 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 except to mplsLcAtmStdIfConfRowStatus and
mplsLcAtmStdIfConfStorageType." mplsLcAtmStdIfConfStorageType."
::= { mplsLcAtmStdInterfaceConfEntry 8 } ::= { mplsLcAtmStdInterfaceConfEntry 8 }
mplsLcAtmStdIfConfStorageType OBJECT-TYPE mplsLcAtmStdIfConfStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
DEFVAL { nonVolatile } 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 }
skipping to change at page 11, line 4 skipping to change at page 10, line 29
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLcAtmStdModuleReadOnlyCompliance MODULE-COMPLIANCE mplsLcAtmStdModuleReadOnlyCompliance 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.
" "
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcAtmStdIfGroup mplsLcAtmStdIfGroup
} }
-- mplsLcAtmStdInterfaceConfTable -- mplsLcAtmStdInterfaceConfTable
OBJECT mplsLcAtmStdCtrlVpi OBJECT mplsLcAtmStdCtrlVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 12, line 4 skipping to change at page 11, line 29
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."
OBJECT mplsLcAtmStdIfConfStorageType OBJECT mplsLcAtmStdIfConfStorageType
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
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,
skipping to change at page 12, line 30 skipping to change at page 12, line 6
mplsLcAtmVcDirectlyConnected, mplsLcAtmVcDirectlyConnected,
mplsLcAtmLcAtmVPI, mplsLcAtmLcAtmVPI,
mplsLcAtmStdIfConfRowStatus, mplsLcAtmStdIfConfRowStatus,
mplsLcAtmStdIfConfStorageType mplsLcAtmStdIfConfStorageType
} }
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
8. MPLS Label Controlled Frame Relay MIB Definitions 8. MPLS Label-Controlled Frame Relay MIB Definitions
The following MIB module imports from [RFC2115], The following MIB module imports from [RFC2115], [RFC3811], and
[RFC3811], [RFC3813]. [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 FROM MPLS-LSR-STD-MIB
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB FROM FRAME-RELAY-DTE-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
; ;
mplsLcFrStdMIB MODULE-IDENTITY mplsLcFrStdMIB MODULE-IDENTITY
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
LAST-UPDATED "200506171200Z" -- 17 June 2005 12:00:00 GMT LAST-UPDATED "200601120000Z" -- 12 January 2006
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 module 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 (2006). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFC 4368; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200506171200Z" -- 17 June 2005 12:00:00 GMT "200601120000Z" -- 12 January 2006
DESCRIPTION DESCRIPTION
"Initial draft revision." "Initial revision, published as part of RFC 4368."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA ::= { mplsStdMIB 10 }
-- Top level components of this MIB module. -- 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
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 extends the MPLS-LSR-STD-MIB's this table sparsely extends the MPLS-LSR-STD-MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcFrStdObjects 1 } ::= { mplsLcFrStdObjects 1 }
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
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.
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 exists. If the associated entries in ifTable and
mplsInterfaceConfTable are deleted, the corresponding mplsInterfaceConfTable are deleted, the corresponding
entry in this table must also be deleted shortly entry in this table must also be deleted shortly
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcFrStdInterfaceConfTable 1 } ::= { mplsLcFrStdInterfaceConfTable 1 }
MplsLcFrStdInterfaceConfEntry ::= SEQUENCE { MplsLcFrStdInterfaceConfEntry ::= SEQUENCE {
mplsLcFrStdTrafficMinDlci DLCI, mplsLcFrStdTrafficMinDlci DLCI,
mplsLcFrStdTrafficMaxDlci DLCI, mplsLcFrStdTrafficMaxDlci DLCI,
mplsLcFrStdCtrlMinDlci DLCI, mplsLcFrStdCtrlMinDlci DLCI,
skipping to change at page 15, line 4 skipping to change at page 14, line 30
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the max DLCI value over which this "This is the max DLCI value over which this
LSR is willing to accept traffic on this LSR is willing to accept traffic on this
interface." interface."
::= { mplsLcFrStdInterfaceConfEntry 2 } ::= { mplsLcFrStdInterfaceConfEntry 2 }
mplsLcFrStdCtrlMinDlci OBJECT-TYPE mplsLcFrStdCtrlMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the min DLCI value over which this "This is the min DLCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
::= { mplsLcFrStdInterfaceConfEntry 3 } ::= { mplsLcFrStdInterfaceConfEntry 3 }
mplsLcFrStdCtrlMaxDlci OBJECT-TYPE mplsLcFrStdCtrlMaxDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 15, line 28 skipping to change at page 15, line 4
"This is the max DLCI value over which this "This is the max DLCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
::= { mplsLcFrStdInterfaceConfEntry 4 } ::= { mplsLcFrStdInterfaceConfEntry 4 }
mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is object is used to create and "This 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 ifEntry and entries in this table, the corresponding ifEntry and
mplsInterfaceConfEntry MUST exist before hand. If an entry mplsInterfaceConfEntry MUST exist beforehand. If a manager
is attempted to be created by a manager for a corresponding attempts to create an entry 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 except to mplsLcFrStdInterfaceConfRowStatus and
mplsLcFrStdInterfaceConfStorageType." mplsLcFrStdInterfaceConfStorageType."
::= { mplsLcFrStdInterfaceConfEntry 5 } ::= { mplsLcFrStdInterfaceConfEntry 5 }
mplsLcFrStdInterfaceConfStorageType OBJECT-TYPE mplsLcFrStdInterfaceConfStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
::= { 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 17, line 4 skipping to change at page 16, line 29
-- 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.
" "
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcFrStdIfGroup mplsLcFrStdIfGroup
} }
-- mplsLcFrStdInterfaceConfTable -- mplsLcFrStdInterfaceConfTable
OBJECT mplsLcFrStdTrafficMinDlci OBJECT mplsLcFrStdTrafficMinDlci
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 18, line 4 skipping to change at page 17, line 30
-- Units of conformance. -- Units of conformance.
mplsLcFrStdIfGroup OBJECT-GROUP mplsLcFrStdIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcFrStdTrafficMinDlci, mplsLcFrStdTrafficMinDlci,
mplsLcFrStdTrafficMaxDlci, mplsLcFrStdTrafficMaxDlci,
mplsLcFrStdCtrlMinDlci, mplsLcFrStdCtrlMinDlci,
mplsLcFrStdCtrlMaxDlci, mplsLcFrStdCtrlMaxDlci,
mplsLcFrStdInterfaceConfRowStatus, mplsLcFrStdInterfaceConfRowStatus,
mplsLcFrStdInterfaceConfStorageType mplsLcFrStdInterfaceConfStorageType
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
} }
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
9. Authors' Addresses
Thomas D. Nadeau Subrahmanya Hegde END
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
10. 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.
11. Acknowledgments 9. Acknowledgments
We wish to thank Joan Cucchiara and Carlos Pignataro for We wish to thank Joan Cucchiara and Carlos Pignataro for their
their comments on this document. comments on this document.
12. Security Considerations 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 MPLS LSRs supporting LC-ATM and/or LC-FR. These MIBs can
MIB can also be used for configuration of certain objects, and also be used for configuration of certain objects, and anything that
anything that can be configured can be incorrectly configured, can be configured can be incorrectly configured, with potentially
with potentially disastrous results. 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
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
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 that
contain objects which may be used to provision MPLS LC or may be used to provision MPLS LC or FR-enabled interfaces.
FR-enabled interfaces. Unauthorized access to objects in Unauthorized access to objects in these tables could result in
these tables, could result in disruption of traffic on the disruption of traffic on the network. This is especially true
network. This is especially true if traffic has been if traffic has been established over these interfaces. The use
established over these interfaces. The use of stronger of stronger mechanisms such as SNMPv3 security should be
mechanisms such as SNMPv3 security should be considered considered where possible. Specifically, SNMPv3 VACM and USM
where possible. Specifically,SNMPv3 VACM and USM MUST be MUST be used with any v3 agent that implements this MIB module.
used with any v3 agent which implements this MIB module. Administrators should consider whether read access to these
Administrators should consider whether read access to objects should be allowed, since read access may be undesirable
these objects should be allowed, since read access may be under certain circumstances.
undesirable under certain circumstances.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the MplsLcAtmStdInterfaceConfTable and o the MplsLcAtmStdInterfaceConfTable and
mplsLcFrStdInterfaceConfTable collectively mplsLcFrStdInterfaceConfTable collectively show the LC-ATM
collectively show the LC-ATM and/or LC-FR interfaces, and/or LC-FR interfaces, their associated configurations, and
their associated configurations and their linkages to other their linkages to other MPLS-related configuration and/or
MPLS-related configuration and/or performanc statistics. performance statistics. Administrators not wishing to reveal
Administrators not wishing to reveal this information should this information should consider these objects
consider these objects sensitive/vulnerable and take sensitive/vulnerable and take precautions so they are not
precautions so they are not revealed. revealed.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005
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
to the objects only to those principals (users) that have legitimate 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.
13. IANA Considerations 11. IANA Considerations
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].
13.1. IANA Considerations for MPLS-LC-ATM-STD-MIB 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
requested from IANA a new assignment under the mplsStdMIB subtree.
New assignments can only be made via a Standards Action as specified
in [RFC2434].
The IANA is requested to assign { mplsStdMIB 9 } to the 11.1. IANA Considerations for MPLS-LC-ATM-STD-MIB
MPLS-LC-ATM-STD-MIB module specified in this document.
13.2. IANA Considerations for MPLS-LC-FR-STD-MIB The IANA has assigned { mplsStdMIB 9 } to the MPLS-LC-ATM-STD-MIB
module specified in this document.
The IANA is requested to assign { mplsStdMIB 10 } to the 11.2. IANA Considerations for MPLS-LC-FR-STD-MIB
MPLS-LC-FR-STD-MIB module specified in this document.
14. References The IANA has assigned { mplsStdMIB 10 } to the MPLS-LC-FR-STD-MIB
module specified in this document.
14.1 Normative References 12. References
[RFC3034] Conta, A., Doolan, P., Malis, A., "Use 12.1. Normative References
of Label Switching on Frame Relay Networks
Specification", Rfc3034, JANUARY 2001.
[RFC3035] Davie, B., mcCloghhrie, K., Rosen., E., Swallow, G., [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label
Rekhter, Y., Doolan, P., "MPLS using LDP and ATM VC Switching on Frame Relay Networks Specification", RFC
Switching", RFC3035, January 2001. 3034, January 2001.
[RFC2115] Brown, C., Baker, F., "Management Information Base [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E.,
for Frame Relay DTEs Using SMIv2", RFC2115, September Swallow, G., Rekhter, Y., and P. Doolan, "MPLS using LDP
1997. and ATM VC Switching", RFC 3035, January 2001.
[RFC2514] Noto, M., Spiegel, E., Tesink, K., et al., "Definitions [RFC2115] Brown, C. and F. Baker, "Management Information Base for
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
of Textual Conventions and OBJECT-IDENTITIES for ATM [RFC2514] Noto, M., Spiegel, E., and K. Tesink, "Definitions 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
Group MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
"Multiprotocol Label Switching Architecture", RFC Label Switching Architecture", RFC 3031, January 2001.
3031, January 2001.
[RFC3811] Nadeau, T., Cucchiara, J., Editors, [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual
"Definition of Textual Conventions and OBJECT- Conventions (TCs) for Multiprotocol Label Switching
IDENTITIES for Multi-Protocol Label Switching (MPLS) (MPLS) Management", RFC 3811, June 2004.
Management", RFC3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Traffic Engineering Management Information Base ", "Multiprotocol Label Switching (MPLS) Traffic Engineering
RFC3812, June 2004. (TE) Management Information Base (MIB)", RFC 3812, June
2004.
[RFC3813] Srinivasan, C., Viswanathan, A. and T. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Nadeau, "MPLS Multiprotocol Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(MPLS) Label Switch Router Management Router (LSR) Management Information Base (MIB)", RFC
Information Base ", RFC3813, June 2004. 3813, June 2004.
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
J., Rose, M., and S. Waldbusser, "Structure of Rose, M., and S. Waldbusser, "Structure of Management
Management Information Version 2 (SMIv2)", STD 58, RFC Information Version 2 (SMIv2)", STD 58, RFC 2578, April
2578, April 1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
J., Rose, M., and S. Waldbusser, "Textual Conventions Rose, M., and S. Waldbusser, "Textual Conventions for
for SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
J., Rose, M., and S. Waldbusser, "Conformance Rose, M., and S. Waldbusser, "Conformance Statements for
Statements for SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
14.2 Informative References 12.2. Informative References
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3815] J. Cucchiara, et al., "Definitions of [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani,
Managed Objects for the Multiprotocol Label "Definitions of Managed Objects for the Multiprotocol
Switching, Label Distribution Protocol Label Switching (MPLS), Label Distribution Protocol
(LDP)", RFC3815, June 2004. (LDP)", RFC3815, June 2004.
15. Intellectual Property Authors' Addresses
Thomas D. Nadeau
Cisco Systems, Inc.
300 Beaver Brook Road
Boxboro, MA 01719
Phone: +1-978-936-1470
EMail: tnadeau@cisco.com
Subrahmanya Hegde
Cisco Systems, Inc.
225 East Tazman Drive
San Jose, CA 95134
Phone: +1-408-525-6562
EMail: subrah@cisco.com
Full Copyright Statement
Copyright (C) The Internet Society (2006).
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.
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
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 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
ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 107 change blocks. 
343 lines changed or deleted 281 lines changed or added

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