Inter-domain Performance Monitoring- Activities List

Activities list

The activity will investigate the following topics:

We are currently looking for people to participate/lead one (or more) of these tasks.

There is also a strong need to contact other groups working in the same area of activities as


Activities description

Metric monitoring, metric accuracy and measurement methodology recommendation

Investigation of the metrics which can be monitored, their parameters, their targeted accuracy. Recommendation on how to monitor the metric have to be done (traffic pattern, etc). The group must have a look to the IETF IPPM working group, the people working in this fields and the users to investigate their needs.
The group will have to inter-act mainly with the Domain Central Tool architecture, data storage, the measurement box guideline groups.


Measurement box guideline

Provide a measurement box functionality wish list. The functionality wish list covers the metric, the parameters, the measurement accuracy, the data accessibility, the data storage, the software requirements, hardware requirements, protocol requirements, the establishment of a monitoring "session" etc This list will be provided to measurement box developer to show the project needs.
Some information about GPS and NTP should also be provided.
The group will inter-act with the data storage, metric monitoring, inter-domain and intra-domain measurement protocol groups.


Inter-domain and intra-domain measurement protocol

Must work on the information fields of the packets exchanged between two measurement boxes (interaction with IPPM if something not adequately specified).
An investigation of the various inter-domain scenario must be done and define the actions which have to be taken in case of difference of services between domains, etc
The group has to inter-act with the measurement box guideline and central domain tool architecture group.


Inter-domain metric additivity and user representation

Investigation of the user data representation. Must classify the users into group and identify their needs and the most useful way of presenting measurement results to the users (e.g. presenting them against reference values).
Must also investigate the metric additivity between domain and which values have to be requested between domain (edge to edge or the value measured on all the sections of a given path).
The group has to inter-act with the metric and central domain tool architecture and data storage groups.


Data storage, data retrieval and data analyses

Investigation of the best way to keep the data stored in a domain in terms of BD location (central DB, distributed), information contained (raw data or statistics). How to retrieve the data.
Interaction with metric additivity and user representation, central domain architecture, measurement box guideline groups.


Domain central tool architecture

Should design the general model architecture then update the design based on the input from other groups. The design has to be divided into several modules which can be implemented separately. This requests the definition of the various modules, the specification of their actions and the definition of inter-actions between the different modules (information contained in the message exchanged between the modules).
The resulting tool should be open source, portable, scalable to be able to handle additional metric and features, should also define what happen in case of request with a non standard format, error messages, communication with other domain tools - user interface, "path finder" module, data analyse.
This group has to inter-act with almost every other group.


Domain central tool implementation

Implementation of modules specified by the domain central tool architecture group and test these modules.


Inter-domain measurement request protocol

Specification of the communication between the domain central tools of different domains. This contains the message format, the information fields and their value, etc. Must be able to be extended to additional metric/statistics/services/... Should have a loot to the IPPM and e2epi groups.
Should inter-act with the architecture and metric groups.


Finding a path in a domain

For a given source-destination IP address, or a traceroute output, find the path and the measurement points which have to be used in a domain. Should also investigate how to retrieve the inter domain data.
Inter-action with the domain central tool architecture and the inter-domain and intra-domain measurement protocol groups.


Trial

Establishment of an embryo of monitoring infrastructure in at least three consecutive domains. These domains should install the domain central tool and some measurement points. The data presentation, measurement concatenation, data exchange can be tested.


Contact: Performance monitoring mailing list or Nicolas Simar Performance monitoring home page