[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 03 04 05 06 07 08 09 10 11 12 13 14 RFC 4150

Internet Draft                                            Russell Dietz
                                                             Hifn, Inc.
                                                            Robert Cole
                                                              AT&T Labs
                                                          June 10, 2002



                   Transport Performance Metrics MIB



                  <draft-ietf-rmonmib-tpm-mib-06.txt>


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 mate-
   rial 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.

   This document is an Internet-Draft.  Internet-Drafts are working doc-
   uments of the Internet Engineering Task Force (IETF), its areas, and
   its working groups.  Note that other groups may also distribute work-
   ing documents as Internet-Drafts.

   Distribution of this document is unlimited. Please send comments to
   the authors, <rdietz@hifn.com> and <rgcole@att.com>.

1.  Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.




R. Dietz, R. Cole       Expires December 10, 2002               [Page 1]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


2.  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 used
   for monitoring selectable performance metrics and statistics derived
   from the monitoring of network packets and sub-application level
   transactions.  The metrics are defined through reference to existing
   IETF, ITU and other standards organizations' documents.  The monitor-
   ing covers both passive and active traffic generation sources.









































R. Dietz, R. Cole       Expires December 10, 2002               [Page 2]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


3.  Table of Contents

1.  Copyright Notice . . . . . . . . . . . . . . . . . . . . . . . .   1
2.  Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
3.  Table of Contents  . . . . . . . . . . . . . . . . . . . . . . .   3
4.  The SNMP Management Framework  . . . . . . . . . . . . . . . . .   4
5.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
5.1.  Terms  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
5.2.  Report Aggregations  . . . . . . . . . . . . . . . . . . . . .   7
5.3.  Structure of the MIB . . . . . . . . . . . . . . . . . . . . .   7
5.4.  Statistics for Aggregation of Data - Conventions . . . . . . .   8
5.5.  Relationship to the Remote Monitoring MIB  . . . . . . . . . .   8
5.6.  Relationship to RMON MIB Protocol Identifier Reference . . . .   8
5.7.  Relationship to Standards-Based Performance Metric Refer-
ences  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
5.8.  Relationship to Application Performance Measurement MIB  . . .   9
6.  Statistics Perspective . . . . . . . . . . . . . . . . . . . . .   9
6.1.  Statistics Structure . . . . . . . . . . . . . . . . . . . . .  10
6.2.  Statistics Analysis  . . . . . . . . . . . . . . . . . . . . .  11
7.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
8.  Intellectual Property  . . . . . . . . . . . . . . . . . . . . .  50
9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . .  50
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . .  51
11. Security Considerations  . . . . . . . . . . . . . . . . . . . .  53
12. Author's Address . . . . . . . . . . . . . . . . . . . . . . . .  54
A.  Full Copyright Statement . . . . . . . . . . . . . . . . . . . .  54

























R. Dietz, R. Cole       Expires December 10, 2002               [Page 3]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


4.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major compo-
   nents:

    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
        STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
        1215 [RFC1215].  The second version, called SMIv2, is described
        in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
        STD 58, RFC 2580 [RFC2580].

    o   Message protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1 and
        described in STD 15, RFC 1157 [RFC1157].  A second version of
        the SNMP message protocol, which is not an Internet standards
        track protocol, is called SNMPv2c and described in RFC 1901
        [RFC1901] and RFC 1906 [RFC1906].  The third version of the mes-
        sage 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 STD 15, RFC 1157 [RFC1157].  A second set of proto-
        col 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
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process.  However, this loss of machine



R. Dietz, R. Cole       Expires December 10, 2002               [Page 4]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


   readable information is not considered to change the semantics of the
   MIB.

5.  Overview

   This document continues the architecture created in the RMON MIB
   [RFC2021] by providing a major feature upgrade, primarily by provid-
   ing new metrics and studies to assist in the analysis of performance
   for transaction flows in the network, in direct relationship to the
   transporting of application layer protocols.

   Performance monitoring agents have been widely used to analyze the
   parameters and metrics related to the perceived performance of dis-
   tributed applications and services in networks. The metrics collected
   by these agents has ranged from basic response time to a combination
   of metrics related to the loss and re-transmission of datagrams and
   PDUs. While the metrics are becoming more useful in the implementa-
   tion of service level monitoring and troubleshooting tools, the lack
   of a standard method to report these in has limited the deployment to
   very specific customer needs and areas.

   This document is intended to create a general framework for the col-
   lection and reporting of performance related metrics on transaction
   flows in a network. The MIB in this document in directly linked to
   the current RMON-2 MIB [RFC2021] and uses the Protocol Directory as a
   key component in reporting the layering involved in the sub-applica-
   tion level transaction flows.

   The specific objectives of this document are to:

      + Provide a drill-down capability to compliment the user-perceived
      monitoring defined within the APM MIB [APM]. This capability is
      intended to support trouble resolution, further characterization
      of performance, and a finer granularity of monitoring capabili-
      ties. The APM MIB provides a method for retrieving aggregated mea-
      surement data of the end-user's perception of application-level
      performance. APM additionally provides thresholding and associated
      alarms in the event the end-user perceived performance degrades
      below defined thresholds.  The TPM MIB compliments the APM MIB
      capabilities by monitoring sub-application level transaction
      aspects not typically perceived by the end-user. As an example,
      APM MIB provides response time statistics of a typical web-browser
      application. This application typically consists of DNS transac-
      tion, TCP connection establishment (or multiple establishments),
      HTTP download of the base page and multiple downloads of the vari-
      ous embedded objects. Ideally TPM MIB would provide statistics on
      the performance aspects of these multiple sub-application level
      transactions.



R. Dietz, R. Cole       Expires December 10, 2002               [Page 5]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


      + Provide additional performance metrics and related statistics.
      For trouble shooting and a finer granularity of performance moni-
      toring, it is useful to provide measurements of additional metrics
      beyond those supported by the APM MIB.

      + Support standards based metrics and associated statistical
      aggregation by defining methods to reference those standards. The
      TPM MIB provides a capability to describe metrics by reference to
      appropriate IETF, ITU or other standards defining metrics. This
      capability is provided through the tpmMetricsDefTable.

      + Provide (as an option) a table storing the measurements of the
      metrics on a transaction by transaction basis. There are times
      when it is useful to have access to the raw measurements. The tpm-
      CurrTable optionally provides access to this capability.


   While this document outlines the basic measurements of performance in
   regard to the transporting of application flows, it does not attempt
   to measure or provide a means to measure the actual perceived perfor-
   mance of the application transactions or quality.  The detailed mea-
   surements of end-user perceived performance is directly related to
   this document and may be found in the APM MIB [APM].

   The objects defined in this document are intended as an interface
   between an RMON agent and an RMON management application and are not
   intended for direct manipulation by humans.  While some users may
   tolerate the direct display of some of these objects, few will toler-
   ate the complexity of manually manipulating objects to accomplish row
   creation.  These functions should be handled by the management appli-
   cation.

5.1.  Terms

   This document uses some terms that need introduction:

   DataSource
        A source of data for monitoring purposes. This term is used
        exactly as defined in the RMON-2 MIB [RFC2021].

   protocol
        A specific protocol encapsulation, as identified for monitoring
        purposes. This term is used exactly as defined in the RMON
        Protocol Identifiers document [RFC2074].

   performance metric
        A specific statistical reporting metric, as identified for
        monitoring purposes.  There can be several metrics reported by



R. Dietz, R. Cole       Expires December 10, 2002               [Page 6]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        an agent in the same implementation.  The metrics are
        extensible based on the agent implementation.

   application
        A network-based, high-level protocol performing useful work
        to an end-user of end-system.  Typically the application
        performs multiple request/response transactions to complete
        its work.  E.g., a web-application downloading a web page
        completes DNS, TCP-connect and multiple HTTP GET transactions
        prior to completing its task.

   transactions
        Elemental request/response transactions comprising more
        complex network-based applications.

5.2.  Report Aggregation

   This MIB provides functions to aggregate measurements into higher
   level summaries identical to the aggregation defined in the APM-MIB
   [APM]. In addition to temporal aggregation of data, the Textual Con-
   vention, TransactionAggregationType, is imported from the APM MIB,
   which specifies the nature of the spatial aggregation employed.


5.3.  Structure of the MIB

   The objects are arranged in the following groups:

       -- tpmCapabilitiesGroup

       -- tpmAggregateReportsGroup

       -- tpmCurrentReportsGroup

       -- tpmExceptionReportsGroup


   These groups are the basic unit of conformance.  If an agent imple-
   ments a group, then it must implement all objects in that group.
   While this section provides an overview of grouping and conformance
   information for this MIB, the authoritative reference for such infor-
   mation is contained in the MODULE-COMPLIANCE and OBJECT-GROUP macros
   later in this MIB.

   These groups are defined to provide a means of assigning object iden-
   tifiers, and to provide a method for implementers of managed agents
   to know which objects they must implement.




R. Dietz, R. Cole       Expires December 10, 2002               [Page 7]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


5.3.1. The tpmCapabilitiesGroup

   The tpmCapabilitiesGroup contains objects and tables which show the
   measurement protocol and metric capabilities of the agent. This group
   primarily consists of the tpmTransactionMetricDirTable and the tpm-
   MetricDefTable.

5.3.2. The tpmAggregateReportsGroup

   The tpmAggregateReportsGroup is used to provide the collection of
   aggregated statistical measurements for the configured report inter-
   vals. The tpmAggregateReportsGroup consists of the tpmAggrReportCn-
   trlTable and the tpmAggrReportTable.

5.3.3. The tpmCurrentReportsGroup

   The tpmCurrentReportsGroup is used to provide the collection of
   uncompleted measurements for the current configured report for those
   transactions caught in progress. A history of these transactions is
   also maintained once the current transaction has completed. The tpm-
   CurrentReportsGroup consists of the tpmCurrReportTable.

5.3.4. The tpmExceptionReportsGroup

   The tpmExceptionReportsGroup is used to link immediate notifications
   of transactions that exceed certain thresholds defined in the apmEx-
   ceptionGroup [APM]. This group reports the aggregated sub-application
   measurements for those applications exceeding thresholds.

5.4.  Statistics for Aggregation of Data - Conventions

   In order to measure the performance of traffic flows in a network,
   the proper analysis of a set of statistics is required.  Since a
   large majority of the statistics have a basis of time, the use of a
   simple statistical model is feasible.  Therefore, the MIB definitions
   within this document all use a basic set of statistical computed val-
   ues to assist in further analysis by a management application.

   The remaining subsections in this section detail the common struc-
   tured features the are applied to the performance metrics in the sta-
   tistical format described above.  The tpmMetricsDefTable (discussed
   below) describes the set of metrics supported in this MIB-set frame-
   work.

5.5.  Relationship to the Remote Monitoring MIB

   This document describes the implementation of an additional MIB for
   the support of performance related metrics within the framework of



R. Dietz, R. Cole       Expires December 10, 2002               [Page 8]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


   the RMON-2 MIB [RFC2021].  The objects and table defined in this MIB
   are an extension to the existing framework for the support of both
   Client/Server and Server push related applications and services.

5.6.  Relationship to RMON MIB Protocol Identifier Reference

   This document uses the Protocol Indentifiers outlined in the current
   Protocol Identifier Reference document, RFC 2074 [RFC2074].  The pro-
   tocol index values throughout the document are a direct reference to
   the same relationship that exists between the RMON-2 MIB [RFC2021]
   and the Protocol Identifier Reference document, RFC 2074 [RFC2074].
   An important extension of the Protocol Identification to application-
   level verbs is found in [APV].

5.7.  Relationship to Standards-Based Performance Metric References

   This document uses the tpmMetricsDefTable to describe the metrics
   supported by an instance of the TPM MIB.  The performance metric
   index values throughout the document are a direct reference to the
   metrics defined in that table.  The table define metrics by directly
   referencing other standards that provide definitive descriptions of
   the metric.

5.8.  Relationship to Application Performance Measurement MIB

   This document uses the apmReportControlIndex, appLocalIndex and apm-
   ReportIndex as outlined in the current Application Performance Mea-
   surement MIB draft document [APM].  These objects are used to create
   a reference link for the purpose of reporting transaction flow
   details on application level measurements.  As such, the TPM MIB is
   designed to provide a drill-down extension to the APM MIB. Further,
   it draws heavily on the ideas and designs laid out in the APM MIB.

6.  Statistics Perspective

   When dealing with time based measurements on application data packets
   it would be ideal if all the timestamps and related data could be
   stored and forwarded for later analysis.  However when faced with
   thousands of conversations per second on ever faster networks, stor-
   ing all the data, even if compressed, would take too much processing,
   memory, and manager download time to be practical.

   It is important to note that in dealing with network data we will be
   dealing with statistical populations and not samples.  Statistics
   books deal with both because the math is similar.  In collecting
   agent data a population, i.e. all the data, must be processed.
   Because of the nature of application protocols just sampling some of
   the packets will not give good results.  Missing just one critical



R. Dietz, R. Cole       Expires December 10, 2002               [Page 9]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


   packet, such as one that specified an ephemeral port on which data
   will be transmitted, or what application will be run, can cause much
   valid data to be lost.

   The time-based measurements the agent collects will come from examin-
   ing the entire group of data, i.e. the population. The population
   will be finite.  The agent will seek only to provide information that
   will describe the actual data. Analysis of that data will be left to
   the management station.

   The simplest form of representing a group of data is by frequency
   distributions, buckets. Statistics provides a great many ways of ana-
   lyzing this type of data and there are some rules in creating the
   buckets. First the range needs to be known. Second a bucket size
   needs to be determined. Fixed bucket sizes are best, while variable
   may be used if needed. However the statistics texts tend to only
   refer to operations of fixed size buckets. This method of describing
   data is expensive for a agent to implement. First the agent must pro-
   cess a great amount of data at a time. In storing the data, determine
   the range, then locating the buckets and then fill in the data after
   the fact takes a fair amount of storage and time. Fixing the range
   and bucket sizes in the beginning can be problematical as the agent
   may have to adjust the values for each of the applications it col-
   lects data on.  Such numbers can be in the thousands.  Additional
   complexity arises in adding new protocols and even in describing the
   buckets themselves to the management application. This is the
   approach taken in the APM MIB.

   A complimentary approach is to provide frequency distribution statis-
   tics. Frequency distribution statistics describes aggregation such as
   mean and standard deviation that can be obtained by summation func-
   tions on the individual data elements in a population.  Analysis of
   the data described by these functions has been greatly studied and
   interpretation of these values is available to anyone with an intro-
   duction to statistics.  In fact, frequency distributions are rou-
   tinely analyzed to generate these varied numbers which are then used
   for further analysis.  Also note that frequency distributions by
   their very nature provide an exact characterization of the data.
   Whereas buckets, will introduce error factors that are not present
   with direct analysis by a summation type formulas.  Because the TPM
   MIB provides a drill-down capability to the APM MIB is has to measure
   and store much more information than the APM MIB.  For this reason,
   and to compliment the APM MIB, the TPM MIB relies on statistical
   descriptions rather than a bucket description of the measurement
   data.

   The agent will provide data that can be used to calculate the most
   basic and useful statistical aggregates.  The agent will not perform



R. Dietz, R. Cole       Expires December 10, 2002              [Page 10]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


   the calculations and provide the statistical measurement directly.
   There are several reason why this is not desired. The first is that
   to find the final measurement can be expensive in terms of computa-
   tion and representation.  There are divisions and square roots and
   the measurements are expressed as floating point values.  The second
   is that by providing the variables to the statistical functions,
   those variables are scalable.  It is possible to combine smaller
   intervals into larger ones.

   An example is the arithmetic mean or average.  This is the sum of the
   data divided by the number of data elements.  The agent will provide
   the sum of the x and the number of elements N. The management station
   can perform the division to obtain the average.  Given two samples,
   they can be combined by adding the sum of the x's and by adding the
   number of elements to get a combined sum and number of elements.  The
   average formula then works just the same.  Also the sum of the x and
   the number of element variables are used in calculating other statis-
   tical measurement values as well.

6.1.  Statistics Structure

   The data statistical elements, datum, of the metric have been chosen
   to maximize the amount of data available while minimizing the amount
   of memory needed to store the statistic and minimizing the CPU pro-
   cessing requirement needed to generate the statistic.

   The statistic data structure contains five unsigned integer datum.

       N        count of the number of data points for the metric
       S(X)     sum of all the data point values for the metric
       S(X2)    sum of all the data point values squared for the metric
       Xmax     maximum data point value for the metric
       Xmin     minimum data point value  for the metric
       S(I*X)   sum of the datapoints multiplied by their order, i.e.,
                = SUM from i=1 to N { i*X sub i}

   A performance metric is used to describe events over a time interval.
   The measurement points can be processed immediately into the statis-
   tic and do not have to be stored for later processing.  For example
   to count the number of events in a time interval it is sufficient to
   increment a counter for each event, it is not necessary to cache all
   the events and then count them at the end of the interval. The
   statistic is also designed to be easily scalable in terms of combin-
   ing adjacent intervals.  For example if an agent created a specific
   statistic every 30 seconds and a user table interval was set to 60
   seconds, the 60 second statistic could be obtained by combining the
   two 30 second statistics.  The following rules will be applied when
   combining adjacent statistics.



R. Dietz, R. Cole       Expires December 10, 2002              [Page 11]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


             N         S(N)
             S(X)      S(S(X))
             S(X2)     S(S(X2))
             Xmax      MAX(Xmax)
             Xmin      MIN(Xmin)
             S(I*X)    S(I*X) + N*S(X) +S(I*X)
                       where the last two terms refer to the
                       statistics from the later 30 second period
                       and N is the count from the former 30 second
                       period.

   This structure gives a generic framework upon which the actual per-
   formance statistics will be defined.  Each specific statistical defi-
   nition must address the specific significance, if any, given to each
   of the metric datum.  While a specific metric definition should try
   to conform to the generic framework, it is acceptable for a metric
   datum to not be used, and to have no meaning, for a specific metric.
   In such cases the datum will default to a 0 value.

6.2.  Statistics Analysis

   The actual meaning of a specific statistical datum is determined by
   the definition of the specific statistic.  The following is a discus-
   sion of the operations and observations that can be performed on a
   generic metric.  This means that the following may or may not apply
   and/or have meaning when applied to any specific metric.

   The following observations and analysis techniques are not all inclu-
   sive.  Rather these are the ones we have come up with at the time of
   writing this document.

       + Number.

       + Frequency.

       + The time interval is the time interval specified in the control
       table.  It is not a metric datum, but it is associated with the
       metric sample.

       + Maximum

       + Minimum

       + Range

       + Arithmetic Mean

       + Root Mean Square



R. Dietz, R. Cole       Expires December 10, 2002              [Page 12]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


       + Variance

       + Standard Deviation

       + Slope of a least-squares line

   These are accessible from the statistical datum provided by this MIB.


7.  Definitions

--
-- RMON-2 Extensions for the Monitoring metrics related to the
-- performance of transporting traffic in networks.
--
--    TPM Metric Collection
--        * Application-to-Protocol transaction linkage
--        * Metric-to-Protocol linkage
--        * Metric study control
--        * Metrics for Client/Server Conversations
--

TPM-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32,
    Counter32, Unsigned32                         FROM SNMPv2-SMI
    MODULE-COMPLIANCE, OBJECT-GROUP               FROM SNMPv2-CONF
    SnmpAdminString                               FROM SNMP-FRAMEWORK-MIB
    RowStatus, TEXTUAL-CONVENTION, TimeStamp,
    TruthValue                                    FROM SNMPv2-TC
    rmon, OwnerString                             FROM RMON-MIB
    protocolDirLocalIndex, LastCreateTime,
    TimeFilter                                    FROM RMON2-MIB
    apmReportControlIndex, AppLocalIndex,
    ClientID, DataSourceOrZero,
    TransactionAggregationType                    FROM APM-MIB
    ClockSource, MicroSeconds                     FROM SSPM-MIB;


-- Transaction performance Monitoring MIB

tpm MODULE-IDENTITY
    LAST-UPDATED    "200206061500Z"  -- 10 June 2002
    ORGANIZATION    "IETF RMON MIB Working Group"
    CONTACT-INFO
            "E-mail: rmonmib@ietf.org
             Subscribe: rmonmib-request@ietf.org



R. Dietz, R. Cole       Expires December 10, 2002              [Page 13]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


                        w/ msg body: subscribe rmonmib

                     Russell Dietz
                     Hifn, Inc.
             Postal: 750 University Ave
                     Los Gatos, CA 95032-7695
                     USA
                Tel: +1 408 399-3623
                Fax: +1 408 399-3501
             E-mail: rdietz@hifn.com

                     Robert G. Cole
                     AT&T Labs
             Postal: 330 Saint Johns Street
                     2nd Floor
                     Havre de Grace, MD 21078
                     USA
                Tel: +1 410 939-8732
                Fax: +1 410 939-8732
             E-mail: rgcole@att.com"
    DESCRIPTION
            "This module defines managed objects for measuring traffic
            related transport performance metrics in relationship to
            application-level measurements in networks.  In
            particular, it describes managed objects used for
            monitoring selectable performance metrics and statistics
            derived from the monitoring of network packets and
            transport protocol states."
    REVISION        "200206061500Z"     -- 10 June 2002
    DESCRIPTION
        "The original version of this MIB, published as RFCXXXX."
    ::= { rmon 30 }                     -- this has NOT been assigned


--
-- Object Identifier Assignments
--

tpmCapabilities         OBJECT IDENTIFIER ::= { tpm 1 }
tpmReports              OBJECT IDENTIFIER ::= { tpm 2 }
tpmConformance          OBJECT IDENTIFIER ::= { tpm 3 }

tpmAggrReportCntrl      OBJECT IDENTIFIER ::= { tpmReports 1 }
tpmAggrReport           OBJECT IDENTIFIER ::= { tpmReports 2 }
tpmCurrReport           OBJECT IDENTIFIER ::= { tpmReports 3 }
tpmExcpReport           OBJECT IDENTIFIER ::= { tpmReports 4 }





R. Dietz, R. Cole       Expires December 10, 2002              [Page 14]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


--
-- Textual Conventions
--

TransactionMetricIndex ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "An index used to uniquely identify an entry in the
        tpmTransactionMetricDir table.  Each such entry defines
        the protocol transaction and metric instance to be
        monitored for a specific application."
    SYNTAX       Integer32 (1..65535)

MetricDefID ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "An index that identifies through reference to a specific
        performance metric.  The metrics are referenced
        through their type (connect, delay, loss, etc.), their
        directional characteristics (one-way, round trip, etc.),
        their name, their reference to a documented definition."
    SYNTAX       Unsigned32 (1..2147483647)


--
-- Extensions to the RMON-2 MIB for the collection of Performance
-- Metrics related to application traffic in a network.
--
-- In order to maintain the RMON 'look-and-feel', some of
-- the text from the RMON-2 and HC-RMON MIBs by
-- Steve Waldbusser have been used in this MIB.
--

--
-- The tpmCapabilitiesGroup
--
--
-- Transport Performance Transaction Metric Directory
--
-- This table is used to describe and link sets of performance
-- metrics and protocols to an entry in the application directory.
-- This table, with the tpmMetricDefTable, describes the capability of
-- the agent to collection sub-application level data related to each
-- entry in the apmAppDirectoryTable.
--

tpmClockResolution OBJECT-TYPE
    SYNTAX      MicroSeconds



R. Dietz, R. Cole       Expires December 10, 2002              [Page 15]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    MAX-ACCESS  read-only
    STATUS      current
    -- UNITS       Microseconds
    DESCRIPTION
        "A read only variable indicating the resolution
         of the measurements possible by this device."
    ::= { tpmCapabilities 1 }

tpmClockMaxSkew OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    -- UNITS       Seconds
    DESCRIPTION
        "A read only variable indicating the maximum
         offset error due to skew of the local clock
         over the time interval 86400 seconds, in seconds."
    ::= { tpmCapabilities 2 }

tpmClockSource OBJECT-TYPE
    SYNTAX      ClockSource
    MAX-ACCESS  read-only
    STATUS      current
    -- UNITS       MicroSeconds
    DESCRIPTION
        "A read only variable indicating the source of the clock.
         This is provided to allow a user to determine how accurate
         the timing mechanism is compared with other devices."
    ::= { tpmCapabilities 3 }

tpmTransactionMetricDirLastChange OBJECT-TYPE
    SYNTAX      TimeStamp
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of sysUpTime at the time the
        tpmTransactionMetricDirTable was last modified, through
        modifications of the tpmTransactionMetricDirConfig object."
    ::= { tpmCapabilities 4 }


tpmTransactionMetricDirTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF TpmTransactionMetricDirEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table lists the protocol transactions and their
        corresponding performance metrics that this agent



R. Dietz, R. Cole       Expires December 10, 2002              [Page 16]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        has the capability to compute and collect, for the specified
        application.  There is one entry in this table for each such
        application, protocol transaction and metric combination
        supported by this agent.  The entries in this
        table represent the metrics that are collected for each
        protocol transaction that comprise the application.
        The agent should boot up with this table pre-configured
        with those combinations of applications, protocol
        transactions and metrics that it knows about and wishes to
        monitor. Implementations must populate the table with all
        possible application, protocol transaction and metric
        combinations and have the default configuration
        objects set to supportedOff(2).  This table
        does not support the creation of new
        combinations by the management application.

        The deletion of an entry in the apmAppDirectoryTable will cause
        the removal of entries from this table.  These entries must
        be removed because the appLocalIndex value will no
        longer be visible in the apmAppDirectoryTable.  When an entry
        is created in the apmAppDirectoryTable and the agent has the
        ability to support metrics for these protocol transactions,
        the appropriate entries must be made in the
        tpmTransactionMetricDefTable."
    ::= { tpmCapabilities 5 }

tpmTransactionMetricDirEntry OBJECT-TYPE
    SYNTAX      TpmTransactionMetricDirEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A conceptual row in the tpmTransactionMetricDirTable.

        An example of the indexing of this entry is
        tpmTransactionMetricDirConfig.5.2  where 5 is the
        value of a valid and visible appLocalIndex object in
        in the appLocalDir table.  The entries describe the
        the transaction and metric pairs monitored for this
        application.  The tpmTransactionMetricProtocolIndex
        identifies the protocol transaction and the
        tpmMetricDefIndex describes the metric monitored."
    INDEX { tpmTransactionMetricAppLocalIndex, -- Application Index
            tpmTransactionMetricIndex    -- (Protocol,Metric) Index
          }
    ::= { tpmTransactionMetricDirTable 1 }

TpmTransactionMetricDirEntry ::= SEQUENCE {
    tpmTransactionMetricAppLocalIndex   AppLocalIndex,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 17]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    tpmTransactionMetricIndex           TransactionMetricIndex,
    tpmTransactionMetricProtocolIndex   Integer32,
    tpmTransactionMetricMetricIndex     Integer32,
    tpmTransactionMetricDirConfig          INTEGER
}

tpmTransactionMetricAppLocalIndex OBJECT-TYPE
    SYNTAX      AppLocalIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "An index used to uniquely identify the application
        which the entries in the tpmTransactionMetricDir
        table are associated."
    ::= { tpmTransactionMetricDirEntry 1 }

tpmTransactionMetricIndex OBJECT-TYPE
    SYNTAX      TransactionMetricIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "An index used to uniquely identify an entry in the
        tpmTransactionMetricDir table.  Each such entry defines
        protocol transaction and metric instance
        to be monitored for a specific application."
    ::= { tpmTransactionMetricDirEntry 2 }

tpmTransactionMetricProtocolIndex OBJECT-TYPE
    SYNTAX      Integer32 (1..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The protocolDirLocalIndex of the particular transaction to
        be analyzed when computing and generating the selected metric
        for a specific application."
    ::= { tpmTransactionMetricDirEntry 3 }

tpmTransactionMetricMetricIndex OBJECT-TYPE
    SYNTAX      Integer32 (1..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The tpmMetricDefID of the particular metric to be
        generated."
    ::= { tpmTransactionMetricDirEntry 4 }

tpmTransactionMetricDirConfig OBJECT-TYPE
    SYNTAX      INTEGER {



R. Dietz, R. Cole       Expires December 10, 2002              [Page 18]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


                    notSupported(1),
                    supportedOff(2),
                    supportedOn(3)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "This object describes and configures the probe's support
        for this performance metric in relationship to the
        specified transaction and application.  The agent
        creates entries in this table for all metric
        and transaction combinations that it can generate.
        Because the probe will only populate this table with supported
        entries, and the table cannot have entries added, the
        notSupported(1) setting is only used to signify that other
        configuration parameters are causing the agent to currently not
        support the generation and collection of this metric for the
        specified protocol and application.  Also, the status of
        this object will not change to notSupported(1) due to a
        change to supportedOff(2) in the tpmMetricDir table.

        If the value of this object is notSupported(1), the probe
        will not perform computations for this performance metric and
        transaction combination and shall not allow this object to be
        changed to any other value. If the value of this object is
        supportedOn(3), the probe supports computations for this
        performance metric and protocol and is configured to perform
        the computations for this performance metric and protocol
        combination for the application for all interfaces.
        If the value of this object is supportedOff(2), the
        probe supports computations for this performance
        metric for the specified protocol, but is configured
        to not perform the computations for this performance
        metric and protocol for the application for any
        interfaces.  Whenever this value changes from
        supportedOn(3) to supportedOff(2), the probe shall
        cause the deletion of all entries in the tpmReportGroup
        tables, for all appropriate studies configured in the
        tpmAggrReportCntrlTable."
    ::= { tpmTransactionMetricDirEntry 5 }


--
-- TPM Metric Definitions Table
--
--    The tpmMetricDefTable describes the metrics available to the
--    TPM MIB.  The tpmMetricDefTable defines metrics by referencing
--    existing IETF, ITU and other standards organizations' documents.



R. Dietz, R. Cole       Expires December 10, 2002              [Page 19]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


tpmMetricDefTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF TpmMetricDefEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains one row per metric supported by this
            agent, and should be populated during system
            initialization."
    ::= { tpmCapabilities 6 }

tpmMetricDefEntry OBJECT-TYPE
    SYNTAX      TpmMetricDefEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "Information about a particular metric."
    INDEX   { tpmMetricDefID }
    ::= { tpmMetricDefTable 1 }

TpmMetricDefEntry ::= SEQUENCE {
      tpmMetricDefID              MetricDefID,
      tpmMetricDefType            INTEGER,
      tpmMetricDefDirType         INTEGER,
      tpmMetricDefName            SnmpAdminString,
      tpmMetricDefReference       SnmpAdminString
}

tpmMetricDefID     OBJECT-TYPE
    SYNTAX      MetricDefID
    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 metric."
    ::= { tpmMetricDefEntry 1 }

tpmMetricDefType   OBJECT-TYPE
    SYNTAX      INTEGER  {
                          other(1),
                          connectMetric(2),
                          delayMetric(3),
                          lossMetric(4)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The basic type of metric indicated by this entry.



R. Dietz, R. Cole       Expires December 10, 2002              [Page 20]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


            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."
    ::= { tpmMetricDefEntry 2 }

tpmMetricDefDirType   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."
    ::= { tpmMetricDefEntry 3 }

tpmMetricDefName OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The textual name of this metric."
    ::= { tpmMetricDefEntry 4 }

tpmMetricDefReference OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-only
    STATUS      current



R. Dietz, R. Cole       Expires December 10, 2002              [Page 21]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    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 tpmMetricDefEntry identified the IPPM
            metric 'Type-P-Round-Trip-Delay', then this object should
            contain the value 'http://www.ietf.org/rfc/rfc2681.txt'."
    ::= { tpmMetricDefEntry 5 }


--
-- The tpmAggregateReportsGroup
--
--
-- The tpmAggrReportCntrlTable is the controlling entry to manage
-- the population of studies in the Transport Aggregate Report
--

tpmAggrReportCntrlTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF TpmAggrReportCntrlEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table to control the collection of performance metric
        studies for selected interfaces, metrics and
        transaction protocols and applications.

        Note that this is not like the typical RMON
        controlTable and dataTable in which each entry creates
        its own data table.  Each entry in this table enables the
        creation of multiple data tables on a study basis.  For each
        interval, the study is updated in place and the current
        data content of the table becomes invalid."
    ::= { tpmReports 1 }

tpmAggrReportCntrlEntry OBJECT-TYPE
    SYNTAX      TpmAggrReportCntrlEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A conceptual row in the tpmAggrReportCntrlTable.

        An example of the indexing of this entry is
        tpmAggrReportCntrlDataSource.1"
    INDEX { tpmAggrReportCntrlIndex }
    ::= { tpmAggrReportCntrlTable 1 }



R. Dietz, R. Cole       Expires December 10, 2002              [Page 22]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


TpmAggrReportCntrlEntry ::= SEQUENCE {
    tpmAggrReportCntrlIndex               Integer32,
    tpmAggrReportCntrlApmControlIndex     Integer32,
    tpmAggrReportCntrlDataSource          DataSourceOrZero,
    tpmAggrReportCntrlAggregationType     TransactionAggregationType,
    tpmAggrReportCntrlInterval            Unsigned32,
    tpmAggrReportCntrlRequestedSize       Unsigned32,
    tpmAggrReportCntrlGrantedSize         Unsigned32,
    tpmAggrReportCntrlRequestedReports    Unsigned32,
    tpmAggrReportCntrlGrantedReports      Unsigned32,
    tpmAggrReportCntrlStartTime           TimeStamp,
    tpmAggrReportCntrlReportNumber        Unsigned32,
    tpmAggrReportCntrlInsertsDenied       Counter32,
    tpmAggrReportCntrlDroppedFrames       Counter32,
    tpmAggrReportCntrlOwner               OwnerString,
    tpmAggrReportCntrlStatus              RowStatus
}


tpmAggrReportCntrlIndex OBJECT-TYPE
    SYNTAX      Integer32 (1..65535)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "An index that uniquely identifies an entry in the
        tpmAggrReportCntrlTable.  Each such entry defines a unique
        report whose results are placed in the tpmAggrReportTable on
        behalf of this tpmAggrReportCntrlEntry."
    ::= { tpmAggrReportCntrlEntry 1 }

tpmAggrReportCntrlApmControlIndex OBJECT-TYPE
    SYNTAX      Integer32 (0..65535)
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This index associates this TpmAggrReportCntrlEntry directly
        with an existing ApmReportControlEntry.  This link is used
        to synchronize reports in the associated tpmAggrReportTable.

        A value of 0 (zero) enables an independent control table that
        will report entries to tpmAggrReportTable based only on the
        other objects in this table.

        This object may not be modified if the associated
        tpmAggrReportCntrlStatus object is equal to active(1)."
    DEFVAL { 0 }
    ::= { tpmAggrReportCntrlEntry 2 }




R. Dietz, R. Cole       Expires December 10, 2002              [Page 23]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


tpmAggrReportCntrlDataSource OBJECT-TYPE
    SYNTAX      DataSourceOrZero
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The source of the data for TPM Reports generated on
        behalf of this tpmAggrReportCntrlEntry.

        If the measurement is being performed by a probe, this should
        be set to interface or port where data was received for
        analysis. If the measurement isn't being performed by a probe,
        this should be set to the primary interface over which the
        measurement is being performed. If the measurement isn't being
        performed by a probe and there is no primary interface or this
        information isn't known, this object should be set to 0.0.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object is set to the corresponding
        apmReportControlTable object in the APM MIB [APM].

        This object may not be modified if the associated
        tpmAggrReportCntrlStatus object is equal to active(1)."
    ::= { tpmAggrReportCntrlEntry 3 }

tpmAggrReportCntrlAggregationType OBJECT-TYPE
    SYNTAX      TransactionAggregationType
             -- INTEGER {
             --    flows(1),
             --    clients(2),
             --    servers(3),
             --    applications(4)
             -- }
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The type of aggregation being performed for this set of
        reports.  See APM MIB [APM].

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object should be set by the agent to the value
        of the apmReportControlAggregationType object.

        This object may not be modified if the associated
        tpmAggrReportCntrlStatus object is equal to active(1)."
    ::= { tpmAggrReportCntrlEntry 4 }

tpmAggrReportCntrlInterval OBJECT-TYPE
    SYNTAX      Unsigned32



R. Dietz, R. Cole       Expires December 10, 2002              [Page 24]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    UNITS       "Seconds"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The interval in seconds over which data is accumulated before
        being aggregated into a report in the tpmAggrReportTable.  All
        reports with the same tpmAggrReportCntrlIndex will be based on
        the same interval.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object should be set by the agent to the value
        of the apmReportControlControlInterval object.

        This object may not be modified if the associated
        tpmReportAggregateCntrlStatus object is equal to active(1)."
    DEFVAL { 3600 }
    ::= { tpmAggrReportCntrlEntry 5 }

tpmAggrReportCntrlRequestedSize OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The maximum number of Client and Server combination
        entries requested for this report.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object should be set by the agent to the value
        of the apmReportControlRequestedSize object.

        When this object is created or modified, the probe
        should set tpmReportCntrlGrantedSize as closely to this
        object as is possible for the particular probe
        implementation and available resources.

        It is important to note that this value is the number of
        requested entries in the tpmAggrReportTable only.  Since the
        probe can derive this table from the apmReportTable, the probe
        must make sure that sufficient resources exist to support the
        creation of the apmReportTable plus any additional resources
        required to convert or support this table."
    ::= { tpmAggrReportCntrlEntry 6 }

tpmAggrReportCntrlGrantedSize OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION



R. Dietz, R. Cole       Expires December 10, 2002              [Page 25]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        "The maximum number of performance entries in this report.

        When the associated tpmAggrReportCntrlRequestedSize object is
        created or modified, the probe should set this
        object as closely to the requested value as is
        possible for the particular implementation and
        available resources. The probe must not lower this
        value except as a result of a set to the associated
        tpmAggrReportCntrlRequestedSize object.

        It is an implementation-specific matter as to whether or not
        zero-valued entries are available."
    ::= { tpmAggrReportCntrlEntry 7 }

tpmAggrReportCntrlRequestedReports OBJECT-TYPE
    SYNTAX      Unsigned32 (1..65535)
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The number of saved reports requested to be allocated on
        behalf of this entry.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object should be set by the agent to the value
        of the apmReportControlcwRequestedReportsDataSource object."
    ::= { tpmAggrReportCntrlEntry 8 }

tpmAggrReportCntrlGrantedReports OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of saved reports the agent has allocated based
        on the requested amount in tpmAggrReportCntrlRequestedReports.
        Since each report can have many entries, the total number of
        entries allocated will be this number multiplied by the
        value of tpmAggrReportCntrlGrantedSize, or 1 if that
        object doesn't exist.

        When the associated tpmAggrReportCntrlRequestedReports object is
        created or modified, the agent should set this object as
        closely to the requested value as is possible for the
        particular implementation and available resources. When
        considering resources available, the agent must consider its
        ability to allocate this many reports each with the number of
        entries represented by tpmAggrReportCntrlGrantedSize, or 1 if
        that object doesn't exist.




R. Dietz, R. Cole       Expires December 10, 2002              [Page 26]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        Note that while the storage required for each report may
        fluctuate due to changing conditions, the agemt must continue
        to have storage available to satisfy the full report size for
        all reports when necessary. Further, the agent must not lower
        this value except as a result of a set to the associated
        tpmAggrReportCntrlRequestedSize object."
    ::= { tpmAggrReportCntrlEntry 9 }

tpmAggrReportCntrlStartTime OBJECT-TYPE
    SYNTAX      TimeStamp
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of sysUpTime when the system began processing the
        report in progress. Note that the report in progress is not
        available.

        This object may be used by the management station to figure
        out the start time for all previous reports saved for this
        tpmAggrReportCntrlEntry, as reports are started at fixed
        intervals.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object is set to the corresponding
        apmReportControlTable object in the APM MIB [APM]."
    ::= { tpmAggrReportCntrlEntry 10 }

tpmAggrReportCntrlReportNumber OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of the report in progress. When an
        tpmAggrReportCntrlEntry is activated, the first report will be
        numbered zero.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object should be set by the agent to the value
        of the apmReportControlReportNumber object."
    ::= { tpmAggrReportCntrlEntry 11 }

tpmAggrReportCntrlInsertsDenied OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of failed attempts to add an entry to reports for
        this tpmReportControlEntry because the number of entries



R. Dietz, R. Cole       Expires December 10, 2002              [Page 27]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        would have exceeded tpmReportAggregateCntrlGrantedSize.

        This number is valuable in determining if enough entries have
        been allocated for reports in light of fluctuating network
        usage. Note that an entry that is denied will often be
        attempted again, this number will not predict the exact number
        of additional entries needed, but can be used to understand
        the relative magnitude of the problem.

        Also note that there is no ordering specified for the entries
        in the report, thus there are no rules for which entries will
        be omitted when not enough entries are available. As a
        consequence, the agent is not required to delete 'least
        valuable' entries first."
    ::= { tpmAggrReportCntrlEntry 12 }

tpmAggrReportCntrlDroppedFrames OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "The total number of frames which were received by the agent
        and therefore not accounted for in the *StatsDropEvents, but
        for which the agent chose not to count for this entry for
        whatever reason.  Most often, this event occurs when the agent
        is out of some resources and decides to shed load from this
        collection.

        This count does not include packets that were not counted
        because they had MAC-layer errors.

        Note that if the alMatrixTables are not implemented or are
        inactive because no protocols are enabled in the protocol
        directory, this value should be 0.

        Note that, unlike the dropEvents counter, this number is the
        exact number of frames dropped."
    ::= { tpmAggrReportCntrlEntry 13 }

tpmAggrReportCntrlOwner OBJECT-TYPE
    SYNTAX      OwnerString
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The entity that configured this entry and is
        therefore using the resources assigned to it.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 28]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        then this object should be set by the agent to the value
        of the apmReportControlReportNumber object."
    ::= { tpmAggrReportCntrlEntry 14 }

tpmAggrReportCntrlStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The status of this performance control entry.

        An entry may not exist in the active state unless all
        objects in the entry have an appropriate value.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object should be set by the agent to the value
        of the apmReportControlReportNumber object.

        If this object is not equal to active(1), all associated
        entries in the tpmAggrReportTable shall be deleted."
    ::= { tpmAggrReportCntrlEntry 15 }


--
-- Transport Aggregate Report Table
--
-- This table contains transport performance metric studies for each
-- of the control table entries in tpmAggrReportCntrlTable.  These
-- studies are provided based on the selections and parameters found
-- for the entry in the tpmAggregateReportCntrlTable.
--

tpmAggrReportTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF TpmAggrReportEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A study of performance statistics for those
        table entries specified in the tpmTransactionMetricDirTable
        associated with the application in question and
        indexed by appLocalIndex and tpmTransactionMetricIndex."
    ::= { tpmReports 2 }

tpmAggrReportEntry OBJECT-TYPE
    SYNTAX      TpmAggrReportEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION



R. Dietz, R. Cole       Expires December 10, 2002              [Page 29]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        "A conceptual row in the tpmAggrReportTable.

        The tpmAggrReportCntrlIndex value in the index identifies the
        tpmAggrReportCntrlEntry on whose behalf this entry was created.
        The tpmAggrReportIndex value in the index identifies which
        report (in the series of reports) this entry is a part of.
        The tpmAggrReportAppLocalIndex value in the index identifies
        the application protocol that is being reported.
        The tpmTransactionMetricIndex value in the index identifies
        the transaction protocol-metric pair for the traffic flows
        aggregated in this entry.
        The protocolDirLocalIndex value in the index identifies the network
        layer protocol of the tpmAggrReportServerAddress. When
        the associated tpmAggrReportCntrlAggregationType value is equal
        to applications(4) or clients(2), this value will equal 0.
        The tpmAggrReportServerAddress value in the index identifies the
        network layer address of the server in traffic flows
        aggregated in this entry.
        The tpmAggrReportApmNameClientID value in the index identifies the
        client in traffic flows aggregated in this entry. If the
        associated tpmAggrReportCntrlAggregationType is equal to
        applications(4) or servers(3), then this object will be set to
        0.

        An example of the indexing of this entry is
        tpmAggrReportStatisticN.3.15.34.262.18.4.128.2.6.7.3256521"
    INDEX { tpmAggrReportCntrlIndex,
            tpmAggrReportIndex,
            tpmAggrReportAppLocalIndex,       -- Application Layer
            tpmAggrReportTransMetricIndex,    -- Metric and Protocol
            protocolDirLocalIndex,            -- Network Layer
            tpmAggrReportServerAddress,
            tpmAggrReportApmNameClientID
          }
    ::= { tpmAggrReportTable 1 }

TpmAggrReportEntry ::= SEQUENCE {
    tpmAggrReportIndex                          Integer32,
    tpmAggrReportAppLocalIndex                  AppLocalIndex,
    tpmAggrReportTransMetricIndex               TransactionMetricIndex,
    tpmAggrReportServerAddress                  OCTET STRING,
    tpmAggrReportApmNameClientID                ClientID,
    tpmAggrReportStatisticN                     Unsigned32,
    tpmAggrReportOverflowStatisticN             Unsigned32,
    tpmAggrReportHCStatisticN                   Unsigned32,
    tpmAggrReportStatisticSumX                  Unsigned32,
    tpmAggrReportOverflowStatisticSumX          Unsigned32,
    tpmAggrReportHCStatisticSumX                Unsigned32,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 30]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    tpmAggrReportStatisticMaximum               Unsigned32,
    tpmAggrReportStatisticMinimum               Unsigned32,
    tpmAggrReportStatisticSumSquared            Unsigned32,
    tpmAggrReportOverflowStatisticSumSquared    Unsigned32,
    tpmAggrReportHCStatisticSumSquared          Unsigned32,
    tpmAggrReportStatisticSumIX                 Unsigned32,
    tpmAggrReportOverflowStatisticSumIX         Unsigned32,
    tpmAggrReportHCStatisticSumIX               Unsigned32,
    tpmAggrReportStatisticSumIXSquared          Unsigned32,
    tpmAggrReportOverflowStatisticSumIXSquared  Unsigned32,
    tpmAggrReportHCStatisticSumIXSquared        Unsigned32
}


tpmAggrReportIndex  OBJECT-TYPE
    SYNTAX      Integer32 (0..2147483647)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The value of tpmAggrReportCntrlNumber for the report to
        which this entry belongs."
    ::= { tpmAggrReportEntry 1 }

tpmAggrReportAppLocalIndex  OBJECT-TYPE
    SYNTAX      AppLocalIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The common application of the transactions aggregated
        in this entry."
    ::= { tpmAggrReportEntry 2 }

tpmAggrReportTransMetricIndex OBJECT-TYPE
    SYNTAX      TransactionMetricIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "A unique index that identifies the transaction and
         metric associated with the statistics reported here."
    ::= { tpmAggrReportEntry 3 }

tpmAggrReportServerAddress OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..108))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The network layer address of the server host in this
        conversation.



R. Dietz, R. Cole       Expires December 10, 2002              [Page 31]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        This is represented as an octet string with
        specific semantics and length as identified
        by the protocolDirLocalIndex component of the index.

        Since this object is an index variable, it is encoded in
        the index according to the index encoding rules.  For
        example, if the protocolDirLocalIndex indicates an
        encapsulation of IP, this object is encoded as a length
        octet of 4, followed by the 4 octets of the IP address,
        in network byte order.

        If the associated tpmAggrReportCntrlAggregationType is equal to
        application(4) or client(2), then this object will be a null
        string and will be encoded simply as a length octet of 0."
    ::= { tpmAggrReportEntry 4 }

tpmAggrReportApmNameClientID OBJECT-TYPE
    SYNTAX      ClientID
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "A unique ID assigned to the machine represented by this
         mapping. This ID is assigned by the agent using an
         implementation-specific algorithm."
    ::= { tpmAggrReportEntry 5 }

tpmAggrReportStatisticN OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The count of the total number of data points for the
        specified metric.  This number always represents the
        total size of the statistical datum analyzed.  Each
        metric specifies the exact meaning of this object.

        This value represents the results for one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmAggrReportEntry 6 }

tpmAggrReportOverflowStatisticN OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated tpmAggrReportStatisticN
        counter has overflowed."



R. Dietz, R. Cole       Expires December 10, 2002              [Page 32]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    ::= { tpmAggrReportEntry 7 }

tpmAggrReportHCStatisticN OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmAggrReportStatisticN."
    ::= { tpmAggrReportEntry 8 }

tpmAggrReportStatisticSumX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The sum of all the data point values for the specified
        metric.  This number always represents the total values
        of the statistical datum analyzed.  Each metric
        specifies the exact meaning of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmAggrReportEntry 9 }

tpmAggrReportOverflowStatisticSumX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated tpmAggrReportStatisticSumX
        counter has overflowed."
    ::= { tpmAggrReportEntry 10 }

tpmAggrReportHCStatisticSumX OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmAggrReportStatisticSumX."
    ::= { tpmAggrReportEntry 11 }

tpmAggrReportStatisticMaximum OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The single maximum data point value observed during the



R. Dietz, R. Cole       Expires December 10, 2002              [Page 33]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        study period for the specified metric.  This number always
        represents the maximum value of any single statistical
        datum analyzed.  Each metric specifies the exact meaning
        of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmAggrReportEntry 12 }

tpmAggrReportStatisticMinimum OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The single minimum data point value observed during the
        study period for the specified metric.  This number always
        represents the minimum value of any single statistical
        datum analyzed.  Each metric specifies the exact meaning
        of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmAggrReportEntry 13 }

tpmAggrReportStatisticSumSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The sum of all the squared data point values for the
        specified metric.  This number always represents the
        total of the squared values of the statistical datum
        analyzed.  Each metric specifies the exact meaning of
        this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmAggrReportEntry 14 }

tpmAggrReportOverflowStatisticSumSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated



R. Dietz, R. Cole       Expires December 10, 2002              [Page 34]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        tpmAggrReportStatisticSumSquared counter has overflowed."
    ::= { tpmAggrReportEntry 15 }

tpmAggrReportHCStatisticSumSquared OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmAggrReportStatisticSumSquared."
    ::= { tpmAggrReportEntry 16 }

tpmAggrReportStatisticSumIX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "For each interval, each data point is associated with a
        value I, I = 1..N where N is the number of data points,
        tpmAggrReportStatisticN. IX is the multiplication of the data point
        value with the current I.  This value along with the other
        statistics values allow the calculation of the slope of
        the least-squares line through the data points."
    ::= { tpmAggrReportEntry 17 }

tpmAggrReportOverflowStatisticSumIX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated
        tpmAggrReportStatisticSumIX counter has overflowed."
    ::= { tpmAggrReportEntry 18 }

tpmAggrReportHCStatisticSumIX OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmAggrReportStatisticSumIX."
    ::= { tpmAggrReportEntry 19 }

tpmAggrReportStatisticSumIXSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "For each interval, each data point is associated with a
        value I, I = 1..N where N is the number of data points,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 35]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        tpmAggrReportStatisticN. IX is the multiplication
        of the data point value with the current I.
        This value along with the other statistics
        values allow the calculation of the slope of
        the least-squares line through the data points."
    ::= { tpmAggrReportEntry 20 }

tpmAggrReportOverflowStatisticSumIXSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated
        tpmAggrReportStatisticSumIXSquared counter has overflowed."
    ::= { tpmAggrReportEntry 21 }

tpmAggrReportHCStatisticSumIXSquared OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of
        tpmAggrReportStatisticSumIXSquared."
    ::= { tpmAggrReportEntry 22 }


--
-- The tpmCurrentReportsGroup
--
--
-- TPM Current Transaction Table
--
-- This table will contain entries associated with an
-- apmReportControlEntry which are a current 'snapshot' of the
-- metrics being collected in association with a set
-- of TPM related application transactions.
-- Once completed, a history of these transactions is retained.
-- Completion is indicated by the
-- value of the tpmCurrReportCompletion object.
--

tpmCurrReportTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF TpmCurrReportEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table contains all sub-flow metrics for transactions
        that have been started but have not yet finished, i.e.



R. Dietz, R. Cole       Expires December 10, 2002              [Page 36]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        current, and a history of those that have finished, i.e.,
        completed."
    ::= { tpmReports 3 }

tpmCurrReportEntry OBJECT-TYPE
    SYNTAX      TpmCurrReportEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A conceptual row in the tpmCurrReportTable.

        The tpmAggrReportControlIndex value in the index identifies
        the tpmAggrReportCntrlEntry on whose behalf this entry was
        created.  The tpmCurrReportAppLocalIndex value in the
        index identifies the application protocol that is begin
        reported.  The protocolDirLocalIndex value in the
        index identifies the network layer protocol
        of the tpmAggrReportServerAddress. When the associated
        tpmAggrReportCntrlAggregationType value is
        equal to applications(4), this value will equal 0.
        The tpmCurrReportServerAddress value in the
        index identifies the network layer address of the
        server in traffic flows aggregated in this entry.
        The tpmCurrReportCurrentApmNameClientID value in the
        index identifies the network layer address of the
        client in traffic flows aggregated in this entry.
        The tpmCurrReportCurrentMetricIndex value in the
        index identifies the transported application protocol
        of the traffic flows aggregated in this entry.

        Note that the order of protocolDirLocalIndex variables is
        the opposite of that in the RMON2 MIB (application.network
        instead of network.application) so that the report entries are
        sorted by application first, server second and client third.
        The tpmCurrReportCntrIndex value in the index identifies
        the tpmAggrReportCntrlEntry on whose behalf this entry was
        created.  The tpmCurrReportMetricIndex value in the index
        identifies the metric and protocol of the
        tpmCurrReportServerAddress, via the tpmTransactionMetricDir
        table.

        An example of the indexing of this table is
        tpmCurrReportStatisticN.3.34.262.18.4.128.2.6.6.3256521.29667"
    INDEX { tpmAggrReportCntrlIndex,
            tpmCurrReportAppLocalIndex,          -- Application Layer
            tpmCurrReportTransMetricIndex,       -- Metric and Protocol
            protocolDirLocalIndex,               -- Network Layer
            tpmCurrReportServerAddress,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 37]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


            tpmCurrReportApmNameClientID,
            tpmCurrReportApmTransactionID
          }
    ::= { tpmCurrReportTable 1 }

TpmCurrReportEntry ::= SEQUENCE {
    tpmCurrReportAppLocalIndex                 AppLocalIndex,
    tpmCurrReportTransMetricIndex              TransactionMetricIndex,
    tpmCurrReportServerAddress                 OCTET STRING,
    tpmCurrReportApmNameClientID               ClientID,
    tpmCurrReportApmTransactionID              Integer32,
    tpmCurrReportMetricValue                   Unsigned32
}

tpmCurrReportAppLocalIndex  OBJECT-TYPE
    SYNTAX      AppLocalIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The common application of the transactions reported
        in this entry."
    ::= { tpmCurrReportEntry 1 }

tpmCurrReportTransMetricIndex OBJECT-TYPE
    SYNTAX      TransactionMetricIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "A unique index that identifies the transaction and
         metric associated with the statistics reported here."
    ::= { tpmCurrReportEntry 2 }

tpmCurrReportServerAddress OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..108))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The network server address for this tpmCurrEntry.

        This is represented as an octet string with
        specific semantics and length as identified
        by the protocolDirLocalIndex component of the index.

        For example, if the protocolDirLocalIndex indicates an
        encapsulation of IP, this object is encoded as a length
        octet of 4, followed by the 4 octets of the IP address,
        in network byte order."
    ::= { tpmCurrReportEntry 3 }



R. Dietz, R. Cole       Expires December 10, 2002              [Page 38]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


tpmCurrReportApmNameClientID OBJECT-TYPE
    SYNTAX      ClientID
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "A unique ID assigned to the machine represented by this
         mapping. This ID is assigned by the agent using an
         implementation-specific algorithm."
    ::= { tpmCurrReportEntry 4 }

tpmCurrReportApmTransactionID OBJECT-TYPE
    SYNTAX      Integer32 (0..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "A unique value for this transaction amongst other
        transactions sharing the same application,
        transaction-layer protocol and metric and
        server and client addresses. Implementations may choose to use
        the value of the client's source port, when possible.

        If the tpmAggrReportCntrlApmControlIndex is non-zero,
        then this object is set to the corresponding
        apmTransactionID object in the APM MIB [APM]."
    ::= { tpmCurrReportEntry 5 }

tpmCurrReportMetricValue OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The current value of the metric being evaluated.
        For some transaction types this value may be 0, e.g.,
        the current round trip time for a DNS query.  For
        other transaction types this will represent the
        current value of a continuously measured metric, e.g.,
        the current throughput of an FTP transaction."
    ::= { tpmCurrReportEntry 6 }

tpmCurrReportCompletion OBJECT-TYPE
    SYNTAX      INTEGER {
                    current(1),
                    completed(2)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The status of this transactione. A may be current or



R. Dietz, R. Cole       Expires December 10, 2002              [Page 39]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        completed."
    ::= { tpmCurrReportEntry 7 }

tpmCurrReportSize OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The maximum number of completed transactions desired to be
        retained in the tpmCurrReportTable. If the agent doesn't have
        enough resources to retain this many, it will retain as many as
        possible. Regardless of this value, the agent must attempt to
        keep records for all current transactions it is monitoring."
    ::= { tpmReports 5 }


--
-- The tpmExceptionReportsGroup
--
--
-- TPM Exception Report Table
--
-- This table will contain the sub-flows related to an
-- apmExceptionTable entry.
--

tpmExcpReportTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF TpmExcpReportEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table contains all sub-flow metrics for transactions
        that have been tagged by the apmExceptionTable filter
        as having had poor performance."
    ::= { tpmReports 6 }

tpmExcpReportEntry OBJECT-TYPE
    SYNTAX      TpmExcpReportEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A conceptual row in the tpmExcpReportTable.  This table
        contains aggregated information associated with
    exceptions counted in the apmExceptionTable.  The
        information is aggregated in a manner identical to the
        aggregation in the tpmAggrReportTable, with the exception
        that data only from transactions associated with a
        flagged application is included.



R. Dietz, R. Cole       Expires December 10, 2002              [Page 40]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        The indexing into this table follows the indexing in the
        APM MIB but adds the tpmTransMetricIndex to identify the
    sub-application transaction and metric pair."
    INDEX { tpmExcpReportAppLocalIndex,         -- Application
            tpmExcpReportApmResponsivenessType, -- Responsiveness Type
            tpmExcpReportApmExceptionIndex,     -- Linkage to ApmExceptions
            tpmExcpReportTransMetricIndex       -- Metric and Protocol
          }
    ::= { tpmExcpReportTable 1 }

TpmExcpReportEntry ::= SEQUENCE {
    tpmExcpReportAppLocalIndex                 AppLocalIndex,
    tpmExcpReportApmResponsivenessType           INTEGER,
    tpmExcpReportApmExceptionIndex             Integer32,
    tpmExcpReportTransMetricIndex              TransactionMetricIndex,
    tpmExcpReportStatisticN                    Unsigned32,
    tpmExcpReportOverflowStatisticN            Unsigned32,
    tpmExcpReportHCStatisticN                  Unsigned32,
    tpmExcpReportStatisticSumX                 Unsigned32,
    tpmExcpReportOverflowStatisticSumX         Unsigned32,
    tpmExcpReportHCStatisticSumX               Unsigned32,
    tpmExcpReportStatisticMaximum              Unsigned32,
    tpmExcpReportStatisticMinimum              Unsigned32,
    tpmExcpReportStatisticSumSquared           Unsigned32,
    tpmExcpReportOverflowStatisticSumSquared   Unsigned32,
    tpmExcpReportHCStatisticSumSquared         Unsigned32,
    tpmExcpReportStatisticSumIX                Unsigned32,
    tpmExcpReportOverflowStatisticSumIX        Unsigned32,
    tpmExcpReportHCStatisticSumIX              Unsigned32,
    tpmExcpReportStatisticSumIXSquared         Unsigned32,
    tpmExcpReportOverflowStatisticSumIXSquared Unsigned32,
    tpmExcpReportHCStatisticSumIXSquared       Unsigned32
}

tpmExcpReportAppLocalIndex  OBJECT-TYPE
    SYNTAX      AppLocalIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The common application of the transactions reported
        in this entry."
    ::= { tpmExcpReportEntry 1 }

tpmExcpReportApmResponsivenessType OBJECT-TYPE
    SYNTAX      INTEGER {
                  transactionOriented(1),
                  throughputOriented(2),
                  streamingOriented(3)



R. Dietz, R. Cole       Expires December 10, 2002              [Page 41]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


                }
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This object describes and configures the agent's support for
        application performance measurement for this application.
        There are 3 types of measurements for different types of
        applications.  Refer to the description in the APM MIB [APM]."
    ::= { tpmExcpReportEntry 2 }

tpmExcpReportApmExceptionIndex OBJECT-TYPE
    SYNTAX      Integer32 (1..65535)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "An index that associates this tpmExcpReportEntry directly
        with an existing apmExceptionEntry."
    ::= { tpmExcpReportEntry 3 }

tpmExcpReportTransMetricIndex OBJECT-TYPE
    SYNTAX      TransactionMetricIndex
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "A unique index that identifies the transaction and
         metric associated with the data reported here."
    ::= { tpmExcpReportEntry 4 }

tpmExcpReportStatisticN OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The count of the total number of data points for the
        specified metric.  This number always represents the
        total size of the statistical datum analyzed.  Each
        metric specifies the exact meaning of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmExcpReportEntry 5 }

tpmExcpReportOverflowStatisticN OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION



R. Dietz, R. Cole       Expires December 10, 2002              [Page 42]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        "The number of times the associated tpmExcpReportStatisticN
        counter has overflowed."
    ::= { tpmExcpReportEntry 6 }

tpmExcpReportHCStatisticN OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmExcpReportStatisticN."
    ::= { tpmExcpReportEntry 7 }

tpmExcpReportStatisticSumX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The sum of all the data point values for the specified
        metric.  This number always represents the total values
        of the statistical datum analyzed.  Each metric
        specifies the exact meaning of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmExcpReportEntry 8 }

tpmExcpReportOverflowStatisticSumX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated
        tpmExcpReportStatisticSumX counter has overflowed."
    ::= { tpmExcpReportEntry 9 }

tpmExcpReportHCStatisticSumX OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmExcpReportStatisticSumX."
    ::= { tpmExcpReportEntry 10 }

tpmExcpReportStatisticMaximum OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current



R. Dietz, R. Cole       Expires December 10, 2002              [Page 43]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    DESCRIPTION
        "The single maximum data point value observed during the
        study period for the specified metric.  This number always
        represents the maximum value of any single statistical
        datum analyzed.  Each metric specifies the exact meaning
        of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmExcpReportEntry 11 }

tpmExcpReportStatisticMinimum OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The single minimum data point value observed during the
        study period for the specified metric.  This number always
        represents the minimum value of any single statistical
        datum analyzed.  Each metric specifies the exact meaning
        of this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmExcpReportEntry 12 }

tpmExcpReportStatisticSumSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The sum of all the squared data point values for the
        specified metric.  This number always represents the
        total of the squared values of the statistical datum
        analyzed.  Each metric specifies the exact meaning of
        this object.

        This value represents the results of one metric and is
        related directly to the specific parameters of the metric
        and the Server and Client addresses involved."
    ::= { tpmExcpReportEntry 13 }

tpmExcpReportOverflowStatisticSumSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current



R. Dietz, R. Cole       Expires December 10, 2002              [Page 44]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    DESCRIPTION
        "The number of times the associated
        tpmExcpReportStatisticSumSquared counter has overflowed."
    ::= { tpmExcpReportEntry 14 }

tpmExcpReportHCStatisticSumSquared OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of
        tpmExcpReportStatisticSumSquared."
    ::= { tpmExcpReportEntry 15 }

tpmExcpReportStatisticSumIX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "For each interval, each data point is associated with a
        value I, I = 1..N where N is the number of data points,
        tpmExcpReportStatisticSumIX is the multiplication of the
        data point value with the current I.  This value along with
        the other statistics values allow the calculation of the slope
        of the least-squares line through the data points."
    ::= { tpmExcpReportEntry 16 }

tpmExcpReportOverflowStatisticSumIX OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated
        tpmExcpReportStatisticSumIX counter has overflowed."
    ::= { tpmExcpReportEntry 17 }

tpmExcpReportHCStatisticSumIX OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of tpmExcpReportStatisticSumIX."
    ::= { tpmExcpReportEntry 18 }

tpmExcpReportStatisticSumIXSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current



R. Dietz, R. Cole       Expires December 10, 2002              [Page 45]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    DESCRIPTION
        "For each interval, each data point is associated with a
        value I, I = 1..N where N is the number of data points,
        tpmExcpReportStatisticN. IX is the multiplication of the data
        point value with the current I.  This value along with the other
        statistics values allow the calculation of the slope of
        the least-squares line through the data points."
    ::= { tpmExcpReportEntry 19 }

tpmExcpReportOverflowStatisticSumIXSquared OBJECT-TYPE
    SYNTAX      Unsigned32 (0..4294967295)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of times the associated
        tpmExcpReportStatisticSumIXSquared counter has overflowed."
    ::= { tpmExcpReportEntry 20 }

tpmExcpReportHCStatisticSumIXSquared OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The high-capacity version of
        tpmExcpReportStatisticSumIXSquared."
    ::= { tpmExcpReportEntry 21 }



--
-- TPM Conformance
--

tpmCompliances  OBJECT IDENTIFIER ::= { tpmConformance 1 }
tpmGroups       OBJECT IDENTIFIER ::= { tpmConformance 2 }

--
-- TPM Compliance Statement
--
-- Compliance statement defines the following TPM MIB
-- implementation:
--
--  - tpmCapabilitiesGroup (minimum)
--  - tpmAggregateReportsGroup (minimum)
--  - tpmCurrentReportsGroup (optional)
--  - tpmExceptionReportsGroup (optional)

tpmCompliance MODULE-COMPLIANCE



R. Dietz, R. Cole       Expires December 10, 2002              [Page 46]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


    STATUS  current
    DESCRIPTION
    "Describes the requirements for conformance to
    the TPM MIB."
    MODULE -- this module
    MANDATORY-GROUPS
    { tpmCapabilitiesGroup,
      tpmAggregateReportsGroup }
    ::= { tpmCompliances 1 }


-- This compliance statement defines the following APM MIB
-- optional groups in order for the TPM MIB to be used in
-- drill-down support of the APM MIB measurements:
--
--  - tpmApmReportControlGroup (optional)
--  - tpmApmTransactionControlGroup (optional)
--  - tpmApmExceptionControlGroup (optional)

tpmApmMIBCompliance MODULE-COMPLIANCE
        STATUS  current
        DESCRIPTION
                " Describes the requirements on the APM MIB
                for conformance to the TPM MIB operating in
                drill-down mode in support of APM MIB
                measurements"
        MODULE  -- this module
        MANDATORY-GROUPS
         { tpmApmReportControlGroup,
           tpmApmTransactionControlGroup,
           tpmApmExceptionControlGroup  }
        ::= { tpmCompliances 2 }


--
--  TPM MIB Groups
--

tpmCapabilitiesGroup    OBJECT-GROUP
    OBJECTS { tpmClockResolution,
              tpmClockMaxSkew,
              tpmClockSource,
              tpmTransactionMetricDirLastChange,
              tpmTransactionMetricProtocolIndex,
              tpmTransactionMetricMetricIndex,
              tpmTransactionMetricDirConfig,
              tpmMetricDefType,
              tpmMetricDefDirType,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 47]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


              tpmMetricDefName,
              tpmMetricDefReference }
    STATUS  current
    DESCRIPTION
        ""
    ::= { tpmGroups 1 }


tpmAggregateReportsGroup    OBJECT-GROUP
    OBJECTS { tpmAggrReportCntrlApmControlIndex,
              tpmAggrReportCntrlDataSource,
              tpmAggrReportCntrlAggregationType,
              tpmAggrReportCntrlInterval,
              tpmAggrReportCntrlRequestedSize,
              tpmAggrReportCntrlGrantedSize,
              tpmAggrReportCntrlRequestedReports,
              tpmAggrReportCntrlGrantedReports,
              tpmAggrReportCntrlStartTime,
              tpmAggrReportCntrlReportNumber,
              tpmAggrReportCntrlInsertsDenied,
              tpmAggrReportCntrlDroppedFrames,
              tpmAggrReportCntrlOwner,
              tpmAggrReportCntrlStatus,
              tpmAggrReportStatisticN,
              tpmAggrReportOverflowStatisticN,
              tpmAggrReportHCStatisticN,
              tpmAggrReportStatisticSumX,
              tpmAggrReportOverflowStatisticSumX,
              tpmAggrReportHCStatisticSumX,
              tpmAggrReportStatisticMaximum,
              tpmAggrReportStatisticMinimum,
              tpmAggrReportStatisticSumSquared,
              tpmAggrReportOverflowStatisticSumSquared,
              tpmAggrReportHCStatisticSumSquared,
              tpmAggrReportStatisticSumIX,
              tpmAggrReportOverflowStatisticSumIX,
              tpmAggrReportHCStatisticSumIX,
              tpmAggrReportStatisticSumIXSquared,
              tpmAggrReportOverflowStatisticSumIXSquared,
              tpmAggrReportHCStatisticSumIXSquared }
    STATUS  current
    DESCRIPTION
        ""
    ::= { tpmGroups 2 }


tpmCurrentReportsGroup  OBJECT-GROUP
    OBJECTS { tpmCurrReportMetricValue,



R. Dietz, R. Cole       Expires December 10, 2002              [Page 48]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


              tpmCurrReportCompletion,
              tpmCurrReportSize }
    STATUS  current
    DESCRIPTION
        ""
    ::= { tpmGroups 3 }

tpmExceptionReportsGroup    OBJECT-GROUP
    OBJECTS { tpmExcpReportStatisticN,
              tpmExcpReportOverflowStatisticN,
              tpmExcpReportHCStatisticN,
              tpmExcpReportStatisticSumX,
              tpmExcpReportOverflowStatisticSumX,
              tpmExcpReportHCStatisticSumX,
              tpmExcpReportStatisticMaximum,
              tpmExcpReportStatisticMinimum,
              tpmExcpReportStatisticSumSquared,
              tpmExcpReportOverflowStatisticSumSquared,
              tpmExcpReportHCStatisticSumSquared,
              tpmExcpReportStatisticSumIX,
              tpmExcpReportOverflowStatisticSumIX,
              tpmExcpReportHCStatisticSumIX,
              tpmExcpReportStatisticSumIXSquared,
              tpmExcpReportOverflowStatisticSumIXSquared,
              tpmExcpReportHCStatisticSumIXSquared }
    STATUS  current
    DESCRIPTION
        ""
    ::= { tpmGroups 4 }


tpmApmReportControlGroup        OBJECT-GROUP
        OBJECTS { apmReportControlIndex,
                  apmReportControlDataSource,
                  apmReportControlControlInterval,
                  apmReportControlRequestedSize,
                  apmReportControlRequestedReports,
                  apmReportControlStartTime,
                  apmReportControlReportNumber,
                  apmReportControlOwner,
                  apmReportControlStatus }
        STATUS   current
        DESCRIPTION
             ""
        ::= { tpmGroups 5 }

tpmApmTransactionControlGroup        OBJECT-GROUP
        OBJECTS { apmTransactionID }



R. Dietz, R. Cole       Expires December 10, 2002              [Page 49]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


        STATUS   current
        DESCRIPTION
             ""
        ::= { tpmGroups 6 }

tpmApmExceptionControlGroup        OBJECT-GROUP
        OBJECTS { apmExceptionIndex }
        STATUS   current
        DESCRIPTION
             ""
        ::= { tpmGroups 7 }


END





































R. Dietz, R. Cole       Expires December 10, 2002              [Page 50]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


8.  Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to per-
   tain 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 implementers 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.

9.  Acknowledgements

   This memo has been produced with a great deal of assistance from
   David Craver, Joseph Maixner and John Metzger of Hifn, Inc. The
   authors also gratefully acknowledge the beneficial discussions they
   have had with Carter Bullard of QoSient, LLC.  The tpmMetricDefTable
   was taken from Andy Bierman's PM-CAPs draft. Finally, this MIB draws
   heavily from the work of Steve Waldbusser and his APM MIB [APM].





















R. Dietz, R. Cole       Expires December 10, 2002              [Page 51]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


10.  References

[RFC2571]   Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
            for Describing SNMP Management Frameworks", RFC 2571, April
            1999.

[RFC1155]   Rose, M., and K. McCloghrie, "Structure and Identification
            of Management Information for TCP/IP-based Internets", STD
            16, RFC 1155, May 1990.

[RFC1212]   Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
            16, RFC 1212, March 1991.

[RFC1215]   M. Rose, "A Convention for Defining Traps for use with the
            SNMP", RFC 1215, March 1991.

[RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Structure of Management Infor-
            mation Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Textual Conventions for
            SMIv2", STD 58, RFC 2579, April 1999.

[RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Conformance Statements for
            SMIv2", STD 58, RFC 2580, April 1999.

[RFC1157]   Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
            Network Management Protocol", STD 15, RFC 1157, May 1990.

[RFC1901]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Introduction to Community-based SNMPv2", RFC 1901, January
            1996.

[RFC1906]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Transport Mappings for Version 2 of the Simple Network Man-
            agement Protocol (SNMPv2)", RFC 1906, January 1996.

[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 Management Proto-
            col (SNMPv3)", RFC 2574, April 1999.





R. Dietz, R. Cole       Expires December 10, 2002              [Page 52]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


[RFC1905]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Pro-
            tocol Operations for Version 2 of the Simple Network Manage-
            ment 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 Manage-
            ment Protocol (SNMP)", RFC 2575, April 1999.

[RFC2570]   Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduc-
            tion to Version 3 of the Internet-standard Network Manage-
            ment Framework", RFC 2570, April 1999.

[RFC2021]   S. Waldbusser, "Remote Network Monitoring Management Infor-
            mation Base Version 2 using SMIv2", RFC 2021, January 1997.

[HCRMON]    S. Waldbusser, "Remote Network Monitoring Management Infor-
            mation Base for High Capacity Networks", draft-ietf-rmonmib-
            hcrmon-04.txt, October 1998.

[RFC2074]   Bierman, A., and R. Iddon, "Remote Network Monitoring MIB
            Protocol Identifiers", RFC 2074, January 1997.

[APM]       S. Waldbusser, "Application Performance Measurement MIB",
            draft-ietf-rmonmib-apm-mib-07.txt, April 23, 2002.

[PM]        A. Bierman, "Performance Measurement Capabilities MIB",
            draft-ietf-rmonmib-pmcaps-02.txt, November 24, 2000.

[PM]        Bierman, A., Dietz, R. and A. Warth "Application Verbs MIB",
            draft-ietf-rmonmib-appverbs-02.txt, March 24, 2002.


















R. Dietz, R. Cole       Expires December 10, 2002              [Page 53]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


11.  Security Considerations

   There are a number of management objects defined in this MIB that
   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 envi-
   ronment without proper protection can have a negative effect on net-
   work operations.

   There are a number of managed objects in this MIB that may contain
   sensitive information.

   It is thus important to control even GET access to these objects and
   possibly to even encrypt the values of these object when sending them
   over the network via SNMP.  Not all versions of SNMP provide features
   for such a secure environment.

   In order to implement this MIB, an agent must make certain management
   information available about protocols and network addresses used
   within a managed system, which may be considered sensitive in some
   network environments.

   Therefore, a network administrator may wish to employ instance-level
   access control, and configure the TPM MIB access (e.g., community
   strings in SNMPv1 and SNMPv2C), such that certain instances within
   this MIB (e.g., tpmReportMetricStatisticN), are excluded from partic-
   ular MIB views.

   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 fea-
   tures 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 config-
   ured to give access to the objects only to those principals (users)
   that have legitimate rights to indeed GET or SET (change/cre-
   ate/delete) them.








R. Dietz, R. Cole       Expires December 10, 2002              [Page 54]

INTERNET DRAFT                   TPM MIB                   June 10, 2002


12.  Author's Address

     Russell Dietz
     Hifn, Inc.
     750 University Ave
     Los Gatos, CA, USA 95032-7695
     Tel: +1 408 399-3623
     Fax: +1 408 399-3501
     E-mail: rdietz@hifn.com

     Robert Cole
     AT&T Labs
     330 Saint Johns Street,
     2nd Floor
     Havre de Grace, MD, USA 21078
     Tel: +1 410 939-8732
     Fax: +1 410 939-8732
     E-mail: rgcole@att.com"

A.  Full Copyright Statement

   Copyright (C) The Internet Society (2002).  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 doc-
   ument 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 MER-
   CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."






R. Dietz, R. Cole       Expires December 10, 2002              [Page 55]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/