Network Working Group Martin Dubuc Internet Draft edgeflow, Inc. Expires: August 2001 Sudheer Dharanikota Nayna Networks, Inc. Thomas D. Nadeau Cisco Systems, Inc. Jonathan P. Lang Evan McGinnis Calient Networks Link Management Protocol Management Information Base Using SMIv2 draft-dubuc-lmp-mib-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. 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 1. Abstract ..................................................... 2 2. Introduction ................................................. 2 3. Terminology .................................................. 3 4. The SNMP Management Framework ................................ 3 4.1. Object Definitions ........................................... 4 5. Feature Checklist ............................................ 4 Dubuc et al. Expires August 2001 [Page 1] Internet Draft MPLS LMP MIB February 23, 2001 6. Outline ...................................................... 5 6.1. Summary of LMP MIB ........................................... 5 7. Brief Description of MIB Objects ............................. 6 7.1. lmpNbrTable .................................................. 6 7.2. lmpControlChannelTable ....................................... 6 7.3. lmpLinkVerificationTable ..................................... 6 7.4. lmpControlChannelPerfTable ................................... 7 7.5. lmpTeLinkTable ............................................... 7 7.6. lmpTeLinkCcMappingTable ...................................... 7 7.7. lmpDataBearingLinkTable ...................................... 7 7.8. lmpDataBearingLinkPerfTable .................................. 7 8. Example of LMP Control Channel Interface Setup ............... 8 9. Application of the Interface Group to LMP .................... 10 9.1. Support of the LMP Layer by ifTable .......................... 11 10. Link Management Protocol MIB Definitions ..................... 12 11. Security Considerations ...................................... 46 12. Acknowledgments .............................................. 46 13. References ................................................... 46 14. Authors' Addresses ........................................... 49 15. Full Copyright Statement ..................................... 50 1. Abstract This memo defines an experimental portion of the Management Informa- tion Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP) [LMP]. 2. Introduction This memo defines an experimental portion of the Management Informa- tion Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP) [LMP]. 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. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119, reference [BCP14]. Dubuc et al. Expires August 2001 [Page 2] Internet Draft MPLS LMP MIB February 23, 2001 3. Terminology This document uses terminology from the document describing the Link Management Protocol [LMP]. LMP messages are exchanged between a node pair over primary control channels. There can be several primary con- trol channels between a pair of nodes. LMP messages can flow on any of the "compatible" control channels at any time. Data-bearing links can be used as backup control channels. The primary control channels can also be used to exchange MPLS control plane information or rout- ing information. LMP is designed to aggregate one or more data-bearing links between a node pair into a TE link. Those data-bearing links can either be com- ponent links (e.g. fiber) or ports (e.g. lambda). Within a TE link a number of data-bearing links are considered as primary and the rest as secondary. If any of the primary data-bearing links fails, data traffic switches over to one of the secondary data-bearing links. Each TE link is associated with one or more control channels. In turn, control channels manage one or more TE links. 4. The SNMP Management Framework The SNMP Management Framework presently consists of five major com- ponents: - An overall architecture, described in RFC 2271 [SNMPArch]. - 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]. - 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, 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]. - Protocol operations for accessing management information. The Dubuc et al. Expires August 2001 [Page 3] Internet Draft MPLS LMP MIB February 23, 2001 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 RFC 1905 [SNMPv2PO]. - A set of fundamental applications described in RFC 2273 [SNMPv3App] and the view-based access control mechanism described in RFC 2575 [SNMPv3VACM]. 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 possi- ble (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 informa- tion is not considered to change the semantics of the MIB. 4.1. Object Definitions 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. 5. Feature Checklist The Link Management protocol MIB (LMP-MIB) is designed to satisfy the following requirements and constraints: - The MIB supports the enabling and disabling of LMP capability on LMP capable interfaces of a photonic switch, optical cross-connect or router. - Support is provided for configuration of the keep alive and link verification parameters. Dubuc et al. Expires August 2001 [Page 4] Internet Draft MPLS LMP MIB February 23, 2001 - The MIB allows the mapping between TE links and control channels to be established either through manual configuration or via the link verification procedure. - The MIB is used to express the mapping between local and remote TE links, as well as local and remote interface identifiers for port or component link. - Performance counters are provided for measuring LMP performance on a per-interface basis. Performance counters are also provided for measuring LMP performance on the data-bearing links. Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB [BUNDLE-MIB]. The TE link table which is used to associate data- bearing links to TE links is defined in the Link Bundling MIB. The TE link table in the LMP MIB contains TE link information specific to LMP. 6. Outline Configuring LMP through an optical device involves the following steps: - Enabling LMP on LMP capable interfaces through configuration of control channels. - Optionally specifying link verification parameters. - Configuring the data-bearing links and associating them to the appropriate TE link (this association is stored in the Link Bundling MIB). - Identifying which control channels manage the TE link. 6.1. Summary of LMP MIB The MIB objects for performing these actions consist of the following tables: - The remote node table which is used to identify the pair of nodes that exchange LMP messages over control channels. - The control channel table (lmpControlChannelTable), Dubuc et al. Expires August 2001 [Page 5] Internet Draft MPLS LMP MIB February 23, 2001 which is used for enabling the LMP protocol on LMP-capable interfaces. - The link verification table (lmpLinkVerificationTable), which is used for configuring the LMP link verification parameters associated with a control channel interface. - The control channel performance table (lmpControlChannelPerfT- able), which is used for collecting LMP performance counts on a per-interface basis. - The TE link table (lmpTeLinkTable), which is used for specifying TE links. - The TE link to control channel mapping table (lmpTeLinkCcMappingTable), which is used to define the control channels associated with a TE link. - The data-bearing link table (lmpDataBearingLinkTable), which is used to specify the data-bearing links that are associated with the link bundles. - The data-bearing link performance table (lmpDataBearingLinkPerfTable), which is used for collecting LMP performance counts on data-bearing links. These tables are described in the subsequent sections. 7. Brief Description of MIB Objects Sections 7.1-7.4 describe objects pertaining to LMP-capable inter- faces of a photonic switch, optical cross-connect or router. Section 7.5 to 7.8 describes objects for specifying TE link and data-bearing links. The MIB objects were derived from the LMP document [LMP]. 7.1. lmpNbrTable This table identifies the pairs of nodes on which LMP is enabled. 7.2. lmpControlChannelTable This table represents the interfaces that are LMP capable. A Dubuc et al. Expires August 2001 [Page 6] Internet Draft MPLS LMP MIB February 23, 2001 photonic, optical cross-connect, or router creates an entry in this table for every LMP capable interface on that device. 7.3. lmpLinkVerificationTable This table represents the link verification parameters associated with the LMP control channel interfaces. 7.4. lmpControlChannelPerfTable This table contains the objects to measure the LMP performance of LMP capable interfaces and is an AUGMENT to the lmpControlChannelTable. High capacity counters are provided for objects that are likely to wrap around quickly. 7.5. lmpTeLinkTable This table represents the TE link information specific to LMP. 7.6. lmpTeLinkCcMappingTable This table specifies the mapping between TE links and control chan- nels. 7.7. lmpDataBearingLinkTable The data-bearing link table enumerates the data-bearing link that are associated with each TE link. 7.8. lmpDataBearingLinkPerfTable This table contains the objects to measure the LMP performance of data-bearing links and is an AUGMENT to the lmpDataBearingLinkTable. Dubuc et al. Expires August 2001 [Page 7] Internet Draft MPLS LMP MIB February 23, 2001 8. Example of LMP Control Channel Setup In this section we provide a brief example of using the MIB objects described in section 11 to set up a LMP control channel. While this example is not meant to illustrate every nuance of the MIB, it is intended as an aid to understanding some of the key concepts. It is meant to be read after going through the MIB itself. Suppose that one would like to manually create two control channels between a pair of nodes that controls 3 data-bearing links (two primary and one secondary). Assume that the data-bearing links are ports (lambdas) and that the secondary data-bearing link can also be used as a backup control channel in case the two primary control channels are down. We also assume that the link verification procedure is not enabled. The following example illustrates which rows and corresponding objects might be created to accomplish this. First, LMP must be enabled between the pair of nodes. In lmpNbrTable: { lmpNbrNodeId = 200 lmpNbrAdminStatus = up(1) lmpNbrRowStatus = createAndGo(4) } Then, the control channels must be set up. The primary control channel are created in the lmpControlChannelTable. The backup control channel will be created later when provisioning the data-bearing links. Note that the backup control channel can be used to carry data traffic until it is preempted for control channel purposes. In lmpControlChannelTable: { lmpCcId = 1 lmpCcCapabilities = 0 lmpCcConfigRetransmitInterval = 10 lmpCcHelloInterval = 5 lmpCcHelloDeadInterval = 15 lmpCcLinkSumRetransmitInterval = 10 lmpCcAdminStatus = up(1) lmpCcRowStatus = createAndGo(4) } { Dubuc et al. Expires August 2001 [Page 8] Internet Draft MPLS LMP MIB February 23, 2001 lmpCcId = 2 lmpCcCapabilities = 0 lmpCcConfigRetransmitInterval = 10 lmpCcHelloInterval = 5 lmpCcHelloDeadInterval = 15 lmpCcLinkSumRetransmitInterval = 10 lmpCcAdminStatus = up(1) lmpCcRowStatus = createAndGo(4) } Next, the three data-bearing links are created. In lmpDataBearingLinkTable: { lmpDataBearingLinkIfId = 41 lmpDataBearingLinkRemoteIfId = 47 lmpCcPreemptability = false(1) lmpDataBearingLinkRowStatus = createAndGo(4) } { lmpDataBearingLinkIfId = 43 lmpDataBearingLinkRemoteIfId = 42 lmpCcPreemptambility = false(1) lmpDataBearingLinkRowStatus = createAndGo(4) } { lmpDataBearingLinkIfId = 44 lmpDataBearingLinkRemoteIfId = 48 lmpCcPreemptability = true(1) lmpDataBearingLinkRowStatus = createAndGo(4) } Note that the data-bearing link type (lmpDataBearingLinkType) does not need to be provisioned as it is automatically populated by the node. Also note that the the node will arbitrarily set two of the three ports as primary data-bearing link and the other as secondary data-bearing link in the componentLinkTable of the Link Bundling MIB. Then, a TE link/bundled link is created in the linkBundlingTable of the LINK-BUNDLING-MIB [BUNDLE-MIB] to bind together the data-bearing links that are associated with the TE link. The TE link will be created with shared protection type. Dubuc et al. Expires August 2001 [Page 9] Internet Draft MPLS LMP MIB February 23, 2001 Once the TE link is created in the linkBundlingTable, a TE link entry is created in the LMP MIB to specify TE link information specific to LMP. In lmpTeLinkTable: { lmpTeLinkId = 20 lmpRemoteTeLinkId = 33 lmpRemoteTeLinkType = unnumbered(2) lmpTeLinkEncodingType = sonet(6) lmpTeLinkBitRate = 100000 lmpTeLinkWavelength = 0 lmpTeLinkAdminStatus = up(1) lmpTeLinkRowStatus = createAndGo(4) } Finally, the mapping between TE link and control channels. In lmpTeLinkCcMapping: { lmpTeLinkId = 20 lmpCcId = 1 lmpTeLinkIdRowStatus = createAndGo(4) } { lmpTeLinkId = 20 lmpCcId = 2 lmpTeLinkIdRowStatus = createAndGo(4) } 9. Application of the Interface Group to LMP 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 LMP interfaces. This memo assumes the interpretation of the Interfaces Group to be in accordance with [IFMIB] 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 LMP interface is represented as an entry in the ifTable. The inter- relation of entries in the ifTable is defined by Interfaces Stack Group defined in [IFMIB]. Dubuc et al. Expires August 2001 [Page 10] Internet Draft MPLS LMP MIB February 23, 2001 When using LMP interfaces, the interface stack table might appear as follows: +----------------------------------------+ | LMP-interface ifType = lmp(199) + +----------------------------------------+ | Underlying Layer... + +----------------------------------------+ In the above diagram, "Underlying Layer..." refers to the ifIndex of any interface type, which has been defined for LMP interworking. Examples include ATM, Frame Relay, Ethernet, etc. 9.1. Support of the LMP Layer by ifTable Some specific interpretations of ifTable for the LMP layer follow. Object Use for the LMP layer ifIndex Each LMP interface is represented by an ifEntry. ifDescr Description of the LMP interface. ifType The value that is allocated for LMP is 199. ifSpeed The total bandwidth in bits per second for use by the LMP layer. ifPhysAddress Unused. ifAdminStatus This variable indicates the administrator's intent as to whether LMP should be enabled, disabled, or running in some diagnostic testing mode on this interface. Also see [IFMIB]. ifOperStatus This value reflects the actual or operational status of LMP on this interface. ifLastChange See [IFMIB]. ifInOctets The number of received octets over the interface, i.e., the number of received, octets received as labeled packets. ifOutOctets The number of transmitted octets over the Dubuc et al. Expires August 2001 [Page 11] Internet Draft MPLS LMP MIB February 23, 2001 interface, i.e., the number of octets transmitted as labeled packets. 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]. ifName Textual name (unique on this system) of the interface or an octet string of zero length. ifLinkUpDownTrapEnable Default is disabled (2). ifConnectorPresent Set to false (2). ifHighSpeed See [IFMIB]. ifHCInOctets The 64-bit version of ifInOctets; supported if required by the compliance statements in [IFMIB]. ifHCOutOctets The 64-bit version of ifOutOctets; supported if required by the compliance statements in [IFMIB]. ifAlias The non-volatile 'alias' name for the interface as specified by a network manager. ifCounterDiscontinuityTime See [IFMIB]. 10. LMP MIB Definitions LMP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, experimental, Integer32, Unsigned32, Counter32, Counter64 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP Dubuc et al. Expires August 2001 [Page 12] Internet Draft MPLS LMP MIB February 23, 2001 FROM SNMPv2-CONF TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, RowPointer, TimeStamp FROM SNMPv2-TC InterfaceIndex, InterfaceIndexOrZero FROM IF-MIB; lmpMIB MODULE-IDENTITY LAST-UPDATED "200102221200Z" -- 22 February 2001 12:00:00 EST ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Martin Dubuc Postal: edgeflow, Inc. 329 March Rd. Kanata, ON, CANADA K2K 2E1 Tel: +1-613-270-9279 x253 Email: martin.dubuc@edgeflow.com Sudheer Dharanikota Postal: Nayna Networks, Inc. 157 Topaz Street Milipitas, CA 95035 Tel: +1-408-956-8000 x357 Email: sudheer@nayna.com Thomas D. Nadeau Postal: Cisco Systems, Inc. 350 Apollo Drive Chelmsford, MA 01824 Tel: +1-978-244-3051 Email: tnadeau@cisco.com Jonathan P. Lang Postal: Calient Networks 25 Castilian Drive Goleta, CA 93117 Email: jplang@calient.net Evan McGinnis Postal: Calient Networks 5853 Rue Ferrari San Jose, CA 95138 Email: evan@calient.net" DESCRIPTION Dubuc et al. Expires August 2001 [Page 13] Internet Draft MPLS LMP MIB February 23, 2001 "This MIB contains managed object definitions for the Link Management Protocol (LMP) as defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., Rekhter, Y., Berger, L., Rajagopalan, B., Basak, D., Sandick, H., Zinin, A., and Banarjee, A., Link Management Protocol, Internet Draft , February 2001." -- Revision history. REVISION "200102221200Z" -- 22 February 2001 12:00:00 EST DESCRIPTION "Updates based on MPLS mailing list feedback." REVISION "200101261200Z" -- 26 January 2001 12:00:00 EST DESCRIPTION "Initial draft version." -- Experimental number TBA - To be assigned by the IANA ::= { experimental 97 } -- Textual Conventions NodeID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This value represents a Node ID." SYNTAX Unsigned32 (1..4294967295) -- A control channel identifier (CCId) LmpCcId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This value represents a control channel identifier. It is a node-wide unique 32-bit integer that is assigned to each direction of the control channel interface." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." SYNTAX InterfaceIndex TeLinkId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION Dubuc et al. Expires August 2001 [Page 14] Internet Draft MPLS LMP MIB February 23, 2001 "This value represents a TE link identifier." SYNTAX InterfaceIndex LmpInterval ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The interval delay in milliseconds." SYNTAX Unsigned32 (1..65535) LmpRetransmitInterval ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The retransmission interval delay in milliseconds." SYNTAX Unsigned32 (1..4294967295) -- Top level components of this MIB -- Traps lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } -- Tables, Scalars lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } -- Conformance lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } lmpAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The desired operational status of LMP on the node." DEFVAL { up } ::= { lmpObjects 1 } -- LMP Neighbor Table lmpNbrTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpNbrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies the neighbor node to which control channels may be established." ::= { lmpObjects 2 } Dubuc et al. Expires August 2001 [Page 15] Internet Draft MPLS LMP MIB February 23, 2001 lmpNbrEntry OBJECT-TYPE SYNTAX LmpNbrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a LMP-enabled device for every pair of nodes that can establish control channels." INDEX { lmpNbrNodeId } ::= { lmpNbrTable 1 } LmpNbrEntry ::= SEQUENCE { lmpNbrNodeId NodeID, lmpNbrAdminStatus Unsigned32, lmpNbrOperStatus Unsigned32, lmpNbrRowStatus RowStatus, lmpNbrStorageType StorageType } lmpNbrNodeId OBJECT-TYPE SYNTAX NodeID MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the LmpNbrTable. This value represents the remote Node ID." ::= { lmpNbrEntry 1 } lmpNbrAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired operational status of LMP to this remote node." ::= { lmpNbrEntry 2 } lmpNbrOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of LMP to this remote node." ::= { lmpNbrEntry 3 } lmpNbrRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current Dubuc et al. Expires August 2001 [Page 16] Internet Draft MPLS LMP MIB February 23, 2001 DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpNbrEntry 4 } lmpNbrStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this entry." ::= { lmpNbrEntry 5 } -- End of lmpNbrTable lmpCcHelloIntervalDefault OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the default value for the HelloInterval parameter used in the Hello protocol keep-alive phase. It indicates how frequently LMP Hello messages will be sent." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpObjects 3 } lmpCcHelloIntervalMin OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the minimum value for the HelloInterval parameter." ::= { lmpObjects 4 } lmpCcHelloIntervalMax OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the maximum value for the HelloInterval parameter." ::= { lmpObjects 5 } Dubuc et al. Expires August 2001 [Page 17] Internet Draft MPLS LMP MIB February 23, 2001 lmpCcHelloDeadIntervalDefault OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the HelloDeadInterval parameter used in the Hello protocol keep-alive phase. It indicates how long a device should wait before declaring the control channel dead. The HelloDeadInterval parameter must be greater than the HelloInterval parameter and should be at least three times the value of HelloInterval." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpObjects 6 } lmpCcHelloDeadIntervalMin OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies minimum value for the HelloDeadInterval parameter." ::= { lmpObjects 7 } lmpCcHelloDeadIntervalMax OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies maximum value for the HelloDeadInterval parameter." ::= { lmpObjects 8 } -- LMP Control Channel Table lmpControlChannelTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpControlChannelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies LMP control channel information." ::= { lmpObjects 9 } lmpControlChannelEntry OBJECT-TYPE Dubuc et al. Expires August 2001 [Page 18] Internet Draft MPLS LMP MIB February 23, 2001 SYNTAX LmpControlChannelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a LMP-enabled device for every control channel." INDEX { lmpCcId } ::= { lmpControlChannelTable 1 } LmpControlChannelEntry ::= SEQUENCE { lmpCcId LmpCcId, lmpCcNbrNodeId Unsigned32, lmpCcCapabilities BITS, lmpCcConfigRetransmitInterval LmpRetransmitInterval, lmpCcHelloInterval LmpInterval, lmpCcHelloDeadInterval LmpInterval, lmpCcLinkSumRetransmitInterval LmpRetransmitInterval, lmpCcAdminStatus Unsigned32, lmpCcOperStatus Unsigned32, lmpCcRowStatus RowStatus, lmpCcStorageType StorageType } lmpCcId OBJECT-TYPE SYNTAX LmpCcId MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the LmpControlChannelTable. This value represents the interface index for the control channel. It points to an interface entry of the LMP-layer in the ifTable." ::= { lmpControlChannelEntry 1 } lmpCcNbrNodeId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "This is the Node ID of the control channel remote node. This value gets created by the node when the Config message is acknowledged by the remote node." ::= { lmpControlChannelEntry 2 } lmpCcCapabilities OBJECT-TYPE SYNTAX BITS { linkVerification(0), faultIsolation(1), lmpDwdm(2) } MAX-ACCESS read-create STATUS current Dubuc et al. Expires August 2001 [Page 19] Internet Draft MPLS LMP MIB February 23, 2001 DESCRIPTION "The capability bit mask indicates which extended LMP procedures are supported. If none of those bits are set, it indicates that only the base LMP procedures are supported." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpControlChannelEntry 3 } lmpCcConfigRetransmitInterval OBJECT-TYPE SYNTAX LmpRetransmitInterval MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the interval that is used for the retransmission of Config messages during the parameter negotiation phase." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpControlChannelEntry 4 } lmpCcHelloInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the negotiated value of the HelloInterval parameter." ::= { lmpControlChannelEntry 5 } lmpCcHelloDeadInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the negotiated value of the HelloDeadInterval parameter." ::= { lmpControlChannelEntry 6 } lmpCcLinkSumRetransmitInterval OBJECT-TYPE SYNTAX LmpRetransmitInterval MAX-ACCESS read-create STATUS current Dubuc et al. Expires August 2001 [Page 20] Internet Draft MPLS LMP MIB February 23, 2001 DESCRIPTION "This object specifies the interval that is used for the retransmission of LinkSummary messages during the property correlation phase." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpControlChannelEntry 7 } lmpCcAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired operational status of this control channel." ::= { lmpControlChannelEntry 8 } lmpCcOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), configuring(3), active(4), switchingOver(5), takingOver(6), goingDown(7) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this control channel interface." ::= { lmpControlChannelEntry 9 } lmpCcRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpControlChannelEntry 10 } lmpCcStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create Dubuc et al. Expires August 2001 [Page 21] Internet Draft MPLS LMP MIB February 23, 2001 STATUS current DESCRIPTION "The storage type for this entry." ::= { lmpControlChannelEntry 11 } -- End of lmpControlChannelTable lmpLinkVerificationInterval OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates how often the link verification procedure is executed. The interval is in milliseconds." ::= { lmpObjects 10 } -- LMP Control Channel Link Verification Table lmpLinkVerificationTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpLinkVerificationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies control channel information associated with the LMP verification procedure." ::= { lmpObjects 11 } lmpLinkVerificationEntry OBJECT-TYPE SYNTAX LmpLinkVerificationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a LMP-enabled device for every control channel that supports the LMP verification procedure." AUGMENTS { lmpControlChannelEntry } ::= { lmpLinkVerificationTable 1 } LmpLinkVerificationEntry ::= SEQUENCE { lmpVerifyInterval LmpInterval, lmpVerifyDeadInterval LmpInterval, lmpVerifyTransportMechanism BITS, lmpVerifyAllLinks Unsigned32 } lmpVerifyInterval OBJECT-TYPE Dubuc et al. Expires August 2001 [Page 22] Internet Draft MPLS LMP MIB February 23, 2001 SYNTAX LmpInterval MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the VerifyInterval parameter used in the LMP link verification process. It indicates the interval at which the Test messages are sent." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpLinkVerificationEntry 1 } lmpVerifyDeadInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the VerifyDeadInterval parameter used in the verification of the physical connectivity of data-bearing links. It specifies the observation period used to detect a Test message at the remote node." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpLinkVerificationEntry 2 } lmpVerifyTransportMechanism OBJECT-TYPE SYNTAX BITS { -- SONET/SDH encoding type: j0OverheadBytes(0), dccSectionOverheadBytes(1), dccLineOverheadBytes(2), pos(3) -- GigE encoding type: TBD -- 10GigE encoding type: TBD } MAX-ACCESS read-only STATUS current DESCRIPTION "This defines the transport mechanism for the Test messages. The scope of this bit mask is restricted to each link encoding type. The local node will set the bits corresponding to the various mechanisms it can support for transmitting LMP Test messages. The receiver chooses the appropriate mechanism in the Dubuc et al. Expires August 2001 [Page 23] Internet Draft MPLS LMP MIB February 23, 2001 BeginVerifyAck message." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpLinkVerificationEntry 3 } lmpVerifyAllLinks OBJECT-TYPE SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates whether the verification process checks all entities or only the new entities that have been added to this TE link." ::= { lmpLinkVerificationEntry 4 } -- End of lmpLinkVerificationTable -- LMP Control Channel Performance Table lmpControlChannelPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpInterfacePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies LMP control channel performance counters." ::= { lmpObjects 12 } lmpControlChannelPerfEntry OBJECT-TYPE SYNTAX LmpInterfacePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a LMP-enabled device for every control channel." AUGMENTS { lmpControlChannelEntry } ::= { lmpControlChannelPerfTable 1 } LmpInterfacePerfEntry ::= SEQUENCE { lmpCcHCHelloReceived Counter64, lmpCcHCHelloSent Counter64, lmpCcConfigReceived Counter32, lmpCcConfigSent Counter32, lmpCcConfigRetransmit Counter32, lmpCcLinkSummaryReceived Counter32, Dubuc et al. Expires August 2001 [Page 24] Internet Draft MPLS LMP MIB February 23, 2001 lmpCcLinkSummarySent Counter32, lmpCcLinkSummaryRetransmit Counter32, lmpCcChannelFailReceived Counter32, lmpCcChannelFailSent Counter32 } lmpCcHCHelloReceived OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Hello messages that have been received on this interface." ::= { lmpControlChannelPerfEntry 1 } lmpCcHCHelloSent OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Hello messages that have been sent on this interface." ::= { lmpControlChannelPerfEntry 2 } lmpCcConfigReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Config messages that have been received on this interface." ::= { lmpControlChannelPerfEntry 3 } lmpCcConfigSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Config messages that have been sent on this interface." ::= { lmpControlChannelPerfEntry 4 } lmpCcConfigRetransmit OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Config messages that Dubuc et al. Expires August 2001 [Page 25] Internet Draft MPLS LMP MIB February 23, 2001 have been retransmitted over this interface." ::= { lmpControlChannelPerfEntry 5 } lmpCcLinkSummaryReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of LinkSummary messages that have been received on this interface." ::= { lmpControlChannelPerfEntry 6 } lmpCcLinkSummarySent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of LinkSummary messages that have been sent on this interface." ::= { lmpControlChannelPerfEntry 7 } lmpCcLinkSummaryRetransmit OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of LinkSummary messages that have been retransmitted over this interface." ::= { lmpControlChannelPerfEntry 8 } lmpCcChannelFailReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of ChannelFail messages that have been received on this interface." ::= { lmpControlChannelPerfEntry 9 } lmpCcChannelFailSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of ChannelFail messages that have been sent on this interface." ::= { lmpControlChannelPerfEntry 10 } Dubuc et al. Expires August 2001 [Page 26] Internet Draft MPLS LMP MIB February 23, 2001 -- End of lmpControlChannelPerfTable -- LMP TE Link Table lmpTeLinkTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpTeLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a collection of TE link." ::= { lmpObjects 13 } lmpTeLinkEntry OBJECT-TYPE SYNTAX LmpTeLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents one TE link. Entries in this table are indexed by the TE link identifier." INDEX { lmpTeLinkId } ::= { lmpTeLinkTable 1 } LmpTeLinkEntry ::= SEQUENCE { lmpTeLinkId TeLinkId, lmpRemoteTeLinkId TeLinkId, lmpRemoteTeLinkType Unsigned32, lmpTeLinkEncodingType Unsigned32, lmpTeLinkBitRate Unsigned32, lmpTeLinkWavelength Unsigned32, lmpTeLinkAdminStatus Unsigned32, lmpTeLinkOperStatus Unsigned32, lmpTeLinkRowStatus RowStatus, lmpTeLinkStorageType StorageType } lmpTeLinkId OBJECT-TYPE SYNTAX TeLinkId MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the lmpTeLinkTable. It points to an interface in the ifTable." ::= { lmpTeLinkEntry 1 } lmpRemoteTeLinkId OBJECT-TYPE SYNTAX TeLinkId Dubuc et al. Expires August 2001 [Page 27] Internet Draft MPLS LMP MIB February 23, 2001 MAX-ACCESS read-create STATUS current DESCRIPTION "This identifies the TE link identifier on the remote side of the TE link. This is either configured manually or is communicated by the remote node during the link verification procedure. It is expected that for unnumbered TE links, this value will be set to 0." ::= { lmpTeLinkEntry 2 } lmpRemoteTeLinkType OBJECT-TYPE SYNTAX INTEGER { numbered(0), unnumbered(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "The remote TE link type (numbered or unnumbered)." ::= { lmpTeLinkEntry 3 } lmpTeLinkEncodingType OBJECT-TYPE SYNTAX INTEGER { packet(1), ethernet(2), ansiPdh(3), etsiPdh(4), sdh(5), sonet(6), digitalWrapper(7), lambda(8), fiber(9) } MAX-ACCESS read-create STATUS current DESCRIPTION "The encoding type of the data-bearing links contained in the TE link." REFERENCE "draft-ietf-mpls-generalized-signaling-00.txt - Generalized MPLS Signaling Functional Description, P. Ashwood-Smith, A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, V. Sharma, G. Swallow, Z. Tang, October 2000." ::= { lmpTeLinkEntry 4 } lmpTeLinkBitRate OBJECT-TYPE SYNTAX Unsigned32 Dubuc et al. Expires August 2001 [Page 28] Internet Draft MPLS LMP MIB February 23, 2001 MAX-ACCESS read-create STATUS current DESCRIPTION "This is the bit rate at which the Test messages will be transmitted and is expressed in bytes per second." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, Februrary 2001." ::= { lmpTeLinkEntry 5 } lmpTeLinkWavelength OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "This value corresponds to the wavelength at which the Test messages will be transmitted over and is measured in nanometers (nm). If each data-bearing link corresponds to a separate wavelength, than this value should be set to 0." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpTeLinkEntry 6 } lmpTeLinkAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The desired operational status of this TE link." ::= { lmpTeLinkEntry 7 } lmpTeLinkOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this TE link." ::= { lmpTeLinkEntry 8 } lmpTeLinkRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create Dubuc et al. Expires August 2001 [Page 29] Internet Draft MPLS LMP MIB February 23, 2001 STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpTeLinkEntry 9 } lmpTeLinkStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object." ::= { lmpTeLinkEntry 10 } -- End of lmpTeLinkTable -- LMP TE Link to Control Channel Mapping Table lmpTeLinkCcMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpTeLinkCcMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides the mapping between TE links and control channels." ::= { lmpObjects 14 } lmpTeLinkCcMappingEntry OBJECT-TYPE SYNTAX LmpTeLinkCcMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created for every TE link to control channel association." INDEX { lmpTeLinkId, lmpTeLinkCcId } ::= { lmpTeLinkCcMappingTable 1 } LmpTeLinkCcMappingEntry ::= SEQUENCE { lmpTeLinkCcId LmpCcId, lmpTeLinkCcMappingRowStatus RowStatus, lmpTeLinkCcMappingStorageType StorageType } lmpTeLinkCcId OBJECT-TYPE SYNTAX LmpCcId MAX-ACCESS accessible-for-notify Dubuc et al. Expires August 2001 [Page 30] Internet Draft MPLS LMP MIB February 23, 2001 STATUS current DESCRIPTION "This is a unique interface index that coupled with teLinkId points into an entry in the lmpTeLinkCcTable." ::= { lmpTeLinkCcMappingEntry 2 } lmpTeLinkCcMappingRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpTeLinkCcMappingEntry 3 } lmpTeLinkCcMappingStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this entry." ::= { lmpTeLinkCcMappingEntry 4 } -- End of lmpTeLinkCcMappingTable -- LMP Data Bearing Link Table lmpDataBearingLinkTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpDataBearingLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies the data-bearing links managed by the LMP." ::= { lmpObjects 15 } lmpDataBearingLinkEntry OBJECT-TYPE SYNTAX LmpDataBearingLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table contains information about the data-bearing links. The index to this table also points to the ifTable and componentLinkTable." INDEX { lmpDataBearingLinkIfId } ::= { lmpDataBearingLinkTable 1 } Dubuc et al. Expires August 2001 [Page 31] Internet Draft MPLS LMP MIB February 23, 2001 LmpDataBearingLinkEntry ::= SEQUENCE { lmpDataBearingLinkIfId InterfaceIndexOrZero, lmpDataBearingLinkType Unsigned32, lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero, lmpDataBearingLinkCcPreemptibility TruthValue, lmpDataBearingLinkAdminStatus Unsigned32, lmpDataBearingLinkOperStatus Unsigned32, lmpDataBearingLinkRowStatus RowStatus, lmpDataBearingLinkStorageType StorageType } lmpDataBearingLinkIfId OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the lmpDataBearingLinkTable. This value represents the interface index for the data-bearing link. It points to an interface in the ifTable." REFERENCE "RFC 2863 - The Interfaces Group MIB, K. McCloghrie and F. Kastenholtz, June 2000." ::= { lmpDataBearingLinkEntry 1 } lmpDataBearingLinkType OBJECT-TYPE SYNTAX INTEGER { port(1), componentLink(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This attribute specifies whether this data-bearing link is a port or a component link. Component link are multiplex capable whereas, ports are not multiplex capable." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpDataBearingLinkEntry 2 } lmpDataBearingLinkRemoteIfId OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION Dubuc et al. Expires August 2001 [Page 32] Internet Draft MPLS LMP MIB February 23, 2001 "Interface identifier of the remote end point. This information is either configured manually or is communicated by the remote node during the link verification procedure." ::= { lmpDataBearingLinkEntry 3 } lmpDataBearingLinkCcPreemptibility OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This attribute specifies whether this data-bearing link is a port or a component link. Component link are multiplex capable whereas, ports are not multiplex capable." DEFVAL { true } ::= { lmpDataBearingLinkEntry 4 } lmpDataBearingLinkAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired operational status of this data-bearing link." ::= { lmpDataBearingLinkEntry 5 } lmpDataBearingLinkOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), testing(3), ccBoot(4), beginVerify(5), psvTst(6), tstDone(7), degraded(8) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this data-bearing link. A data-bearing link is in the degraded state if the control channel and associated backup control channel(s) are down but the data-bearing link is still operational." REFERENCE "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, February 2001." ::= { lmpDataBearingLinkEntry 6 } Dubuc et al. Expires August 2001 [Page 33] Internet Draft MPLS LMP MIB February 23, 2001 lmpDataBearingLinkRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpDataBearingLinkEntry 7 } lmpDataBearingLinkStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object." ::= { lmpDataBearingLinkEntry 8 } -- End of lmpDataBearingLinkTable -- LMP Data Bearing Link Performance Table lmpDataBearingLinkPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies the data-bearing links LMP performance counters." ::= { lmpObjects 16 } lmpDataBearingLinkPerfEntry OBJECT-TYPE SYNTAX LmpDataBearingLinkPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table contains information about the LMP performance counters for the data-bearing links." AUGMENTS { lmpDataBearingLinkEntry } ::= { lmpDataBearingLinkPerfTable 1 } LmpDataBearingLinkPerfEntry ::= SEQUENCE { lmpDataBearingLinkTestReceived Counter32, lmpDataBearingLinkTestSent Counter32 } lmpDataBearingLinkTestReceived OBJECT-TYPE Dubuc et al. Expires August 2001 [Page 34] Internet Draft MPLS LMP MIB February 23, 2001 SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Test messages that have been received on this interface." ::= { lmpDataBearingLinkPerfEntry 1 } lmpDataBearingLinkTestSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Test messages that have been sent on this interface." ::= { lmpDataBearingLinkPerfEntry 2 } -- End of lmpDataBearingLinkTable -- Notification Configuration lmpLinkPropertyMismatchTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpTeLinkPropertyMismatch and lmpDataBearingLinkPropertyMismatch traps, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 17 } lmpCcTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpControlChannelSwitchover trap, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 18 } lmpUnprotectedTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write Dubuc et al. Expires August 2001 [Page 35] Internet Draft MPLS LMP MIB February 23, 2001 STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpUnprotected trap, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 19 } lmpDataBearingLinkTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpDataBearingLinkDegraded trap, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 20 } -- Notifications lmpNotifyPrefix OBJECT IDENTIFIER ::= { lmpNotifications 0 } -- Link Property Mismatch Traps lmpTeLinkPropertyMismatch NOTIFICATION-TYPE OBJECTS { lmpTeLinkId, lmpRemoteTeLinkId, lmpRemoteTeLinkId } STATUS current DESCRIPTION "This notification is generated when a TE link property mismatch is detected on the node. The first remote TE link id is the remote TE link id configured on the node. The second remote TE link id is the remote TE link id received in the LinkSummary message." ::= { lmpNotifyPrefix 1 } lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE OBJECTS { lmpTeLinkId, lmpDataBearingLinkIfId, lmpDataBearingLinkRemoteIfId, lmpDataBearingLinkRemoteIfId } STATUS current DESCRIPTION "This notification is generated when a data-bearing link property Dubuc et al. Expires August 2001 [Page 36] Internet Draft MPLS LMP MIB February 23, 2001 mismatch is detected on the node. The first remote entity interface id is the remote entity interface id configured on the node. The second remote entify interface id is the remote entity interface id received in the LinkSummary message." ::= { lmpNotifyPrefix 2 } -- Control Channel Trap lmpControlChannelSwitchover NOTIFICATION-TYPE OBJECTS { lmpCcId, lmpDataBearingLinkIfId } STATUS current DESCRIPTION "This notification is generated when one of the backup control channel, which was previously designated as a data-bearing link, is now used to carry control channel traffic. lmpCcId identifies the target control channel and lmpDataBearingLinkIfId refers to the interface identifier of the data-bearing link which is now used to carry control channel traffic." ::= { lmpNotifyPrefix 3 } -- Control Channel Interface Trap lmpUnprotected NOTIFICATION-TYPE OBJECTS { lmpCcNbrNodeId } STATUS current DESCRIPTION "This notification is generated when all but one control channel is operational and there are no more operational data-bearing links that can be used as backup control channel. If the only operational control channel fails, then there will be no more control channels between the pair of nodes and all the data-bearing links between the pair of nodes will go to degraded state." ::= { lmpNotifyPrefix 4 } -- Data-bearing Link Trap lmpDataBearingLinkDegraded NOTIFICATION-TYPE OBJECTS { lmpTeLinkId, lmpDataBearingLinkIfId } STATUS current DESCRIPTION "This notification is generated when a lmpDataBearingLinkOperStatus object managed by one of the configured control channel entry enters the degraded state." ::= { lmpNotifyPrefix 5 } Dubuc et al. Expires August 2001 [Page 37] Internet Draft MPLS LMP MIB February 23, 2001 -- End of notifications -- Module compliance lmpGroups OBJECT IDENTIFIER ::= { lmpConformance 1 } lmpCompliances OBJECT IDENTIFIER ::= { lmpConformance 2 } lmpModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support the MPLS LMP MIB." MODULE -- this module -- The mandatory groups have to be implemented -- by all LMP-enabled devices. However, they may all be supported -- as read-only objects in the case where manual -- configuration is unsupported. MANDATORY-GROUPS { lmpNodeGroup, lmpControlChannelGroup, lmpLinkPropertyCorrelationGroup, lmpPerfGroup, lmpTeLinkGroup, lmpDataBearingLinkGroup } -- Scalars OBJECT lmpAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpLinkVerificationInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcHelloIntervalDefault MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcHelloIntervalMin Dubuc et al. Expires August 2001 [Page 38] Internet Draft MPLS LMP MIB February 23, 2001 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcHelloIntervalMax MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcHelloDeadIntervalDefault MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcHelloDeadIntervalMin MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcHelloDeadIntervalMax MIN-ACCESS read-only DESCRIPTION "Write access is not required." -- lmpControlChannelTable OBJECT lmpNbrRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpNbrStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." -- lmpControlChannelTable OBJECT lmpCcCapabilities MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcConfigRetransmitInterval Dubuc et al. Expires August 2001 [Page 39] Internet Draft MPLS LMP MIB February 23, 2001 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcLinkSumRetransmitInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpCcRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpCcOperStatus SYNTAX INTEGER { up(1), down(2) } MIN-ACCESS read-only DESCRIPTION "A value of active(3), configuring(4), switchingOver(5), takingOver(6) and goingDown(7) need not be supported." OBJECT lmpCcStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." -- lmpLinkVerificationTable OBJECT lmpVerifyInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpVerifyDeadInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpVerifyAllLinks MIN-ACCESS read-only DESCRIPTION "Write access is not required." -- lmpTeLinkTable Dubuc et al. Expires August 2001 [Page 40] Internet Draft MPLS LMP MIB February 23, 2001 OBJECT lmpRemoteTeLinkId MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpRemoteTeLinkType MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpTeLinkEncodingType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpTeLinkBitRate MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpTeLinkWavelength MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpTeLinkRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpTeLinkStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." -- lmpTeLinkCcMappingTable OBJECT lmpTeLinkCcMappingRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION Dubuc et al. Expires August 2001 [Page 41] Internet Draft MPLS LMP MIB February 23, 2001 "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpTeLinkCcMappingStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." -- lmpDataBearingLinkTable OBJECT lmpDataBearingLinkRemoteIfId MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpDataBearingLinkCcPreemptibility MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpDataBearingLinkOperStatus SYNTAX INTEGER { up(1), down(2), degraded(4) } MIN-ACCESS read-only DESCRIPTION "A value of testing(3) need not be supported." OBJECT lmpDataBearingLinkRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpDataBearingLinkStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." ::= { lmpCompliances 1 } -- Units of conformance lmpNodeGroup OBJECT-GROUP OBJECTS { lmpAdminStatus, Dubuc et al. Expires August 2001 [Page 42] Internet Draft MPLS LMP MIB February 23, 2001 lmpNbrAdminStatus, lmpNbrOperStatus, lmpNbrRowStatus, lmpNbrStorageType, lmpUnprotectedTrapEnable } STATUS current DESCRIPTION "Collection of objects needed for LMP node configuration." ::= { lmpGroups 1 } lmpControlChannelGroup OBJECT-GROUP OBJECTS { lmpCcNbrNodeId, lmpCcHelloIntervalDefault, lmpCcHelloIntervalMin, lmpCcHelloIntervalMax, lmpCcHelloDeadIntervalDefault, lmpCcHelloDeadIntervalMin, lmpCcHelloDeadIntervalMax, lmpCcCapabilities, lmpCcConfigRetransmitInterval, lmpCcHelloInterval, lmpCcHelloDeadInterval, lmpCcLinkSumRetransmitInterval, lmpCcOperStatus, lmpCcAdminStatus, lmpCcRowStatus, lmpCcStorageType, lmpCcTrapEnable } STATUS current DESCRIPTION "Collection of objects needed for LMP interface configuration." ::= { lmpGroups 2 } lmpLinkPropertyCorrelationGroup OBJECT-GROUP OBJECTS { lmpLinkPropertyMismatchTrapEnable } STATUS current DESCRIPTION "Collection of objects needed to implement the link property correlation procedure." ::= { lmpGroups 3 } lmpLinkVerificationGroup OBJECT-GROUP OBJECTS { lmpLinkVerificationInterval, lmpVerifyInterval, Dubuc et al. Expires August 2001 [Page 43] Internet Draft MPLS LMP MIB February 23, 2001 lmpVerifyDeadInterval, lmpVerifyTransportMechanism, lmpVerifyAllLinks } STATUS current DESCRIPTION "Collection of objects needed to implement the link verification procedure." ::= { lmpGroups 4 } lmpPerfGroup OBJECT-GROUP OBJECTS { lmpCcHCHelloReceived, lmpCcHCHelloSent, lmpCcConfigReceived, lmpCcConfigSent, lmpCcConfigRetransmit, lmpCcLinkSummaryReceived, lmpCcLinkSummarySent, lmpCcLinkSummaryRetransmit, lmpCcChannelFailReceived, lmpCcChannelFailSent, lmpDataBearingLinkTestReceived, lmpDataBearingLinkTestSent } STATUS current DESCRIPTION "Collection of objects needed for providing performance information about LMP interfaces and data-bearing links." ::= { lmpGroups 5 } lmpTeLinkGroup OBJECT-GROUP OBJECTS { lmpRemoteTeLinkId, lmpRemoteTeLinkType, lmpTeLinkEncodingType, lmpTeLinkBitRate, lmpTeLinkWavelength, lmpTeLinkAdminStatus, lmpTeLinkOperStatus, lmpTeLinkRowStatus, lmpTeLinkStorageType } STATUS current DESCRIPTION "Collection of objects needed for TE link configuration." ::= { lmpGroups 6 } lmpDataBearingLinkGroup OBJECT-GROUP OBJECTS { lmpDataBearingLinkType, Dubuc et al. Expires August 2001 [Page 44] Internet Draft MPLS LMP MIB February 23, 2001 lmpDataBearingLinkRemoteIfId, lmpDataBearingLinkCcPreemptibility, lmpDataBearingLinkOperStatus, lmpDataBearingLinkAdminStatus, lmpDataBearingLinkRowStatus, lmpDataBearingLinkStorageType, lmpDataBearingLinkTrapEnable } STATUS current DESCRIPTION "Collection of objects needed for data-bearing link configuration." ::= { lmpGroups 7 } lmpNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { lmpTeLinkPropertyMismatch, lmpDataBearingLinkPropertyMismatch, lmpControlChannelSwitchover, lmpUnprotected, lmpDataBearingLinkDegraded } STATUS current DESCRIPTION "Set of notifications implemented in this module. None is mandatory." ::= { lmpGroups 8 } -- End of LMP-MIB END 11. Security Considerations It is clear that this MIB is potentially useful for monitoring of LMP enabled devices. This MIB can also be used for configuration of cer- tain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. At this writing, no security holes have been identified beyond those that SNMP Security [SNMPArch] is itself intended to address. These relate to primarily controlled access to sensitive information and the ability to configure a device - or which might result from opera- tor error, which is beyond the scope of any security architecture. There are a number of management objects defined in this MIB which have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure Dubuc et al. Expires August 2001 [Page 45] Internet Draft MPLS LMP MIB February 23, 2001 environment without proper protection can have a negative effect on network operations. The use of SNMP Version 3 is recommended over prior versions, for configuration control, as its security model is improved. SNMPv1 or SNMPv2 are by themselves 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 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 leg- itimate rights to indeed GET or SET (change/create/delete) them. There are a number of managed objects in this MIB that may contain information that may be sensitive from a business perspective, in that they represent a customer's interface to the G-MPLS network. Allowing uncontrolled access to these objects could result in mali- cious and unwanted disruptions of network traffic or incorrect confi- gurations for these customers. There are no objects that are particu- larly sensitive in their own right, such as passwords or monetary amounts. 12. Acknowledgments The general structure of this draft, including sections on applica- bility of Interface Group and relationship with ifTable, has been modeled around draft-ietf-mpls-lsr-mib-06.txt. The authors wish to thank Dmitry Ryumkin. 13. References [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., Rekhter, Y., Berger, L., Rajagopalan, B., Basak, D., Sandick, H., Zinin, A., and Banarjee, A., "Link Management Protocol", Internet Draft , February 2001. [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., Dubuc et al. Expires August 2001 [Page 46] Internet Draft MPLS LMP MIB February 23, 2001 Bernstein, G., Drake, J., Fan, Y., Kompella, K., Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., Saha, D., Sharma, V., Swallow, G., and Tang, Z., "Generalized MPLS Signaling Function Description", Internet Draft , November 2000. [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., "Link Bundling in MPLS Traffic Engineering", Internet Draft , November 2000. [BUNDLE-MIB] Dubuc, M., "Link Bundling MIB", Internet Draft , 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 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS,(http://www.isi.edu/in- notes/iana/assignements/address-family-numbers), for MIB see: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib [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 Identification of Management Information for TCP/IP- based Internets", RFC 1155, May 1990. [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, March 1991. [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Dubuc et al. Expires August 2001 [Page 47] Internet Draft MPLS LMP MIB February 23, 2001 Management Protocol (SNMPv3)", RFC 2574, April 1999. [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. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [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. [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. [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. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", Dubuc et al. Expires August 2001 [Page 48] Internet Draft MPLS LMP MIB February 23, 2001 RFC 1906, January 1996. [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998. [SNMPv3USM] 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, "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. [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB", RFC 2863, June 2000. [BCP14] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 14. Authors' Addresses Martin Dubuc Sudheer Dharanikota edgeflow, Inc. Nayna Networks, Inc. 329 March Rd. 157 Topaz Street Kanata, ON, CANADA K2K 2E1 Milipitas, CA 95035 Phone: +1-613-270-9279 x253 Phone: +1-408-956-8000 x357 Email: martin.dubuc@edgeflow.com Email: sudheer@nayna.com Thomas D. Nadeau Jonathan P. Lang Cisco Systems, Inc. Calient Networks Dubuc et al. Expires August 2001 [Page 49] Internet Draft MPLS LMP MIB February 23, 2001 350 Apollo Drive 25 Castilian Drive Chelmsford, MA 01824 Goleta, CA 93117 Phone: +1-978-244-3051 Email: jplang@calient.net Email: tnadeau@cisco.com Evan McGinnis Calient Networks 5853 Rue Ferrari San Jose, CA 95138 Email: evan@calient.net 15. Full Copyright Statement Copyright (C) The Internet Society (2000). 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 docu- ment itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of develop- ing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. Dubuc et al. Expires August 2001 [Page 50]