How to store traceroute measurements and related metrics

Document Type Replaced Internet-Draft (individual)
Author Saverio Niccolini 
Last updated 2006-10-17 (latest revision 2006-03-10)
Replaced by RFC 5388
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ippm-storetraceroutes
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This memo describes a standard way to store traceroute measurements and related metrics. To better address the traceroute measurements storing issue, the authors first of all give a definition of the traceroute tool, describe the tool itself as well as its parameters and the default values on the most common operating systems and the output results that can be stored. Afterwards, the common information model with the base elements of the traceroute measurement storing is defined dividing the information elements in two semantically separated groups (configuration elements and results ones). Moreover an additional element is defined to relate configuration elements and results ones by means of a common unique identifier. On the basis of the information model a data model is then proposed in order to actually store the traceroute measurements. Finally considerations on how to extract relevant metrics related to traceroute measurements are given.


Saverio Niccolini (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)