wdiff draft-ietf-ippm-reporting-mib-02.txt draft-ietf-ippm-reporting-mib-03.txt

Network Working Group E. Stephan/J. Jewitt
Internet Draft France Telecom R&D
Document: draft-ietf-ippm-reporting-mib-02.txt March 1st, draft-ietf-ippm-reporting-mib-03.txt June, 2003

IPPM reporting MIB

Status of this Memo

This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1].

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 made obsolete by other documents at
any time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

Abstract

This memo defines a portion of the Management Information Base (MIB)
designed for use with network management protocols in TCP/IP-based
internets.
In particular, this MIB specifies the objects used for managing the
results of the IPPM metrics measures, for pushing alarms, and for
reporting the measures results.

Table of Contents

1. Introduction................................................3 Introduction................................................2
2. The IPPM Framework..........................................3
3. The SNMP Management Framework...............................3
4. Overview....................................................5
4.1. Textual Conventions.........................................6
4.2.
4.2 Structure of the MIB........................................8
4.3. MIB.........................................8
4.3 Row identification in an application namespace.............10
4.4. namespace..............10
4.4 Relationship of IPPM REPORTING MIB tables............................11
5. IPPM-REPORTING-MIB conceptual presentation.................15
5.1. IPPM-REPORTING-MIB diagram.................................15
5.2. Conceptual programming interface...........................16
5.3. SNMP mapping...............................................16
6. tables...................11
5 Measurement architectures..................................17
6.1. architectures...................................12
5.1 Proxy architecture.........................................17
6.2. architecture..........................................12
5.2 Reporting architecture.....................................18
6.3. architecture......................................13
5.3 Gateway architecture.......................................20
6.4. Security...................................................20
7. architecture........................................15
5.4 Security....................................................15
6 Reporting mode integration.................................21
7.1. Integration................................................21
7.2. integration..................................16
6.1 Integration.................................................16
6.2 Setup of the measure.......................................21
7.3. measure network................................16
6.3 Setup of the a measurement report............................22
7.4. Writing report...............................16
6.4 Updating the results in history of the IPPM-REPORTING-MIB..............22
7.5. MIB.............................17
6.5 Report download and upload.................................23
7.6. upload..................................17
6.6 Default value..............................................23
8. Definition.................................................24
9. value...............................................17
7 Definition..................................................17
8 Security Considerations....................................67
9.1. Privacy....................................................67
9.2. Considerations.....................................71
8.1 VACM Access control.........................................71
8.2 Privacy.....................................................74
8.3 Measurement aspects........................................67
9.3. aspects.........................................74
8.4 Management aspects.........................................68
10. aspects..........................................75
9 Document management........................................69
10.1. management.........................................75
9.1 Open issues.................................................69
10.2. changes since release 00....................................69
10.3. issues.................................................76
9.2 Changes done since release 01....................................70
11. References.................................................72
12. Acknowledgments............................................73
13. 02...............................76
10 References..................................................77
11 Acknowledgments.............................................78
12 Authors Addresses..........................................73 Addresses...........................................78

1. Introduction
This memo defines a MIB for managing measures network measurements based upon
the IP performance metrics specified by the IPPM Working Group.

The definition of objects in the IPPM MIB are built on notions
introduced and discussed in the IPPM Framework document, RFC 2330
[ii].

This memo defines a Management Information Base (MIB), and as such it
is intended to be respectful of the "Boilerplate for IETF MIBs"
defined in http://www.ops.ietf.org/mib-boilerplate.html.

There are companion documents to the IPPM-REPORTING-MIB both in the
Transport Area (See section 2), and in the Operations and Management
Area (See section 3). The reader should be familiar with these
documents.

2. The IPPM Framework

The IPPM Framework consists of 3 major components:

A general framework for defining performance metrics, as described in
the Framework for IP Performance Metrics, RFC 2330 [2];

A set of standardized metrics which conform to this framework: The
IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; The One-way
Delay Metric for IPPM, RFC 2679 [iv]; The One-way Packet Loss Metric
for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC
2681 [vi].

Emerging metrics that are being specified in respect of this
framework.

3. The SNMP Management Framework

The SNMP Management Framework consists of five major components:

An overall architecture, described in RFC 2571 [6]. [2].

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 [7], [3], STD 16, RFC 1212 [8] [4] and RFC 1215 [9]. [5]. The second
version, called SMIv2, is described in STD 58, RFC 2578 [10], [6], STD 58,
RFC 2579 [11] [7] and STD 58, RFC 2580 [12]. [8].

Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [13]. [9]. A second version of the SNMP
message protocol, which is not an Internet standards track protocol,
is called SNMPv2c and described in RFC 1901 [14] [10] and RFC 1906 [15]. [11].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [15], [11], RFC 2572 [16] [12] and RFC 2574 [17]. [13].

Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [13]. [9]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 [18]. [14].

A set of fundamental applications described in RFC 2573 [19] [15] and
the view-based access control mechanism described in RFC 2575 [20]. [16].

A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [21]. [17].

Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.

This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.

Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name.

The object type together with an object instance serves to uniquely
identify a specific instantiation of the object. For human
convenience, we often use a textual string, termed the descriptor, to
refer to the object type.

4. Overview

Although the number of measurement devices that implement IPPM
metrics is growing, there is not currently any standardized
management interface to manage remotely the measurement of these
metrics. This memo defines a Management Information Base for managing
the measurement of IPPM metrics.

To permit metrics to be referenced by other MIBs and other protocols,
the IPPM WG has defined a registry of the current metrics and a
framework for the integration of future metrics in the [IPPM metrics
registry].

As the specification of new metrics is a continuous process, this
memo defines a framework for the integration of the future
standardized metrics. To address future needs specialized tables may
be created, while augmenting the definition of the ippmMeasureTable.

The MIB architecture is inspired by the RMON model [xxiii],[xxiv]
which specifies the MIB for the monitoring of a single point of
measure. The IPPM-REPORTING-MIB differs from this model in that IPPM
metrics measurement involves several points of measure and requires
common references for time and for measure identification.

The IPPM-REPORTING-MIB introduces a framework where each application
identifies its measures in an owner namespace. Using the namespace
framework, an application The administrator may
grant other owners access to its
measurement results for a measure, or set of measures to another owner via
view based access control. As a result, one owner may compute
aggregated metrics computation, reporting, or
alarming. on another ownerÆs network measures.

Different architectures may be used to perform metric measurements,
using a control protocol and a test protocol. Different control
frameworks are suitable for performing measurements. The memo lists
them, while also looking for a way to integrate them with the IPPM-
REPORTING-MIB. This section is for informational purposes only, and
is intended to help to specify the relationship among the test
protocol, the control protocol and the IPPM-REPORTING-MIB.

Special care has been taken to provide a reporting mode suitable for
control protocols and test protocols. It addresses the need to
provide access to results for the applications. Moreover, it may be
used to reduce the number of control frameworks.

This MIB is intended to handle multiple concurrent sessions by SNMP
applications. However, the SNMP requests are not necessarily to be
handled explicitly by the measurement devices, but can be sent to
middleware performing an aggregation function. This allows for
continuous collection of measurements and statistics computation.

4.1. Textual Conventions

Five

Seven types of data are introduced as a textual convention conventions in this
document: TypeP, IppmOwnerString, TimeUnit,TypeP, TypePaddress,
GMTTimeStamp, IppmStandardMetrics and IppmReportDefinition.

4.1.1.

4.1.1 IppmOwnerString

This octet string is used to represent the owners of the various
measures and reports in the measurement system.

4.1.2 TimeUnit

This textual convention is used to indicate a unit of time, ranging
from nanosecond, microsecond, millisecond, second, hour, day, week,
month, and year.

4.1.3 TypeP and TypePaddress

Section 13 of the IPPM framework [2] introduces the generic notion of
a "packet of type P" because in some contexts the metric's value
depends on the type of the packets involved in the metric. In the
definition of a metric, the type P will be explicitly defined,
partially defined, or left generic. Measurement of metrics defined
with generic type P are made specific when performing actual
measurements. This naming convention serves as an It is important reminder that one must be conscious of the exact type
of traffic being measured.

The standardization of the management of the IPPM measures relies on
the capability to finely and unambiguously configure the type P of
the packets, and the parameters of the protocol suites of the type P.

RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv]
specifies a macro for the definition of protocol identifier. The
RFC2896 [xxvi] defines the protocol identifiers for different
protocol encapsulation trees.

The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER
defined for identifying protocol suites in RMON2. It is achieved by
defining the TypeP and the TypePaddress as new syntax in SMIv2
TEXTUAL-CONVENTION.

4.1.1.1.

4.1.3.1 Internet addresses

The section 14 of the IPPM framework defines (for the usual case of a
unidirectional path through the Internet) the term "Src" and "Dst".
"Src" denotes the IP address of the beginning of the path, and "Dst"
denotes the IP address of the end.

The section 3 of the RMON PI Reference specifies the Protocol
Identifier Encoding rules, which consists briefly in a recursive
length value format. "Src" and "Dst" are protocol identifier
parameters. Their values are encoded in separated fields using the
encoding rules of the protocol identifier, but without trailing
parameters.

The packet encapsulation defined in an instance of TypeP embeds the
format of "Src" and "Dst" and their values. The type and value of
these addresses depend on the type P of the packet, IP version 4,
IPV6, IP in IP... Both participate in the completion of the packet
encoding.

Examples:

RFC2896 defines the protocol identifiers ip and ipip4. Should there
be an Internet tunnel end-point of the IP address 192.168.1.1 in the
tunnel 128.2.6.7. the TypeP of the source address of the tunnel, Src,
is 'ip.ipip4'. The encoding of 'ip.ipip4' using the RFC2895 rules
adds a trailer 2.0.0. It means that an instance of this protocol
identifier has 2 parameters, which values will be set only when
implemented. In the IPPM TypeP context these 2 parameters are
provided in Src (or Dst). In the current example the value of Src is
"192.168.1.1 128.2.6.7".

4.1.2.

4.1.4 GMTTimeStamp

This textual convention defines the time at which an event occurred.
It is very similar to the NTP timestamp format except that it
represents the time elapsed since January 1st, 2000 instead of
January 1st, 1900.

4.1.3.

4.1.5 IppmStandardMetrics

Each standard metric is identified in the IPPM-METRICS-REGISTRY under
the node rfc in a chronological order. This textual convention
defines an octet string to permit several metrics to be performed in
a single measure.

4.1.4.

4.1.6 Report definition

A report consists of sending, or logging, a subset of results of
measurements that have been taken over a period of time. The report
consists of actions that are taken on the measurement results. An
action is performed either:

+ For each result
+ On the results corresponding to a measurement cycle
+ On the results available at the measurement completion.

To preserve the scalability of the whole measurement system, it
limits:

+ The amount of data sent to the applications
+ The bandwidth consumption for uploading the result
+ The number of alarms sent to the applications
+ The amount of data saved in the point of measure

The comparison of the measures results in a metric threshold that
identifies particular measure values and times that directly impact
service availability.

The comparison of the duration of repeated events with a duration
threshold identifies particular measure values and times that
directly affect an SLA.

The combination of IPPM metric results, threshold events, and event
filtering provides a very efficient mechanism to report results,
events, and alarms.

A report is described using the TEXTUAL-CONVENTION
IppmReportDefinition. The report setup must not dramatically increase
the amount of data needed by the control protocol to setup a measure:

+ A basic report is defined in the object ippmReportSetupDefinition;
+ More elaborate reports are described using a metric threshold to
generate alarms and events.
+ Pushing of alarms and reports requires a management station
address to which the data will be sent.
+ SLA alarms are described using an events duration threshold.

The TEXTUAL-CONVENTION IppmReportDefinition specifies the list of
events and actions that are used to create a report.

4.2.

4.2 Structure of the MIB

The MIB is arranged as follow:

- ippmNotifications

- ippmOwnersGroup ippmSystem

- ippmSystemGroup ippmOwners

- ippmMeasureGroup ippmHistory

- ippmHistoryGroup ippmNetMeasure

- ippmNetworkMeasureGroup ippmAggrMeasure

- ippmAggrMeasureGroup ippmReport

- ippmReportGroup
4.2.1. The ippmOwners Group

This group identifies an owner, or group of owners that have access
to measurements on a probe.

4.2.2. ippmNotifications

4.2.1 The ippmSystem Group

This group consists of a set of parameters describing the clock
synchronization at a particular point of measure over time. time, as well
as the system clock where the IPPM-REPORTING-MIB agent resides.

This group is critical to the implementation of the IPPM MIB.

Section 6.3. of the IPPM Framework states that
"Those who develop such measurement methodologies should strive to:
+ Minimize their uncertainties/errors,
+ Understand and document the sources of uncertainty/error, and
+ Quantify the amounts of uncertainty/error."

The aim of this group is to have these values available to compute
reliable statistics. The implementation of this group is mandatory,
whether the time synchronization is automatic or not.

4.2.3.

4.2.2 The ippmMeasureGroup ippmOwners Group

This group displays all the measures configured on the measurement
entity. It consists of the ippmMetricsTable and ippmMeasureTable. The
ippmMeasureTable holds the common part identifies an owner, or group of owners that have access
to measurements on a measure, while probe.

4.2.3 The ippmMeasure Group

This group contains all the
specific parameters IPPM metrics that are handled in registered and
available for use by the corresponding auxiliary table
(ippmNetworkMeasure, ippmAggrMeasureTable...) . agent.

The measurement entity describes in the ippmMetricsTable of the SNMP
agent the local implementation of the standardized metrics. All
standardized metrics should be displayed in this table, with the
capability
ippmMetricCapabilities object defining whether the metric is
implemented or not.

4.2.4 The control protocol registers a description ippmHistory Group

The results of the existing measures
in the ippmMeasureTable and any given measure are stored in the auxiliary measure tables. ippmHistoryTable.
The
ippmMeasureTable table indexing is read-create, but only allows for the
creation of "aggregated" measures when defined in conjunction with
the ippmAggrMeasureTable. Network measures are not allowed to be
created directly by the management entity, and as such the measure that there is an entry in this table values for these measures should be display only.

The results each
result of the measurements are logged in the ippmHistoryTable.

4.2.4. a given measure for a given metric.

4.2.5 The ippmNetworkMeasure ippmNetMeasure Group

The control protocol registers a description of the existing network
measures in the ippmNetworkMeasureTable and in the ippmMeasureTable. ippmNetMeasureTable.

This group displays the network measures defined by the control
protocol. The results are saved in the ippmHistoryTable.

ippmNetworkMeasureTable

ippmNetMeasureTable is an auxiliary table a reflection of ippmMeasureTable,
and is responsible for the configuration of the
network measure.

4.2.5.

4.2.6 The ippmAggrMeasure Group

ippmAggrMeasureTable is an auxiliary table of ippmMeasureTable, and
is responsible for the consolidation consolidation, or
aggregation, of the results previously measured and saved in the
ippmHistoryTable. The aggregated results are saved in the
ippmHistoryTable and may be used for higher aggregated measures.

4.2.6.

4.2.7 The Report Group

This group displays the existing reports of the measures collected.
The ippmReportSetupTable is an auxiliary table of ippmMeasureTable, and
is responsible for the configuration of the
reports.
The reports are saved in the ippmReportTable, or sent directly to the
applications.

4.2.7.

4.2.8 The Notification Group

The Notification group specifies a list of valid notifications. They
are used to push alarms or reports generate alarms,or reports, to the applications.

4.3.

4.3 Row identification in an application namespace

The control protocol protocol, or the test protocol protocol, adds rows in the
namespace of the corresponding measure.

An identifier of an instance of an object is defined as a list of
objects in the clause INDEX. An object instance identifier in an owner namespace is defined as a
list of objects in the clause INDEX where the first object type is
IppmOwnerString.

As the OBJECT IDENTIFIER, which identifies the instance, begins with
the owner value, the remaining values of the index fields may be
chosen independently from one namespace to another.

This allows the user to choose arbitrary values for the remaining
fields of the INDEX clause without checking that the values of these
fields exists in the MIB tables. This allows the owner to use the
same values across MIB implementations.

Thus, it avoids polling to determine the next free index. Also, as a
consequence, two applications will never find the same free index
value.

The usage of owner namespace increases the speed of the management
operations while reducing bandwidth consumption and CPU load in the
agents and applications.

Measurements are requested by management applications. An instance of
an object managed by a management station is identified by the
management station IppmOwnerString and the private index provided by
the MS.

As the MS manages its private range of indices, it simply chooses one
when it wishes to create a new control entry. For the same reason,
the setup of a measure on several points of measures consists of
simply sending the same copy of the measure setup to the different
points of measures involved.

4.4.

4.4 Relationship of IPPM REPORTING MIB tables

There is inherently a relationship between various tables in the IPPM
Mib,
REPORTING MIB, and as such, the data integrity must be assured. This
relationship is depicted in the following examples.

4.4.1.

4.4.1 Relationship between the Owners Table and the Measure Table aggregated
measure table

The owners table contains the list of "owners" that can create and
activate remote IPPM measurements remotely aggregated measures in an agent. As IPPM agent or read the table is
"Read/Create", these users and their associated
"access" rights on metric measurements can be directly configured.
existing network measures.

It is recommended to make use of "view based access control" in order
to restrict access to this table. For example, the master user "acme"
"administrator" may be given "write" privileges on the
ippmOwnersTable, whereas all others are restricted to "read" access.
The user "acme" "administrator" can then setup the list of other users that
have access to measures.

There must be at least 1 owner in the owners owners' table. This owner may
be either setup by default by the IPPM agent, or configured as stated
above.

An owner may have multiple corresponding entries in the network and
aggregated measure
table. tables. Each entry in the measure table must be is
associated with one, and only one, entry in the owners owners' table. That
is to say, that a defined measure may NOT have multiple owners.

Thus, we have a 1:N relationship between the owners owners' table and the a
measure table.

+---------------------+ +---------------------------+
| ippmOwnersTable | | ippmMeasureTable |
+---------------------+ 1:N +---------------------------+
| OwnersOwner: "Acme" |--------------| Measure Owner: "Acme" |
| "Foo" | | Measure Name:"OneWayDelay"|
| . | |...... |
| . | | Measure Owner: "Foo" |
| . | | Measure Name: "PacketLoss"|
| | | Measure Owner: "Foo" |
+---------------------+ +---------------------------+

4.4.2.

4.4.2 Relationship between the Network Measure Table and the Network Measure
Table/Aggregated
Aggregated Measure Table

The network measure table and the aggregated measure is read-only, thus entries in this table can
must be
seen as logical "extensions" to populated by the measure table. agent upon startup.
The measure table agent could potentially read a database that contains information that is common to both types
of measurements. The information found in the Network Measure Table
and the Aggregated Measure Table is specific to each type of measure.

As the network measure table is read-only, entries in this table must
be populated by the agent upon startup.
The agent could potentially read a database that contains network
measures configured by a 3rd party proprietary management system network
measures configured by a 3rd party proprietary management system that
directly interacts with the points of measure. An entry can not be
created in the network measure table without creating the
corresponding entry in the measure table associated to the measure.
This also implies that However, the "owner"
of the measure be defined in the owners table.

The aggregated measure table allows for an "owner" to create
aggregated measures (such as average, minimum, maximum) on existing
measures that are in the measure table. If an "owner" (A) wishes to
measures. An owner may even create an aggregated measure measures on a measure "owned" network
measures that are owned by another
"owner" (B), then "owner" (B) must grant "owner" (A) access to his
measures. This can be done in the resultsharing table.

Even though the Measure Table other owners. However, it is read-create, an "owner" should only
be able to create, or modify entries in the measure table that
correspond recommended
to aggregated measure types. Should an "owner" attempt use view based access control to
update an entry in the measure table that corresponds grant access of network measures
to an entry owners in the network measure table, than access should be denied.

+---------------------------+ +----------------------------------+
| ippmMeasureTable system.

5 Measurement architectures

There are three main measurement architectures.

5.1 Proxy architecture

. +----+ +----+
. |NMS1| |NMS2|
. +----+ +----+
. ^ ^
. | | ippmNetworkMeasureTable
. +----------+ +----------+
. |
+---------------------------+ +----------------------------------+ | Measure Owner: "Acme"
. SNMP or Sibling
. | | MeasureSrc: "Src1"
. v v
. +--------------------------+
. | IPPM-REPORTING-MIB agent | Measure Name:"OneWayDelay
. +--------------------------+
. ^ ^
. | ---| MeasureDst: "Dst1" |
. OWDP-Control
. | ....... |
. +----------+ +----------+
. | ........ |
. v v
.+----------------+ +------------------+
.| Packets-Sender |--OWDP-Test-->| Packets-Receiver | Measure Owner: "Foo" | | MeasureSrc: "Src2"
.+----------------+ +------------------+

In this architecture, the different NMSÆs query the IPPM-REPORTING-
MIB agent for measurements. The agent controls whether the NMS is
granted access to perform the measure requested. Each NMS accesses
the results of its measurements in the IPPM-REPORTING-MIB statistics
table.

The measurement setup/teardown and the data collection are done using
the control protocol and the test protocol.

In this mode the NMS does not depend on the control protocol nor on
the test protocol. The entities involved in the measurement do not
need to implement the IPPM-REPORTING-MIB nor SNMP. This mode allows
for lightweight implementation in the point of measure, and also for
heterogeneous control protocols to coexist.

Finally, the proxy is a checkpoint where measurement activity may be
logged, and where access to measurement setups may be tightly
controlled. Thus, it provides a reliable architecture to manage the
security of a measurement system.

5.2 Reporting architecture

In this architecture the SNMP protocol is only used to read the
results of the measurements in the IPPM-REPORTING-MIB History Table,
and also to inform the NMS that an event has occurred.

. +----+ +----+
. |NMS1| |NMS2|
. +----+ +----+
. ^ ^ ^ ^
. | | Measure Name: "PacketLoss"| | MeasureDst: "Dst2" |
. SNMP| SNMP|
. | | +----------------------------------+ | |
. | | +----------------------------------+ | |
. | ippmAggrMeasureTable OWDP | OWDP
. |Control |Control
. | | +----------------------------------+ | Measure Owner: "Acme" |
. | AMHistoryOwner: "Foo" | +------------------------------+
. | Measure Name: "AvgPLoss" | ---| AMHistoryMetric: "PacketLoss" |
+---------------------------+ +----------------------------------+

As
. +------------------+ +------------------+

The activation of a measure by the aggregated control protocol or the test
protocol creates a measure in the IPPM-REPORTING-MIB Network Measure
table. The table essentially "inherits" from in question may be not accessible by SNMP. In this
case, a list of the measure table, one can not create an entry identifiers (owner, index) is this table without
first creating an entry in handled by
the measurement software.

Each timestamped result of the measure table. Likewise, one can not
delete an entry is logged in the measure IPPM-
REPORTING-MIB History table without first deleting the
corresponding row in order to allow read access to the
NMSÆs and event handling.

On completion, the measurement results are managed according to the aggregated
measure setup:
+ The results may be sent to an NMS;
+ They may be dropped from the IPPM-REPORTING-MIB History table. This logic

In this mode, it is recommended to use an SNMPv2 Inform PDU to send
reporting events because it ensures that there are no "orphaned" table entries in the aggregated measure
table.

5. IPPM-REPORTING-MIB conceptual presentation

5.1. IPPM-REPORTING-MIB diagram

Conceptual view entire block of objects configured the
result is received. There is no control using SNMP Trap PDU.

5.3 Gateway architecture

The gateway architecture combines the IPPM-REPORTING-MIB

+--------------------------------------------------------+ proxy mode and the reporting
mode.

. +-------+ +------+
. | IPPM-REPORTING-MIB entity NMS1 | | NMS2 |
. +-------+ +------+
. ^ ^
. | +---------------------+ +-------------------+ |
. SNMP SNMP
. | |
. | +----------------------------------------+
. | | |
. +-------------+ +------------------+
. | | Measure scheduler | | Result storage |
. +----------------------------------------+ |
. | | | | | |
. | | ^ v v | | ^ ^^^
. | | +------------------------+ | |
. | | | IPPM-REPORTING-MIB | ||| | |
. | +----------|----------+ +-|---|||-----------+ | | Gateway | | ||| |
. | +----------|--------------|---|||-----------+ | +------------------------+ | |
. | owner | ||| | control server | | |
. | Acces | ||| +------------------------+ | |
. | | ^ ^ | Control | |||
. | | | +----------|--------------|---|||-----------+ | | |
. | ||| |
+------------------|--------------|---|||----------------+
| | |||
| | |||
+----------------+ | +----------+-+ ||| +-------------+
| ControlMeasure | | | GetResult | ||| | CreateResult|
|----------------+-+ |------------| ||+--+-------------|
| | | | || | |
| owner | | owner | || | owner |
| privateNdx | | privateNdx | || | privateNdx |
| metrics | | metric | || | metrics | OWDP-Control protocol | scheduler |
. | timestamp | || | timestamp | | addresses | +------------+ ||
. | value | +-----+ +-------+ | status | || +-------------+
+----------------+ ||
||
+---------------------------+|
. | |
+---------+---------+ +------+-----------------+
|GetMeasureResults | |GetMeasureMetricResults |
|-------------------| |------------------------| | |
. v v v v v v
. +-------------+---------+ +--------+-------------+
. | owner IPPM- | Packets | owner |Packets | IPPM | privateNdx
. |REPORTING-MIB| Sender | |Receiver|REPORTING-MIB|
. | privateNdx agent | |-OWDP-Test->| | metric agent |
+-------------------+ +------------------------+
. +-------------+---------+ +--------+-------------+

The managed objects of NMS measurement queries are registered in the IPPM-REPORTING-MIB are
gateway and performed by the measures control and the results.

5.2. Conceptual programming interface

This section describes a conceptual programming interface for test protocol. The NMS
directly consults the
integration result in the corresponding IPPM REPORTING MIB
agent of the IPPM-REPORTING-MIB in a point points of measure.

5.2.1. Measure

5.4 Security

The proxy mode provides flexibility and control

A measure is created/deleted/suspended through the ControlMeasure()
call.

5.2.2. Result log

A result of a measure is created in the IPPM-REPORTING-MIB History
table using a CreateResult() call. Results belonging to a measure are
managed according access to the setup
points of measure, while allowing lightweight control protocol and
test protocol implementations in the points of measure.

5.2.3. Reporting

Results are reported using Different
security rules may be applied to the method GetResult(),
GetMeasureMetricResults() NMS domain and GetMeasureResults() respectively to get
a singleton result, the singleton result measurement
system domains.

The reporting mode has 2 security domains:

+ The control of a metric measure, the measurement setups relies on the control
and
finally to get the singleton result test protocol security mechanisms;
+ The control of a measure.

5.2.4. Logical calls

Objects are managed using 5 main primitives:

controlMeasure();
CreateResult();
GetResult();
GetMeasureMetricResults();
GetMeasureResults().

5.3. SNMP mapping

ControlMeasure() corresponds access to a SNMP set-request on a conceptual
row of ippmMeasureEntry and the results depends on a conceptual row of
ippmNetworkMeasureEntry.

CreateResult() is a internal interface for adding measure results in the ippmHistoryTable.

GetResult() corresponds to an SNMP get-request on a result.

GetMeasureMetricResults() corresponds to a SNMP walk
security mechanisms such as community strings, but may also be
restricted using VACM for customized access.

The gateway mode security relies on the results security of a metric measure subtree.

GetMeasureResults() corresponds to a SNMP walk on the results proxy mode
and of a
measure subtree.

6. Measurement architectures

There are four main measurement architectures.

6.1. Proxy architecture

+----+ +----+
|NMS1| |NMS2|
+----+ +----+
^ ^
| |
+----------+ +----------+
| |
SNMP or Sibling
| |
v v
+--------------------------+
| the reporting mode.

6 Reporting mode integration

The IPPM-REPORTING-MIB agent |
+--------------------------+
^ ^
| |
OWDP-Control
| |
+----------+ +----------+
| |
v v
+----------------+ +------------------+
| Packets-Sender |--OWDP-Test-->| Packets-Receiver |
+----------------+ +------------------+

In this architecture, standardizes the different NMSÆs query parameters that:

+ Define the IPPM-REPORTING-
MIB agent for measurements. The agent controls whether configuration of the NMS is
granted access to perform IPPM metrics measures;
+ Define the measure requested. Each NMS accesses format of the results of its measurements in the IPPM-REPORTING-MIB statistics
table.

The measurement setup/teardown and the data collection are done using measure;
+ Define the control protocol and report of the test protocol.

In this mode IPPM metric measures results.

It introduces the NMS does not depend either on concept of owner namespace to allow for fast
configuration and reporting across multiple points of measurement.

A measure is a distributed object describing a task to be performed
by the control protocol
nor on and the test protocol. The entities involved protocols. A measure is identified by its
owner and its owner index. This identifier is the same in all the measurement do
not need to implement
points of measure. As the IPPM-REPORTING-MIB nor SNMP. This mode
allows owner chooses the index, there is no need
for lightweight implementation in negotiation between the point NMS and the points of measure before
activating the measure.

A measure is primarily defined by its identifier, the metrics to
measure, the description of the end point addresses and
also for heterogeneous control protocols to coexist.

Finally, the proxy
description of the scheduling of the measure.

The description of the measure is a checkpoint where measurement activity distributed to the points of
measure involved. The distribution may not be
logged, synchronized.

6.1 Integration

The integration of the IPPM-REPORTING-MIB, and where access to the test and control
protocols consists in pushing the network measure setup/teardown
parameters and the result values from the measurement setups may be tightly
controlled. Thus, it provides a reliable architecture software to manage the
security
IPPM-REPORTING-MIB agent.

6.2 Setup of the measure network

The measurement system updates the MIB on creation of a network
measure.

6.3 Setup of a measurement system.

6.2. Reporting architecture

In this architecture report
A measurement report setup describes events and data to include in
the SNMP protocol report. A report is only used to read by an NMS in the
results ippmReportTable, or
pushed to a NMS using a SNMP Inform PDU, an email, or a SMS.

Different types of reports may be combined:

+ A trivial report defines the measurements results to be saved in the IPPM-REPORTING-MIB History Table,
and also
ippmReportTable;
+ A basic report defines the host to inform which the NMS that an event has occurred.

+----+ +----+
|NMS1| |NMS2|
+----+ +----+
^ ^ ^ ^
| | | |
SNMP| SNMP|
| | | |
| | | |
| OWDP | OWDP
|Control |Control
| | | |
| | +------------------------------+
| | | | |
| | +--|---------------------------+ |
| | | | | |
| +--|--|------------------------+ | |
| | | | | | |
+--------+---------------------+ | |
| | | | | | | |
| | | | | | | |
v v v v v v v v
+------------------+ +------------------+
|IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB|
| agent | | agent |
+------------------+ +------------------+
| Packets-Sender |--OWDP-Test-->| Packets-Receiver |
+------------------+ +------------------+

The activation results are pushed
on completion of the measure;
+ An alarm report defines a threshold on the results of the
measure. A message is sent to a measure by host when the control protocol result rises above,
or falls below the test
protocol creates threshold;
+ An SLA report defines a measure in threshold on the IPPM-REPORTING-MIB Measure table. results of the
measure. The table in question may be not accessible by SNMP. In this case, a
list report consists of the results of the measure identifiers (owner, index) is handled by (time
and value) of the filtered events. The reports are sent at each
measurement software.

Each timestamped result of cycle, or when the measure is logged on completes.

6.4 Updating the history of the MIB

Results have to be written by the fly measurement task in the
IPPM-REPORTING-MIB History table agent
implementing the IPPM REPORTING MIB.

Adding the results of a measurement consists in order to allow read access to the
NMSÆs and event handling.

On completion, transfer of the
result from the measurement results are managed according software to the
measure setup:
+ SNMP agent. The results protocol
that provides the result may be sent to an NMS the control protocol, or the test
protocol.

6.5 Report download and upload

A report is read in the ippmReportTable using a SNMP Trap PDU SNMP, or pushed by the
IPPM_MIB agent using a SNMP Inform PDU. The NMS may be the sender entity PDU, an email or the control
entity; a SMS.

6.6 Default value

The default values correspond to IP version 4.

7 Definition

IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN

IMPORTS
MODULE-IDENTITY,
NOTIFICATION-TYPE,
OBJECT-TYPE,
experimental ,Integer32
FROM SNMPv2-SMI
--
-- ippm
-- FROM IPPM-REGISTRY

--
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
RowStatus,
StorageType,
TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF;

ippmReportingMib MODULE-IDENTITY
LAST-UPDATED "200306291200Z" -- June, 2003
ORGANIZATION "France Telecom - R&D"
CONTACT-INFO
"Emile Stephan
France Telecom - R&D
2, Avenue Pierre Marzin
Technopole Anticipa
22307 Lannion Cedex
FRANCE
Tel: + They may be dropped from 33 2 96 05 36 10
E-mail: emile.stephan@francetelecom.com

Jessie Jewitt
France Telecom - R&D
801 Gateway Blvd. Suit 500
South San Francisco, CA 94080
Tel : 1 650 875-1524
E-mail : jessie.jewitt@rd.francetelecom.com"

DESCRIPTION
" This memo defines a portion of the IPPM-REPORTING-MIB History table. Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets. In this mode, particular, it is recommended to use an SNMPv2 Inform PDU to send specifies the result because it ensures that objects used for
managing the entire block results of the result is
received. There is no control using SNMP Trap PDU.

6.3. Gateway architecture

The gateway architecture combines the proxy mode IPPM metrics measurements, alarms and the
reporting
mode.

+-------+ +------+
| NMS1 | | NMS2 |
+-------+ +------+
^ ^
| |
SNMP SNMP
| |
| +----------------------------------------+
| | |
+-------------+ +------------------+
| | | | |
+----------------------------------------+ |
| | | | | |
| | v v | |
| | +------------------------+ | |
| | | IPPM-REPORTING-MIB | | |
| | | scheduler | | |
| | +------------------------+ | |
| | | control server | | |
| | +------------------------+ | |
| | ^ ^ | |
| | | | | |
| | OWDP-Control protocol | |
| | | | | |
| | +-----+ +-------+ | |
| | | | | |
v v v v v v
+-------------+---------+ +--------+-------------+
| IPPM- | Packets | |Packets | IPPM |
|REPORTING-MIB| Sender | |Receiver|REPORTING-MIB|
| agent | |-OWDP-Test->| | agent |
+-------------+---------+ +--------+-------------+

The NMS measurement queries are registered in the IPPM-REPORTING-MIB
scheduler and performed by the control and the test protocol. The NMS
directly consults the result in the corresponding points of measure.

6.4. Security

The proxy mode provides flexibility and control of the access to the
points of measure, while allowing lightweight control protocol and
test protocol implementations in the points of measure. Different
security rules may be applied measurement results."

REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION
"General cleanup
Change 5 tables to the NMS domain and read write"

REVISION "200302141200Z" -- 14 February 2003
DESCRIPTION
"Modifications based upon feedback from IETF-55"
REVISION "200306291200Z" -- 29 June 2003
DESCRIPTION
"Adaptation to measurement
system domains.

The reporting mode has 2 security domains:
+The control of the measurement setups relies on the control and
the test protocol security mechanisms.
+ The control VACM, preparation of access to the results depends on final version"

::= { experimental 10001 }

ippm OBJECT IDENTIFIER ::= { experimental 10000 }

--
-- TEXTUAL-CONVENTION
--

IppmOwnerString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An OwnerString, which length is limited to 32."
SYNTAX OCTET STRING (SIZE (0..32))

TimeUnit ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A enumerated list of time units."
SYNTAX INTEGER {
year(1),
month(2),
week(3),
day(4),
hour(5),
second(6),
millisecond(7),
microsecond(8),
nanosecond(9)
}
--
--

IppmStandardMetrics ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Each standard metric is identified in the SNMP
security mechanisms.

The gateway mode security relies on IPPM-METRICS-
REGISTRY under the security of node rfc in chronological order. In order to
allow for
several metrics to be calculated in a single measure, there is an
need
to describe in a bit string the proxy mode
and metrics to be measured.
This textual convention defines an octet string that gathers in a
bit string a sequence of the reporting mode.

7. Reporting mode integration bits. The IPPM-REPORTING-MIB standardizes the parameters that:

+ Define bit order corresponds to the configuration
order
of the IPPM metrics measures;
+ Define metric identifiers in the format registry.
The first bit of the results of string has the measure;
+ Define index 0. The index 1
corresponds to the report first metric of the IPPM metric measures results.

It introduces registry
(instantaneousUnidirectionalConnectivity ).

Example:
One-way-Delay(6) is identified as the concept leaf number 6 of owner namespace to allow for fast
configuration and reporting across multiple points the node
rfc of measurement.

A measure the
registry. One-way-Packet-Loss(12) is a distributed object describing a task to be performed
by identified as the control and leaf
number 12 of the test protocols. node
rfc of the registry. A network measure is identified by its
owner performing both One-way-
Delay(6) and its owner index. This identifier is the same One-
way-Packet-Loss(12) will be described as '0001000001000000'b,
'1040'B.
"
SYNTAX OCTET STRING

GMTTimeStamp ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value at which a specific occurrence happened. The specific
occurrence must be defined in all the
points description of any object
defined using this type.

field octets contents range
----- ------ -------- -----
1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1
2 5-8 fractional part of measure. As the owner chooses second* 0..2^32 - 1
* the index, there value is no need
for negotiation between in network-byte order

The timestamp format is directly inspired from the NMS and NTP timestamp
format.
It differs because it counts the points second since 1 Jan 2000 0H00
instead of 1 Jan 1900 0H00. The most significant bit of measure before
activating the measure.

A measure is primarily defined by its identifier, part
that represents the metrics second is reserved. It will wrap in year 2068
(The NTP timestamp will wrap in year 2036).

This bit is set to
measure, indicate if the description fractional part of the end point addresses second
contains a precision field and a synchronization field as
initially proposed in the
description of the scheduling of OWAMP draft.

When this bit is not set the measure. resolution is maximal.

The description maximal resolution is close to 250 picoseconds.

The precision of the measure timestamp must be provided in another field.
"
SYNTAX OCTET STRING (SIZE (8))

TypeP ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is distributed a display string used to describe the points
protocol encapsulation list of
measure involved. The distribution may not be synchronized.

7.1. Integration

The control protocol, test protocol a packet, and is used as the IPPM-REPORTING-MIB share
the same semantic.

The integration value
of the IPPM-REPORTING-MIB, and SYNTAX clause for the test type of the Src and control
protocols, relies on Dst of an IPPM
measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER
for the use definition of protocol identifiers, while its companion
document, the conceptual programming interface
described in section 6. RFC2896 defines a set of protocol identifiers.

TypeP is defined as a display string. It consists in pushing the measure
setup/teardown parameters and of a list of
dot separated protocol names. Each protocol name has been
previously defined using the result values from macro PROTOCOL-IDENTIFIER of the measurement
software to RFC
2895.

Examples:
The RFC2896 defines the IPPM-REPORTING-MIB agent.

7.2. Setup protocol identifiers 'ether2', 'ip',
'ipip4', 'udp', 'tcp', 'telnet'...

The TypeP of the measure source address corresponding to telnet is the
string 'ip.tcp.telnet'.

The creation TypeP of the measure consists only source address corresponding to UDP packets sent
in transferring an IP tunnel is the string 'ip.ipip4.udp'.

Note:
An IPPM measure
description from is active, so generally a TypeP value does not
describe the measurement software link layer (i.e. ether2...). Valid Internet packets
are sent from Src to Dst. Then the MIB. The management choice of the measure is done using link layer
relies on the ControlMeasure().

The protocol, which provides Internet stack."
SYNTAX OCTET STRING (SIZE (0..512))

TypePaddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"This textual convention is a Display string used to describe the
parameters of the measure to manage,
may be the control protocol encapsulation list of the test protocol.

Different frameworks may be used to setup a measure.

7.2.1. Synchronous setup

The control protocol sets up the measure both in the sender and packet,
basically the
receiver before the measurement.

7.2.2. Asynchronous setup

The control protocol sets up the measure only address.

TypePaddress is defined as a display string. It consists in the sender. In this
case, the receiver has a service already activated (or pending )for
the typeP
list of space separated parameter list. Each parameter in the measurement.

As the first test packet includes the description
list corresponds to a parameter of the measure, it
may differ from regular test packets. If the first test packet is not
consistent with the regular test packets, it must not be used for
performing metrics measurement.

7.3. Setup a PROTOCOL-IDENTIFIER of the measurement report
TypeP.
Example:
The report description TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value
is an extension to the '192.168.1.1 128.2.6.7'."
SYNTAX OCTET STRING (SIZE (0..512))

IppmReportDefinition ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" A report definition is a list of statements describing a
measure. It describes the event and the data to include in the report. A report
statement is read by an NMS part of this process if its bit in the ippmReportTable, or pushed definition is set
to '1'. For all bit values that are set to one, a NMS using a SNMP Trap PDU, a SNMP Inform PDU, an email, or a
SMS.

The control protocol, or the test protocol, includes the description
of the report in the setup of the measure.

Different types of reports may will be combined:

+ A trivial
generated.

The report defines the process uses results to be saved in the
ippmReportTable;
+ A basic report defines the host to which the results history table. Threshold
values are pushed
on completion of provided by the measure;
+ An alarm report defines setup.

Given that not all results from a threshold on metric measurement are
pertinent to a particular report, and that the results size of the
measure. A message is sent to report
must be limited whenever possible, the guidelines for the definition
of a host when report are as follows:

+ Select the result raises or
fall events for consideration (1);
+ Configure filters to select pertinent values (2);
+ Describe the threshold; way the report is delivered (3);
+ An SLA Describe clean up actions to perform on report defines completion (4);

-1- events

Events determine when a threshold on the results report is processed. Events are
exclusive. The possible values are:

onSingleton:
The report is processed each time a new result of the
measure. measurement
occurs.

onMeasureCycle:
The events are filtered using report is processed each time a staircase method. cycle of measure is
completed.

onMeasureCompletion:
The report consists in is processed at the results end of the measure (time measurement.

-2- filters
Filters determine if a result belongs to a report.
ReportInBandResults and value) ReportOutBandResults are exclusive. The
usage of ReportInBandResults and ReportOutBandResults exclude the filtered events. The reports
usage of ReportAboveResults and ReportBelowResults.
Possible values are:

reportUpAndDownResults:
Report contiguous results that are sent at each measure cycle
or when the measure completes.

7.4. Writing on opposite sides of
the up and down metric threshold.

ReportInBandResults:

Report results in the IPPM-REPORTING-MIB

Results have to be written by lower than the measurement task in high metric threshold
field of the agent
implementing report setup and greater than the IPPM MIB.

Adding low
metric threshold field of the report setup.

ReportOutBandResults:
Report results of a measurement consists in greater than the transfer high metric threshold
field of the
result from report setup and lower than the measurement software to low metric
threshold field of the agent. The protocol that
provides report setup.

ReportAboveResults:
Report results greater than the result may be high metric threshold
field of the control protocol, or report setup.

ReportBelowResults:
Report results lower than the test
protocol.

Writing a result is done using low metric threshold field
of the CreateResult().

7.5. Report download and upload

A report is read in setup.

reportExceededEventsDuration:
Save the ippmReportTable using SNMP, or pushed by results of the
IPPM_MIB agent using a SNMP Trap PDU, a metric only if the current
filter triggers repeatedly for a series of contiguous
results during more than
ippmReportSetupDurationThreshold seconds.

-3- deliver

Even though report delivery statements are not exclusive, care
should be taken to limit the number of report methods to 2. The
delivery methods are:

inIppmReportTable:
Store the report in the local ippmReportTable.
NOTE WELL: Results are not stored in the report table if
this flag is not set.

inSNMPv2TrapPDU:
Send the report using a SNMPv2-Trap-PDU.

inInformRequestPDU:
Send the report using a SNMP Inform PDU, InformRequest-PDU.

inEmail:
Send the report using an email or email.

inSMS:
Send the report using a SMS.

7.6. Default value

The default values correspond

-4- Cleanup
onReportDeliveryClearReport(12):

Remove all the results corresponding to IP version 4.

8. Definition

IPPM-REPORTING-MIB DEFINITIONS this measure
from the ippmReportTable when the report has been
delivered.

"
SYNTAX BITS {
none(0), -- reserved
onSingleton(1),
onMeasureCycle(2),
onMeasureCompletion(3),
reportUpAndDownResults(4),
reportInBandResults(5),
reportOutBandResults(6),
reportAboveResults(7),
reportBelowResults(8),
reportExceededEventsDuration(9),
inIppmReportTable(10),
inSNMPv2TrapPDU(11),
inInformRequestPDU(12),
inEmail(13),
inSMS(14),
onReportDeliveryClearReport(15)
}

--
-- IPPM Notifications
--
ippmNotifications OBJECT IDENTIFIER ::= BEGIN

IMPORTS
MODULE-IDENTITY,
NOTIFICATION-TYPE,
OBJECT-TYPE,
experimental ,Integer32
FROM SNMPv2-SMI { ippm 0 }

--
-- IPPM Conformance
--
ippmConformance OBJECT IDENTIFIER ::= { ippm 1 }

-- FROM IPPM-REGISTRY
--
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
RowStatus,
StorageType,
TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF;

ippmReportingMib MODULE-IDENTITY
LAST-UPDATED "200203171200Z" IPPM Mib objects definitions
-- March 17, 2002
ORGANIZATION "France Telecom - R&D"
CONTACT-INFO
"Emile Stephan
France Telecom - R&D
2, Avenue Pierre Marzin
Technopole Anticipa
22307 Lannion Cedex
FRANCE
Tel: + 33 2 96 05 36 10
E-mail: emile.stephan@francetelecom.com

Jessie Jewitt
France Telecom - R&D
801 Gateway Blvd. Suit 500
South San Francisco, CA 94080
Tel :

ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 650 875-1524
E-mail : jessie.jewitt@rd.francetelecom.com"

DESCRIPTION
" This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets. In particular, it specifies the objects used for
managing the results of the IPPM metrics measurements, alarms and
reporting the measures results."

REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION
"General cleanup
Change 5 tables to read write"

REVISION "200302141200Z" -- 14 February 2003
DESCRIPTION
"Modifications based upon feedback from IETF-55" }
ippmOwners OBJECT IDENTIFIER ::= { experimental 10001 ippmReportingMib 2 }

ippm
ippmHistory OBJECT IDENTIFIER ::= { experimental 10000 ippmReportingMib 3 }
ippmMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 4 }
ippmReport OBJECT IDENTIFIER ::= { ippmReportingMib 5 }

--
-- TEXTUAL-CONVENTION ippmSystem Group
--

IppmOwnerString ::= TEXTUAL-CONVENTION
--

ippmSystemTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An OwnerString, which length
"The current time of the system running the IPPM REPORTING MIB
SNMP agent.
When the agent is limited to 32."
SYNTAX OCTET STRING (SIZE (0..32))

TimeUnit ::= TEXTUAL-CONVENTION
STATUS running in proxy mode is it the current
DESCRIPTION
"A list time of the
proxy agent.
When the agent is located in the probe, it is the current time units."
of the probe agent. "
::= { ippmSystem 1 }

ippmSystemSynchronizationType OBJECT-TYPE
SYNTAX INTEGER {
year(1),
month(2),
week(3),
day(4),
hour(5),
second(6),
millisecond(7),
microsecond(8),
nanosecond(9)
other(0),
ntp(1),
gps(2),
cdma(3)
}
--
--

IppmStandardMetrics ::= TEXTUAL-CONVENTION
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" Each standard metric is identified in the IPPM-METRICS-
REGISTRY under
"ippmSystemSynchronizationType describes the node rfc in a chronological order. To permit
several metrics mechanism
used to synchronize the system running the IPPM REPORTING MIB
SNMP agent.

Other(0)
The synchronization process must be performed defined
in a single measure there the ippmSystemSynchonizationDescription.

Ntp(1)
The system is an
need
to describe in a bit string synchronized using the metrics to be performed,
granted...
This textual convention defines an octet string that gathered network
time protocol. The NTP synchronization must be described
in
a
bit string a sequence of bits. the ippmSystemSynchonizationDescription.

Gps(2)
The bit order corresponds to system is synchronized using the
order
of GPS clocks.

Cdma(3)
The system is synchronized using the metrics identifiers in CDMA clocks."
::= { ippmSystem 2 }

ippmSystemSynchronizationDesc OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The description of the registry.
The first bit synchronization process of the string has system
running the index 0. The index 1
corresponds to IPPM REPORTING MIB SNMP agent."
::= { ippmSystem 3 }

ippmSystemClockResolution OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
-- UNITS "picoseconds"
STATUS current
DESCRIPTION
"ippmSystemClockResolution provides the first metric precision of the registry
(instantaneousUnidirectionalConnectivity ).

Example:
One-way-Delay(6) clock
used for the measures . The unit is identified as the leaf number 6 of picosecond. For example,
the node
rfc clock on an old Unix host might advance only once every 10
msec, and thus have a resolution of the
registry. One-way-Packet-Loss(12) 10 msec. So its resolution is identified as
100000 picosecond and the leaf
number 12 value of ippmSystemClockResolution is
100000."
::= { ippmSystem 4 }

ippmSystemOperationalStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
up(1),
down(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the node
rfc status of the registry. A network measure performing both One-way-
Delay(6) system running the IPPM
REPORTING MIB SNMP agent. It does not describe end points measurement
status.
unknown(0)
up(1) means service is operational and One-
way-Packet-Loss(12) will be described as '0001000001000000'b,
'1040'B. available for general use.
down(2) means the proxy is not available for use.
"
SYNTAX OCTET STRING

GMTTimeStamp
::= TEXTUAL-CONVENTION { ippmSystem 5 }

ippmSynchronizationTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of
"This table registers the ippmSystemTime object at which a specific
occurrence happened. The specific occurrence must be defined in event related to the description of any object defined using this type.

field octets contents range
----- ------ -------- -----
1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1
2 5-8 fractional part synchronization of
the second* 0..2^32 - 1
* the value is in network-byte order

The timestamp format is directly inspired from the NTP timestamp
format.
It differs because it counts the second since 1 Jan 2000 0H00
instead of 1 Jan 1900 0H00. The most significant bit points of the part
that represents the second is reserved. It will wrap in year 2068
(The NTP timestamp will wrap in year 2036).

This bit measure. Each event is set to indicate if the fractional part of the second
contains a precision field and a synchronization field as
initially proposed described in the OWAMP draft.

When this bit is not set the resolution an
ippmSynchronizationEntry.
ippmSynchronizationTable is maximal.

The maximal resolution mandatory.
ippmSynchronizationTable content is close to 250 picoseconds.

The precision of the timestamp must be provided in another field.
"
SYNTAX OCTET STRING (SIZE (8))

TypeP read only."
::= TEXTUAL-CONVENTION { ippmSystem 6 }

ippmSynchronizationEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This textual convention is a display string used to describe the
protocol encapsulation list of
"An entry describes a packet, and is used as the value modification of the synchronization status.
"
INDEX { ippmPointOfMeasureIndex, ippmSynchronizationIndex }
::= { ippmSynchronizationTable 1 }

IppmSynchronizationEntry ::=
SEQUENCE {
ippmSynchronizationIndex Integer32,
ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum Integer32,
ippmSynchronizationResolution Integer32
}

ippmSynchronizationIndexOBJECT-TYPE
SYNTAX clause for the type of the Src and Dst of an IPPM
measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER
for Integer32 (1 .. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that identifies the definition of protocol identifiers while its companion
document, synchronization events in
chronological order."
::= { ippmSynchronizationEntry 1 }

ippmSynchronizationTime OBJECT-TYPE
SYNTAX GMTTimeStamp

MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the RFC2896 defines a set synchronization event occurs."
::= { ippmSynchronizationEntry 2 }

ippmSynchronizationStratum OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The stratum level of protocol identifiers.

TypeP the clock computed when the synchronization
event occurs."
::= { ippmSynchronizationEntry 3 }

ippmSynchronizationResolution OBJECT-TYPE
SYNTAX Integer32
UNITS "NanoSeconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The new time resolution computed after the synchronization event
occurred."
::= { ippmSynchronizationEntry 4 }

ippmPointOfMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" This table is defined as a display string. It consists in a the list of
dot separated protocol names. Each protocol name has been
previously defined using measurement end points available in
the macro PROTOCOL-IDENTIFIER measurement system.

Proxy mode:
It is the list of the RFC
2895.

Examples:
The RFC2896 defines measurement end points of the protocol identifiers 'ether2', 'ip',
'ipip4', 'udp', 'tcp', 'telnet'...

The TypeP set of probes
for which the source address corresponding to telnet IPPM proxy provides an SNMP interface.

IPPM MIB implemented in a probe:
It is the
string 'ip.tcp.telnet'.

The TypeP list of the source address corresponding to UDP packets sent
in an IP tunnel measurement end points of the probe.

The ippmPointOfMeasureTable content is read only. This implies
that the string 'ip.ipip4.udp'.

Notes:
An IPPM measure measurement software handles the table internally

ippmPointOfMeasureTable is active, so generally a TypeP value does not
describe the link layer (i.e. ether2...). Valid Internet packets
are sent from Src to Dst. Then the choice of the link layer
relies on the Internet stack."
SYNTAX OCTET STRING (SIZE (0..255))

TypePaddress mandatory."
::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a" { ippmSystem 7 }

ippmPointOfMeasureEntry OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This textual convention is a Display string used to describe the
parameters of
" An entry may be the protocol encapsulation list management address of a packet,
basically the address.

TypePaddress is defined as a display string. It consists middleware in a
list
charge of space separated parameter list. Each parameter in the
list corresponds a parameter management of a PROTOCOL-IDENTIFIER set of probes. It may the
TypeP.
Example:
The TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value
is '192.168.1.1 128.2.6.7'."
SYNTAX OCTET STRING (SIZE (0..255))

IppmReportDefinition ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IppmReportDefinition is intended to be used for describing the
report resulting from
management address of a measurement. By default, all probe that contains several line cards.

An entry describes the results capability of a
measure belong to the report point of this measure. The first step of the report definition sets up triggers on
description may make the value use of the measure, and on the distribution over time wildcards to define multiple
capabilities."
INDEX { ippmPointOfMeasureIndex }
::= { ippmPointOfMeasureTable 1 }

IppmPointOfMeasureEntry ::= SEQUENCE {
ippmPointOfMeasureIndex Integer32,
ippmPointOfMeasureMgmtAddrType InetAddressType,
ippmPointOfMeasureMgmtAddress InetAddress,
ippmPointOfMeasureTypePAddress TypeP,
ippmPointOfMeasureAddress InetAddress,
ippmPointOfMeasureMetrics IppmStandardMetrics
}

ippmPointOfMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1 .. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A local index that identifies an entry of the events
generated by these triggers.

The resulting points of measures corresponding to an event are reported
periodically, or sent in alarms as soon as the event occurs.

The end of the description describes housekeeping tasks.

An action is performed if the corresponding bit is set to 1.

onSingleton(1):
The actions are performed each time a new result of
table."
::= { ippmPointOfMeasureEntry 1 }

ippmPointOfMeasureMgmtAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type associated with the measure
occurs.

onMeasureCycle(2):
The actions are performed management address."
::= { ippmPointOfMeasureEntry 2 }

ippmPointOfMeasureMgmtAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The management address on the results point of measure"
::= { ippmPointOfMeasureEntry 3 }

ippmPointOfMeasureTypePAddress OBJECT-TYPE
SYNTAX TypeP
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the measure at the end of
each cycle type P address of measure.

onMeasureCompletion(3):
The actions are performed on the results point of measure."
DEFVAL { "ip" }
::= { ippmPointOfMeasureEntry 4 }

ippmPointOfMeasureAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the measure at the end address of the point of measure.

reportOnlyUptoDownMetricResults(4):
Report

It is represented as an octet string with specific semantics and
length as identified by the contiguous results that are on opposite sides ippmPointOfMeasureTypePAddress.

For example, if the ippmPointOfMeasureTypePAddress indicates an
encapsulation of 'ip', this object length is 4, followed by the
metric threshold.

reportOnlyExceededEventsDuration(5):
Report 4
octets of the IP address, in network byte order."
::= { ippmPointOfMeasureEntry 5}

ippmPointOfMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics
MAX-ACCESS read-only
STATUS current result of a series
DESCRIPTION
"Metrics supported by this point of contiguous results that
exceed measure."
::= { ippmPointOfMeasureEntry 6 }

ippmMetricTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is mandatory. It describes the current
implementation. Each IPPM standardized metric threshold when the duration of must be described
in the series table.
ippmMetricTable content is over
the events duration threshold seconds.

inIppmReportTable(6):
Store the report in the local ippmReportTable.

inSNMPTrapPDU(7):
Send the report using a SNMP-Trap-PDU.

inSNMPv2TrapPDU(8):
Send the report using a SNMPv2-Trap-PDU.

inInformRequestPDU(9):
Send the report using a SNMP InformRequest-PDU.

inEmail(10):
Send the report using an email.

inSMS(11):
Send the report using a SMS.

onReportDeliveryClearHistory(12):
Remove all the results corresponding to this measure from the
ippmHistoryTable when the report has been delivered.

onReportDeliveryClearReport(13):
Remove all the results corresponding to this measure from the
ippmReportTable when the report has been delivered.
"
SYNTAX BITS {
none(0), -- reserved
onSingleton(1),
onMeasureCycle(2),
onMeasureCompletion(3),
reportOnlyUptoDownMetricResults(4),
reportOnlyExceededEventsDuration(5),
inIppmReportTable(6),
inSNMPTrapPDU(7),
inSNMPv2TrapPDU(8),
inInformRequestPDU(9),
inEmail(10),
inSMS(11),
onReportDeliveryClearHistory (12),
onReportDeliveryClearReport (13)
}

--
-- IPPM Notifications
--
ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 }

--
-- IPPM Conformance
--
ippmConformance OBJECT IDENTIFIER read only."
::= { ippm 1 }

--
-- IPPM Mib objects definitions
-- ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 }
ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 }
ippmMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 3 }
ippmHistory OBJECT IDENTIFIER ::= { ippmReportingMib 4 }
ippmNetworkMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 5 }
ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 6 }
ippmReport OBJECT IDENTIFIER ::= { ippmReportingMib 7 8 }

--
-- ippmSystem Group
--
--

ippmSystemTime

ippmMetricEntry OBJECT-TYPE
SYNTAX GMTTimeStamp IppmMetricEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"The current time of
"An entry describes the measurement system." static capabilities of a metric
implementation."
INDEX { ippmMetricIndex }
::= { ippmSystem ippmMetricTable 1 }

ippmSystemSynchronizationType OBJECT-TYPE
SYNTAX INTEGER

IppmMetricEntry ::=
SEQUENCE {
other(0),
ntp(1),
gps(2),
cdma(3)
ippmMetricIndex Integer32,
ippmMetricCapabilities INTEGER,
ippmMetricType INTEGER,
ippmMetricUnit INTEGER,
ippmMetricDescription SnmpAdminString
}

ippmMetricIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"ippmSystemSynchronizationType describes the mechanism
used to synchronize the system.

Other(0)
The synchronization process must be defined
in
"ippmMetricIndex defines an unambiguous index for each
standardized metric. It identifies a metric. Its value is the ippmSystemSynchonizationDescription.

Ntp(1)
The system
value of the node of the metric in an IPPM registry. This value
is synchronized using the network
time protocol. The NTP synchronization must be described same in any implementation of the ippmSystemSynchonizationDescription.

Gps (2)
The system is synchronized using IPPM REPORTING MIB.

Example:
In the GPS clocks.

Cdma(3)
The system IPPM-METRICS-REGISTRY, onewayPacketLossAverage is synchronized using
registered as the CDMA clocks."
::= { ippmSystem 2 }

ippmSystemSynchronizationDesc OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The description node 14 of ippmMetricsRegistry.metrics.rfc.
Consequently the synchronization process." index of the metric onewayPacketLossAverage in
the IppmMetricTable will always be '14'"
::= { ippmSystem 3 ippmMetricEntry 1 }

ippmSystemClockResolution

ippmMetricCapabilities OBJECT-TYPE
SYNTAX Integer32 INTEGER {
notImplemented(0),
implemented(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemClockResolution provides the precision
"A value of notImplemented implies the clock
used for metric is not implemented.
A value of implemented implies the measures. The unit metric is implemented either
in the picosecond. For example, proxy or the clock on an old Unix host might advance only once every 10
msec, and thus have a resolution point of only 10 msec. So its
resolution measure itself.
Example: if the aggregated metric is 100000 picosecond and not implemented in the value point
of
ippmSystemClockResolution is 100000." measure it may be implemented in the proxy."
DEFVAL { implemented }
::= { ippmSystem 4 ippmMetricEntry 2 }

ippmSystemCurrentSynchronization

ippmMetricType OBJECT-TYPE
SYNTAX Integer32 INTEGER {
network(0),
aggregated(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index on the last synchronization event in
"Indicates the
ippmSynchronizationTable." metric type, whether it is network or aggregated"
DEFVAL { aggregated }
::= { ippmSystem 5 ippmMetricEntry 3 }

ippmSynchronizationTable

ippmMetricUnit OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry INTEGER {
noUnit(0),
second(1),
millisecond(2),
microsecond(3),
nanosecond(4),
percentage(5),
packet(6),
byte(7),
kilobyte(8),
megabyte(9)
}
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"This table registers
"The unit used in the event related to current entity for the synchronization results of the point
measurement of measure. Each event is described this metric."
::= { ippmMetricEntry 4 }

ippmMetricDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the metric implementation following the exact
name of this metric in the registry. For example:
oneWayDelay: text ."
::= { ippmMetricEntry 5 }

--
-- ippmOwners Group
--
-- The ippmOwners objects are responsible for managing
-- the owners access to the measurements.
--
--
ippmOwnersTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmOwnersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A management entity wishing to create and activate remote Ippm
measurements in an
ippmSynchronizationEntry.
ippmSynchronizationTable is mandatory.
ippmSynchronizationTable agent must previously be registered in the
ippmOwnersTable.
ippmOwnersTable content is read only." read-create. It contains at least the
owner 'monitor'. ææ
::= { ippmSystem 6 ippmOwners 1 }

ippmSynchronizationEntry

ippmOwnersEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry IppmOwnersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a modification
"The description of the synchronization status.
" resources granted to an SNMP application.

For example, an instance of ippmOwnersOwner with an
IppmOwnerString 'acme', which represents the 14th owner created
in ippmOwnersTable would be named ippmOwnersEntryOwner.14.

Notes:

The ippmOwnersIndex value is a local index managed directly by
the agent. The management application must poll to get the next
available index value.
It is not used in anyway in other IPPM tables."
INDEX { ippmSynchronizationIndex ippmOwnersIndex }
::= { ippmSynchronizationTable ippmOwnersTable 1 }

IppmSynchronizationEntry

IppmOwnersEntry ::= SEQUENCE {
ippmSynchronizationIndex
ippmOwnersIndex Integer32,
ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum
ippmOwnersOwner IppmOwnerString,
ippmOwnersGrantedMetrics IppmStandardMetrics,
ippmOwnersQuota Integer32,
ippmSynchronizationResolution Integer32
ippmOwnersIpAddressType InetAddressType,
ippmOwnersIpAddress InetAddress,
ippmOwnersEmail SnmpAdminString,
ippmOwnersSMS SnmpAdminString,
ippmOwnersStatus RowStatus
}

ippmSynchronizationIndex

ippmOwnersIndex OBJECT-TYPE
SYNTAX Integer32 (1 .. (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary index that identifies the synchronization events an entry in
chronological order." the owners
table."
::= { ippmSynchronizationEntry ippmOwnersEntry 1 }

ippmSynchronizationTime

ippmOwnersOwner OBJECT-TYPE
SYNTAX GMTTimeStamp IppmOwnerString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The time when the synchronization event occurs." owner described by this entry."
::= { ippmSynchronizationEntry ippmOwnersEntry 2 }

ippmSynchronizationStratum

ippmOwnersGrantedMetrics OBJECT-TYPE
SYNTAX Integer32 IppmStandardMetrics
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The stratum level of the clock computed when
" Defines the synchronization
event occurs." metrics granted to an owner for which measurements
can be performed."
::= { ippmSynchronizationEntry ippmOwnersEntry 3 }

ippmSynchronizationResolution

ippmOwnersQuota OBJECT-TYPE
SYNTAX Integer32
UNITS "NanoSeconds"
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The new time resolution computed after
" The maximum number of records that this owner may have in the synchronization event
occured." history
table and/or in the report table.ÆÆ
::= { ippmSynchronizationEntry ippmOwnersEntry 4 }

ippmPointOfMeasureTable

ippmOwnersIpAddressType OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry InetAddressType {
ipv4(1) ,
ipv6(2),
dns(16)
}
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" A lookup table that identifies the management software in
charge of the point
"The IP address type of measures.

ippmPointOfMeasureTable content is read only. It means that the
measurement software handles the table internally

ippmPointOfMeasureTable management entity corresponding to
this owner.
InetAddressType is mandatory." restricted to ipv4(1),ipv6(2)and dns(16). "
::= { ippmSystem 7 ippmOwnersEntry 5 }

ippmPointOfMeasureEntry

ippmOwnersIpAddress OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry InetAddress (SIZE (1..128))
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" An entry may be the management
"The IP address of a middleware in
charge of the management of a set of probes. It may the management address of a probe that contains several line cards.

An entry describes the capability of a point of measure. The
description may make the use of wildcards entity corresponding to define multiple
capabilities."
INDEX { ippmPointOfMeasureIndex }
::= { ippmPointOfMeasureTable 1 }

IppmPointOfMeasureEntry this
owner."
::=
SEQUENCE {
ippmPointOfMeasureIndex Integer32,
ippmPointOfMeasureMgmtAddrType InetAddressType,
ippmPointOfMeasureMgmtAddress InetAddress,
ippmPointOfMeasureTypePAddress TypeP,
ippmPointOfMeasureAddress InetAddress ippmOwnersEntry 6 }

ippmPointOfMeasureIndex

ippmOwnersEmail OBJECT-TYPE
SYNTAX Integer32 (1 .. 65535) SnmpAdminString
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The index email address of the entry." management entity corresponding to this
owner."
::= { ippmPointOfMeasureEntry 1 ippmOwnersEntry 7 }
ippmPointOfMeasureMgmtAddrType

ippmOwnersSMS OBJECT-TYPE
SYNTAX InetAddressType SnmpAdminString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The type SMS phone number of address associated with the management address" entity corresponding to
this owner."
::= { ippmPointOfMeasureEntry 2 ippmOwnersEntry 8 }

ippmPointOfMeasureMgmtAddress

ippmOwnersStatus OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128)) RowStatus
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The management address on the point status of measure" this table entry."
::= { ippmPointOfMeasureEntry 3 ippmOwnersEntry 9 }

ippmPointOfMeasureTypePAddress

-- ippmHistory Group
--
--

--
-- ippmHistoryTable
--

ippmHistoryTable OBJECT-TYPE
SYNTAX TypeP SEQUENCE OF IppmHistoryEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"Defines the type P of the address of
"The table containing the point of measure."
DEFVAL { "ip" } measurement results."
::= { ippmPointOfMeasureEntry 4 ippmHistory 1 }

ippmPointOfMeasureAddress

ippmHistoryEntry OBJECT-TYPE
SYNTAX InetAddress IppmHistoryEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"Specifies the address
"An ippmHistoryEntry entry is one of the point results of measure.

It is represented as an octet string with specific semantics and
length as a measure
identified by ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex and ippmHistoryIndex.

In the ippmPointOfMeasureTypePAddress.

For example, if index :

+ ippmHistoryMeasureOwner identifies the ippmPointOfMeasureTypePAddress indicates an
encapsulation owner of 'ip', this object length is 4, followed by the 4
octets of measure;

+ ippmHistoryMeasureIndex identifies the IP address, measure in network byte order."
::= { ippmPointOfMeasureEntry 5}

--
-- ippmOwners Group
--
-- The ippmOwners objects are responsible for managing
-- the owners access to owner
namespace;

+ ippmHistoryMetricIndex identifies the measurements.
--
--
ippmOwnersTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmOwnersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A management entity wishing to create and activate remote Ippm
measurements in an agent must previously be registered in metric measured by the
ippmOwnersTable.
ippmOwnersTable content
measure. The metric is read-create. It contains at least described in the
owner 'monitor'. It is mandatory, except if corresponding entry of
the VACM framework n ippmMetricTable;

+ ippmHistoryIndex is
used." the local index of the result on the
history table."
INDEX { ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex, ippmHistoryIndex }
::= { ippmOwners ippmHistoryTable 1 }

ippmOwnersEntry OBJECT-TYPE
SYNTAX IppmOwnersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The description of the resources granted to an SNMP application.

For example, an instance of ippmOwnersOwner with an
IppmOwnerString 'acme', which represents the 14th owner created
in ippmOwnersTable would be named ippmOwnersEntryOwner.14.

Notes:

The ippmOwnersIndex value is a local index managed directly by
the agent. The management application must poll to get the next
available index value.
It is not used in anyway in the other IPPM tables."
INDEX { ippmOwnersIndex }
::= { ippmOwnersTable 1 }

IppmOwnersEntry

IppmHistoryEntry ::=
SEQUENCE {
ippmOwnersIndex
ippmHistoryMeasureOwner IppmOwnerString,
ippmHistoryMeasureIndex Integer32,
ippmOwnersOwner SnmpAdminString,
ippmOwnersGrantedMetrics IppmStandardMetrics,
ippmOwnersGrantedRules BITS,
ippmOwnersIpAddressType InetAddressType,
ippmOwnersIpAddress InetAddress,
ippmOwnersEmail SnmpAdminString,
ippmOwnersSMS SnmpAdminString,
ippmOwnersStatus RowStatus
ippmHistoryMetricIndex Integer32,
ippmHistoryIndex Integer32,
ippmHistorySequence Integer32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32
}

ippmOwnersIndex

ippmHistoryMeasureOwner OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary index
"The owner of the measure that identifies an entry in produced this table" result."
::= { ippmOwnersEntry ippmHistoryEntry 1 }

ippmOwnersOwner

ippmHistoryMeasureIndex OBJECT-TYPE
SYNTAX SnmpAdminString Integer32 (1.. 65535)
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"The
" The owner described by index of the measure that produced this entry." result."
::= { ippmOwnersEntry ippmHistoryEntry 2 }

ippmOwnersGrantedMetrics

ippmHistoryMetricIndex OBJECT-TYPE
SYNTAX IppmStandardMetrics Integer32 (1.. 65535)
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
" Defines ippmHistoryMetricIndex identifies the metrics granted to an owner." metric measured by the
measure. The metric is described in the corresponding entry of
the ippmMetricTable."
::= { ippmOwnersEntry ippmHistoryEntry 3 }

ippmOwnersGrantedRules

ippmHistoryIndex OBJECT-TYPE
SYNTAX BITS {
all(0),
readonly(1),
permanent(2),
sender(3),
receiver(4),
report(5),
alarm(6)
} Integer32 (1.. 65535)
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"Defines the rules this owner may act on
" A local index that identifies a result in the history table."
::= { ippmHistoryEntry 4 }

ippmHistorySequence OBJECT-TYPE
SYNTAX Integer32 (0.. 65535)
MAX-ACCESS read-only
STATUS current IPPM MIB
instance.
all(0):
The owner
DESCRIPTION
"ippmHistorySequence is granted all the rules.
readonly(1):
The measures (not only sequence index of the metrics) that this owner may access
are setup by measurement
results for a metric.

Network metrics:
It's the manager sequence index of a measurement packet. Typically, it
identifies the point order of measure. The owner can
not add new measures for these metrics. The creation and the
configuration of packet in the measures corresponding to these metrics are
managed stream of packets sends
by the manager of source.

Aggregated metrics:
It is the point sequence index of measure.
permanent(2):
The measures (not only the metrics) that this owner may access
are determined by computed aggregated metric
result."
::= { ippmHistoryEntry 5 }

ippmHistoryTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when the manager measurement occured."
::= { ippmHistoryEntry 6 }

ippmHistoryValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The observed value of the point of measure. The owner
can not add new measurement."
::= { ippmHistoryEntry 7 }

--
-- ippmMeasure Group
--

--
--
-- ippmNetMeasureTable
--
--

ippmNetMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmNetMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A entry is a measurement that performs network measures for these metrics. and
provides results.
It performs several metric measurements per packet exchange. Each
step of a measure produces a singleton result per metric. The creation
time of the measurement and the
first configuration value of the measures corresponding to these
metrics metric are managed by saved in
the manager of ippmHistoryTable."
::= { ippmMeasure 1 }

ippmNetMeasureEntry OBJECT-TYPE
SYNTAX IppmNetMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" Typically the point configuration operation sets both the values of measure.
the new IppmNetMeasureEntry.
The
owner may modify IppmNetMeasureTable is mandatory.

The IppmNetMeasureTable content is read only. It means that the measures parameters of
measurement software handles the entries table internally. The setup of
the
corresponding ippmMeasureEntry whose access network measure is read-write.
Typically this allows the owner to suspend not permitted through the measures, IPPM REPORTING
MIB. OWAP provides a setup protocol to
change the beginning enable and end of the measures.

sender(3):

The owner may only activate measures for those metrics that send
packets from the current point of measure. This flag is only
suitable for network teardown
networks measures. It shall be ignored for derived
metrics.
receiver(4):

The owner may only activate measures for those metrics that
receive packets on the current point of measure. This flag ippmNetMeasureMetrics is
only suitable for network measures. It shall set to a list of metrics to be ignored for
derived metrics. Such control increases the security. The owner
may not generate packets
computed from the probe.

report(5): same raw packet exchange. Each step of
measurement delivers a singleton per chosen metric. Results are
timestamped and saved in the ippmHistoryTable.

The owner may setup ippmNetMeasureTable typical usage consists in providing
network measure indices in order to allow aggregated metrics on the measures
corresponding to these metrics.

alarm(6):
The owner may setup alarms
perform aggregation on the results of the measures
metrics.
e.g.:
if the owner Acme is granted with the metric Instantaneous-
Unidirectional-Connectivity as a Receiver in the current point of
measure, then Acme can not setup a Instantaneous-Unidirectional-
Connectivity to another point of measure."
DEFVAL network measures.ÆÆ

INDEX { ippmNetMeasureOwner, ippmNetMeasureIndex }
::= { ippmNetMeasureTable 1 }

IppmNetMeasureEntry ::= SEQUENCE { ippmOwnersEntry 4
ippmNetMeasureOwner IppmOwnerString,
ippmNetMeasureIndex Integer32,
ippmNetMeasureName SnmpAdminString,
ippmNetMeasureMetrics IppmStandardMetrics,
ippmNetMeasureBeginTime GMTTimeStamp,
ippmNetMeasureCollectionRateUnit TimeUnit,
ippmNetMeasureCollectionRate Integer32,
ippmNetMeasureDurationUnit TimeUnit,
ippmNetMeasureDuration Integer32,
ippmNetMeasureHistorySize Integer32,
ippmNetMeasureFailureMgmtMode INTEGER,
ippmNetMeasureResultsMgmt Integer32,
ippmNetMeasureSrcTypeP TypeP,
ippmNetMeasureSrc TypePaddress,
ippmNetMeasureDstTypeP TypeP,
ippmNetMeasureDst TypePaddress,
ippmNetMeasureTxMode Integer32,
ippmNetMeasureTxPacketRateUnit Integer32,
ippmNetMeasureTxPacketRate INTEGER,
ippmNetMeasureDevtnOrBurstSize Integer32,
ippmNetMeasureMedOrIntBurstSize Integer32,
ippmNetMeasureLossTimeout Integer32,
ippmNetMeasureL3PacketSize Integer32,
ippmNetMeasureDataPattern OCTET STRING,
ippmNetMeasureMap SnmpAdminString,
ippmNetMeasureSingletons INTEGER,
ippmNetMeasureOperState INTEGER
}

ippmOwnersIpAddressType

ippmNetMeasureOwner OBJECT-TYPE
SYNTAX InetAddressType IppmOwnerString
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"The IP address type owner of the management entity corresponding to
this owner." network measurement."
::= { ippmOwnersEntry 5 ippmNetMeasureEntry 1 }

ippmOwnersIpAddress

ippmNetMeasureIndex OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128)) Integer32 (1.. 65535)
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"The IP address owner index of the management entity corresponding to this
owner. The address is human readable and is represented using the
dot format." network measure. "
::= { ippmOwnersEntry 6 ippmNetMeasureEntry 2 }

ippmOwnersEmail

ippmNetMeasureName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"The email address name of the management entity corresponding to this
owner." metric instance. It illustrates the specificity
of the metric and includes the metric and the TypeP.

Example:
IP-TCP-HTTP-One-way-Delay: free text "
::= { ippmOwnersEntry 7 ippmNetMeasureEntry 3 }

ippmOwnersSMS

ippmNetMeasureMetrics OBJECT-TYPE
SYNTAX SnmpAdminString IppmStandardMetrics
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"The SMS phone number of
"Defines the management entity corresponding metrics to compute within this owner."
::= { ippmOwnersEntry 8 }

ippmOwnersStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status measure. ONLY network
metrics of the same type are allowed in this table entry."
::= { ippmOwnersEntry 9 }

--
-- ippmResultSharingTable
--

ippmResultSharingTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmResultSharingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" The ippmResultSharingTable controls field.
A measure may be configured for the access result of an owner different metric
singletons to be archived in the measure results ippmHistoryTable. The
ippmMetricIndex of other owners. An owner may grant another
access to read the created result has the value of its measure.

Entries may exist the bit
index of the corresponding ippmMeasureMetrics as explained above
in ippmResultSharingTable even if the measures
to be shared are not yet defined. Deleting a ippmMetricIndex definition.

Example:
A measure entry asking for One-way-Delay(6) and One-way-Packet-Loss(12)
generated a flow of singletons which are logged in the
ippmMeasureTable does not delete
ippmHistoryTable. The singletons created for the entries corresponding to
this One-way-Delay
measure in have a value of ippmMetricIndex of 6 while the ippmResultSharingTable. This table is
optional.

ippmResultSharingTable content is read-create.

If this table is not implemented then created
singletons for the owner has only access
to its own measurement results." One-way-Packet-Loss measure have a value of
ippmMetricIndex of 12.

One measure may perform simultaneously
either several network metrics
either several aggregated metrics

"
-- { one-way-Delay, one-way-Packet-Loss }
DEFVAL { ææ0000001000001ÆÆ }
::= { ippmOwners 2 ippmNetMeasureEntry 4 }

ippmResultSharingEntry

ippmNetMeasureBeginTime OBJECT-TYPE
SYNTAX IppmResultSharingEntry GMTTimeStamp
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"An entry allows an owner to read
"Specifies the results of a measure owned
by another owner.
It permits 2 typical usages:
1) Creating derived measurements on these results
2) Reading the results from a remote management station.

Example: if acme.12 is a One-way-Delay(6) measure, Acme may allow
Peter to make derived metrics on time at which the results of this measure."
INDEX { ippmResultSharingOwner, ippmResultSharingIndex}
::= { ippmResultSharingTable 1 }

IppmResultSharingEntry measurement begins."
::= SEQUENCE {
ippmResultSharingOwner IppmOwnerString,
ippmResultSharingIndex Integer32,
ippmResultSharingMeasureOwner IppmOwnerString,
ippmResultSharingMeasureIndex Integer32,
ippmResultSharingGrantedOwner IppmOwnerString,
ippmResultSharingStatus RowStatus ippmNetMeasureEntry 5 }
ippmResultSharingOwner

ippmNetMeasureCollectionRateUnit OBJECT-TYPE
SYNTAX IppmOwnerString TimeUnit
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
" The owner
"Specifies the unit of this result control entry. Typically the owner who
created this conceptual row." measurement period."
DEFVAL { second }
::= { ippmResultSharingEntry 1 ippmNetMeasureEntry 6 }

ippmResultSharingIndex

ippmNetMeasureCollectionRate OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
" The index
"Gives the period used to collect singletons from the point of this result control entry. The
measures.
This value is managed by used as the owner. On creation a SNMP error 'inconsistentValue' is
returned if this value is already cycle period in use by this owner." the report."
DEFVAL { 60 }
::= { ippmResultSharingEntry 2 ippmNetMeasureEntry 7 }

ippmResultSharingMeasureOwner

ippmNetMeasureDurationUnit OBJECT-TYPE
SYNTAX IppmOwnerString TimeUnit
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"The owner of
"Specifies the measure to be shared. The couple
ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex
identifies absolutely a measure" measurement duration unit."
DEFVAL { second }
::= { ippmResultSharingEntry 3 ippmNetMeasureEntry 8 }

ippmResultSharingMeasureIndex

ippmNetMeasureDuration OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"The index of
"Specifies the measure to be shared." measurement duration."
DEFVAL { 120 }
::= { ippmResultSharingEntry 4 ippmNetMeasureEntry 9 }

ippmResultSharingGrantedOwner

ippmNetMeasureHistorySize OBJECT-TYPE
SYNTAX IppmOwnerString Integer32
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION

"The owner who is granted access to
"Specifies the result maximum number of the measure
described results saved for each metric of
this measure.
Overflow condition will be managed by the couple ippmResultSharingMeasureOwner,
ippmResultSharingMeasureIndex." object
ippmNetMeasureResultsMgmt. "

::= { ippmResultSharingEntry 5 ippmNetMeasureEntry 10 }

ippmResultSharingStatus

ippmNetMeasureFailureMgmtMode OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" The status of this table entry. Once the entry status is set to
active."
::= INTEGER { ippmResultSharingEntry 6
auto(1),
manual(2),
discarded(3)
}

--
--
-- ippmMeasure Group
--
--
--

ippmMetricTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricEntry
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"This table describes the current implementation object defines whether this row and the measure controlled
by this row are kept in volatile storage and lost upon reboot or
if this row is
mandatory. Each IPPM standardized metric must be described backed up
by non-volatile or permanent storage.
'auto'
continue the measurement and erase the older entries in the
table.

In reporting mode,
history.
'manual'
continue the measurement and erase the older entries of this table may be not
accessible. It means that in the
history.
'discarded'
continue the measurement software handles and erase the
table internally.

ippmMetricTable is mandatory.
ippmMetricTable content is read only."
::= { ippmMeasure 1 }

ippmMetricEntry OBJECT-TYPE
SYNTAX IppmMetricEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes older entries in the static capabilities of a metric
implementation."
INDEX { ippmMetricIndex }
::=
history.

Possible values are: other(1), volatile(2), nonVolatile(3),
permanent(4)

Network: "
DEFVAL { ippmMetricTable 1 auto }

IppmMetricEntry
::=
SEQUENCE {
ippmMetricIndex Integer32,
ippmMetricCapabilities INTEGER,
ippmMetricUnit INTEGER,
ippmMetricDescription SnmpAdminString,
ippmMetricMaxHistorySize Integer32 ippmNetMeasureEntry 11 }

ippmMetricIndex

ippmNetMeasureResultsMgmt OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) INTEGER {
wrap(1),
suspend(2),
delete(3)
}
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"ippmMetricIndex defines an unambiguous index for each
standardized metric. Its value is
"
Action to take when the value of log is full. The user may choose
to either wrap, in which case the node of agent writes over existing
records. The user may choose to suspend writing to the
metric log in the IPPM-REPORTING-MIB metrics registry
ippmMib.metrics.rfc.
Each metric registered in
event that he wishes to archive the standard registry must be present data. The resume action
causes the agent to begin to write in this table. thelog, and assumes the
data has been cleared.
This index is used to identify object indicates the metric calculated between way the
IPPM-REPORTING-MIB entities involved measurement results are managed
when the owner quota has been exceeded:
'wrap'
continue the measurement and erase the older entries in the measure.
Example:
The index of
history.
'suspend'
stop the metric onewayPacketLossAverage which is
registered as ippmMib.metrics.rfc.onewayPacketLossAverage will
always have measure and keep the value 14." results in the history.
'delete'
remove the results from the history.
"
::= { ippmMetricEntry 1 ippmNetMeasureEntry 12 }

ippmMetricCapabilities

ippmNetMeasureSrcTypeP OBJECT-TYPE
SYNTAX INTEGER {
notImplemented(0),
implemented(1)
} TypeP
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value
"Defines the type P of notImplemented implies the metric is not implemented.
A value source address of implemented implies the metric is implemented." packets sent by
the measure."
DEFVAL { implemented "ip" }
::= { ippmMetricEntry 2 ippmNetMeasureEntry 13 }

ippmMetricUnit

ippmNetMeasureSrc OBJECT-TYPE
SYNTAX INTEGER {
noUnit(0),
second(1),
ms(2),
us(3),
ns(4),
percentage(5),
packets(6),
byte(7),
kbyte(8),
megabyte(9)
} TypePaddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The unit used in
"Specifies the current entity for address of the results source of the
measurement measure.
It is represented as a list of this metric." parameters corresponding to those
of the PROTOCOL IDENTIFIER sets in ippmNetMeasureSrcTypeP."
::= { ippmMetricEntry 3 }

ippmMetricDescription ippmNetMeasureEntry 14}

ippmNetMeasureDstTypeP OBJECT-TYPE
SYNTAX SnmpAdminString TypeP
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description
"Defines the type P of the metric implementation." destination address of the packets
sent by the measure."
DEFVAL { "ip" }
::= { ippmMetricEntry 4 ippmNetMeasureEntry 15 }

ippmMetricMaxHistorySize

ippmNetMeasureDst OBJECT-TYPE
SYNTAX Integer32 TypePaddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum number address of results that the destination of the measure.
It is represented as a metric measure
can save in list of parameters corresponding to those
of the ippmHistoryTable."
DEFVAL { 200 } PROTOCOL IDENTIFIER set in ippmNetMeasureDstTypeP."
::= { ippmMetricEntry 5 ippmNetMeasureEntry 16 }
--
-- ippmMeasureTable
--
--

ippmMeasureTable

ippmNetMeasureTxMode OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMeasureEntry INTEGER {
other(0),
periodic(1),
poisson(2),
multiburst(3)
}
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"The table of all transmit mode used to send the IPPM measures which are running in packets:
'other'
The rule used to send the
device. They may not all be active.

A measure consists of packets is unknown.
'periodic'
Packets are sent periodically at ippmNetMeasureTxPacketRate
rate.
'poisson'
Packets are sent using a subset of metrics to compute. The results
of Poisson law, the measure may be saved in median is the ippmHistoryTable. The
configuration value
of ippmNetMeasureMedOrIntBurstSize, the measure sets the deviation is
ippmNetMeasureDevtnOrBurstSize.
'multiburst'
Packets are sent bursty at ippmNetMeasureTxPacketRate. The
size of the history
requested in ippmMeasureHistorySize.

The maximum number burst is made of MIB objects to be collected in the portion
of ippmHistoryTable associated with this metric depends on the
value of the ippmMetricMaxHistorySize.

The value of each metric ippmMeasureHistorySize must not be over
the value of ippmMetricMaxHistorySize corresponding to this
metric in the ippmMetricTable.

The ippmMeasureTable is mandatory.

ippmMeasureTable content is read-create. The table is handled
internally by the measurement software for network measures.

The setup of network is not permitted through ippmNetMeasureDevtnOrBurstSize
packets.
Between 2 consecutive bursts, transmission stops during the IPPM REPORTING
MIB. OWAP provides a setup protocol time
needed to enable and teardown
networks measures." send ippmNetMeasureInterBurstPacketsNb.

"
::= { ippmMeasure 2 ippmNetMeasureEntry 17 }

ippmMeasureEntry

ippmNetMeasureTxPacketRateUnit OBJECT-TYPE
SYNTAX IppmMeasureEntry TimeUnit
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"The measure entries are created/deleted internally by packet rate unit used to send the
measurement software."
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmMeasureTable 1 }

IppmMeasureEntry packets."
::=
SEQUENCE {
ippmMeasureOwner IppmOwnerString,
ippmMeasureIndex Integer32,
ippmMeasureName SnmpAdminString,
ippmMeasureMetrics IppmStandardMetrics,
ippmMeasureBeginTime GMTTimeStamp,
ippmMeasureClockPeriodUnit TimeUnit,
ippmMeasureClockPeriod Integer32,
ippmMeasureDurationUnit TimeUnit,
ippmMeasureDuration Integer32,
ippmMeasureHistorySize Integer32,
ippmMeasureStorageType StorageType,
ippmMeasureStatus RowStatus ippmNetMeasureEntry 18 }

ippmMeasureOwner

ippmNetMeasureTxPacketRate OBJECT-TYPE
SYNTAX IppmOwnerString Integer32
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"The owner who has configured this entry." rate the packets are sent."
::= { ippmMeasureEntry 1 ippmNetMeasureEntry 19 }

ippmMeasureIndex

ippmNetMeasureDevtnOrBurstSize OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"The owner index of the measure. The value is managed by
"Indicates the
owner." average number of packets per seconds sent using a
poisson law.

ippmNetMeasurePoissonRate can not be used conjointly with
ippmNetMeasureClockPattern."
DEFVAL { 30 }
::= { ippmMeasureEntry 2 ippmNetMeasureEntry 20 }

ippmMeasureName

ippmNetMeasureMedOrIntBurstSize OBJECT-TYPE
SYNTAX SnmpAdminString Integer32
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"The name of the instance of
"According to the metric. It illustrates transmit mode, this value indicates the
specificity average
number of packets per seconds sent using a poisson law, or the metric and includes the metric and the typeP.

example: IP-port-HTTP-connectivity"
number of packets to wait between consecutive bursts."
DEFVAL { 30 }
::= { ippmMeasureEntry 3 ippmNetMeasureEntry 21 }

ippmMeasureMetrics

ippmNetMeasureLossTimeout OBJECT-TYPE
SYNTAX IppmStandardMetrics Integer32
MAX-ACCESS read-create read-only
STATUS current
-- UNITS "Milliseconds"
DESCRIPTION
"Defines
"Specifies the metrics to compute within this measure. A measure
may be configured for delay after which the result of different metric singletons
to be archived in the ippmHistoryTable. The ippmMetricIndex of packet is considered lost by the created result has
sink."
DEFVAL { 10 }
::= { ippmNetMeasureEntry 22 }

ippmNetMeasureL3PacketSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the value size of the bit index of packets counted at the
corresponding ippmMeasureMetrics as explained above IP network
layer in regards to the
ippmMetricIndex TypeP definition.

Example:
A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12)
generated For a flow of singletons which are logged in TypeP 'ip ipip4' the
ippmHistoryTable. The singletons created for L3 size will be the One-way-Delay
measure have a value of ippmMetricIndex size of 6 while the created
singletons for
the One-way-Packet-Loss measure have a value of
ippmMetricIndex of 12."
-- { one-way-Delay, one-way-Packet-Loss } packet at ipip4 level.
"
DEFVAL { '0001000001000000'b 64 }
::= { ippmMeasureEntry 4 ippmNetMeasureEntry 23 }

ippmMeasureBeginTime

ippmNetMeasureDataPattern OBJECT-TYPE
SYNTAX GMTTimeStamp OCTET STRING
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Specifies
"The pattern used to fill the time at which payload of the measure starts." packet."
DEFVAL { 'FF'H }
::= { ippmMeasureEntry 5 ippmNetMeasureEntry 24 }

ippmMeasureClockPeriodUnit

ippmNetMeasureMap OBJECT-TYPE
SYNTAX TimeUnit SnmpAdminString
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Specifies the unit
"A administrative name of a network management map to which the measure period."
belongs."
DEFVAL { second "" }

::= { ippmMeasureEntry 6 ippmNetMeasureEntry 25 }

ippmMeasureClockPeriod

ippmNetMeasureSingletons OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Specifies
"Reports the amount number of time between 2 measurement action
intervals. The action is specific to singletons performed per metric by the semantic
measure since the beginning of the measure.

Network metrics:

The ippmNetworkMeasureClockPattern transforms This parameters is
required for aggregation."
::= { ippmNetMeasureEntry 26 }

ippmNetMeasureOperState OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
running(1),
stopped(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the flow of
periodical instants as a flow of unpredictable instants operational status of
measurement packet emission.

As the source and the sink share the definition of network measure.ÆÆ
::= { ippmNetMeasureEntry 27 }

--
--
-- ippmAggrMeasureTable
--
--

ippmAggrMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmAggrMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" An aggregated measure summarizes the clock results of previous
network or aggregated measures. The results may be saved in the measure, as the sending timestamp is part of the measurement
packet, the sink have the information to verify that the stream
ippmHistoryTable.

Each step of packets generated by the source respects calculation for the clock law.

Aggregated metrics:

They are performed periodically on measure produces a sequence of results of other
measures. The period corresponds to singleton
result per metric."
::= { ippmMeasure 2 }

ippmAggrMeasureEntry OBJECT-TYPE
SYNTAX IppmAggrMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Typically the interval between two
successive computations of configuration operation sets the metric. The value of
ippmHistoryTimestamp result of a aggregated
theIppmAggrMeasureEntry.

ippmAggrMeasureTable is mandatory.

The ippmAggrMeasureMetrics defines the metric computed
corresponds to the value of the ippmHistoryTimestamp compute.
The results of the last
metric measure to summarize are identified by:
+ ippmAggrMeasureHistoryOwner,
+ ippmAggrMeasureHistoryOwnerIndex and
+ ippmAggrMeasureHistoryMetric

The aggregated task starts at ippmMeasureBeginTime and ends after
ippmMeasureDuration. An aggregated result of the sequence used is performed and saved
in to compute the aggregated
metric."
DEFVAL ippmHistoryTable for each ippmMeasureCollectionRate tick.
"
INDEX { 60 ippmAggrMeasureOwner, ippmAggrMeasureIndex }
::= { ippmMeasureEntry 7 ippmAggrMeasureTable 1 }

IppmAggrMeasureEntry ::= SEQUENCE {
ippmAggrMeasureOwner IppmOwnerString,
ippmAggrMeasureIndex Integer32,
ippmAggrMeasureName SnmpAdminString,
ippmAggrMeasureMetrics IppmStandardMetrics,
ippmAggrMeasureBeginTime GMTTimeStamp,
ippmAggrMeasureAggrPeriodUnit TimeUnit,
ippmAggrMeasureAggrPeriod Integer32,
ippmAggrMeasureDurationUnit TimeUnit,
ippmAggrMeasureDuration Integer32,
ippmAggrMeasureHistorySize Integer32,
ippmAggrMeasureStorageType StorageType,
ippmAggrMeasureHistoryOwner IppmOwnerString,
ippmAggrMeasureHistoryOwnerIndex Integer32,
ippmAggrMeasureHistoryMetric Integer32,
ippmAggrMeasureAdminState Integer32,
ippmAggrMeasureFastReport OBJECT IDENTIFIER,
ippmAggrMeasureMap SnmpAdminString,
ippmAggrMeasureResultsMgmt Integer32,
ippmAggrMeasureStatus RowStatus
}

ippmMeasureDurationUnit

ippmAggrMeasureOwner OBJECT-TYPE
SYNTAX TimeUnit IppmOwnerString
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"Specifies the unit of the measure duration."
DEFVAL { second }
"The owner who has configured this entry."
::= { ippmMeasureEntry 8 ippmAggrMeasureEntry 1 }

ippmMeasureDuration

ippmAggrMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"Specifies the duration
"The owner index of the measure."
DEFVAL { 120 } measure. The value is managed by the
owner."
::= { ippmMeasureEntry 9 ippmAggrMeasureEntry 2 }

ippmMeasureHistorySize

ippmAggrMeasureName OBJECT-TYPE
SYNTAX Integer32 SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies
"The name of the maximum number instance of results saved for each metric the metric. It illustrates the
specificity of the metric and includes the metric and the typeP.

example: IP-port-HTTP-connectivity"
::= { ippmAggrMeasureEntry 3 }

ippmAggrMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the metrics to compute within this aggregated measure. The history

ONLY aggregated metrics of each the same type are allowed in this
field.
A measure may be configured for the result of different metric is managed as a circular
table.
singletons to be archived in the ippmHistoryTable. The newest
ippmMetricIndex of the created result overwrites has the oldest one when value of the
history granted to this metric bit
index of the corresponding ippmAggrMeasureMetrics as explained
above in the ippmMetricIndex definition.

Example:
A measure is full. asking for One-way-Delay(6) and One-way-Packet-Loss(12)
generated a flow of singletons which are logged in the
ippmHistoryTable. The management singletons created for the One-way-Delay
measure have a value of ippmMetricIndex of 6 while the results may be optimized if synchronized
with created
singletons for the reports steps One-way-Packet-Loss measure have a value of this measure.
ippmMetricIndex of 12.
"
DEFVAL
::= { 120 ippmAggrMeasureEntry 4 }

ippmAggrMeasureBeginTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the time at which the aggregated measure starts."
::= { ippmMeasureEntry 10 ippmAggrMeasureEntry 5 }

ippmMeasureStorageType

ippmAggrMeasureAggrPeriodUnit OBJECT-TYPE
SYNTAX StorageType TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines whether this row and
"Specifies the unit of the aggregated measure controlled
by this row are kept in volatile storage and lost upon reboot or
if this row is backed up
by non-volatile or permanent storage.
Possible values are: other(1), volatile(2), nonVolatile(3),
permanent(4), readOnly(5)" period."
DEFVAL { nonVolatile second }
::= { ippmMeasureEntry 11 ippmAggrMeasureEntry 6 }

ippmMeasureStatus

ippmAggrMeasureAggrPeriod OBJECT-TYPE
SYNTAX RowStatus Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this table entry. Once
"Specifies the entry status is set to
active, the associate entry cannot be modified."
::= { ippmMeasureEntry 12 }

--
-- ippmHistory Group
--
--

--
-- ippmHistoryTable
--

ippmHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table amount of time between 2 measurement action
intervals. The action is specific to the results semantic of the measures."
::= { ippmHistory 1 }

ippmHistoryEntry OBJECT-TYPE
SYNTAX IppmHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An ippmHistoryEntry entry is one of measure.

Network metrics:

The ippmNetMeasureClockPattern transforms the results flow of periodical
instants as a measure
identified by ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex flow of unpredictable instants of measurement
packet emission.

As the source and ippmHistoryIndex.

In the index :

+ ippmMeasureOwner identifies sink share the owner definition of the measure;

+ ippmMeasureIndex identifies clock of
the measure in measure, as the owner namespace;

+ ippmMetricIndex identifies sending timestamp is part of the measurement
packet, the sink have the information to verify that the stream
of packets generated by the source respects the clock law.

Aggregated metrics:

They are performed periodically on a sequence of results of other
measures. The period corresponds to the interval between two
successive computations of the metric. The value of
ippmHistoryTimestamp result of a aggregated metric measured in
ippmMetricTable;

+ ippmHistoryIndex is computed
corresponds to the local index value of the ippmHistoryTimestamp of the last
metric result on of the
history table."
INDEX sequence used in to compute the aggregated
metric."
DEFVAL { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex,
ippmHistoryIndex 60 }
::= { ippmHistoryTable 1 ippmAggrMeasureEntry 7 }

ippmAggrMeasureDurationUnit OBJECT-TYPE
SYNTAX TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the unit of the measure duration."
DEFVAL { second }

IppmHistoryEntry
::=
SEQUENCE {
ippmHistoryIndex Integer32,
ippmHistorySequence Integer32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32 ippmAggrMeasureEntry 8 }

ippmHistoryIndex

ippmAggrMeasureDuration OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" A local index that only identifies a result in
"Specifies the history
table." duration of the measure."
DEFVAL { 120 }
::= { ippmHistoryEntry 1 ippmAggrMeasureEntry 9 }

ippmHistorySequence

ippmAggrMeasureHistorySize OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"ippmHistorySequence is
"Specifies the sequence index maximum number of the measurement results saved for each metric of
this measure. Overflow condition will be managed by the object
ippmAggrMeasureResultsMgmt. "
::= { ippmAggrMeasureEntry 10 }

ippmAggrMeasureStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines whether this row and the measure of a metric.

Network metrics:
It's controlled
by this row are kept in volatile storage and lost upon reboot or
if this row is backed up
by non-volatile or permanent storage.
Possible values are: other(1), volatile(2), nonVolatile(3),
permanent(4), readOnly(5)."
DEFVAL { nonVolatile }
::= { ippmAggrMeasureEntry 11 }

ippmAggrMeasureResultsMgmt OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object displays the sequence index of a measurement packet. Typically, it
identifies way the order history of the packet in aggregated
measure is managed.
'wrap'
continue the stream of packets sends
by measure and erase the source.

Aggregated metrics:
It is older entries in the sequence index of
history.
'suspend'
stop the measure and keep the aggregated metric results
computed." in the history.
"
DEFVAL { wrap }
::= { ippmHistoryEntry 2 ippmAggrMeasureEntry 12 }
ippmHistoryTimestamp

ippmAggrMeasureHistoryOwner OBJECT-TYPE
SYNTAX GMTTimeStamp IppmOwnerString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The instant owner of the measure to summarize. "
::= { ippmAggrMeasureEntry 13 }

ippmAggrMeasureHistoryOwnerIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner index of the result." measure to summarize. "
::= { ippmHistoryEntry 3 ippmAggrMeasureEntry 14 }

ippmHistoryValue

ippmAggrMeasureHistoryMetric OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The value metric of the measure." measure to summarize. "
::= { ippmHistoryEntry 4 ippmAggrMeasureEntry 15 }

ippmOnHistoryFullAction

ippmAggrMeasureAdminState OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2),
resume(3)
start(0),
stop(1)
}
MAX-ACCESS read-write read-create
STATUS current
DESCRIPTION
"Action to take when
"This object controls the history log activity of the aggregated measure.
'start'
The aggregated measure is full. started.
'stop'
The user may choose
to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action
causes the agent to begin to write in the history log, and
assumes the data has been cleared." aggregated measure is stopped.
"
::= { ippmHistory 2 ippmAggrMeasureEntry 16 }

--
-- ippmNetworkMeasure Group
--

--
--
-- ippmNetworkMeasureTable
--
--

ippmNetworkMeasureTable

ippmAggrMeasureFastReport OBJECT-TYPE
SYNTAX SEQUENCE OF IppmNetworkMeasureEntry OBJECT IDENTIFIER
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"A entry fast report is required in order to verify quickly that a
measure which performs network measures is running well.
The feature 'fast report' is active if IppmAggrMeasureFastReport
is not null and
provides points to a flow notification.
A fast report consists of results.

This table extends sending by email to the ippmMeasureTable.

It performs several metric measurements per packet exchange. Each
step owner of the
measure, a measure produces a singleton result per metric. The
time table of the measure and the value results of all the metric are saved in the
ippmHistoryTable."
::= { ippmNetworkMeasure 1 }

ippmNetworkMeasureEntry OBJECT-TYPE
SYNTAX IppmNetworkMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" Typically metrics computed by
this aggregated measure. The owner email address is read from the configuration operation sets both
ippmOwnersTable.

ippmAggrMeasureFastReport identifies the values of notification which
defines the new ippmMeasureEntry and header of the new IppmNetworkMeasureEntry.

IppmNetworkMeasureTable is mandatory.

IppmNetworkMeasureTable content is read only. It means that the
measurement software handles the table internally. report.

The setup results part of
network is not permitted through the IPPM REPORTING MIB. OWAP
provides a setup protocol to enable and teardown networks
measures.

The ippmMeasureMetrics report is set to a list made of metrics to be computed
from the same raw packet exchange. Each step of measurement
delivers a singleton column of results
per chosen metric. metrics. Results are timestamped
and saved in the ippmHistoryTable.

The ippmNetworkMeasureTable typical usage consists is providing
network measure indexes to permits separated using commas.

To avoid disaster, an aggregated measure to perform
aggregation on the results of network measures.
An obvious usage of the ippmNetworkMeasureTable consists in the
verification using a fast report must
have a cycle of the network measures states."
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmNetworkMeasureTable aggregation greater than or equal to 1 second and
should not sent more than an email every 5 minutes and should not
sent more than 12 emails."
-- DEFVAL { 0.0 }

IppmNetworkMeasureEntry
::=
SEQUENCE {
ippmNetworkMeasureSrcTypeP TypeP,
ippmNetworkMeasureSrc TypePaddress,
ippmNetworkMeasureDstTypeP TypeP,
ippmNetworkMeasureDst TypePaddress,
ippmNetworkMeasureClockPattern OCTET STRING,
ippmNetworkMeasurePoissonRate Integer32,
ippmNetworkMeasureTimeoutDelay Integer32,
ippmNetworkMeasureL3PacketSize Integer32,
ippmNetworkMeasureDataPattern OCTET STRING ippmAggrMeasureEntry 17 }

ippmNetworkMeasureSrcTypeP

ippmAggrMeasureMap OBJECT-TYPE
SYNTAX TypeP SnmpAdminString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Defines the type P of the source address
"This object allows for classification of the packets sent by measure. It is
typically the measure." name of an administrative map.
"
DEFVAL { '04000080001000'H "" } -- ->ip: 4.0.0.8.0.1.0
::= { ippmNetworkMeasureEntry 1 ippmAggrMeasureEntry 18 }

ippmNetworkMeasureSrc

ippmAggrMeasureStatus OBJECT-TYPE
SYNTAX TypePaddress RowStatus
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Specifies the address of the source
"The status of this table entry. Once the measure.
It entry status is represented as a list of parameters corresponding set to those
active, the associate entry cannot be modified.

The creation of an aggregated measure forced the creation of the PROTOCOL IDENTIFIER sets
corresponding entry in ippmNetworkMeasureSrcTypeP." ippmMeasureTable."
::= { ippmNetworkMeasureEntry 2}

ippmNetworkMeasureDstTypeP ippmAggrMeasureEntry 19 }

--
-- ippmReport Group
--

ippmReportPathToResults OBJECT-TYPE
SYNTAX TypeP SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the type P of the destination address of
" It is typically an URL describing the packets
sent by file location where the measure."
results are logged. "
::= { ippmNetworkMeasureEntry 3 ippmReport 1 }

ippmNetworkMeasureDst

--
--
-- ippmReportSetupTable
--
--

ippmReportSetupTable OBJECT-TYPE
SYNTAX TypePaddress SEQUENCE OF IppmReportSetupEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"Specifies the address of the source of the measure.
It
"The ippmReportSetupTable is represented as a list of parameters corresponding to those definition of reports. It
defines the PROTOCOL IDENTIFIER sets results of network or aggregated measures that are to
be reported. A report is saved in ippmNetworkMeasureSrcTypeP." the ippmReportTable, or sent to
an application using a SNMP Trap, a SNMP inform PDU, an email, or
a SMS. The reporting task is not intended to be a batch action
processed at the end of the measure. It is coupled with threshold
detections and event filtering to deliver application level
events and data, while preserving scalability.

"
::= { ippmNetworkMeasureEntry 4 ippmReport 2 }

ippmNetworkMeasureClockPattern

ippmReportSetupEntry OBJECT-TYPE
SYNTAX OCTET STRING IppmReportSetupEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"This cyclic clock shapes
"The report applies to the profile results of a measure as defined in
either the instants of
measurement action provided by ippmMeasureClockPeriod according
to an arbitrary distribution law. The clock resolution is
ippmMeasureClockPeriod. network measure table, or the aggregated measure
table.

The bits of ippmReportSetupDefinition describes the clock pattern set data and the events
to include in the
value 1 determine report. The definition consists of a list of
tasks to perform on the valid instants results of measurement action. the measure.

A
measure report is associated to be processed if and only if a network measure or to an aggregated
measure.

Note 1: To associate a report to an existing measure the current bit value
is 1.
This pseudo-random clock pattern allows manager
suspends the configuration measure by setting either the
NMS of numerous kind of time sampling law such as periodic,
pseudo random ippmNetMeasureStatus
or Poisson.

The source of the measure sends ippmAggrMeasureStatus to 'notInService'. Then one sets the stream of measurement packets
synchronously with
report fields and activates the stream of instants selected measure by setting the clock
pattern sampling.

ippmNetworkMeasureClockPattern can not be used conjointly with
ippmNetworkMeasurePoissonRate."
DEFVAL
corresponding MeasureStatus to 'active'.

Note 2: A report is tied to a measure. The period of the measure"
INDEX { "11111111" ippmReportSetupOwner, ippmReportSetupIndex }
-- 100% periodic
::= { ippmNetworkMeasureEntry 5 ippmReportSetupTable 1 }

ippmNetworkMeasurePoissonRate OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the average number of packets per seconds sent using a
poisson law.

ippmNetworkMeasurePoissonRate can not be used conjointly with
ippmNetworkMeasureClockPattern."
DEFVAL

IppmReportSetupEntry ::=
SEQUENCE { 30
ippmReportSetupOwner IppmOwnerString,
ippmReportSetupIndex Integer32,
ippmReportSetupMeasureOwner IppmOwnerString,
ippmReportSetupMeasureIndex Integer32,
ippmReportSetupMeasureMetric Integer32,
ippmReportSetupDefinition IppmReportDefinition,
ippmReportSetupUpDownThreshold Integer32,
ippmReportSetupLowThreshold Integer32,
ippmReportSetupHighThreshold Integer32,
ippmReportSetupDurationThresUnit TimeUnit,
ippmReportSetupDurationThreshold Integer32,
ippmReportSetupReportSize Integer32,
ippmReportSetupResultsMgmt Integer32,
ippmReportSetupNMS SnmpAdminString,
ippmReportSetupNotification OBJECT IDENTIFIER,
ippmReportSetupMap SnmpAdminString,
ippmReportSetupStatus RowStatus
}

ippmReportSetupOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner who has configured this report entry."
::= { ippmNetworkMeasureEntry 6 ippmReportSetupEntry 1 }

ippmNetworkMeasureTimeoutDelay

ippmReportSetupIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only not-accessible
STATUS current
-- UNITS "Milliseconds"
DESCRIPTION
"Specifies the delay after which
"The owner index of the packet report entry. The value is considered lost managed by the
sink."
DEFVAL { 1 }
owner."
::= { ippmNetworkMeasureEntry 7 ippmReportSetupEntry 2 }

ippmNetworkMeasureL3PacketSize

ippmReportSetupMeasureOwner OBJECT-TYPE
SYNTAX Integer32 IppmOwnerString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Specifies the size
"The owner of the packets sent at the last network layer
in regards measure to the TypeP definition."
DEFVAL { 64 } report."
::= { ippmNetworkMeasureEntry 8 ippmReportSetupEntry 3 }

ippmNetworkMeasureDataPattern

ippmReportSetupMeasureIndex OBJECT-TYPE
SYNTAX OCTET STRING Integer32 (1.. 65535)
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The current field defines index of the round robin pattern used measure to fill
the packet."
DEFVAL { 'FF'H } report."
::= { ippmNetworkMeasureEntry 9 ippmReportSetupEntry 4 }

--
--
-- ippmAggrMeasure Group
--
--
--
--
-- ippmAggrMeasureTable
--
--

ippmAggrMeasureTable

ippmReportSetupMeasureMetric OBJECT-TYPE
SYNTAX SEQUENCE OF IppmAggrMeasureEntry Integer32 (1.. 65535)
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" This table extends the ippmMeasureTable.
An aggregated measure summarizes the results of previous network
or aggregated measures. The results may be saved in the
ippmHistoryTable.

Each step
"The metric of the calculation for the measure produces a singleton
result per metric." to report."
::= { ippmAggrMeasure 1 ippmReportSetupEntry 5 }

ippmAggrMeasureEntry

ippmReportSetupDefinition OBJECT-TYPE
SYNTAX IppmAggrMeasureEntry IppmReportDefinition
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"Typically the configuration operation sets both
"In order to properly define a report, one must provide
information to:
+ Select the values of events to consider for reporting;
+ Configure filters to select pertinent values;
+ Describe the new ippmMeasureEntry and of way the new IppmAggrMeasureEntry.

ippmAggrMeasureTable report is mandatory.

ippmAggrMeasureTable content delivered;
+ Describe clean up actions to perform on report completion;
The format of a report sent to a NMS is read only. It means that the
measure software handles described in a
notification defined in the table internally. ippmNotifications node.

The ippmMeasureMetrics defines event and the metric to compute.
The results of filter selected in the measure report definition
determines the notification to summarize are identified by:
+ ippmAggrMeasureHistoryOwner, refer:
+ ippmAggrMeasureHistoryOwnerIndex Up and Down filter report format is ippmUpAndDownReport;
+ ippmAggrMeasureHistoryMetric

The aggregated task starts at ippmMeasureBeginTime Inband filter report format is ippmInBandReport;
+ Outband filter report format is ippmOutBandReport;
+ Above filter report format is ippmAboveReport;
+ Below filter report format is ippmBelowReport;
+ Any filter and ends after
ippmMeasureDuration. An aggregated result reportExceededEventsDuration report format is performed
ippmEventsDurationExceededReport;
+ Any filter and saved
in the ippmHistoryTable for each ippmMeasureClockPeriod tick. "
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmAggrMeasureTable 1 }

IppmAggrMeasureEntry ::=
SEQUENCE {
ippmAggrMeasureHistoryOwner IppmOwnerString,
ippmAggrMeasureHistoryOwnerIndex Integer32,
ippmAggrMeasureHistoryMetric Integer32
}

ippmAggrMeasureHistoryOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner of event onMeasureCompletion report format is
ippmCompletedMeasureReport;

Example 1:
Consider a report definition, which reports on the measure to summarize. "
::= { ippmAggrMeasureEntry 1 }

ippmAggrMeasureHistoryOwnerIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner index fly, up and
down result events of the measure to summarize. "
::= a metric measure:

ippmReportSetupDefinition { ippmAggrMeasureEntry 2
onSingleton,
reportUpAndDownMetricResults,
inSNMPv2TrapPDU
}

ippmAggrMeasureHistoryMetric OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The metric

The value of the measure to summarize. "
::= { ippmAggrMeasureEntry 3 }

--
-- ippmReport Group
--

--
--
-- ippmReportSetupTable
--
--

ippmReportSetupTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmReportSetupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ippmReportSetupTable threshold is a list of definition of reports. given by
ippmReportSetupUpDownThreshold. It
defines has the results of value '5' in this
example.

Being a network or aggregated measures that are
to be reported. A flow of results { 3.3 3.2 3.2 5.1 5.3 5.6 6.3 5.2 4.0 3.8
...}, the report is saved in process will send 2 traps:
+ The first one carries the ippmReportTable, or sent results 3.2 and 5.1
corresponding to an application using a SNMP Trap, a SNMP inform PDU, an email
or a SMS. The reporting task is not intended down to be a batch action
processed at up event;
+ The second one carries the end results 5.2 and 4.0 of the measure. It is coupled with threshold
detections and event filtering
up to deliver application level
events and data, while preserving scalability.

It extends down event
UpAndDown

Example 2:
Consider the definition report definition, which reports per measure cycle
in a SNMP informRequestPDU, up and down results events of a
metric measure:
:

ippmReportSetupDefinition {
onMeasureCycle,
reportUpAndDownMetricResults,
inInformRequestPDU,
onReportDeliveryClearReport
}
The value of the definition threshold is given by
ippmReportSetupUpDownThreshold. It has the value '5' in this
example.
The cycle of a measure may include the definition of the measure setup is set to 10 results.

Being a report." flow of 10 results { 3.3 3.2 3.2 5.1 5.3 5.6 6.3 5.2 4.0
3.8 ... }, the report process will send one InformRequestPDU that
carries the couples (3.2, 5.1) and (5.2 ,4.0) corresponding to
the first down to up event and to the second up to down event,
respectively.
"
::= { ippmReport 1 } ippmReportSetupEntry 6 }

ippmReportSetupUpDownThreshold OBJECT-TYPE
SYNTAX IppmReportSetupEntry Integer32
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The report applies to the results of the measure which
"An event is
extended by the current report definition.

Typically the creation of a report sets both generated when the values result of the
new measure and those of exceeds the new IppmReportSetupEntry.
value of ippmReportSetupMetricThreshold.
The ippmReportSetupDefinition describes the data and threshold has the events
to include in same unit as the report. metric. The definition consists metric unit is
recorded in a list of
tasks to perform on the results object ippmMetricsUnit of this metric entry in
the measure.

A report is associated to a network measure or to an aggregated
measure.

Note 1 : To associate a report to an existing measure ippmMetricTable.
"
::= { ippmReportSetupEntry 7 }

ippmReportSetupLowThreshold OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An event is generated when the manager
suspends result of the measure while setting of the ippmMeasureStatus to
'notInService'. Then he setups
metric is lower that the report fields and activates value of ippmReportSetupLowThreshold.
The threshold has the measure while setting same unit as the ippmMeasureStatus to 'active'.

Note 2 : A report is tied to a measure. metric. The period metric unit is
recorded in the object ippmMetricsUnit of this metric entry in
the measure ippmMetricTable.
"
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmReportSetupTable 1 }

IppmReportSetupEntry
::=
SEQUENCE {
ippmReportSetupDefinition IppmReportDefinition,
ippmReportSetupMetricThreshold Integer32,
ippmReportSetupDurationThreshold Integer32,
ippmReportSetupNMS SnmpAdminString,
ippmReportSetupNotification OBJECT IDENTIFIER,
ippmReportSetupStatus RowStatus ippmReportSetupEntry 8 }

ippmReportSetupDefinition

ippmReportSetupHighThreshold OBJECT-TYPE
SYNTAX IppmReportDefinition Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The description
"An event is generated when the result of the events and actions that are used in measure of the
definition
metric exceeds the value of ippmReportSetupHighThreshold.

The threshold has the report.
Send same unit as the report using metric. The metric unit is
recorded in the type object ippmMetricsUnit of message selected by this metric entry in
the bits 8
to 12. The report consists ippmMetricTable.
"
::= { ippmReportSetupEntry 9 }

ippmReportSetupDurationThresUnit OBJECT-TYPE
SYNTAX TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The unit of the duration threshold."
::= { ippmReportSetupEntry 10 }

ippmReportSetupDurationThreshold OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An event is generated when contiguous results of the measure which
have been saved in are
over the ippmReportTable. If ippmReportSetupUpDownThreshold, during
ippmReportSetupDurationThreshold seconds.

Performance:
To improve the
onEventSendReport(7) bit is unset, performance of the system, the report is not saved.

The message sent is a notification defined in process may
be synchronized with the
ippmNotifications node. The notification sent depends on the step
of the measure:
+ Singleton events are sent using the notification
ippmSingletonAlarm
+ Exceeded events durations are sent using the notification
ippmEventsDurationExceededAlarm
+ A report of a cycle of measure is sent using the notification
ippmCycleOfMeasureReport
+ A report collection of a complete network measure is sent using
or with the notification
ippmCompletedMeasureReport

Example 1:
The report setup period of aggregation of an alarm to be sent to the owner in a SNMP
Trap each time aggregate measure."

DEFVAL { 15 }
::= { ippmReportSetupEntry 11 }

ippmReportSetupReportSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the two maximum number of results are found on saved for each side of the metric threshold value of 5:

ippmReportSetupMetricThreshold 5
ippmReportSetupDefinition {
onSingleton(1),
reportOnlyUptoDownMetricResults(4),
inSNMPTrapPDU(8)
}

Example 2:
this measure. The setup history of a report to be sent to the owner in a SNMP
informRequestPDU per measure cycle. It reports the two results
found on each side of the metric threshold of 5:

ippmReportSetupMetricThreshold 5
ippmReportSetupDefinition {
onMeasureCycle(2),
reportOnlyUptoDownMetricResults(4),
inInformRequestPDU(10),
onReportDeliveryClearHistory(13)
}

Default report: is managed as a circular
table. The default report provides the control protocol with an implicit
mechanism to forward the newest result of a cycle of measure to the
owner of overwrites the measure while deleting oldest one when the results corresponding
history granted to this cycle of metric measure from the ippmHistoryTable on reception is full.

The management of the response to results may be optimized if synchronized
with the InformRequestPDU :
ippmReportSetupDefinition {
onMeasureCycle(2),
inInformRequestPDU(10),
onReportDeliveryClearHistory(13)
} reports steps of this measure. "
DEFVAL { { onMeasureCycle, inInformRequestPDU,
onReportDeliveryClearHistory} }
::= { ippmReportSetupEntry 1 12 }

ippmReportSetupMetricThreshold

ippmReportSetupResultsMgmt OBJECT-TYPE
SYNTAX Integer32 INTEGER {
wrap(1),
suspend(2),
delete(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An event is generated
"
Action to take when the result of the measure exceeds the
value of ippmReportSetupMetricThreshold. report log is full. The threshold has user may choose
to either wrap, in which case the same unit as the metric. agent writes over existing
records. The metric unit is
recorded in user may choose to suspend writing to the object ippmMetricsUnit of this metric entry log in the ippmMetricTable.
"
::= { ippmReportSetupEntry 2 }

ippmReportSetupDurationThreshold OBJECT-TYPE
SYNTAX Integer32
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An
event is generated when contiguous results of that he wishes to archive the measure are
over data. The resume action
causes the ippmReportSetupMetricThreshold, during
ippmReportSetupDurationThreshold seconds.

Performance:
To improve agent to begin to write in the performance report log, and assumes
the ippmReportSetupDurationThreshold
may have data has been cleared
This object indicates the same value as way the ippmMeasurePeriod.
The default value of ippmReportSetupDurationThreshold measure results are managed
when the owner quota is
ippmMeasurePeriod. That improves over:
'wrap'
continue the performance because measure and erase the
threshold comparison is synchronized with older entries in the ippmMeasurePeriod
aggregation cycle. That improves
history.
'suspend'
stop the performance because it
synchronized measure and keep the report exportation with results in the management of history.
'delete'
remove the
history and report records of a measure."

DEFVAL { 15 } results from the history.
"
::= { ippmReportSetupEntry 3 13 }

ippmReportSetupNMS OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The recipient of the report may be provided in the setup. By
default the recipient of the report is the owner of the measure.
Its addresses are recorded in the ippmOwnersTable.
The type of ippmReportSetupNMS is not InetAddress because the
report may be sent using SMS or fax.
"
::= { ippmReportSetupEntry 4 14 }

ippmReportSetupNotification OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" ippmReportSetupNotification identifies
"Even though the notification used to
send the report. The definition of the notification defines use is defined in the
content and report
definition, the format object ippmReportSetupNotification provides
flexibility to select another notification. "
-- DEFVAL { 0.0 }
::= { ippmReportSetupEntry 15 }

ippmReportSetupMap OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An administrative name of a map to which the report. " report belongs."
DEFVAL { "" }
::= { ippmReportSetupEntry 5 16 }

ippmReportSetupStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this table entry. "
::= { ippmReportSetupEntry 6 17 }

--
-- ippmReportTable
--

ippmReportTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmReportEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ippmReportTable logs the results of the reports. The results
consist of a subset of the results of a measure as described in
the report definition. The activation of an up and down filtering
in the report definition limits the results logged to those
corresponding to major events. Otherwise, the ippmReportTable is
identical to the ippmHistoryTable."

::= { ippmReport 2 3 }

ippmReportEntry OBJECT-TYPE
SYNTAX IppmReportEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A report is a list of results of a measure. This sample is
associated with the ippmReportSetupEntry which has set up the
report. An ippmReportEntry entry is one of the results of a
measure to report.

An ippmReportEntry entry is one of the results of a measure
identified by ippmReportOwner, ippmReportIndex, ippmReportIndex ippmReportMeasureOwner, ippmReportMeasureIndex,
ippmReportMetricIndex and ippmHistoryIndex. ippmReportIndex.

In the index:

+ ippmMeasureOwner ippmReportMeasureOwner identifies the owner of the measure;

+ ippmMeasureIndex ippmReportMeasureIndex identifies the measure in the owner
namespace;

+ ippmMetricIndex ippmReportMetricIndex identifies the metric measured in
ippmMetricTable;

+ ippmReportIndex is the local index of the result on the report
table."

INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex, ippmReportMeasureOwner, ippmReportMeasureIndex,
ippmReportMetricIndex, ippmReportIndex }
::= { ippmReportTable 1 }

IppmReportEntry ::=
SEQUENCE {
ippmReportMeasureOwner IppmOwnerString,
ippmReportMeasureIndex Integer32,
ippmReportMetricIndex Integer32,
ippmReportIndex Integer32,
ippmReportSequence Integer32,
ippmReportTimestamp GMTTimeStamp,
ippmReportValue Integer32
}

ippmReportIndex

ippmReportMeasureOwner OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local index owner of the result of a metric measure" measure that produced this result."
::= { ippmReportEntry 1 }

ippmReportSequence

ippmReportMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
" ippmReportSequence is the sequence The owner index of the measurement
results of the measure of a metric.

Network metrics:

It's that produced this result."
::= { ippmReportEntry 2 }

ippmReportMetricIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" ippmReportMetricIndex identifies the metric measured by the
measure. The metric is described in the corresponding entry of
the ippmMetricTable."
::= { ippmReportEntry 3 }

ippmReportIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local index of the result of a metric measure"
::= { ippmReportEntry 4 }

ippmReportSequence OBJECT-TYPE
SYNTAX Integer32 (0.. 65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION

" ippmReportSequence is the sequence index of the measurement
results of the measure of a metric.

Network metrics:

It's the sequence index of a measurement packet. Typically, it
identifies the order of the packet in the stream of packets sends
by the source.

Aggregated metrics:

It is the sequence index of the aggregated metric results
computed."
::= { ippmReportEntry 2 5 }

ippmReportTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The instant of the measure of the result."
::= { ippmReportEntry 3 6 }

ippmReportValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value."
::= { ippmReportEntry 4 }
ippmOnReportFullAction OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2),
resume(3)
}

MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Action to take when the report log is full. The user may choose
to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action
causes the agent to begin to write in the report log, and assumes
the data has been cleared."

::= { ippmReport 3 7 }

--
-- IPPM Notifications
--

ippmSingletonAlarm

ippmUpAndDownReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmReportTimestamp,
ippmReportValue
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A notification sent because 2 contiguous results are on opposite
sides of the metric threshold value.

The notification contains the instances of the ippmReportValue ippmHistoryValue
object that exceeded the threshold.
The notification contains the instances of the
ippmReportTimestamp
ippmHistoryTimestamp identifying the time the event occurred." occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 1 }

ippmEventsDurationExceededAlarm

ippmInBandReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmReportTimestamp,
ippmReportValue
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A notification sent when because the duration value of contiguous raising
ippmReportSetupMetricThreshold exceeds the
ippmReportSetupDurationThreshold measure is under
the high threshold value and greater than the low threshold
value.
The notification contains the instances of the ippmReportValue ippmHistoryValue
object that exceeded the threshold.
The notification contains the instances of the
ippmReportTimestamp
ippmHistoryTimestamp identifying the time the event occurred." occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 2 }

ippmCycleOfMeasureReport

ippmOutBandReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistoryValue
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A notification sent when a measure cycle completes. because the result of the measure is either
greater than the high threshold or lower than the low threshold.
The notification contains the instances of the ippmReportValue
objects saved in ippmHistoryValue
object that exceeded the ippmReportTable for this measure cycle. threshold.
The
ippmHistoryTimestamp notification contains the instances of the index identifies
ippmHistoryTimestamp identifying the time the
measures where performed." event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 3 }

ippmCompletedMeasureReport

ippmAboveReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistoryValue
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A notification sent when a measure completes.
" The index notification contains the instances of the included ippmReportSetupDefinition ippmHistoryValue
object
identifies the ippmMeasureEntry and the ippmResultSetupEntry that
specified exceeded the report. threshold.

The notification contains the instances of the ippmReportValue
objects saved in the ippmReportTable for this measure cycle. The
ippmHistoryTimestamp of the index identifies identifying the time the
measures where performed." event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 4 }

ippmHistoryLogFull

ippmBelowReport NOTIFICATION-TYPE
OBJECTS {
ippmOnHistoryFullAction
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A
"
The notification sent when the history log is full. It indicates
what action is to be taken. If the action is wrap the agent will
write over existing records in contains the beginning instances of the log file. If ippmHistoryValue
object that exceeded the action is suspend, threshold.
The notification contains the agent halts all recording instances of measures
in the history table. If
ippmHistoryTimestamp identifying the action is resume, time the agent begins
writing measures again in event occurred.
ippmReportPathToResults is a link to the history log" file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 5 }

ippmReportLogFull

ippmEventsDurationExceededReport NOTIFICATION-TYPE
OBJECTS {
ippmOnReportFullAction
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue
}
STATUS current
DESCRIPTION
"A notification sent when the report log is full. It indicates
what action is to be taken. If the action is wrap duration of continuously rising
metric threshold exceeds the agent will
write over existing records in ippmReportSetupDurationThreshold
value.

The notification contains the beginning instances of the log file. If ippmReportValue
object that exceeded the action is suspend, threshold.

The notification contains the agent halts all recording instances of measures
in the report table. If
ippmReportTimestamp identifying the action time the event occurred.
ippmReportPathToResults is resume, a link to the file name, which
contains detailled results corresponding to this event.
"
::= { ippmNotifications 6 }

ippmCompletedMeasureReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A notification sent when a measure completes.
The index of the included ippmReportSetupDefinition object
identifies the ippmMeasureEntry and the ippmResultSetupEntry that
specified the report.

ippmReportPathToResults is a link to the file name, which
contains the results of this measure cycle."
::= { ippmNotifications 7 }

ippmAggrMeasureHistoryFull NOTIFICATION-TYPE
OBJECTS {
ippmAggrMeasureName,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue

}
STATUS current
DESCRIPTION
" A notification sent when the size of the history of a metric of
a aggregated measure exceeds ippmAggrMeasureHistorySize. The
agent begins
writing measures again will then manage the reports according to the policy
described in ippmAggrMeasureResultsMgmt."
::= { ippmNotifications 8 }

ippmNetMeasureHistoryFull NOTIFICATION-TYPE
OBJECTS {
ippmNetMeasureName,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue

}
STATUS current
DESCRIPTION
" A notification sent when the size of the history of a metric of
a network measure exceeded ippmNetMeasureHistorySize. Then the
agent manages the records according to the policy described in
ippmNetMeasureResultsMgmt."
::= { ippmNotifications 9 }

ippmReportLogFull NOTIFICATION-TYPE
OBJECTS {
-- iIppmReportMetricIndex,
ippmReportSetupResultsMgmt,
ippmReportTimestamp,
ippmReportSequence,
ippmReportValue
}
STATUS current
DESCRIPTION
"A notification sent when the size of the report log" of a metric of a
measure exceeded ippmReportSetupReportSize. Then the agent
manages the reports according to the policy described in
ippmReportSetupResultsMgmt."
::= { ippmNotifications 6 10 }

--
-- IPPM MIB Conformance statements
--

ippmCompliances OBJECT IDENTIFIER ::={ ippmConformance 1 }

ippmGroups OBJECT IDENTIFIER ::={ ippmConformance 2 }

ippmProxyInterDomainCompliances MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement the
IPPM MIB as a proxy in interdomain. The implementation of the
VACM control is mandatory."
MODULE -- this module
MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, ippmNetMeasureGroup, ippmHistoryGroup,
ippmAggrMeasureGroup, ippmReportGroup, ippmNotificationGroup
}
::= { ippmCompliances 1 }

ippmProxyCompliances MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement the
IPPM MIB as a proxy."
MODULE -- this module
MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, ippmNetMeasureGroup, ippmHistoryGroup,
ippmAggrMeasureGroup, ippmReportGroup, ippmNotificationGroup
}
GROUP ippmOwnersGroup
DESCRIPTION
"The ippmOwnersGroup is needed if VACM is not implemented."
::= { ippmCompliances 2 }

ippmProbeCompliances MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement the
IPPM MIB in a probe."
MODULE -- this module
MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, ippmNetMeasureGroup, ippmHistoryGroup
}
::= { ippmCompliances 3 }

ippmSystemGroup OBJECT-GROUP
OBJECTS {
ippmSystemSynchronizationDesc,
ippmSystemTime,
ippmSystemSynchronizationType,
ippmSystemClockResolution,
ippmSystemCurrentSynchronization,
ippmSynchronizationTime,
ippmSynchronizationStratum,
ippmSynchronizationResolution,
ippmPointOfMeasureMgmtAddrType,
ippmPointOfMeasureMgmtAddress,
ippmPointOfMeasureTypePAddress,
ippmPointOfMeasureAddress
}
STATUS current
DESCRIPTION
"The IPPM System Group"
::= { ippmGroups 1}

ippmMeasureGroup OBJECT-GROUP
OBJECTS {
ippmPointOfMeasureAddress,
ippmSystemOperationalStatus,
ippmPointOfMeasureMetrics,
ippmMetricCapabilities,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmMetricMaxHistorySize,
ippmMeasureName,
ippmMeasureMetrics,
ippmMeasureBeginTime,
ippmMeasureClockPeriodUnit,
ippmMeasureClockPeriod,
ippmMeasureDurationUnit,
ippmMeasureDuration,
ippmMeasureHistorySize,
ippmMeasureStorageType,
ippmMeasureStatus
ippmMetricDescription
}
STATUS current
DESCRIPTION
"The IPPM Measure System Group"
::= { ippmGroups 2}

ippmNetworkMeasureGroup 1}

ippmNetMeasureGroup OBJECT-GROUP
OBJECTS {
ippmNetworkMeasureSrcTypeP,
ippmNetworkMeasureSrc,
ippmNetworkMeasureDstTypeP,
ippmNetworkMeasureDst,
ippmNetworkMeasureClockPattern,
ippmNetworkMeasurePoissonRate,
ippmNetworkMeasureTimeoutDelay,
ippmNetworkMeasureL3PacketSize,
ippmNetworkMeasureDataPattern
ippmNetMeasureName,
ippmNetMeasureMetrics,
ippmNetMeasureBeginTime,
ippmNetMeasureCollectionRateUnit,
ippmNetMeasureCollectionRate,
ippmNetMeasureDurationUnit,
ippmNetMeasureDuration,
ippmNetMeasureHistorySize,
ippmNetMeasureFailureMgmtMode,
ippmNetMeasureResultsMgmt,
ippmNetMeasureSrcTypeP,
ippmNetMeasureSrc,
ippmNetMeasureDstTypeP,
ippmNetMeasureDst,
ippmNetMeasureTxMode,
ippmNetMeasureTxPacketRateUnit,
ippmNetMeasureTxPacketRate,
ippmNetMeasureDevtnOrBurstSize,
ippmNetMeasureMedOrIntBurstSize,
ippmNetMeasureLossTimeout,
ippmNetMeasureL3PacketSize,
ippmNetMeasureDataPattern,
ippmNetMeasureMap,
ippmNetMeasureSingletons,
ippmNetMeasureOperState
}
STATUS current
DESCRIPTION
"The IPPM Network Measure Group"
::= { ippmGroups 3}

ippmHistoryGroup OBJECT-GROUP
OBJECTS {
ippmHistorySequence,
ippmHistoryTimestamp,
ippmOnHistoryFullAction,
ippmHistoryValue
}
STATUS current
DESCRIPTION
"The IPPM History Group"
::= { ippmGroups 4}

ippmAggrMeasureGroup OBJECT-GROUP
OBJECTS {
ippmAggrMeasureName,
ippmAggrMeasureMetrics,
ippmAggrMeasureBeginTime,
ippmAggrMeasureAggrPeriodUnit,
ippmAggrMeasureAggrPeriod,
ippmAggrMeasureDurationUnit,
ippmAggrMeasureDuration,
ippmAggrMeasureHistorySize,
ippmAggrMeasureStorageType,
ippmAggrMeasureHistoryOwner,
ippmAggrMeasureHistoryOwnerIndex,
ippmAggrMeasureHistoryMetric
ippmAggrMeasureHistoryMetric,
ippmAggrMeasureAdminState,
ippmAggrMeasureFastReport,
ippmAggrMeasureMap,
ippmAggrMeasureResultsMgmt,
ippmAggrMeasureStatus
}
STATUS current
DESCRIPTION
"The IPPM AggregatedMeasure Group"
::= { ippmGroups 5}

ippmReportGroup OBJECT-GROUP
OBJECTS {
ippmReportSetupMeasureOwner,
ippmReportSetupMeasureIndex,
ippmReportSetupMeasureMetric,
ippmReportSetupDefinition,
ippmReportSetupMetricThreshold,
ippmReportSetupUpDownThreshold,
ippmReportSetupLowThreshold,
ippmReportSetupHighThreshold,
ippmReportSetupDurationThresUnit,
ippmReportSetupDurationThreshold,
ippmReportSetupReportSize,
ippmReportSetupResultsMgmt,
ippmReportSetupNMS,
ippmReportSetupNotification,
ippmReportSetupMap,
ippmReportSetupStatus,
ippmReportPathToResults,
ippmReportSequence,
ippmReportTimestamp,
ippmReportValue,
ippmOnReportFullAction
ippmReportValue
}
STATUS current
DESCRIPTION
"The IPPM Report Group"
::= { ippmGroups 6}

ippmOwnersGroup OBJECT-GROUP
OBJECTS {
ippmOwnersOwner,
ippmOwnersGrantedMetrics,
ippmOwnersGrantedRules,
ippmOwnersQuota,
ippmOwnersIpAddressType,
ippmOwnersIpAddress,
ippmOwnersEmail,
ippmOwnersSMS,
ippmOwnersStatus,
ippmOwnersIpAddressType,
ippmResultSharingMeasureOwner,
ippmResultSharingMeasureIndex,
ippmResultSharingGrantedOwner,
ippmResultSharingStatus
ippmOwnersStatus
}
STATUS current
DESCRIPTION
"The IPPM Owners Group"
::= { ippmGroups 7}

ippmNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
ippmSingletonAlarm,
ippmCycleOfMeasureReport,
ippmUpAndDownReport,
ippmInBandReport,
ippmOutBandReport,
ippmAboveReport,
ippmBelowReport,
ippmEventsDurationExceededReport,
ippmCompletedMeasureReport,
ippmEventsDurationExceededAlarm,
ippmHistoryLogFull,
ippmAggrMeasureHistoryFull,
ippmNetMeasureHistoryFull,
ippmReportLogFull
}
STATUS current
DESCRIPTION
"The IPPM Notification Group"
::= { ippmGroups 8}

END

8 Security Considerations

9.1.

8.1 VACM Access control
View Based Access Control, or VACM may be used to restrict access to
certain objects, or even object instances within tables. For example,
one may:

+ Give an 'administrator' write access to the ippmOwnersTable,
whereas all other users may only have read access
+ Give access to individual rows in the network measure, aggregated
measure, history, and report table to particular owners based upon
indexing on an 'owners name', and even upon a particular measure.
This will be illustrated below.
+ Give access of one ownerÆs measure, and associated results, to
another owner in order to create an aggregated measure based upon the
results.

8.1.1 Example of implementing VACM control for the IPPM-REPORTING-MIB

The following example illustrates how one could use VACM to restrict
access to particular objects within the MIB. It uses syntax specific
to a particular agent development toolkit, but may be generalized
using the concepts as defined in the VACM MIB.

In this example, we have two NMS users, namely user1=owner1 and
user2=owner2:
1) First we define the two users and their host addresses:
com2sec owner1 owner1computer@ private
com2sec owner2 owner2computer@ private

2) We then define SNMPv2c groups
group owner1 v2c owner1
group owner2 v2c owner2
view notif included ippmNotifications ff

3.1) For the user owner1, we now define the views for which he will
have read access
# covers PointOfMeasureTable SynchronizationTable and all scalars
view owner1read included ippmSystem ff
# covers OwnersTable
view owner1read included ippmOwners ff
# covers MetricsTable
view owner1read included ippmMeasure ff
# covers NetworkMeasureTable
view owner1read included
ippmNetMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
# covers AggrMeasureTable
view owner1read included
ippmAggrMeasureOwner.6.111.119.110.101.114.49 ff.df.c0

3.2) We will now define the views for which owner1 will have write
access
view owner1write included
ippmAggrMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
# covers ReportSetupTable
view owner1read included
ippmReportSetupOwner.6.111.119.110.101.114.49 ff.df.c0
view owner1write included
ippmReportSetupOwner.6.111.119.110.101.114.49 ff.df.c0
# covers HistoryTable
view owner1read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
# covers ReportTable
view owner1read included
ippmReportOwner.6.111.119.110.101.114.49 ff.df.c0

3.3) For owner2, we will define the views for which he has read
access
view owner2read included ippmSystem ff
view owner2read included ippmOwners ff
view owner2read included ippmMeasure ff
# covers NetworkMeasureTable plus let's say the owner1 network
measure of index X
view owner2read included
ippmNetMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2read included
ippmNetMeasureOwner.6.111.119.110.101.114.49.X ff.df.e0
# covers AggrMeasureTable plus let's say the OWNER1 aggregated
measure of index Y
view owner2read included
ippmAggrMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2read included
ippmAggrMeasureOwner.6.111.119.110.101.114.49.Y ff.df.e0
3.4) For owner2, we will define the views for which he has write
access
view owner2write included
ippmAggrMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
# covers ReportSetupTable
view owner2read included
ippmReportSetupOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2write included
ippmReportSetupOwner.6.111.119.110.101.114.50 ff.df.c0
# covers HistoryTable plus OWNER1 related X network measure results
and OWNER1 related Y aggregated measure results
view owner2read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.49.X ff.df.e0
view owner2read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.49.Y ff.df.e0
# covers ReportTable
view owner2read included
ippmReportOwner.6.111.119.110.101.114.50 ff.df.c0
3.5) Now we give the two users access to the views defined above.
Note that owner1 and owner2 have read access to owner1read and
owner2read views respectively. They have write access to owner1write
and owner2write view respectively. And they both have access to all
the notifications.

access owner1 "" any noauth exact owner1read
owner1write notif
access owner2 "" any noauth exact owner2read
owner2write notif

8.2 Privacy

The privacy concerns of network measurement are intrinsically limited
by the active measurements. Unlike passive measurements, there can be
no release of existing user data.

9.2.

8.3 Measurement aspects

Conducting Internet measurements raises both security and privacy
concerns. This memo does not specify an implementation of the
metrics, so it does not directly affect the security of the Internet
nor of applications that run on the Internet. However,
implementations of these metrics must be mindful of security and
privacy concerns.

There are two types of security concerns: potential harm caused by
the measurements, and potential harm to the measurements. The
measurements could cause harm because they are active, and inject
packets into the network. The measurement parameters MUST be
carefully selected so that the measurements inject trivial amounts of
additional traffic into the networks they measure. If they inject
"too much" traffic, they can skew the results of the measurement, and
in extreme cases cause congestion and denial of service.

The measurements themselves could be harmed by routers giving
measurement traffic a different priority than "normal" traffic, or by
an attacker injecting artificial measurement traffic. If routers can
recognize measurement traffic and treat it separately, the
measurements will not reflect actual user traffic. If an attacker
injects artificial traffic that is accepted as legitimate, the loss
rate will be artificially lowered. Therefore, the measurement
methodologies SHOULD include appropriate techniques to reduce the
probability measurement traffic can be distinguished from "normal"
traffic.

Authentication techniques, such as digital signatures, may be used
where appropriate to guard against injected traffic attacks.

9.3.

8.4 Management aspects

There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-only. Such objects
may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.

SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.

It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [18] and the View-based
Access Control Model RFC 2575 [21] is recommended.

It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.

10. Document management

10.1. Open issues

Describe incompatible bit combinations in IPPMreport and granted
metric

Run SMIlint.

Discussion on the management of the history size.

10.2. changes since release 00

+ Put in a description of the relationship of certain tables,
particularly the measure/network measure/aggregated measure table.

+ The TC GMTTimeStamp is the common type to define timestamp objects.

+ ippmHisoryTable index simplified: ippmHistoryTimestamp replaced
with ippmHistorySqceNdx in the index.

+ The MIB has been compiled using net-snmp.

+ Snmpadminstring replaces Displaystring.

+ IP addresses defined using INETaddresstype.

+ Sharing table is optional to permit the VACM framework to be used.

+ The description of the network measure table emphases that the set
up of network measure is not permitted using SNMP.

+ The TC StandardMetrics then, there is removed and replaced with no
control as to who on the table
ippmMetricsTable.

+ The table pointOfMeasureTable secure network is added to describe multiples
interfaces devices

+ 5 tables have been changed allowed to read/create: ippmOwnersTable,
ippmMeasureTable, ippmAggrMeasureTable, ippmResultSharingTable, and
ippmReportSetupTable.

+ IppmHistoryTable access and ippmReportTable index reviews:

IppmHistorySqceNdx field added in
GET/SET (read/change/create/delete) the ippmHistoryTable.
INDEX modified. IppmHistorySqceNdx replaces IppmHistoryTimemark.

+ IppmSystem group refurbished:
IppmSystemTimer renamed ippmSystemTime.
Current and last synch event concept generalized objects in this MIB.

It is recommended that the
ippmSynchronizationTable.

10.3. Changes since release 01

+ Document Format:
Make use of implementors consider the regular MIB object indentation.

+ Typos correction: ippmMeasureHystorySize and so on.

+ Time unit textual convention:
Enumerations listed in description clauses (e.g. ms, us, ns may
not be universally understood so explicitly named security
features as millisecond,
microsecond, nanosecond)

+ Clarify ClearHistory and ClearReport definition:
OnReportDeliveryClearHistory and OnReportDeliveryClearReport
options

+ Added scalars ippmOnReportFullAction and ippmOnHistoryFullAction:
To take action when the tables are full. A scalar, which is read-
write and indicates provided by the action to be taken when SNMPv3 framework. Specifically, the log is full.
Options are: wrap, suspend, resume. Same was done for report
group.

+ Conformance section:
Added use
of the MODULE-COMPLIANCE macro User-based Security Model RFC 2574 [18] and the corresponding OBJECT-
GROUPS instances.
Added View-based
Access Control Model RFC 2575 [21] is recommended.

It is then a compliance instances for proxy mode, proxy inter-domain
mode and probe mode.

+ PointOfMeasure:
Put in ippmPointOfMeasureMgmtAddrType-> InetAddressType with
ippmPointOfMeasureMgmtAddress-> InetAddress.
Changed point of measure address customer/user responsibility to be INET also.

+ Took out default point ensure that the SNMP
entity giving access to an instance of measure address:
Added OwnersIpAddressType this MIB, is properly
configured to give access to be in pair with OwnersIpAddress

+ Added ippmSynchronizationResolution in the ppmSynchronizationTable:
It indicates the new time resolution (Henk request).

+ Added objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.

9 Document management

9.1 Open issues

Defval 0 for an object ippmReportSetupNotification in the report setup. OID ?
Usage of accessible-for-notify for an index ?
Subtype of InetAddress ?

9.2 Changes done since release 02

+ IppmHistoryIndex added Security/VACM:
sharing table removed;
ippmMeasure merged with networkMeasure and AggrMeasure to have
all networkMeasure objects in read only.
Indexes belong to the history table:

To differentiate the result index from the test packet order. table;
remove all reference to SNMPv1 ...inSNMPTrapPDU

+ IppmReportIndex System:
ippmSystemOperationalStatus added in the report table:
To differentiate

ippmSynchronizationTable adapted for proxy mode:
ippmPointOfMeasureIndex added to the result index of
ippmSystemCurrentSynchronization removed from the test packet order. system

capabilities:
ippmPointOfMeasureMetrics added to
IppmPointOfMeasureEntry;
ippmMetricType added to ippmMetricsTable;

+ Smilint: Owners
ippmMetricMaxHistorySize replaced with the option -s -l6:
Name length exceeded 32 chars:
Prefix:
+ ippmAggregatedMeasure -> ippmAggrMeasure;
+ IppmSystemSynchronizationDescription
-> ippmSystemSynchronizationDescr;
+ IppmReportSetupEventsDurationThreshold
-> ippmReportSetupDurationThreshold.

+ ippmNotifications identified under ippm quota in ippmOwnersTable;

+ TC OwnerString ippmOnHistoryFullAction replaced with IppmOwnerString to fix a warning
of the key length;

+ Gain 0 error and warning !

+ ippmAggrMeasureStatus removed:
The status of the row is managed resultsMgmt in the ippmMeasureTable

+ Notifications:
definition clarified;
ippmReportTimestamp added to notification
ippmEventsDurationExceededAlarm, ippmSingletonAlarm,
ippmCycleOfMeasureReport, ippmCompletedMeasureReport. aggr and network.;

+ IppmNetworkMeasureEntry :
ippmNetworkMeasurePoissonRate network measure:
ippmNetMeasureOperState added as the average rates.

+ TypeP redefined as a SnmpAdminString instead of a raw OCTET STRING
e.g: '080000080000000011020000'H -> "ip.ipip4".
open issue:
is there a need to indicate the number of parameters state of the
protocol identifier ? "ip.ipip4.2" or "ip.ipip4" ?

+ TypePaddress Textual convention created:
Dst and Src value is a display string instead network
measure
state;
added burst mode;
state of a raw OCTET
STRING. It is the list of parameters measure: nb of a TypeP.
e.g:
Src address TypeP is "ip.ipip4": 128.2.6.7 in 192.168.1.1.
Src value was '0A04C0A801010480020607'H.
Src is now "192.168.1.1 128.2.6.7".

open issue:

is there any potential parameter with one singletons collected and oper status
added;

+aggregated metric:
fast report added to get raw results by email;

+ report setup:
onReportDeliveryClearHistory removed from IppmReportDefinition;

+ Map field added to network, aggr and report tables to help to map
on topology map or more space
inside ?

11. admin view.

10 References

[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.

[2] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring
Connectivity", RFC 2678, September 1999.

[3] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay
Metric for IPPM", RFC 2679, September 1999.

[4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet
Loss Metric for IPPM", RFC 2680, September 1999.

[5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay
Metric for IPPM.", RFC 2681, September 1999.

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

[7]

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

[8]

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

[9]

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

[10]

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

[11]

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

[12]

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

[13]

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

[14]

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

[15]

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

[16]Case,

[12]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.

[17]

[13] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)",
RFC 2574, April 1999.

[18]

[14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996.

[19]

[15] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999.

[20]

[16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.

[21]

[17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
to Version 3 of the Internet-standard Network Management
Framework", RFC 2570, April 1999.

12.

11 Acknowledgments

A Kerbe.

13.

12 Authors Addresses

Emile STEPHAN
France Telecom R & D
2 avenue Pierre Marzin
F-22307 Lannion cedex
Phone: (+ 33) 2 96 05 11 11
Email: emile.stephan@francetelecom.com

Jessie Jewitt
France Telecom R & D
801 Gateway Blvd. Suit 500
South San Francisco, CA 94080
Tel : 1 650 875-1524
Email : jessie.jewitt@francetelecom.com

Full Copyright Statement

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 its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.