< draft-ietf-rmonmib-tpm-mib-13.txt   draft-ietf-rmonmib-tpm-mib-14.txt >
Internet Draft Russell Dietz Internet Draft Russell Dietz
Hifn, Inc. Hifn, Inc.
Robert Cole Robert Cole
JHU/APL JHU/APL
January 12, 2004 June 28, 2004
Transport Performance Metrics MIB Transport Performance Metrics MIB
<draft-ietf-rmonmib-tpm-mib-13.txt> <draft-ietf-rmonmib-tpm-mib-14.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [RFC2026]. all provisions of Section 10 of RFC2026 [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Distribution of this document is unlimited. Please send comments to Distribution of this document is unlimited. Please send comments to
the authors, <rdietz@hifn.com> and <rgcole@att.com>. the authors, <rdietz@hifn.com> and <robert.cole@jhuapl.edu>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for monitoring In particular, it describes managed objects used for monitoring
selectable performance metrics and statistics derived from the selectable performance metrics and statistics derived from the
monitoring of network packets and sub-application level transactions. monitoring of network packets and sub-application level transactions.
The metrics are defined through reference to existing IETF, ITU and The metrics can be defined through reference to existing IETF, ITU
other standards organizations' documents. The monitoring covers both and other standards organizations' documents. The monitoring covers
passive and active traffic generation sources. both passive and active traffic generation sources.
1. Table of Contents 1. Table of Contents
Copyright Notice . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Copyright Notice . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1. Table of Contents . . . . . . . . . . . . . . . . . . . . . . 3 1. Table of Contents . . . . . . . . . . . . . . . . . . . . . . 3
2. The SNMP Management Framework . . . . . . . . . . . . . . . . 4 2. The SNMP Management Framework . . . . . . . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Report Aggregations . . . . . . . . . . . . . . . . . . . . . 6 3.2. Report Aggregations . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 3, line 30 skipping to change at page 3, line 30
4. Statistics Perspective . . . . . . . . . . . . . . . . . . . . 9 4. Statistics Perspective . . . . . . . . . . . . . . . . . . . . 9
4.1. Statistics Structure . . . . . . . . . . . . . . . . . . . . . 10 4.1. Statistics Structure . . . . . . . . . . . . . . . . . . . . . 10
4.2. Statistics Analysis . . . . . . . . . . . . . . . . . . . . . 11 4.2. Statistics Analysis . . . . . . . . . . . . . . . . . . . . . 11
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Intellectual Property . . . . . . . . . . . . . . . . . . . . 53 6. Intellectual Property . . . . . . . . . . . . . . . . . . . . 53
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53
8. Normative References . . . . . . . . . . . . . . . . . . . . . 54 8. Normative References . . . . . . . . . . . . . . . . . . . . . 54
9. Informative References . . . . . . . . . . . . . . . . . . . . 55 9. Informative References . . . . . . . . . . . . . . . . . . . . 55
10. Security Considerations . . . . . . . . . . . . . . . . . . . 56 10. Security Considerations . . . . . . . . . . . . . . . . . . . 56
11. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 58 11. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 58
A. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 59 12. Full Copyright Statement . . . . . . . . . . . . . . . . . . 59
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Overview 3. Overview
This document continues the architecture created in the RMON2-MIB This document continues the architecture created in the RMON2-MIB
[RFC2021] by providing a major feature upgrade, primarily by [RFC2021] by providing a major feature upgrade, primarily by
providing new metrics and studies to assist in the analysis of providing new metrics and studies to assist in the analysis of
performance for transaction flows in the network, in direct performance for sub-application transaction flows in the network, in
relationship to the transporting of application layer protocols. direct relationship to the transporting of application layer
protocols.
Performance monitoring agents have been widely used to analyze the Performance monitoring agents have been widely used to analyze the
parameters and metrics related to the perceived performance of parameters and metrics related to the perceived performance of
distributed applications and services in networks. The metrics distributed applications and services in networks. The metrics
collected by these agents has ranged from basic response time to a collected by these agents have ranged from basic response time to a
combination of metrics related to the loss and re-transmission of combination of metrics related to the loss and re-transmission of
datagrams and PDUs. While the metrics are becoming more useful in the datagrams and PDUs. While the metrics are becoming more useful in the
implementation of service level monitoring and troubleshooting tools, implementation of service level monitoring and troubleshooting tools,
the lack of a standard method to report these in has limited the the lack of a standard method to report these has limited the
deployment to very specific customer needs and areas. deployment to very specific customer needs and areas.
This document is intended to create a general framework for the This document is intended to create a general framework for the
collection and reporting of performance related metrics on collection and reporting of performance related metrics on sub-
transaction flows in a network. The MIB in this document in directly application level transaction flows in a network. The MIB in this
linked to the current RMON2-MIB [RFC2021] and uses the Protocol document in directly linked to the current RMON2-MIB [RFC2021] and
Directory as a key component in reporting the layering involved in uses the Protocol Directory as a key component in reporting the
the sub-application level transaction flows. layering involved in the sub-application level transaction flows.
The specific objectives of this document are to: The specific objectives of this document are to:
+ Provide a drill-down capability to compliment the user-perceived + Provide a drill-down capability to compliment the user-perceived
monitoring defined within the APM-MIB [RFCXXX1]. This capability monitoring defined within the APM-MIB [RFC3729]. This capability
is intended to support trouble resolution, further is intended to support trouble resolution, further
characterization of performance, and a finer granularity of characterization of performance, and a finer granularity of
monitoring capabilities. The APM-MIB provides a method for monitoring capabilities. The APM-MIB provides a method for
retrieving aggregated measurement data of the end-user's retrieving aggregated measurement data of the end-user's
perception of application-level performance. APM additionally perception of application-level performance. APM additionally
provides thresholding and associated alarms in the event the end- provides thresholding and associated alarms in the event the end-
user perceived performance degrades below defined thresholds. The user perceived performance degrades below defined thresholds. The
TPM-MIB compliments the APM-MIB capabilities by monitoring sub- TPM-MIB compliments the APM-MIB capabilities by monitoring sub-
application level transaction aspects not typically perceived by application level transaction aspects not typically perceived by
the end-user. As an example, APM-MIB provides response time the end-user. As an example, APM-MIB provides response time
statistics of a typical web-browser application. This application statistics of a typical web-browser application. This application
typically consists of DNS transaction, TCP connection typically consists of DNS transactions, TCP connection
establishment (or multiple establishments), HTTP download of the establishment (or multiple establishments), HTTP download of the
base page and multiple downloads of the various embedded objects. base page and multiple downloads of the various embedded objects.
Ideally TPM-MIB would provide statistics on the performance Ideally TPM-MIB would provide statistics on the performance
aspects of these multiple sub-application level transactions. aspects of these multiple sub-application level transactions.
+ Provide additional performance metrics and related statistics. + Provide additional performance metrics and related statistics.
For trouble shooting and a finer granularity of performance For trouble shooting and a finer granularity of performance
monitoring, it is useful to provide measurements of additional monitoring, it is useful to provide measurements of additional
metrics beyond those supported by the APM-MIB. metrics beyond those supported by the APM-MIB.
+ Support standards based metrics and associated statistical + Support standards based metrics and associated statistical
aggregation by defining methods to reference those standards. The aggregation by defining methods to reference those standards. The
TPM-MIB provides a capability to describe metrics by reference to TPM-MIB provides a capability to describe metrics by reference to
appropriate IETF, ITU or other standards defining metrics. This appropriate IETF, ITU or other, including enterprise specific,
capability is provided through the tpmMetricsDefTable. standards bodies defining metrics. This capability is provided
through the tpmMetricsDefTable.
Specifically, this MIB itself does not make references to such
IETF, ITU and other organization's metric specifications. What it
does do is to allow for the setup of the tpmMetricDefTable that
does reference such IETF, ITU and other metric specifications, and
it allows to (dynamically) list pointers to such specifications in
this table. The following objects do allow for that, and the
DESCRIPTION clauses (of the below objects) explain how such is
done:
tpmMetricDefName OBJECT-TYPE
tpmMetricDefReference OBJECT-TYPE
tpmMetricDefGlobalID OBJECT-TYPE
The tpmMetricDefGlobalID object contains a reference to the Object
ID in a metrics registration MIB being developed in the IPPM
Working Group at the IETF, e.g., the IPPM-REGISTRY-MIB [RFCXXX3],
which defines the metric. For metrics defined within the IPPM
Working Group, which are included in the IPPM-REGISTRY-MIB, this
object is used to reference those metrics directly. For metrics
not included within the IPPM-REGISTRY-MIB, the value of this
object is set to 0.0 for none.
Examples of appropriate references include the ITU-T
Recommendation Y.1540 [Y.1540] on IP packet transfer performance
metrics or the IETF documents from the IPPM WG, e.g., RFC2681 on
the round trip delay metric [RFC2681] or RFC3393 on the delay
variation metric [RFC3393] or others, including RFC2679 [RFC2679],
RFC2680 [RFC2680], and RFC3432 [RFC3432]. While no specific
metric is mandatory, implementations should, at a minimum, support
a round trip delay and a round trip loss metric.
+ Provide (as an option) a table storing the measurements of the + Provide (as an option) a table storing the measurements of the
metrics on a transaction by transaction basis. There are times metrics on a transaction by transaction basis. There are times
when it is useful to have access to the raw measurements. The when it is useful to have access to the raw measurements. The
tpmCurReportTable optionally provides access to this capability. tpmCurReportTable optionally provides access to this capability.
While this document outlines the basic measurements of performance in While this document outlines the basic measurements of performance in
regard to the transporting of application flows, it does not attempt regard to the transporting of application flows, it does not attempt
to measure or provide a means to measure the actual perceived to measure or provide a means to measure the actual perceived
performance of the application transactions or quality. The detailed performance of the application transactions or quality. The detailed
measurements of end-user perceived performance is directly related to measurements of end-user perceived performance is directly related to
this document and may be found in the APM-MIB [RFCXXX1]. this document and may be found in the APM-MIB [RFC3729].
The objects defined in this document are intended as an interface The objects defined in this document are intended as an interface
between an RMON agent and an RMON management application and are not between an RMON agent and an RMON management application and are not
intended for direct manipulation by humans. While some users may intended for direct manipulation by humans. While some users may
tolerate the direct display of some of these objects, few will tolerate the direct display of some of these objects, few will
tolerate the complexity of manually manipulating objects to tolerate the complexity of manually manipulating objects to
accomplish row creation. These functions should be handled by the accomplish row creation. These functions should be handled by the
management application. management application.
3.1. Terms 3.1. Terms
skipping to change at page 6, line 4 skipping to change at page 6, line 35
The objects defined in this document are intended as an interface The objects defined in this document are intended as an interface
between an RMON agent and an RMON management application and are not between an RMON agent and an RMON management application and are not
intended for direct manipulation by humans. While some users may intended for direct manipulation by humans. While some users may
tolerate the direct display of some of these objects, few will tolerate the direct display of some of these objects, few will
tolerate the complexity of manually manipulating objects to tolerate the complexity of manually manipulating objects to
accomplish row creation. These functions should be handled by the accomplish row creation. These functions should be handled by the
management application. management application.
3.1. Terms 3.1. Terms
This document uses some terms that need introduction: This document uses some terms that need introduction:
DataSource DataSource
A source of data for monitoring purposes. This term is used A source of data for monitoring purposes. This term is used
exactly as defined in the RMON2-MIB [RFC2021]. exactly as defined in the RMON2-MIB [RFC2021].
protocol protocol
A specific protocol encapsulation, as identified for monitoring A specific protocol encapsulation, as identified for monitoring
purposes. This term is used exactly as defined in the RMON purposes. This term is used exactly as defined in the RMON
Protocol Identifiers document [RFC2895]. Protocol Identifiers document [RFC2895].
performance metric performance metric
A specific statistical reporting metric, as identified for A specific, measured reporting metric, as identified for
monitoring purposes. There can be several metrics reported by monitoring purposes. There can be several metrics reported by
an agent in the same implementation. The metrics are an agent in the same implementation. The metrics are
extensible based on the agent implementation. extensible based on the agent implementation.
application application
A network-based, high-level protocol performing useful work A network-based, high-level protocol performing useful work
to an end-user of end-system. Typically the application to an end-user of end-system. Typically the application
performs multiple request/response transactions to complete performs multiple request/response transactions to complete
its work. E.g., a web-application downloading a web page its work. E.g., a web-application downloading a web page
completes DNS, TCP-connect and multiple HTTP GET transactions completes DNS, TCP-connect and multiple HTTP GET transactions
prior to completing its task. prior to completing its task.
transactions transactions
Elemental request/response transactions comprising more Elemental request/response transactions comprising more
complex network-based applications. complex network-based applications. E.g., a transaction
may include an ftp get request and the file download in
response.
3.2. Report Aggregation 3.2. Report Aggregation
This MIB module provides functions to aggregate measurements into This MIB module provides functions to aggregate measurements into
higher level summaries identical to the aggregation defined in the higher level summaries identical to the aggregation defined in the
APM-MIB [RFCXXX1]. In addition to temporal aggregation of data, the APM-MIB [RFC3729]. In addition to temporal aggregation of data, the
Textual Convention, TransactionAggregationType, is imported from the Textual Convention, TransactionAggregationType, is imported from the
APM-MIB, which specifies the nature of the spatial aggregation APM-MIB, which specifies the nature of the spatial aggregation
employed. employed.
3.3. Structure of the MIB 3.3. Structure of the MIB
The objects are arranged in the following groups: The objects are arranged in the following groups:
-- tpmCapabilitiesGroup -- tpmCapabilitiesGroup
skipping to change at page 7, line 44 skipping to change at page 8, line 32
uncompleted measurements for the current configured report for those uncompleted measurements for the current configured report for those
transactions caught in progress. A history of these transactions is transactions caught in progress. A history of these transactions is
also maintained once the current transaction has completed. The also maintained once the current transaction has completed. The
tpmCurrentReportsGroup consists of the tpmCurReportTable and the tpmCurrentReportsGroup consists of the tpmCurReportTable and the
tpmCurReportSize object. tpmCurReportSize object.
3.3.4. The tpmExceptionReportsGroup 3.3.4. The tpmExceptionReportsGroup
The tpmExceptionReportsGroup is used to link immediate notifications The tpmExceptionReportsGroup is used to link immediate notifications
of transactions that exceed certain thresholds defined in the of transactions that exceed certain thresholds defined in the
apmExceptionGroup [RFCXXX1]. This group reports the aggregated sub- apmExceptionGroup [RFC3729]. This group reports the aggregated sub-
application measurements for those applications exceeding thresholds. application measurements for those applications exceeding thresholds.
The tpmExceptionReportsGroup consists of the tpmExcpReportTable. The tpmExceptionReportsGroup consists of the tpmExcpReportTable.
3.4. Statistics for Aggregation of Data - Conventions 3.4. Statistics for Aggregation of Data - Conventions
In order to measure the performance of traffic flows in a network, In order to measure the performance of traffic flows in a network,
the proper analysis of a set of statistics is required. Since a 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 large majority of the statistics have a basis of time, the use of a
simple statistical model is feasible. Therefore, the MIB definitions simple statistical model is feasible. Therefore, the MIB definitions
within this document all use a basic set of statistical computed within this document all use a basic set of statistical computed
values to assist in further analysis by a management application. values to assist in further analysis by a management application.
The remaining subsections in this section detail the common The remaining subsections in this section detail the common
structured features the are applied to the performance metrics in the structured features the are applied to the performance metrics in the
statistical format described above. The tpmMetricsDefTable statistical format described above. The tpmMetricsDefTable
skipping to change at page 8, line 48 skipping to change at page 9, line 33
supported by an instance of the TPM-MIB. The performance metric supported by an instance of the TPM-MIB. The performance metric
index values throughout the document are a direct reference to the index values throughout the document are a direct reference to the
metrics defined in that table. The table defines metrics by directly metrics defined in that table. The table defines metrics by directly
referencing other standards that provide definitive descriptions of referencing other standards that provide definitive descriptions of
the metric. the metric.
3.8. Relationship to Application Performance Measurement MIB 3.8. Relationship to Application Performance Measurement MIB
This document uses the apmReportControlIndex, appLocalIndex and This document uses the apmReportControlIndex, appLocalIndex and
apmReportIndex as outlined in the current Application Performance apmReportIndex as outlined in the current Application Performance
Measurement MIB draft document [RFCXXX1]. These objects are used to Measurement MIB [RFC3729]. These objects are used to create a
create a reference link for the purpose of reporting transaction flow reference link for the purpose of reporting transaction flow details
details on application level measurements. As such, the TPM-MIB is on application level measurements. As such, the TPM-MIB is designed
designed to provide a drill-down extension to the APM-MIB. Further, to provide a drill-down extension to the APM-MIB. Further, it draws
it draws heavily on the ideas and designs laid out in the APM-MIB. heavily on the ideas and designs laid out in the APM-MIB.
4. Statistics Perspective 4. Statistics Perspective
When dealing with time based measurements on application data packets When dealing with time based measurements on application data packets
it would be ideal if all the timestamps and related data could be it would be ideal if all the timestamps and related data could be
stored and forwarded for later analysis. However when faced with stored and forwarded for later analysis. However when faced with
thousands of conversations per second on ever faster networks, thousands of conversations per second on ever faster networks,
storing all the data, even if compressed, would take too much storing all the data, even if compressed, would take too much
processing, memory, and manager download time to be practical. processing, memory, and manager download time to be practical.
skipping to change at page 9, line 19 skipping to change at page 10, line 4
it would be ideal if all the timestamps and related data could be it would be ideal if all the timestamps and related data could be
stored and forwarded for later analysis. However when faced with stored and forwarded for later analysis. However when faced with
thousands of conversations per second on ever faster networks, thousands of conversations per second on ever faster networks,
storing all the data, even if compressed, would take too much storing all the data, even if compressed, would take too much
processing, memory, and manager download time to be practical. processing, memory, and manager download time to be practical.
It is important to note that in dealing with network data we will be It is important to note that in dealing with network data we will be
dealing with statistical populations and not samples. Statistics dealing with statistical populations and not samples. Statistics
books deal with both because the math is similar. In collecting books deal with both because the math is similar. In collecting
agent data a population, i.e., all the data, must be processed. agent data a population, i.e., all the data, must be processed.
Because of the nature of application protocols just sampling some of Because of the nature of application protocols just sampling some of
the packets will not give good results. Missing just one critical the packets will not give good results. Missing just one critical
packet, such as one that specified an ephemeral port on which data packet, such as one that specified an ephemeral port on which data
will be transmitted, or what application will be run, can cause much will be transmitted, or what application will be run, can cause much
valid data to be lost. valid data to be lost.
The time-based measurements the agent collects will come from The time-based measurements the agent collects will come from
examining the entire group of data, i.e., the population. The examining the entire group of data, i.e., the population. The
population will be finite. The agent will seek only to provide population will be finite. The agent will seek only to provide
information that will describe the actual data. Analysis of that data information that will describe the actual data. Analysis of that data
will be left to the management station. will be left to the management station.
The simplest form of representing a group of data is by frequency The simplest form of representing a group of data is by frequency
distributions, buckets. Statistics provides a great many ways of distributions, i.e., buckets. Statistics provides a great many ways
analyzing this type of data and there are some rules in creating the of analyzing this type of data and there are some rules in creating
buckets. First the range needs to be known. Second a bucket size the buckets. First the range needs to be known. Second a bucket size
needs to be determined. Fixed bucket sizes are best, while variable needs to be determined. Fixed bucket sizes are best, while variable
may be used if needed. However the statistics texts tend to only may be used if needed. However the statistics texts tend to only
refer to operations of fixed size buckets. This method of describing refer to operations of fixed size buckets. This method of describing
data is expensive for a agent to implement. First the agent must data is expensive for a agent to implement. First the agent must
process a great amount of data at a time. In storing the data, process a great amount of data at a time. In storing the data,
determine the range, then locating the buckets and then fill in the 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 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 range and bucket sizes in the beginning can be problematical as
the agent may have to adjust the values for each of the applications the agent may have to adjust the values for each of the applications
it collects data on. Such numbers can be in the thousands. it collects data on. Such numbers can be in the thousands.
Additional complexity arises in adding new protocols and even in Additional complexity arises in adding new protocols and even in
describing the buckets themselves to the management application. This describing the buckets themselves to the management application. This
is the approach taken in the APM-MIB. is the approach taken in the APM-MIB.
A complimentary approach is to provide frequency distribution A complimentary approach is to provide frequency distribution
statistics. Frequency distribution statistics describes aggregation statistics. Frequency distribution statistics describes aggregation
such as mean and standard deviation that can be obtained by summation such as mean and standard deviation that can be obtained by summation
functions on the individual data elements in a population. Analysis functions on the individual data elements in a population. Analysis
of the data described by these functions has been greatly studied and of the data described by these functions has been greatly studied and
interpretation of these values is available to anyone with an interpretation of these values is available to anyone with an
introduction to statistics. In fact, frequency distributions are introduction to statistics. In fact, frequency distributions are
routinely analyzed to generate these varied numbers which are then routinely analyzed to generate these varied numbers which are then
used for further analysis. Also note that frequency distributions by used for further analysis. Also note that frequency distributions by
their very nature provide an exact characterization of the data. their very nature provide an exact characterization of the data.
Whereas buckets, will introduce error factors that are not present Whereas buckets, will introduce error factors that are not present
with direct analysis by a summation type formulas. Because the TPM- 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 MIB provides a drill-down capability to the APM MIB it has to measure
and store much more information than the APM-MIB. For this reason, and store much more information than the APM-MIB. For this reason,
and to compliment the APM-MIB, the TPM-MIB relies on statistical and to compliment the APM-MIB, the TPM-MIB relies on statistical
descriptions rather than a bucket description of the measurement descriptions rather than a bucket description of the measurement
data. data.
The agent will provide data that can be used to calculate the most The agent will provide data that can be used to calculate the most
basic and useful statistical aggregates. The agent will not perform basic and useful statistical aggregates. The agent will not perform
the calculations and provide the statistical measurement directly. the calculations and provide the statistical measurement directly.
There are several reason why this is not desired. The first is that There are several reason why this is not desired. The first is that
to find the final measurement can be expensive in terms of to find the final measurement can be expensive in terms of
skipping to change at page 11, line 12 skipping to change at page 11, line 46
S(X) sum of all the data point values 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 S(X2) sum of all the data point values squared for the metric
Xmax maximum data point value for the metric Xmax maximum data point value for the metric
Xmin minimum data point value for the metric Xmin minimum data point value for the metric
S(I*X) sum of the data points multiplied by their order, i.e., S(I*X) sum of the data points multiplied by their order, i.e.,
= SUM from i=1 to N { i*X sub i} = SUM from i=1 to N { i*X sub i}
A performance metric is used to describe events over a time interval. A performance metric is used to describe events over a time interval.
The measurement points can be processed immediately into the The measurement points can be processed immediately into the
statistic and do not have to be stored for later processing. For statistic and do not have to be stored for later processing. For
example to count the number of events in a time interval it is 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 sufficient to increment a counter for each event. It is not
to cache all the events and then count them at the end of the necessary to cache all the events and then count them at the end of
interval. The statistic is also designed to be easily scalable in the interval. The statistic is also designed to be easily scalable in
terms of combining adjacent intervals. For example if an agent terms of combining adjacent intervals. For example if an agent
created a specific statistic every 30 seconds and a user table created a specific statistic every 30 seconds and a user table
interval was set to 60 seconds, the 60 second statistic could be interval was set to 60 seconds, the 60 second statistic could be
obtained by combining the two 30 second statistics. The following obtained by combining the two 30 second statistics. The following
rules will be applied when combining adjacent statistics. rules will be applied when combining adjacent statistics.
N S(N) N S(N)
S(X) S(S(X)) S(X) S(S(X))
S(X2) S(S(X2)) S(X2) S(S(X2))
Xmax MAX(Xmax) Xmax MAX(Xmax)
skipping to change at page 13, line 17 skipping to change at page 14, line 4
RowStatus, TEXTUAL-CONVENTION, TimeStamp, RowStatus, TEXTUAL-CONVENTION, TimeStamp,
StorageType FROM SNMPv2-TC --[RFC2579] StorageType FROM SNMPv2-TC --[RFC2579]
rmon, OwnerString FROM RMON-MIB --[RFC2819] rmon, OwnerString FROM RMON-MIB --[RFC2819]
protocolDirLocalIndex, protocolDirLocalIndex,
ZeroBasedCounter32 FROM RMON2-MIB --[RFC2021] ZeroBasedCounter32 FROM RMON2-MIB --[RFC2021]
ZeroBasedCounter64 FROM HCNUM-TC --[RFC2856] ZeroBasedCounter64 FROM HCNUM-TC --[RFC2856]
AppLocalIndex, TransactionAggregationType, AppLocalIndex, TransactionAggregationType,
RmonClientID, DataSourceOrZero, RmonClientID, DataSourceOrZero,
apmAppDirAppLocalIndex, apmExceptionIndex, apmAppDirAppLocalIndex, apmExceptionIndex,
apmReportGroup, apmExceptionGroup, apmReportGroup, apmExceptionGroup,
apmAppDirResponsivenessType FROM APM-MIB --[RFCXXX1] apmAppDirResponsivenessType FROM APM-MIB --[RFC3729]
SspmClockSource, SspmClockMaxSkew, SspmClockSource, SspmClockMaxSkew,
SspmMicroSeconds FROM SSPM-MIB; --[RFCXXX2] SspmMicroSeconds FROM SSPM-MIB; --[RFCXXX2]
-- Transaction Performance Monitoring MIB -- Transaction Performance Monitoring MIB
tpmMIB MODULE-IDENTITY tpmMIB MODULE-IDENTITY
LAST-UPDATED "200401121500Z" -- 12 January 2004 LAST-UPDATED "200406281500Z" -- 28 June 2004
ORGANIZATION "IETF RMON MIB Working Group" ORGANIZATION "IETF RMON MIB Working Group"
CONTACT-INFO CONTACT-INFO
"E-mail: rmonmib@ietf.org "E-mail: rmonmib@ietf.org
Subscribe: rmonmib-request@ietf.org Subscribe: rmonmib-request@ietf.org
w/ msg body: subscribe rmonmib w/ msg body: subscribe rmonmib
Russell Dietz Russell Dietz
Hifn, Inc. Hifn, Inc.
Postal: 750 University Ave Postal: 750 University Ave
Los Gatos, CA 95032-7695 Los Gatos, CA 95032-7695
skipping to change at page 14, line 14 skipping to change at page 14, line 47
USA USA
Tel: +1 443 778-6951 Tel: +1 443 778-6951
E-mail: robert.cole@jhuapl.edu" E-mail: robert.cole@jhuapl.edu"
DESCRIPTION DESCRIPTION
"This module defines extensions to the RMON2-MIB module "This module defines extensions to the RMON2-MIB module
for the collection of Performance Metrics related to for the collection of Performance Metrics related to
application traffic in a network. In particular, application traffic in a network. In particular,
it describes managed objects used for monitoring it describes managed objects used for monitoring
selectable performance metrics and statistics selectable performance metrics and statistics
derived from the monitoring of network packets and derived from the monitoring of network packets and
transport protocol states. sub-application level transactions.
In order to maintain the RMON 'look-and-feel', some of In order to maintain the RMON 'look-and-feel', some of
the text from the RMON2 [RFC2021] and HC-RMON [RFC3273] the text from the RMON2 [RFC2021] and HC-RMON [RFC3273]
MIBs by Steve Waldbusser have been used in this MIB module. MIBs by Steve Waldbusser have been used in this MIB module.
Copyright (C) The Internet Society (year). This version of Copyright (C) The Internet Society (year). This version of
this MIB module is part of RFC xxxx; see the RFC itself for this MIB module is part of RFC xxxx; see the RFC itself for
full legal notices." full legal notices."
REVISION "200401121500Z" -- 12 January 2004 REVISION "200406281500Z" -- 28 June 2004
DESCRIPTION DESCRIPTION
"The original version of this MIB module, "The original version of this MIB module,
published as RFCXXXX." published as RFCXXXX."
-- RFC-Editor assigns XXXX -- RFC-Editor assigns XXXX
::= { rmon nn } -- To be assigned by IANA ::= { rmon nn } -- To be assigned by IANA
-- We suggest a value of 30 for nn -- We suggest a value of 30 for nn
-- --
-- Object Identifier Assignments -- Object Identifier Assignments
-- --
skipping to change at page 19, line 45 skipping to change at page 20, line 31
-- TPM Metric Definitions Table -- TPM Metric Definitions Table
-- --
tpmMetricDefTable OBJECT-TYPE tpmMetricDefTable OBJECT-TYPE
SYNTAX SEQUENCE OF TpmMetricDefEntry SYNTAX SEQUENCE OF TpmMetricDefEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tpmMetricDefTable describes the metrics "The tpmMetricDefTable describes the metrics
available to the TPM-MIB. The tpmMetricDefTable available to the TPM-MIB. The tpmMetricDefTable
defines metrics by referencing existing IETF, can define metrics by referencing existing IETF,
ITU and other standards organizations' documents. ITU and other standards organizations' documents,
including enterprise specific documents.
Examples of appropriate references include the
ITU-T Recommendation Y.1540 [Y.1540] on IP
packet transfer performance metrics or the
IETF documents from the IPPM WG, e.g., RFC2681
on the round trip delay metric [RFC2681] or
RFC3393 on the delay variation metric [RFC3393]
or others, including RFC2679 [RFC2679], RFC2680
[RFC2680], and RFC3432 [RFC3432]. While no
specific metric is mandatory, implementations
should, at a minimum, support a round trip delay
and a round trip loss metric.
This table contains one row per metric supported by this This table contains one row per metric supported by this
agent, and should be populated during system agent, and should be populated during system
initialization." initialization."
::= { tpmCapabilities 6 } ::= { tpmCapabilities 6 }
tpmMetricDefEntry OBJECT-TYPE tpmMetricDefEntry OBJECT-TYPE
SYNTAX TpmMetricDefEntry SYNTAX TpmMetricDefEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular metric." "Information about a particular metric."
INDEX { tpmMetricDefinitionID } INDEX { tpmMetricDefinitionID }
::= { tpmMetricDefTable 1 } ::= { tpmMetricDefTable 1 }
skipping to change at page 21, line 52 skipping to change at page 22, line 49
the value, e.g., 'Type-P-Round-Trip-Delay'." the value, e.g., 'Type-P-Round-Trip-Delay'."
::= { tpmMetricDefEntry 4 } ::= { tpmMetricDefEntry 4 }
tpmMetricDefReference OBJECT-TYPE tpmMetricDefReference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a reference to the document which "This object contains a reference to the document which
defines this metric. If this document is available online defines this metric. If this document is available online
via electronic download, then a URL should be specified in via electronic download, then a dereferencable URL
this object. should be specified in this object. The implementation
must support an HTTP URL type and may support additional
types of dereferencable URLs such as an FTP type.
For example, if this tpmMetricDefEntry identified the IPPM For example, if this tpmMetricDefName identified the IPPM
metric 'Type-P-Round-Trip-Delay', then this object should metric 'Type-P-Round-Trip-Delay', then this object should
contain the value, e.g., contain the value, e.g.,
'http://www.ietf.org/rfc/rfc2681.txt'." 'http://www.ietf.org/rfc/rfc2681.txt'."
::= { tpmMetricDefEntry 5 } ::= { tpmMetricDefEntry 5 }
tpmMetricDefGlobalID OBJECT-TYPE tpmMetricDefGlobalID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a reference to the Object ID "This object contains a reference to the Object ID
in a metrics registration MIB being developed in a metrics registration MIB being developed
in the IPPM WG at the IETF, e.g., the in the IPPM WG at the IETF, e.g., the
IPPM-REGISTRY-MIB, which defines the metric. IPPM-REGISTRY-MIB [RFCXXX3], which defines the metric.
In the event that this metric has no corresponding In the event that this metric has no corresponding
OID or until the IPPM-REGISTRY-MIB is defined, then OID or until the IPPM-REGISTRY-MIB is defined, then
the value should be set to 0.0 for none." the value should be set to 0.0 for none."
::= { tpmMetricDefEntry 6 } ::= { tpmMetricDefEntry 6 }
-- --
-- The tpmAggregateReportsGroup -- The tpmAggregateReportsGroup
-- --
tpmAggrReportCntrlTable OBJECT-TYPE tpmAggrReportCntrlTable OBJECT-TYPE
skipping to change at page 24, line 43 skipping to change at page 25, line 41
If the measurement is being performed by a probe, this should If the measurement is being performed by a probe, this should
be set to interface or port where data was received for be set to interface or port where data was received for
analysis. If the measurement isn't being performed by a probe, analysis. If the measurement isn't being performed by a probe,
this should be set to the primary interface over which the this should be set to the primary interface over which the
measurement is being performed. If the measurement isn't being measurement is being performed. If the measurement isn't being
performed by a probe and there is no primary interface or this performed by a probe and there is no primary interface or this
information isn't known, this object should be set to 0.0. information isn't known, this object should be set to 0.0.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero, If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object is set to the corresponding then this object is set to the corresponding
apmReportControlTable object in the APM-MIB [RFCXXX1]. apmReportControlTable object in the APM-MIB [RFC3729].
This object may not be modified if the associated This object may not be modified if the associated
tpmAggrReportCntrlStatus object is equal to active(1)." tpmAggrReportCntrlStatus object is equal to active(1)."
::= { tpmAggrReportCntrlEntry 3 } ::= { tpmAggrReportCntrlEntry 3 }
tpmAggrReportCntrlAggrType OBJECT-TYPE tpmAggrReportCntrlAggrType OBJECT-TYPE
SYNTAX TransactionAggregationType SYNTAX TransactionAggregationType
-- INTEGER { -- INTEGER {
-- flows(1), -- flows(1),
-- clients(2), -- clients(2),
skipping to change at page 53, line 36 skipping to change at page 54, line 36
7. Acknowledgements 7. Acknowledgements
This memo has been produced with a great deal of assistance from This memo has been produced with a great deal of assistance from
David Craver, Joseph Maixner and John Metzger of Hifn, Inc. The David Craver, Joseph Maixner and John Metzger of Hifn, Inc. The
authors also gratefully acknowledge the beneficial discussions they authors also gratefully acknowledge the beneficial discussions they
have had with Carter Bullard of QoSient, LLC. The tpmMetricDefTable have had with Carter Bullard of QoSient, LLC. The tpmMetricDefTable
was taken from Andy Bierman's performance management capabilities was taken from Andy Bierman's performance management capabilities
draft, which was a draft proposed early on in the RMON WG during the draft, which was a draft proposed early on in the RMON WG during the
formation of the TPM and APM MIB work. Finally, this MIB module formation of the TPM and APM MIB work. Finally, this MIB module
draws heavily from the work of Steve Waldbusser and his APM-MIB draws heavily from the work of Steve Waldbusser and his APM-MIB
[RFCXXX1]. [RFC3729].
8. Normative References 8. Normative References
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management [RFC2021] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021, January Information Base Version 2 using SMIv2", RFC 2021, January
1997. 1997.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3",
RFC 2026, October 1996. RFC 2026, October 1996.
skipping to change at page 54, line 49 skipping to change at page 55, line 49
2002. 2002.
[RFC3395] Bierman, A., Bucci, C., Dietz, R. and A. Warth "Remote [RFC3395] Bierman, A., Bucci, C., Dietz, R. and A. Warth "Remote
Network Monitoring MIB Protocol Identifiers Reference Network Monitoring MIB Protocol Identifiers Reference
Extensions", RFC 3395, September 2002. Extensions", RFC 3395, September 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing Simple Network Management Protocol (SNMP) for Describing Simple Network Management Protocol (SNMP)
Management Frameworks", RFC 3411, December 2002. Management Frameworks", RFC 3411, December 2002.
[RFCXXX1] Waldbusser, S., "Application Performance Measurement MIB", [RFC3729] Waldbusser, S., "Application Performance Measurement MIB",
RFC XXX1, October 2003. RFC 3729, March 2004.
[RFCXXX2] Kalbfleisch, K., Cole, R.G. and D. Romascanu, "Definition of [RFCXXX2] Kalbfleisch, K., Cole, R.G. and D. Romascanu, "Definition of
Managed Objects for Synthetic Sources for performance Managed Objects for Synthetic Sources for performance
Monitoring Algorithms", RFC XXX2, January 2004. Monitoring Algorithms", RFC XXX2, January 2004.
[RFCXXX3] Stephan, E., "IPPM metrics registry", RFC XXX3, May 2004.
9. Informative References 9. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[Y.1540] The ITU-T Recommendation Y.1540, "IP Data Transport Service
- IP packet transfer performance metrics", ITU-T Rec.
Y.1540, December 2002.
[RFC2679] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay
Metric for IPPM", RFC 2679, September 1999.
[RFC2680] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-Way Packet
Loss Metric for IPPM" RFC 2680, September 1999.
[RFC2681] Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-Trip
Delay Metric for IPPM", RFC 2681, September 1999.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393,
November 2002.
[RFC3432] Raisanen, V., Grotefeld, G. and A. Morton, "Network
Performance Measurement with Periodic Streams", RFC 3432,
November 2002.
10. Security Considerations 10. Security Considerations
This MIB relates to a system which provides a passive monitoring This MIB relates to a system which provides a passive monitoring
capability of a broadcast subnet, a switched subnet or point-to-point capability of a broadcast subnet, a switched subnet or point-to-point
subnets. As such, it collects information relating to network layer subnets. As such, it collects information relating to network layer
addresses, traffic statistics relating to conversations and to addresses, traffic statistics relating to conversations and to
application-level activities. These statistics could be deemed application-level activities. These statistics could be deemed
sensitive in certain networking environments. sensitive in certain networking environments.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
skipping to change at page 58, line 24 skipping to change at page 59, line 24
Robert Cole Robert Cole
Johns Hopkins University Applied Physics Laboratory Johns Hopkins University Applied Physics Laboratory
MP2-170 MP2-170
11100 Johns Hopkins Road 11100 Johns Hopkins Road
Laurel, MD 20723-6099 Laurel, MD 20723-6099
USA USA
Tel: +1 443-778-6951 Tel: +1 443-778-6951
Email: robert.cole@jhuapl.edu Email: robert.cole@jhuapl.edu
A. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Intellectual Property
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an The IETF takes no position regarding the validity or scope of any
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING Intellectual Property Rights or other rights that might be claimed to
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING pertain to the implementation or use of the technology described in
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION this document or the extent to which any license under such rights
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF might or might not be available; nor does it represent that it has
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
* 2) The reference to RFCXXX1 throughout this document point * * 2) The reference to RFCXXX2 throughout this document point *
* to the current <draft-ietf-rmonmib-apm-mib-11.txt>. This * * to the current <draft-ietf-rmonmib-sspm-mib-12.txt>. This *
* MIB module imports TCs from this draft. Once the APM MIB *
* draft is published as an RFC, then the RFCXXX1 references *
* need to be replaced with the APM MIB RFC number. *
* *
* 3) The reference to RFCXXX2 throughout this document point *
* to the current <draft-ietf-rmonmib-sspm-mib-09.txt>. This *
* MIB module imports TCs from this draft. Once the SSPM MIB * * MIB module imports TCs from this draft. Once the SSPM MIB *
* draft is published as an RFC, then the RFCXXX2 references * * draft is published as an RFC, then the RFCXXX2 references *
* need to be replaced with the SSPM MIB RFC number. * * need to be replaced with the SSPM MIB RFC number. *
* * * *
* 3) The reference to RFCXXX3 throughout this document point *
* to the current <draft-ietf-ippm-metrics-registry-06.txt>. *
* This MIB module can reference OIDs from this draft. Once *
* published as an RFC, then the RFCXXX3 references *
* need to be replaced with the IPPM Metric Registry RFC *
* number. *
* *
*************************************************************** ***************************************************************
 End of changes. 48 change blocks. 
89 lines changed or deleted 171 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/