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