draft-ietf-mpls-te-mib-06.txt   draft-ietf-mpls-te-mib-07.txt 
Network Working Group Cheenu Srinivasan Network Working Group Cheenu Srinivasan
Internet Draft Tachion Networks, Inc. Internet Draft Alphion Corp.
Expires: September 2001 Expires: February 2002
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
March 2, 2001 August 2001
MPLS Traffic Engineering Management Information Base Using Multiprotocol Label Switching (MPLS) Traffic Engineering
SMIv2 Management Information Base
draft-ietf-mpls-te-mib-06.txt draft-ietf-mpls-te-mib-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document is an Internet-Draft and is in full
conformance with all provisions of Section 10 of RFC2026. conformance with all provisions of Section 10 of RFC 2026
[RFC2026].
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by six months and may be updated, replaced, or obsoleted by
other documents at any time. It is inappropriate to use other documents at any time. It is inappropriate to use
Internet-Drafts as reference material or to cite them other Internet-Drafts as reference material or to cite them other
than as "work in progress." than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be The list of Internet-Draft Shadow Directories can be
accessed at http://www.ietf.org/shadow.html. accessed at http://www.ietf.org/shadow.html.
Table of Contents
Abstract ................................................ 2
1. Introduction ......................................... 2
2. Terminology .......................................... 2
3. The SNMP Management Framework ........................ 3
4. Feature List ......................................... 4
5. Outline .............................................. 4
5.1. Summary of Traffic Engineering MIB ................ 5
6. Brief Description of MIB Objects ..................... 5
6.1. mplsTunnelTable ................................... 5
6.2. mplsTunnelResourceTable ........................... 6
6.3. mplsTunnelHopTable ................................ 6
6.4. mplsTunnelARHopTable .............................. 6
6.5. mplsTunnelCHoptable ............................... 6
6.6. mplsTunnelPerfTable ............................... 6
6.7. mplsTunnelCRLDPResTable ........................... 7
7. Application of the Interface Group to MPLS Tunnels ... 7
7.1. Support of the MPLS Tunnel Interface by ifTable ... 8
8. Example of Tunnel Setup .............................. 9
9. The Use of RowPointer ............................... 11
10. MPLS Traffic Engineering MIB Definitions ........... 11
11. Security Considerations ............................ 60
12. Acknowledgments .................................... 61
13. References ......................................... 61
14. Authors' Addresses ................................. 64
15. Full Copyright Statement ........................... 64
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management Information Base (MIB) for use with network management
protocols in the Internet community. In particular, it protocols in the Internet community. In particular, it
describes managed objects for Multi-Protocol Label describes managed objects for Multi-Protocol Label
Switching (MPLS) [MPLSArch] based traffic engineering. Switching (MPLS) [RFC3031] based traffic engineering.
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management Information Base (MIB) for use with network management
protocols in the Internet community. In particular, it protocols in the Internet community. In particular, it
describes managed objects for modeling a Multi-Protocol describes managed objects for modeling a Multi-Protocol
Label Switching (MPLS) [MPLSArch] based traffic Label Switching (MPLS) [RFC3031] based traffic engineering.
engineering. This MIB should be used in conjunction with This MIB should be used in conjunction with the companion
the companion document [LSRMIB] for MPLS based traffic document [LSRMIB] for MPLS based traffic engineering
engineering configuration and management. configuration and management.
Comments should be made directly to the MPLS mailing list Comments should be made directly to the MPLS mailing list
at mpls@uu.net. at mpls@uu.net.
This memo does not, in its draft form, specify a standard This memo does not, in its draft form, specify a standard
for the Internet community. for the Internet community.
2. Terminology 2. Terminology
This document uses terminology from the MPLS architecture This document uses terminology from the MPLS architecture
document [MPLSArch] and MPLS Label Switch Router MIB document [RFC3031] and MPLS Label Switch Router MIB
[LSRMIB]. Some frequently used terms are described next. [LSRMIB]. Some frequently used terms are described next.
An explicitly routed LSP (ERLSP) is referred to as an MPLS An explicitly routed LSP (ERLSP) is referred to as an MPLS
tunnel. It consists of one in-segment and/or one out- tunnel. It consists of one in-segment and/or one out-
segment at the ingress/egress LSRs, each segment being segment at the ingress/egress LSRs, each segment being
associated with one MPLS interface. These are also associated with one MPLS interface. These are also
referred to as tunnel segments. Additionally, at an referred to as tunnel segments. Additionally, at an
intermediate LSR, we model a connection as consisting of intermediate LSR, we model a connection as consisting of
one or more in-segments and/or one or more out-segments. one or more in-segments and/or one or more out-segments.
The binding or interconnection between in-segments and out- The binding or interconnection between in-segments and out-
segments in performed using a cross-connect. These objects segments in performed using a cross-connect. These objects
are defined in the MPLS Label Switch Router MIB [LSRMIB]. are defined in the MPLS Label Switch Router MIB [LSRMIB].
3. The SNMP Management Framework 3. The SNMP Management Framework
The SNMP Management Framework presently consists of five The SNMP Management Framework presently consists of five
major components: major components:
- An overall architecture, described in RFC 2271 - An overall architecture, described in RFC 2571
[SNMPArch]. [RFC2571].
- Mechanisms for describing and naming objects and events - Mechanisms for describing and naming objects and events
for the purpose of management. The first version of for the purpose of management. The first version of
this Structure of Management Information (SMI) is this Structure of Management Information (SMI) is
called SMIv1 and described in RFC 1155 [SMIv1], RFC called SMIv1 and described in STD 16, RFC 1155
1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, RFC
second version, called SMIv2, is described in RFC 1902 1215 [RFC1215]. The second version, called SMIv2, is
[SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. described in STD 58, RFC 2578 [RFC2578], STD 58, RFC
2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management - Message protocols for transferring management
information. The first version of the SNMP message information. The first version of the SNMP message
protocol is called SNMPv1 and described in RFC 1157 protocol is called SNMPv1 and described in STD 15, RFC
[SNMPv1]. A second version of the SNMP message 1157 [RFC1157]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 protocol, is called SNMPv2c and described in RFC 1901
[SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version [RFC1901] and RFC 1906 [RFC1906]. The third version of
of the message protocol is called SNMPv3 and described the message protocol is called SNMPv3 and described in
in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
2574 [SNMPv3USM]. [RFC2574].
- Protocol operations for accessing management - Protocol operations for accessing management
information. The first set of protocol operations and information. The first set of protocol operations and
associated PDU formats is described in RFC 1157 associated PDU formats is described in STD 15, RFC 1157
[SNMPv1]. A second set of protocol operations and [RFC1157]. A second set of protocol operations and
associated PDU formats is described in RFC 1905 associated PDU formats is described in RFC 1905
[SNMPv2PO]. [RFC1905].
- A set of fundamental applications described in RFC 2273 - A set of fundamental applications described in RFC 2573
[SNMPv3App] and the view-based access control mechanism [RFC2573] and the view-based access control mechanism
described in RFC 2575 [SNMPv3VACM]. 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 Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB. store, termed the Management Information Base or MIB.
Objects in the MIB are defined using the mechanisms defined Objects in the MIB are defined using the mechanisms defined
in the SMI. This memo specifies a MIB module that is in the SMI.
compliant to the SMIv2. A MIB conforming to the SMIv1 can
be produced through the appropriate translations. The
resulting translated MIB must be semantically equivalent,
except where objects or events are omitted because no
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.
3.1. Object Definitions
Managed objects are accessed via a virtual information This memo specifies a MIB module that is compliant to the
store, termed the Management Information Base or MIB. SMIv2. A MIB conforming to the SMIv1 can be produced
Objects in the MIB are defined using the subset of Abstract through the appropriate translations. The resulting
Syntax Notation One (ASN.1) defined in the SMI. In translated MIB must be semantically equivalent, except
particular, each object type is named by an OBJECT where objects or events are omitted because no translation
IDENTIFIER, an administratively assigned name. The object is possible (use of Counter64). Some machine-readable
type together with an object instance serves to uniquely information in SMIv2 will be converted into textual
identify a specific instantiation of the object. For human descriptions in SMIv1 during the translation process.
convenience, we often use a textual string, termed the However, this loss of machine-readable information is not
descriptor, to also refer to the object type. considered to change the semantics of the MIB.
4. Feature List 4. Feature List
The MPLS traffic engineering MIB is designed to satisfy the The MPLS traffic engineering MIB is designed to satisfy the
following requirements and constraints. following requirements and constraints.
- The MIB supports configuration of point-to-point - The MIB supports configuration of point-to-point
unidirectional tunnels. unidirectional tunnels.
- MPLS tunnels need not be interfaces, but it is possible - MPLS tunnels need not be interfaces, but it is possible
to configure a tunnel as an interface. to configure a tunnel as an interface.
- The MIB supports manually configured MPLS tunnels as - The MIB supports manually configured MPLS tunnels as
well as those set up via any MPLS signaling protocol. well as those set up via an MPLS signaling protocol.
- The MIB supports persistent as well as non-persistent - The MIB supports persistent as well as non-persistent
tunnels. tunnels.
5. Outline 5. Outline
Traffic engineering support for MPLS tunnels requires the Traffic engineering support for MPLS tunnels requires the
following configuration. following configuration.
- Setting up MPLS tunnels along with appropriate - Setting up MPLS tunnels along with appropriate
skipping to change at page 4, line 50 skipping to change at page 5, line 23
The MIB objects for performing these actions consist of the The MIB objects for performing these actions consist of the
following tables. following tables.
- Tunnel table (mplsTunnelTable) for setting up MPLS - Tunnel table (mplsTunnelTable) for setting up MPLS
tunnels. tunnels.
- Resource table (mplsTunnelResourceTable) for setting up - Resource table (mplsTunnelResourceTable) for setting up
the tunnel resources. the tunnel resources.
- Tunnel specified, actual, and computed hop tables
(mplsTunnelHopTable, mplsTunnelARHopTable, and
mplsTunnelCHopTable) for strict and loose source routed
MPLS tunnel hops.
- CRLDP resource table (mplsTunnelCRLDPResTable) for - CRLDP resource table (mplsTunnelCRLDPResTable) for
specifying resource objects applicable to tunnels specifying resource objects applicable to tunnels
signaled using CRLDP. signaled using CRLDP.
- Tunnel hop table (mplsTunnelHopTable) for configuring These tables are described in the subsequent sections.
strict and loose source routed MPLS tunnels hops.
When a tunnel is signaled via a MPLS signaling protocol,
the mplsTunnelARHopTable gives the actual list of hops
traversed by the tunnel as reported by the signaling
protocol. These tables are described in the subsequent
sections.
6. Brief Description of MIB Objects 6. Brief Description of MIB Objects
The objects described in this section support the The objects described in this section support the
functionality described in documents [RSVPTun][CR-LDP]. functionality described in documents [RSVPTE] and [CRLDP].
The tables support both manually configured and signaled The tables support both manually configured and signaled
tunnels. tunnels.
6.1. mplsTunnelTable 6.1. mplsTunnelTable
The mplsTunnelTable allows new MPLS tunnels to be created The mplsTunnelTable allows new MPLS tunnels to be created
between an MPLS LSR and a remote endpoint, and existing between an MPLS LSR and a remote endpoint, and existing
tunnels to be reconfigured or removed. Note that we only tunnels to be reconfigured or removed. Note that we only
support point-to-point tunnel segments, although multi- support point-to-point tunnel segments, although multi-
point-to-point and point-to-multi-point connections are point-to-point and point-to-multi-point connections are
skipping to change at page 6, line 31 skipping to change at page 7, line 4
6.5. mplsTunnelCHoptable 6.5. mplsTunnelCHoptable
mplsTunnelCHopTable lists the actual hops computed by a mplsTunnelCHopTable lists the actual hops computed by a
constraint-based routing algorithm based on the constraint-based routing algorithm based on the
mplsTunnelHopTable. The support of this table is optional mplsTunnelHopTable. The support of this table is optional
since not all implementations may support computation of since not all implementations may support computation of
hop list using a constraint-based routing protocol. hop list using a constraint-based routing protocol.
6.6. mplsTunnelPerfTable 6.6. mplsTunnelPerfTable
mplsTunnelPerfTable provides several counters to measure mplsTunnelPerfTable provides several counters to measure
the performance of the MPLS tunnels. This table auguments the performance of the MPLS tunnels. This table augments
mplsTunnelTable. mplsTunnelTable.
6.7. mplsTunnelCRLDPResTable 6.7. mplsTunnelCRLDPResTable
mplsTunnelCRLDPResTable contains resource information for mplsTunnelCRLDPResTable contains resource information for
those tunnels that are signaled using CRLDP. This is a those tunnels that are signaled using CRLDP [CRLDP]. This
sparse extension to mplsTunnelResourceTable and is also is a sparse extension to mplsTunnelResourceTable and is
indexed by mplsTunnelResourceIndex. As with also indexed by mplsTunnelResourceIndex. As with
mplsTunnelResourceTable, multiple tunnels may share the mplsTunnelResourceTable, multiple tunnels may share the
same resources by pointing to the same entry in this table. same resources by pointing to the same entry in this table.
Tunnels that do not share resources must point to separate Tunnels that do not share resources must point to separate
entries in this table. entries in this table.
7. Application of the Interface Group to MPLS Tunnels 7. Application of the Interface Group to MPLS Tunnels
The Interfaces Group of MIB II defines generic managed The Interfaces Group of MIB II defines generic managed
objects for managing interfaces. This memo contains the objects for managing interfaces. This memo contains the
media-specific extensions to the Interfaces Group for media-specific extensions to the Interfaces Group for
managing MPLS Tunnels as logical interfaces. managing MPLS Tunnels as logical interfaces.
This memo assumes the interpretation of the Interfaces This memo assumes the interpretation of the Interfaces
Group to be in accordance with [IFMIB] which states that Group to be in accordance with [RFC2233] which states that
the interfaces table (ifTable) contains information on the the interfaces table (ifTable) contains information on the
managed resource's interfaces and that each sub-layer below managed resource's interfaces and that each sub-layer below
the internetwork layer of a network interface is considered the internetwork layer of a network interface is considered
an interface. Thus, the MPLS interface is represented as an interface. Thus, the MPLS interface is represented as
an entry in the ifTable. The interrelation of entries in an entry in the ifTable. The interrelation of entries in
the ifTable is defined by Interfaces Stack Group defined in the ifTable is defined by the Interfaces Stack Group
[IFMIB]. defined in [RFC2233].
When using MPLS Tunnels as interfaces, the interface stack When using MPLS Tunnels as interfaces, the interface stack
table might appear as follows: table might appear as follows:
+------------------------------------------------+ +------------------------------------------------+
| MPLS-Tunnel-interface ifType = mplsTunnel(150) | | MPLS tunnel interface ifType = mplsTunnel(150) |
+------------------------------------------------+ +------------------------------------------------+
| MPLS-interface ifType = mpls(166) | | MPLS interface ifType = mpls(166) |
+------------------------------------------------+ +------------------------------------------------+
| Underlying Layer | | Underlying layer |
+------------------------------------------------+ +------------------------------------------------+
In the above diagram, "Underlying Layer" refers to the In the above diagram, "Underlying Layer" refers to the
ifIndex of any interface type, which has been defined for ifIndex of any interface type, which has been defined for
MPLS interworking. Examples include ATM, Frame Relay, MPLS interworking. Examples include ATM, Frame Relay, and
Ethernet, etc. Ethernet.
7.1. Support of the MPLS Tunnel Interface by ifTable 7.1. Support of the MPLS Tunnel Interface by ifTable
Some specific interpretations of ifTable for those MPLS Some specific interpretations of ifTable for those MPLS
tunnels represented as interfaces follow: tunnels represented as interfaces follow:
Object Use for the MPLS tunnel. Object Use for the MPLS tunnel.
ifIndex Each MPLS tunnel is represented by an ifIndex Each MPLS tunnel is represented by an
ifEntry. ifEntry.
skipping to change at page 8, line 7 skipping to change at page 8, line 26
ifDescr Description of the MPLS tunnel. ifDescr Description of the MPLS tunnel.
ifType The value that is allocated for MPLS ifType The value that is allocated for MPLS
tunnel is 150. tunnel is 150.
ifSpeed The total bandwidth in bits per second ifSpeed The total bandwidth in bits per second
for use by the MPLS tunnel. for use by the MPLS tunnel.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus See [IFMIB]. ifAdminStatus See [RFC2233].
ifOperStatus Assumes the value down(2) if the MPLS ifOperStatus Assumes the value down(2) if the MPLS
tunnel is down. tunnel is down.
ifLastChange See [IFMIB]. ifLastChange See [RFC2233].
ifInOctets The number of octets received over the ifInOctets The number of octets received over the
MPLS tunnel. MPLS tunnel.
ifOutOctets The number of octets transmitted over ifOutOctets The number of octets transmitted over
the MPLS tunnel. the MPLS tunnel.
ifInErrors The number of labeled packets dropped ifInErrors The number of labeled packets dropped
due to uncorrectable errors. due to uncorrectable errors.
ifInUnknownProtos The number of received packets ifInUnknownProtos The number of received packets
discarded during packet header discarded during packet header
validation, including packets with validation, including packets with
unrecognized label values. unrecognized label values.
ifOutErrors See [IFMIB]. ifOutErrors See [RFC2233].
ifName Textual name (unique on this system) of ifName Textual name (unique on this system) of
the MPLS tunnel or an octet string of the MPLS tunnel or an octet string of
zero length. zero length.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Default is disabled (2). Default is disabled (2).
ifConnectorPresent Set to false (2). ifConnectorPresent Set to false (2).
ifHighSpeed See [IFMIB]. ifHighSpeed See [RFC2233].
ifHCInOctets The 64-bit version of ifInOctets; ifHCInOctets The 64-bit version of ifInOctets;
supported if required by the compliance supported if required by the compliance
statements in [IFMIB]. statements in [RFC2233].
ifHCOutOctets The 64-bit version of ifOutOctets; ifHCOutOctets The 64-bit version of ifOutOctets;
supported if required by the compliance supported if required by the compliance
statements in [IFMIB]. statements in [RFC2233].
ifAlias The non-volatile 'alias' name for the ifAlias The non-volatile 'alias' name for the
MPLS tunnel as specified by a network MPLS tunnel as specified by a network
manager. manager.
8. Example of Tunnel Setup 8. Example of Tunnel Setup
This section contains an example of which MIB objects This section contains an example of which MIB objects
should be modified if one would like to create a best should be modified if one would like to create a best
effort, loosely routed, unidirectional traffic engineered effort, loosely routed, unidirectional traffic engineered
skipping to change at page 10, line 41 skipping to change at page 11, line 11
mplsTunnelHopType = loose (2), mplsTunnelHopType = loose (2),
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
9. The Use of RowPointer 9. The Use of RowPointer
RowPointer is a textual convention used to identify a RowPointer is a textual convention used to identify a
conceptual row in an SNMP Table by pointing to one of its conceptual row in an SNMP Table by pointing to one of its
objects. In this MIB, in mplsTunnelTable, the objects objects. In this MIB, in mplsTunnelTable, the objects
mplsTunnelXCPointer and mplsTunnelResourcePointer are of mplsTunnelXCPointer and mplsTunnelResourcePointer are of
type RowPointer. The object mplsTunnelXCPointer points to a type RowPointer. The object mplsTunnelXCPointer points to
specific entry in the mplsXCTable [LSRMIB]. This entry in a specific entry in the mplsXCTable [LSRMIB]. This entry
the mplsXCTable is the associated LSP for the given MPLS in the mplsXCTable is the associated LSP for the given MPLS
tunnel entry. The object mplsTunnelResourcePointer points tunnel entry. The object mplsTunnelResourcePointer points
to a specific entry in a traffic parameter table. An to a specific entry in a traffic parameter table. An
example of such a traffic parameter table is example of such a traffic parameter table is
mplsTunnelResourceTable. It indicates a specific instance mplsTunnelResourceTable. It indicates a specific instance
of a traffic parameter entry that is associated with a of a traffic parameter entry that is associated with a
given MPLS tunnel entry. given MPLS tunnel entry.
10. MPLS Traffic Engineering MIB Definitions 10. MPLS Traffic Engineering MIB Definitions
MPLS-TE-MIB DEFINITIONS ::= BEGIN MPLS-TE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Integer32, Unsigned32, Counter32, experimental, Integer32, Unsigned32, Counter32,
Counter64, TimeTicks, TimeStamp Counter64, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer, TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer,
StorageType, DisplayString StorageType, DisplayString, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
MplsBitRate, MplsBurstSize, MplsLSPID,
MplsBitRate, MplsBurstSize, MplsLSPID MplsTunnelIndex, MplsTunnelInstanceIndex,
FROM MPLS-LSR-MIB MplsTunnelAffinity, MplsLsrIdentifier, MplsPathIndex,
MplsPathIndexOrZero
FROM MPLS-TC-MIB
InetAddressIPv4, InetAddressIPv6 InetAddressIPv4, InetAddressIPv6
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB
;
mplsTeMIB MODULE-IDENTITY mplsTeMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200103021200Z" -- March 2, 2001 12:00:00 EST "200108241200Z" -- August 24, 2001 12:00:00 GMT
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Cheenu Srinivasan "
Postal: Tachion Networks, Inc. Cheenu Srinivasan
Monmouth Park Corporate Center I Postal: Alphion Corp.
Building C, 185 Monmouth Park Highway 4 Industrial Way West
West Long Branch, NJ 07764 Eatontown, NJ 07724
Tel: +1-732-542-7750 x1234 Tel: +1-732-676-7066
Email: cheenu@tachion.com Email: cheenu@alphion.com
Arun Viswanathan Arun Viswanathan
Postal: Force10 Networks, Inc. Postal: Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
Tel: +1-408-571-3516 Tel: +1-408-571-3516
Email: arun@force10networks.com Email: arun@force10networks.com
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
"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions "This MIB module contains managed object definitions
for MPLS Traffic Engineering (TE) as defined in: for MPLS Traffic Engineering (TE) as defined in:
Extensions to RSVP for LSP Tunnels, Awduche et al, 1. Extensions to RSVP for LSP Tunnels, Awduche et
Internet Draft <draft-ietf-mpls-rsvp-lsp-tunnel- al, Internet Draft <draft-ietf-mpls-rsvp-lsp-tunnel-
07.txt>, August 2000; Constraint-Based LSP Setup 08.txt>, February 2001
using LDP, B. Jamoussi, Internet Draft <draft-ietf- 2. Constraint-Based LSP Setup using LDP, B. Jamoussi
mpls-cr-ldp-04.txt>, July 2000; Requirements for (Editor), Internet Draft <draft-ietf-mpls-cr-ldp-
Traffic Engineering Over MPLS, Awduche, D., J. 05.txt>, February 2001
Malcolm, J., Agogbua, J., O'Dell, M., J. McManus, 3. Requirements for Traffic Engineering Over MPLS,
<rfc2702.txt>, September 1999." Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M.,
and J. McManus, RFC 2702, September 1999"
-- Revision history. -- Revision history.
REVISION REVISION
"200103021200Z" -- 2 March 2001 12:00:00 EST "200108241200Z" -- 24 August 2001 12:00:00 GMT
DESCRIPTION
"Removed SMIv2 from title. Upgraded SNMP boilerplate.
Updated references to reflect this change. Removed
TCs; Updated IMPORTS clause to import them from
MPLS TC MIB. Updated author contact information.
Introduced a TOC."
REVISION
"200103021200Z" -- 2 March 2001 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Updates based on MPLS WG last call feedback." "Updates based on MPLS WG last call feedback."
REVISION REVISION
"200011211200Z" -- 21 November 2000 12:00:00 EST "200011211200Z" -- 21 November 2000 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Updates based on MPLS WG feedback." "Updates based on MPLS WG feedback."
REVISION REVISION
"200007141200Z" -- 14 July 2000 12:00:00 EST "200007141200Z" -- 14 July 2000 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Updates based on MPLS WG feedback." "Updates based on MPLS WG feedback."
REVISION REVISION
"200005261200Z" -- 26 May 2000 12:00:00 EST "200005261200Z" -- 26 May 2000 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Updates based on MPLS WG feedback." "Updates based on MPLS WG feedback."
REVISION REVISION
"200003031200Z" -- 3 March 2000 12:00:00 EST "200003031200Z" -- 3 March 2000 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Updates based on MPLS WG feedback." "Updates based on MPLS WG feedback."
REVISION REVISION
"199907161200Z" -- 16 July 1999 12:00:00 EST "199907161200Z" -- 16 July 1999 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial draft version."
::= { experimental 95 } ::= { experimental 95 }
MplsTunnelIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Index into mplsTunnelTable."
SYNTAX Integer32 (1..65535)
MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Instance index into mplsTunnelTable."
SYNTAX Unsigned32 (0..65535)
MplsTunnelAffinity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Include-any, include-all, or exclude-all constraint
for link selection."
SYNTAX Unsigned32
MplsLsrId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier for an MPLS LSR. This MAY
represent an IpV4 address."
SYNTAX Unsigned32
MplsPathIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier used to identify a specific path
used by a tunnel."
SYNTAX Unsigned32
MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier used to identify a specific path
used by a tunnel. If this value is set to 0, it
indicates that no path is in use."
SYNTAX Unsigned32
-- Top level components of this MIB. -- Top level components of this MIB.
-- tables, scalars -- tables, scalars
mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 } mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 }
mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 } mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 }
-- traps -- traps
mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 3 } mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 3 }
mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 } mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 }
skipping to change at page 16, line 17 skipping to change at page 15, line 50
signaling protocol. Whenever a new entry is created signaling protocol. Whenever a new entry is created
with mplsTunnelIsIf set to true(1), then a with mplsTunnelIsIf set to true(1), then a
corresponding entry is created in ifTable as well corresponding entry is created in ifTable as well
(see RFC 2233). The ifType of this entry is (see RFC 2233). The ifType of this entry is
mplsTunnel(150)." mplsTunnel(150)."
REFERENCE REFERENCE
"1. RFC 2233 - The Interfaces Group MIB using SMIv2, "1. RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie, K., and F. Kastenholtz, Nov. 1997 McCloghrie, K., and F. Kastenholtz, Nov. 1997
2. RFC 1700 - Assigned Numbers, Reynolds, J. and J. 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J.
Postel, Oct. 1994" Postel, Oct. 1994"
INDEX { mplsTunnelIndex, mplsTunnelInstance, INDEX {
mplsTunnelIngressLSRId, mplsTunnelEgressLSRId mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
} }
::= { mplsTunnelTable 1 } ::= { mplsTunnelTable 1 }
MplsTunnelEntry ::= SEQUENCE { MplsTunnelEntry ::= SEQUENCE {
mplsTunnelIndex MplsTunnelIndex, mplsTunnelIndex MplsTunnelIndex,
mplsTunnelInstance MplsTunnelInstanceIndex, mplsTunnelInstance MplsTunnelInstanceIndex,
mplsTunnelIngressLSRId MplsLsrId, mplsTunnelIngressLSRId MplsLsrIdentifier,
mplsTunnelEgressLSRId MplsLsrId, mplsTunnelEgressLSRId MplsLsrIdentifier,
mplsTunnelName DisplayString, mplsTunnelName DisplayString,
mplsTunnelDescr DisplayString, mplsTunnelDescr DisplayString,
mplsTunnelIsIf TruthValue, mplsTunnelIsIf TruthValue,
mplsTunnelIfIndex InterfaceIndexOrZero, mplsTunnelIfIndex InterfaceIndexOrZero,
mplsTunnelXCPointer RowPointer, mplsTunnelXCPointer RowPointer,
mplsTunnelSignallingProto INTEGER, mplsTunnelSignallingProto INTEGER,
mplsTunnelSetupPrio INTEGER, mplsTunnelSetupPrio INTEGER,
mplsTunnelHoldingPrio INTEGER, mplsTunnelHoldingPrio INTEGER,
mplsTunnelSessionAttributes BITS, mplsTunnelSessionAttributes BITS,
mplsTunnelOwner INTEGER, mplsTunnelOwner INTEGER,
skipping to change at page 17, line 31 skipping to change at page 17, line 17
SYNTAX MplsTunnelInstanceIndex SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies an instance of a tunnel. It is "Uniquely identifies an instance of a tunnel. It is
useful to identify multiple instances of tunnels useful to identify multiple instances of tunnels
for the purposes of backup and parallel tunnels." for the purposes of backup and parallel tunnels."
::= { mplsTunnelEntry 2 } ::= { mplsTunnelEntry 2 }
mplsTunnelIngressLSRId OBJECT-TYPE mplsTunnelIngressLSRId OBJECT-TYPE
SYNTAX MplsLsrId SYNTAX MplsLsrIdentifier
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The purpose of this object is to uniquely identity a "The purpose of this object is to uniquely identity a
tunnel within a network. When the MPLS signalling tunnel within a network. When the MPLS signalling
protoocol is rsvp(2) this value should mimic the protoocol is rsvp(2) this value SHOULD mimic the
Extended Tunnel Id field in the Session object. Extended Tunnel Id field in the SESSION object.
When the MPLS signalling protoocol is crldp(3) this When the MPLS signalling protoocol is crldp(3) this
value should mimic the Ingress LSR Router ID field value SHOULD mimic the Ingress LSR Router ID field
in the LSPID TLV object." in the LSPID TLV object."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, Internet Draft <draft-ietf-mpls-rsvp- Awduche et al, Internet Draft <draft-ietf-mpls-rsvp-
lsp-tunnel-07.txt>, August 2000., lsp-tunnel-08.txt>, February 2001.,
2. Constraint-Based LSP Setup using LDP, Jamoussi, 2. Constraint-Based LSP Setup using LDP, Jamoussi,
Internet Draft <draft-ietf-mpls-cr-ldp-04.txt>, Internet Draft <draft-ietf-mpls-cr-ldp-05.txt>,
July 2000." February 2001."
::= { mplsTunnelEntry 3 } ::= { mplsTunnelEntry 3 }
mplsTunnelEgressLSRId OBJECT-TYPE mplsTunnelEgressLSRId OBJECT-TYPE
SYNTAX MplsLsrId SYNTAX MplsLsrIdentifier
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the egress LSR Id." "Specifies the egress LSR ID."
::= { mplsTunnelEntry 4 } ::= { mplsTunnelEntry 4 }
mplsTunnelName OBJECT-TYPE mplsTunnelName OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The canonical name assigned to the tunnel. This name "The canonical name assigned to the tunnel. This name
can be used to refer to the tunnel on the LSRĘs can be used to refer to the tunnel on the LSRĘs
console port. If mplsTunnelIsIf is set to true console port. If mplsTunnelIsIf is set to true
skipping to change at page 28, line 31 skipping to change at page 28, line 16
mplsTunnelHopEntry OBJECT-TYPE mplsTunnelHopEntry OBJECT-TYPE
SYNTAX MplsTunnelHopEntry SYNTAX MplsTunnelHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a tunnel hop. An "An entry in this table represents a tunnel hop. An
entry is created by a network administrator for entry is created by a network administrator for
signaled ERLSP set up by an MPLS signaling signaled ERLSP set up by an MPLS signaling
protocol." protocol."
INDEX { mplsTunnelHopListIndex, INDEX {
mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex } mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex,
mplsTunnelHopIndex
}
::= { mplsTunnelHopTable 1 } ::= { mplsTunnelHopTable 1 }
MplsTunnelHopEntry ::= SEQUENCE { MplsTunnelHopEntry ::= SEQUENCE {
mplsTunnelHopListIndex MplsPathIndex, mplsTunnelHopListIndex MplsPathIndex,
mplsTunnelHopPathOptionIndex MplsPathIndex, mplsTunnelHopPathOptionIndex MplsPathIndex,
mplsTunnelHopIndex MplsPathIndex, mplsTunnelHopIndex MplsPathIndex,
mplsTunnelHopAddrType INTEGER, mplsTunnelHopAddrType INTEGER,
mplsTunnelHopIpv4Addr InetAddressIPv4, mplsTunnelHopIpv4Addr InetAddressIPv4,
mplsTunnelHopIpv4PrefixLen Unsigned32, mplsTunnelHopIpv4PrefixLen Unsigned32,
mplsTunnelHopIpv6Addr InetAddressIPv6, mplsTunnelHopIpv6Addr InetAddressIPv6,
skipping to change at page 46, line 9 skipping to change at page 45, line 46
mplsTunnelCRLDPResStorageType StorageType mplsTunnelCRLDPResStorageType StorageType
} }
mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize SYNTAX MplsBurstSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mean burst size in bytes." "The mean burst size in bytes."
DEFVAL { 0 }
::= { mplsTunnelCRLDPResEntry 2 } ::= { mplsTunnelCRLDPResEntry 2 }
mplsTunnelCRLDPResExcessBurstSize OBJECT-TYPE mplsTunnelCRLDPResExcessBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize SYNTAX MplsBurstSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Excess burst size in bytes." "The Excess burst size in bytes."
REFERENCE REFERENCE
"CR-LDP Specification, Section 4.3." "CR-LDP Specification, Section 4.3."
DEFVAL { 0 }
::= { mplsTunnelCRLDPResEntry 3 } ::= { mplsTunnelCRLDPResEntry 3 }
mplsTunnelCRLDPResFrequency OBJECT-TYPE mplsTunnelCRLDPResFrequency OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unspecified(1), unspecified(1),
frequent(2), frequent(2),
veryFrequent(3) veryFrequent(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 61, line 29 skipping to change at page 61, line 14
operations. operations.
It is thus important to control even GET access to these It is thus important to control even GET access to these
objects and possibly to even encrypt the values of these objects and possibly to even encrypt the values of these
object when sending them over the network via SNMP. Not object when sending them over the network via SNMP. Not
all versions of SNMP provide features for such a secure all versions of SNMP provide features for such a secure
environment. environment.
SNMPv1 by itself is not a secure environment. Even if the SNMPv1 by itself is not a secure environment. Even if the
network itself is secure (for example by using IPSec network itself is secure (for example by using IPSec
[IPSEC]), there is no control as to who on the secure [RFC2401]), there is no control as to who on the secure
network is allowed to access and GET/SET network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB. It is (read/change/create/delete) the objects in this MIB. It is
recommended that the implementers consider the security recommended that the implementers consider the security
features as provided by the SNMPv3 framework. features as provided by the SNMPv3 framework.
Specifically, the use of the User-based Security Model Specifically, the use of the User-based Security Model
[SNMPv3USM] and the View- based Access Control [RFC2574] and the View- based Access Control [RFC2575] is
[SNMPv3VACM] is recommended. It is then a customer/user recommended. It is then a customer/user responsibility to
responsibility to ensure that the SNMP entity giving ensure that the SNMP entity giving access to an instance
access to an instance of this MIB, is properly configured of this MIB, is properly configured to give access to the
to give access to the objects only to those principals objects only to those principals (users) that have
(users) that have legitimate rights to indeed GET or SET legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
12. Acknowledgments 12. Acknowledgments
We wish to thank Adrian Farrel, Eric Gray, Joan Cucchiara, We wish to thank Adrian Farrel, Eric Gray, Joan Cucchiara,
Patrick Kerharo, Paul Langille and Mike Piecuch for their Patrick Kerharo, Paul Langille and Mike Piecuch for their
comments on this draft. comments on this draft.
13. References 13. References
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, [Assigned] Reynolds, J., and J. Postel, "Assigned
"Multiprotocol Label Switching Numbers", RFC 1700, October 1994. See also:
Architecture", Internet Draft <draft-ietf- http://www.isi.edu/in-
mpls-arch-0.txt>, July 2000. notes/iana/assignments/smi-numbers
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C,
Viswanathan, A. and H. Sjostrand,
"Definition of Textual Conventions and
OBJECT-IDENTITIES for Multi-Protocol Label
Switching (MPLS) Management", Internet Draft
<draft-ietf-mpls-tc-mib-02.txt>, August
2001.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. [LSRMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau, "MPLS Label Switch Router Management Nadeau, "MPLS Label Switch Router Management
Information Base Using SMIv2", Internet Information Base Using SMIv2", Internet
Draft <draft-ietf-mpls-lsr-mib-06.txt>, July Draft <draft-ietf-mpls-lsr-mib-07.txt>,
2000. January 2001.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D.,
Farinacci, D., Federokow, G., Li, T., and A.
Conta, "MPLS Label Stack Encoding", Internet
Draft <draft-ietf-mpls-label-encaps-08.txt>,
July 2000.
[RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, [RSVPTE] Awaduche, D., Berger, L., Der-Haw, G., Li,
T., Swallow, G., and V. Srinivasan, T., Swallow, G., and V. Srinivasan,
"Extensions to RSVP for LSP Tunnels", "Extensions to RSVP for LSP Tunnels",
Internet Draft <draft-mpls-rsvp-lsp-tunnel- Internet Draft <draft-mpls-rsvp-lsp-tunnel-
07.txt>, August 2000. 08.txt>, February 2001.
[CR-LDP] B. Jamoussi (Editor), "Constraint-Based LSP [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP
Setup using LDP", Internet Draft <draft-ietf- Setup using LDP", Internet Draft <draft-ietf-
mpls-cr-ldp-04.txt>, July 2000. mpls-cr-ldp-05.txt>, February 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned
Numbers", RFC 1700, October 1994. See also:
http://www.isi.edu/in-
notes/iana/assignments/smi-numbers
[SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen,
"An Architecture for Describing SNMP
Management Frameworks", RFC 2271, January
1998.
[SMIv1] Rose, M., and K. McCloghrie, "Structure and [RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for Identification of Management Information for
TCP/IP-based Internets", RFC 1155, May 1990. TCP/IP-based Internets", RFC 1155, May 1990.
[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J.
Davin, "Simple Network Management Protocol",
RFC 1157, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB
Definitions", RFC 1212, March 1991. Definitions", RFC 1212, March 1991.
[SNMPv1Traps] M. Rose, "A Convention for Defining Traps [RFC1215] M. Rose, "A Convention for Defining Traps
for use with the SNMP", RFC 1215, March for use with the SNMP", RFC 1215, March
1991. 1991.
[SMIv2] Case, J., McCloghrie, K., Rose, M., and S. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Structure of Management
Information for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC
1902, January 1996.
[SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Textual Conventions for Version
2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, SNMP Research, Inc.,
Cisco Systems, Inc., January 1996.
[SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Conformance Statements for
Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1904, January 1996.
[SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J.
Davin, "Simple Network Management Protocol",
RFC 1157, May 1990.
[SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based Waldbusser, "Introduction to Community-based
SNMPv2", RFC 1901, January 1996. SNMPv2", RFC 1901, January 1996.
[SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
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.
Waldbusser, "Transport Mappings for Version Waldbusser, "Transport Mappings for Version
2 of the Simple Network Management Protocol 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996. (SNMPv2)", RFC 1906, January 1996.
[SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. [RFC2026] S. Bradner, "The Internet Standards Process
-- Revision 3", RFC 2026, October 1996.
[RFC2233] McCloghrie, K. and F. Kastenholtz, "The
Interface Group MIB Using SMIv2", RFC 2233,
November 1997.
[RFC2401] Kent, S., and Atkinson, R., "Security
Architecture for the Internet Protocol", RFC
2401, November 1998.
[RFC2570] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction to Version 3 of the
Internet-standard Network Management
Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen,
"An Architecture for Describing SNMP
Management Frameworks", RFC 2571, April
1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B.
Wijnen, "Message Processing and Dispatching Wijnen, "Message Processing and Dispatching
for the Simple Network Management Protocol for the Simple Network Management Protocol
(SNMP)", RFC 2272, January 1998. (SNMP)", RFC 2572, April 1999.
[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based
Security Model (USM) for version 3 of the Security Model (USM) for version 3 of the
Simple Network Management Protocol Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999. (SNMPv3)", RFC 2574, April 1999.
[SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie,
Waldbusser, "Protocol Operations for Version
2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996.
[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2273, January 1998.
[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie,
"View-based Access Control Model (VACM) for "View-based Access Control Model (VACM) for
the Simple Network Management Protocol the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder,
Architecture for the Internet Protocol", RFC J., Case, J., Rose, M., and S. Waldbusser,
2401, November 1998. "Structure of Management Information Version
2 (SMIv2)", STD 58, RFC 2578, April 1999.
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder,
Interfaces Group MIB using SMIv2", RFC 2233, J., Case, J., Rose, M., and S. Waldbusser,
Nov. 1997. "Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999.
[INETADDRMIB] Daniele, M., Haberman, B., Routhier, S. and [RFC2702] Awduche, D., Malcolm, J., Agogbua, J.,
O'Dell, M., and J. McManus, "Requirements
for Traffic Engineering Over MPLS", RFC
2702, September 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser,
"Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC2851] Daniele, M., Haberman, B., Routhier, S., and
J. Schoenwaelder, "Textual Conventions for J. Schoenwaelder, "Textual Conventions for
Internet Network Addresses", RFC 2851, June Internet Network Addresses", RFC 2851, June
2000. 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching
Architecture", RFC 3031, January 2001.
14. Authors' Addresses 14. Authors' Addresses
Cheenu Srinivasan Cheenu Srinivasan
Tachion Networks, Inc. Alphion Corp.
Monmouth Park Corporate Center I 4 Industrial Way West
Building C, 185 Monmouth Park Highway Eatontown, NJ 07724
West Long Branch, NJ 07764 Phone: +1-732-676-7066
Phone: +1-732-542-7750 x1234 Email: cheenu@alphion.com
Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
Phone: +1-408-571-3516 Phone: +1-408-571-3516
Email: arun@force10networks.com Email: arun@force10networks.com
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Copyright (C) The Internet Society (2001). All Rights
Reserved. Reserved.
This document and translations of it may be copied and This document and translations of it may be copied and
furnished to others, and derivative works that comment on furnished to others, and derivative works that comment on
or otherwise explain it or assist in its implementation may or otherwise explain it or assist in its implementation may
be prepared, copied, published and distributed, in whole or be prepared, copied, published and distributed, in whole or
in part, without restriction of any kind, provided that the in part, without restriction of any kind, provided that the
above copyright notice and this paragraph are included on above copyright notice and this paragraph are included on
all such copies and derivative works. However, this all such copies and derivative works. However, this
document itself may not be modified in any way, such as by document itself may not be modified in any way, such as by
 End of changes. 

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