[rfc-dist] RFC 5388 on Information Model and XML Data Model for Traceroute Measurements
rfc-editor at rfc-editor.org
Thu Dec 11 15:12:49 PST 2008
A new Request for Comments is now available in online RFC libraries.
Title: Information Model and XML Data
Model for Traceroute Measurements
Author: S. Niccolini, S. Tartarelli,
J. Quittek, T. Dietz, M. Swany
Status: Standards Track
Date: December 2008
Mailbox: saverio.niccolini at nw.neclab.eu,
sandra.tartarelli at nw.neclab.eu,
quittek at nw.neclab.eu,
thomas.dietz at nw.neclab.eu,
swany at UDel.Edu
I-D Tag: draft-ietf-ippm-storetraceroutes-12.txt
This document describes a standard way to store the configuration and
the results of traceroute measurements. This document first
describes the terminology used in this document and the traceroute
tool itself; afterwards, the common information model is defined,
dividing the information elements into two semantically separated
groups (configuration elements and results elements). Moreover, an
additional element is defined to relate configuration elements and
results elements by means of a common unique identifier. On the
basis of the information model, a data model based on XML is defined
to store the results of traceroute measurements. [STANDARDS TRACK]
This document is a product of the IP Performance Metrics Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist