Internet Draft Andy Bierman Cisco Systems, Inc. 14 July 2000 Performance Measurement Capabilities MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [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. Distribution of this document is unlimited. Please send comments to the authors. 1. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. 2. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In Internet-Draft PM Capabilities MIB July 2000 particular, it describes managed objects used for classifying and characterizing the performance measurement (PM) capabilities of various standard and proprietary PM techniques. 3. Table of Contents 1 Copyright Notice ................................................ 1 2 Abstract ........................................................ 1 3 Table of Contents ............................................... 2 4 The SNMP Management Framework ................................... 3 5 Overview ........................................................ 4 5.1 Terms ......................................................... 4 5.1.1 Performance Measurement (PM) ................................ 4 5.1.2 PM Data ..................................................... 4 5.1.3 APM Device .................................................. 4 5.1.4 TPM Device .................................................. 5 5.1.5 PM Collection Point ......................................... 5 5.1.6 PM Study Class .............................................. 5 5.1.7 PM Study .................................................... 5 5.1.8 PM Report Class ............................................. 6 5.1.9 APM Report .................................................. 6 5.1.10 TPM Report ................................................. 6 5.1.11 PM Location ................................................ 6 5.1.12 PM Class ................................................... 6 5.2 Relationship to RMON-2 MIB .................................... 7 5.3 Relationship to IPPM .......................................... 7 5.4 Relationship to Other MIBs .................................... 7 6 PM Framework Components ......................................... 7 6.1 Performance Criteria .......................................... 7 6.2 Performance Measurement Granularity ........................... 8 6.3 Network Traffic Selection Criteria ............................ 8 6.4 Network Traffic Generation Configuration ...................... 8 6.5 Set of Metrics ................................................ 8 6.6 PM Study Class Capabilities ................................... 8 6.7 PM Collection Point Location .................................. 9 6.8 PM Study Configuration ........................................ 9 6.9 PM Study Results Storage and Retrieval ........................ 9 7 PM Caps MIB Groups .............................................. 9 7.1 PM Capabilities ............................................... 9 8 Definitions ..................................................... 9 9 Intellectual Property ........................................... 27 10 References ..................................................... 27 11 Security Considerations ........................................ 31 12 Author's Address ............................................... 32 13 Full Copyright Statement ....................................... 33 Expires January 2001 [Page 2] Internet-Draft PM Capabilities MIB July 2000 4. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in RFC 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed 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 Expires January 2001 [Page 3] Internet-Draft PM Capabilities MIB July 2000 information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 5. Overview There is a need for a standardized way of characterizing the performance measurement capabilities of remote monitoring tools which provide statistics based on these measurements. There are many different techniques for measuring and characterizing the performance of specific network-based applications available at this time. A standardized framework for describing the capabilities of a particular technique is needed as a pre-requisite for a standardized Performance Measurement results reporting framework. This memo addresses the specific requirements of the Performance Measurement capabilities framework. Other aspects of this framework, such as configuration and results reporting are not addressed in this memo. 5.1. Terms Some new terms are used throughout this document: 5.1.1. Performance Measurement (PM) This term refers to any implementation-specific PM Data collection mechanism, for the purpose of instrumenting the Application Performance Measurement (APM) MIB [APM] and/or the Transport Performance Metrics (TPM) MIB [TPM]. 5.1.2. PM Data The actual measurements, kept in some internal representation, collected from one or more PM Collection Points. This data is converted into one or more APM and/or TPM Reports, in an implementation-specific manner. 5.1.3. APM Device A device which contains an SNMP agent which implements the APM MIB. For the purpose of the standard, the APM device is the entity that is reporting the APM results, in the form of standard MIB objects. An APM Device can obtain PM data from one or more PM Collection Points. Expires January 2001 [Page 4] Internet-Draft PM Capabilities MIB July 2000 5.1.4. TPM Device A device which contains an SNMP agent which implements the TPM MIB. For the purpose of the standard, the TPM device is the entity that is reporting the TPM results, in the form of standard MIB objects. A TPM Device can obtain PM data from one or more PM Collection Points. 5.1.5. PM Collection Point The general location, within the spectrum of possible vantage points, that PM Data is collected, for one or more APM or TPM Studies (and perhaps more than one APM or TPM device). The interaction between an APM or TPM device and a PM Collection Point is outside the scope of this standard. 5.1.6. PM Study Class The unique set of mechanisms and parameters that classifies and identifies a particular APM or TPM collection capability. E.g., - the set of protocols collected - test attributes (standard and proprietary) - collection technique(s) - PM Collection Point information - report capabilities - vendor-specific Study Class ID 5.1.7. PM Study This is an instantiation of a particular PM Study Class, for the purpose of generating APM and/or TPM reports. Some parameters, such as: - the dataSource to monitor - any resource restrictions to enforce - the specific set of result data to collect are relevant only in the context of an PM Study, not a PM Study Class. Expires January 2001 [Page 5] Internet-Draft PM Capabilities MIB July 2000 5.1.8. PM Report Class The type of APM or TPM report produced on behalf of a particular PM Study Class. E.g., - distribution-based aggregation - statistica-based aggregation - exception-based reporting 5.1.9. APM Report The set of result data for a particular PM Study. This is in the form of standard MIB objects and notifications in the APM MIB [APM]. 5.1.10. TPM Report The set of result data for a particular PM Study. This is in the form of standard MIB objects and notifications in the TPM MIB [TPM]. 5.1.11. PM Location The notion of where a PM Collection Point is obtaining PM Data. At the highest level, the possible locations are: - client - network - server 5.1.12. PM Class At the highest level, there are three classes of PM technology. - passive collection No test traffic is introduced into the system being measured. PM Data is derived from observable 'user activity' in the actual operating environment. - active collection Some form of test traffic is introduced into the system being measured. PM Data is derived from measured attributes of this test traffic. Expires January 2001 [Page 6] Internet-Draft PM Capabilities MIB July 2000 - built-in collection Measurement mechanisms are somehow embedded in actual network traffic, for the purpose of PM Data collection. PM Data is derived from measured attributes, via these built-in mechanisms. 5.2. Relationship to RMON-2 MIB This MIB uses the protocolDirTable [RFC2021] to identify the protocols which are relevant to a particular PM Study Class. Implementation of the protocolDirectoryGroup is required. 5.3. Relationship to IPPM This MIB uses the Metric definitions found in IPPM documents ([RFC2330] [RFC2678] [RFC2679] [RFC2680] [RFC2681]) to define derived metrics for use with the APM and TPM MIBs. 5.4. Relationship to Other MIBs This MIB assumes that a standard Application Performance Measurement MIB [APM] will be produced, which will provide support for basic configuration and collection of APM Reports. This MIB also assumes that a standard Transport Performance Measurement MIB [TPM] will be produced, which will provide additional 'drill-down' support for transport layer protocols and additional metrics not directly supported by the APM MIB. 6. PM Framework Components A PM Study is executed and reported within the PM Framework. Usually, some sort of network infrastructure is assumed, in which client devices, application servers, forwarding devices, and one or more PM monitoring devices are connected. However, non-networking based methodologies can also be used. Some basic attributes of the PM Framework are listed below. 6.1. Performance Criteria A set of network, transport, and/or application performance criteria is needed, based on some combination of network traffic attributes. The specification and evaluation of performance test results is beyond the scope of this document. Expires January 2001 [Page 7] Internet-Draft PM Capabilities MIB July 2000 6.2. Performance Measurement Granularity Each PM Study Class explicitly defines the granularity of the test, in terms of the purpose, selected metrics, and other attributes. 6.3. Network Traffic Selection Criteria For PM techniques which monitor or generate network traffic, a set of rules is needed which specifies which packets will be included for measurement in a particular performance test. This includes device attributes such as interface identity, and packet attributes such as VLAN ID, QoS value, IP subnet or host addresses, application type(s), and application payload. 6.4. Network Traffic Generation Configuration Active PM techniques require that the traffic generation mechanism(s) be properly configured prior to execution of any PM Studies. These configuration requirements are outside the scope of this document. 6.5. Set of Metrics For each PM Study Class, there are one or more metrics, appropriate for the associated network traffic and performance selection criteria, which are measured by the APM and/or TPM device(s) used for an individual PM Study. 6.6. PM Study Class Capabilities For each PM Study Class supported by an APM or TPM Device, there is a set of capabilities associated with the selected set of metrics and performance criteria. There is also a set of possible report output capabilities associated with each class. Expires January 2001 [Page 8] Internet-Draft PM Capabilities MIB July 2000 6.7. PM Collection Point Location The physical location of each PM Collection Point is an important attribute of each PM Study Class. +------------+ +---------+ +----------+ +----------+ | | | Last | | Last Hop | | | | Client |<-->| Hop for |<--> ... <-->| for Net |<-->| Network | | | | Client | | Service | | Service | +------------+ +---------+ +----------+ +----------+ <------------- Measurement Device Location ------------> For the purposes of this MIB, a PM Collection Point resides in either the 'client', the 'network', or the 'server'. 6.8. PM Study Configuration Each PM Study may require some combination of generic and test-specific configuration commands in order to prepare the network environment for measurement. Specific PM Study configuration mechanisms are beyond the scope of this document. 6.9. PM Study Results Storage and Retrieval Each APM or TPM Device must be able to store the APM or TPM Reports generated on behalf of each PM Study, and convey these reports to a management application. The specification of these mechanisms are beyond the scope of this document. 7. PM Caps MIB Groups The PM Caps MIB contains one MIB group. 7.1. PM Capabilities This group contains MIB objects used to report the capabilities of the PM Study Classes supported by a particular APM or TPM Device. 8. Definitions PMCAPS-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32 Expires January 2001 [Page 9] Internet-Draft PM Capabilities MIB July 2000 FROM SNMPv2-SMI TruthValue, RowPointer FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB rmon FROM RMON-MIB protocolDirLocalIndex, protocolDirectoryGroup PROM RMON2-MIB; pmCapsMIB MODULE-IDENTITY LAST-UPDATED "200007140000Z" ORGANIZATION "IETF RMONMIB WG" CONTACT-INFO " Andy Bierman Cisco Systems, Inc. RMONMIB WG Chair and PMCAPS MIB Editor Postal: 170 West Tasman Drive San Jose, CA USA 95134 Tel: +1 408 527-3711 E-mail: abierman@cisco.com Send comments to Mailing list subscription information: http://www.ietf.org/mailman/listinfo/rmonmib " DESCRIPTION "The MIB module for representing Performance Measurement Capabilities." REVISION "200007140000Z" DESCRIPTION "Initial Version of the Performance Measurement Capabilities MIB." ::= { rmon 25 } pmCapsMIBObjects OBJECT IDENTIFIER ::= { pmCapsMIB 1 } pmCaps OBJECT IDENTIFIER ::= { pmCapsMIBObjects 1 } pmMetrics OBJECT IDENTIFIER ::= { pmCapsMIBObjects 2 } -- -- PM Metric Table -- Expires January 2001 [Page 10] Internet-Draft PM Capabilities MIB July 2000 pmMetricTable OBJECT-TYPE SYNTAX SEQUENCE OF PmMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row per PM Metric supported by this agent, and should be populated during system initialization." ::= { pmCaps 1 } pmMetricEntry OBJECT-TYPE SYNTAX PmMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular PM Metric." INDEX { pmMetricID } ::= { pmMetricTable 1 } PmMetricEntry ::= SEQUENCE { pmMetricID OBJECT IDENTIFIER, pmMetricType INTEGER, pmMetricDirType INTEGER, pmMetricName SnmpAdminString, pmMetricReference SnmpAdminString } pmMetricID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index for this entry. This object identifies the standard or vendor-specific registration OBJECT IDENTIFER defined for a particular PM metric." ::= { pmMetricEntry 1 } pmMetricType OBJECT-TYPE SYNTAX INTEGER { other(1), connectMetric(2), delayMetric(3), lossMetric(4) } MAX-ACCESS read-only Expires January 2001 [Page 11] Internet-Draft PM Capabilities MIB July 2000 STATUS current DESCRIPTION "The basic type of metric indicated by this entry. The value 'other(1)' indicates that this metric cannot be characterized by any of the remaining enumerations specified for this object. The value 'connectMetric(2)' indicates that this metric measures connectivity characteristics. The value 'delayMetric(3)' indicates that this metric measures delay characteristics. The value 'lossMetric(4)' indicates that this metric measures loss characteristics." ::= { pmMetricEntry 2 } pmMetricDirType OBJECT-TYPE SYNTAX INTEGER { oneWay(1), twoWay(2), multiWay(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The directional characteristics of the this metric. The value 'oneWay(1)' indicates that this metric is measured with some sort of uni-directional test. The value 'twoWay(2)' indicates that this metric is measured with some sort of bi-directional test. The value 'multiWay(3)' indicates that this metric is measured with some combination of uni-directional and/or bi- directional tests." ::= { pmMetricEntry 3 } pmMetricName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION Expires January 2001 [Page 12] Internet-Draft PM Capabilities MIB July 2000 "The textual name of this metric." ::= { pmMetricEntry 4 } pmMetricReference OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains a reference to the document which defines this metric. If this document is available online via electronic download, then a URL should be specified in this object. For example, if this pmMetricEntry identified the IPPM metric 'Type-P-Round-Trip-Delay', then this object should contain the value 'http://www.ietf.org/rfc/rfc2681.txt'." ::= { pmMetricEntry 5 } -- -- PM Study Class Table -- pmStudyClassTable OBJECT-TYPE SYNTAX SEQUENCE OF PmStudyClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row per PM Study Class supported by this APM/TPM Device, and should be populated during system initialization." ::= { pmCaps 2 } pmStudyClassEntry OBJECT-TYPE SYNTAX PmStudyClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular PM Study Class." INDEX { pmStudyClassID } ::= { pmStudyClassTable 1 } PmStudyClassEntry ::= SEQUENCE { pmStudyClassID OBJECT IDENTIFIER, pmStudyClassMeasLoc BITS, Expires January 2001 [Page 13] Internet-Draft PM Capabilities MIB July 2000 pmStudyClassMeasType BITS, pmStudyClassCollectPts Integer32, pmStudyClassCollectCaps BITS, pmStudyClassOutputCaps BITS, pmStudyClassCtlTablePtr RowPointer } pmStudyClassID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index for this entry. This object identifier should specify the standard or vendor-specific registration OID for this PM Study Class." ::= { pmStudyClassEntry 1 } pmStudyClassMeasLoc OBJECT-TYPE SYNTAX BITS { pmClient(0), pmNetwork(1), pmServer(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The measurement location characteristics of the PM Data collection methodologies employed by this PM Study Class. If this PM Study class utilizes some sort of measurement technology located on the host machine being monitored, then the 'pmClient' BIT will be set. Note that this bit should only be set if any PM technology is installed on the client, in addition to the 'normal' protocol operations supported by that machine. If this PM Study class utilizes some sort of measurement technology located on one or more networking devices (e.g., routers, switches, RMON probes), then the 'pmNetwork' BIT will be set. If this PM Study class utilizes some sort of measurement technology located on the application server being monitored, then the 'pmServer' BIT will be set. Note that this bit should only be set if any PM technology is Expires January 2001 [Page 14] Internet-Draft PM Capabilities MIB July 2000 installed on the server, in addition to the 'normal' protocol operations supported by that machine." ::= { pmStudyClassEntry 2 } pmStudyClassMeasType OBJECT-TYPE SYNTAX BITS { pmPassive(0), pmActive(1), pmBuiltin(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type(s) of collection methodologies employed by this PM Study Class. If this PM Study class utilizes some sort of passive monitoring technology, (i.e., UI operations and/or protocol transactions of real users are measured) the 'pmPassive' BIT will be set. If this PM Study class utilizes some sort of active monitoring technology, (i.e., protocol transactions generated for the purpose of obtaining PM Data) the 'pmPassive' BIT will be set. If this PM Study class utilizes some sort of built-in monitoring technology, (i.e., UI operations and/or protocol transactions of real users are somehow altered to provide PM Data) the 'pmBuiltin' BIT will be set." ::= { pmStudyClassEntry 3 } pmStudyClassCollectPts OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of PM Collection Points utilized in this PM Study Class. If this is a variable quantity, then this object should contain the minimum number needed for this PM Study Class to function." ::= { pmStudyClassEntry 4 } pmStudyClassCollectCaps OBJECT-TYPE SYNTAX BITS { Expires January 2001 [Page 15] Internet-Draft PM Capabilities MIB July 2000 pmCollectTrans(0), pmCollectApp(1), pmCollectFlow(2), pmCollectNonNet(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies some generic characteristics of the collection methodologies employed by this PM Study Class. If this PM Study class utilizes some sort of transport layer PM Data collection technology, then the 'pmCollectTrans' BIT will be set. If this PM Study class utilizes some sort of application layer PM Data collection technology, then the 'pmCollectApp' BIT will be set. If this PM Study class utilizes PM Data collection technology based on monitoring of some sort of network flow summary information, then the 'pmCollectFlow' BIT will be set. If this PM Study class utilizes some sort of PM Data collection technology based on monitoring of non-network events, such as UI monitoring of window events, then the 'pmCollectNonNet' BIT will be set." ::= { pmStudyClassEntry 5 } pmStudyClassOutputCaps OBJECT-TYPE SYNTAX BITS { pmOutputOther(0), pmOutputApmDist(1), pmOutputApmStat(2), pmOutputApmHist(3), pmOutputApmFlow(4), pmOutputApmExcept(5), pmOutputApmProp(6), pmOutputTpmDist(7), pmOutputTpmStat(8), pmOutputTpmHist(9), pmOutputTpmExcept(10), pmOutputTpmProp(11) } Expires January 2001 [Page 16] Internet-Draft PM Capabilities MIB July 2000 MAX-ACCESS read-only STATUS current DESCRIPTION "The type(s) of APM and/or TPM Reports that this PM Study Class can provide. [ed. - this list will change as the APM and TPM MIBs are finalized.] If this PM Study class can generate standard reports not described by any of the provided BITS here, then the 'pmOutputOther' BIT will be set. If this PM Study class can generate distribution-oriented reports for application layer protocols, then the 'pmOutputApmDist' BIT will be set. If this PM Study class can generate statistics-oriented reports for application layer protocols, then the 'pmOutputApmStat' BIT will be set. If this PM Study class can generate historical analysis oriented reports for application layer protocols, then the 'pmOutputApmHist' BIT will be set. If this PM Study class can generate flow decomposition analysis oriented reports for application layer protocols, then the 'pmOutputApmFlow' BIT will be set. If this PM Study class can generate profile exception oriented reports for application layer protocols, then the 'pmOutputApmExcept' BIT will be set. If this PM Study class can generate vendor-specific proprietary reports for application layer protocols, in addition to standard reports, then the 'pmOutputApmProp' BIT will be set. If this PM Study class can generate distribution-oriented reports for transport layer protocols, then the 'pmOutputTpmDist' BIT will be set. If this PM Study class can generate statistics-oriented reports for transport layer protocols, then the 'pmOutputTpmStat' BIT will be set. If this PM Study class can generate historical analysis Expires January 2001 [Page 17] Internet-Draft PM Capabilities MIB July 2000 oriented reports for transport layer protocols, then the 'pmOutputTpmHist' BIT will be set. If this PM Study class can generate flow decomposition analysis oriented reports for transport layer protocols, then the 'pmOutputTpmFlow' BIT will be set. If this PM Study class can generate profile exception oriented reports for transport layer protocols, then the 'pmOutputTpmExcept' BIT will be set. If this PM Study class can generate vendor-specific proprietary reports for transport layer protocols, in addition to standard reports, then the 'pmOutputTpmProp' BIT will be set." ::= { pmStudyClassEntry 6 } pmStudyClassCtlTablePtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies a specific MIB table that can be used to configure detailed aspects of the collection or report processing functions for this PM Study Class. This object just identifies a particular row in the MIB table to use, not any particular agent which implements this MIB table. This agent may or may not contain an implementation of the specified MIB, and/or the specified MIB may not be accessible in the same views as the this MIB. If no appropriate row in a MIB table can be identified, then the value { 0 0 } is returned." ::= { pmStudyClassEntry 7 } -- -- PM Study Metric Table -- pmStudyMetricTable OBJECT-TYPE SYNTAX SEQUENCE OF PmStudyMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Expires January 2001 [Page 18] Internet-Draft PM Capabilities MIB July 2000 "This table contains one row for each metric supported by the specified PM Study Class, and should be populated during system initialization." ::= { pmCaps 3 } pmStudyMetricEntry OBJECT-TYPE SYNTAX PmStudyMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Metrics information related to a particular PM Study Class. The pmStudyClassID value in the index identifies the pmStudyClassEntry with the same index value." INDEX { pmStudyClassID } ::= { pmStudyMetricTable 1 } PmStudyMetricEntry ::= SEQUENCE { pmStudyMetricID OBJECT IDENTIFIER } pmStudyMetricID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the PM Metric associated with this PM Study, and contains the same value as the pmMetricID index for that pmMetricEntry." ::= { pmStudyMetricEntry 1 } -- -- PM Study Protocol Table -- pmStudyProtocolTable OBJECT-TYPE SYNTAX SEQUENCE OF PmStudyProtocolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row for each protocol supported by the specified PM Study Class, and should be populated during system initialization. Expires January 2001 [Page 19] Internet-Draft PM Capabilities MIB July 2000 This is an indication of the protocols the indicated PM Study Class is capable of measuring. The actual protocols present in a given APM or TPM Report may be a subset of the protocols identified in this table. This table contain entries which reference any protocol in the protocolDirTable. If the index of this entry identifies an internal node in the protocolDirTable, then the pmStudyProtocolIsSubtree object is relevant." ::= { pmCaps 4 } pmStudyProtocolEntry OBJECT-TYPE SYNTAX PmStudyProtocolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Protocol information about a particular PM Study Class. The pmStudyClassID value in the index identifies the pmStudyClassEntry with the same index value, associated with the list of protocols in this table. The protocolDirLocalIndex value identifies the protocolDirEntry which contains the same value in the protocolDirLocalIndex object." INDEX { pmStudyClassID, protocolDirLocalIndex } ::= { pmStudyProtocolTable 1 } PmStudyProtocolEntry ::= SEQUENCE { pmStudyProtocolIsSubtree TruthValue } pmStudyProtocolIsSubtree OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether or not this entry identifies one node or an entire subtree of the protocolDirTable. If set to 'true(1)' then the specified protocolDirEntry, and all its children, are supported by the specified PM Study Class. If set to 'false(2)', then the specified protocolDirEntry Expires January 2001 [Page 20] Internet-Draft PM Capabilities MIB July 2000 identified by this entry is supported by the PM Study Class." ::= { pmStudyProtocolEntry 1 } -- -- APM Metric Registry -- -- APM Avaiability Metric for all transaction types pmAppAvailMetric OBJECT-IDENTITY STATUS current DESCRIPTION "Metric Name: Type-P-APM-Availability Metric Definition: This metric characterizes the availability of a network service by measuring the percentage of successful transactions the network service delivers over a given time interval. This metric is calculated by first measuring the IPPM metric 'Type-P-Interval-Bidirectional-Connectivity' for the interval starting at the instant 'Src' initiates a transaction of Type-P with the 'Dst' host, and ending at the instant the last packet of the transaction has been received. In addition to successful connectivity over this interval, the particular application request must also succeed, for a transaction to be considered successful. If either condition is false, then that transaction is considered to be unsuccessful. The derived metric is defined as the total number of successful transactions between Src and Dst, divided by the total number of transaction attempts between Src and Dst, during the time interval dT. Metric Parameters: Src, the network address of a host Dst, the network address of a host dT, a time interval Expires January 2001 [Page 21] Internet-Draft PM Capabilities MIB July 2000 Metric Units: Percentage Mapping of Type P: Type P refers to an application protocol encapsulation, identified by a specific protocolDirEntry. Metric Type: connectMetric(1) Metric Dir Type: twoWay(2)" REFERENCE "IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678], Section 5, September 1999." ::= { pmMetrics 1 } -- APM Responsiveness Metric for Transaction-oriented applications pmAppTransRespMetric OBJECT-IDENTITY STATUS current DESCRIPTION "Metric Name: Type-P-APM-Transaction-Responsiveness Metric Definition: This metric characterizes the speed at which a transaction-oriented network application delivers a requested service, by measuring the speed of individual application transactions. This metric is calculated by utilizing a variation of the IPPM metric 'Type-P-Round-trip-Delay'. The total transaction time (dT) is determined by summing all the packet transactions of Type-P between the Src and Dst hosts. The bi-directional flight times are measured (as specified by the IPPM metric definition), but the server response time for each request is included in the measurement. The derived metric is defined as the total number of tenths of seconds for the transaction between Src and Dst to complete. Metric Parameters: Src, the network address of a host Dst, the network address of a host dT, a time interval Expires January 2001 [Page 22] Internet-Draft PM Capabilities MIB July 2000 Metric Units: Tenths of seconds Mapping of Type P: Type P refers to an application protocol encapsulation, identified by a specific protocolDirEntry, which is characterized as a transaction-oriented protocol. Metric Type: delayMetric(2) Metric Dir Type: twoWay(2)" REFERENCE "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681], Section 2, September 1999." ::= { pmMetrics 2 } -- APM Responsiveness Metric for Throughput-oriented applications -- [ed., in progress] pmAppTputRespMetric OBJECT-IDENTITY STATUS current DESCRIPTION "Metric Name: Type-P-APM-Throughput-Responsiveness Metric Definition: This metric characterizes the speed at which a throughput-oriented network application delivers a requested service, by measuring the transfer rate of individual application transactions. This metric is calculated by ... [rest of para is TBD] The derived metric is normalized and inverted, into units of 'seconds per terabit'. For transactions up to one terabit in size, it is defined as the total number of seconds it would take for the transaction between Src and Dst to complete, if the transaction size included one terabit of data. For transactions over one terabit in size, it is defined as the average number of seconds for the transaction between Src and Dst to complete, for each terabit of data. E.g., a transfer rate of 2Kbps equals 500,000,000 and a transfer rate of 1Gbps = 1000. Expires January 2001 [Page 23] Internet-Draft PM Capabilities MIB July 2000 Metric Parameters: Src, the network address of a host Dst, the network address of a host dT, a time interval B, a number of terabits Metric Units: Seconds Per Terabit Mapping of Type P: Type P refers to an application protocol encapsulation, identified by a specific protocolDirEntry, which is characterized as a throughput-oriented protocol. Metric Type: delayMetric(2) Metric Dir Type: twoWay(2)" REFERENCE "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681], Section 2, September 1999." ::= { pmMetrics 3 } -- APM Responsiveness Metric for Stream-oriented applications -- [ed., in progress] pmAppStreamRespMetric OBJECT-IDENTITY STATUS current DESCRIPTION "Metric Name: Type-P-APM-Stream-Responsiveness Metric Definition: This metric characterizes the 'quality' at which a streaming-oriented network application delivers a requested service, by measuring the percentage of time that the service is degraded or interrupted to the total time to deliver the service. [Rest of definition TBD] Metric Parameters: Src, the network address of a host Dst, the network address of a host Metric Units: [TBD] Expires January 2001 [Page 24] Internet-Draft PM Capabilities MIB July 2000 Mapping of Type P: Type P refers to an application protocol encapsulation, identified by a specific protocolDirEntry, which is characterized as a streaming-oriented protocol. Metric Type: delayMetric(2) Metric Dir Type: twoWay(2)" REFERENCE "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681], Section 2, September 1999." ::= { pmMetrics 4 } -- -- TPM Metric Registry [TBD] -- -- placeholder for notifications pmCapsNotifications OBJECT IDENTIFIER ::= { pmCapsMIB 2 } -- conformance information pmCapsConformance OBJECT IDENTIFIER ::= { pmCapsMIB 3 } pmCapsCompliances OBJECT IDENTIFIER ::= { pmCapsConformance 1 } pmCapsGroups OBJECT IDENTIFIER ::= { pmCapsConformance 2 } -- compliance statements pmCapsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which implement version 1 of the APM Capabilities MIB." MODULE -- this module MANDATORY-GROUPS { protocolDirectoryGroup, pmCapsGroup } ::= { pmCapsCompliances 1 } -- MIB groupings pmCapsGroup OBJECT-GROUP OBJECTS { Expires January 2001 [Page 25] Internet-Draft PM Capabilities MIB July 2000 pmMetricType, pmMetricDirType, pmMetricName, pmMetricReference, pmStudyClassMeasLoc, pmStudyClassMeasType, pmStudyClassCollectPts, pmStudyClassCollectCaps, pmStudyClassOutputCaps, pmStudyClassCtlTablePtr, pmStudyMetricID, pmStudyProtocolIsSubtree } STATUS current DESCRIPTION "The collection of objects which are used to represent application performance measurement capabilities, for which a single agent provides management information." ::= { pmCapsGroups 1 } END Expires January 2001 [Page 26] Internet-Draft PM Capabilities MIB July 2000 9. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards- related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 10. References [APM] Waldbusser, S., "Application Performance Measurement MIB", , May 2000. [TPM] Dietz, R., "Transport Performance Metrics MIB", , May 2000. [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, STD 16, Performance Systems International, Hughes LAN Systems, May 1990. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, STD 15, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. Expires January 2001 [Page 27] Internet-Draft PM Capabilities MIB July 2000 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, STD 16, Performance Systems International, Hughes LAN Systems, March 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March 1991. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, 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, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [RFC2021] S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", RFC 2021, International Network Services, January 1997. [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2026, Harvard University, October, 1996. [RFC2330] Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, "Framework for IP Performance Metrics", RFC 2330, May 1998. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Expires January 2001 [Page 28] Internet-Draft PM Capabilities MIB July 2000 Inc., Ericsson, Cisco Systems, April 1999. [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 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, IBM T. J. Watson Research, 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, IBM T. J. Watson Research, BMC Software, Inc., Cisco Systems, Inc., April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., Expires January 2001 [Page 29] Internet-Draft PM Capabilities MIB July 2000 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999. [RFC2678] Mahdavi, J., and V. Paxson, "IPPM Metrics for Measuring Connectivity", RFC 2678, September 1999. [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, A One-Way Delay Metric for IPPM", RFC 2679, September 1999. [RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, A One-Way Packet Loss Metric for IPPM", RFC 2680, September 1999. [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Metric for IPPM", RFC 2681, September 1999. Expires January 2001 [Page 30] Internet-Draft PM Capabilities MIB July 2000 11. Security Considerations There are no management objects defined in this MIB that have a MAX- ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is 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 RFC 2574 [RFC2574] and the View- based Access Control Model RFC 2575 [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. Expires January 2001 [Page 31] Internet-Draft PM Capabilities MIB July 2000 12. Author's Address Andy Bierman Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA Phone: +1 408-527-3711 Email: abierman@cisco.com Expires January 2001 [Page 32] Internet-Draft PM Capabilities MIB July 2000 13. 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 document 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 developing 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. Expires January 2001 [Page 33]